Skip to content

feat(detector): surface the coordination catalog at /coordination with binding→signal links - #263

Merged
datascry merged 1 commit into
mainfrom
feat/coordination-catalog-site
Jul 14, 2026
Merged

feat(detector): surface the coordination catalog at /coordination with binding→signal links#263
datascry merged 1 commit into
mainfrom
feat/coordination-catalog-site

Conversation

@datascry

Copy link
Copy Markdown
Owner

Follow-up to #261 (the coordination catalog) — put it on the site and complete the matched red/blue pair.

What

  • Blue-signal glossary. The generator now also emits a glossary of the coordination signals — what each binding catches (fp_collision, trace_collision, template_similarity, shared_ticket, shared_real_ip, flood_shape, arrival_regularity, proxy_egress) and whether it's unambiguous, corroboration-gated, or an Axis-A dimension — and each strategy's binding links to its signal there.
  • On the site at /coordination. The same generated block is now spliced into two files — fleet/README.md and a new docs/coordination-catalog.md — served by the detector via the existing DOC_PAGES machinery (route + sitemap + docs hub + llms.txt all wired). The --check drift gate now covers both files.
  • Working in-page anchors. render_markdown_doc gains the toc extension so headings get ids and the binding→glossary #anchor links resolve — matching GitHub's slug scheme, so the same links also work in the README. (The link rewriter already leaves #-anchors alone.)

Grounded live

/coordination serves 200; the ladder + glossary render; the anchor round-trips end-to-end — a binding's href="#fp_collision" resolves to the glossary heading id="fp_collision"; and it's discoverable in the docs hub, sitemap, and llms.txt.

Verification

  • fleet 37 passed @ 97.95% (glossary + link + unknown-signal-guard covered)
  • detector 533 passed @ 95.20% (new /coordination test asserts the anchor round-trip + hub/sitemap presence)
  • ruff / mypy / headers clean; python -m skulk.catalog --check green on both files

This closes the follow-up flagged in #261 — the coordination catalog is now the matched red/blue pair, live on the site.

…h binding→signal links

Follow-up to the coordination catalog: put it on the site and complete the
matched red/blue pair. The generator now also emits a blue-signal GLOSSARY (what
each binding catches — fp_collision, trace_collision, template_similarity,
shared_ticket, shared_real_ip, flood_shape, arrival_regularity, proxy_egress —
and whether it's unambiguous, corroboration-gated, or an Axis-A dimension), and
each strategy's binding links to its signal there.

The same generated block is now spliced into TWO files — fleet/README.md and a new
docs/coordination-catalog.md — served by the detector at /coordination via the
existing DOC_PAGES machinery (route + sitemap + docs hub + llms.txt all wired). The
render_markdown_doc pipeline gains the `toc` extension so heading ids exist and the
in-page binding→glossary anchors resolve (matching GitHub's slug scheme, so the
same links work in the README too); the link rewriter already leaves #anchors alone.

Grounded live: /coordination serves 200, the ladder + glossary render, and the
anchor round-trips (a binding's href="#fp_collision" resolves to the glossary
id="fp_collision"); listed in the docs hub, sitemap and llms.txt.

fleet 37 passed 97.95%; detector 533 passed 95.20%; the coordination --check gate
now covers both generated files.
@datascry
datascry merged commit 6316999 into main Jul 14, 2026
23 checks passed
@datascry
datascry deleted the feat/coordination-catalog-site branch July 14, 2026 04:00
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