docs(plan): decision notes for held PRs #193 + #197#226
Open
hanwencheng wants to merge 1 commit into
Open
Conversation
…#197 (broker child-path policy) Both PRs conflict with arch.md as written; these notes lay out options + a recommendation + the exact arch.md edits each path would need, so the team can decide and the PRs can be reworked. Docs only. - issue-8: agent-omni generation suffix — recommend gen-0-bare (backward-compatible) - issue-7: child-path policy — recommend broker-side, renamed off 'TEE', bounded authority
This was referenced Jun 7, 2026
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.
What
Two decision notes under
docs/plan/that unblock the two PRs flagged hold in the review of #202 / #197 / #193 / #192 / #181:issue-8-agent-omni-generation-decision.md→ for Reserve generation suffix for child key derivation #193 / issue v0.1+: Generation suffix for child key rotation (/0, /1, /2) #8issue-7-child-path-policy-decision.md→ for Add TEE-side child path access policies #197 / issue v0.2+: TEE-side access control / security groups for child paths #7Why
Both PRs are foundational identity / trust-surface changes that conflict with
arch.mdas written — #193 changes the frozen canonicalagent_omni(§5/§6.2), and #197 adds an undocumented broker authority mislabeled "TEE" (vs §14/§16). Rather than merge or close blind, each note lays out the options, a recommendation, and the exactarch.mdedits the chosen path would require, so the team can decide and the PRs can be reworked coherently.TL;DR recommendations
//<label>(no change to today'sagent_omni), suffix only forN ≥ 1. Backward-compatible; still reserves the rotation namespace. First confirm omni-level rotation is even wanted vs. K3-epoch + device re-pair + fresh-label re-bootstrap.Docs only — no code changes.
🤖 Generated with Claude Code