project-iris 0.0.13 → 0.0.14

package/dist/iris_bundle/frameworks/iris-core/templates/construction/bolt-types/spike-bolt.md

@@ -1,240 +0,0 @@
-# Bolt Type: Spike (Research)
-
-## Mandatory Output Rules (READ FIRST)
-
-- 🚫 **NEVER** use ASCII tables for options - they break at different terminal widths
-- ✅ **ALWAYS** use numbered list format: `N - **Option**: Description`
-- ✅ **ALWAYS** use status indicators: ✅ (done) ⏳ (current) [ ] (pending) 🚫 (blocked)
-
-## Success Metrics
-
-- ✅ Activities presented as numbered lists (not tables)
-- ✅ Stage progress shown with status indicators
-- ✅ Human checkpoints clearly marked
-
-## Failure Modes
-
-- ❌ Using ASCII table for activities
-- ❌ Auto-advancing without human confirmation
-- ❌ Exceeding time-box without approval
-
----
-
-## Metadata
-
-```yaml
-bolt_type: spike-bolt
-name: Spike Bolt
-description: Research and proof-of-concept for unknown areas
-version: 1.0.0
-suitable_for:
-  - Technical research
-  - Proof of concept
-  - Evaluating technologies
-  - Risk mitigation
-stages_count: 2
-```
-
----
-
-## Overview
-
-This bolt type is for research and proof-of-concept work when there are unknowns that need investigation before committing to implementation.
-
-**Best For**:
-
-- Evaluating new technologies
-- Proof of concept for risky approaches
-- Research before estimation
-- Validating assumptions
-- Learning and experimentation
-
-**Important**: Spike bolts produce **knowledge**, not production code. The output is documentation, not deployable software.
-
----
-
-## Stages
-
-### Stage 1: explore
-
-**Objective**: Investigate the unknown area and document findings
-
-**Duration**: Time-boxed (hours to days, strictly limited)
-
-**Activities**:
-
-1 - **Define research questions**: List what needs to be answered
-2 - **Investigate options**: Research and document alternatives
-3 - **Build throwaway prototypes**: Create proof-of-concept code
-4 - **Test assumptions**: Validate or invalidate beliefs
-5 - **Identify risks**: Document potential issues
-6 - **Evaluate trade-offs**: Compare options
-
-**Artifact**: `spike-exploration.md`
-**Location**: Path defined by `schema.units` in `.iris/aidlc/memory/memory-bank.yaml`
-*(Default: `{intents-path}/{intent}/units/{unit}/spike-exploration.md`)*
-
-**Template Structure**:
-
-```markdown
----
-stage: explore
-bolt: {bolt-id}
-created: {YYYY-MM-DDTHH:MM:SSZ}
-time_box: {hours}
----
-
-## Spike Exploration: {topic}
-
-### Research Questions
-1. {question 1}
-2. {question 2}
-
-### Options Investigated
-
-- **{Option}**: {Description} - Pros: {list} - Cons: {list}
-
-### Prototype Notes
-{What was built, what was learned}
-
-### Assumptions Tested
-
-- **{Assumption}**: Valid: {yes/no} - Evidence: {details}
-
-### Risks Identified
-
-- **{Risk}**: Likelihood: {H/M/L} - Impact: {H/M/L} - Mitigation: {approach}
-```
-
-**Completion Criteria**:
-
-- [ ] All research questions addressed
-- [ ] Options evaluated
-- [ ] Prototypes built (if applicable)
-- [ ] Assumptions validated or invalidated
-- [ ] Risks documented
-
-**⛔ HUMAN Checkpoint**: Present exploration summary and **STOP**. Wait for user to confirm before proceeding to Stage 2.
-
----
-
-### Stage 2: document
-
-**Objective**: Consolidate findings into actionable recommendations
-
-**Duration**: Hours (typically 1-2 hours)
-
-**Activities**:
-
-1 - **Summarize findings**: Create high-level summary
-2 - **Make recommendations**: Propose best approach
-3 - **Estimate implementation**: Provide effort estimates
-4 - **Identify next bolts**: Suggest follow-up work
-5 - **Present to team**: Share knowledge
-
-**Artifact**: `spike-report.md`
-**Location**: Path defined by `schema.units` in `.iris/aidlc/memory/memory-bank.yaml`
-*(Default: `{intents-path}/{intent}/units/{unit}/spike-report.md`)*
-
-**Template Structure**:
-
-```markdown
----
-stage: document
-bolt: {bolt-id}
-created: {YYYY-MM-DDTHH:MM:SSZ}
----
-
-## Spike Report: {topic}
-
-### Summary
-{High-level summary of what was learned}
-
-### Key Findings
-1. {finding 1}
-2. {finding 2}
-
-### Recommendation
-**Recommended Approach**: {option}
-
-**Rationale**: {why this option}
-
-### Implementation Estimate
-
-- **{Component}**: Effort: {estimate} - Confidence: {H/M/L}
-
-### Risks to Monitor
-
-- **{Risk}**: Mitigation: {strategy}
-
-### Suggested Next Steps
-1. {Create bolt for...}
-2. {Update requirements with...}
-3. {Add story for...}
-
-### Artifacts to Archive
-- [ ] Prototype code (if reusable): {location}
-- [ ] Research notes: {location}
-```
-
-**Completion Criteria**:
-
-- [ ] Findings documented
-- [ ] Clear recommendation made
-- [ ] Estimates provided
-- [ ] Next steps identified
-- [ ] Knowledge shared with team
-
-**⛔ HUMAN Checkpoint**: Present spike report and **STOP**. Wait for user to confirm bolt completion.
-
----
-
-## Stage Execution
-
-### Sequence
-
-```text
-explore → document
-```
-
-### Time-Boxing
-
-Spikes **MUST** be time-boxed:
-
-- Define maximum duration upfront
-- Stop when time-box expires
-- Document whatever was learned
-- Don't extend without explicit approval
-
-### State Tracking
-
-```yaml
----
-current_stage: document
-stages_completed:
-  - name: explore
-    completed: 2024-12-05T16:00:00Z
-    time_spent: 4h
-status: in-progress
-time_box: 8h
-time_remaining: 4h
----
-```
-
----
-
-## Important Notes
-
-### Spike Output
-
-- **NOT** production code
-- **NOT** deployable software
-- **IS** knowledge and documentation
-- **IS** input for real construction bolts
-
-### After a Spike
-
-1. Review findings with team
-2. Update requirements if needed
-3. Create real construction bolts
-4. Archive or delete prototype code

