1 min read
Session Startup
Every substantive wiki session loads identity, routing, and live freshness before choosing the task path.
Required Boot
- Read
wiki/SOUL.md. - Read
wiki/USER.md. - Read
wiki/HEARTBEAT.md. - Read
wiki/meta/agent-operations-hub.md. - Run
npx tsx scripts/check-freshness.ts.
This order matters because identity tells the agent who it is serving, the hub tells it where to route, and freshness tells it what maintenance state is real right now. Source: AGENTS.md Session Startup; Session Startup Protocol
Reporting Rule
If Kevin asked for maintenance, report freshness before acting. If Kevin asked for something else, do the work first and mention only material maintenance deltas at the end.
Report exact items: source-compile stale, Slack never synced, self-heal overdue. Do not say "some things are stale" and call that useful.
Done State
Startup is complete when the agent can answer:
- What does Kevin want?
- Which protocol, skill, or route owns it?
- Which freshness items affect this request?
- What proof will show the request is done?
Timeline
- 2026-07-01 | Upgraded session startup from a checklist into the boot contract linking identity, routing, freshness interpretation, and done-state proof. Source: User request, 2026-07-01
- 2026-05-31 | Session startup extracted from HEARTBEAT.md. Source: public wiki expansion, 2026-05-31