Every file is generated from the same validated input. The manifest records each file hash and a deterministic content root so a recipient can verify the bundle.
README.mdHuman-facing entry point, boundaries, and use sequence
implementation-pack.jsonCanonical machine-readable implementation package
executive-implementation-brief.mdDecision, Fit, operating posture, constraints, and critical open decisions
decision-design.jsonThe validated source Decision Design, unchanged
system-architecture.mdRequired components, data flows, trust boundaries, and excluded higher authority
evidence-contract.mdSources, freshness, effective time, validation, gaps, conflicts, and dependencies
authority-and-human-controls.mdAI may/may-not, approvals, limits, abstention, override, stop, and escalation
decision-record.schema.jsonDecision-specific trace contract separating recommendation, authorization, execution, and outcome
evaluation-and-rollout-plan.mdComparator, indicators, staged rollout, stop conditions, and authority-expansion evidence
failure-and-recovery-plan.mdPrevention, detection, fail-closed behavior, recovery, rollback, and ownership
implementation-backlog.mdSequenced phases, dependencies, acceptance evidence, and blocked open decisions
production-acceptance-checklist.mdUnverified gates that must pass before production reliance
build-buy-rubric.mdVendor-neutral evaluation requirements and accepted-only implementation context
codex-handoff.mdStandalone implementation prompt with scope, tests, prohibitions, and proof requirements
unresolved-decisions-and-approvals.mdUnknowns, conflicts, assumptions, approvals, and accountable owners
manifest.jsonPer-file hashes, sizes, roles, and deterministic content root