@accelerationguy/accel 1.0.0

package/modules/drive/src/templates/milestone-archive.md

@@ -0,0 +1,236 @@
+# Milestone Archive Template
+
+Template for milestone archives at `.drive/milestones/v{VERSION}-{NAME}.md`.
+
+**Purpose:** Preserve complete phase details for completed milestones. Created by complete-milestone workflow when a milestone ships.
+
+---
+
+## File Template
+
+```markdown
+# Milestone v{{VERSION}}: {{MILESTONE_NAME}}
+
+**Status:** ✅ SHIPPED {{DATE}}
+**Phases:** {{PHASE_START}}-{{PHASE_END}}
+**Total Plans:** {{PLAN_COUNT}}
+
+## Overview
+
+{{MILESTONE_DESCRIPTION}}
+
+## Phases
+
+{{#PHASES}}
+### Phase {{PHASE_NUM}}: {{PHASE_NAME}}
+
+**Goal:** {{PHASE_GOAL}}
+**Depends on:** {{DEPENDS_ON}}
+**Plans:** {{PLAN_COUNT}} completed
+
+Plans:
+- [x] {{PHASE_NUM}}-01: {{PLAN_DESCRIPTION}}
+- [x] {{PHASE_NUM}}-02: {{PLAN_DESCRIPTION}}
+[... all plans ...]
+
+**Details:**
+{{PHASE_SCOPE_FROM_ROADMAP}}
+{{/PHASES}}
+
+{{#DECIMAL_PHASES}}
+### Phase {{PHASE_NUM}}: {{PHASE_NAME}} [INSERTED]
+
+**Goal:** {{PHASE_GOAL}}
+**Depends on:** {{DEPENDS_ON}}
+**Reason:** {{INSERTION_REASON}}
+
+Plans:
+- [x] {{PHASE_NUM}}-01: {{PLAN_DESCRIPTION}}
+{{/DECIMAL_PHASES}}
+
+---
+
+## Milestone Summary
+
+**Decimal Phases:**
+{{#HAS_DECIMAL_PHASES}}
+- Phase {{PHASE_NUM}}: {{PHASE_NAME}} (inserted after Phase {{PARENT_PHASE}} for {{REASON}})
+{{/HAS_DECIMAL_PHASES}}
+{{^HAS_DECIMAL_PHASES}}
+None
+{{/HAS_DECIMAL_PHASES}}
+
+**Key Decisions:**
+{{#DECISIONS}}
+- {{DECISION}} (Rationale: {{RATIONALE}})
+{{/DECISIONS}}
+
+**Issues Resolved:**
+{{#ISSUES_RESOLVED}}
+- {{ISSUE}}
+{{/ISSUES_RESOLVED}}
+
+**Issues Deferred:**
+{{#ISSUES_DEFERRED}}
+- {{ISSUE}} (deferred to: {{DEFERRED_TO}})
+{{/ISSUES_DEFERRED}}
+
+**Technical Debt Incurred:**
+{{#TECH_DEBT}}
+- {{DEBT_ITEM}} (address in: {{WHEN}})
+{{/TECH_DEBT}}
+
+---
+
+*For current project status, see [ROADMAP.md](../ROADMAP.md) and [STATE.md](../STATE.md)*
+```
+
+---
+
+## Placeholder Reference
+
+| Placeholder | Source | Example |
+|-------------|--------|---------|
+| `{{VERSION}}` | Milestone version | `0.2` |
+| `{{MILESTONE_NAME}}` | Milestone theme | `Session Continuity` |
+| `{{DATE}}` | Ship date | `2026-01-28` |
+| `{{PHASE_START}}` | First phase number | `7` |
+| `{{PHASE_END}}` | Last phase number | `8.7` |
+| `{{PLAN_COUNT}}` | Total plans | `5` |
+| `{{MILESTONE_DESCRIPTION}}` | One-sentence summary | From MILESTONES.md entry |
+| `{{PHASE_NUM}}` | Phase number | `7` or `8.5` |
+| `{{PHASE_NAME}}` | Phase name | `Session Handoff` |
+| `{{PHASE_GOAL}}` | Phase goal | From ROADMAP.md |
+| `{{DEPENDS_ON}}` | Phase dependencies | `Phase 6` |
+| `{{PLAN_DESCRIPTION}}` | Plan brief | From ROADMAP.md or SUMMARY |
+| `{{PHASE_SCOPE_FROM_ROADMAP}}` | Scope bullets | From ROADMAP.md |
+| `{{INSERTION_REASON}}` | Why decimal inserted | `Urgent quality fix` |
+| `{{DECISION}}` | Decision made | From STATE.md Decisions |
+| `{{RATIONALE}}` | Why decided | From STATE.md |
+
+---
+
+## Filename Convention
+
+**Pattern:** `.drive/milestones/v{VERSION}-{NAME}.md`
+
+**Rules:**
+- VERSION: Numeric version without `v` prefix in filename → `0.2`, `1.0`, `2.0`
+- NAME: Kebab-case milestone theme → `session-continuity`, `core-loop`, `mvp`
+
+**Examples:**
+- `v0.1-core-loop.md`
+- `v0.2-session-continuity.md`
+- `v1.0-mvp.md`
+- `v2.0-redesign.md`
+
+---
+
+## Usage Guidelines
+
+### When to create archives
+
+Archives are created by the `complete-milestone` workflow when:
+- All phases in a milestone are complete
+- Milestone is officially shipped
+- Before planning begins on next milestone
+
+### How to fill template
+
+The workflow populates from:
+1. **ROADMAP.md** — Phase details, goals, scope, plan lists
+2. **STATE.md** — Decisions from Accumulated Context section
+3. **MILESTONES.md** — Overview description
+4. **SUMMARY files** — Plan completion details
+
+### After archiving
+
+1. Update ROADMAP.md — Collapse milestone in `<details>` tag
+2. Update STATE.md — Clear completed phase context
+3. Continue numbering — Never restart phase numbers at 01
+
+---
+
+## Example
+
+```markdown
+# Milestone v0.2: Session Continuity
+
+**Status:** ✅ SHIPPED 2026-01-28
+**Phases:** 7-8.7
+**Total Plans:** 5
+
+## Overview
+
+Pause/resume workflow with handoff files and enhanced STATE.md session tracking.
+
+## Phases
+
+### Phase 7: Session Handoff
+
+**Goal:** Create pause/resume workflow for session breaks
+**Depends on:** Phase 6
+**Plans:** 1 completed
+
+Plans:
+- [x] 07-01: Handoff file generation and resume workflow
+
+**Details:**
+- HANDOFF-*.md template for context capture
+- Resume command for context restoration
+- Session continuity section in STATE.md
+
+### Phase 8.5: Quality Extensions [INSERTED]
+
+**Goal:** Code quality tooling integration
+**Depends on:** Phase 8
+**Reason:** Discovered need during Phase 8 review
+
+Plans:
+- [x] 08.5-01: SonarQube integration (optional)
+
+### Phase 8.6: Codebase CLAUDE.md [INSERTED]
+
+**Goal:** Project-level Claude Code configuration
+**Depends on:** Phase 8.5
+**Reason:** Improve agent context for Drive projects
+
+Plans:
+- [x] 08.6-01: CLAUDE.md template for codebase guidance
+
+### Phase 8.7: SonarQube Integration [INSERTED]
+
+**Goal:** Automated code quality checks
+**Depends on:** Phase 8.6
+**Reason:** Complete quality tooling suite
+
+Plans:
+- [x] 08.7-01: SonarQube project setup and config
+
+---
+
+## Milestone Summary
+
+**Decimal Phases:**
+- Phase 8.5: Quality Extensions (inserted after Phase 8 for code quality tooling)
+- Phase 8.6: Codebase CLAUDE.md (inserted after Phase 8.5 for agent context)
+- Phase 8.7: SonarQube Integration (inserted after Phase 8.6 for quality checks)
+
+**Key Decisions:**
+- SonarQube is optional integration (Rationale: Not all projects need code quality tooling)
+- Minimize subagents for dev work (Rationale: ~70% quality, high token cost)
+
+**Issues Resolved:**
+- Session context lost after /clear
+- No way to pause and resume work
+
+**Issues Deferred:**
+- None
+
+**Technical Debt Incurred:**
+- None
+
+---
+
+*For current project status, see [ROADMAP.md](../ROADMAP.md) and [STATE.md](../STATE.md)*
+```

