Skip to content

Migration document preservation

The migration design, plan, and execution-prompt documents necessarily carried donor identifiers, so they cannot stay in the current tree once the strict residual gate runs with no exceptions. They were archived read-only outside every repository and then removed from this tree. Git history retains them.

This record is deliberately sanitized: run ID, relative archive paths, hashes, counts and status only. It contains no donor identifier, URL, or raw evidence value.

  • Run ID: 20260725T070221Z-068ccbb1a63b1fc6
  • Producer: docs/QA
  • Archive root: mamnajem-migration-archive/<run-id> (outside all six repositories)
  • Sealed by: scripts/seal-mamnajem-evidence.sh migration
  • Documents archived: 8
  • Status: sealed, verified read-only, sources removed

Archived documents

Paths are relative to the run directory. SHA-256 is of the file as it existed in this tree immediately before removal, and is reproduced in the archive's MANIFEST.sha256.

Relative archive path SHA-256
plans/backend.md f1627d4aa99d398958b24c6e7f5be8f0934e55bc28c1001378ded9e437191217
plans/forge-architecture.md 23cc97f5f500d9c9b89a5e1f2a8293362d11b59f4278e41dd8562b9e79a07268
plans/greenfield-big-bang-master.md e15ded0fdc7fb06fe6f5c09d1804a5405a9559b5ea6b78151d5d48127af9e4d8
plans/mobile.md 396cb8290fe6d69b7969a0cda71e5ca60015d374e52a884e5de36868b509414b
plans/verification-cutover.md f9a4a72959eb6af4efb3a15c758ec778f655933b9b87c2987bf21d2859d8614f
plans/web-admin.md 3f1f626b62bc506ca7e2badfc36ca591a9a3a8a972841413d3ef9324c0c599fc
prompts/greenfield-execution-prompt.md 215a7df6bd459781a6f6f28a2ec2ab3659d319d0b5627721506af628e4f8faf6
specs/greenfield-big-bang-design.md 5fb44f592730e84cc7cc8fe2048fdfde412f90f1ee70cc87b26b4dc3ac048cb4

What the sealer guarantees

seal-mamnajem-evidence.sh refuses symlinks, wildcards, absolute or traversing destinations, colliding destinations, an existing run destination, Terraform state and saved plans, and sources matching credential patterns. It copies into a same-filesystem hidden incoming directory, writes a sorted relative-path MANIFEST.sha256 that excludes itself, verifies every byte, renames atomically into the run directory, applies read-only modes, and verifies again. Sources are removed only when the explicit approval token is supplied, and their absence is proven afterwards.

Bootstrap evidence — sealed 2026-07-29

The bootstrap evidence was the last thing this record left open. It could not be archived while architecture/scripts/verify-mamnajem-project-governance.cjs read the migration ledger from it at run time: removing the directory would have broken the check that proves repository governance.

That tie is gone. The verifier now reads the ledger from MAMNAJEM_MIGRATION_LEDGER_FILE, a GitLab file variable on mamnajem/architecture, and still accepts the directory when the file variable is absent. The ledger stays out of every tree because it carries donor project IDs, which is exactly what the residual gate exists to keep out.

  • Run ID: 20260725T070221Z-068ccbb1a63b1fc6
  • Archive root: mamnajem-bootstrap-archive/<run-id> (outside all six repositories)
  • Sealed by: scripts/seal-mamnajem-evidence.sh migration
  • Files archived: 160, plus MANIFEST.sha256
  • MANIFEST.sha256 digest: 98596fd73d619972c7481f1ca9c715b7d817aeb188a7a5188ffb84c70765042d
  • Status: sealed, sha256 -c verified after sealing, mode dr-x------, sources removed

Contents: the migration ledger, the source commit ledger and its digest, the source ref/object inventory, the history-copy evidence (per repository: inventory, governance, branch and internal-ref tag maps), the naming contract and its digest, the final-gate record, the execution task ledger, and the provider-access preflight and secret-scan records.

Sources were removed after each archived copy was compared byte-for-byte against the source by digest, and their absence proven afterwards.

One finding the sealer produced

The sealer refused the first attempt: execution-task-ledger.md matched its AKIA[0-9A-Z]{16} rule. The strings were AWS access key IDs, not secrets, but a fail-closed gate is worth more than two literal identifiers in an archive, so they were redacted to AKIAYAKE<redacted>XX before sealing.

Reading the surrounding text turned up a real item rather than a formatting one. The ledger recorded an operator access key created 2026-07-25T16:57Z whose secret nobody held, left alive in case CI depended on it. It did not: it was last used 2026-07-26T01:44Z and appeared in no group or project variable across all six projects. It was deleted on 2026-07-29. The grant that allowed it — iam:DeleteAccessKey scoped to that one user — was published as policy version v4, used once, and revoked; the policy is back on v3 and v4 is deleted. The operator's remaining key still authenticates.