teamspec 3.2.0 → 4.1.0

package/teamspec-core/definitions/definition-of-done.md

@@ -1,7 +1,10 @@
 # Definition of Done (DoD)
 
-> **Version:** 2.0  
-> **Owner:** QA (validates completeness), SM (enforces at sprint close)
+> **Version:** 4.0  
+> **Status:** Normative  
+> **Owner:** FA (gates story completion)  
+> **Verifier:** QA (validates acceptance criteria)  
+> **Source:** [registry.yml](../registry.yml)
 
 A story is **Done** when ALL of the following are satisfied.
 
@@ -9,121 +12,81 @@ A story is **Done** when ALL of the following are satisfied.
 
 ## Mandatory Checklist
 
-### 1. Code Complete ✓
+Before a story moves to `done/`:
 
-| Check | Required |
-|-------|----------|
-| All tasks in dev plan marked complete | ✓ |
-| Code merged to main/develop branch | ✓ |
-| No outstanding TODOs in code (for this story) | ✓ |
-
-### 2. Tests Pass ✓
+### 1. Acceptance Criteria Verified ✓
 
 | Check | Required |
 |-------|----------|
-| Unit tests written and passing | ✓ |
-| Integration tests passing (if applicable) | ✓ |
-| Test coverage meets team threshold | ✓ |
-
-**Linter Rule:** `TS-DOD-002` — Tests are feature-level
+| All ACs tested and passing | ✓ |
+| QA sign-off obtained | ✓ |
+| No critical bugs outstanding | ✓ |
 
-### 3. Code Reviewed ✓
+### 2. Code Complete ✓
 
 | Check | Required |
 |-------|----------|
-| Pull request reviewed and approved | ✓ |
-| All review comments addressed | ✓ |
+| Code reviewed and approved | ✓ |
+| Code merged to main/develop branch | ✓ |
 | CI/CD pipeline passing | ✓ |
 
-### 4. Acceptance Criteria Verified ✓
+### 3. Tests Passing ✓
 
 | Check | Required |
 |-------|----------|
-| All ACs tested and passing | ✓ |
-| QA sign-off obtained | ✓ |
-| No critical bugs outstanding | ✓ |
+| Unit tests written and passing | ✓ |
+| Integration tests passing (if applicable) | ✓ |
+| All automated tests green | ✓ |
 
-### 5. Feature Canon Updated ✓ (CRITICAL)
+### 4. Feature-Increment Complete ✓
 
 | Check | Required |
 |-------|----------|
-| Feature file updated to reflect new behavior | ✓ |
-| Change Log entry added with story reference | ✓ |
-| Story Ledger updated | ✓ |
-| FA verified Canon sync | ✓ |
-
-**Linter Rule:** `TS-DOD-001` — Canon sync required before Done
+| Feature-Increment TO-BE section complete | ✓ |
+| TO-BE accurately reflects implemented behavior | ✓ |
+| Ready for deployment | ✓ |
 
-> ⚠️ **A story CANNOT be Done if it changes behavior and the Feature Canon is NOT updated.**
+**Note:** Feature-Increment TO-BE is merged into Product Canon AFTER deployment via `ts:po sync`.
 
 ---
 
-## Canon Sync Process
+## What Done Does NOT Include
 
-Before marking a story Done:
+| Action | When It Happens |
+|--------|-----------------|
+| Deployment to production | After DoD, during sprint close |
+| Canon sync (`ts:po sync`) | After deployment + QA verification |
+| Regression test update | At Deployment Verification Gate |
 
-1. **FA runs `ts:fa sync`** — Updates Feature Canon
-2. **FA updates Change Log** — Links to story ID
-3. **FA updates Story Ledger** — Records in `features/story-ledger.md`
-4. **QA verifies** — Tests match updated Canon
-
-### Change Log Entry Format
-
-```markdown
-| Date | Story | Change Summary | Author |
-|------|-------|----------------|--------|
-| YYYY-MM-DD | S-XXX | Brief description | FA Name |
-```
-
-### Story Ledger Entry Format
-
-```markdown
-| Story ID | Title | Sprint | Features Modified | Merged Date |
-|----------|-------|--------|-------------------|-------------|
-| S-XXX | Story title | Sprint N | F-001, F-002 | YYYY-MM-DD |
-```
+> ⚠️ **Canon is NEVER updated at DoD.** Canon sync happens POST-DEPLOY only.
 
 ---
 
-## Optional (Profile-Dependent)
-
-These checks apply based on team profile:
-
-### Regulated Profile
+## Enforcement
 
-| Check | Applies To |
-|-------|------------|
-| Compliance checklist signed off | regulated |
-| Audit trail documented | regulated |
-| Release notes updated | regulated |
-
-### Enterprise Profile
-
-| Check | Applies To |
-|-------|------------|
-| Documentation updated | enterprise |
-| Stakeholder notification sent | enterprise |
+| Actor | Responsibility |
+|-------|----------------|
+| FA | Marks story Done after QA verification |
+| QA | Verifies all ACs, provides sign-off |
+| DEV | Ensures code complete and merged |
+| Linter | Automated validation via `teamspec lint` |
 
 ---
 
-## Sprint Close Verification
+## Story State Flow
 
-At sprint close, SM verifies:
+```
+backlog/ → ready-to-refine/ → in-progress/ → done/
+                   ↑                          │
+                 DoR gate                   DoD gate
+```
 
-| Check | Owner |
-|-------|-------|
-| All "Done" stories have Canon sync | SM |
-| Story Ledger is current | FA |
-| No orphan stories (behavior change without Canon update) | QA |
+After `done/`, story proceeds to deployment and eventually Canon sync.
 
 ---
 