package/modules/drive/src/templates/milestone-context.md

@@ -0,0 +1,190 @@
+# Milestone Context Template
+
+Template for `.drive/MILESTONE-CONTEXT.md` — temporary handoff from discuss-milestone to create-milestone.
+
+**Purpose:** Persist milestone discussion context across `/clear` boundaries. This is a handoff artifact, not permanent documentation.
+
+---
+
+## File Template
+
+```markdown
+# Milestone Context
+
+**Generated:** {{DATE}}
+**Status:** Ready for /drive:create-milestone
+
+## Features to Build
+
+[Features identified during discussion — the substance of this milestone]
+
+- **{{FEATURE_1}}**: {{DESCRIPTION}}
+- **{{FEATURE_2}}**: {{DESCRIPTION}}
+- **{{FEATURE_3}}**: {{DESCRIPTION}}
+
+## Scope
+
+**Suggested name:** v{{VERSION}} {{THEME_NAME}}
+**Estimated phases:** {{PHASE_COUNT}}
+**Focus:** {{ONE_SENTENCE_THEME}}
+
+## Phase Mapping
+
+[How features map to phases — rough breakdown]
+
+| Phase | Focus | Features |
+|-------|-------|----------|
+| {{NEXT_PHASE}} | {{FOCUS}} | {{FEATURES}} |
+| {{NEXT_PHASE+1}} | {{FOCUS}} | {{FEATURES}} |
+| {{NEXT_PHASE+2}} | {{FOCUS}} | {{FEATURES}} |
+
+## Constraints
+
+[Any constraints or boundaries identified during discussion]
+
+- {{CONSTRAINT_1}}
+- {{CONSTRAINT_2}}
+
+## Additional Context
+
+[Anything else captured during discussion that informs the milestone]
+
+{{NOTES}}
+
+---
+
+*This file is temporary. It will be deleted after /drive:create-milestone creates the milestone.*
+*Do NOT commit this file to version control.*
+```
+
+---
+
+## Lifecycle
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│                    MILESTONE CONTEXT LIFECYCLE                   │
+├─────────────────────────────────────────────────────────────────┤
+│                                                                  │
+│  1. /drive:discuss-milestone                                      │
+│     └─> Explores features, scope, constraints                    │
+│     └─> Creates MILESTONE-CONTEXT.md at end                      │
+│                                                                  │
+│  2. /clear (safe now)                                            │
+│     └─> Context persisted in file                                │
+│     └─> Session can be cleared                                   │
+│                                                                  │
+│  3. /drive:create-milestone                                       │
+│     └─> Reads MILESTONE-CONTEXT.md                               │
+│     └─> Uses context to populate ROADMAP.md                      │
+│     └─> Deletes MILESTONE-CONTEXT.md after success               │
+│                                                                  │
+│  Result: Clean handoff across session boundaries                 │
+│                                                                  │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+### Key Points
+
+1. **Created by:** `discuss-milestone` command at end of discussion
+2. **Consumed by:** `create-milestone` command
+3. **Deleted after:** Milestone successfully created
+4. **Not committed:** Exclude from version control (temporary artifact)
+
+---
+
+## Content Guidelines
+
+### What to Include
+
+| Section | Include | Purpose |
+|---------|---------|---------|
+| Features | User-facing capabilities to build | Defines milestone substance |
+| Scope | Version number, theme, phase count | Frames the work |
+| Phase Mapping | Rough feature-to-phase breakdown | Guides create-milestone |
+| Constraints | Technical/business limits | Prevents scope creep |
+| Additional Context | Discussion notes, decisions | Preserves conversation |
+
+### What NOT to Include
+
+| Avoid | Why |
+|-------|-----|
+| Technical implementation details | That comes during phase planning |
+| Detailed phase specifications | create-milestone handles that |
+| Code architecture decisions | Research phase work |
+| Exhaustive task lists | PLAN.md level of detail |
+
+**Key principle:** This captures the *what* and *why*, not the *how*.
+
+---
+
+## Integration with Drive Workflow
+
+### Before discuss-milestone
+
+```
+STATE.md shows: Previous milestone complete
+ROADMAP.md shows: Phases complete, next milestone undefined
+```
+
+### After discuss-milestone
+
+```
+MILESTONE-CONTEXT.md: Created with discussion output
+STATE.md: Updated to note milestone discussion complete
+```
+
+### After create-milestone
+
+```
+MILESTONE-CONTEXT.md: Deleted
+ROADMAP.md: Updated with new milestone and phases
+STATE.md: Updated with new phase position
+```
+
+---
+
+## Example
+
+```markdown
+# Milestone Context
+
+**Generated:** 2026-01-29
+**Status:** Ready for /drive:create-milestone
+
+## Features to Build
+
+- **Milestone lifecycle commands**: Create, complete, and discuss milestones
+- **Roadmap modification commands**: Add and remove phases dynamically
+- **Milestone templates**: Entry format, archive format, context handoff
+
+## Scope
+
+**Suggested name:** v0.3 Roadmap & Milestone Management
+**Estimated phases:** 3
+**Focus:** Complete milestone management tooling for Drive framework
+
+## Phase Mapping
+
+| Phase | Focus | Features |
+|-------|-------|----------|
+| 9 | Templates | MILESTONES.md, archive, context templates |
+| 10 | Workflows | discuss-milestone, complete-milestone, add-phase |
+| 11 | Commands | CLI commands for milestone operations |
+
+## Constraints
+
+- Templates first, then workflows, then commands (dependency order)
+- Keep commands simple — complex logic in workflows
+
+## Additional Context
+
+- Discussed need for milestone grouping in ROADMAP.md
+- User preference for tabular layouts over bullet lists
+- Consider optional SonarQube scan before milestone completion
+
+---
+
+*This file is temporary. It will be deleted after /drive:create-milestone creates the milestone.*
+*Do NOT commit this file to version control.*
+```

