exec-function-per-track-cadence

ARCHIVED

so did we fall back to only doing one of the available tests per day? Once I finish one all the others are not available. this seems like we're engineering super sparse data collection I don't remember this morning, much less this month. Is it rigorous enough to do it weekly? And yes I agree with flag vs forbid.

STAGES

  1. proposal08-27
  2. requirements08-27
  3. design08-27
  4. tasks08-27
  5. build—
  6. archived08-27

CAPABILITIES — 2 IN ONE CHANGE

  • exec-function-check-in-window2 requirements
  • exec-function-session-cadence3 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1A due track offers its tasknot stated
  • ✓1.2A track that is not due offers nothingnot stated
  • ✓1.3The assigned block keeps its placenot stated
  • ✓1.4Finishing one track leaves the others availablenot stated
  • ✓1.5The same measure cannot be re-run for a better scorenot stated
  • ✓1.6The check-in holds to a weeknot stated
  • ✓1.7A later session is savednot stated
  • ✓1.8A later session is markednot stated
  • ✓1.9The first session of a day is not markednot stated
  • ✓1.10The window is stated with the itemsnot stated
  • ✓1.11Documentation matches the formnot stated
  • ○1.12A new check-in records its windownot stated
  • ✓1.13Earlier check-ins remain identifiablenot stated

WHAT HAPPENED

  1. ARCHIVED

    proposal and specs and design and tasks and archive landed

    2026-08-27 · 1 pull request
    • #408docs(openspec): archive the two exec-function changes

History read from a manifest built at 2026-09-30 (09e7bcc).

1 pull request, found by commits touching the change folder