package/dist/lib.js

@@ -1,96 +0,0 @@
-import fs from "node:fs";
-import path from "node:path";
-import { spawn } from "node:child_process";
-export function repoRoot() {
-    return process.cwd();
-}
-export function ensureDir(p) {
-    fs.mkdirSync(p, { recursive: true });
-}
-export function copyDir(src, dst) {
-    ensureDir(dst);
-    for (const entry of fs.readdirSync(src, { withFileTypes: true })) {
-        const s = path.join(src, entry.name);
-        const d = path.join(dst, entry.name);
-        if (entry.isDirectory())
-            copyDir(s, d);
-        else if (entry.isSymbolicLink()) {
-            const link = fs.readlinkSync(s);
-            try {
-                fs.symlinkSync(link, d);
-            }
-            catch { /* ignore */ }
-        }
-        else {
-            ensureDir(path.dirname(d));
-            fs.copyFileSync(s, d);
-        }
-    }
-}
-export function removeDir(p) {
-    if (!fs.existsSync(p))
-        return;
-    fs.rmSync(p, { recursive: true, force: true });
-}
-export function writeFile(p, content) {
-    ensureDir(path.dirname(p));
-    fs.writeFileSync(p, content, "utf8");
-}
-/**
- * Sanitize a folder name to be a valid npm package name
- */
-export function sanitizeFolderName(name) {
-    return name
-        .toLowerCase()
-        .replace(/[^a-z0-9-_]/g, "-")
-        .replace(/^-+|-+$/g, "")
-        .replace(/-+/g, "-")
-        || "my-project";
-}
-/**
- * Check if npm is available in PATH
- */
-export function hasNpm() {
-    try {
-        const result = spawn("npm", ["--version"], { stdio: "ignore" });
-        return true;
-    }
-    catch {
-        return false;
-    }
-}
-/**
- * Spawn a command asynchronously and return the result
- */
-export function spawnAsync(command, args, cwd) {
-    return new Promise((resolve) => {
-        const proc = spawn(command, args, {
-            cwd,
-            stdio: ["inherit", "pipe", "pipe"],
-            shell: true
-        });
-        let stdout = "";
-        let stderr = "";
-        if (proc.stdout) {
-            proc.stdout.on("data", (data) => {
-                const text = data.toString();
-                stdout += text;
-                process.stdout.write(text);
-            });
-        }
-        if (proc.stderr) {
-            proc.stderr.on("data", (data) => {
-                const text = data.toString();
-                stderr += text;
-                process.stderr.write(text);
-            });
-        }
-        proc.on("close", (code) => {
-            resolve({ code: code ?? 0, stdout, stderr });
-        });
-        proc.on("error", (err) => {
-            stderr += err.message;
-            resolve({ code: 1, stdout, stderr });
-        });
-    });
-}

package/dist/templates/construction/bolt-template.md

