The deliverable
Anatomy of a Matrix Bundle.
Every build produces one controlled, signed bundle — not a pile of guessed code. It pins the architecture, the standards, the tasks, and the boundaries your AI coder must stay inside, then proves what it produced.
your-project / matrix-bundle
The contract — immutable
MATRIX_BLUEPRINT.yaml · locked
The architecture contract — stack, services, routes, pages, and tasks. The single source of truth the AI coder may not change.
MATRIX_STANDARDS.lock · signed
The exact standards pinned to this build — rule ids and digests from the chosen quality profile (NIST SSDF, OWASP ASVS & LLM Top 10, SLSA).
MATRIX_ALLOWED_CHANGES.md
Exactly which files and folders a batch may touch. Anything outside the allowlist is rejected on validation.
The work
MATRIX_TASKS.md
The scoped task list — each task names its allowed files, so the build advances one safe batch at a time.
MATRIX_ACCEPTANCE_CRITERIA.md
When each task is done — the commands (tests, lint, build) that must pass before a change becomes a commit.
coder-prompts/ · per coder
Ready, contract-bound prompts for Claude Code, Codex, Cursor, GitPilot, IBM Bob, and more — plus tool-native helpers like CLAUDE.md and AGENTS.md.
Docs & provenance
docs/architecture.md · docs/security.md
Human-readable architecture and security intent, generated from the blueprint and the active standards.
manifest.json · sbom.cdx.json · attestation.json
The signed proof — file digests, a CycloneDX SBOM, and verifiable provenance (Cosign / GitHub attestation). Provenance you can verify, not trust.
Validation is fail-closed. A change inside the allowlist that meets the criteria becomes an immutable Matrix Commit; a forbidden edit is rejected with a scoped repair prompt — under the public Ruslan Magana Definitions.