Solutions checklists

What it does

For every solution slug, a per-step checklist captures owner, planned/actual timestamps, evidence, sign-off, and reviewer approval. The database enforces no-self-review and requires the step to be signed off before it can be reviewed.

Required inputs

• Step ref — stable identifier from the solution definition.
• Owner — initials or name of the engineer responsible.
• Planned at and actual at — timestamps.
• Evidence — link or freeform note.
• Sign-off — initials of the executor.
• Reviewer — initials of a different engineer (no self-review).
• Review notes — optional commentary.

Example output

`` Step PRE-001 — "Cable spine ports" Owner: AB Planned: 2026-05-02 09:00 Actual: 2026-05-02 09:14 Sign-off: AB @ 09:15 Reviewer: CD @ 09:22 — "verified labels match diagram" ``