Machine.inc signal specimen

Pheromonal Signals

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.

Replay Runs
1
Queries Observed
4
Route Families
2
Feedback Events
4
Pheromonal trace animation Reinforcement brightens a lane, decay thins the residue, and exploration opens a new curve that can become the default path.
incoming patterns retrieval routes latest compare ambiguous search hybrid local
Reinforce Repeated success makes a route brighter, faster to spot, and harder to ignore.
Decay Stale confidence loses thickness when the environment changes or evidence stops arriving.
Shift Exploration opens a fresher lane, then the colony can migrate toward it if reality rewards the move.

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.

What stays protected

Replay runs, raw summaries, telemetry-derived detail, and route-by-route evidence stay in the admin evidence room under /admin/.

Why it matters

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.

Observed route repertoire

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.

How to read the trace

"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.