# Current Software Plan

Blocks 01–10 are complete and remain historical records in
`Codex Documentation/Archived plans/`. The active path resumes at Block 11.

The backend sequence is Blocks 11–17. 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 01–10 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 | `V1_BLOCK_12_Occupancy_Scheduling_Correctness.md` | Planned | 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 | `V1_BLOCK_15_Persistence_Schema_Codecs_Repositories.md` | Planned | Backend |
| 16 | `V1_BLOCK_16_MongoDB_Runtime_Adapter.md` | Planned | 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 |

## Recommended mode labels

Chunks and stages use only:

- `low`
- `medium`
- `high`
- `extra high`

Blocks do not receive a Codex thinking-level classification.