NextMyDay/docs/specs
Claus Lohmar 820dc005b3 docs(spec-005): record the TOTP-step render fix
Add §11 (the bug, the write-free IssueTOTP seam, the rendered TOTP page, the
tightened tests) and bump the status revision to 2026-10-15d. Note the two
builder choices: the secret is shown as text rather than a QR image, and
`pendingGUID` now means pending AND in-window (409 on an expired window).
2026-10-15 07:07:33 +00:00
..
README.md docs: add the project plan, M0/M0.1 specs, agent guide and README 2026-10-14 10:53:44 +00:00
spec-001-git-bootstrap.md chore: bootstrap MyDay repository 2026-10-13 11:52:30 +00:00
spec-002-routing-model.md docs: add the project plan, M0/M0.1 specs, agent guide and README 2026-10-14 10:53:44 +00:00
spec-003-core-door.md docs: update the plan, specs and deploy guide for the setup toggle (D-045) 2026-10-15 06:47:36 +00:00
spec-004-identity-sessions.md docs: add the project plan, M0/M0.1 specs, agent guide and README 2026-10-14 10:53:44 +00:00
spec-005-setup-wizard.md docs(spec-005): record the TOTP-step render fix 2026-10-15 07:07:33 +00:00
spec-006-enroll-login.md docs: record the M0 review fixes and correct the README 2026-10-14 11:30:17 +00:00
spec-007-roles-chain-recovery.md docs: record the M0 review fixes and correct the README 2026-10-14 11:30:17 +00:00
spec-008-module-registry.md docs: add the project plan, M0/M0.1 specs, agent guide and README 2026-10-14 10:53:44 +00:00
spec-009-web-pwa.md docs: update the plan, specs and deploy guide for the setup toggle (D-045) 2026-10-15 06:47:36 +00:00

Specs — MyDay

Implementation specs, in build order. A spec precedes its code. The design of record is ../../PROJECT_PLAN.md; decisions are D-nnn.

Convention: spec-NNN-<slug>.md · Status: Draft → Ready for implementation → Implemented · one spec per coherent slice; each ends with acceptance criteria.


Index

# Spec Milestone Status Depends on
001 Git connection bootstrap Prep Implemented —
002 Routing model (internal/core/routing) M0 Implemented —
003 The core door (server + httpx) M0 Implemented 002, 004
004 Identity & sessions (core/auth, core/users) M0 Implemented 002
005 /setup wizard + bootstrap M0 Implemented 003, 004
006 Enroll & login (Passkey + TOTP) M0 Implemented 004
007 Roles, the chain & recovery M0 Implemented 004, 006
008 Module registry & the Modules page M0 Implemented 003
009 Web layer & PWA (screens · WebAuthn JS · service worker) M0.1 Implemented 005, 006, 007

The M0 slice order

002 routing ─► 004 identity/sessions ─► 003 door ─┬─► 005 setup wizard
                                                   ├─► 006 enroll/login
                                                   ├─► 007 roles/chain/recovery
                                                   └─► 008 registry/modules page
                                                                  │
                                                                  └─► 009 web layer & PWA

002 is the Stage-0 gate (ROUTING.md §11): the pure model is approved and unit-tested before any server code. 002 ✅ · 004 ✅ · 003 ✅ · 006 ✅ · 005 ✅ · 007 ✅ · 008 ✅ · 009 ✅ implemented. M0 + M0.1 are complete; next is M1 — org structure.