Agent-maintained current checkpoint, not a chronological log. Replace guidance with concise facts and links during project setup and as work proceeds. Read PROJECT.md for human intent; use records/RECORDS.md for evidence and decisions. Link relevant H records for human steering and authority.
NOT_STARTED — project objective has not yet been initialized.
Last applied human input: none.
Reconcile this section before dependent work; see Persistent loop robustness.
- Session owner / last checkpoint: none. Record an identifier and a timestamp with timezone while working; release it when finishing. Advisory, not a lock: a successor may reclaim a stale entry and record the takeover.
- In-flight action: none. Before an irreversible or long action, record the exact operation, its expected observable effect, how to tell whether it completed, and the verification or rollback step. A non-empty entry means the outcome is UNKNOWN: verify actual state before repeating it.
- Attempts on current gap: none. Reset when the gap changes; change approach or escalate when consecutive attempts produce no new evidence.
- Effort limit: none stated. Record any budget or stopping limit and what to do when it is reached.
No approaches ruled out yet. Consult this list before choosing an action and add to it when an approach fails for an understood reason. Never delete an entry; mark it superseded when evidence changes.
| Approach / hypothesis | Why ruled out (evidence) | Revisit if |
|---|
Not initialized. Source: PROJECT.md.
No requirements registered yet. Assign IDs from PROJECT.md at initialization.
| ID / source | Short criterion | Validation method / test ID | Status | Current evidence |
|---|
Not inspected. Add architecture, important interfaces, and artifact entry points.
No engineering results validated yet.
- Objective, available system, and acceptance criteria need initial inspection.
- No observed engineering failures recorded yet; this does not imply tests pass.
Not inspected. Capture only reproducibility-critical configuration, versions, hardware/connection details, calibration validity, and authorized operating scope with its source and conditions. For hardware integration, record explicit candidate approval, reviewed revision, scope and limits; recheck actual device state only after the gate. Keep secrets outside this file.
Read PROJECT.md, inspect the available system, register requirements and validation methods, then choose the most consequential gap. If the objective is still blank, request it. For hardware projects, exhaust useful hardware-independent work first. Keep only the current phase, milestone and next few useful actions here.
None assessed yet. Record dependency, affected requirements, independent work remaining, and the exact condition that clears each blocker. A pending candidate review belongs below, not here.
Incomplete: initialization and engineering validation have not begun. Completion requires current evidence for all required acceptance criteria plus final system validation and reproducible operating instructions in the report. Hardware-ready is a candidate milestone; VALIDATED also requires the applicable physical acceptance tests to pass.