chati-dev 4.5.10 → 4.5.12

package/framework/workflows/brownfield-service.yaml

@@ -1,121 +1,27 @@
-# Brownfield Service Workflow
-# Backend/API enhancements for existing projects
-
 workflow:
   id: brownfield-service
   name: Brownfield Service Enhancement
-  version: "1.0.0"
+  version: "2.0.0"
   type: brownfield
   project_types: [api-enhancement, service-modernization, backend-refactoring]
-  description: >
-    Pipeline for backend/API changes in existing projects.
-    Same as brownfield-fullstack but Architect focuses on
-    API design, data model, and service architecture.
-    UX agent runs in minimal mode (API documentation only).
+  execution_authority: rail
+  planning_focus: [api, data, security, operations]
 
 phases:
-  - phase: 0
-    name: Deep Discovery
-    category: DISCOVER
-    sequence:
-      - agent: brownfield-wu
-        action: full-discovery
-        creates: [artifacts/0-WU/wu-full-report.md]
-
+  - { phase: 0, name: Deep Discovery, category: DISCOVER, sequence: [{ agent: brownfield-wu, action: deep-discovery }, { agent: brief, action: problem-extraction }] }
   - phase: 1
-    name: Problem Definition
-    category: DISCOVER
-    sequence:
-      - agent: brief
-        action: problem-extraction
-        creates: [artifacts/1-Brief/brief-report.md]
-
-  - phase: 2
-    name: Architecture & Specification
-    category: PLAN
-    sequence:
-      - agent: architect
-        action: assess-architecture
-        creates: [artifacts/3-Architecture/architecture.md]
-        notes: "Focus on API design, data model, service patterns"
-      - agent: detail
-        action: create-prd
-        creates: [artifacts/2-PRD/prd.md]
-        template: brownfield-prd-tmpl.yaml
-
-  - phase: 3
-    name: Execution Planning
+    name: Planning
     category: PLAN
     sequence:
-      - agent: phases
-        action: create-roadmap
-        creates: [artifacts/5-Phases/phases.md]
-      - agent: tasks
-        action: create-tasks
-        creates: [artifacts/6-Tasks/tasks.md]
-
-  - phase: 4
-    name: Planning Quality Gate (Planning Team)
-    category: PLAN
-    sequence:
-      - agent: qa-planning
-        action: validate-traceability
-        creates: [artifacts/7-QA-Planning/qa-planning-report.md]
-        notes: >
-          Runs inside Planning Team (Article XXI), not as a standalone step.
-          Activates after Detail and Architect complete their tasks.
-          Score synced to session.yaml by orchestrator on team dissolution.
-
-  - phase: 5
-    name: Implementation
-    category: BUILD
-    sequence:
-      - agent: dev
-        action: implement-tasks
-      - agent: qa-implementation
-        action: validate-code
-        creates: [artifacts/9-QA-Implementation/qa-implementation-report.md]
-
-  - phase: 6
-    name: Deployment
-    category: DEPLOY
-    sequence:
-      - agent: devops
-        action: deploy
-        creates: [artifacts/10-Deploy/deploy-report.md]
+      - { agent: architect, action: service-design }
+      - { agent: detail, action: create-prd }
+      - { agent: ux, action: api-consumer-experience }
+      - { agent: phases, action: create-roadmap }
+      - { agent: tasks, action: seal-task-graph }
+      - { agent: qa-planning, action: validate-planning }
+  - { phase: 2, name: RAIL Execution, category: RAIL, runtime: project-local-rail }
+  - { phase: 3, name: Release Lane, category: RELEASE, requires: [rail_complete, independent_review_approved, explicit_human_authorization] }
 
 transitions:
