adr

Examples from HELIX’s own docs. These generated pages come from docs/helix/. Use them to see the method in practice; start with the artifact-type catalog for reusable templates.

ADR-002: HELIX Tracker Write Safety Model
ADR-003: Autonomy is a Three-Position Spectrum, Not a Fixed Level
ADR-004: Artifact Dependencies Are Encoded in meta.yml.relationships Only (No Separate dependencies.yaml)
ADR-005: Concern practices.md is HELIX-activity-keyed
ADR-006: Concern boundary lives once, in concern.md
ADR-007: Empty ADR References Headers Are Dropped; Required Only When a Concern Cites a Specific ADR
ADR-008: data-PRD Is a Kind-Switch Variant of PRD, Not a Sibling Artifact
ADR-009: Acceptance Criteria Live in User-Stories; Feature-Specification Owns Functional Areas and Decomposition
ADR-010: feature-registry and parking-lot stay separate with an explicit handoff
ADR-011: ux-radix owns Radix and shadcn prescriptions; react-nextjs references
ADR-012: Runbook owns incident response procedures; monitoring-setup owns detection only
ADR-013: Cross-phase informs edges are valid when declared on the downstream artifact
ADR-014: Deferred: architecture-style slot occupants remain four separate concerns