Data
Data identity and shape: how messages/jobs/rules/sessions/agents are persisted and named, migration discipline, and identity. Legacy chattr uses JSONL message log + JSON stores; the clean repo decides the durable model per slice.
Data contract
Data identity and shape: how messages/jobs/rules/sessions/agents are persisted and named, migration discipline, and identity. Legacy chattr uses JSONL message log + JSON stores; the clean repo decides the durable model per slice.
The rule
Enforced by
schema lint / contract tests + CI — derived from these rules
- Naming rule (pending) — table/column/file naming conventions.
Open items (confirm to lock)
- Persistence model: keep JSONL/JSON stores vs adopt a DB — decide per slice.
- Migration discipline (if a DB is adopted) — define and lock.
- Naming conventions — define and lock.
Multi-agent coordination
How agents and humans coordinate in a room: behavioral roles, an authoritative ground-truth ledger, a real gate-runner instead of self-reported checks, a shared step-state board, message discipline, and turn-taking. Targets the real friction — duplicated effort and self-reported truth — not output quality.
Design system
The visual language in one place, from the v3 design standard: one token contract for both themes and all layers — surfaces (six-layer ladder), ink (five steps), accent/semantic, typography (IBM Plex Sans/Mono, role-named scale), spacing (4px grid, eight steps), radius, elevation, motion, icons. Components reference semantic roles, never raw hex.