-  discover_to_plan:
-    trigger: "brief.status == completed"
-    type: automatic
-    action: "Update project.state = plan"
-  plan_to_build:
-    trigger: "qa-planning.score >= 95"
-    type: automatic
-    action: "Update project.state = build"
-  build_to_validate:
-    trigger: "dev.status == completed"
-    type: automatic
-    action: "Update project.state = validate"
-  validate_to_preview:
-    trigger: "qa-implementation.status == approved"
-    type: automatic
-    action: "Launch user preview (orchestrator-preview task)"
-    notes: "User must approve preview before advancing to deploy"
-  preview_to_deploy:
-    trigger: "user_preview.decision in [approve_keep, approve_kill]"
-    type: manual
-    action: "Update project.state = deploy"
-    notes: "User explicitly approves the preview"
-  deploy_to_completed:
-    trigger: "devops.status == completed"
-    type: automatic
-    action: "Update project.state = completed"
-  backward_to_plan:
-    trigger: "qa-implementation.issue_type in [spec, architecture]"
-    type: backward
-    action: "Update project.state = plan, route to responsible agent"
-  backward_to_discover:
-    trigger: "qa-implementation.issue_type in [requirements, scope]"
-    type: backward
-    action: "Update project.state = discover, route to brief or wu agent"
+  plan_to_rail: { trigger: "qa-planning.score >= 95 && tasks.handoff == sealed", target: rail }
+  rail_to_release: { trigger: "rail.all_tasks_approved == true", target: release }

package/framework/workflows/brownfield-ui.yaml

@@ -1,127 +1,27 @@
-# Brownfield UI Workflow
-# Frontend/UI changes for existing projects
-
 workflow:
   id: brownfield-ui
   name: Brownfield UI Enhancement
-  version: "1.0.0"
+  version: "2.0.0"
   type: brownfield
   project_types: [ui-modernization, frontend-migration, component-library, design-system-update]
-  description: >
-    Pipeline for frontend/UI changes in existing projects.
-    Same as brownfield-fullstack but UX agent takes a larger role,
-    including Design System audit and component inventory.
-    Architect focuses on frontend architecture and state management.
+  execution_authority: rail
+  planning_focus: [design-system, accessibility, responsive-behavior, visual-regression]
 
 phases:
-  - phase: 0
-    name: Deep Discovery
-    category: DISCOVER
-    sequence:
-      - agent: brownfield-wu
-        action: full-discovery
-        creates: [artifacts/0-WU/wu-full-report.md]
-        notes: "UX scout call gets extra attention for component audit"
-
+  - { phase: 0, name: Deep Discovery, category: DISCOVER, sequence: [{ agent: brownfield-wu, action: deep-discovery }, { agent: brief, action: problem-extraction }] }
   - phase: 1
-    name: Problem Definition
-    category: DISCOVER
-    sequence:
-      - agent: brief
-        action: problem-extraction
-        creates: [artifacts/1-Brief/brief-report.md]
-
-  - phase: 2
-    name: Architecture & Experience
-    category: PLAN
-    sequence:
-      - agent: architect
-        action: assess-architecture
-        creates: [artifacts/3-Architecture/architecture.md]
-        notes: "Focus on frontend architecture, state management, component patterns"
-      - agent: detail
-        action: create-prd
-        creates: [artifacts/2-PRD/prd.md]
-        template: brownfield-prd-tmpl.yaml
-      - agent: ux
-        action: define-experience
-        creates: [artifacts/4-UX/ux-specification.md]
-        notes: "Full Design System audit + new token definitions"
-
-  - phase: 3
-    name: Execution Planning
+    name: Planning
     category: PLAN
     sequence:
-      - agent: phases
-        action: create-roadmap
-        creates: [artifacts/5-Phases/phases.md]
-      - agent: tasks
-        action: create-tasks
-        creates: [artifacts/6-Tasks/tasks.md]
-
-  - phase: 4
-    name: Planning Quality Gate (Planning Team)
-    category: PLAN
-    sequence:
-      - agent: qa-planning
-        action: validate-traceability
-        creates: [artifacts/7-QA-Planning/qa-planning-report.md]
-        notes: >
-          Runs inside Planning Team (Article XXI), not as a standalone step.
-          Activates after Architect, Detail, and UX complete their tasks.
-          Score synced to session.yaml by orchestrator on team dissolution.
-
-  - phase: 5
-    name: Implementation
-    category: BUILD
-    sequence:
-      - agent: dev
-        action: implement-tasks
-        notes: "Design System token enforcement is critical for UI work"
-      - agent: qa-implementation
-        action: validate-code
-        creates: [artifacts/9-QA-Implementation/qa-implementation-report.md]
-
-  - phase: 6
-    name: Deployment
-    category: DEPLOY
-    sequence:
-      - agent: devops
-        action: deploy
-        creates: [artifacts/10-Deploy/deploy-report.md]
+      - { agent: architect, action: frontend-design }
+      - { agent: detail, action: create-prd }
+      - { agent: ux, action: design-system-and-flows }
+      - { agent: phases, action: create-roadmap }
+      - { agent: tasks, action: seal-task-graph }
+      - { agent: qa-planning, action: validate-planning }
+  - { phase: 2, name: RAIL Execution, category: RAIL, runtime: project-local-rail }
+  - { phase: 3, name: Release Lane, category: RELEASE, requires: [rail_complete, independent_review_approved, explicit_human_authorization] }
 
 transitions:
-  discover_to_plan:
-    trigger: "brief.status == completed"
-    type: automatic
-    action: "Update project.state = plan"
-  plan_to_build:
-    trigger: "qa-planning.score >= 95"
-    type: automatic
-    action: "Update project.state = build"
-  build_to_validate:
-    trigger: "dev.status == completed"
-    type: automatic
-    action: "Update project.state = validate"
-  validate_to_preview:
-    trigger: "qa-implementation.status == approved"
-    type: automatic
-    action: "Launch user preview (orchestrator-preview task)"
-    notes: "User must approve preview before advancing to deploy"
-  preview_to_deploy:
-    trigger: "user_preview.decision in [approve_keep, approve_kill]"
-    type: manual
-    action: "Update project.state = deploy"
-    notes: "User explicitly approves the preview"
-  deploy_to_completed:
-    trigger: "devops.status == completed"
-    type: automatic
-    action: "Update project.state = completed"
-  backward_to_plan:
-    trigger: "qa-implementation.issue_type in [spec, architecture]"
-    type: backward
-    action: "Update project.state = plan, route to responsible agent"
-  backward_to_discover:
-    trigger: "qa-implementation.issue_type in [requirements, scope]"
-    type: backward
-    action: "Update project.state = discover, route to brief or wu agent"
+  plan_to_rail: { trigger: "qa-planning.score >= 95 && tasks.handoff == sealed", target: rail }
+  rail_to_release: { trigger: "rail.all_tasks_approved == true", target: release }

package/framework/workflows/greenfield-fullstack.yaml

@@ -1,146 +1,33 @@
-# Greenfield Fullstack Workflow
-# Handles: web apps, SaaS, MVP, enterprise, prototypes
-# The single unified pipeline for all greenfield project types
-
 workflow:
   id: greenfield-fullstack
   name: Greenfield Fullstack Development
-  version: "1.0.0"
+  version: "2.0.0"
   type: greenfield
   project_types: [web-app, saas, enterprise, prototype, mvp, api, mobile-web]
-  description: >
-    Complete development pipeline for new projects. The Architect agent
-    adapts scope based on project needs (full-stack, service-only, or UI-only)
-    rather than requiring separate workflow definitions.
+  execution_authority: rail
 
 phases:
   - phase: 0
     name: Discovery
     category: DISCOVER
     sequence:
-      - agent: greenfield-wu
-        action: operational-discovery
-        creates: [artifacts/0-WU/wu-operational-report.md]
-        notes: "Operational context only (no codebase to analyze)"
-
+      - { agent: greenfield-wu, action: operational-discovery, creates: [artifacts/0-WU/wu-operational-report.md] }
+      - { agent: brief, action: problem-extraction, creates: [artifacts/1-Brief/brief-report.md] }
   - phase: 1
