project-iris 0.0.11 → 0.0.13

package/dist/iris_bundle/frameworks/iris-core/templates/inception/stories-template.md

@@ -0,0 +1,38 @@
+---
+intent: {NNN}-{intent-name}
+phase: inception
+status: stories-created
+updated: {YYYY-MM-DDTHH:MM:SSZ}
+---
+
+# {Intent Name} - Stories
+
+## User Stories
+
+### Story-1: {Title}
+
+**As a** {user type}
+**I want** {goal}
+**So that** {benefit}
+
+**Acceptance Criteria**:
+
+- [ ] {Criterion 1}
+- [ ] {Criterion 2}
+
+**Priority**: High/Medium/Low
+**Estimate**: {T-shirt size: S/M/L/XL}
+
+### Story-2: {Title}
+
+...
+
+## Technical Stories
+
+### Tech-Story-1: {Title}
+
+**Description**: {What needs to be done technically}
+**Rationale**: {Why this is needed}
+**Acceptance Criteria**:
+
+- [ ] {Criterion}

package/dist/iris_bundle/frameworks/iris-core/templates/inception/story-template.md

@@ -0,0 +1,147 @@
+# Story Template
+
+Use this template when creating individual story files during story creation.
+
+---
+
+## Frontmatter
+
+```yaml
+---
+id: {SSS}-{title-slug}
+unit: {UUU}-{unit-name}
+intent: {NNN}-{intent-name}
+status: draft
+priority: must|should|could
+created: {YYYY-MM-DDTHH:MM:SSZ}
+assigned_bolt: null
+implemented: false
+---
+```
+
+---
+
+## Content
+
+```markdown
+# Story: {SSS}-{title-slug}
+
+## User Story
+
+**As a** {user role}
+**I want** {goal/action}
+**So that** {benefit/reason}
+
+## Acceptance Criteria
+
+- [ ] **Given** {precondition}, **When** {action}, **Then** {expected outcome}
+- [ ] **Given** {precondition}, **When** {action}, **Then** {expected outcome}
+- [ ] **Given** {precondition}, **When** {action}, **Then** {expected outcome}
+
+## Technical Notes
+
+{Implementation hints, constraints, or considerations}
+
+## Dependencies
+
+### Requires
+- {Other stories this depends on, or "None"}
+
+### Enables
+- {Stories that depend on this, or "None"}
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| {edge case 1} | {behavior} |
+| {edge case 2} | {behavior} |
+
+## Out of Scope
+
+- {What this story does NOT cover}
+```
+
+---
+
+## Priority Levels
+
+| Priority | Meaning | Criteria |
+|----------|---------|----------|
+| `must` | Required for MVP | System unusable without this |
+| `should` | Important | Significant value, not blocking |
+| `could` | Nice to have | Enhances experience |
+
+---
+
+## Status Values
+
+| Status | Meaning |
+|--------|---------|
+| `draft` | Story written, needs review |
+| `ready` | Reviewed, ready for bolt |
+| `in-progress` | Being implemented in a bolt |
+| `implemented` | Code complete |
+| `tested` | Tests passing |
+| `done` | All acceptance criteria met |
+
+---
+
+## Example
+
+```yaml
+---
+id: 001-user-signup
+unit: 001-auth-service
+intent: 001-user-authentication
+status: ready
+priority: must
+created: 2024-12-05T10:00:00Z
+assigned_bolt: 001-auth-service
+implemented: false
+---
+```
+
+```markdown
+# Story: 001-user-signup
+
+## User Story
+
+**As a** new user
+**I want** to register with my email and password
+**So that** I can access the application
+
+## Acceptance Criteria
+
+- [ ] **Given** I am on the registration page, **When** I enter valid email and password, **Then** my account is created and I receive a confirmation email
+- [ ] **Given** I enter an email that already exists, **When** I submit registration, **Then** I see an error message "Email already registered"
+- [ ] **Given** I enter a password less than 8 characters, **When** I submit, **Then** I see validation error
+
+## Technical Notes
+
+- Password must be hashed with bcrypt (cost factor 12)
+- Email validation should use RFC 5322 compliant regex
+- Rate limit registration to 5 attempts per IP per hour
+
+## Dependencies
+
+### Requires
+- None (first story)
+
+### Enables
+- 002-user-login (User login)
+- 003-email-verification (Email verification)
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| SQL injection in email | Safely escaped, validation fails |
+| Very long email (255+ chars) | Validation error |
+| Unicode in password | Allowed, properly encoded |
+
+## Out of Scope
+
+- Social login (OAuth) - separate story
+- Password reset - separate story
+```

package/dist/iris_bundle/frameworks/iris-core/templates/inception/system-context-template.md

@@ -0,0 +1,29 @@
+---
+intent: {NNN}-{intent-name}
+phase: inception
+status: context-defined
+updated: {YYYY-MM-DDTHH:MM:SSZ}
+---
+
+# {Intent Name} - System Context
+
+## System Overview
+
+{High-level description of what we are building}
+
+## Context Diagram
+
+{Mermaid diagram showing System, Users, and External Systems}
+
+## External Integrations
+
+- **System A**: {Purpose of integration}
+- **System B**: {Purpose of integration}
+
+## High-Level Constraints
+
+- {e.g., Must run on AWS, Must use existing Auth provider}
+
+## Key NFR Goals
+
+- {High-level performance/security goals to guide construction}

package/dist/iris_bundle/frameworks/iris-core/templates/inception/unit-brief-template.md

