State-of-play app health

Current value · last verified 2 days ago

Context

The app monitors itself. If it's not being used regularly (no logins for 14 days), this surfaces and the digest agent escalates: 'is this the right tool, should we retire it?' Prevents the app becoming exactly what it's trying to fix.

Related files

• docs/ARCHITECTURE.md
• docs/SEED_ITEMS.md

History · 4 entries

1. updated11 Sept 58251, 07:49

   via audit pass — reflect Phases 5 and 6a completion

   show diff

   - before:

   MVP under construction as of 12 April 2026. Phase 1 in progress: schema, seed, dashboard, review flow, item detail, browse, manual signal posting, magic link auth. Architecture document at docs/ARCHITECTURE.md. Next phases: Claude conversation, journal mode, background agents, snapshot generator.

   + after:

   Phases 1-5 + 6a complete as of 13 April 2026. Phase 1: schema, seed, dashboard, review, items, signals, magic link auth. Phase 2: Talk to Claude with pre-briefing + propose_update tool. Phase 3: journal mode multi-item parser. Phase 4: background agents (drift, filesystem, update proposer, daily digest). Phase 5: snapshot generator writes STATE_OF_PLAY.md weekly. Phase 6a: git silence detector on the tick cron. Remaining Phase 6: 6b calendar (needs OAuth), 6c bank (needs open-banking OAuth), 6d telegram (needs bot token). Also pending: Vercel deploy, no tests exist, cron not installed on this machine.

2. affirmed13 Apr 2026, 22:28
3. snoozed13 Apr 2026, 22:28

   Snoozed 1 days

4. created12 Apr 2026, 15:53

   Seeded from docs/SEED_ITEMS.md on 2026-04-12