Repository navigation
docs: declare Corpus v2 purpose and building blocks - #85
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.
Declare the user promise and verified public-contract building blocks in
corpus.jsonschema v2. Preserve the existing documentation selection and repin local docs commands to Corpus340b66fc8f723c1babe35fce8240c82cd196b0db.Replace only the root-manifest repo-map pattern
docs-kit.jsonwithcorpus.json: repo-map swap only; this repo has no Veritas attestation chain yet (pre-existing). No bootstrap or policy-change attestation was created.Local evidence: the initial sweep ran readiness with Veritas 1.7.3. This follow-up runs
attest statusand full readiness with Veritas 1.10.1, including the unchangednpm run verifygate.CI evidence:
npm run veritas:readinessuses lockfile-resolved Veritas 1.7.4. The follow-up also ran that normal local readiness script with 1.7.4: exit 0, with the same three pre-existing missing-chain/trust-status warnings. This local run is separate from the hosted readiness lane.Pinned Corpus check passes. Hosted results must be read on this PR’s current head; local evidence is separate.