@@ -0,0 +1,177 @@
+# Unit Brief Template
+
+Use this template when creating unit briefs during decomposition. This is the **critical input for Construction**.
+
+---
+
+## Frontmatter
+
+```yaml
+---
+unit: {UUU}-{unit-name}
+intent: {NNN}-{intent-name}
+phase: inception
+status: draft|ready
+created: {YYYY-MM-DDTHH:MM:SSZ}
+updated: {YYYY-MM-DDTHH:MM:SSZ}
+---
+```
+
+**Note**: The `unit` field uses the full folder name including the 3-digit prefix (e.g., `001-auth-service`). This matches the folder structure and enables direct path construction in scripts. Story naming uses the story title (e.g., `001-user-signup.md`).
+
+---
+
+## Content
+
+```markdown
+# Unit Brief: {Unit Name}
+
+## Purpose
+
+{Clear, concise statement of what this unit does and why it exists}
+
+## Scope
+
+### In Scope
+- {What this unit IS responsible for}
+- {What this unit IS responsible for}
+
+### Out of Scope
+- {What this unit is NOT responsible for}
+- {What other units handle}
+
+---
+
+## Assigned Requirements
+
+**These FRs from the intent are assigned to this unit. Stories will be created from these.**
+
+| FR | Requirement | Priority |
+|----|-------------|----------|
+| FR-{n} | {description from intent requirements.md} | Must/Should/Could |
+
+---
+
+## Domain Concepts
+
+### Key Entities
+| Entity | Description | Attributes |
+|--------|-------------|------------|
+| {Entity 1} | {What it represents} | {Key properties} |
+| {Entity 2} | {What it represents} | {Key properties} |
+
+### Key Operations
+| Operation | Description | Inputs | Outputs |
+|-----------|-------------|--------|---------|
+| {Operation 1} | {What it does} | {Input data} | {Output data} |
+| {Operation 2} | {What it does} | {Input data} | {Output data} |
+
+---
+
+## Story Summary
+
+| Metric | Count |
+|--------|-------|
+| Total Stories | {n} |
+| Must Have | {n} |
+| Should Have | {n} |
+| Could Have | {n} |
+
+### Stories
+
+| Story ID | Title | Priority | Status |
+|----------|-------|----------|--------|
+| {story-1} | {Title} | Must | Planned |
+| {story-2} | {Title} | Should | Planned |
+
+---
+
+## Dependencies
+
+### Depends On
+| Unit | Reason |
+|------|--------|
+| {unit-name} | {Why this dependency exists} |
+
+### Depended By
+| Unit | Reason |
+|------|--------|
+| {unit-name} | {Why they depend on this} |
+
+### External Dependencies
+| System | Purpose | Risk |
+|--------|---------|------|
+| {External system} | {Why needed} | {Risk level} |
+
+---
+
+## Technical Context
+
+### Suggested Technology
+{Recommendations based on tech stack standards}
+
+### Integration Points
+| Integration | Type | Protocol |
+|-------------|------|----------|
+| {System/Unit} | API/Event/DB | REST/GraphQL/Kafka |
+
+### Data Storage
+| Data | Type | Volume | Retention |
+|------|------|--------|-----------|
+| {Data type} | SQL/NoSQL/Cache | {Volume} | {Retention} |
+
+---
+
+## Constraints
+
+- {Technical constraint specific to this unit}
+- {Business constraint specific to this unit}
+
+---
+
+## Success Criteria
+
+### Functional
+- [ ] {Criterion 1: What must work}
+- [ ] {Criterion 2: What must work}
+
+### Non-Functional
+- [ ] {Performance target}
+- [ ] {Security requirement}
+
+### Quality
+- [ ] Code coverage > 80%
+- [ ] All acceptance criteria met
+- [ ] Code reviewed and approved
+
+---
+
+## Bolt Suggestions
+
+Based on stories and complexity:
+
+| Bolt | Type | Stories | Objective |
+|------|------|---------|-----------|
+| bolt-{unit}-1 | DDD | S1, S2 | Core entities |
+| bolt-{unit}-2 | DDD | S3, S4 | API layer |
+
+---
+
+## Notes
+
+{Any additional context, risks, or considerations for Construction}
+```
+
+---
+
+## Quality Checklist
+
+Before marking unit brief as ready:
+
+- [ ] Purpose is clear and specific
+- [ ] Scope boundaries are defined
+- [ ] Key entities identified
+- [ ] Stories assigned to this unit
+- [ ] Dependencies mapped
+- [ ] Success criteria are measurable
+- [ ] Bolt suggestions provided

package/dist/iris_bundle/frameworks/iris-core/templates/inception/units-template.md

@@ -0,0 +1,52 @@
+---
+intent: {NNN}-{intent-name}
+phase: inception
+status: units-decomposed
+updated: {YYYY-MM-DDTHH:MM:SSZ}
+---
+
+# {Intent Name} - Unit Decomposition
+
+## Units Overview
+
+This intent decomposes into {N} units of work:
+
+### Unit 1: {unit-name}
+
+**Description**: {What this unit does}
+
+**Stories**:
+
+- Story-1: {Title}
+- Story-3: {Title}
+
+**Deliverables**:
+
+- {Specific artifacts this unit produces}
+
+**Dependencies**:
+
+- Depends on: {Other units}
+- Depended by: {Units that need this}
+
+**Estimated Complexity**: S/M/L/XL
+
+### Unit 2: {unit-name}
+
+...
+
+## Unit Dependency Graph
+
+```text
+[Unit A] ──> [Unit B] ──> [Unit D]
+   │            │
+   └────> [Unit C] ──┘
+```
+
+## Execution Order
+
+Based on dependencies:
+
+1. Day 1-2: Unit A (foundation)
+2. Day 2-4: Unit B, Unit C (parallel)
+3. Day 5-6: Unit D (integration)

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

@@ -0,0 +1,226 @@
+# 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

@@ -0,0 +1,49 @@
+---
+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}