Repository navigation
feat(gateway): implement AP073 native agent delegation on AP074 - #215
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AP074 supplied one bound effect and recovery owner but could not enforce enrolled machine → A → B delegation with shared ancestor capacity and scoped information flow. This implements AP073 on those owners: native enrollment, scoped effects, permanent ancestor reservations, fresh revocation fences, exact independent approval, controlled disclosure, created-resource recovery, commissioned successor identities, coordinated federation and native records conformance.
Provider writes remain data-only gateway recipes. Admission, capacity and recovery use the existing journal and final entry fence. Superseded disposable schemas are rejected directly. The original AP073 checkpoint remains preserved on
codex/identity-authority-foundationat97163513.Review map:
docs/specs/0073-identity-authority-and-enforcement-foundation.md.docs/plans/0073-assurance-map.mdand ADRs0018–0022.docs/plans/0073-foundation-assessment.md.Validation on
804bd57a9fbc95c2d0976dc59c5ac9a9282ce3e4:Assurance remains scoped: translated leaves do not establish a full-product theorem; tree/origin/backend composition remains reviewed and tested product glue. Federation requires one coordinated authority store. Safe restoration requires an independently authenticated checkpoint/floor and operator quarantine. The installed signer is scripted independent approval evidence, not a human-presence trial. Native records and provider doubles do not establish production-provider qualification. AP070 remains an independent application-owned reference. No merge or deployment was performed.