Skip to content

HELIX Install Why HELIX Use HELIX Types Concerns Platforms Reference GitHub

CTRL K

Install
Why HELIX
Use HELIX
Types
Concerns
Platforms
Reference

adr
contracts
decisions
executions
- Execution Docs
features
hero image concepts
- HERO-2026-05-12 Document Spine Helix Concept
solution designs
- Solution Design: SD-002 — First-Class Principles
technical designs
test plans
- TP-014 Appendix A: Real-World Intent Patterns From Session Logs
- Workflow Test Plan: HELIX Across Five Runtimes
Product Vision
Project Concerns
Product Requirements Document
Project Principles
Architecture
Bench Build Results — 2026-06-05
First post-P14 full-bench run — 2026-06-06
Data Design — HELIX Bead Tracker
Design: helix-library Split
HELIX Family: Marker File + Type/Flow/Instance Linkage Relaxation
Family Marker + Linkage Relaxation — Entry-Point Report
helix-family Readiness Report
Homepage Worked Example Graph
Implementation Plan: helix-library Family (monorepo, test-first)
Phase 5a results — canonical promotion targeted re-bench
Phase 7 results — synthetic-prompt rewrite verification
Phase 8 results — bench infra + 5 surgical fixes
Plan: harden the Claude Code install surface
Plan: Fold DataHelix templates into the HELIX catalog
Plan: §Refresh as a first-class HELIX skill behavior
Plan — HELIX self-improvement from the yolo-demo arc (2026-05-24, rev 2: codex-reviewed)
Plan — concern slots + operator house-style (2026-05-25)
Plan — decomposition/coverage determinism + e2e expectation (2026-05-25)
Plan — integrate the measurement-discipline learnings into HELIX (2026-05-25)
Plan — DDx-reference runtime-neutrality remediation (2026-05-25)
Plan — sample-data concern (semantic faker, varied shapes) (2026-05-25)
Plan — UX interface guidelines (ux-radix active-state) + DESIGN.md artifact (2026-05-25)
Plan — aggressive-verification concern + AC-citation traceability (2026-05-25)
Plan: `admin-console` + `auth` concerns — the foundational product surfaces (it.35)
Plan — it.36: bidirectional spec↔code traceability gate + spec-is-the-contract principle
Plan — complex-brief robustness: verification ENFORCEMENT + spike-first for unknowns (2026-05-26)
Plan — it.37: artifact-tier decomposition boundaries (PRD ↔ FEAT ↔ story)
Plan: spike-first ACTIVATION trigger (close the reframe-and-defer escape hatch)
Plan: it.34 — "defer the vendor" is NOT a spike; a spike must EXERCISE the real provider and prove its economics (+ build the app-side data; unowned business calls → guidance-needed)
Plan — concern-library expansion + make-concerns-bite + iterate-to-convergence (2026-05-27)
Curated page scopes — lock the document boundaries before the prose pass
Prose-quality pass — evaluate and implement the expanded Vale findings
Rename "authority order" to "authority hierarchy"
Artifact-type and concern audit — gaps and remediation plan
Plan: helix-infra sibling repo
FINAL Plan: helix-library Split — REVISED POST-MONOREPO 2026-06-04
Plan: helix-library Migration
Plan: Conversation-bench + Autonomy slider + Flow model
Security Architecture — DDx Agent Execution Surface
Stage 5b — partial results + API rate limit hit
Test Plan: helix Family Bench Fixtures
Phase 6 Tier 4 results — canonical-iteration verification re-bench
Validation Plan — Vertical Slice Completion
HELIX Family Vertical-Slice Validation Results — 2026-06-05
Deployment Checklist — HELIX Plugin and Website Release
Monitoring Setup — `ddx-server`
Release Notes — HELIX v0.3.3
Runbook — `ddx-server`
Improvement Backlog — HELIX 2026-Q2
Metrics Dashboard: HELIX 2026-Q2 (post-`v0.3.3`)
HELIX Prompt Iteration Protocol and Evaluation Rubric
Research: Principles Injection Strategy Effectiveness
Security Metrics — HELIX 2026-Q2 (post-`v0.3.3`)

On this page

executions

executions

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.

Execution Docs

© 2025 Hextra Project.