-    name: Problem Definition
-    category: DISCOVER
-    sequence:
-      - agent: brief
-        action: problem-extraction
-        creates: [artifacts/1-Brief/brief-report.md]
-        notes: "5-phase extraction process"
-
-  - phase: 2
-    name: Product Specification
-    category: PLAN
-    sequence:
-      - agent: detail
-        action: create-prd
-        creates: [artifacts/2-PRD/prd.md]
-        template: prd-tmpl.yaml
-        notes: "Detail comes BEFORE Architect in greenfield"
-
-  - phase: 3
-    name: Technical Design
-    category: PLAN
-    sequence:
-      - agent: architect
-        action: design-architecture
-        creates: [artifacts/3-Architecture/architecture.md]
-        template: fullstack-architecture-tmpl.yaml
-        notes: "Tech stack selection, data model, deployment strategy"
-      - agent: architect
-        action: dep-audit
-        creates: [artifacts/3-Architecture/dep-audit.yaml]
-        notes: "Verify dependency versions, vulnerabilities, and compatibility before implementation"
-      - agent: ux
-        action: define-experience
-        creates: [artifacts/4-UX/ux-specification.md]
-        notes: "UX follows Architect (needs to know the stack)"
-
-  - phase: 4
-    name: Execution Planning
-    category: PLAN
-    sequence:
-      - agent: phases
-        action: create-roadmap
-        creates: [artifacts/5-Phases/phases.md]
-        notes: "MVP-first phase breakdown"
-      - agent: tasks
-        action: create-tasks
-        creates: [artifacts/6-Tasks/tasks.md]
-        template: task-tmpl.yaml
-        notes: "Atomic tasks with Given-When-Then criteria"
-
-  - phase: 5
-    name: Planning Quality Gate (Planning Team)
+    name: Planning
     category: PLAN
     sequence:
-      - agent: qa-planning
-        action: validate-traceability
-        creates: [artifacts/7-QA-Planning/qa-planning-report.md]
-        template: qa-gate-tmpl.yaml
-        notes: >
-          Runs inside Planning Team (Article XXI), not as a standalone step.
-          Activates after Detail, Architect, and UX complete their tasks.
-          Must score >= 95% to proceed to BUILD. Score synced to session.yaml by orchestrator on team dissolution.
-
-  - phase: 6
-    name: Implementation
-    category: BUILD
-    sequence:
-      - agent: dev
-        action: implement-tasks
-        notes: "Interactive or autonomous (Ralph Wiggum) mode"
-      - agent: qa-implementation
-        action: validate-code
-        creates: [artifacts/9-QA-Implementation/qa-implementation-report.md]
-        template: qa-gate-tmpl.yaml
-        notes: "Tests + SAST + code review. Must pass to deploy"
-
-  - phase: 7
-    name: Deployment
-    category: DEPLOY
-    sequence:
-      - agent: devops
-        action: deploy
-        creates: [artifacts/10-Deploy/deploy-report.md]
-        notes: "Git operations, deployment, documentation"
+      - { agent: detail, action: create-prd, creates: [artifacts/2-PRD/prd.md] }
+      - { agent: architect, action: design-architecture, creates: [artifacts/3-Architecture/architecture.md] }
+      - { agent: ux, action: define-experience, creates: [artifacts/4-UX/ux-specification.md] }
+      - { agent: phases, action: create-roadmap, creates: [artifacts/5-Phases/phases.md] }
+      - { agent: tasks, action: seal-task-graph, creates: [artifacts/6-Tasks/tasks.md] }
+      - { agent: qa-planning, action: validate-planning, creates: [artifacts/7-QA-Planning/qa-planning-report.md] }
+  - { phase: 2, name: RAIL Execution, category: RAIL, runtime: project-local-rail, contract: .chati/v2/rail/handoffs }
+  - { phase: 3, name: Release Lane, category: RELEASE, requires: [rail_complete, independent_review_approved, explicit_human_authorization] }
 
 transitions:
