DevArch Demo Script

Logged into devarch macOS user (clean account)
No ~/.claude/ artifacts, no repos in ~/
Three windows ready: Terminal (large), Browser x2 (events + app)
Screen recording running
iPad showing this script

Act 1 — The Install

Beat 1 — Clone DevArch

Get the product

Terminal

"Starting from a clean macOS account. No tools, no repos, nothing."

cd ~
git clone https://github.com/DevArch-AI/devarch-ai.git

Beat 2 — Create the project

Empty repo, no code yet

Terminal

mkdir tax1040 && cd tax1040
git init
npm init -y

Beat 3 — Install DevArch

One command brings the methodology in

Terminal

"DevArch installs agents, hooks, and skills into the Claude Code environment. One command."

../devarch-ai/docs/workflow/devarch install

WAIT — let output finish, show what it installed

Beat 4 — Start Claude Code + Demo Events

Open Claude Code, start the event feed

Terminal Events

claude

Once inside Claude Code:

/demo-events start

SHOW — open http://localhost:3377 in the events browser window

"This event feed shows DevArch's hooks firing in real time. Every structured decision the agent makes shows up here."

Act 2 — Discovery

Beat 5 — Brainstorm

Define the domain through conversation

Terminal Events

/brainstorm

"We're building a 1040 tax return app. Supports W2 and 1099 income, standard and itemized deductions — mortgage interest, charitable contributions, vehicle expenses. Outputs the completed 1040 with tax owed or refund."

WAIT — let the brainstorm converge. Answer its questions. Hit these points:

TypeScript full-stack (shows wire-type sharing)
EZ path first, then 1099, then itemized
Domain matters: filing status, brackets, phase-outs, standard vs itemized logic
Output: calculate tax owed / refund amount

Act 3 — Planning

Beat 6 — Session Planning

DevArch decomposes the work into phases

Terminal Events

"Now I ask DevArch to plan. It breaks the project into session-sized phases."

"Plan the implementation of this tax app"

WAIT — plan-gate events fire on the event feed. Show the plan when it appears.

"Each phase is scoped to one session. DevArch won't start coding until I approve the plan."

Say: "looks good, let's start phase 1"

Act 4 — Building (EZ Path)

Beat 7 — First Code

Domain types + W2 income handler

Terminal Events

Let DevArch work. Watch for:

Header comments on every file (Rule 8)
Boundary check events when domain files are created
Behavior Statements in the conversation before tests
Wire types extracted into a shared file (Rule 7b)

SHOW — event feed lighting up with boundary-check, mutation-verify events

Beat 8 — Test Grading

DevArch grades every test GREEN/YELLOW/RED

Terminal

"Every test gets graded. RED and YELLOW tests are rewritten before committing. Only GREEN ships."

WAIT — watch for the Behavior Statement, then test derivation + grading in the conversation

Beat 9 — First ADR

Architecture Decision Record captured

Terminal

"DevArch asks if a decision is ADR-worthy. This one constrains future sessions, so we record it."

If DevArch doesn't prompt for an ADR naturally, nudge: "That tax rule modeling decision feels ADR-worthy"

Beat 10 — Show the App

EZ path working end-to-end

Terminal App

"W2 income in, standard deduction applied, tax calculated. The EZ path works."

SHOW — switch to app browser window, enter W2 data, see tax result

Act 5 — Session Continuity

Beat 11 — End Session 1

Work summary + commit

Terminal Events

"commit and push"

"DevArch writes a structured work summary before committing. Every session leaves a trail."

SHOW — session-finalize event on the feed

Exit Claude Code: /exit

Beat 12 — Start Session 2

Recap + pre-session audit

Terminal Events

claude

"New session. DevArch reads the last summary, presents a recap, runs a pre-session audit. No context lost."

WAIT — let the recap and audit finish. This is a key selling moment.

Say: "let's continue with the next phase"

Act 6 — Complexity (1099 + Itemized)

Beat 13 — 1099 Income

New bounded context, Schedule C/SE

Terminal Events

Watch for new boundary checks as a second context emerges. Commands and events named per Rule 9.

Beat 14 — Itemized Deductions

Mortgage, charity, vehicle — standard vs itemized decision

Terminal Events

"Now the app decides whether standard or itemized is better. Mortgage interest has the TCJA date rule — that's a Behavior Statement with REJECTS WHEN."

This should trigger another ADR about the standard-vs-itemized decision logic.

Beat 15 — Show the App (Full)

Complete 1040 with all income + deductions

App

SHOW — enter W2 + 1099 income, mortgage + charity deductions, see the full 1040 result with correct tax/refund

Act 7 — The Close

Beat 16 — Final Commit

Wrap up, summary, push

Terminal Events

"commit and push"

SHOW — final session-finalize event

Beat 17 — The Artifact

Show what DevArch produced beyond the code

Terminal

"Beyond the working app, look at what DevArch produced:"

ls docs/context/    # session summaries
ls docs/adrs/       # architecture decisions
cat docs/context/project-profile.md

"Every session is documented. Every architectural decision is recorded. A new team member can read these and understand not just what was built, but why."

Key moments to capture for the edit:
• The install (30 sec)
• Event feed lighting up for the first time (10 sec)
• Brainstorm converging on the domain (60 sec)
• Plan decomposition (30 sec)
• A Behavior Statement leading to tests (45 sec)
• Test grading (GREEN) (15 sec)
• An ADR being captured (30 sec)
• Wire-type sharing in action (15 sec)
• Session recap across restart (30 sec)
• The working app (30 sec)
• The docs artifact at the end (30 sec)

Target final cut: 5–7 minutes

Pre-Recording Checklist

Act 1 — The Install

Act 2 — Discovery

Act 3 — Planning

Act 4 — Building (EZ Path)

Act 5 — Session Continuity

Act 6 — Complexity (1099 + Itemized)

Act 7 — The Close