@@ -1,226 +0,0 @@
-# Bolt Instance Template
-
-## Mandatory Output Rules (READ FIRST)
-
-- 🚫 **NEVER** use ASCII tables for options - they break at different terminal widths
-- ✅ **ALWAYS** use numbered list format: `N - **Option**: Description`
-- ✅ **ALWAYS** use status indicators: ✅ (done) ⏳ (current) [ ] (pending) 🚫 (blocked)
-
----
-
-Use this template when creating new bolt instances during bolt planning.
-
-**Directory Structure**: Each bolt gets its own directory containing the bolt metadata and stage artifacts:
-
-```text
-memory-bank/bolts/{bolt-id}/
-├── bolt.md                      # Bolt instance metadata (this template)
-├── ddd-01-domain-model.md       # Stage 1 artifact (created during execution)
-├── ddd-02-technical-design.md   # Stage 2 artifact (created during execution)
-└── ddd-03-test-report.md        # Stage 4 artifact (created during execution)
-```
-
----
-
-## Frontmatter
-
-```yaml
----
-id: bolt-{unit}-{sequence}
-unit: {UUU}-{unit-name}
-intent: {NNN}-{intent-name}
-type: ddd-construction-bolt
-status: planned
-stories:
-  - story-1
-  - story-2
-created: {YYYY-MM-DDTHH:MM:SSZ}
-started: null
-completed: null
-current_stage: null
-stages_completed: []
-
-# Bolt Dependencies (for execution ordering)
-requires_bolts: []          # Bolts that must complete before this bolt can start
-enables_bolts: []           # Bolts that become unblocked when this bolt completes
-requires_units: []          # Units that must exist (usually empty)
-blocks: false               # Computed: true if any requires_bolts are incomplete
-
-# Complexity Assessment (aggregate of included stories)
-complexity:
-  avg_complexity: 2        # 1=Low, 2=Medium, 3=High
-  avg_uncertainty: 1       # 1=Low, 2=Medium, 3=High
-  max_dependencies: 2      # Highest dependency score among stories
-  testing_scope: 2         # 1=Unit, 2=Integration, 3=E2E
----
-```
-
----
-
-## Required Frontmatter Fields (VALIDATION CHECKLIST)
-
-Before creating a bolt, verify ALL required fields are present:
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| `id` | **YES** | Bolt identifier (format: `{BBB}-{unit-name}`) |
-| `unit` | **YES** | Parent unit ID |
-| `intent` | **YES** | Parent intent ID |
-| `type` | **YES** | Bolt type (`ddd-construction-bolt` or `simple-construction-bolt`) |
-| `status` | **YES** | Current status (`planned`, `in-progress`, `completed`, `blocked`) |
-| `stories` | **YES** | Array of story IDs included in this bolt |
-| `created` | **YES** | Creation timestamp |
-| `requires_bolts` | **YES** | Array of bolt IDs this depends on (can be empty `[]`) |
-| `enables_bolts` | **YES** | Array of bolt IDs waiting on this (can be empty `[]`) |
-| `complexity` | **YES** | Complexity assessment block |
-
-**If any required field is missing, the bolt is INVALID.**
-
----
-
-## Content
-
-```markdown
-# Bolt: {bolt-id}
-
-## Overview
-
-{Brief description of what this bolt will accomplish}
-
-## Objective
-
-{Specific goal of this bolt tied to the stories it covers}
-
-## Stories Included
-
-- **{story-1}**: {title} (Must)
-- **{story-2}**: {title} (Should)
-
-## Bolt Type
-
-**Type**: {type name}
-**Definition**: `.iris/aidlc/templates/construction/bolt-types/{type}.md`
-
-## Stages
-
-- [ ] **1. {stage-1}**: Pending → {artifact}
-- [ ] **2. {stage-2}**: Pending → {artifact}
-- [ ] **3. {stage-3}**: Pending → {artifact}
-- [ ] **4. {stage-4}**: Pending → {artifact}
-
-## Dependencies
-
-### Requires
-- {Previous bolt or None}
-
-### Enables
-- {Next bolt or deployment}
-
-## Success Criteria
-
-- [ ] All stories implemented
-- [ ] All acceptance criteria met
-- [ ] Tests passing
-- [ ] Code reviewed
-
-## Notes
-
-{Any additional context or considerations}
-```
-
----
-
-## Status Values
-
-- **planned**: Bolt created, not started
-- **in-progress**: Currently being executed
-- **completed**: All stages done
-- **blocked**: Cannot proceed due to dependency
-
----
-
-## Stage Status Symbols
-
-- [ ] = Pending
-- ⏳ = In Progress
-- ✅ = Complete
-- 🚫 = Blocked
-
----
-
-## Example
-
-```yaml
----
-id: bolt-auth-service-1
-unit: 001-auth-service
-intent: 001-user-authentication
-type: ddd-construction-bolt
-status: in-progress
-stories:
-  - story-1
-  - story-2
-created: 2024-12-05
-started: 2024-12-05
-completed: null
-current_stage: design
-stages_completed:
-  - name: model
-    completed: 2024-12-05T10:00:00Z
-    artifact: ddd-01-domain-model.md
-
-requires_bolts: []
-enables_bolts:
-  - bolt-auth-service-2
-requires_units: []
-blocks: false
-
-complexity:
-  avg_complexity: 2
-  avg_uncertainty: 1
-  max_dependencies: 1
-  testing_scope: 2
----
-
-# Bolt: bolt-auth-service-1
-
-## Overview
-
-First bolt for authentication service covering user registration and login.
-
-## Objective
-
-Implement core authentication functionality including user registration with email verification and secure login.
-
-## Stories Included
-
-- **story-1**: User can register (Must)
-- **story-2**: User can login (Must)
-
-## Bolt Type
-
-**Type**: DDD Construction Bolt
-**Definition**: `.iris/aidlc/templates/construction/bolt-types/ddd-construction-bolt.md`
-
-## Stages
-
-- ✅ **1. model**: Complete → ddd-01-domain-model.md
-- ⏳ **2. design**: In Progress → ddd-02-technical-design.md ← current
-- [ ] **3. implement**: Pending → src/auth-service/
-- [ ] **4. test**: Pending → ddd-03-test-report.md
-
-## Dependencies
-
-### Requires
-- None (first bolt)
-
-### Enables
-- bolt-auth-service-2 (MFA implementation)
-
-## Success Criteria
-
-- ✅ Domain model defined
-- [ ] API design complete
-- [ ] Implementation complete
-- [ ] Tests passing
-```

