spec-workflow ยท diff
git:20260813.2b6dede to git:20261017.2033867
1 added, 0 removed. Audit A to A.
+ <!-- hyperfide-owned: generated-spec v1 -->
---
description: Ion portable spec workflow (task-driven + cortex)
alwaysApply: true
---
<!-- GENERATED by cg spec render from spec/ kvx โ DO NOT EDIT. -->
# Demo Spec Workflow
The single source of truth for how to work in this repo is **`spec/`** (kvx).
This file is a GENERATED pointer to it. Do not hand-edit it; edit `spec/workflow.kvx` and run `spec/specgen`.
> spec/ (kvx). Generated files are pointers โ regenerate, never hand-edit.
## Principles
- **Task Driven**: Work is driven by the active feature's task list.
- **One In Progress**: At most one task is in_progress at a time.
## The loop (every session)
1. Read the active spec.kvx.
2. Pick the next eligible task by wave.
3. Implement, verify, mark done.
## Persistent project memory (when configured)
- **Recall**: Load relevant context at session start.
- **Remember**: Persist durable decisions as they occur.
## Active feature
`spec/demo/spec.kvx` โ read its `[meta]` status, `[req.*]` acceptance criteria, and the `[task.*]` list (status + wave + requires). Work one task at a time in wave order; update `status` in the kvx as you go.
## Hard rules
- **No Fakes**: Never fake a test to make it pass.
- **No Git**: The user drives commits.