cab3e935d6
Write SPEC.md v0.1 from the owner interview (requirements, data model, stack, API outline, security, business rules, deployment, milestones, UX sprint brief, contracts). Fill the CLAUDE.md blanks, move the Gradle pin files into android/, point the tools at android/ and server/, and record the git bootstrap exception in the handoff. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Handoff: state of the work
Living document, rewritten in place (never a second copy). A new orchestrator session reads CLAUDE.md, then this.
1. Where things stand
mainat8bef22a(root commit "Scaffold: agent starter kit (seeded from Ebb)"). No gate yet: neitherandroid/norserver/has a project.- Branch
agent-spec(on top ofmain, not landed):SPEC.mdv0.1, filledCLAUDE.md, Gradle files moved toandroid/, tool scripts adjusted. - Installed on the owner's phone: nothing.
- Bootstrap exception (2026-10-17): the repository had no commits, so the normal worktree flow could not start. The spec agent created the root commit directly in the main checkout (stray
.DS_Storefiles deleted,.DS_Storeadded to.gitignore), then branchedagent-specthere. From now on the normal flow of CLAUDE.md › Orchestration applies.
2. Open work (one line each, with who owns it: agent or owner)
- Land
agent-spec(orchestrator). - Plans agent: write
PLAN-*.mdand a start prompt per plan inprompts/from SPEC §11 (M1, M2a, M2b, M2c, M3, M4, M5, M6, M7a-M7f, M8, M9, M10, M11, U1, U2). - UX agent: U1 UX directions (SPEC §13), in parallel with M1. Owner reviews the directions before U2 and before any UI work.
- Owner: answer SPEC §12 OQ-1 to OQ-4 (needed by M2c and M9).
3. Owner questions (asked, unanswered)
- OQ-1 Local container registry address, HTTP or HTTPS, credentials (SPEC §12).
- OQ-2 Splitwise CSV format confirmed against a real export, group list and target account names, non-SEK rows (SPEC §12).
- OQ-3 LAN addresses and SSH users of the Kvitt Pi and the Home Assistant Pi; certificate directory on the HA Pi; which SSH add-on (SPEC §12).
- OQ-4 Google Drive folder id for backups (SPEC §12).
4. Paused (waiting on something outside the repo)
5. Numbering
Next free: D-001 (no decisions logged yet; the interview decisions are in SPEC v0.1 itself). SPEC v0.1 is written; the next spec version is v0.2. Schema version 1 is defined in SPEC §14.1 (not yet implemented); the next schema version is 2. Sync protocol 1, push payload 1.
6. How the work is run
See CLAUDE.md › Orchestration. HUMAN steps in reports are relayed in chat by the orchestrator; the owner does not read them in files.