package/dist/templates/construction/bolt-types/ddd-construction-bolt/adr-template.md

@@ -1,49 +0,0 @@
----
-bolt: {bolt-id}
-created: {YYYY-MM-DDTHH:MM:SSZ}
-status: proposed | accepted | deprecated | superseded
-superseded_by: {adr-number if applicable}
----
-
-# ADR-{number}: {title}
-
-## Context
-
-{Describe the situation that requires a decision. What is the problem or opportunity? What constraints exist? What forces are at play?}
-
-## Decision
-
-{State the decision clearly. What did we decide to do?}
-
-## Rationale
-
-{Explain why this decision was made. What alternatives were considered? Why were they rejected?}
-
-### Alternatives Considered
-
-| Alternative | Pros | Cons | Why Rejected |
-|-------------|------|------|--------------|
-| {option 1} | | | |
-| {option 2} | | | |
-
-## Consequences
-
-### Positive
-
-- {Benefit 1}
-- {Benefit 2}
-
-### Negative
-
-- {Trade-off 1}
-- {Trade-off 2}
-
-### Risks
-
-- {Risk 1 and mitigation}
-
-## Related
-
-- **Stories**: {related story IDs}
-- **Standards**: {if this should be added to standards later}
-- **Previous ADRs**: {related ADR numbers}

package/dist/templates/construction/bolt-types/ddd-construction-bolt/ddd-01-domain-model-template.md

@@ -1,55 +0,0 @@
----
-unit: {UUU}-{unit-name}
-bolt: {BBB}-{unit-name}
-stage: model
-status: complete
-updated: {YYYY-MM-DDTHH:MM:SSZ}
----
-
-# Static Model - {Unit Name}
-
-## Bounded Context
-
-{Define the bounded context for this unit}
-
-## Domain Entities
-
-| Entity | Properties | Business Rules |
-|--------|------------|----------------|
-| {Entity} | {properties} | {rules} |
-
-## Value Objects
-
-| Value Object | Properties | Constraints |
-|--------------|------------|-------------|
-| {ValueObject} | {properties} | {constraints} |
-
-## Aggregates
-
-| Aggregate Root | Members | Invariants |
-|----------------|---------|------------|
-| {Root} | {members} | {invariants} |
-
-## Domain Events
-
-| Event | Trigger | Payload |
-|-------|---------|---------|
-| {Event} | {trigger} | {payload} |
-
-## Domain Services
-
-| Service | Operations | Dependencies |
-|---------|------------|--------------|
-| {Service} | {operations} | {dependencies} |
-
-## Repository Interfaces
-
-| Repository | Entity | Methods |
-|------------|--------|---------|
-| {Repository} | {entity} | {methods} |
-
-## Ubiquitous Language
-
-| Term | Definition |
-|------|------------|
-| {term} | {definition} |