Prove atomic capture occurrence storage

[flyingrobots]

Goal

Prove whether one immutable capture occurrence per complete Git WARP entity admission can replace the current paged source authority without hiding enumeration authority in a manifest or contaminating performance evidence.

Plan

• Freeze the capture-occurrence identities, invariants, chronology law, and falsification gates.
• Prove one-patch entity birth and restart-stable exact recovery against exact git-warp 19.1.0.
• Falsify complete basis-bound enumeration through the supported 19.1 application surface.
• Certify additive real-corpus replay in a coexistence repository.
• Compare the current paged adapter and atomic adapter in independently populated repositories.
• Demolish and rebuild derived projections with identical fingerprints.

Current status

Gate 1 passes. One complete entity admission produces one writer patch; the Think receipt preserves capture ID, intent ID, allocated representation subject, opaque occurrence, outcome, and evidence basis; both initial profile values round-trip after every runtime closes and a fresh runtime opens. Equal payload bytes under distinct acts produce distinct subjects and occurrences.

Gate 2 is blocked by an exact executable witness. After restart, the supported git-warp 19.1 Runtime, Lane, captured coordinate, coordinate optic, coordinate source, and advanced exports expose no basis-bound entity enumerator. The adapter therefore returns typed CAPTURE_ENUMERATION_UNAVAILABLE with the actual unreadable basis. It does not fall back to a manifest, deep import, raw ref decoder, or projection.

Gates 3 through 6 are prohibited until complete source enumeration is available. This is a stacked experimental PR; PR #29 remains the v19 runtime prerequisite. The default Think storage path is unchanged, no retained mind is touched, and no git-warp or lower repository was modified.

Validation: npm run test:fast passes 199/199; the focused atomic gate suite passes 4/4; Markdown lint, Mermaid rendering, Git diff checks, and both runtime-truth ratchets pass.

Open questions

• Should a future, separately authorized git-warp change expose a complete basis-bound entity enumeration Observer, or should the atomic representation adopt a different single-patch discoverability invariant?

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[flyingrobots]

Gate 2 found the experiment stopping boundary. Exact entity admission and restart recovery work, including distinct identities for equal payloads, but the supported 19.1 application surface cannot enumerate all capture entities from repository, lane, and basis after manifests and projections are gone. Proceeding to replay would make the manifest silently authoritative, so migration and performance work are now intentionally blocked. No production path or lower repository changed.