Routing & prompts — built, with a dormant half

Every piece gets its analysis prompt from a router. This page is how that actually works today, what is switched off, and what the standing rulings will change. Verified against the running code and live tables on 17 August 2026.

The two layers

Layer one — by source — is live. Sixteen active routes pick a prompt by where the piece came from: each social platform, each ad library, landing pages, the newsroom, and so on. This is the router the pipeline actually uses.

Layer two — by what the piece is about — exists but is switched off. Twelve rows, every one inactive, keyed on the old mixed content-category carve. The family reconciliation is what re-keys or retires this layer: the recommendation keeps routing on facts knowable at ingest and keeps the family out of prompts entirely.

The prompts

Forty-three prompt versions exist; nineteen are marked production. The system half of each prompt is hand-written per route; the user half is shared template text. Two honest gaps, found by probing:

• Version stamps are mostly missing — eleven of the nineteen production prompts carry no schema-version key, so "which vocabulary was this classified under" is often unanswerable. The ruled future — every classification stamped with its taxonomy version — needs this fixed.
• Prompts are not yet generated from the registry. The standing ruling says every choice list an analyzer sees is generated from the governed registry; today the lists are written by hand and kept in sync by discipline. This is the single highest-leverage build in the routing area.

Live drift, found by probing

• Two content categories in live use — research and model documentation, about 290 pieces — have no route at all, active or dormant.
• Three source types in live use — vendor portfolios among them — have no routing row, so they ride default handling.
• A dead twin of the routing table sits in the database, structurally identical, queried by nothing — leftover from an earlier design, worth retiring.

What the family ruling changes here

Under the taken-provisionally mechanism, nothing about routing stores a family: the router keys on source and format at ingest and on type after classification. The dormant second layer either re-keys to facts that exist at ingest or retires. Prompt generation from the registry is what makes the ratified vocabulary actually reach the analyzers.

Where to look next

• The content pipeline — where the routed prompt runs.
• The schema view — the full pipeline walk with the reconciliation options compared.