Identity, Session, and Routing
Agent work starts from identity, session state, and routing: who is acting, what context is live, and which skill/tool/page owns the next move. Source: User request, 2026-06-27; Agent Operations Hub
When To Use This
Use this page when an agent session is ambiguous: new repo, stale context, unclear tool choice, cross-agent handoff, or a task that touches wiki, skills, packs, and runtime behavior at once. Source: Agent Operations Hub, 2026-06-27
Decision Matrix
| Question | First route | Proof |
|---|---|---|
| Who is the agent serving? | Session Identity Contract and user/wiki spine | Loaded SOUL/USER/HEARTBEAT or active repo instructions |
| What context is authoritative? | Current worktree, then qmd/wiki, then external sources | File reads and command output |
| Which capability owns the task? | Skill Resolver then Capability Routing Map | Skill/tool/page selected with reason |
| Is this repeatable? | No-one-off rule, then skill/automation update | New or updated durable artifact |
Core Model
Identity is the operating contract. Session state is the live evidence. Routing is the ownership decision. Mixing these layers creates brittle work: the agent either acts from stale memory, chooses the wrong tool, or updates the wrong page. Source: Session Identity Contract; Capability Routing Map
Tool And Skill Routing
Read the wiki spine for durable context, use rg for exact repo state, use qmd for compiled knowledge, and use Skill Resolver when a repeatable workflow might already have an owner. Generated packs are downstream context, not the authority. Source: Wiki Capsules And Agent Doc Packs, 2026-06-27
Failure Modes
- Treating chat memory as current repo state.
- Loading a broad pack when a specific skill owns the task.
- Updating generated packs instead of the source page or generator.
- Skipping the no-one-off rule when a request will recur.
Evidence And Timeline
This cluster is grounded in the session startup contract, the resolver, the capability routing map, and the generated pack architecture. The operational proof is that agents can route from identity to skill/tool/page without searching random pages. Source: Agent Operations Hub; Skill Resolver
Concept Position
| Field | Value |
|---|---|
| Concept family | Brain, memory, and retrieval |
| Concept owned | Agent work starts from identity, session state, and routing: who is acting, what context is live, and which skill/tool/page owns the next m... |
| Category map | Concept System Map |
Timeline
- 2026-07-01 | Concepts category refresh added this page to the Brain, memory, and retrieval family, linked it to Concept System Map, and kept it standalone because it owns this reusable mental model: Agent work starts from identity, session state, and routing: who is acting, what context is live, and which skill/tool/page owns the next m... Source: User request, 2026-07-01
- 2026-06-27 | Canonical cluster page created so identity, session, and routing are represented as one readable synthesis rather than scattered startup notes. Source: User request, 2026-06-27