teamspec 3.2.0 → 4.1.0

package/teamspec-core/teamspec.yml

@@ -1,69 +1,85 @@
 # TeamSpec Configuration
-# Version: 2.0.0
+# Version: 4.0.0
 
-version: "2.0"
-name: "TeamSpec Feature Canon Operating Model"
+version: "4.0"
+name: "TeamSpec Product-Canon Operating Model"
 
 # Core principles
 principles:
-  - Feature Canon is the source of truth for system behavior
+  - Product Canon is the source of truth for production behavior (AS-IS)
+  - Feature-Increments propose changes to products (TO-BE)
   - Stories describe deltas (changes), not full behavior
+  - Canon is updated ONLY after deployment via ts:po sync
   - Structural artifacts require explicit creation commands
   - Each role has clear ownership boundaries
 
 # Folder structure reference
 structure:
   teamspec_root: ".teamspec"
-  project_root: "projects/{project-id}"
+  products_root: "products/{product-id}"
+  projects_root: "projects/{project-id}"
   
-  folders:
-    features: "projects/{project-id}/features"
+  product_folders:
+    features: "products/{product-id}/features"
+    business_analysis: "products/{product-id}/business-analysis"
+    solution_designs: "products/{product-id}/solution-designs"
+    technical_architecture: "products/{product-id}/technical-architecture"
+    decisions: "products/{product-id}/decisions"
+    regression_tests: "products/{product-id}/qa/regression-tests"
+    
+  project_folders:
+    feature_increments: "projects/{project-id}/feature-increments"
+    epics: "projects/{project-id}/epics"
     stories: "projects/{project-id}/stories"
-    adr: "projects/{project-id}/adr"
-    decisions: "projects/{project-id}/decisions"
     dev_plans: "projects/{project-id}/dev-plans"
-    qa: "projects/{project-id}/qa"
+    test_cases: "projects/{project-id}/qa/test-cases"
+    bug_reports: "projects/{project-id}/qa/bug-reports"
     sprints: "projects/{project-id}/sprints"
-    epics: "projects/{project-id}/epics"
 
 # Role definitions
 roles:
+  PO:
+    name: "Product Owner"
+    owns:
+      - "Products (product.yml, structure)"
+      - "Projects (project.yml, scope)"
+      - "Product Canon (approval authority)"
+      - "Canon sync execution"
   BA:
     name: "Business Analyst"
     owns:
-      - "Problem/goal definition"
-      - "Business value and scope"
-      - "Feature Canon: Purpose & Scope section"
+      - "Business Analysis artifacts"
+      - "Domain knowledge documentation"
   FA:
     name: "Functional Analyst"
     owns:
-      - "Functional specifications"
-      - "Story slicing"
-      - "Feature Canon: Behavior section"
-      - "Feature Canon: Change Log"
+      - "Features (f-PRX-*.md)"
+      - "Feature-Increments (fi-PRX-*.md)"
+      - "Epics (epic-PRX-*.md)"
+      - "Stories (s-eXXX-YYY-*.md)"
   SA:
     name: "Solution Architect"
     owns:
-      - "Technical design"
-      - "Architecture decisions (ADRs)"
+      - "Solution Designs"
+      - "Technical Architecture"
+      - "ADRs"
   DEV:
     name: "Developer"
     owns:
       - "Implementation"
-      - "Development plans"
+      - "Dev plans (dp-eXXX-sYYY-*.md)"
   QA:
-    name: "Quality Assurance"
+    name: "QA Engineer"
     owns:
-      - "Test cases (feature-level)"
+      - "Project test cases (tc-fi-PRX-*.md)"
+      - "Product regression tests (rt-f-PRX-*.md)"
       - "Bug reports"
-      - "UAT packs"
   SM:
     name: "Scrum Master"
     owns:
-      - "Sprint management"
-      - "Process facilitation"
+      - "Sprint operations"
+      - "Deployment checklist"
   DES:
     name: "Designer"
     owns:
-      - "UI/UX design"
-      - "Design system"
+      - "UX/UI design artifacts"

package/teamspec-core/templates/README.md

