Each file records a gap that, when opened, could not be closed by workspace code alone. Some required an external service account (payment merchant, IdP, or audio CDN); others required a product decision about identity, sharing, or audit semantics. These are dated decision records, not a live gap dashboard: contracts may now exist even when the original runbook remains useful as closure history.
Every record now uses the result-page evidence structure: dated frontmatter and opening disposition, an exact truth table, one evidence map, proven observations, explicit authority boundaries, portable rerun commands, source trail, cross-references, and open questions. That shape preserves the original decision while making later implementation progress legible without silently turning source presence into production proof.
Contents#
crypto-merchant-settlement.md— the fail-closed quote and signed settlement core now ship; a production invoice provisioner and chain watcher remain deploy-bound.nyx-logged-observation-contract.md— decision history for the canonical logged-observation contract, distinct from the observation-window forecast. The contract now ships asLoggedObservationSchemainlibs/contracts/src/nyx/index.ts.library-collection-contract.md— decision history for the canonicalLibraryCollectioncontract, now shipped fromlibs/contracts/src/library/index.ts.atelier-scene-contract.md— the canonicalAtelierScenedecision history: recipient identity, share scope, cue-privacy fields, and render-pipeline reference.AtelierSceneSchemanow ships.studio-scene-contract.md— what an authoring-sideStudioSceneneeds beyond path/session/kind: scoring, voice mapping, and publication gates.StudioSceneSchemanow ships.metis-course-proposal-contract.md— distinguishesMetisCourseProposal(a creator submits an idea) fromMetisCourseBuild(the curated course).MetisCourseProposalSchemanow ships.real-sit-audio-cdn.md— procedural BFF ambient audio and env-gated voice guidance now ship; recorded-media ingest, signed CDN/HLS delivery, and paid-content protection remain open.
How to extend#
When a new external dependency is identified, add a dated reconciled-partial
record with the same eight sections. Prefer one compact table and one restrained
flow over copied implementation snippets. Name what is already shipped, what is
deploy- or decision-bound, and the exact observation that would close the gap.