Skip to content

feat(registry): give the TRACE Registry a page on agentrust-io.com - #45

Merged
imran-siddique merged 1 commit into
mainfrom
feat/trace-registry-page
Sep 4, 2026
Merged

feat(registry): give the TRACE Registry a page on agentrust-io.com#45
imran-siddique merged 1 commit into
mainfrom
feat/trace-registry-page

Conversation

@imran-siddique

Copy link
Copy Markdown
Member

The registry has only ever had a raw GitHub URL to hand out. That is a weak answer when the ask is a link an audience can act on, and it is the link currently going into the CSA Sept 9 post-event share list.

Adds /registry/ on the apex site, built on the same pattern as /wcm/.

What is on the page

  • Proof grid, counted on main at 4697f2c: 2 published entries, 1 signed checkpoint, trace-verify 0.3.1 on PyPI, 225 tests passing. Two entries is a small number and the page says so rather than dressing it up.
  • Checkpoint 1 verbatim from registry/2026/09/01.ndjson, not an illustration.
  • How it works: producer signs, only a digest is anchored, append-only MMR, signed checkpoint chains to the previous one.
  • Verify it yourself: pip install trace-verify, clone, run tools/verify_checkpoint_chain.py. No verification endpoint, because an endpoint you have to trust is not verification.
  • Limits, stated on the page rather than in a footnote: consistency of what it covers is not coverage of the registry; the June 2026 entry is deliberately not folded in retroactively; no external witness receipt has come back and verified offline yet; the first anchored record's producer key is single-use by construction.

Also

Registered in sitemap.xml, supernav.js (SITES entry plus apex-path resolution), and llms.txt.

Rendered and checked locally against the real stylesheet.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CJQz3ToBJPj97WUNStAwSQ

The registry has only ever had a raw GitHub URL to hand out, which is a
poor answer when the ask is a link an audience can act on. This adds
/registry/ on the apex site, built on the same pattern as /wcm/.

Every figure on the page is checkable from the public repository and was
counted on main at 4697f2c: two published entries, one signed checkpoint,
trace-verify 0.3.1 on PyPI, 225 tests. The checkpoint block is copied
verbatim from registry/2026/09/01.ndjson rather than illustrated.

The limits section states the four that matter: the chain proves
consistency of what it covers rather than coverage of the registry, the
June 2026 entry is deliberately not folded in retroactively, no external
witness receipt has come back and verified offline yet, and the first
anchored record's producer key is single-use by construction.

Also registers the page in sitemap.xml, supernav.js, and llms.txt.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CJQz3ToBJPj97WUNStAwSQ
@imran-siddique
imran-siddique merged commit 9697f58 into main Sep 4, 2026
2 checks passed
@imran-siddique
imran-siddique deleted the feat/trace-registry-page branch September 4, 2026 19:31
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