package/modules/drive/src/templates/paul-json.md

@@ -0,0 +1,147 @@
+# drive.json Template
+
+Template for `.drive/drive.json` - machine-readable satellite manifest for external system discovery.
+
+**Purpose:** Provides a standardized signal file that workspace management systems (Momentum) can scan for, detect, and register Drive-managed projects.
+
+---
+
+## File Template
+
+```json
+{
+  "name": "{project_name}",
+  "version": "{milestone_version}",
+  "milestone": {
+    "name": "{milestone_name}",
+    "version": "{milestone_version}",
+    "status": "not_started | in_progress | complete"
+  },
+  "phase": {
+    "number": 0,
+    "name": "{phase_name}",
+    "status": "not_started | planning | in_progress | complete"
+  },
+  "loop": {
+    "plan": null,
+    "position": "IDLE | PLAN | APPLY | UNIFY"
+  },
+  "timestamps": {
+    "created_at": "{ISO 8601}",
+    "updated_at": "{ISO 8601}"
+  },
+  "satellite": {
+    "groom": true
+  }
+}
+```
+
+---
+
+## Field Reference
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `name` | string | Project name (from init or directory name) |
+| `version` | string | Current milestone version (e.g., "0.1.0") |
+| `milestone.name` | string | Current milestone name (e.g., "v0.1 Initial Release") |
+| `milestone.version` | string | Milestone version tag |
+| `milestone.status` | enum | `not_started`, `in_progress`, `complete` |
+| `phase.number` | number | Current phase number (0 = no phase yet) |
+| `phase.name` | string | Current phase name ("None" if no phase) |
+| `phase.status` | enum | `not_started`, `planning`, `in_progress`, `complete` |
+| `loop.plan` | string\|null | Current plan ID (e.g., "12-01") or null if idle |
+| `loop.position` | enum | `IDLE`, `PLAN`, `APPLY`, `UNIFY` |
+| `timestamps.created_at` | string | ISO 8601 timestamp of drive.json creation |
+| `timestamps.updated_at` | string | ISO 8601 timestamp of last update |
+| `satellite.groom` | boolean | Whether Momentum groom should health-check this project (default: true) |
+
+---
+
+## Field Update Triggers
+
+| Workflow | Fields Updated |
+|----------|---------------|
+| `init-project` | All fields (initial creation) |
+| `plan-phase` | `loop.plan`, `loop.position` → "PLAN", `timestamps.updated_at` |
+| `apply-phase` | `loop.position` → "APPLY", `timestamps.updated_at` |
+| `unify-phase` | `phase.*`, `loop.position` → "IDLE", `loop.plan` → null, `timestamps.updated_at` |
+| `create-milestone` | `milestone.*`, `version`, `phase.*`, `loop.*` → IDLE, `timestamps.updated_at` |
+| `complete-milestone` | `milestone.status` → "complete", `timestamps.updated_at` |
+
+**Note:** Not all workflows currently implement sync. v1.1 implements sync in: init-project, unify-phase, create-milestone, complete-milestone. Plan-phase and apply-phase sync are deferred (unify catches up).
+
+---
+
+## Example: Newly Initialized Project
+
+```json
+{
+  "name": "my-app",
+  "version": "0.0.0",
+  "milestone": {
+    "name": "None",
+    "version": "0.0.0",
+    "status": "not_started"
+  },
+  "phase": {
+    "number": 0,
+    "name": "None",
+    "status": "not_started"
+  },
+  "loop": {
+    "plan": null,
+    "position": "IDLE"
+  },
+  "timestamps": {
+    "created_at": "2026-03-17T14:00:00-05:00",
+    "updated_at": "2026-03-17T14:00:00-05:00"
+  },
+  "satellite": {
+    "groom": true
+  }
+}
+```
+
+## Example: Mid-Development Project
+
+```json
+{
+  "name": "casegate",
+  "version": "0.2.0",
+  "milestone": {
+    "name": "v0.2 API Layer",
+    "version": "0.2.0",
+    "status": "in_progress"
+  },
+  "phase": {
+    "number": 5,
+    "name": "Authentication",
+    "status": "in_progress"
+  },
+  "loop": {
+    "plan": null,
+    "position": "IDLE"
+  },
+  "timestamps": {
+    "created_at": "2026-02-01T09:00:00-06:00",
+    "updated_at": "2026-03-15T16:30:00-05:00"
+  },
+  "satellite": {
+    "groom": true
+  }
+}
+```
+
+---
+
+## Design Notes
+
+- **Machine-readable only.** drive.json is for external systems, not humans. Humans read STATE.md.
+- **Always tooling-generated.** Created by init, synced by workflows. Never hand-edited.
+- **Backward compatible.** Workflows check for drive.json existence before syncing. Pre-v1.1 projects without drive.json are silently skipped.
+- **Satellite config.** The `satellite` object is for consumer-side settings. Momentum reads `satellite.groom` to decide whether to include this project in health checks.
+
+---
+
+*Template added: v1.1 Satellite Manifest*

