mikkel/nexus
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
nexus/.planning/phases/01-foundation/01-VALIDATION.md
Mikkel Georgsen 6c4272ce85 [nexus] chore: migrate .planning/ from agent repo to nexus repo 
Planning artifacts (milestones v1.0-v1.2.1, v1.3 queue, PROJECT.md,
STATE.md, config) now live alongside the code they describe.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-04 03:55:42 +00:00

2.6 KiB
Raw Blame History

phase slug status nyquist_compliant wave_0_complete created
1 foundation draft false false 2026-03-30

Phase 1 — Validation Strategy

Per-phase validation contract for feedback sampling during execution.

Test Infrastructure

Property Value
Framework vitest 3.x (already configured in root vitest.config.ts)
Config file vitest.config.ts (root multi-project config)
Quick run command pnpm vitest run --project packages/db
Full suite command pnpm vitest run
Estimated runtime ~30 seconds

Sampling Rate

  • After every task commit: Run pnpm vitest run --project packages/db
  • After every plan wave: Run pnpm vitest run
  • Before /gsd:verify-work: Full suite must be green
  • Max feedback latency: 30 seconds

Per-Task Verification Map

Task ID Plan Wave Requirement Test Type Automated Command File Exists Status
01-01-01 01 1 FOUND-01 unit pnpm vitest run packages/branding ❌ W0 ⬜ pending
01-02-01 02 1 FOUND-02 file-check test -f .planning/ZONE-TAXONOMY.md ❌ W0 ⬜ pending
01-03-01 03 1 FOUND-03 script `echo "test" .git/hooks/commit-msg` ❌ W0
01-04-01 04 1 FOUND-04 config-check git config --get rerere.enabled ❌ W0 ⬜ pending

Status: ⬜ pending · ✅ green · ❌ red · ⚠️ flaky

Wave 0 Requirements

  • packages/branding/src/__tests__/vocab.test.ts — unit test for VOCAB export
  • Branding package added to vitest config projects

If none: "Existing infrastructure covers all phase requirements."

Manual-Only Verifications

Behavior Requirement Why Manual Test Instructions
Pre-commit hook rejects bad messages FOUND-03 Git hook only runs during actual commits Run git commit --allow-empty -m "bad" and verify rejection, then git commit --allow-empty -m "[nexus] good" and verify acceptance
Rebase runbook accuracy FOUND-04 Document content review Read .planning/REBASE-RUNBOOK.md and verify it documents git range-diff workflow

Validation Sign-Off

  • All tasks have <automated> verify or Wave 0 dependencies
  • Sampling continuity: no 3 consecutive tasks without automated verify
  • Wave 0 covers all MISSING references
  • No watch-mode flags
  • Feedback latency < 30s
  • nyquist_compliant: true set in frontmatter

Approval: pending