chati-dev 2.0.8 → 2.1.0

package/framework/data/entity-registry.yaml

@@ -5,7 +5,7 @@
 metadata:
   version: "1.0.0"
   last_updated: "2026-02-12T00:00:00Z"
-  entity_count: 47
+  entity_count: 50
   checksum_algorithm: sha256
 
 entities:
@@ -19,7 +19,7 @@ entities:
       adaptability: 0.2
 
     greenfield-wu:
-      path: chati.dev/agents/planning/greenfield-wu.md
+      path: chati.dev/agents/discover/greenfield-wu.md
       type: agent
       purpose: "Analyze greenfield project context, constraints, and technology landscape"
       keywords: [greenfield, analysis, context, technology, constraints]
@@ -27,7 +27,7 @@ entities:
       adaptability: 0.5
 
     brownfield-wu:
-      path: chati.dev/agents/planning/brownfield-wu.md
+      path: chati.dev/agents/discover/brownfield-wu.md
       type: agent
       purpose: "Deep discovery of existing codebase — architecture, patterns, debt, dependencies"
       keywords: [brownfield, discovery, codebase, architecture, debt]
@@ -35,7 +35,7 @@ entities:
       adaptability: 0.5
 
     brief:
-      path: chati.dev/agents/planning/brief.md
+      path: chati.dev/agents/discover/brief.md
       type: agent
       purpose: "Extract and structure user requirements through 5 elicitation phases"
       keywords: [requirements, elicitation, brief, functional, non-functional]
@@ -43,7 +43,7 @@ entities:
       adaptability: 0.4
 
     detail:
-      path: chati.dev/agents/planning/detail.md
+      path: chati.dev/agents/plan/detail.md
       type: agent
       purpose: "Transform Brief into formal PRD with complete specifications"
       keywords: [prd, specification, detail, formal, requirements]
@@ -51,7 +51,7 @@ entities:
       adaptability: 0.4
 
     architect:
-      path: chati.dev/agents/planning/architect.md
+      path: chati.dev/agents/plan/architect.md
       type: agent
       purpose: "Design technical architecture, make technology decisions, define system boundaries"
       keywords: [architecture, technology, design, patterns, boundaries]
@@ -59,7 +59,7 @@ entities:
       adaptability: 0.3
 
     ux:
-      path: chati.dev/agents/planning/ux.md
+      path: chati.dev/agents/plan/ux.md
       type: agent
       purpose: "Design user experience, interaction flows, and interface structure"
       keywords: [ux, design, interaction, flows, interface, wireframes]
@@ -67,7 +67,7 @@ entities:
       adaptability: 0.5
 
     phases:
-      path: chati.dev/agents/planning/phases.md
+      path: chati.dev/agents/plan/phases.md
       type: agent
       purpose: "Decompose PRD into development phases with MVP-first strategy"
       keywords: [phases, decomposition, mvp, planning, milestones]
@@ -75,7 +75,7 @@ entities:
       adaptability: 0.4
 
     tasks:
-      path: chati.dev/agents/planning/tasks.md
+      path: chati.dev/agents/plan/tasks.md
       type: agent
       purpose: "Create executable tasks with acceptance criteria from phase definitions"
       keywords: [tasks, acceptance-criteria, executable, given-when-then]
@@ -155,6 +155,14 @@ entities:
       dependencies: []
       adaptability: 0.6
 
+    quick-brief:
+      path: chati.dev/templates/quick-brief-tmpl.yaml
+      type: template
+      purpose: "Condensed brief template for Quick Flow pipeline — single-pass extraction"
+      keywords: [quick, brief, template, fast-track, condensed]
+      dependencies: [brief]
+      adaptability: 0.6
+
   workflows:
     greenfield-fullstack:
       path: chati.dev/workflows/greenfield-fullstack.yaml
@@ -196,6 +204,14 @@ entities:
       dependencies: [orchestrator]
       adaptability: 0.5
 
+    quick-flow:
+      path: chati.dev/workflows/quick-flow.yaml
+      type: workflow
+      purpose: "Fast-track pipeline for simple tasks: bug fixes, small features, config changes. Skips full PLAN phase."
+      keywords: [quick, fast-track, bug-fix, hotfix, simple, condensed]
+      dependencies: [orchestrator, brief, dev, qa-implementation, devops]
+      adaptability: 0.4
+
   schemas:
     session:
       path: chati.dev/schemas/session.schema.json
