Session Startup Protocol
Every
kevin-wikisession starts by loading identity, routing, and freshness state before other work.
Startup exists because Kevin should not track system health manually. The agent is responsible for knowing what is stale, what is overdue, which protocols apply, and what should be surfaced without derailing the current request. Source: AGENTS.md Session Startup; Operational Heartbeat
Required Read Order
wiki/SOUL.md- agent identity and operating rules.wiki/USER.md- Kevin's current profile, preferences, work, and philosophy.wiki/HEARTBEAT.md- cadence and done checks.wiki/meta/agent-operations-hub.md- routing map.npx tsx scripts/check-freshness.ts- live maintenance state.
Do not skip the freshness command in this repo. Its output is part of the session context, not a nice-to-have diagnostic.
Freshness Report Interpretation
| Output class | Meaning | Agent action |
|---|---|---|
NEEDS ATTENTION |
Local automation or sync is overdue, never run, or stale | Mention concretely and offer/run the relevant automation if it is in scope |
NOTICES |
Often cloud-run automations or informational gaps | Mention only if relevant or if Kevin asked for maintenance |
UP TO DATE |
No action needed | Do not recite unless useful |
| uncompiled raw sources | Knowledge has been captured but not compiled | Route to source-compile or manual ingest |
| doctor/index/routing drift | Machine facts are stale | Run the relevant doctor or index step after task work |
Reporting Rule
If Kevin's request is maintenance-related, report freshness before acting. If the request is unrelated, do the requested work first and mention the maintenance deltas briefly at the end. The report should name exact automations or syncs, not vague "some things are stale."
After Startup
Route the task through the hub:
- answer from compiled knowledge -> The Brain-Agent Loop
- create/update a page -> Wiki Brain Operating Model, Filing Decision Tree, and Wiki Page Format
- choose a skill/tool -> Skill Resolver
- capture a URL/repo/post -> Capture Ingest Protocol
- set up another repo ->
agent-docsand Required Project Tooling
Then choose the closeout proof before starting work. Wiki edits need index/qmd/log and often Generated Surface Contract plus Generated Surface Refresh. Automation runs need Automation Proof Contract. Agent config edits need the executable surface, wiki reference, routing update, generated packs or skills checks when relevant, and log entry.
Done
Startup is complete when the agent can answer:
- What does Kevin want in this session?
- Which protocol or skill applies?
- What maintenance state should be mentioned?
- What would make this task done and verifiable?
Timeline
- 2026-07-01 | Added generated-surface source/projection routing to startup closeout selection. Source: User request, 2026-07-01
- 2026-07-01 | Aligned startup with the refreshed heartbeat control loop: live freshness state, proof-first closeout selection, automation proof, and generated-surface refresh. Source: User request, 2026-07-01; Operational Heartbeat
- 2026-07-01 | Updated startup routing so wiki page work uses the brain-shape model before the filing resolver, matching the current Agent Soul and Operational Heartbeat. Source: User request, 2026-07-01
- 2026-06-18 | Expanded startup protocol with required read order, freshness interpretation, reporting rules, and done criteria for future agents. Source: User request, 2026-06-18; Operational Heartbeat
- 2026-05-31 | Meta page compiled from AGENTS.md session startup and HEARTBEAT. Source: AGENTS.md