-  discover_to_plan:
-    trigger: "brief.status == completed"
-    type: automatic
-    action: "Update project.state = plan"
-  plan_to_build:
-    trigger: "qa-planning.score >= 95"
-    type: automatic
-    action: "Update project.state = build"
-  build_to_validate:
-    trigger: "dev.status == completed"
-    type: automatic
-    action: "Update project.state = validate"
-  validate_to_preview:
-    trigger: "qa-implementation.status == approved"
-    type: automatic
-    action: "Launch user preview (orchestrator-preview task)"
-    notes: "User must approve preview before advancing to deploy"
-  preview_to_deploy:
-    trigger: "user_preview.decision in [approve_keep, approve_kill]"
-    type: manual
-    action: "Update project.state = deploy"
-    notes: "User explicitly approves the preview"
-  deploy_to_completed:
-    trigger: "devops.status == completed"
-    type: automatic
-    action: "Update project.state = completed"
-  backward_to_plan:
-    trigger: "qa-implementation.issue_type in [spec, architecture]"
-    type: backward
-    action: "Update project.state = plan, route to responsible agent"
-  backward_to_discover:
-    trigger: "qa-implementation.issue_type in [requirements, scope]"
-    type: backward
-    action: "Update project.state = discover, route to brief or wu agent"
+  discover_to_plan: { trigger: "brief.status == completed", target: plan }
+  plan_to_rail: { trigger: "qa-planning.score >= 95 && tasks.handoff == sealed", target: rail }
+  rail_to_release: { trigger: "rail.all_tasks_approved == true", target: release }
+  release_to_completed: { trigger: "release.receipt.status == completed", target: completed }

package/framework/workflows/quick-flow.yaml

@@ -1,127 +1,36 @@
-# Quick Flow Workflow
-# Fast-track pipeline for simple tasks: bug fixes, small features, config changes
-# Skips full DISCOVER/PLAN phases when complexity is low
-
 workflow:
   id: quick-flow
-  name: Quick Flow — Fast Track Development
-  version: "1.0.0"
+  name: Quick Flow
+  version: "2.0.0"
   type: any
   project_types: [bug-fix, small-feature, config-change, hotfix, refactor]
-  description: >
-    Condensed pipeline for tasks that don't need full discovery/planning.
-    Used when the orchestrator detects low complexity: clear requirements,
-    known codebase, small scope. Skips Detail, Architect, UX, Phases, Tasks,
-    and QA-Planning. Goes straight from Brief (quick) to Dev.
+  execution_authority: rail
+  description: Condensed planning with the same sealed RAIL and Release contracts as the full workflow.
 
 detection:
-  # Orchestrator uses these signals to auto-detect quick-flow eligibility
-  triggers:
-    - "User explicitly requests quick fix or hotfix"
-    - "Single, well-defined requirement (can be stated in one sentence)"
-    - "Bug report with reproduction steps"
-    - "Configuration or environment change"
-    - "Small refactoring with clear scope"
-    - "User says 'just do it' or 'quick fix' or similar urgency signals"
-    - "Simple, fun, or experimental project (single-purpose tool, game, prototype)"
-    - "Single-page utility or learning project with no production requirements"
-  disqualifiers:
-    - "New feature requiring architecture decisions (multiple services, database design, auth system)"
-    - "Multiple interconnected requirements (>3 distinct features)"
-    - "Complex greenfield project (enterprise, multi-service, compliance requirements)"
-    - "Enterprise or compliance context"
-    - "User explicitly requests full pipeline"
-    - "Scope involves more than 5 files"
-    - "Requires database schema changes"
-    - "Requires new API endpoints (>2)"
-
   confidence_threshold: 0.8
   user_confirmation: true
+  disqualifiers:
+    - architecture decision required
+    - more than five files expected
+    - database schema change
+    - more than two new API endpoints
 
 phases:
   - phase: 0
