focus-flow/Codex Documentation/Archived plans
2026-06-26 19:38:39 -07:00
..
V1_BLOCKS_07_10_UPDATED docs(plan): archive completed v1 block 10 2026-06-24 15:16:24 -07:00
PLAN_REVIEW_SUMMARY.md docs: reset plan around sqlite workflow 2026-06-26 19:38:39 -07:00
README.md docs: reset plan around sqlite workflow 2026-06-26 19:38:39 -07:00
V1_BACKEND_COMPLETION_GAP_MATRIX.md docs: reset plan around sqlite workflow 2026-06-26 19:38:39 -07:00
V1_BLOCK_01_Project_Foundation.md feat(scheduling): add starter domain and placement engine 2026-06-19 15:45:11 -07:00
V1_BLOCK_02_Domain_Model.md feat(scheduling): add starter domain and placement engine 2026-06-19 15:45:11 -07:00
V1_BLOCK_03_Scheduling_Engine.md feat(scheduling): roll over unfinished flexible tasks 2026-06-19 16:05:24 -07:00
V1_BLOCK_04_Backlog_Quick_Capture.md feat(backlog): add staleness markers 2026-06-19 16:13:04 -07:00
V1_BLOCK_05_Recurring_Locked_Blocks.md feat(locked-time): track completed locked-hour work 2026-06-19 16:30:21 -07:00
V1_BLOCK_06_Task_Actions_State_Transitions_SUPERSEDED.md feat(tasks): implement surprise task logging 2026-06-24 11:47:40 -07:00
V1_BLOCK_06_Task_Actions_State_Transitions_UPDATED.md feat(tasks): implement surprise task logging 2026-06-24 11:47:40 -07:00
V1_BLOCK_07_Child_Tasks.md feat(tasks): support parent-owned child tasks 2026-06-24 12:14:32 -07:00
V1_BLOCK_07_Child_Tasks_UPDATED.md feat(tasks): support parent-owned child tasks 2026-06-24 12:14:32 -07:00
V1_BLOCK_08_Today_Timeline_State.md test(timeline): add timeline state regression suite 2026-06-24 13:59:26 -07:00
V1_BLOCK_08_Today_Timeline_State_UPDATED.md test(timeline): add timeline state regression suite 2026-06-24 13:59:26 -07:00
V1_BLOCK_09_Persistence_Preparation.md docs(data): document MongoDB non-sync boundary 2026-06-24 14:23:46 -07:00
V1_BLOCK_09_Persistence_Preparation_UPDATED.md docs(data): document MongoDB non-sync boundary 2026-06-24 14:23:46 -07:00
V1_BLOCK_10_Testing_Documentation_Handoff.md docs(plan): archive completed v1 block 10 2026-06-24 15:16:24 -07:00
V1_BLOCK_11_Backend_Baseline_Domain_Contracts.md feat(domain): harden v1 time semantics 2026-06-24 17:14:45 -07:00
V1_BLOCK_12_Occupancy_Scheduling_Correctness.md feat(scheduling): add structured outcomes and invariants 2026-06-25 09:19:16 -07:00
V1_BLOCK_13_Lifecycle_Statistics_Project_Reminders.md feat(reminders): add protected rest reminder policy 2026-06-25 10:08:48 -07:00
V1_BLOCK_14_Application_Use_Cases_Read_Models.md feat(app): add app-open rollover recovery 2026-06-25 11:00:22 -07:00
V1_BLOCK_15_Persistence_Schema_Codecs_Repositories.md docs(plan): archive completed persistence block 2026-06-25 12:20:09 -07:00
V1_BLOCK_16_MongoDB_Runtime_Adapter.md docs: reset plan around sqlite workflow 2026-06-26 19:38:39 -07:00
V1_BLOCK_16_REPOSITORY_ADAPTER_CHECKLIST.md docs: reset plan around sqlite workflow 2026-06-26 19:38:39 -07:00
V1_BLOCK_17_Backend_Acceptance_Handoff.md docs: reset plan around sqlite workflow 2026-06-26 19:38:39 -07:00
V1_BLOCK_18_UI_Foundation_Design_Spike.md docs: reset plan around sqlite workflow 2026-06-26 19:38:39 -07:00
V1_TEST_COVERAGE_MATRIX.md docs(plan): capture v1 backend baseline 2026-06-24 16:25:19 -07:00

Current Software Plan

Blocks 0112 are complete and remain historical records in Codex Documentation/Archived plans/. The active path resumes at Block 13.

The backend sequence is Blocks 1117. Block 18 is a deliberately limited UI foundation block and is blocked until the backend completion gate in Chunk 17.4 passes.

Execution rules

  1. Read AGENTS.md first.
  2. Read V1_BACKEND_COMPLETION_GAP_MATRIX.md before starting Block 11.
  3. Execute active block documents in numeric order.
  4. Execute only the next chunk or stage requested by the user.
  5. Respect every BREAKPOINT as a hard stop.
  6. When the next chunk changes recommended Codex level, stop and ask the user to confirm the mode switch before continuing.
  7. Run the relevant formatter, analyzer, unit tests, contract tests, and integration tests before claiming a chunk is complete.
  8. Commit completed bounded work with a descriptive conventional commit.
  9. Mark a completed plan Complete, move it to Codex Documentation/Archived plans/, and commit the archive move.
  10. Do not rewrite archived Blocks 0110 to make new work appear previously complete. Add errata or new active work instead.

Scope guardrails

Backend V1 includes the application-facing use cases, persistence schema, MongoDB adapter boundary, deterministic scheduling behavior, internal statistics, and UI-independent read models required by Today, Backlog, quick capture, locked time, rollover, surprise logging, child tasks, free slots, project defaults, and reminder policy decisions.

Backend V1 does not include week/month views, reports, overwhelm shield, burnout catch-up, drag-and-drop, a visible task-history panel, task dependencies, context tags, advanced sync, user accounts, production authentication, or flexible-task overrun behavior.

The UI must never receive a MongoDB connection string or database credentials. Block 16 must choose and document a trusted runtime boundary before adding a runtime database dependency.

Active plan index

Order Plan Status Backend/UI
11 ../Archived plans/V1_BLOCK_11_Backend_Baseline_Domain_Contracts.md Complete, archived Backend
12 ../Archived plans/V1_BLOCK_12_Occupancy_Scheduling_Correctness.md Complete, archived Backend
13 V1_BLOCK_13_Lifecycle_Statistics_Project_Reminders.md Planned Backend
14 V1_BLOCK_14_Application_Use_Cases_Read_Models.md Planned Backend
15 ../Archived plans/V1_BLOCK_15_Persistence_Schema_Codecs_Repositories.md Complete, archived Backend
16 V1_BLOCK_16_MongoDB_Runtime_Adapter.md In progress Backend
17 V1_BLOCK_17_Backend_Acceptance_Handoff.md Planned Backend gate
18 V1_BLOCK_18_UI_Foundation_Design_Spike.md Planned, blocked UI foundation

Chunks and stages use only:

  • low
  • medium
  • high
  • extra high

Blocks do not receive a Codex thinking-level classification.