@@ -1,14 +1,14 @@
-# TeamSpec 2.0 Templates
+# TeamSpec 4.0 Templates
 
-> **Version:** 2.0  
-> **Last Updated:** 2026-01-07  
-> **Purpose:** Aligned templates for Feature Canon operating model
+> **Version:** 4.0  
+> **Last Updated:** 2026-01-11  
+> **Purpose:** Aligned templates for Product-Canon operating model
 
 ---
 
 ## Overview
 
-These templates are designed for the TeamSpec 2.0 Feature Canon operating model. Each template:
+These templates are designed for the TeamSpec 4.0 Product-Canon operating model. Each template:
 
 1. **Identifies its owner** — Which role creates/maintains it
 2. **States its artifact type** — Source of Truth, Execution, Planning, or Operational

package/teamspec-core/templates/adr-template.md

@@ -1,28 +1,30 @@
 # ADR-XXX: [Decision Title]
 
-<!-- 
-  ⚠️ ADR RULES
-  
-  Architecture Decision Records document technical decisions.
-  
-  RULES:
-  1. ADRs link to features they affect
-  2. ADRs link to business decisions that triggered them
-  3. SA does NOT update Feature Canon directly - ADRs inform FA
-  4. If behavior is affected, FA must review Feature Canon
-  
-  TEAMSPEC RULES ENFORCED:
-  - TS-ADR-001: ADR required for architecture-impacting changes
-  - TS-ADR-002: ADR must link to affected features
+<!--
+  ⛔ DEPRECATED TEMPLATE - DO NOT USE
+
+  This template is DEPRECATED as of TeamSpec 4.0.
+
+  USE INSTEAD: ta-template.md (Technical Architecture)
+
+  REASON: TeamSpec 4.0 renamed "ADR" to "Technical Architecture" (TA)
+  - Artifact naming: ta-{PRX}-{NNN}-{description}.md
+  - Commands: ts:sa ta (not ts:sa adr)
+
+  The commands ts:sa design and ts:sa adr were REMOVED in 4.0.
+  See: spec/4.0/registry.yml commands section (REMOVED commands)
+
+  See: spec/4.0/registry.yml for correct artifact patterns
 -->
 
-> **Template Version**: 2.0  
+> **Template Version**: 2.0 (DEPRECATED)
 > **Last Updated**: 2026-01-07
+> **Status**: ⛔ DEPRECATED - Use ta-template.md instead
 
 ---
 
-**Document Owner:** SA (Solution Architect)  
-**Artifact Type:** Technical Decision (Canonical)  
+**Document Owner:** SA (Solution Architect)
+**Artifact Type:** Technical Decision (DEPRECATED - use Technical Architecture)
 **Lifecycle:** Permanent, versioned
 
 ---

package/teamspec-core/templates/bai-template.md

