focus-flow/Codex Documentation/Current Software Plan
2026-06-24 14:16:30 -07:00
..
V1_BLOCKS_07_10_UPDATED feat(data): add MongoDB document mapping helpers 2026-06-24 14:16:30 -07:00
README.md test(timeline): add timeline state regression suite 2026-06-24 13:59:26 -07:00
V1_BLOCK_09_Persistence_Preparation.md feat(data): add MongoDB document mapping helpers 2026-06-24 14:16:30 -07:00
V1_BLOCK_10_Testing_Documentation_Handoff.md docs(project): commit current repository state 2026-06-24 11:11:15 -07:00

Current Software Plan

Execute active V1 block documents in numeric order. Blocks 01-08 are completed and archived; the next active block is Block 09.

Execution rules

  1. Read AGENTS.md first.
  2. Read the relevant block document.
  3. Execute only the next chunk/stage requested by the user.
  4. Respect all BREAKPOINT markers.
  5. If the next chunk/stage changes recommended Codex level, stop and ask the user to confirm they switched mode.
  6. Commit completed work blocks/chunks with conventional commits.
  7. Move completed plan files to Codex Documentation/Archived plans/ when the plan is complete.

Chunks and stages use:

  • low
  • medium
  • high
  • extra high

Do not infer a new level name.

V1 plan index

  1. V1_BLOCK_01_Project_Foundation.md
  2. V1_BLOCK_02_Domain_Model.md
  3. V1_BLOCK_03_Scheduling_Engine.md
  4. V1_BLOCK_04_Backlog_Quick_Capture.md
  5. V1_BLOCK_05_Recurring_Locked_Blocks.md
  6. V1_BLOCK_06_Task_Actions_State_Transitions_UPDATED.md — archived
  7. V1_BLOCK_07_Child_Tasks.md — archived
  8. V1_BLOCK_08_Today_Timeline_State.md — archived
  9. V1_BLOCK_09_Persistence_Preparation.md
  10. V1_BLOCK_10_Testing_Documentation_Handoff.md