eai-cli 0.0.0-bootstrap.0

package/resources/gofer/templates/journey/base-journey.md

@@ -0,0 +1,95 @@
+---
+id: {{journey-id}}
+name: {{journey-name}}
+featureId: {{feature-id}}
+status: draft
+created: {{created-date}}
+modified: {{modified-date}}
+---
+
+# Customer Journey: {{journey-name}}
+
+## Overview
+
+{{journey-description}}
+
+---
+
+## Actors
+
+| ID | Name | Type | Role |
+|----|------|------|------|
+{{#each actors}}
+| {{id}} | {{name}} | {{type}} | {{role}} |
+{{/each}}
+
+### Actor Descriptions
+
+{{#each actors}}
+#### {{name}} ({{type}})
+
+{{role}}
+
+{{/each}}
+
+---
+
+## Journey Steps
+
+{{#each steps}}
+### Step {{stepNumber}}: {{action}}
+
+**Actor**: {{actorId}}
+
+{{action}}
+
+{{#if outcome}}
+**Expected Outcome**: {{outcome}}
+{{/if}}
+
+{{#if notes}}
+**Notes**: {{notes}}
+{{/if}}
+
+{{/each}}
+
+---
+
+## Journey Diagram
+
+```mermaid
+sequenceDiagram
+    {{#each actors}}
+    participant {{id}} as {{name}}
+    {{/each}}
+
+    {{#each steps}}
+    Note over {{actorId}}: Step {{stepNumber}}
+    {{actorId}}->>{{actorId}}: {{action}}
+    {{/each}}
+```
+
+---
+
+## Touchpoints
+
+| ID | Type | Description | Actors | Steps |
+|----|------|-------------|--------|-------|
+{{#each touchpoints}}
+| {{id}} | {{type}} | {{description}} | {{actorIds}} | {{stepNumbers}} |
+{{/each}}
+
+---
+
+## Confirmation Status
+
+- [ ] Actors confirmed by stakeholder
+- [ ] Steps confirmed by stakeholder
+- [ ] Touchpoints identified
+- [ ] Journey diagram reviewed
+
+---
+
+## Notes
+
+_Add any additional notes or considerations here._

package/resources/gofer/templates/journey/industry-variants.yaml

@@ -0,0 +1,277 @@
+# Industry Variant Templates for Journey Generation
+#
+# These templates define industry-specific patterns and innovations
+# that can be applied when generating journey variants.
+#
+# @see spec.md FR-017 through FR-020
+
+industries:
+  retail:
+    name: Retail
+    keywords:
+      - shopping
+      - cart
+      - checkout
+      - inventory
+      - product catalog
+    patterns:
+      - Abandoned cart recovery
+      - Personalized recommendations
+      - Loyalty programs
+      - Omnichannel experience
+      - Real-time inventory sync
+    innovations:
+      - AI-powered virtual try-on
+      - Voice commerce integration
+      - AR product visualization
+      - Predictive inventory management
+      - Hyper-personalization via ML
+    touchpoints:
+      - Mobile app
+      - Website
+      - In-store kiosk
+      - Customer service chat
+      - Email/SMS notifications
+
+  healthcare:
+    name: Healthcare
+    keywords:
+      - patient
+      - appointment
+      - medical
+      - health records
+      - diagnosis
+    patterns:
+      - Patient portal access
+      - Appointment scheduling
+      - Secure messaging
+      - Prescription management
+      - Telehealth visits
+    innovations:
+      - AI symptom checker
+      - Remote patient monitoring
+      - Predictive health analytics
+      - Natural language clinical notes
+      - Drug interaction AI
+    touchpoints:
+      - Patient portal
+      - Mobile health app
+      - Wearable devices
+      - Video consultation
+      - Pharmacy integration
+
+  finance:
+    name: Finance
+    keywords:
+      - account
+      - transaction
+      - payment
+      - investment
+      - loan
+    patterns:
+      - Multi-factor authentication
+      - Real-time fraud detection
+      - Budget tracking
+      - Automated savings
+      - Investment portfolio management
+    innovations:
+      - AI-powered financial advisor
+      - Predictive spending insights
+      - Voice-activated banking
+      - Blockchain verification
+      - Biometric authentication
+    touchpoints:
+      - Mobile banking app
+      - Web portal
+      - ATM
+      - Customer service
+      - Third-party fintech integrations
+
+  education:
+    name: Education
+    keywords:
+      - student
+      - course
+      - learning
+      - assessment
+      - curriculum
+    patterns:
+      - Learning management system
+      - Progress tracking
+      - Peer collaboration
+      - Assignment submission
+      - Grade reporting
+    innovations:
+      - Adaptive learning AI
+      - AI tutoring assistants
+      - VR/AR learning experiences
+      - Automated essay feedback
+      - Learning path optimization
+    touchpoints:
+      - LMS platform
+      - Mobile learning app
+      - Video conferencing
+      - Discussion forums
+      - Parent portal
+
+  hospitality:
+    name: Hospitality
+    keywords:
+      - booking
+      - reservation
+      - guest
+      - room
+      - amenity
+    patterns:
+      - Online booking
+      - Digital check-in/out
+      - Room service ordering
+      - Loyalty rewards
+      - Guest preferences
+    innovations:
+      - AI concierge service
+      - Smart room controls
+      - Facial recognition check-in
+      - Predictive maintenance
+      - Dynamic pricing AI
+    touchpoints:
+      - Booking website
+      - Mobile app
+      - In-room tablet
+      - Front desk kiosk
+      - Voice assistant
+
+  logistics:
+    name: Logistics
+    keywords:
+      - shipment
+      - tracking
+      - delivery
+      - warehouse
+      - supply chain
+    patterns:
+      - Real-time tracking
+      - Route optimization
+      - Inventory management
+      - Returns processing
+      - Proof of delivery
+    innovations:
+      - AI demand forecasting
+      - Autonomous delivery vehicles
+      - Drone delivery
+      - Digital twin warehouses
+      - Predictive maintenance for fleet
+    touchpoints:
+      - Tracking portal
+      - Driver mobile app
+      - Warehouse management system
+      - Customer notifications
+      - API integrations
+
+  manufacturing:
+    name: Manufacturing
+    keywords:
+      - production
+      - quality
+      - assembly
+      - equipment
+      - maintenance
+    patterns:
+      - Production scheduling
+      - Quality control
+      - Equipment monitoring
+      - Supply chain visibility
+      - Work order management
+    innovations:
+      - Predictive maintenance AI
+      - Digital twin simulation
+      - Computer vision QC
+      - Cobots (collaborative robots)
+      - Generative design AI
+    touchpoints:
+      - Shop floor terminals
+      - SCADA systems
+      - Mobile maintenance app
+      - ERP integration
+      - Supplier portal
+
+  legal:
+    name: Legal
+    keywords:
+      - case
+      - document
+      - contract
+      - client
+      - billing
+    patterns:
+      - Case management
+      - Document version control
+      - Time tracking
+      - Client portal
+      - E-discovery
+    innovations:
+      - AI contract analysis
+      - Legal research AI
+      - Predictive case outcomes
+      - Automated document assembly
+      - NLP for document review
+    touchpoints:
+      - Case management system
+      - Client portal
+      - Document management
+      - Billing system
+      - Court filing integration
+
+  real_estate:
+    name: Real Estate
+    keywords:
+      - property
+      - listing
+      - showing
+      - offer
+      - closing
+    patterns:
+      - Property search
+      - Virtual tours
+      - Offer management
+      - Document signing
+      - Closing coordination
+    innovations:
+      - AI property valuation
+      - VR property tours
+      - Predictive market analysis
+      - Automated lead scoring
+      - Smart contract closings
+    touchpoints:
+      - Property portal
+      - Mobile app
+      - Virtual tour platform
+      - E-signature system
+      - MLS integration
+
+  entertainment:
+    name: Entertainment
+    keywords:
+      - content
+      - streaming
+      - ticket
+      - event
+      - subscription
+    patterns:
+      - Content discovery
+      - Personalized recommendations
+      - Social sharing
+      - Subscription management
+      - Event ticketing
+    innovations:
+      - AI content curation
+      - Interactive streaming
+      - AR/VR experiences
+      - AI-generated content
+      - Dynamic ad personalization
+    touchpoints:
+      - Streaming app
+      - Smart TV app
+      - Mobile app
+      - Social media integration
+      - Ticketing platform

package/resources/gofer/templates/loop-contract-template.json

@@ -0,0 +1,68 @@
+{
+  "schemaVersion": 1,
+  "loopId": "{{featureId}}",
+  "profile": "standard",
+  "objective": "Keep feature delivery aligned with current goals, approved scope, implementation evidence, and validation gates.",
+  "entryStage": "0_gofer_start",
+  "maxIterations": 3,
+  "budget": {
+    "maxWallClockMinutes": null,
+    "maxModelSpendUsd": null,
+    "stopOnBudgetWarning": true
+  },
+  "modelTiers": {
+    "simple": "Use the repo model policy simple tier.",
+    "medium": "Use the repo model policy medium tier.",
+    "hard": "Use the repo model policy hard tier.",
+    "arbiter": "Use the repo model policy arbiter tier only for release-critical or contradictory results."
+  },
+  "evalCommands": [
+    {
+      "id": "loop-audit",
+      "stage": "5_implement",
+      "command": "node .specify/scripts/node/gofer-loop-audit.mjs --feature-dir {FEATURE_DIR} --stage 5_implement --json --strict",
+      "purpose": "Verify bounded loop contract and implementation-loop ledger evidence before marking implementation complete.",
+      "runWhen": "before and after implementation loops"
+    },
+    {
+      "id": "closed-loop-audit",
+      "stage": "6_validate",
+      "command": "node .specify/scripts/node/gofer-closed-loop-audit.mjs --feature-dir {FEATURE_DIR} --json --strict",
+      "purpose": "Verify goal, traceability, drift, and validation freshness before final scoring.",
+      "runWhen": "before validation scoring"
+    }
+  ],
+  "successCriteria": [
+    {
+      "id": "SC-LOOP-001",
+      "description": "Each implementation or validation loop records iteration evidence in loop-ledger.jsonl.",
+      "evidence": ["loop-ledger.jsonl"]
+    },
+    {
+      "id": "SC-LOOP-002",
+      "description": "All configured evaluation commands pass before Gofer reports the feature complete.",
+      "evidence": ["validation-report.md", "loop-audit-report.md"]
+    }
+  ],
+  "stopConditions": [
+    {
+      "id": "STOP-001",
+      "description": "Stop when all success criteria have evidence and no blocking loop findings remain.",
+      "status": "active"
+    },
+    {
+      "id": "STOP-002",
+      "description": "Escalate instead of looping forever when the same failing action reaches maxIterations.",
+      "status": "active"
+    }
+  ],
+  "humanEscalation": {
+    "maxFailedIterations": 3,
+    "owner": "feature owner",
+    "escalateWhen": [
+      "the same failure repeats at maxIterations",
+      "a security, privacy, data, or release-critical gate remains red",
+      "budget or context-window limits would hide evidence"
+    ]
+  }
+}

package/resources/gofer/templates/plan-template.md

@@ -0,0 +1,215 @@
+# Implementation Plan: [FEATURE]
+
+**Branch**: `[###-feature-name]` | **Date**: [DATE] | **Spec**: [link]
+**Input**: Feature specification from
+`.specify/specs/[###-feature-name]/spec.md`
+
+**Note**: This template is filled in by `/3_gofer_plan` (or legacy
+`/3_gofer_plan`). Recommended: Use `/0_gofer_start` to auto-chain the entire
+pipeline.
+
+## Executive Summary
+
+[Three to five plain-language bullets covering what will be built, the chosen
+architecture, why it fits EAI Platform/Azure, the largest delivery risk, and the
+next decision or validation gate.]
+
+## Technical Context
+
+<!--
+  ACTION REQUIRED: Replace the content in this section with the technical details
+  for the project. The structure here is presented in advisory capacity to guide
+  the iteration process.
+-->
+
+**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS
+CLARIFICATION]  
+**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]  
+**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]  
+**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]  
+**Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
+**App Stack Policy**: [For app delivery: EAI Platform including app template
+first, Azure second, all other technology only as an approved exception]  
+**Project Type**: [single/web/mobile - determines source structure]  
+**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps
+or NEEDS CLARIFICATION]  
+**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory,
+offline-capable or NEEDS CLARIFICATION]  
+**Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS
+CLARIFICATION] **Brand Profile**: [`.specify/memory/brand-profile.json` path,
+`/8_gofer_branding` needed, or N/A]
+
+## Constitution Check
+
+_GATE: Must pass before Phase 0 research. Re-check after Phase 1 design._
+
+[Gates determined based on constitution file]
+
+## Project Structure
+
+### Documentation (this feature)
+
+```text
+.specify/specs/[###-feature]/
+├── goal-ledger.json      # Machine-readable goals, metrics, and re-loop triggers
+├── spec.md              # Feature specification (/2_gofer_specify)
+├── research.md          # Codebase research (/1_gofer_research)
+├── journeys/
+│   └── base-journey.md  # AI-augmented app journey when app delivery applies
+├── ui-preview-brief.md  # App-delivery preview brief when app delivery applies
+├── ui-review-log.md     # App-delivery preview evidence and iteration log
+├── ui-approval.md       # App-delivery approval gate record
+├── service-fit-matrix.md # App-delivery capability selection evidence
+├── plan.md              # This file (/3_gofer_plan)
+├── data-model.md        # Data model design (/3_gofer_plan)
+├── quickstart.md        # Quick start guide (/3_gofer_plan)
+├── contracts/           # API contracts (/3_gofer_plan)
+├── tasks.md             # Task breakdown (/4_gofer_tasks)
+├── traceability.md      # Spec -> task -> code -> test coverage (/4,/6)
+├── validation-report.md # Objective/rubric quality gate (/6_gofer_validate)
+├── goal-rebaseline-report.md # Closed-loop drift report (/6 or CI)
+└── issues.md            # GitHub issues (/4_gofer_tasks)
+```
+
+### Source Code (repository root)
+
+<!--
+  ACTION REQUIRED: Replace the placeholder tree below with the concrete layout
+  for this feature. Delete unused options and expand the chosen structure with
+  real paths (e.g., apps/admin, packages/something). The delivered plan must
+  not include Option labels.
+-->
+
+```text
+# [REMOVE IF UNUSED] Option 1: Single project (DEFAULT)
+src/
+├── models/
+├── services/
+├── cli/
+└── lib/
+
+tests/
+├── contract/
+├── integration/
+└── unit/
+
+# [REMOVE IF UNUSED] Option 2: Web application (when "frontend" + "backend" detected)
+backend/
+├── src/
+│   ├── models/
+│   ├── services/
+│   └── api/
+└── tests/
+
+frontend/
+├── src/
+│   ├── components/
+│   ├── pages/
+│   └── services/
+└── tests/
+
+# [REMOVE IF UNUSED] Option 3: Mobile + API (when "iOS/Android" detected)
+api/
+└── [same as backend above]
+
+ios/ or android/
+└── [platform-specific structure: feature modules, UI flows, platform tests]
+```
+
+**Structure Decision**: [Document the selected structure and reference the real
+directories captured above]
+
+## AI-Augmented App Journey
+
+For application delivery, the plan must preserve the four-step-or-fewer
+AI-augmented journey from `journeys/base-journey.md`. For non-app work, state
+why no app journey is required.
+
+| Step | Business Goal | AI Assistance | Architecture Implication | Validation |
+| ---- | ------------- | ------------- | ------------------------ | ---------- |
+| 1    | [goal]        | [assist]      | [component/API/data]     | [test]     |
+| 2    | [goal]        | [assist]      | [component/API/data]     | [test]     |
+| 3    | [goal]        | [assist]      | [component/API/data]     | [test]     |
+| 4    | [goal]        | [assist]      | [component/API/data]     | [test]     |
+
+## Branded Deliverables Plan
+
+For stakeholder-facing app delivery, describe how approved brand choices affect
+documents, diagrams, decks, UI preview notes, headers, footers, confidentiality
+labels, and logo usage. If `/8_gofer_branding` has not run and branding matters,
+add it as a prerequisite before `/7a_stakeholder_comms`.
+
+## Visual Documentation Plan
+
+Use visuals to explain the plan, not to decorate it. Prefer Mermaid for
+Markdown-native diagrams, Marp for stakeholder slide decks, D2 for compact
+process/system sketches when Mermaid becomes noisy, and Structurizr/C4 when the
+architecture needs model-as-code consistency.
+
+| Visual             | Tool / format                | Audience               | Question answered                      | Evidence                      |
+| ------------------ | ---------------------------- | ---------------------- | -------------------------------------- | ----------------------------- |
+| Context boundary   | Mermaid C4 or Structurizr/C4 | CTO / delivery         | What is inside and outside the system? | `visuals/c4-context.md`       |
+| Runtime containers | Mermaid C4 or Structurizr/C4 | CTO / engineers        | What deployable parts exist?           | `visuals/c4-container.md`     |
+| User/process flow  | Mermaid sequence/state or D2 | Business / delivery    | What happens in what order?            | [path]                        |
+| Stakeholder slides | Marp                         | Executives / reviewers | What is the simple review story?       | `presentation.marp.md` or N/A |
+
+## UI Preview And Service-Fit Gate
+
+For application delivery, the plan must lock the approved preview and service
+selection before downstream implementation is treated as complete. For non-app
+work, state why this gate is not applicable.
+
+| Gate              | Required Artifact                              | Validation                                                                                               |
+| ----------------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
+| Preview scope     | `ui-preview-brief.md`                          | [how the MVP preview scope is defined]                                                                   |
+| Platform describe | `eai --describe`                               | [CLI version, tenant/platform capability notes, package lane]                                            |
+| Block catalog     | `eai blocks list` / `eai blocks describe <id>` | [selected IDs, Storybook story IDs, theme override points, coupling status, and custom-block exceptions] |
+| Resource bindings | `eai resources schema`                         | [object fields/actions/events feeding selected blocks]                                                   |
+| Preview evidence  | `ui-review-log.md`                             | [screenshot, local render, or Playwright-style proof]                                                    |
+| UI approval       | `ui-approval.md`                               | [who approves and when]                                                                                  |
+| Service fit       | `service-fit-matrix.md`                        | [how accessible vs purchasable vs unavailable is proved]                                                 |
+
+## AI-Readable Blocks Bridge
+
+| Workstream                 | Required Decision                                            | Plan Reference                            |
+| -------------------------- | ------------------------------------------------------------ | ----------------------------------------- |
+| Package profile            | [external / internal / hybrid]                               | [where tasks will enforce profile choice] |
+| Package lane               | [public package / internal app / hybrid adapter / app-local] | [package/export path]                     |
+| Block porting              | [reuse / port / custom-block exception]                      | [block IDs and story IDs]                 |
+| source-platform decoupling | [coupled / decoupled / adapter boundary]                     | [eai resources schema or adapter path]    |
+| Public-readiness           | [required / deferred / not applicable]                       | [consumer-facing checks]                  |
+
+## Dual-State Delivery Discipline
+
+Track capabilities that move from mock-safe behavior to hybrid or live
+integration. This table should match `goal-ledger.json`.
+
+| Capability | Current State (mock/hybrid/live) | Target State | Promotion Criteria | Validation Owner |
+| ---------- | -------------------------------- | ------------ | ------------------ | ---------------- |
+| [name]     | [mock]                           | [live]       | [evidence]         | [owner]          |
+
+## Complexity Tracking
+
+> **Fill ONLY if Constitution Check has violations that must be justified**
+
+| Violation                  | Why Needed         | Simpler Alternative Rejected Because |
+| -------------------------- | ------------------ | ------------------------------------ |
+| [e.g., 4th project]        | [current need]     | [why 3 projects insufficient]        |
+| [e.g., Repository pattern] | [specific problem] | [why direct DB access insufficient]  |
+
+## EnterpriseAI Profile Metadata
+
+> Populated by default for EnterpriseAI runs. Standard-profile runs leave this
+> section empty only when the user explicitly opts out.
+
+- **EAI CLI Version Pin**: `[major.minor, e.g. 2.0]` — the installed `eai`
+  version is recorded here at plan generation time. Deployment tasks reference
+  this pin to prevent drift between local and CI environments.
+- **EAI App Template Reference**: `[eai-app-template tag or SHA]`
+- **Deployment Repo Reference**: `[deployment-repo tag or SHA]`
+- **Package Profile Choice**: `[external | internal | hybrid]`
+- **Package Lane**:
+  `[public-package | internal-app | hybrid-adapter | app-local]`
+- **Coupling Status**:
+  `[source-platform-coupled | source-platform-decoupled | hybrid-adapter]`
+- **Public-Readiness Target**: `[required | deferred | not-applicable]`