@@ -0,0 +1,125 @@
+# Business Analysis Increment: `<bai-PRX-XXX-description>`
+
+> **ID:** bai-PRX-XXX  
+> **Product:** `<product-id>` (PRX)  
+> **Project:** `<project-id>`  
+> **Target BA:** `<ba-PRX-XXX-name>`  
+> **Target Feature:** `<f-PRX-XXX-feature-name>`  
+> **Status:** draft | proposed | approved | implemented | synced
+
+---
+
+**Document Owner:** BA (Business Analyst)  
+**Artifact Type:** Business Analysis Increment (Project)  
+**Lifecycle:** Project-scoped, merged to Product BA after approval
+
+---
+
+## Metadata
+
+| Field | Value |
+| :--- | :--- |
+| **BAI ID** | bai-PRX-XXX |
+| **Status** | Proposed / Accepted / Implemented / Synced |
+| **Date** | YYYY-MM-DD |
+| **Author** | [BA Name] |
+| **Target BA** | [ba-PRX-XXX](../../products/PRX/business-analysis/ba-PRX-XXX-*.md) |
+| **Feature Increment** | [fi-PRX-XXX](../feature-increments/fi-PRX-XXX-*.md) |
+
+---
+
+## 1. Overview
+
+_Brief description of the business analysis increment specific to this project._
+
+---
+
+## 2. Business Context
+
+### 2.1 Business Problem
+
+_What business problem does this address?_
+
+### 2.2 Stakeholders
+
+_Who is impacted by this analysis?_
+
+### 2.3 Business Goals
+
+_What are we trying to achieve?_
+
+---
+
+## 3. AS-IS (Current Product BA)
+
+> _Auto-populated from Product Business Analysis. DO NOT EDIT unless correcting errors._
+
+_Copy relevant sections from the Product BA._
+
+---
+
+## 4. TO-BE (Project Business Analysis)
+
+### 4.1 New/Changed Business Capabilities
+
+_Describe what the project-specific analysis includes that product analysis doesn't._
+
+### 4.2 Success Metrics
+
+| Metric | Baseline | Target | Timeline |
+|--------|----------|--------|----------|
+| [Metric 1] | [Current] | [Goal] | [Timeline] |
+| [Metric 2] | [Current] | [Goal] | [Timeline] |
+
+### 4.3 Out of Scope
+
+_Explicitly state what this increment does NOT include._
+
+---
+
+## 5. Impact Analysis
+
+### 5.1 Affected Stakeholders
+
+| Stakeholder | Impact | Notes |
+|-------------|--------|-------|
+| [Stakeholder 1] | [Impact] | [Notes] |
+| [Stakeholder 2] | [Impact] | [Notes] |
+
+### 5.2 Organizational Impact
+
+_How this change affects business processes and operations._
+
+### 5.3 Dependencies
+
+_Other initiatives or decisions this depends on._
+
+---
+
+## 6. Integration Notes
+
+### 6.1 Product BA Alignment
+
+_How this project BAI aligns with or extends the product BA._
+
+### 6.2 Merge Strategy
+
+_How this BAI will be merged back to Product BA after project completion._
+
+---
+
+## 7. Review & Approval
+
+| Role | Name | Status | Date |
+|------|------|--------|------|
+| BA (Author) | [Name] | ✅ | YYYY-MM-DD |
+| PO | [Name] | ⏳ | |
+| FA | [Name] | ⏳ | |
+
+---
+
+## Change Log
+
+| Date | Author | Change |
+|------|--------|--------|
+| YYYY-MM-DD | @author | Initial draft |

package/teamspec-core/templates/bug-report-template.md

@@ -1,26 +1,29 @@
-# Bug: [Title]
+# Bug Report: `bug-{project-id}-{NNN}-{description}`
 
-<!-- 
+<!--
   ⚠️ BUG CLASSIFICATION IS MANDATORY
