📖What it means
The route a conversation turn takes through the ONE shared chat machinery — the composer that assembles the agent's persona, its brief, its live grounding over the records it owns, the turn's recorded stages and its receipt. Every agent's web and channel conversations are meant to run here, so that a turn behaves the same whichever door it arrived through. It is the default route, not the special one.
📖Easily confused with
[{"term": "lane", "distinction": "NOT A LANE. 'Lane' is about BUILD work \u2014 the route an initiative travels to be executed (planner, Orion bypass, Albus bypass) and therefore the route accountability travels. A path is about a single CONVERSATION TURN and carries no initiative, no mode and no escalation ladder. The two were confused for months because the code calls this 'Carol's lane', and the confusion is why the estate had four informal names for one thing. Not a SUBSCRIPTION or a MODEL: the path is which machinery composes the turn, not which vendor answers it."}]
📖Nuance
Carol is the case that proved the distinction matters. Her WhatsApp turns are supposed to run here; through 2026-09-04 every one of them failed over to the direct path instead, logged each time. Two capabilities live only here — the elapsed-time gaps that let an agent tell an old message from a new one, and the turn's stage record — so a turn that leaves this path silently loses them.
📖Also called
- the one engine
- shared chat machinery
- engine path
📖Filed under
Category: work.
Source: Data Dictionary · Public information reflected here.