@@ -333,11 +349,19 @@ entities:
     elicitation:
       path: chati.dev/patterns/elicitation.md
       type: framework
-      purpose: "Elicitation patterns for requirements gathering"
+      purpose: "Elicitation patterns overview and quick reference"
       keywords: [elicitation, requirements, gathering, patterns, interview]
-      dependencies: [brief]
+      dependencies: [brief, elicitation-library]
       adaptability: 0.6
 
+    elicitation-library:
+      path: chati.dev/patterns/elicitation-library.yaml
+      type: intelligence
+      purpose: "Comprehensive catalog of 24 elicitation methods with triggers, steps, agent mapping, and auto-selection rules"
+      keywords: [elicitation, methods, brain-dump, scamper, moscow, five-whys, delphi, pre-mortem, personas, journey-map, stakeholder-map]
+      dependencies: [brief]
+      adaptability: 0.5
+
   i18n:
     en:
       path: chati.dev/i18n/en.yaml

package/framework/domains/agents/brief.yaml

@@ -45,3 +45,17 @@ rules:
   - id: br-05
     text: "MUST validate that success metrics are measurable and specific"
     priority: normal
+
+  - id: br-06
+    text: >
+      MUST select elicitation methods from chati.dev/patterns/elicitation-library.yaml
+      based on project context (type, user level, complexity). Auto-selection rules
+      in the library determine primary and secondary methods.
+    priority: high
+
+  - id: br-07
+    text: >
+      MUST use at least 3 different elicitation methods across the 5 extraction phases.
+      Single-method extraction produces shallow requirements. Recommended: brain-dump +
+      five-whys + playback as minimum set.
+    priority: high

package/framework/domains/agents/qa-implementation.yaml

@@ -41,3 +41,19 @@ rules:
   - id: qai-backward
     text: "If spec/architecture issues found, trigger backward transition to planning mode."
     priority: high
+
+  - id: qai-adversarial
+    text: >
+      ADVERSARIAL REVIEW: Every QA pass MUST identify minimum 3 findings
+      (improvements, warnings, or suggestions). Zero findings is suspiciously
+      clean — trigger mandatory re-review with deeper analysis. This prevents
+      rubber-stamping. Findings can be any severity (low/info counts).
+    priority: critical
+
+  - id: qai-devil-advocate
+    text: >
+      DEVIL'S ADVOCATE: After initial review, assume the opposite conclusion
+      and actively search for evidence to support it. If initial pass says
+      APPROVED, spend one extra pass trying to find reasons to FAIL.
+      Document what you looked for and why it held up (or didn't).
+    priority: high

package/framework/domains/agents/qa-planning.yaml

@@ -42,3 +42,19 @@ rules:
   - id: qap-strategy
     text: "Test strategy must include unit, integration, and E2E test categories."
     priority: normal
+
+  - id: qap-adversarial
+    text: >
+      ADVERSARIAL REVIEW: Every planning validation MUST identify minimum 3
+      findings (gaps, improvements, or suggestions). Zero findings is
+      suspiciously clean — re-analyze with deeper scrutiny across all
+      traceability chains. Findings can be any severity.
+    priority: critical
+
+  - id: qap-devil-advocate
+    text: >
+      DEVIL'S ADVOCATE: After traceability validation, assume the plan has
+      a hidden flaw and actively search for it. Challenge assumptions,
+      question requirement completeness, and look for scope gaps that
+      could surface during BUILD. Document the adversarial analysis.
+    priority: high

package/framework/domains/constitution.yaml

@@ -9,7 +9,7 @@ summary: >
   context brackets, memory governance, registry governance,
   session lock, model governance.
 
-articleCount: 16
+articleCount: 17
 
 rules:
   - id: art-i
@@ -21,7 +21,7 @@ rules:
     priority: critical
 
   - id: art-iii
-    text: "Memory and context must be managed through designated systems (PRISM, RECALL)."
+    text: "Memory and context must be managed through designated systems (PRISM)."
     priority: high
 
   - id: art-iv
@@ -75,3 +75,7 @@ rules:
   - id: art-xvi
     text: "Model governance: respect per-agent model assignments. No downgrade from assigned model."
     priority: high
+
+  - id: art-xvii
+    text: "Execution mode governance: autonomous requires gate >= 90%. Safety net with circuit breaker (3 failures)."
+    priority: critical

package/framework/domains/workflows/brownfield-discovery.yaml

@@ -1,11 +1,9 @@
 # Brownfield Discovery Workflow Domain — PRISM L3
-# Discovery-only pipeline (no implementation)
+# Standalone discovery pipeline (no implementation)
+# Agent: brownfield-wu only (7 phases of analysis)
 
 steps:
   - brownfield-wu
-  - brief
-  - detail
-  - architect
 
 rules:
   - id: disc-deep
@@ -14,3 +12,6 @@ rules:
   - id: disc-readonly
     text: "Discovery workflow does not modify project code."
     priority: high
+  - id: disc-standalone
+    text: "Brownfield discovery is a standalone workflow using only brownfield-wu across 7 analysis phases."
+    priority: normal

package/framework/domains/workflows/quick-flow.yaml

@@ -0,0 +1,23 @@
+# Quick Flow Workflow Domain — PRISM L3
+# Fast-track pipeline for simple tasks (bug fixes, small features, config changes)
+# Skips full PLAN phase — goes from Brief directly to Dev
+
+steps:
+  - brief
+  - dev
+  - qa-implementation
+  - devops
+
+rules:
+  - id: qf-scope
+    text: "Quick Flow is only for low-complexity tasks. Escalate to full pipeline if scope grows."
+    priority: critical
+  - id: qf-quality
+    text: "QA-Implementation validation is mandatory even in Quick Flow. No quality shortcuts."
+    priority: critical
+  - id: qf-brief
+    text: "Brief runs in quick-extraction mode: single-pass, 2 rounds max."
+    priority: high
+  - id: qf-escalation
+    text: "If dev discovers unexpected complexity, pause and offer escalation to full pipeline."
+    priority: high

package/framework/hooks/mode-governance.js

@@ -28,13 +28,25 @@ const MODE_SCOPES = {
   },
 };
 
