feat(uci): add admitted collective memory boundary - #278
feat(uci): add admitted collective memory boundary#278Tarik Skalić (tarikskalic33) wants to merge 30 commits into
Conversation
|
Deployment failed for project hub with the following error: Learn More: https://vercel.com/tariks-projects-e9198507?upgradeToPro=build-rate-limit |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
aegisomega | 1560628 | Commit Preview URL Branch Preview URL |
Aug 20 2026, 03:00 PM |
|
Deployment failed for project hook-generator with the following error: Learn More: https://vercel.com/tariks-projects-e9198507?upgradeToPro=build-rate-limit |
|
Deployment failed for project hub with the following error: Learn More: https://vercel.com/tariks-projects-e9198507?upgradeToPro=build-rate-limit |
|
Deployment failed for project platform-picker with the following error: Learn More: https://vercel.com/tariks-projects-e9198507?upgradeToPro=build-rate-limit |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Deployment failed for project platform-picker with the following error: Learn More: https://vercel.com/tariks-projects-e9198507?upgradeToPro=build-rate-limit |
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
UCI-6 — Collective Memory Admission
Status: IMPLEMENTED / SECURITY-REVIEW HARDENED / RESTACKED / EXACT-HEAD VERIFIED / READY FOR REVIEW
Exact hardened stacked parent:
#277@be07805af9887ff15272167740b07cf958c3137eExact reviewed head:
156062855a91b77133d8999ce34883432435b167Established local/reference contract
authority=EVIDENCE_ONLYand authority weight0;AdmissionRecordV1re-read from the local admission store and exactTransitionIdentity.action_digest == MemoryProjectionRequestV1.rootbinding;MEMORY_INTERNAL_BASE_DIRECT_USE_FORBIDDEN);UCI-6 security RED → GREEN
Independent UCI-6 diff review found the importable prestate-less internal memory-store path. A regression was committed before the patch:
Focused GREEN:
Parent-chain hardening inherited by UCI-6
Parent #276 was independently reviewed and hardened after the first UCI-6 reviewed checkpoint. The inherited effect-evidence boundary now rejects ordinary fabricated
EffectWitnessconstruction, uses descriptor-relative POSIXO_NOFOLLOWcontainment for the local filesystem reference adapter, applies bounded streaming hashing, and locks its own frozen-parent CI contract. Parent #277 was then restacked and reverified on that hardened UCI-4 head.Current reviewed parent evidence:
The detailed chronology is repo-bound in
docs/audits/2026-08-20-uci6-parent-review-hardening-addendum.md.Second fail-closed UCI-6 restack
UCI-6 was advanced with a true two-parent Git merge, not copied parent state:
The exact parent delta from the prior reviewed UCI-5 head
c1a562…tobe07805…was six files only: four UCI-4 hardened files plus the UCI-5 workflow and CI-contract test.Before changing UCI-6's frozen-parent contract, native CI failed closed exactly as intended:
No semantic result is promoted from that failed-lineage candidate.
Final exact-head evidence
UCI-6 Collective Memory Contract— run32383398222, job96471870476— SUCCESSOther exact-head gates on
156062855…:32383398222— SUCCESS32383398194— SUCCESS32383398202— SUCCESS32383398216— SUCCESSSKIPPED; not counted as pass/failure evidenceThe UCI-5 PR-native workflow is intentionally scoped to its own frozen-parent PR. Its three CI-contract guards execute directly inside the UCI-6 exact-head gate instead.
Explicit non-claims / residual boundary
This PR establishes a local SQLite reference memory boundary, not production distributed memory or semantic truth.
The process-local effect-witness issuance boundary inherited from UCI-4 is not a cryptographic attestation mechanism. The descriptor-relative filesystem hardening is a POSIX local/reference boundary and does not establish an atomic snapshot against a privileged adversary.
Parents #276 and #277 are READY FOR REVIEW on their exact hardened heads. No merge to #277, #276, #275, or canonical
mainoccurred.