-    name: Quick Brief
-    category: DISCOVER
-    sequence:
-      - agent: brief
-        action: quick-extraction
-        creates: [artifacts/1-Brief/quick-brief.md]
-        notes: >
-          Condensed extraction: single-pass, no 5-phase process.
-          Capture: what, why, constraints, acceptance criteria.
-          Duration: 2-5 min max.
-        template: quick-brief-tmpl.yaml
-        config:
-          max_rounds: 2
-          require_approval: true
-
-  - phase: 1
-    name: Implementation
-    category: BUILD
-    sequence:
-      - agent: dev
-        action: implement-tasks
-        notes: >
-          Dev works directly from Quick Brief (no PRD, no architecture doc).
-          Scope is tight: fix the bug, add the small feature, make the change.
-          Self-critique checklist still applies.
-
-  - phase: 2
-    name: Validation
-    category: BUILD
-    sequence:
-      - agent: qa-implementation
-        action: validate-code
-        creates: [artifacts/9-QA-Implementation/qa-implementation-report.md]
-        notes: >
-          Full QA-Implementation validation still applies (no shortcuts on quality).
-          Adversarial review still mandatory.
-          Tests must pass, SAST must be clean.
-        config:
-          adversarial_review: true
-          minimum_findings: 3
-
-  - phase: 3
-    name: Deployment
-    category: DEPLOY
+    name: Compact Planning
+    category: PLAN
     sequence:
-      - agent: devops
-        action: deploy
-        creates: [artifacts/10-Deploy/deploy-report.md]
-        notes: "Standard deployment process"
+      - { agent: brief, action: quick-extraction, creates: [artifacts/1-Brief/quick-brief.md] }
+      - { agent: tasks, action: compact-sealed-task-graph, creates: [artifacts/6-Tasks/tasks.md] }
+      - { agent: qa-planning, action: validate-compact-plan, creates: [artifacts/7-QA-Planning/qa-planning-report.md] }
+  - { phase: 1, name: RAIL Execution, category: RAIL, runtime: project-local-rail }
+  - { phase: 2, name: Release Lane, category: RELEASE, requires: [rail_complete, independent_review_approved, explicit_human_authorization] }
 
 transitions:
-  quick_brief_to_build:
-    trigger: "brief.status == completed"
-    type: automatic
-    action: "Skip full PLAN phase, go directly to BUILD"
-    notes: "No Detail, Architect, UX, Phases, Tasks, or QA-Planning"
-  build_to_validate:
-    trigger: "dev.status == completed"
-    type: automatic
-    action: "Update project.state = validate"
-  validate_to_deploy:
-    trigger: "qa-implementation.status == approved"
-    type: automatic
-    action: "Update project.state = deploy"
-    notes: "User preview skipped for quick-flow (scope too small)"
-  deploy_to_completed:
-    trigger: "devops.status == completed"
-    type: automatic
-    action: "Update project.state = completed"
+  plan_to_rail: { trigger: "qa-planning.score >= 95 && tasks.handoff == sealed", target: rail }
+  rail_to_release: { trigger: "rail.all_tasks_approved == true", target: release }
 
 escalation:
-  # If at any point the quick-flow feels insufficient, escalate to full pipeline
-  triggers:
-    - "Dev discovers the change is more complex than expected"
-    - "QA-Implementation finds architectural issues"
-    - "Scope creep detected (>5 files, new APIs, schema changes)"
-    - "Dev agent requests escalation"
-  action: >
-    Pause quick-flow, notify user:
-    "This task is more complex than initially estimated.
-    Recommend switching to full pipeline for proper planning.
-    Options:
-    1. Switch to full pipeline (Recommended)
-    2. Continue with quick-flow (document risk)
-    3. Abort and reassess"
+  triggers: [scope-expansion, architecture-decision, planning-gate-failure]
+  action: restart with the appropriate full planning workflow