S21 · Personal Time Management

Declared state: built, not well structured.

This is the repository plan and evidence, not a live health reading. A task marked done may still depend on credentials, devices, deployment or a newer acceptance test.

Dependencies

No dependencies are declared in the catalog.

Tasks and gates

21.F1 · **`routines.json` holds the owner's real routines.** It is effectively empty today — the

Tier F · done · Verification: hermetic-test

Gate: `test_day_shape.py` [1]-[4].

  • recorded-note · 2026-09-12 · docs/SYSTEMS-DETAILS.md:2486

21.F2 · Conflict detection: double-booked, no-travel-time, no-breaks are detected and named.

Tier F · done · Verification: hermetic-test

Gate: `test_day_shape.py` [5]-[8].

  • recorded-note · 2026-09-12 · docs/SYSTEMS-DETAILS.md:2504

21.F3 · Date and time handling is robust across timezones and phrasings.

Tier F · done · Verification: hermetic-test

Gate: `check_date_robustness.py` (now in `run_all_tests.py`, 12 tests × 12 clock cases),

  • recorded-note · 2026-09-12 · docs/SYSTEMS-DETAILS.md:2516

21.R1 · Time-blocking proposals for committed work, offered not imposed.

Tier R · open · Verification: planned-test

Gate: new `test_time_blocking.py` - planned gate. new `test_time_blocking.py`

    21.R2 · Actual-vs-planned tracking: where the day really went, from `activity.py`.

    Tier R · open · Verification: planned-test

    Gate: new `test_time_blocking.py` - planned gate. `test_time_blocking.py` [actuals]

      21.R3 · Energy-aware scheduling — hard work into the hours it has historically worked.

      Tier R · open · Verification: planned-test

      Gate: new `test_time_blocking.py` - planned gate. `test_time_blocking.py` [energy]

        21.E1 · A month where every routine commitment either happened or was consciously renegotiated

        Tier E · open · Verification: manual

        Gate: routine adherence log.

          HUD screen contracts

          All subsystems · Source: docs/systems-plan.json.