What the public sees
A narrative surface. The root page explains the pattern: traces, reinforcement, evaporation, and re-routing. It should feel like a specimen from Machine.inc, not an exposed admin console.
This public view is not a dashboard. It is a publishable specimen of how repeated choices become navigational residue: one route strengthens, another decays, and a better path emerges when reality changes.
PAR treats retrieval strategy like organizational memory. Every answer leaves a trace. Good traces thicken. Stale traces evaporate. Exploration creates the next candidate route before old habits harden into blind spots.
A narrative surface. The root page explains the pattern: traces, reinforcement, evaporation, and re-routing. It should feel like a specimen from Machine.inc, not an exposed admin console.
Replay runs, raw summaries, telemetry-derived detail, and route-by-route evidence stay in the admin evidence room under /admin/.
Consulting and leadership audiences do not need raw traces first. They need to see how organizational memory forms, why drift happens, and how a system can adapt before habit becomes dogma.
The current preview can pull a small set of public metrics from replay runs without exposing the raw run artifacts. These route families become the public proof that the colony is learning in shape, not only in slogans.
"A good path is not chosen once. It is re-earned until the colony can trust it, then surrendered when the terrain changes."
Machine.inc framing: routing as living organizational memory, not a frozen rules engine.