# Session: 2026-06-17 — Reverse-engineer, plan, kick off Phase 0 ## Goal Take an inherited Create/Anything export of an insole-production time tracker, understand it, decide a direction, and start building toward a self-owned version. ## Work done 1. **Git repo created.** Initialised, baseline commit of the code "as received". 2. **Reverse-engineering.** Established it is a two-app monorepo: `apps/mobile` (Expo) + `apps/web` (Next.js backend on Neon Postgres) + `publisher/`. Found it heavily coupled to the Create platform; the live data/accounts are held in the platform's DB (owned by the friend's Create account), not by us. 3. **Fixes committed.** Corrected `CLAUDE.md`; found & repaired `/api/logs` (git-ignored by an over-broad `logs` rule **and** missing its `import sql`); added a reverse-engineered `apps/web/db/schema.sql`; reconciled `yarn.lock` with `package.json`; installed deps. 4. **Brainstormed the target** (superpowers:brainstorming) and wrote **`docs/roadmap.md`** — vision + 8 decisions + architecture + 6-phase roadmap. 5. **Wrote `docs/plans/phase-0-foundation.md`** (superpowers:writing-plans) — a TDD plan for the dockerized backend. 6. **Repo hygiene:** `.gitattributes` (LF normalization); gitignored `.mcp.json` and `CLAUDE.local.md`. ## Key decisions (full detail in docs/roadmap.md) - Purpose: real workshop tool **and** learning vehicle. - **Clean break** from the Create platform; **greenfield rebuild** porting the good parts. - **Dedicated backend service** (Option A) owns auth + DB; mobile and admin are clients. - Stack: **Hono + better-auth + Drizzle + SQLite (libsql)**, TypeScript everywhere, **dockerized** (local now, any cloud later). Project name: **SoleLog** (`@solelog/*`). ## Current state - Working tree clean; planning docs tracked under `docs/`. - Phase 0 plan ready; implementation kicked off via a multi-agent **workflow** (per-task implement + adversarial verify). - Inherited `apps/mobile` / `apps/web` remain untouched as reference. ## Next steps - Complete Phase 0 (tasks 1–6): dockerized backend + auth round-trip. - Then Phase 1 (worker timing flow with server-authoritative sessions). ## Open items to confirm with the friend - Whether any **live data / worker accounts** exist in his Create instance that must be exported before going live on a fresh DB (a greenfield can't recreate it). - Real **workbench ↔ activity** mapping (hardcoded/seeded for now).