docs(verifier): add edge verification recipe#785
Merged
Conversation
Adds docs/SOLUTIONS/verify-at-the-edge.md, a generic edge verification recipe for PEAC records. Provider-specific references are kept in a separate section. The recipe restates existing verifier limits and resource-bound verification behavior from docs/specs/RESOURCE-LIMITS.md without inventing new values. Adds a doc-truth gate at tests/tooling/edge-verifier-doc-truth.test.ts that asserts H1, generic-first ordering, the full boundary block, and the absence of forbidden public-prose tokens. Updates docs/SOLUTIONS/README.md with the recipe row. No schema, registry, type URI, conformance, API, CLI, package-publication, or wire surface changes. docs/releases/facts.json untouched; build_targets remains 107.
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.
Summary
Adds a generic edge verification recipe for PEAC records, with provider-specific references kept secondary. The recipe restates existing verifier limits and resource-bound verification behavior from
docs/specs/RESOURCE-LIMITS.md.Scope
docs/SOLUTIONS/verify-at-the-edge.md(generic edge verification recipe; H1# Verify PEAC records at the edge; full "PEAC does NOT" boundary block; provider-specific Cloudflare reference confined to one row in a stability-class table).tests/tooling/edge-verifier-doc-truth.test.ts(24 doc-truth assertions across 7 describe blocks; forbidden-prose patterns assembled non-contiguously so the test source stays scan-clean).docs/SOLUTIONS/README.mdindex updated with a recipe row.Out of scope (no behavior change)
docs/releases/facts.jsonuntouched.Posture
docs/specs/RESOURCE-LIMITS.md. Verify report shape and error shape link topackages/schema/openapi/verify.yamland RFC 9457 Problem Details.Drift sentinels (unchanged from post-PR-1)
build_targets= 107published_packages= 36conformance_requirement_ids= 290conformance_sections= 32extension_groups= 19receipt_types= 61allKeys= 27Validation
pnpm exec vitest run tests/tooling/edge-verifier-doc-truth.test.ts— 24/24 pass.node reference/scripts/verify-local-doc-truth.mjs— exit 0; 26 files clean.node reference/scripts/verify-final-hygiene.mjs— 7/7 PASS.