Wiki

surface

Shared operating context for Waterbasin

A stronger documentation landing page for the current multi-agent program: live project state, execution rules, durable decisions, and the user context shaping how the team operates.

Browse projects Dashboard handoff

Project state

Active tracks

Source: shared brain

Track

Team infrastructure

Operational

Goal: Maintain the multi-agent operating model on NNW22586.
Current state: Kujo/Hermes is active as the orchestrator, research, and integration lane while Odysseus is being integrated as a coding executor lane and Zephyr remains an additional engineering lane.
Next: Keep host-facing service ownership and deployment conventions documented.

Track

Odysseus integration

In progress

Goal: Use Odysseus as a coding executor that Hermes/Kujo can orchestrate over Tailscale.
Current state: Bearer-authenticated worker routes, real backend wiring, a live smoke test against gemma4:e4b, and workspace-fidelity fixes now support real coding work in a git-backed worker clone.
Next: Continue delegating implementation work through the worker path while keeping the execution split explicit.

Track

Obsidian memory system

Needs upkeep

Goal: Keep /opt/brain useful as durable cross-agent context rather than letting it drift stale.
Current state: Shared notes are intended to stay current as architecture and workflow milestones land.
Next: Update shared state whenever major architecture or workflow changes are proven.

Completed milestones

Proof points

SSH access from Quinn's orchestrator host to NNW22586 is complete.
OpenClaw gateway config and CLI path fixes were applied and confirmed.
Kujo auto_thread is disabled so replies remain visible in-channel.
Odysseus worker API foundation, backend wiring, and workspace fidelity are documented as completed milestones.

Quick routes

Move through the basin

Browse projects Dashboard handoff

Operating model

How the team runs

Execution split

Odysseus handles coding execution and worker runtime, while Hermes remains the orchestration, review, integration, and externally hosted surface.

Canonical hosting

Externally hosted services stay on the Hermes host unless David explicitly directs otherwise.

Shared memory

The canonical vault lives at /opt/brain on NNW22586 so agents can keep durable context on a shared filesystem.

Discord discipline

Agent replies must use raw mention format like <@1493676856388485180>, and auto-threading must remain disabled because threads break Quinn's receive loop.

User and team context

Who this is for

Lead

David (dasani) — project lead and stakeholder.

Communication

Direct, terse replies with no padding; raw mention format for Quinn is expected in all agent responses.

Current team shape

Quinn is the orchestrator, Kujo handles research and integration, Zephyr is an engineering lane, and Odysseus is the coding executor.

Infrastructure context

Agents operate on NNW22586 and coordinate through Discord, with canonical external hosting staying on Hermes by default.

Key decisions

Recent log

These are the durable rules currently shaping delegation, hosting, and shared memory.

2026-06-03

Odysseus execution role

Odysseus is now the coding executor lane, while Kujo/Hermes remains the orchestrator, reviewer, and verifier because the worker API and workspace model are proven enough for delegated implementation work.

2026-06-03

Canonical hosting authority

Public and external services stay centralized on Hermes so coding execution can move faster without fragmenting host-facing integration.

2026-06-03

Worker workspace model

Odysseus uses a dedicated host-visible git-backed clone mounted into the worker runtime so edits preserve real .git visibility, changed_files, and patch output while staying isolated from the main checkout.

2026-04-16

Vault location and reply rules

The shared vault lives at /opt/brain, raw Discord mention format is mandatory, and Hermes auto_thread must remain false so Quinn can reliably see replies.