Wave Template
Reusable template for Valenar implementation waves.
Use the docs-only workflow for documentation work and the default code-wave workflow for runtime or engine work.
Workflow Variants
| Workflow | Step order | Verification focus |
|---|---|---|
| Default code wave | Explore -> Implement -> Validate -> Tenets | build, tests, spec compliance, tenet checks |
| Docs-only wave | Explore -> Implement -> Verify | prompt fidelity, touched-doc consistency, canon, source-of-truth alignment |
Each named step is a dispatched role, never an inline checklist for the orchestrator to run directly.
Required role chain for Valenar waves: explorer -> implementer -> verifier.
For docs-only waves, the verifier performs the Verify step.
Verify or Validate FAIL means Implement runs again with the failure as the new spec.
FAIL means immediate re-dispatch to Implement with the failure as the new spec; inline wave execution remains forbidden.
Blank Template
## Wave N — [Title]
**Goal:** [one sentence]
**Status:** [planned / active / shipped]
**Workflow:** [default code wave / docs-only wave]
### Ships
- [deliverable 1]
- [deliverable 2]
- [deliverable 3]
### Does Not Ship
- [explicitly deferred item]
- [explicitly deferred item]
### Files Affected
- New files:
- `[path/to/file]`
- Modified files:
- `[path/to/file]` — [what changed]
### Authorities
- [../systems/gd-resources-items-crafting.md](../systems/gd-resources-items-crafting.md) — [why it matters]
- [../systems/gd-world-pressure-nexus.md](../systems/gd-world-pressure-nexus.md) — [why it matters]
- [../generation/gd-world-generation-contract.md](../generation/gd-world-generation-contract.md) — [why it matters]
### Open Questions
1. [question] — proposed answer: [...]
2. [question] — proposed answer: [...]
### Verification Forecast
- `[command or check]` — [what it verifies]
- `[command or check]` — [what it verifies]
Working Rules
- Keep docs-only waves inside approved documentation paths.
- Treat Explore, Implement, Validate, Verify, and Tenets as dispatched roles, not inline orchestrator work.
- The main project agent is the orchestrator and must dispatch wave work instead of doing it inline.
- Do not invent files, APIs, syntax, lore, or mechanics.
- Update the owner doc before updating summary pages.
- Treat committed repository docs as authority ahead of scratch notes.