feat(website): add HAIKU references, rename Construction to Execution, add Operation/Reflection docs

jwaldrip · claude · jwaldrip · commit 6fc0097c1210 · 2026-03-06T07:55:19.000-07:00
- Add "Part of the HAIKU Method" badge on homepage with link to haikumethod.ai
- Update hero description to reference HAIKU as parent methodology
- Add HAIKU reference to footer, about page, start-here, docs index, quick-start
- Add HAIKU Method to navigation (Resources &gt; Related Projects) and footer links
- Rename "Construction" to "Execution" across all website documentation
- Replace /construct with /execute in all docs (quick-start, workflows, guides, examples, checklists)
- Add Operational and Reflective workflow sections to workflows.md
- Add HAIKU reference note to AI-DLC paper
- Add changelog entry covering HAIKU integration, /execute, Operation, Reflection phases

Co-Authored-By: Claude Opus 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+### Added
+
+- HAIKU integration — AI-DLC is now the software development profile of HAIKU (Human AI Knowledge Unification)
+- `/execute` skill replaces `/construct` (deprecated alias still works)
+- Operation phase (`/operate`) available for AI-DLC intents (opt-in)
+- Reflection phase (`/reflect`) available for AI-DLC intents (opt-in)
+- `operational` and `reflective` workflows
+- Configurable quality gates via `.ai-dlc/settings.yml`
+
+### Changed
+
+- "Construction" renamed to "Execution" in user-facing messages and documentation
+
+### Deprecated
+
+- `/construct` (use `/execute` instead)
+
 ## [1.20.6] - 2026-03-05
 
 ### Fixed
