intent: portable-core-contracts - #184
Merged
Merged
Conversation
Owner
Author
Codex reviewer (cross-vendor, read-only)Reviewed-head: e96b5b7 Posted verbatim by The documentation-only amendment consistently replaces the single-PR delivery constraint with gated, dependency-ordered child parts while preserving the accepted contract and safety boundaries. No actionable regression is evident in the changed lines. |
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.
Tracks #155
Intake acceptance: #155 comment 5464340863
What changed
Boundary
This amendment changes only how the work is split and delivered. The five document kinds, three capability IDs, five permission IDs, v1 meanings, canonical bytes, error classes, claims-not-authority boundary, and no-live-activation outcome do not change.
Only
work/portable-core-contracts/intent.mdchanges. No implementation code, spec, plan, issue state, label, workflow, or PR #183 state changes here.After G1 merge, the old spec and plan are stale by design. Work remains paused until a new G2 spec-with-risk and high-risk plan are independently reviewed and operator-merged.
Proof
git diff --check origin/main...e96b5b7742b1de5a8265109a75f1346696f54d66: clean.f77fc1fdd8f7af228e7f211740901b265fc545ae.Human merge only. This PR does not merge or resume PR #183.