Repository navigation
CP-003: add canonical requirement graph and operation contracts - #7
Merged
Merged
Conversation
Activation: CP003-ACT-a1efe3b2-v1 No implementation code or remote write.
Owner
Author
CP-003 accepted publication and hosted-CI evidence
This comment supersedes only the PR description's pre-run |
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.
CP-003: canonical requirement graph and operation/result contracts
Why
CP-003 establishes the source-owned requirement graph and closed, versioned
operation/result contract boundaries required before later execution handlers
are implemented. It prevents schema presence, task status, presentation data,
or missing evidence from being mistaken for implemented or admitted product
support.
What changes
boundary.
diagnostic formats, and safe next-action tuples.
diagnostic evidence, backup sets, release manifests, graph, and catalog.
exit evaluation with serialized-result parity checks.
parsing/resource, plan identity, and presentation non-authority checks.
ADR/reference/source-CI documentation, and changelog entries.
This is a source-only foundation slice. It introduces no privileged executor,
collector, renderer, scheduler, release signer, backup service, admission
authority, deployment, or server operation.
Traceability
CP-003;coding/tasks/CP-003.mdG03/G04/G09/G19; UX-R01/R03/R07; UXS-C04/C12
a1efe3b27f3905d5ccf06aafcf31062e4b02aac3/dddc691ae2102ef3fe5c2d85d97db6c3d245f44e4bd079679b5a840b6f31dc20553fc5cf7b9f386amaintainer authorization for exact branch push and draft PR
CP003-ACT-a1efe3b2-v1; activation commit3a2633f8c73bba438a28ddb7385d23f255458321CP003-CPD12-IR1R2-dddc691a-v1; complete report SHA-2569238eb7cd2b441a2d82d076ef238411493c248fb9984e83b25b50902642f0b39;no unresolved material source blocker
CP003-E01-SOURCE-dddc691a-v1; evidence ZIP SHA-256181f5755db3abbfe1734e7feddae6f9de09787597b664e1ec4236814005b5413implementation paths; 51 base-to-candidate paths total
x86_64, CPython 3.14.7; lock SHA-256
1ac29d7c89c7c59afabe414429083786d9170c2b363ca61552dbbc0989a77faeand writers 1.0.0
Validation
CP003-CPD12-IR1R2-dddc691a-v1; independent AI review, not a second human approvalCP003-E01-SOURCE-dddc691a-v1a8c5a083ae88b29f2d3cf469648ba7c426106eccd06c390017c4e172f162a190Operator documentation and compatibility
The change adds ADR-0003 plus contract, evidence/status, and source-CI reference
documentation. Existing CP-002 configuration, JCS, package, CLI, and scanner
compatibility suites passed on the exact candidate. Unknown contract versions
and unowned values fail closed; no dependency, lock, or workflow file changes.
Risks and recovery
Later consumers still must implement and qualify authoritative policy loading,
evidence authentication, plan admission, durable execution, rendering,
backup/restore behavior, and release/product gates. A checksum proves byte
identity, not authenticity. If the task branch or
maindrifts from the exactrecorded identities, stop publication/integration and reconcile; do not force,
rewrite history, delete the branch, or reuse stale evidence.
Review and merge conditions
The maintainer accepted the exact reviewed and canonically tested source
candidate and authorized only branch publication plus this draft PR. Merge is
not authorized. Keep the PR draft, observe only its ordinary Source CI trigger,
and preserve the exact head/base identities. Any source change creates a new
candidate requiring affected review and testing. Task merge, if separately
authorized later, would not confer release, deployment, product, or server
qualification.
Opening this PR may trigger ordinary Source CI under the existing reviewed
pull_requesttrigger. No manual workflow dispatch or rerun is authorized.