diff --git a/website/app/about/page.tsx b/website/app/about/page.tsx
@@ -16,8 +16,16 @@ export default function AboutPage() {
 
 				<div className="prose prose-gray dark:prose-invert max-w-none">
 					<p className="lead text-xl text-gray-600 dark:text-gray-400">
-						AI-DLC is a methodology for structured, iterative software
-						development with AI assistants. It provides a framework for
+						AI-DLC is how software teams use the{" "}
+						<a
+							href="https://haikumethod.ai"
+							target="_blank"
+							rel="noopener noreferrer"
+							className="text-blue-600 hover:underline dark:text-blue-400"
+						>
+							HAIKU Method
+						</a>{" "}
+						(Human AI Knowledge Unification). It provides a framework for
 						organizing work into focused units with clear phases and
 						responsibilities.
 					</p>
@@ -41,7 +49,7 @@ export default function AboutPage() {
 					<h2>The Hat System</h2>
 
 					<p>
-						AI-DLC organizes work through hats — distinct mindsets that keep each phase of development focused. The default construction workflow uses three core hats, while specialized workflows add hats for security testing, design, TDD, and scientific debugging.
+						AI-DLC organizes work through hats — distinct mindsets that keep each phase of development focused. The default execution workflow uses three core hats, while specialized workflows add hats for security testing, design, TDD, and scientific debugging.
 					</p>
 
 					<h3>Planner</h3>
@@ -114,6 +122,23 @@ export default function AboutPage() {
 						<div><code>/plugin install ai-dlc@thebushidocollective-ai-dlc --scope project</code></div>
 					</div>
 
+					<h2>Part of the HAIKU Method</h2>
+					<p>
+						AI-DLC is the software development profile of{" "}
+						<a
+							href="https://haikumethod.ai"
+							target="_blank"
+							rel="noopener noreferrer"
+							className="text-blue-600 hover:underline dark:text-blue-400"
+						>
+							HAIKU
+						</a>{" "}
+						(Human AI Knowledge Unification) — a methodology for structured
+						collaboration between humans and AI across any domain. HAIKU provides
+						the universal framework; AI-DLC applies it specifically to software
+						development.
+					</p>
+
 					<h2>Part of Han</h2>
 					<p>
 						AI-DLC is part of the{" "}
diff --git a/website/app/components/Footer.tsx b/website/app/components/Footer.tsx
@@ -20,8 +20,16 @@ export function Footer() {
 							AI-DLC
 						</Link>
 						<p className="mt-3 text-sm text-gray-600 dark:text-gray-400">
-							A methodology for iterative AI-driven development with hat-based
-							workflows.
+							The software development profile of the{" "}
+							<a
+								href="https://haikumethod.ai"
+								target="_blank"
+								rel="noopener noreferrer"
+								className="underline hover:text-gray-900 dark:hover:text-white"
+							>
+								HAIKU Method
+							</a>
+							.
 						</p>
 						{/* Social links */}
 						<div className="mt-4 flex gap-3">
diff --git a/website/app/page.tsx b/website/app/page.tsx
@@ -237,7 +237,15 @@ export default function Home() {
 									<span className="absolute inline-flex h-full w-full animate-ping rounded-full bg-blue-400 opacity-75" />
 									<span className="relative inline-flex h-2 w-2 rounded-full bg-blue-500" />
 								</span>
-								Now available for Claude Code
+								Part of the{" "}
+								<a
+									href="https://haikumethod.ai"
+									target="_blank"
+									rel="noopener noreferrer"
+									className="underline hover:text-blue-900 dark:hover:text-blue-100"
+								>
+									HAIKU Method
+								</a>
 							</div>
 							<h1 className="mb-6 text-4xl font-bold tracking-tight sm:text-5xl lg:text-6xl">
 								<span className="bg-gradient-to-r from-blue-600 to-purple-600 bg-clip-text text-transparent dark:from-blue-400 dark:to-purple-400">
@@ -248,8 +256,16 @@ export default function Home() {
 								AI-Driven Development Lifecycle
 							</p>
 							<p className="mb-8 text-lg text-gray-600 dark:text-gray-400">
-								A methodology for iterative, high-quality software development
-								with AI. Structure your work with clear phases, switch contexts
+								AI-DLC is how software teams use the{" "}
+								<a
+									href="https://haikumethod.ai"
+									target="_blank"
+									rel="noopener noreferrer"
+									className="text-blue-600 hover:underline dark:text-blue-400"
+								>
+									HAIKU Method
+								</a>
+								. Structure your work with clear phases, switch contexts
 								intentionally, and ship with confidence.
 							</p>
 							<div className="flex flex-col gap-4 sm:flex-row">
diff --git a/website/app/start-here/page.tsx b/website/app/start-here/page.tsx
@@ -157,7 +157,17 @@ export default function StartHerePage() {
 				<div className="mb-8 text-center">
 					<h1 className="mb-4 text-4xl font-bold">Start Here</h1>
 					<p className="text-lg text-gray-600 dark:text-gray-400">
-						Your guided path to understanding and implementing AI-DLC.
+						Your guided path to understanding and implementing AI-DLC, the
+						software development profile of the{" "}
+						<a
+							href="https://haikumethod.ai"
+							target="_blank"
+							rel="noopener noreferrer"
+							className="text-blue-600 hover:underline dark:text-blue-400"
+						>
+							HAIKU Method
+						</a>
+						.
 					</p>
 				</div>
 
diff --git a/website/content/docs/adoption-roadmap.md b/website/content/docs/adoption-roadmap.md
@@ -31,7 +31,7 @@ Before starting Phase 1, ensure you have:
 **First session:**
 1. Install the AI-DLC plugin
 2. Create your first intent with 2-3 units
-3. Work through the first unit using `/elaborate` and `/construct`
+3. Work through the first unit using `/elaborate` and `/execute`
 4. Complete the full hat cycle
 
 **Subsequent sessions:**
diff --git a/website/content/docs/checklist-first-intent.md b/website/content/docs/checklist-first-intent.md
@@ -70,16 +70,16 @@ Use `/elaborate` to define your intent collaboratively with Claude.
 ### Elaboration Complete
 - [ ] Intent is clear and well-defined
 - [ ] Units are appropriately scoped
-- [ ] Ready to begin construction
+- [ ] Ready to begin execution
 
 ---
 
 ## Phase 2: First Unit
 
-Work through your first unit using `/construct`.
+Work through your first unit using `/execute`.
 
-### Start Construction
-- [ ] Run `/construct`
+### Start Execution
+- [ ] Run `/execute`
 - [ ] Verify Claude loaded the correct unit
 
 ### Planner Hat
@@ -137,7 +137,7 @@ Continue with remaining units.
 
 ### For Each Remaining Unit
 
-- [ ] Run `/construct` to load next unit
+- [ ] Run `/execute` to load next unit
 - [ ] Review any dependencies are satisfied
 - [ ] Complete Planner → Builder → Reviewer cycle
 - [ ] Commit with unit reference
@@ -146,7 +146,7 @@ Continue with remaining units.
 ### Between Units
 
 - [ ] Check if context is getting heavy
-- [ ] `/clear` if needed, then `/construct` to continue
+- [ ] `/clear` if needed, then `/execute` to continue
 - [ ] Verify committed artifacts reflect current state
 
 ### Handling Blockers
@@ -214,7 +214,7 @@ Answer these questions honestly:
 
 **Tooling:**
 - [ ] Any friction with the commands?
-- [ ] Did `/clear` + `/construct` work smoothly?
+- [ ] Did `/clear` + `/execute` work smoothly?
 - [ ] Were artifacts helpful?
 
 ### Metrics to Note
@@ -240,7 +240,7 @@ Based on this experience:
 | Command | When to Use |
 |---------|-------------|
 | `/elaborate` | Start new intent |
-| `/construct` | Continue/start unit work |
+| `/execute` | Continue/start unit work |
 | `/researcher` | Need more understanding |
 | `/planner` | Need to redesign approach |
 | `/builder` | Ready to implement |
diff --git a/website/content/docs/concepts.md b/website/content/docs/concepts.md
@@ -306,7 +306,7 @@ If you `/clear` without the stop hook:
 
 1. Committed artifacts (`.ai-dlc/`) are safe
 2. Ephemeral state persists in `han keep`
-3. Run `/construct` to continue
+3. Run `/execute` to continue
 
 ## Next Steps
 
diff --git a/website/content/docs/cowork.md b/website/content/docs/cowork.md
@@ -26,9 +26,9 @@ In cowork mode, after elaboration writes `.ai-dlc/` artifacts and creates ticket
 - The intent branch is pushed to the remote automatically
 - Builders can pull the branch or clone independently
 
-## Construction in Cowork
+## Execution in Cowork
 
-The `/construct` skill handles cowork transparently:
+The `/execute` skill handles cowork transparently:
 
 - Ensures remote tracking is configured for the intent branch
 - Pulls latest changes before starting each unit
diff --git a/website/content/docs/example-bugfix.md b/website/content/docs/example-bugfix.md
@@ -60,7 +60,7 @@ indicate database connection timeout. Issue started approximately
 
 Since this is a single investigation, I'll create one unit for the full debug cycle."
 
-## Phase 2: Construction
+## Phase 2: Execution
 
 ### Observer Hat (OHOTL)
 
diff --git a/website/content/docs/example-feature.md b/website/content/docs/example-feature.md
@@ -117,12 +117,12 @@ Shall I create these files?"
 User: Yes, looks good.
 ```
 
-## Phase 2: Construction - Unit 01
+## Phase 2: Execution - Unit 01
 
 ### Starting the First Unit
 
 ```
-User: /construct
+User: /execute
 ```
 
 ### Planner Hat (HITL)
@@ -280,7 +280,7 @@ All quality gates pass. Unit complete."
 
 Ready for unit-02."
 
-## Phase 3: Construction - Unit 02
+## Phase 3: Execution - Unit 02
 
 ### Planner Hat
 
@@ -365,7 +365,7 @@ All gates pass."
 
 APPROVE."
 
-## Phase 4: Construction - Units 03-04
+## Phase 4: Execution - Units 03-04
 
 *(Similar pattern continues for frontend and preferences units)*
 
diff --git a/website/content/docs/guide-developer.md b/website/content/docs/guide-developer.md
@@ -16,7 +16,7 @@ This guide covers the day-to-day workflow of using AI-DLC. It assumes you've com
    - Review any blockers from previous sessions
 
 2. **Load context**
-   - Run `/construct` if continuing existing work
+   - Run `/execute` if continuing existing work
    - Run `/elaborate` if starting new work
 
 3. **Announce your hat**
@@ -52,7 +52,7 @@ This guide covers the day-to-day workflow of using AI-DLC. It assumes you've com
 You left off mid-unit or a colleague handed you an intent.
 
 ```
-/construct
+/execute
 ```
 
 This loads the intent and current unit state. Review what's been done:
@@ -91,7 +91,7 @@ Solution:
 /clear
 ```
 
-Then `/construct` to reload from committed state. The hat system ensures your progress is captured in files, not just context.
+Then `/execute` to reload from committed state. The hat system ensures your progress is captured in files, not just context.
 
 ### Getting Stuck
 
diff --git a/website/content/docs/hats.md b/website/content/docs/hats.md
@@ -15,11 +15,11 @@ The hat system prevents:
 - **Quality shortcuts**: Skipping review to "just ship it"
 - **Role confusion**: Trying to attack and defend code at the same time
 
-By explicitly switching hats, you maintain focus and ensure each phase gets proper attention. Domain research happens during Mob Elaboration (`/elaborate`), before construction begins.
+By explicitly switching hats, you maintain focus and ensure each phase gets proper attention. Domain research happens during Mob Elaboration (`/elaborate`), before execution begins.
 
 ## Core Hats
 
-These hats form the backbone of the default construction workflow: **Planner -> Builder -> Reviewer**. They are also reused across other workflows.
+These hats form the backbone of the default execution workflow: **Planner -> Builder -> Reviewer**. They are also reused across other workflows.
 
 ### Planner
 
diff --git a/website/content/docs/index.md b/website/content/docs/index.md
@@ -4,7 +4,7 @@ description: An introduction to AI-DLC and its core concepts
 order: 1
 ---
 
-AI-DLC is a methodology for structured, iterative software development with AI assistants. It provides a framework for organizing work into focused units with clear phases and responsibilities.
+AI-DLC is the software development profile of the [HAIKU Method](https://haikumethod.ai) (Human AI Knowledge Unification). It provides a framework for structured, iterative software development with AI assistants, organizing work into focused units with clear phases and responsibilities.
 
 ## Why AI-DLC?
 
diff --git a/website/content/docs/installation.md b/website/content/docs/installation.md
@@ -172,7 +172,7 @@ However, committing is recommended - it provides:
 
 ### Commands Not Recognized
 
-**Symptom:** `/elaborate` or `/construct` don't activate
+**Symptom:** `/elaborate` or `/execute` don't activate
 
 **Solutions:**
 1. Restart Claude Code session
diff --git a/website/content/docs/providers.md b/website/content/docs/providers.md
@@ -6,7 +6,7 @@ order: 7
 
 # Providers
 
-Providers connect AI-DLC to external systems your team already uses — ticketing, specs, design tools, and communication channels. When configured, AI-DLC automatically syncs work across these systems during elaboration and construction.
+Providers connect AI-DLC to external systems your team already uses — ticketing, specs, design tools, and communication channels. When configured, AI-DLC automatically syncs work across these systems during elaboration and execution.
 
 ## Provider Categories
 
@@ -74,7 +74,7 @@ When you run `/elaborate`, AI-DLC uses providers to enrich the process:
    - Unit `depends_on` relationships become ticket blocked-by links
    - Epic and ticket keys are stored in intent/unit frontmatter
 
-### During Construction
+### During Execution
 
 Hats interact with providers as they work:
 
diff --git a/website/content/docs/quick-start.md b/website/content/docs/quick-start.md
diff --git a/website/content/docs/workflows.md b/website/content/docs/workflows.md
diff --git a/website/content/papers/ai-dlc-2026.md b/website/content/papers/ai-dlc-2026.md
diff --git a/website/lib/navigation.ts b/website/lib/navigation.ts
