lsm / neokai / 22375459660
84%

DEFAULT BRANCH: dev
Ran
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
22375459660

push

github

web-flow 
docs: Room Runtime Implementation Plan (#147)

* docs: add room runtime implementation plan

Detailed plan for implementing the Room Runtime v0.21 with the
minimal feature set needed to reach autonomous room operation:

- Phase 0: Database schema (task_pairs, task_messages tables)
- Phase 1: Core infrastructure (repositories, message queue)
- Phase 2: Room runtime core (tick loop, session observer)
- Phase 3: Agent sessions (Room Agent, Craft, Lead)
- Phase 4: Task pair manager
- Phase 5: Message routing
- Phase 6: Recovery

The plan focuses on the minimal path to get the room working
autonomously so it can help build the remaining features.

* docs: clarify this is minimal core for self-bootstrapping, not full spec

* docs: address PR review feedback on impl plan

Fixes from gpt-5-codex and claude-opus-4-6 reviews:

- Schema: Document existing columns (priority, depends_on) to avoid conflicts
- Schema: Add room_audit_log table for debugging
- Schema: Version starts at 1 for optimistic locking
- Lead Agent: Add escalate tool (critical for loop)
- Lead Agent: Add tool contract enforcement section
- Room Agent: Add retry_task tool
- Recovery: Handle session_lost, message queue recovery, active work time reset
- Implementation order: Clarify dependency graph and critical path
- Add unit test plan section
- Specify async-mutex package for Mutex implementation

* docs: address round 2 PR review feedback

Critical fixes from Opus and GPT-5-Codex round 2:

- Pair Creation Flow: Add step 5 - send initial task instruction to Craft
  (this triggers Craft to begin working)
- Add Escalation Return Path section (5.3) - human responds to Lead,
  Runtime transitions pair back to awaiting_lead
- Clarify Lead Tool Routing: MCP callbacks calling Runtime directly,
  not DaemonHub events (with code example)
- Clarify message delivery: Lead→Craft is synchronous (no queue delay),
  task_messages used for recovery only
- Add Task Selection Ordering section (5.4) - priority/... (continued)
Source Files on build 22375459660
Detailed source file information is not available for this build.