Files
agentic-dev/docs/work
Danijel Martinek 7f1a8d0212 docs: introduce library evaluation policy (ADR-022 + PRD)
- ADR-022 codifies the tiered library-evaluation policy: 8 hard
  auto-reject filters (license, types, maintenance, boundary-fit,
  shadow-check, EU residency, CVE scan, named consumer), 3
  discussion prompts, per-decision trace artifact at
  docs/library-decisions/, and a 4-layer enforcement stack
  (Claude PreToolUse/PostToolUse hook -> evaluate-library skill ->
  pre-commit hook -> sandcastle reviewer prompt). Mirrors the
  conformance-system latency pattern from ADR-012.
- PRD at docs/work/prds/2026-05-14-library-evaluation-policy.prd.md
  seeds the implementation epic; status: approved, ready for
  \`pnpm work decompose\`.
- Glossary gains "Library trace" + "Pre-shipped trace" entries
  referenced by both artifacts.

Catalyst: the 2026-05-14 grill session nearly adopted
trpc-to-openapi + zod-to-json-schema before someone asked who the
HTTP consumer was. Honest answer: none -- all callers are TS via
createCaller. This policy makes that question structurally
unavoidable for any future feature- or core-tier dep.
2026-05-14 06:41:28 +02:00
..

docs/work — the local task system

Filesystem-backed Epic/Story/Task hierarchy used by AI agents and humans alike. See docs/architecture/agent-first-workflow-and-conformance.md for the full design. Until the work-system-v1 epic ships orchestration tooling, this folder is human-driven — agents read the files for context, humans flip checkboxes.

Layout

  • prds/<date>-<slug>.prd.md — source PRDs
  • <epic-slug>/_epic.md — one folder per epic
  • <epic-slug>/<story-slug>/_story.md — one folder per story
  • <epic-slug>/<story-slug>/<task-slug>.task.md — one file per task
  • _templates/ — copy-paste templates (added in work-system-v1)
  • _state.json — derived index (added in work-system-v1)

PRD lifecycle

PRD status frontmatter field: draft → in-review → approved → shipped.

  • draft → in-review — author flips when ready for review (manual)
  • in-review → approved — human reviewer flips on acceptance (manual)
  • approved → shipped — auto-flipped by pnpm work prd-ship <prd-id> when the seed epic finishes. The state-builder surfaces this signal under _state.jsonneeds_prd_ship[] so the orchestrator (or a reviewer running the sandcastle workflow) can act on it.

The decomposer refuses to run on draft PRDs. Once approved, the seed epic is generated; once the epic completes, the PRD is automatically flipped to shipped along with its commit list.