SESSION REGISTRYOne row per session · S[DDMMYY]-[N]
|8 sessions
| SESSION | DATE | PROJECT | ACTOR | STATUS | OPENED | CLOSED | NOTES | ACTIONS |
|---|---|---|---|---|---|---|---|---|
| S210726-4 | 2026-07-24 | RS//RS//RSC#1 | Session Agent | OPEN | 11:30 | — | ||
| S200726-1 | 2026-07-23 | RS//DF//TFC#1 | $B-RES-01 | CLOSED | 09:15 | 17:40 | ||
| S190726-1 | 2026-07-22 | RS//RS//RSC#1 | Session Agent | CLOSED | 14:00 | 18:20 | ||
| S180726-1 | 2026-07-21 | RS//RS//RSC#1 | Session Agent | CLOSED | 10:30 | 16:45 | ||
| S170726-3 | 2026-07-20 | RS//RS//RSC#1 | Session Agent | CLOSED | 09:00 | 13:10 |
1 / 2
SESSION INDEXTypes of sessions in RS — the taxonomy
OPSOPERATIONAL
Working session tied to a live project operation. Most sessions are this type. Produces tasks, runs, and outputs.
METAMETA
Designing the OS itself — editing the Playbook, building templates, creating skills. Exempt from the Request chain.
REVREVIEW
Reviewing output, sign-off sessions, harvest sessions. No new runs opened, just assessment.
PLANPLANNING
Project or operation planning — scoping runs, building task registries, setting milestones.
ONBONBOARDING
Bringing a new client, project, or agent into the system. Load operations, register entities.
MAINTMAINTENANCE
Tech, infra, or workflow fixes. TEC operations live here.
Session type is declared at /open · default is OPERATIONAL
HOW SESSIONS WORK
STEP 1
/open
Binds to a project. Generates Session Code (S[DDMMYY]-[N]). Reads registries. Registers Session Actor. Writes to Session Registry.
STEP 2
Work the cards
Invoke wrap skills. Every task card worked is stamped with the Session Code. Requests → Tasks → Runs chain.
STEP 3
/close
Summary surfaced. Task Log written. Session Registry row updated with CLOSED status. last-session.md written for next session bridge.
Registry: 1xjJg9RHZcn820Oh80LrS1Aslew0uRciWJnaB-DhRzRk · Session Card = front cover + blurb · Session Log = everything in between