{
  "name": "Logline AI Knowledge Source Pack",
  "purpose": "Knowledge-only RAG/training/crawler source pack for the current Logline v1 language and runtime concepts",
  "developmentStatus": "v1 under active development; source pack may be updated in place until release/distribution",
  "excludes": [
    "assistant chat API contracts",
    "edit-plan schemas",
    "assistant response JSON examples",
    "Workbench mutation internals",
    "customer-specific run manifests"
  ],
  "highPriorityRules": [
    "Declarative Logline clauses use =:; ordinary = is for bindings/definitions and named call arguments; == is equality; : separates object entries.",
    "Logline segment types are transition, event, group, repeat, parallel, and crossroads.",
    "Transition and event are direct record-matching leaves; Group is a bounded observation/derivation segment.",
    "Repeat, parallel, and crossroads are structured executable segment containers.",
    "Collector and const are declarations, not scenario segment types.",
    "attemptedBy may reference Transition, Event, or Group executable segments.",
    "Transitions do not support action/actions/effect/effects/handler/callback fields.",
    "A scenario can fail even when compiler diagnostics are empty.",
    "Canonical top-level record timestamps are normalized to CTE before Engine execution; payload timestamps are not automatically rewritten.",
    "time.reference returns a temporal-reference identity; time.anchor returns a resolved CTE timestamp.",
    "Missing named temporal references or anchors do not fall back to a canonical source clock.",
    "Multi-source record order is CTE timestamp, resolved source order, then source-local cursor order.",
    "record.index is the final canonical merged-stream index, not a source-local file index.",
    "Workbench AI question drafting, compiler review and isolated preview do not themselves send requests, authorize program changes, or substitute for a normal Run/Report.",
    "The hosted Workbench and customer-controlled Enterprise execution runtime have distinct roles.",
    "Implemented Enterprise capabilities are not automatically released or validated in every cloud environment."
  ],
  "reviewedSourceRevision": "e2d3b2f1",
  "knowledgeDomains": [
    "language-and-diagnostics",
    "canonical-records-and-time",
    "execution-and-reporting",
    "verified-examples",
    "workbench-workflows",
    "enterprise-runtime-and-licensing"
  ],
  "sourceBoundaries": "metadata/CAPABILITY_AND_SOURCE_BOUNDARIES.md"
}
