site: promote CPB + composition — dedicated page, nav, registry accuracy - #14
Merged
Conversation
… accuracy - New /cpb.html: covers the Composition draft (CAN/WHO/WHAT/AUDIT framework) and CPB (jcs-n canonicalization, derived identifier, typed reference) side by side, the open registry (AAC #1, MachineMandate registering as #2, the three-rung owner-authored/third-party/provisional onboarding ladder), and the mutation-probe conformance rigor (condition-removed mutants, assertion -free checks fail CI). - Soften the "TypeScript SDK passes 21+ vectors" claim: verified locally and via CI that the published @agentactioncapsule/emit passes an earlier 21-vector snapshot, not the current 27-vector suite — claim now states the Python reference lib passes the full suite and a second implementation is in progress. - Fix "provisional registry" language and dead-end links: point at the real scitt-payload-binding REGISTRY.md and vectors/ instead of the AAC repo's unrelated test-vectors and the provisional-candidates doc. - Add a first-class "Composition (CPB)" nav item sitewide (top nav + docs sidebar where present) and strengthen the landing #cpb section with a CTA into the new page. - Fix stale draft-version citation: Bilateral was still cited as -00 in docs/bilateral.html; bumped to -01. - Add cpb.html to the Dockerfile COPY list and sitemap.xml. Boundary: mechanism + open registry + vectors + composition only — no KYB, Authority-operated framing, reputation/pricing, or two-sided-market language. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: stevenmih <stevenmih88-3@gmail.com>
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
Implements items 2–7 of asg
inbox.md[site-cpb-promote](item 1, committing the CPB -01 spec source toagent-action-capsule/spec/, is out of scope for this lane — flagged separately, see outbox).@agentactioncapsule/emit@0.1.0passes its bundled 21-vector CPB snapshot — but the canonicalscitt-payload-bindingvector suite has since grown to 27 vectors (NFC-boundary + nested-array-normalization additions), and the TS suite hasn't been updated. Softened the site's "byte-compatible, independently verified" claim to accurately state the Python reference lib passes the full current suite (CI-verified) and a second implementation (TypeScript) is in progress.agent-action-capsule/tree/main/test-vectors(AAC's own vectors, unrelated to CPB) andagent-action-capsule/.../cpb-provisional-registry.md(a different, still-provisional candidate list — not where AAC/MachineMandate are registered). Repointed to the realscitt-payload-binding/REGISTRY.mdandvectors/. Updated language: AAC is the first registered payload profile; MachineMandate is registering as the second (PR open, pending owner confirmation) — dropped "provisional" framing./cpb.htmlpage covering both companion drafts side by side: the Composition draft (draft-mih-sato-agent-accountability-composition-00, the CAN/WHO/WHAT/AUDIT framework + shared action-digest join key + assurance tiers) and CPB (draft-mih-sokolov-scitt-payload-binding-01, the binding mechanism — jcs-n, derived identifier, typed reference). Also covers the open registry (three-rung owner-authored / third-party-documented / provisional onboarding ladder) and the conformance rigor (mutation-probe self-test: condition-removed mutants, assertion-free checks fail CI — sourced fromscitt-payload-binding/.github/check_vectors.py). Links both drafts, the registry, the vectors, and the reference implementation.index.html#cpb, ~L459–489): swapped the overclaiming third card for an honest "open registry" card, added a CTA linking to the new page, fixed the footer link line.nav-links) and to the docs sidebar where present.draft-mih-*citations — found and fixed one stale citation:docs/bilateral.htmlwas still citingdraft-mih-agent-bilateral-attestation-00, bumped to-01. All other citations (AAC-02, CPB-01) were already current.cpb.htmlto theDockerfileCOPY list (the exact class of trap that bit[site-deploy-push]earlier today) and tositemap.xml.Boundary
Mechanism + open registry + vectors + composition only. No KYB, no Authority-operated framing, no reputation/pricing, no two-sided-market/worked-examples language. Self-scanned the diff against the known reserved-vocabulary categories; the automated
neutralityCI gate (secret-backed) is the authoritative check — see PR checks.Test plan
npx vitest runincapsule-emit-js(publish-fixes branch): 60/60 pass, confirming the TS 21-vector claim before softening itpython3 -m pytest -qinscitt-payload-binding(cpb-vectors-and-ref-impl branch): 30/30 pass, confirming the Python full-suite claimdocker build+docker runlocally:/,/cpb.html,/cpb(clean URL),/docs/how-it-composes.html,/docs/bilateral.html,/ip.html,/playground.html,/docs/all 200Composition (CPB)nav content served correctly from the built containerneutrality/dco/ other CI checks green on this PR (verify before merge)🤖 Generated with Claude Code