package/modules/drive/src/vector-config/PAUL

@@ -0,0 +1,26 @@
+# CARL Domain: Drive (Plan-Apply-Unify Loop)
+# AI-assisted development workflow. Activates when .paul/ exists in project.
+Drive_STATE=active
+Drive_ALWAYS_ON=false
+
+# Rule 0: Scope
+Drive_RULE_0=Drive governs structured AI development via Plan-Apply-Unify loop. Requires .paul/ directory.
+
+# MUST (critical)
+Drive_RULE_1=LOAD BEFORE EXECUTE: Before ANY /drive:* command, MUST Read the command file (~/.claude/accel-drive/src/commands/{name}.md) AND its execution_context workflow file. NEVER execute Drive commands from memory or inference - always load the actual files first. If files cannot be loaded, STOP and inform user.
+Drive_RULE_2=No implementation code without approved PLAN.md. Research/exploration OK. Violation = stop, request approval.
+Drive_RULE_3=Every APPLY must be followed by UNIFY. UNIFY reconciles plan vs actual, updates STATE.md, logs decisions.
+Drive_RULE_4=Respect PLAN.md "Boundaries" / "DO NOT CHANGE" sections. Stop and confirm before modifying protected items.
+Drive_RULE_5=When blocked: document in STATE.md Blockers, notify human, await approval before workarounds.
+Drive_RULE_6=At phase transition: VERIFY state consistency (STATE.md, PROJECT.md, ROADMAP.md aligned). Blocking error if misaligned. Re-read full files, check all fields.
+
+# SHOULD (quality)
+Drive_RULE_7=Tasks require verification criteria: <verify>[proof of success]</verify>. No verify = cannot complete.
+Drive_RULE_8=Log all APPLY deviations: what, why, downstream impact. Audit trail for UNIFY.
+Drive_RULE_9=Use BDD acceptance criteria: Given [precondition] / When [action] / Then [outcome].
+
+# MAY (patterns)
+Drive_RULE_10=Size tasks for single session (~50% context). Split larger tasks during planning.
+Drive_RULE_11=One commit per phase at transition. Format: {type}({phase}): {description}. WIP commits optional at pause. Version alignment required at milestone.
+Drive_RULE_12=Urgent work uses decimal phases (2.1, 2.2). Integers = planned, decimals = interruptions.
+

package/modules/drive/src/vector-config/PAUL.manifest

@@ -0,0 +1,11 @@
+# ============================================================================
+# PAUL - Plan-Apply-Unify Loop (AI-assisted development workflow)
+# ============================================================================
+# Installation:
+#   1. Copy the PAUL domain file to ~/.accel/vector/PAUL (or project .accel/vector/PAUL)
+#   2. Append this block to your ~/.accel/vector/manifest (or project .accel/vector/manifest)
+# ============================================================================
+PAUL_STATE=active
+PAUL_ALWAYS_ON=false
+PAUL_RECALL=paul,plan phase,apply phase,unify phase,PLAN.md,STATE.md,development workflow,vibe coding,ai development,planning framework,.paul/
+# PAUL_EXCLUDE=