feat: finalize DGAF v1 governed control plane with TGL hardening

[ndrorchestration]

Purpose

Finalize the viable Governed Recursive Control Plane subset as a clean DGAF v1 integration candidate.

Included

• immutable GovernanceEnvelope with downward-only authority/tool/data/risk/budget inheritance;
• deterministic ControlPlane lifecycle, active-parent child creation, bounded depth, and fail-closed budget/concurrency handling;
• exact state identity and cycle detection;
• append-oriented branch provenance registry;
• explicit proposal/authorization/commit barrier;
• deterministic control-plane and TGL lifecycle integration tests;
• capability-boundary regression coverage;
• hardened TGL status reduction and complete audit sealing;
• dedicated CI lane with exact PR-head checkout assertion and pinned CI dependencies;
• deployment workflow hardened to attest READY production deployments against the exact Git SHA;
• architecture, file-tree, canonical agent-role mapping, and finalization-gate documentation;
• current-state and Notion/GitHub governance reconciliation.

Cross-surface reconciliation

PR #139 is the canonical current engineering lane. PRs #132/#133/#134 are historical/superseded remediation records. Issue #137 remains the canonical deployment/source-provenance gate.

Boundary

This PR is non-authorizing. It does not rebind PDMAL, create a freeze, grant pilot authorization, unblind data, or change empirical N. PDMAL remains an optional governed execution substrate.

The separate ndrorchestration/agent-control-plane repository remains reference material for contract comparison, not a dependency.

Verification

Current PR #139 head: dad96fc74c052b6251fc2fe4ae79205b024a741b.

The substantive implementation checkpoint a728ce3ee8a024646c0971c9d4f392abaa3d691a completed dedicated DGAF v1 Control-Plane Contract run 33247361730 with exact candidate checkout PASS, pinned dependency setup PASS, and 41/41 control-plane/TGL/adversarial/capability-boundary tests passing.

All commits after a728ce3… through the current head are documentation/governance/CI provenance-hardening changes; no later code-changing verification claim is inferred unless a corresponding exact-head run exists.

The feature branch is 0 commits behind current main. A non-destructive two-parent merge incorporated current mainline history without force-moving the branch.

Vercel source identity is now explicitly enforceable by the deployment workflow: it requires READY, target=production, a Vercel Git source SHA, and equality between that source SHA and GITHUB_SHA; exact deployment evidence is retained as an artifact. Issue #137 remains open until a deployment of the verified intended candidate is observed and the runtime checks pass against that exact source.

Experimental boundary

Current experimental state remains PRE-FREEZE / FAIL-CLOSED / NOT AUTHORIZED / N=0. No freeze was created, no pilot was authorized, no data were unblinded, and no empirical result was generated by this engineering PR.

[vercel]

Deployment failed for project dynamicgovernanceagenticformation with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ndrorchestration?upgradeToPro=build-rate-limit

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dynamicgovernanceagenticformation	Ready	Preview	Aug 29, 2026 10:13am