docs: proposed personal and team coding-agent assignment authority (JVNAUTOSCI-2755) - #643
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
1 participant
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.
The DGX pilot confines coding work to a configured delegator and repository, but that is not a general personal/team assignment-grant model. This documentation-only proposal defines explicit per-agent grants, trusted issuance and admission, repository/action scope and revocation recovery while preserving independent owners and team agents.
The source audit is refreshed against
a6074640f23dd1d714b2872c6f6cb35a94815ec7. It accounts for existing trusted-actor dispatch receipts, legacy creator-based admission, supervisor repairs and the documented Mac task adapter. The proposal extends existing dispatch provenance rather than adding a parallel admission record. It distinguishes source evidence, supplied controller runtime evidence and still-unverified canonical registrations/consumers.Merge decision changes — ready for documentation publication after the refreshed checks pass. The proposal remains Draft/proposed; merging grants no implementation, policy activation or deployment authority. Complete live inventory and refreshed private Von delivery remain task handoff work, not claims this PR makes. The retained original private delivery is acknowledged without treating it as read-back of revised content.
Validation: read-only source audit and allow/deny scenario walkthrough;
git diff --check; 112 local links/anchors resolved; six design tables (58 rows) rendered; 25 cited source symbols verified. No application code, live assignments, additional model runs, operational configuration or private evidence are included. GitHub syntax and secret checks must pass for the final commit.Decision surface: JVNAUTOSCI-2755. The worker has no canonical Von tools; Jira currently requires reauthentication. The authorised controller/operator must reconcile the live inventory, update the existing private full-design document, read back its task association/content as the requester and deliver/read back the exact document pointer before task completion. No grant, identity, runtime, database or deployment changes are requested.