Skip to content

docs(verifier): add edge verification recipe#785

Merged
jithinraj merged 1 commit into
mainfrom
docs/v0-14-4-edge-verifier-recipes
May 18, 2026
Merged

docs(verifier): add edge verification recipe#785
jithinraj merged 1 commit into
mainfrom
docs/v0-14-4-edge-verifier-recipes

Conversation

@jithinraj
Copy link
Copy Markdown
Member

@jithinraj jithinraj commented May 17, 2026

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

  • New 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).
  • New 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.md index updated with a recipe row.

Out of scope (no behavior change)

  • No schema changes.
  • No registry changes.
  • No type URI changes.
  • No conformance changes.
  • No API / CLI / package-publication / wire surface changes.
  • No live-network test.
  • No hosted-verifier product language.
  • No release-state transition; docs/releases/facts.json untouched.

Posture

  • Generic edge recipe first; provider-specific references second. The "Minimal deployment pattern" section teaches the bounded verification shape generically. Cloudflare Worker and Docker Compose appear only inside the "Provider-specific references" table as one-line stability-class rows.
  • Cites repo-local source-truth Body cap 256 KiB, JWKS fetch timeout 5,000 ms, JWKS keys cap 100, TTL bounds 60..86,400 s default 3,600 s, Node resolver outbound 30,000 ms default, redirect chain cap 5 — all restated from docs/specs/RESOURCE-LIMITS.md. Verify report shape and error shape link to packages/schema/openapi/verify.yaml and RFC 9457 Problem Details.
  • PEAC does NOT block covers six bounded actions: host the governed runtime, authorize the action, route agent traffic, enforce runtime policy, operate payment rails, or become an edge platform. The boundary is stated once in the recipe and verified by the doc-truth test.

Drift sentinels (unchanged from post-PR-1)

  • build_targets = 107
  • published_packages = 36
  • conformance_requirement_ids = 290
  • conformance_sections = 32
  • extension_groups = 19
  • receipt_types = 61
  • API contract allKeys = 27

Validation

  • 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.

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.
@jithinraj jithinraj merged commit 72b7aa2 into main May 18, 2026
25 checks passed
@jithinraj jithinraj deleted the docs/v0-14-4-edge-verifier-recipes branch May 18, 2026 01:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant