feat(ci): wire dormant native and legacy proof boundaries

Closed
  • Is something wrong?
#2,030 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@dnlrsls is already working on this.

Since Oct 22, 2026.

  • #2041 by @dnlrsls — merged

Assessment

This issue has not been assessed yet.

Description

status:approved type:feature
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 2 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

After phase1 is integrated by a human, wire the actual native evaluator read continuation and actual legacy GHA job-completion boundary to the foundation, without changing original values, guards, required names or disabled API traces. A post-evaluation hold is NOT an in-flight witness. No API-created substitute check, source/provenance bypass or runtime activation.

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
10h 46m
Merged PRs (30d)
268

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Gentleman-Programming/engram

All issues in Gentleman-Programming/engram

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.