WorkHub gives users one persistent conversational place to ask, clarify, continue, create, and inspect work. It is backed by one stable Coordination Session per Runtime Host while concrete execution remains authoritative in ordinary Sessions.
This document names the approved target architecture. Each Runtime Host now provisions and reuses the stable Coordination Session role described below. The current R2.4 routing behavior remains a transitional deterministic baseline or target resolver; it does not define the final WorkHub coordination semantics. The decision and authority boundaries are recorded in the WorkHub Coordination Session ADR.
Session: The existing transcript, execution-boundary, permission, interaction, and recovery substrate. A Session owns only the conversation or execution admitted to that Session.
Coordination Session: The stable special Session role owned independently by each Runtime Host for its WorkHub conversation. It owns WorkHub user messages, ordinary Q&A, clarification, coordination decisions, bounded delegation references, and coordination summaries, but no ordinary Session execution or lifecycle facts. It is not a separate database, event store, transcript substrate, or lifecycle authority. It is hidden from the ordinary Session list and excluded from every routing-candidate set, so it never routes to itself. Cross-Host coordination is not supported in the first milestone.
ordinary Session: A Session that owns concrete work execution, including its project/filesystem scope, model and permissions, root-Turn admission, tools, artifacts, recovery, lifecycle, and authoritative execution transcript.
Work: User-facing continuity around a goal. Whether Work is 1:1 with Session, 1:N over Sessions, or an independent durable entity is deliberately unresolved.
WorkHub: The unified conversational entry and coordination surface backed by the active Runtime Host's Coordination Session. It may answer locally, clarify, delegate to an existing ordinary Session, or create a new ordinary Session.
projection: A rebuildable, read-only view derived from Coordination Session and ordinary Session facts. WorkHub cards, filters, status summaries, and navigation aids are projections; they own no durable facts and can be discarded without losing work.
disposition: The single proposed coordination outcome for one WorkHub input:
answer_here answers in the Coordination Session; delegate_existing targets one
bounded, valid ordinary Session; create_new creates an ordinary Session before
delegating and is visibly announced as new work; and clarify continues in the
Coordination Session without guessing or creating.
delegation: A bounded reference from a Coordination Turn to one target ordinary
Session and Turn, including only its identity, disposition, and coordination-owned
link status (active, superseded, or aborted). A link is aborted only when a
correction retired its source but the replacement target became unavailable or
started waiting before admission; it is not the target Turn's execution status.
Delegation links the separately authoritative transcripts; it does not copy the
target's complete execution transcript into WorkHub. Target acceptance, running,
waiting, completion, failure, abort, and recovery state remain ordinary Session
facts and appear in WorkHub only as read-only projections.
Action Gate: The deterministic Runtime boundary that validates a proposed
disposition and operation before any write, including target/Host validity,
archive and waiting state, self-routing, explicit creation, expected-Turn Stop
ownership, confirmation, tools, and permissions. All model and routing output is
advisory and cannot authorize a write. An initial create_new requires affirmative,
executable trusted user text; a corrective create_new additionally requires an
explicit new-Session clause. Negated or withdrawn creation intent is rejected in
both cases.
Route correction: A user's explicit decision that an input belongs to a different existing or newly created Session. R2.4 retains only bounded inference memory for target resolution; destructive confirmation must also be evidenced by an affirmative target action in the trusted user text; negated or withdrawn target actions fail closed and cannot come from routing output alone. The Coordination Session durably claims one replacement intent per source delegation in transcript order. It delegates exact pending-Message cancellation or owning-Turn Stop to the target Session, then atomically records the replacement link and supersession. Only a root Turn created by the delegated Message may be stopped; consuming the Message as steering does not give WorkHub ownership of the surrounding user Turn. When recovery folds multiple source Messages into one successor Turn, every source shares that Turn and no individual delegation owns Stop authority over it. Replacement replay is bound to the resolved stable target Session identity. If that target becomes unavailable, waits for user input, or corrective creation cannot be admitted after source retirement, the Coordination transcript records an auditable replacement-aborted terminal fact and removes the retired source from active linkage. Correction never replaces either Session's transcript authority.
R2.4: The deterministic context-continuity routing baseline. It remains useful as an experiment baseline or target resolver behind WorkHub's coordination layer; it is not the final architecture or authority boundary of WorkHub.
Avoid: copied execution transcripts, self-routing, a second Session/WorkHub storage substrate, or treating model/routing output as execution authority.