+// Maps session states to governance modes (Article XI)
+const STATE_TO_GOVERNANCE_MODE = {
+  discover: 'planning',
+  plan: 'planning',
+  planning: 'planning',
+  build: 'build',
+  validate: 'build',
+  deploy: 'deploy',
+  completed: 'deploy',
+};
+
 function getCurrentMode(projectDir) {
   const sessionPath = join(projectDir, '.chati', 'session.yaml');
   if (!existsSync(sessionPath)) return 'planning'; // Default to most restrictive
 
   const raw = readFileSync(sessionPath, 'utf-8');
   const match = raw.match(/^\s*mode:\s*(.+)$/m);
-  return match ? match[1].trim().replace(/^["']|["']$/g, '') : 'planning';
+  const state = match ? match[1].trim().replace(/^["']|["']$/g, '') : 'discover';
+  return STATE_TO_GOVERNANCE_MODE[state] || 'planning';
 }
 
 function isPathAllowed(filePath, projectDir, mode) {
@@ -83,7 +95,7 @@ async function main() {
   }
 }
 
-export { getCurrentMode, isPathAllowed, MODE_SCOPES };
+export { getCurrentMode, isPathAllowed, MODE_SCOPES, STATE_TO_GOVERNANCE_MODE };
 
 // Only run main when executed directly (not imported by tests)
 import { fileURLToPath } from 'url';

package/framework/hooks/model-governance.js

@@ -93,4 +93,8 @@ async function main() {
 
 export { AGENT_MODELS, UPGRADE_CONDITIONS, getCurrentAgent };
 
-main();
+// Only run main when executed directly (not imported by tests)
+import { fileURLToPath } from 'url';
+if (process.argv[1] === fileURLToPath(import.meta.url)) {
+  main();
+}

package/framework/hooks/prism-engine.js

@@ -27,7 +27,7 @@ function readSessionState(projectDir) {
   };
 
   return {
-    mode: extract('mode') || 'planning',
+    mode: extract('mode') || 'discover',
     currentAgent: extract('current_agent') || null,
     workflow: extract('workflow') || null,
     pipelinePosition: extract('pipeline_position') || null,

package/framework/hooks/session-digest.js

@@ -21,7 +21,7 @@ function extractDigest(projectDir) {
 
   return {
     timestamp: new Date().toISOString(),
-    mode: extract('mode') || 'planning',
+    mode: extract('mode') || 'discover',
     currentAgent: extract('current_agent') || 'none',
     pipelinePosition: extract('pipeline_position') || 'unknown',
     workflow: extract('workflow') || 'unknown',
@@ -57,4 +57,8 @@ async function main() {
   }
 }
 
-main();
+// Only run main when executed directly (not imported by tests)
+import { fileURLToPath } from 'url';
+if (process.argv[1] === fileURLToPath(import.meta.url)) {
+  main();
+}

package/framework/hooks/settings.json

@@ -16,6 +16,17 @@
         ]
       }
     ],
+    "PreCompact": [
+      {
+        "matcher": ".*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node chati.dev/hooks/session-digest.js"
+          }
+        ]
+      }
+    ],
     "PreToolUse": [
       {
         "matcher": "Read",

package/framework/i18n/en.yaml

@@ -16,9 +16,9 @@ installer:
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Will install:"
-  agents_count: "13 agent definitions (PLANNING, BUILD, DEPLOY phases)"
-  workflows_count: "5 workflow blueprints"
-  templates_count: "5 templates (PRD, Brownfield PRD, Architecture, Task, QA Gate)"
+  agents_count: "13 agent definitions (DISCOVER, PLAN, BUILD, DEPLOY phases)"
+  workflows_count: "6 workflow blueprints"
+  templates_count: "6 templates (PRD, Brownfield PRD, Architecture, Task, QA Gate, Quick Brief)"
   constitution: "Constitution (17 Articles + Preamble)"
   session_mgmt: "Session management system"
   quality_gates: "Quality gates (4-tier validation)"

package/framework/i18n/es.yaml

@@ -16,9 +16,9 @@ installer:
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Se instalara:"
-  agents_count: "13 definiciones de agentes (fases PLANNING, BUILD, DEPLOY)"
-  workflows_count: "5 blueprints de workflow"
-  templates_count: "5 templates (PRD, PRD Brownfield, Arquitectura, Task, QA Gate)"
+  agents_count: "13 definiciones de agentes (fases DISCOVER, PLAN, BUILD, DEPLOY)"
+  workflows_count: "6 blueprints de workflow"
+  templates_count: "6 templates (PRD, PRD Brownfield, Arquitectura, Task, QA Gate, Quick Brief)"
   constitution: "Constitucion (17 Articulos + Preambulo)"
   session_mgmt: "Sistema de gestion de sesion"
   quality_gates: "Quality gates (validacion en 4 capas)"

package/framework/i18n/fr.yaml

@@ -16,9 +16,9 @@ installer:
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Sera installe:"
-  agents_count: "13 definitions d'agents (phases PLANNING, BUILD, DEPLOY)"
-  workflows_count: "5 blueprints de workflow"
-  templates_count: "5 templates (PRD, PRD Brownfield, Architecture, Task, QA Gate)"
+  agents_count: "13 definitions d'agents (phases DISCOVER, PLAN, BUILD, DEPLOY)"
+  workflows_count: "6 blueprints de workflow"
+  templates_count: "6 templates (PRD, PRD Brownfield, Architecture, Task, QA Gate, Quick Brief)"
   constitution: "Constitution (17 Articles + Preambule)"
   session_mgmt: "Systeme de gestion de session"
   quality_gates: "Quality gates (validation en 4 couches)"

package/framework/i18n/pt.yaml

@@ -16,9 +16,9 @@ installer:
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Sera instalado:"
-  agents_count: "13 definicoes de agentes (fases PLANNING, BUILD, DEPLOY)"
-  workflows_count: "5 blueprints de workflow"
-  templates_count: "5 templates (PRD, PRD Brownfield, Arquitetura, Task, QA Gate)"
+  agents_count: "13 definicoes de agentes (fases DISCOVER, PLAN, BUILD, DEPLOY)"
+  workflows_count: "6 blueprints de workflow"
+  templates_count: "6 templates (PRD, PRD Brownfield, Arquitetura, Task, QA Gate, Quick Brief)"
   constitution: "Constituicao (17 Artigos + Preambulo)"
   session_mgmt: "Sistema de gerenciamento de sessao"
   quality_gates: "Quality gates (validacao em 4 camadas)"

package/framework/intelligence/context-engine.md

@@ -25,7 +25,7 @@ The orchestrator injects context through 5 hierarchical layers:
 
 | Layer | Name | Source | When Active |
 |-------|------|--------|-------------|
-| **L0** | Constitution | `chati.dev/constitution.md` (Articles I-XVI) | ALWAYS (non-negotiable) |
+| **L0** | Constitution | `chati.dev/constitution.md` (Articles I-XVII) | ALWAYS (non-negotiable) |
 | **L1** | Mode + Global | `config.yaml` + mode governance (planning/build/deploy) | ALWAYS |
 | **L2** | Agent Scope | `chati.dev/agents/{agent}/` — mission, inputs, outputs, criteria | When agent is active |
 | **L3** | Pipeline State | `.chati/session.yaml` — pipeline position, scores, backlog | When session is active |
@@ -49,7 +49,7 @@ The orchestrator produces a structured XML block injected into agent prompts:
 ```xml
 <chati-context bracket="MODERATE">
   <constitution>
-    Articles I-XVI governing agent behavior.
+    Articles I-XVII governing agent behavior.
     Key: Self-validation required. Loop until quality threshold.
     Guided options (1,2,3). Persistent session state.
     Two-layer handoff. Language protocol. Deviation protocol.

package/framework/intelligence/decision-engine.md

@@ -16,7 +16,7 @@ The registry catalogs every artifact in the system:
 metadata:
   version: "1.0.0"
   last_updated: "2026-02-12T00:00:00Z"
-  entity_count: 48
+  entity_count: 50
   checksum_algorithm: sha256
 
 entities:
@@ -28,7 +28,7 @@ entities:
       keywords: [routing, session, deviation, handoff]
       dependencies: [constitution, session-schema, config]
       adaptability: 0.2
-  # ... (all 48 entities)
+  # ... (all 50 entities)
 ```
 
 ### Entity Fields

package/framework/manifest.json

@@ -0,0 +1,5 @@
+{
+  "createdAt": "2026-02-17T13:17:01.898Z",
+  "files": {},
+  "version": "2.1.0"
+}

package/framework/manifest.sig

@@ -0,0 +1 @@
+K7nMiR+S85Glix0PI1CJZYBWjkXyAXnT9EtiZNJgrz637qwR+sJ/XXWby38+MxU3n4z1WRyQlY2LcEwNSekFDw==

package/framework/orchestrator/chati.md

@@ -70,6 +70,51 @@ Before determining state, check if the user passed a subcommand:
 -> Resume session. Go to Step 5 (Session Resume)
 ```
 
+### Step 3b: Quick Flow Detection
+
+Before full project setup, check if this is a quick-flow candidate:
+
+```
+Quick Flow Triggers (any of these):
+  - User explicitly requests: "quick fix", "hotfix", "bug fix", "small change"
+  - Single, well-defined requirement (one sentence)
+  - Bug report with reproduction steps
+  - Configuration/environment change
+  - Small refactoring with clear scope
+
+Quick Flow Disqualifiers (any of these blocks quick-flow):
+  - New feature requiring architecture decisions
+  - Multiple interconnected requirements
+  - Greenfield project (no existing codebase)
+  - Enterprise or compliance context
+  - User explicitly requests full pipeline
+  - Scope involves > 5 files or database schema changes
+
+IF quick-flow detected (confidence >= 0.8):
+  1. Present to user:
+     "This looks like a quick task. I can use Quick Flow (fast-track):
+      Brief (quick) → Dev → QA → Deploy
+      Skips: Detail, Architect, UX, Phases, Tasks, QA-Planning
+
+      1. Use Quick Flow (Recommended for this task)
+      2. Use full pipeline instead
+      Enter number:"
+
+  2. IF user confirms quick-flow:
+     - Load workflow: chati.dev/workflows/quick-flow.yaml
+     - Set session.yaml: workflow = quick-flow
+     - Set project.state = discover
+     - Activate Brief agent in quick-extraction mode
+     - Skip to Quick Brief (see quick-flow.yaml)
+
+  3. IF user prefers full pipeline:
+     - Continue to Step 4 (New Project Setup)
+
+  4. Escalation: If during quick-flow, complexity exceeds expectations:
+     - Pause and offer switch to full pipeline
+     - See quick-flow.yaml escalation section
+```
+
 ### Step 4: New Project Setup
 
 #### 3a. Detect Project Type
@@ -96,7 +141,7 @@ If not already set in session.yaml:
 project:
   name: "{detected or asked}"
   type: greenfield | brownfield
-  state: planning
+  state: discover
 execution_mode: interactive
 current_agent: greenfield-wu | brownfield-wu
 language: "{detected}"
@@ -106,8 +151,8 @@ user_level_confidence: 0.0
 
 #### 3d. Route to First Agent
 ```
-If greenfield -> Read chati.dev/agents/planning/greenfield-wu.md -> Activate
-If brownfield -> Read chati.dev/agents/planning/brownfield-wu.md -> Activate
+If greenfield -> Read chati.dev/agents/discover/greenfield-wu.md -> Activate
+If brownfield -> Read chati.dev/agents/discover/brownfield-wu.md -> Activate
 ```
 
 ### Step 5: Session Resume
@@ -144,14 +189,14 @@ brownfield-wu -> Brief -> Architect -> Detail -> UX -> Phases -> Tasks -> QA-Pla
 ### Agent Location Map
 | Agent | File |
 |-------|------|
-| greenfield-wu | chati.dev/agents/planning/greenfield-wu.md |
-| brownfield-wu | chati.dev/agents/planning/brownfield-wu.md |
-| brief | chati.dev/agents/planning/brief.md |
-| detail | chati.dev/agents/planning/detail.md |
-| architect | chati.dev/agents/planning/architect.md |
-| ux | chati.dev/agents/planning/ux.md |
-| phases | chati.dev/agents/planning/phases.md |
-| tasks | chati.dev/agents/planning/tasks.md |
+| greenfield-wu | chati.dev/agents/discover/greenfield-wu.md |
+| brownfield-wu | chati.dev/agents/discover/brownfield-wu.md |
+| brief | chati.dev/agents/discover/brief.md |
+| detail | chati.dev/agents/plan/detail.md |
+| architect | chati.dev/agents/plan/architect.md |
+| ux | chati.dev/agents/plan/ux.md |
+| phases | chati.dev/agents/plan/phases.md |
+| tasks | chati.dev/agents/plan/tasks.md |
 | qa-planning | chati.dev/agents/quality/qa-planning.md |
 | dev | chati.dev/agents/build/dev.md |
 | qa-implementation | chati.dev/agents/quality/qa-implementation.md |
@@ -167,7 +212,8 @@ When an agent completes (score >= 95%):
   4. Orchestrator identifies next agent from pipeline
   5. Update session.yaml: current_agent = next_agent
   6. Update project.state if crossing macro-phase boundary:
-     - WU through QA-Planning = planning
+     - WU + Brief = discover
+     - Detail through QA-Planning = plan
      - Dev + QA-Implementation = build
      - Final validation = validate
      - DevOps = deploy
@@ -344,7 +390,7 @@ model_selections:
 Before any agent writes a file, the orchestrator validates the operation against the current mode:
 
 ```
-If project.state == "planning":
+If project.state == "discover" OR "plan":
   ALLOW write to: chati.dev/**, .chati/**
   BLOCK write to: everything else
   ALLOW read: everything (essential for brownfield-wu codebase analysis)
@@ -364,13 +410,13 @@ If project.state == "deploy":
 Mode transitions are AUTOMATIC based on quality gate results. The orchestrator executes the transition when the trigger condition is met.
 
 ```
-planning -> build:
+plan -> build:
   TRIGGER: qa-planning agent completes with score >= 95%
   ACTION:
     1. Update project.state = "build"
     2. Log transition in session.yaml mode_transitions:
        - timestamp: "{now}"
-         from: planning
+         from: plan
          to: build
          trigger: "qa-planning completed with score {score}%"
          type: automatic
@@ -403,12 +449,12 @@ deploy -> completed:
 ### Backward Transitions
 
 ```
-build/validate -> planning:
+build/validate -> plan:
   TRIGGER: qa-implementation classifies issue as:
     - issue_type: "spec" (requirement gap, ambiguity, conflict)
     - issue_type: "architecture" (design flaw, missing component)
   ACTION:
-    1. Update project.state = "planning"
+    1. Update project.state = "plan"
     2. Log backward transition in mode_transitions:
        - type: backward
          reason: "{QA finding description}"
@@ -550,9 +596,11 @@ Display project status dashboard:
   Phase: {state}           Mode: {execution_mode}
   Language: {language}     IDE: {ides}
 
-  PLANNING:
-    WU: {score}  Brief: {score}  Detail: {score}  Arch: {score}
-    UX: {score}  Phases: {score}  Tasks: {score}  QA-P: {score}
+  DISCOVER:
+    WU: {score}  Brief: {score}
+  PLAN:
+    Detail: {score}  Arch: {score}  UX: {score}
+    Phases: {score}  Tasks: {score}  QA-P: {score}
 
   BUILD:
     Dev: {status}  QA-Impl: {status}