Semantic manifest basics

frontier discover infers a target mart from target/manifest.json (it will try dbt compile if the file is missing) and uploads a DRAFT mapping. It never activates automatically.

frontier discover
frontier discover --model customer_summary
frontier discover --yes

Review routes, grain, and confidence in Frontier, then Activate. Inferred routes and low-confidence mappings cannot be activated until they are confirmed. CI fetches the active snapshot at assessment start and fails closed when none exists (MANIFEST_NOT_FOUND / MANIFEST_NOT_ACTIVE / MANIFEST_IS_DRAFT).

Customer CI runs frontier manifest fetch and writes target/frontier-manifest.json. Later inspect/compare/prove steps pass --manifest-file so the assessment is stamped with that version, not whichever mapping is later active.

frontier manifest fetch --output target/frontier-manifest.json

--allow-local-manifest is for explicit local/demo overrides. It is not used in the generated GitHub workflow. See Configuration reference.