spec-workflow · diff
git:20261017.e2f8909 to git:20261022.a8528d7
5 added, 19 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.
+ This file is a generated pointer. The single workflow source is `spec/workflow.kvx`; edit it and run `hyperfide spec render`, never this file.
- ## Principles
+ ## Active feature
- - **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.
+ `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.
## 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
+ ## Where the rules are
- - **No Fakes**: Never fake a test to make it pass.
- - **No Git**: The user drives commits.
+ Principles, hard rules and policies live only in `spec/workflow.kvx`: `[principle]`, `[hard_rules]`, `[status_values]`, `[memory]`. Read them there.