-  
+
   When reporting bugs, you MUST classify whether the issue is:
   - Implementation defect (code doesn't match Canon)
   - Feature Canon wrong (Canon doesn't match business intent)
   - Undocumented behavior (neither covers this case)
-  
+
   Classification determines who fixes what.
-  
+
+  NAMING PATTERN: bug-{project-id}-{NNN}-{description}.md
+  EXAMPLE: bug-q1-auth-042-oauth-timeout.md
+
   TEAMSPEC RULES ENFORCED:
   - TS-QA-002: Bug classification required (exactly one)
 -->
 
-> **Template Version**: 2.0  
-> **Last Updated**: 2026-01-07
+> **Template Version**: 4.0
+> **Last Updated**: 2026-01-11
 
 ---
 
-**Document Owner:** QA (QA Engineer)  
-**Artifact Type:** Defect Report  
+**Document Owner:** QA (QA Engineer)
+**Artifact Type:** Bug Report (Project-scoped)
 **Lifecycle:** Open → Resolved → Closed
 
 ---
@@ -29,7 +32,9 @@
 
 | Field | Value |
 | :--- | :--- |
-| **Bug ID** | BUG-XXX |
+| **Bug ID** | bug-{project-id}-{NNN} |
+| **Project** | {project-id} |
+| **Product** | {product-id} ({PRX}) |
 | **Severity** | Critical / High / Medium / Low |
 | **Priority** | P1 / P2 / P3 / P4 |
 | **Environment** | Staging / Dev / Production |
@@ -61,7 +66,7 @@
 
 > What should happen (reference Feature Canon if applicable).
 
-**Feature Canon Reference:** [F-XXX](../../features/F-XXX-name.md), Section: [Section Name]
+**Feature Canon Reference:** [f-{PRX}-{NNN}](../../products/{product-id}/features/f-{PRX}-{NNN}-*.md), Section: [Section Name]
 
 [What the system should do according to Feature Canon]
 
@@ -143,16 +148,17 @@ Is the behavior documented in Feature Canon?
 
 | Feature | Section | Expected Behavior |
 |---------|---------|-------------------|
-| [F-XXX](../../features/F-XXX-name.md) | [Section] | [Brief description from Canon] |
+| [f-{PRX}-{NNN}](../../products/{product-id}/features/f-{PRX}-{NNN}-*.md) | [Section] | [Brief description from Canon] |
 
 ---
 
-## Related Stories / Bugs
+## Related Artifacts
 
 | ID | Type | Relationship |
 |----|------|--------------|
-| [S-XXX] | Story | Introduced behavior |
-| [BUG-YYY] | Bug | Related issue |
+| [s-e{EEE}-{SSS}](../stories/**/s-e{EEE}-{SSS}-*.md) | Story | Introduced behavior |
+| [fi-{PRX}-{NNN}](../feature-increments/fi-{PRX}-{NNN}-*.md) | Feature-Increment | Related FI |
+| [bug-{project-id}-{NNN}](./bug-{project-id}-{NNN}-*.md) | Bug | Related issue |
 
 ---
 

package/teamspec-core/templates/business-analysis-template.md

@@ -1,26 +1,29 @@
-# Business Analysis Document: [Feature Name]
+# Business Analysis: `ba-{PRX}-{NNN}-{description}`
 
-<!-- 
+<!--
   ⚠️ THIS IS A PLANNING ARTIFACT, NOT SOURCE OF TRUTH
-  
+
   This Business Analysis document captures analysis and decisions
   during the planning phase.
-  
+
   SOURCE OF TRUTH:
-  - For current system behavior → Feature Canon (/features/F-XXX.md)
-  - For business decisions → Decision Log (/decisions/DEC-XXX.md)
-  
+  - For current system behavior → Feature Canon (f-{PRX}-{NNN}.md)
+  - For business decisions → Decision Log (dec-{PRX}-{NNN}.md)
+
   This document becomes HISTORICAL after Feature Canon is created.
+
+  NAMING PATTERN: ba-{PRX}-{NNN}-{description}.md
+  EXAMPLE: ba-ACME-001-checkout-process.md
 -->
 
-> **Template Version**: 2.0  
-> **Last Updated**: 2026-01-07
+> **Template Version**: 4.0
+> **Last Updated**: 2026-01-11
 
 ---
 
-**Document Owner:** BA (Business Analyst)  
-**Artifact Type:** Planning (Not Source of Truth)  
-**Lifecycle:** Historical after Feature Canon creation
+**Document Owner:** BA (Business Analyst)
+**Artifact Type:** Business Analysis (Product Canon)
+**Lifecycle:** Permanent, updated via bai-* increments
 
 | Metadata | Details |
 | :--- | :--- |
@@ -61,7 +64,7 @@
 
 | Feature ID | Feature Name | Status | Link |
 |------------|--------------|--------|------|
-| [F-XXX](../features/F-XXX-name.md) | [Feature Name] | Draft / Active | |
+| [f-{PRX}-{NNN}](../features/f-{PRX}-{NNN}-*.md) | [Feature Name] | Draft / Active | |
 
 ---
 

package/teamspec-core/templates/decision-log-template.md

@@ -1,27 +1,30 @@
-# DEC-XXX: [Decision Title]
+# Decision: `dec-{PRX}-{NNN}-{description}`
 
-<!-- 
+<!--
   ⚠️ DECISION LOG RULES
-  
-  Business decisions must be logged and linked to affected features.
-  
+
+  Product-level business decisions must be logged and linked to affected features.
+
   RULES:
   1. Decisions must link to at least one feature
-  2. BA owns business decisions
+  2. PO owns product decisions (not BA)
   3. Decisions that affect scope require feature review
   4. Cross-feature decisions require SA acknowledgment
-  
+
+  NAMING PATTERN: dec-{PRX}-{NNN}-{description}.md
+  EXAMPLE: dec-ACME-001-payment-provider.md
+
   TEAMSPEC RULES ENFORCED:
   - TS-DEC-001: Decision must link to features
 -->
 
-> **Template Version**: 2.0  
-> **Last Updated**: 2026-01-07
+> **Template Version**: 4.0
+> **Last Updated**: 2026-01-11
 
 ---
 
-**Document Owner:** BA (Business Analyst)  
-**Artifact Type:** Business Decision (Canonical)  
+**Document Owner:** PO (Product Owner)
+**Artifact Type:** Product Decision (Canonical)
 **Lifecycle:** Permanent
 
 ---
@@ -30,16 +33,17 @@
 
 | Field | Value |
 |-------|-------|
-| **Decision ID** | DEC-XXX |
+| **Decision ID** | dec-{PRX}-{NNN} |
+| **Product** | {product-id} ({PRX}) |
 | **Date Proposed** | YYYY-MM-DD |
 | **Date Confirmed** | YYYY-MM-DD (or "Pending") |
-| **Decision Owner(s)** | [Stakeholder Name(s)] |
+| **Decision Owner** | PO (Product Owner) |
 | **Facilitator** | [BA Name] |
 | **Status** | Proposed / Confirmed / Superseded |
 | **Type** | Reversible / Costly / Irreversible |
 | **Severity** | Minor / Major / Critical |
 | **Scope** | Feature / Cross-Feature / Product |
-| **Superseded By** | [DEC-YYY if applicable] |
+| **Superseded By** | [dec-{PRX}-{NNN} if applicable] |
 
 ---
 
@@ -86,7 +90,7 @@ _What did we decide? State explicitly and unambiguously._
 
 | Feature ID | Feature Name | Impact Description |
 |------------|--------------|-------------------|
-| [F-XXX](../features/F-XXX-name.md) | [Feature Name] | [Scoped in / Scoped out / Behavior changed / Priority set] |
+| [f-{PRX}-{NNN}](../features/f-{PRX}-{NNN}-*.md) | [Feature Name] | [Scoped in / Scoped out / Behavior changed / Priority set] |
 
 ---
 
@@ -158,8 +162,8 @@ _What would it cost to reverse this decision later?_
 |-------|-------|
 | **Acknowledged By** | [SA Name] |
 | **Date** | YYYY-MM-DD |
-| **Assessment** | No Impact / Requires ADR / Approved |
-| **ADR Reference** | [ADR-XXX](../adr/ADR-XXX-*.md) (if required) |
+| **Assessment** | No Impact / Requires TA / Approved |
+| **TA Reference** | [ta-{PRX}-{NNN}](../technical-architecture/ta-{PRX}-{NNN}-*.md) (if required) |
 
 **Architecture Notes**:
 [SA assessment of technical implications]
@@ -187,17 +191,17 @@ _Stakeholder confirmation that decision is accurate and approved._
 |----------|------|------------------|
 | [BA Title] | [Link] | [Section] |
 
-### Related Stories (if applicable)
+### Related Feature-Increments (if applicable)
 
-| Story ID | Story Title | Relationship |
-|----------|-------------|--------------|
-| [S-XXX](../stories/*/S-XXX-*.md) | [Title] | Created from this decision |
+| FI ID | Description | Relationship |
+|-------|-------------|--------------|
+| [fi-{PRX}-{NNN}](../../projects/{project-id}/feature-increments/fi-{PRX}-{NNN}-*.md) | [Brief description] | Created from this decision |
 
 ### Related Decisions
 
 | Decision ID | Relationship |
 |-------------|--------------|
-| [DEC-YYY] | Depends on / Superseded by / Related to |
+| [dec-{PRX}-{NNN}] | Depends on / Superseded by / Related to |
 
 ---