feat(ci): add dormant proof release contract
Maintainers usually reply within 1 day
Assessment
This issue has not been assessed yet.
Description
Existing Issue Search
- I searched existing issues and will add evidence to a canonical tracker when applicable.
Parent #2026 tracks the complete controls; this is the dedicated phase 1 delivery tracker, not a replacement for #1810.
🔍 Observed Consequence
Missing controlled boundaries prevent safe completion of the remaining retirement evidence. A single oversized change would couple CI security review, integration and rollback.
💡 Desired Outcome
Deliver and review one coherent dormant preparation phase without closing #2026 or #1810 prematurely.
📦 Affected Area
Other
Release Context
Not release-specific. Initial canonical main b3c399a12a115f556ff95430cd1c3b2b4e065936. Later phases must start from freshly verified canonical main containing the previous human-integrated phase.
🔄 Workarounds and Constraints
Refs #2026, #1810 and #2008. No changes to #2008, no production activation, environments, credentials, permissions, hosted probes, old fixtures, required-context set, queue or merge operations. No experimental allowance is reused. Default OFF, no additional client requests or changed producer results.
📎 Additional Context
Accepted phase scope
Implement only the default-off manual-release foundation: a bounded read-only witness contract bound to allowlisted numeric actor, case, run/attempt, phase, original head, workflow source and a fresh single-use checkpoint. Preserve the original supplied result and inputs; default OFF performs zero extra reads. No producer or CI orchestration wiring in this phase. Documentation must state this is a foundation, not hosted gate evidence.
Verification and dependencies
Focused deterministic RED/GREEN, read-only/no-side-effect refusal cases, applicable Node and workflow contracts, independent high-risk verification and the user-owned native review process. Normal draft PR CI is authorized; live scenario proof is not. No local test or isolated model counts as canonical gate proof.
Delivery strategy is a verified-main chain. Each PR closes only its own phase issue and references #2026/#1810. Phases2/3 wait for the preceding phase to be integrated by a human; there is no automatic Ready/merge. Only the final completed phase may also close #2026, never #1810/#1802.
- Dominant language
- Go
- Stars
- 7.1k
- Forks
- 729
- Avg merge
- 8h 26m
- Merged PRs (30d)
- 356
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Gentleman-Programming/engram
-
status:needs-review type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Gentleman-Programming/engram#2079 ·
Maintainers usually reply within 1 day
-
status:needs-review
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Gentleman-Programming/engram#2065 ·
Maintainers usually reply within 1 day
-
priority:medium status:needs-review type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Gentleman-Programming/engram#863 · 1 comment ·
Maintainers usually reply within 1 day
-
status:needs-review type:question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Gentleman-Programming/engram#2080 · 1 comment ·
Maintainers usually reply within 1 day
-
status:needs-review type:bug
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Gentleman-Programming/engram#2078 ·
Maintainers usually reply within 1 day
All issues in Gentleman-Programming/engram
Similar issues
-
compress: block buffers get re-zeroed on every call, and the zeroing is immediately overwrittenOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/ch-go#1218 ·
Maintainers usually reply within 13 days
-
automation models
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
podman-container-tools/podman#30031 ·
Maintainers usually reply within 1 day