v1.9.1 — Provenance (Clearance, Holding Pattern, Tail Number)

Provenance — v1.7.0 → v1.9.1

Three mechanisms, one throughline: closing gaps in what the runtime could say about its own state — which exact state an approval was checked against, which concrete move fired versus its reusable type, whether traversal is finished versus merely blocked on something external. Each is a soundness property of the logic/traversal layer itself, independent of any particular model or harness.

Name	Mechanism	Version
Clearance	AuthorizationReceipt — approval scoped to one transition and the exact inspected state it was issued against, not an ambient authorized=True boolean	v1.7.0
Holding Pattern	PendingInput / OutcomeKind.AWAIT — waiting on a declared external dependency, distinct from IDLE	v1.8.0
Tail Number	MoveIntent / inspect_move() — a concrete proposed move's own identity, distinct from its reusable transition type	v1.9.0
—	AuthorizationReceipt expiry rebound to a dedicated _authorization_clock, found via adversarial testing against the live engine, not design review	v1.9.1

Also in this release:

• 3 new runnable example scenarios (python -m fpf_thinking_map.examples) — one per mechanism, alongside the existing Ignition Lock walkthroughs
• ARCHITECTURE.md and README updated to match the current module graph and outcome/check counts
• First CHANGELOG.md for the project

Full narrative: docs/deep/EXPANDED_PROVENANCE.md
Version-by-version: CHANGELOG.md

26/26 self-verification checks pass (python -m fpf_thinking_map.verify); dev_mcp's own 38/38 test suite unaffected.