# Knowledge Source Boundaries and Evidence Hierarchy

This pack describes the current Logline language and product concepts using reviewed repository source and maintained documentation. It must not be used to infer capabilities or security guarantees absent from the referenced implementation and accepted verification.

## Evidence priority

1. Current grammar, validation, compiler and Engine behavior determine accepted syntax and runtime semantics.
2. Exact, validated example programs and paired fixtures demonstrate their stated cases, not all possible inputs.
3. Workbench and Enterprise source together with tests establish the existence of implemented controls and contracts.
4. Product documentation explains intended user workflows and deployment requirements; requirements/design documents alone do not establish shipped behavior.
5. AI-generated prose, recommendations and example snippets are hypotheses until checked against current authoritative source and data.

## Distinguish these statuses

- **Documented / designed:** requirement, architecture, or intended behavior; not proof of implementation.
- **Implemented:** represented in current source; may still require environment-specific validation.
- **Verified:** explicitly tested or accepted for a stated scope; never broaden the scope without evidence.
- **Released / publicly available:** tied to actual publication or live service availability, not to a successful local build alone.

For all operational questions, identify what information the user must supply (for example source clock meaning, authority, deployment environment and actual manifest contract) instead of fabricating missing values. Never assume a public AI service response has been verified simply because the Workbench can prepare a request.

## Privacy and security

A `.lgl` file is declarative source, not a script for running system commands. Do not include credentials, customer logs, proprietary identifiers, individual usage information, signing keys, sensitive deployment configurations or authenticated customer API responses in public-facing examples. An assistant knowledge corpus and a customer Enterprise runtime are different trust domains. Public crawler access to this pack is not permission to collect customers' source or logs.

## Corpus identity

Repository source reviewed: `e2d3b2f1`. The repository may evolve after this review; future updates should regenerate the pack and revalidate examples. The published mirror and aggregate text resources must be generated from the maintained `docs/ai-assistant/source-pack/` directory rather than edited separately.