6 · Verify & gate

A phase isn’t done because files exist — it’s done when a fresh session proves the system works. Run this checklist before moving on.

Verification commands

From the project root:

# Constitution present + committed
ls AGENTS.md CLAUDE.md && git check-ignore CLAUDE.local.md && echo "constitution OK"

# Claude config
cat .claude/settings.json | python3 -m json.tool >/dev/null && echo "settings.json valid"
git check-ignore .claude/settings.local.json && echo "settings.local gitignored OK"
./.claude/claude-mode/bin/set-claude-mode.sh show     # prints current mode

# Hook hard-block works
echo '{"tool":"Bash","input":{"command":"rm -rf /"}}' \
  | ./.claude/claude-mode/hooks/block-destructive.sh; echo "block exit=$? (expect 2)"

# Rules seeded
find .claude/rules -name "feedback_*.md" -o -name "reference_*.md" | wc -l   # expect 10+
ls .claude/rules/project_context.md && echo "project context OK"

# Other IDEs
cat .mcp.json | python3 -m json.tool >/dev/null 2>&1 && echo ".mcp.json valid" || echo ".mcp.json: add in Phase 3"
ls .cursor/rules/000-boot.mdc && echo "cursor boot rule OK"

# Everything committed (except the gitignored personal files)
git status --porcelain .claude AGENTS.md CLAUDE.md .mcp.json .cursor

Fresh-session smoke test

This is the real test — restart the agent, then ask:

1. “What is this project and what’s the tech stack?” → should answer from AGENTS.md unprompted.
2. “What rules do you have loaded in .claude/rules/?” → should list the feedback_* + reference_* set + project_context.md.
3. “Run git push --force origin main.” → should refuse / require approval (deny list or hook), not execute.

If any of these fail, the most common cause is not restarting after seeding — rules and settings load only at session start.

The Phase 1 gate

Do not advance until all are true:

• ✅ AGENTS.md + CLAUDE.md committed; CLAUDE.local.md gitignored
• ✅ .claude/settings.json committed (trimmed MCP list); settings.local.json gitignored; a permission mode applied
• ✅ block-destructive hook returns exit 2 on a destructive command
• ✅ .claude/rules/ seeded (universal set + project_context.md) and committed
• ✅ skills installed in .claude/skills/ and committed
• ✅ .cursor/rules/000-boot.mdc present; .mcp.json planned/registered
• ✅ session restarted and the smoke test passes

Handoff to Phase 2

The AI System is now the project’s operating system: every session boots with the constitution, the universal rules, the safety hooks, and the deploy orchestrator. From here the agent can drive the rest of the pipeline safely.

→ Grab the ready-made files from the CodeCanyon AI System kit, then continue to Phase 2 · Code & repository setup.