ARCHITECTURE §6: the last cycle, from the side that was actually loose - #40
Merged
Merged
Conversation
§6 recorded `policy <-> authority` as the one cycle that stays, with a reason that was true but described only one side: `_from_section` constructs an `Authority` and `canonical_grants` consumes one, so neither moves below `policy.py`, and moving their two callers up to `control.py` would change what `policy_hash` is taken over. The other side was `authority.py` importing eight names from `policy.py`, none of them `Policy`: schemas, the strict loader, the condition grammar, type-strict equality, key validation. That is the document grammar, and it is shared vocabulary rather than either axis's property. It lives in `grammar.py` now. The v0.3 exception is honoured more exactly rather than repealed. §4.5 requires the two axes to share ONE condition evaluator; it is now owned by neither. `CLAIMS.md` gains three corrected file paths the repointer cannot fix on its own: it moves line numbers within a file and these symbols changed file. Signed-off-by: arpan <contact@arpanghoshal.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
Warning Review limit reachedNext included review available in 3 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (13)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Pairs with the kernel PR of the same branch name.
§6 recorded
policy <-> authorityas the one cycle that stays. The reason was true but described one side only. The other side wasauthority.pyimporting the policy document grammar frompolicy.py, which is shared vocabulary rather than either axis's property; it now lives ingrammar.py, below both, and SPEC-v0.3 §4.5's one-evaluator requirement is honoured more exactly than before.Also here: the regenerated API reference, and three
CLAIMS.mdfile paths the repointer cannot fix on its own, because it moves line numbers within a file and these symbols changed file.🤖 Generated with Claude Code