-## Quick Reference
-
-```
-DoD = Code + Tests + Review + ACs + Feature Canon Updated
-```
-
-**Most Common Failure:** Story marked "Done" without updating Feature Canon.
+## Related
 
-If Canon is not updated, the story is **NOT DONE**.
+- [Definition of Ready](definition-of-ready.md)
+- [Gates Overview](../gates.md)
+- [Registry (Source of Truth)](../registry.yml)

package/teamspec-core/definitions/definition-of-ready.md

@@ -1,7 +1,10 @@
 # Definition of Ready (DoR)
 
-> **Version:** 2.0  
-> **Owner:** FA (gates story readiness), SM (enforces in sprint planning)
+> **Version:** 4.0  
+> **Status:** Normative  
+> **Owner:** FA (gates story readiness)  
+> **Verifier:** SM (enforces in sprint planning)  
+> **Source:** [registry.yml](../registry.yml)
 
 A story is **Ready** for development when ALL of the following are satisfied.
 
@@ -9,26 +12,27 @@ A story is **Ready** for development when ALL of the following are satisfied.
 
 ## Mandatory Checklist
 
-### 1. Feature Canon Link ✓
+Before a story enters `in-progress/`:
+
+### 1. Epic Link ✓
 
 | Check | Required |
 |-------|----------|
-| Story links to existing Feature(s) in Feature Canon | ✓ |
-| Feature file exists in `features/` folder | ✓ |
-| Feature link uses correct format: `[F-XXX](../../features/F-XXX-name.md)` | ✓ |
+| Story linked to Epic via filename (`s-eXXX-YYY-*.md`) | ✓ |
+| Epic file exists in `projects/{project-id}/epics/` | ✓ |
 
-**Linter Rule:** `TS-STORY-001` — Feature link required
+**Linter Rule:** `TS-STORY-001` — Epic link required
 
-### 2. Delta Format ✓
+### 2. Feature-Increment Reference ✓
 
 | Check | Required |
 |-------|----------|
-| Story uses Before/After delta format | ✓ |
-| "Before" section references Feature Canon | ✓ |
-| "After" section describes ONLY the change | ✓ |
-| Story does NOT restate full feature behavior | ✓ |
+| Story references a Feature-Increment (`fi-PRX-NNN-*.md`) | ✓ |
+| Feature-Increment file exists in `projects/{project-id}/feature-increments/` | ✓ |
+| Feature-Increment has AS-IS section (current Canon state) | ✓ |
+| Feature-Increment has TO-BE section (proposed change) | ✓ |
 
-**Linter Rule:** `TS-STORY-002` — Delta-only format required
+**Linter Rule:** `TS-FI-001` — AS-IS/TO-BE required
 
 ### 3. Acceptance Criteria ✓
 
@@ -36,69 +40,40 @@ A story is **Ready** for development when ALL of the following are satisfied.
 |-------|----------|
 | All ACs are testable (Given/When/Then or clear assertions) | ✓ |
 | No ambiguous terms ("should work well", "user-friendly") | ✓ |
-| ACs cover the delta, not the entire feature | ✓ |
+| ACs describe the delta (change), not full feature behavior | ✓ |
 
 **Linter Rule:** `TS-STORY-003` — ACs must be testable
 
-### 4. FA Acceptance Gate ✓
+### 4. No Placeholders ✓
 
 | Check | Required |
 |-------|----------|
-| FA has reviewed and initialed the story | ✓ |
-| FA confirms delta is correctly scoped | ✓ |
-| FA confirms feature link is correct | ✓ |
+| No TBD/TODO/placeholder content in story | ✓ |
+| No TBD/TODO content in linked Feature-Increment | ✓ |
 
-**Gate:** FA Acceptance section complete in story
+**Linter Rule:** `TS-CONTENT-001` — No placeholder content
 
-### 5. Dev Plan Exists ✓
+### 5. Estimate Assigned ✓
 
 | Check | Required |
 |-------|----------|
-| Dev plan file exists in `dev-plans/` | ✓ |
-| Story links to dev plan | ✓ |
-| Dev plan has no TBD/TODO items | ✓ |
-
-**Linter Rule:** `TS-DEVPLAN-001` — Dev plan required before implementation
-
----
-
-## Optional (Profile-Dependent)
-
-These checks apply based on team profile:
-
-### Regulated Profile
-
-| Check | Applies To |
-|-------|------------|
-| Risk assessment completed | regulated |
-| Compliance impact documented | regulated |
-| Sign-off from compliance officer | regulated |
-
-### Enterprise Profile
-
-| Check | Applies To |
-|-------|------------|
-| Architecture review completed | enterprise |
-| Cross-team dependencies identified | enterprise |
+| Story has estimate (points or time) | ✓ |
+| Estimate is realistic based on dev plan | ✓ |
 
 ---
 
-## Workflow Gate
-
-Stories MUST be in `stories/ready-for-development/` folder to enter sprint.
+## Enforcement
 
-| From Folder | To Folder | Owner |
-|-------------|-----------|-------|
-| `backlog/` | `ready-to-refine/` | FA |
-| `ready-to-refine/` | `ready-for-development/` | DEV (after refinement) |
-| `ready-for-development/` | Sprint | SM (sprint planning) |
+| Actor | Responsibility |
+|-------|----------------|
+| FA | Creates story, ensures all content is complete |
+| SM | Verifies checklist before sprint planning |
+| Linter | Automated validation via `teamspec lint` |
 
 ---
 
-## Quick Reference
-
-```
-DoR = Feature Link + Delta Format + Testable ACs + FA Gate + Dev Plan
-```
+## Related
 
-If any check fails, the story is **NOT READY** for development.
+- [Definition of Done](definition-of-done.md)
+- [Gates Overview](../gates.md)
+- [Registry (Source of Truth)](../registry.yml)