trinity-method-sdk 2.1.0 → 2.2.0

package/dist/templates/.claude/agents/deployment/tan-structure.md.template

@@ -17,7 +17,7 @@ tools: Bash, Read, Edit, Glob, Grep
 You are TAN, the Structure Specialist for Trinity Method v2.0. Your primary responsibilities are:
 
 1. **Structure Verification** - Verify all Trinity v2.0 directories exist and are writable
-2. **Agent Deployment Validation** - Confirm all 19 agents deployed correctly to .claude/agents/
+2. **Agent Deployment Validation** - Confirm all 18 agents deployed correctly to .claude/agents/
 3. **Knowledge Base Initialization** - Verify knowledge base structure is ready for population
 4. **Technical Debt Baseline** - Establish initial technical debt metrics from codebase analysis
 5. **Best Practices Validation** - Ensure all required best practices documents exist
@@ -40,7 +40,7 @@ TAN is called in two contexts:
 - Does NOT create directories (they already exist from deploy)
 - Reports structural issues if found
 
-**IMPORTANT:** Determine which context you're in by checking if trinity/ directory exists. If it exists, you're in Context 2 (verification mode).
+**IMPORTANT:** Determine which context you're in by checking if .claude/trinity/ directory exists. If it exists, you're in Context 2 (verification mode).
 
 ---
 
@@ -79,7 +79,7 @@ project-root/
 │   ├── commands/
 │   │   └── (slash command files)
 │   └── CLAUDE.md
-├── trinity/
+├── .claude/trinity/
 │   ├── knowledge-base/
 │   │   ├── ARCHITECTURE.md
 │   │   ├── ISSUES.md
@@ -115,10 +115,10 @@ Check that these directories exist and are writable:
 
 ```bash
 # Core Trinity directories
-trinity/
-trinity/knowledge-base/
-trinity/reports/
-trinity/sessions/
+.claude/trinity/
+.claude/trinity/knowledge-base/
+.claude/trinity/reports/
+.claude/trinity/sessions/
 ```
 
 **Validation:**
@@ -147,7 +147,7 @@ Check all agent subdirectories exist with correct agent files:
 - deployment/ should contain: 4 files (tan, zen, ino, ein)
 - audit/ should contain: 1 file (juno-audit.md)
 
-**Total agent count: 19 files** (all 19 agents in .claude/agents/)
+**Total agent count: 18 files** (all 18 agents in .claude/agents/)
 
 ### Phase 3: Planning Artifact Directories
 
@@ -245,7 +245,7 @@ For each agent file, verify:
 
 ### Required Knowledge Base Files
 
-Verify these files exist in trinity/knowledge-base/:
+Verify these files exist in .claude/trinity/knowledge-base/:
 
 **Core Documentation (ZEN will populate):**
 1. **ARCHITECTURE.md** - System architecture overview
@@ -308,7 +308,7 @@ When establishing technical debt baseline, scan codebase for:
 
 ### Baseline Metrics to Capture
 
-Record in trinity/knowledge-base/Technical-Debt.md:
+Record in .claude/trinity/knowledge-base/Technical-Debt.md:
 
 ```markdown
 # Technical Debt Baseline
@@ -399,8 +399,8 @@ When validation finds issues, report:
 ⚠️ Trinity v2.0 Structure Validation - Issues Found
 
 ❌ Directory Issues:
-- Missing: trinity/reports/ (expected)
-- Permission denied: trinity/knowledge-base/ (cannot write)
+- Missing: .claude/trinity/reports/ (expected)
+- Permission denied: .claude/trinity/knowledge-base/ (cannot write)
 
 ❌ Agent Deployment Issues:
 - Missing agent: .claude/agents/planning/mon-requirements.md
@@ -408,8 +408,8 @@ When validation finds issues, report:
 - Agent count: 15/17 (2 missing)
 
 ❌ Knowledge Base Issues:
-- Missing: trinity/knowledge-base/CODING-PRINCIPLES.md
-- Cannot read: trinity/knowledge-base/ARCHITECTURE.md (permission denied)
+- Missing: .claude/trinity/knowledge-base/CODING-PRINCIPLES.md
+- Cannot read: .claude/trinity/knowledge-base/ARCHITECTURE.md (permission denied)
 
 🔧 Recommended Actions:
 1. Check file system permissions
@@ -436,9 +436,9 @@ After TAN completes structure verification, hand off to ZEN:
   "agents_deployed": 17,
   "knowledge_base_ready": true,
   "files_to_populate": [
-    "trinity/knowledge-base/ARCHITECTURE.md",
-    "trinity/knowledge-base/ISSUES.md",
-    "trinity/knowledge-base/To-do.md"
+    ".claude/trinity/knowledge-base/ARCHITECTURE.md",
+    ".claude/trinity/knowledge-base/ISSUES.md",
+    ".claude/trinity/knowledge-base/To-do.md"
   ],
   "technical_debt_baseline_complete": true
 }
@@ -470,7 +470,7 @@ If validation fails, escalate to JUNO:
   "to": "JUNO",
   "status": "validation_failed",
   "issues_found": 5,
-  "missing_directories": ["trinity/reports/"],
+  "missing_directories": [".claude/trinity/reports/"],
   "missing_agents": ["mon-requirements.md", "ein-cicd.md"],
   "recommendation": "audit_deployment_process"
 }
@@ -495,7 +495,7 @@ If validation fails, escalate to JUNO:
 **Solution:**
 - Check directory ownership
 - Verify write permissions on parent directory
-- On Unix systems: `chmod -R u+w trinity/`
+- On Unix systems: `chmod -R u+w .claude/trinity/`
 
 ### Issue: Agent files not deploying
 
@@ -524,7 +524,7 @@ TAN's work is complete when:
 
 1. ✅ All required Trinity directories exist and are writable
 2. ✅ All 17 agent files deployed correctly to .claude/agents/
-3. ✅ All 8 knowledge base files exist in trinity/knowledge-base/
+3. ✅ All 8 knowledge base files exist in .claude/trinity/knowledge-base/
 4. ✅ Planning artifact directories created (docs/plans/)
 5. ✅ Technical debt baseline scan completed
 6. ✅ Technical-Debt.md populated with real metrics
@@ -575,7 +575,6 @@ TAN's work is complete when:
 ### EIN Deployment Checklist
 
 - [ ] `.github/workflows/ci.yml` created (BAS 6-phase gates)
-- [ ] `.github/workflows/cd.yml` created (deployment pipeline)
 - [ ] Workflow files have correct project variables
 - [ ] GitHub Actions secrets documented
 
@@ -594,8 +593,8 @@ If user declines CI/CD:
 
 **Symptom**:
 ```
-Error: Cannot create trinity/work-orders/
-Parent directory 'trinity/' does not exist
+Error: Cannot create .claude/trinity/work-orders/
+Parent directory '.claude/trinity/' does not exist
 ```
 
 **Cause**: Project root mismatch or permissions
@@ -609,17 +608,17 @@ pwd
 cd /path/to/project
 
 # Create manually if needed
-mkdir -p trinity/work-orders
-mkdir -p trinity/sessions
-mkdir -p trinity/planning
-mkdir -p trinity/reports
+mkdir -p .claude/trinity/work-orders
+mkdir -p .claude/trinity/sessions
+mkdir -p .claude/trinity/planning
+mkdir -p .claude/trinity/reports
 ```
 
 ### Issue 2: Agents Directory Incomplete
 
 **Symptom**:
 ```
-Warning: Only 15 of 19 agents deployed
+Warning: Only 15 of 18 agents deployed
 Missing: INO, EIN, APO, BON
 ```
 
@@ -652,7 +651,7 @@ ls -la .claude/
 
 # Fix permissions (Unix/Mac)
 chmod -R 755 .claude/
-chmod -R 755 trinity/
+chmod -R 755 .claude/trinity/
 
 # Windows: Right-click → Properties → Security → Edit
 ```

package/dist/templates/.claude/agents/deployment/zen-knowledge.md.template

@@ -50,7 +50,7 @@ You are **ZEN**, Trinity Method v2.0 Knowledge Base Specialist for {{PROJECT_NAM
 
 ### Phase 1: Create ARCHITECTURE.md
 
-Location: `trinity/knowledge-base/ARCHITECTURE.md`
+Location: `.claude/trinity/knowledge-base/ARCHITECTURE.md`
 
 ```markdown
 # {{PROJECT_NAME}} - Architecture
@@ -89,7 +89,7 @@ Location: `trinity/knowledge-base/ARCHITECTURE.md`
 ```
 {{PROJECT_NAME}}/
 ├── {{SOURCE_DIR}}/              # Application source
-├── trinity/
+├── .claude/trinity/
 │   ├── knowledge-base/          # Documentation + Best Practices (v2.0)
 │   │   ├── ARCHITECTURE.md (this file)
 │   │   ├── ISSUES.md
@@ -149,7 +149,7 @@ See: `docs/plans/adrs/` for Architecture Decision Records created by ROR agent d
 
 ### Phase 2: Create Trinity.md
 
-Location: `trinity/knowledge-base/Trinity.md`
+Location: `.claude/trinity/knowledge-base/Trinity.md`
 
 ```markdown
 # {{PROJECT_NAME}} - Trinity Method v2.0
@@ -217,10 +217,9 @@ Trinity v2.0 adapts implementation approach based on scope:
 5. Update knowledge base documentation
 
 **Work Order System (Legacy):**
-- Investigation orders: trinity/work-orders/
-- Work order templates: trinity/templates/work-orders/
-- Investigation templates: trinity/templates/investigations/
-- Patterns: trinity/patterns/
+- Investigation orders: .claude/trinity/work-orders/
+- Work order templates: .claude/trinity/templates/work-orders/
+- Investigation templates: .claude/trinity/templates/investigations/
 - *Note: v2.0 uses scale-based workflows, work orders optional*
 
 ### Quality Standards (v2.0)
@@ -232,7 +231,7 @@ Trinity v2.0 adapts implementation approach based on scope:
 - Try-catch wraps all async operations
 - No code duplication (DRY principle)
 
-**See:** `trinity/knowledge-base/CODING-PRINCIPLES.md`
+**See:** `.claude/trinity/knowledge-base/CODING-PRINCIPLES.md`
 
 **Testing Quality (enforced by BAS Phase 4-5):**
 - TDD cycle: RED-GREEN-REFACTOR mandatory
@@ -240,14 +239,14 @@ Trinity v2.0 adapts implementation approach based on scope:
 - Independent tests (no interdependencies)
 - Test names descriptive and clear
 
-**See:** `trinity/knowledge-base/TESTING-PRINCIPLES.md`
+**See:** `.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md`
 
 **AI Development (scale workflows):**
 - Small scale: Direct implementation, 0 stops
 - Medium scale: Design + tasks, 2 stops
 - Large scale: Full planning (PRD + ADR + design + plan + tasks), 4 stops
 
-**See:** `trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md`
+**See:** `.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md`
 
 **Documentation Quality:**
 - Architecture: Always current
@@ -256,13 +255,13 @@ Trinity v2.0 adapts implementation approach based on scope:
 - Issues: Catalogued with patterns
 - Scale-based requirements
 
-**See:** `trinity/knowledge-base/DOCUMENTATION-CRITERIA.md`
+**See:** `.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md`
 
 ## Trinity v2.0 Structure
 
 ```
 {{PROJECT_NAME}}/
-├── trinity/
+├── .claude/trinity/
 │   ├── knowledge-base/
 │   │   ├── ARCHITECTURE.md
 │   │   ├── Trinity.md (this file)
@@ -300,7 +299,7 @@ Trinity v2.0 adapts implementation approach based on scope:
 
 ### Phase 3: Create To-do.md
 
-Location: `trinity/knowledge-base/To-do.md`
+Location: `.claude/trinity/knowledge-base/To-do.md`
 
 ```markdown
 # {{PROJECT_NAME}} - Tasks
@@ -345,19 +344,19 @@ When adding new tasks, estimate scale:
 
 ## Technical Debt
 
-See: `trinity/knowledge-base/Technical-Debt.md` for comprehensive debt tracking with v2.0 compliance checks.
+See: `.claude/trinity/knowledge-base/Technical-Debt.md` for comprehensive debt tracking with v2.0 compliance checks.
 
 ## Best Practices Documents (v2.0)
 
 Reference these for all implementations:
-- `trinity/knowledge-base/CODING-PRINCIPLES.md` - Code quality standards
-- `trinity/knowledge-base/TESTING-PRINCIPLES.md` - TDD methodology
-- `trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md` - Scale workflows
-- `trinity/knowledge-base/DOCUMENTATION-CRITERIA.md` - Doc requirements
+- `.claude/trinity/knowledge-base/CODING-PRINCIPLES.md` - Code quality standards
+- `.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md` - TDD methodology
+- `.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md` - Scale workflows
+- `.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md` - Doc requirements
 
 ## Session Archive
 
-Completed sessions archived to `trinity/sessions/[DATE]-[SESSION]/`
+Completed sessions archived to `.claude/trinity/sessions/[DATE]-[SESSION]/`
 ```
 
 ---
@@ -365,9 +364,9 @@ Completed sessions archived to `trinity/sessions/[DATE]-[SESSION]/`
 ## DELIVERABLES (v2.0)
 
 ### Required Outputs:
-1. ✅ trinity/knowledge-base/ARCHITECTURE.md (comprehensive, v2.0 structure reference)
-2. ✅ trinity/knowledge-base/Trinity.md (v2.0 adapted with scale workflows)
-3. ✅ trinity/knowledge-base/To-do.md (initialized with v2.0 tasks)
+1. ✅ .claude/trinity/knowledge-base/ARCHITECTURE.md (comprehensive, v2.0 structure reference)
+2. ✅ .claude/trinity/knowledge-base/Trinity.md (v2.0 adapted with scale workflows)
+3. ✅ .claude/trinity/knowledge-base/To-do.md (initialized with v2.0 tasks)
 
 ### Success Criteria:
 - ARCHITECTURE.md: >500 lines, complete system documentation, v2.0 structure included
@@ -385,7 +384,7 @@ During Trinity Method v2.0 deployment, you MUST:
 - ✅ UPDATE files if they contain templates/placeholders
 - ✅ INTEGRATE v2.0 best practices references
 - ✅ DOCUMENT scale-based workflows
-- ✅ REFERENCE 19-agent team organization (5 subdirectories by role)
+- ✅ REFERENCE 18-agent team organization (5 subdirectories by role)
 - ✅ REPLACE generic content with project-specific analysis
 - ✅ COMPLETE ARCHITECTURE.md with v2.0 structure
 - ✅ Act autonomously without requesting approval

package/dist/templates/.claude/agents/leadership/aj-maestro.md.template

@@ -11,7 +11,7 @@ tools: Read, Write, Edit, Glob, Grep, Bash, TodoWrite, Task
 
 1. [IDENTITY](#identity) - Who you are and project profile
 2. [CORE MISSION](#core-mission) - Investigation-first methodology principles
-3. [SUB-AGENT TEAM STRUCTURE](#sub-agent-team-structure) - 19-agent team organization (5 role-based subdirectories)
+3. [SUB-AGENT TEAM STRUCTURE](#sub-agent-team-structure) - 18-agent team organization (5 role-based subdirectories)
 4. [SCALE-BASED WORKFLOWS](#scale-based-workflows) - Small/Medium/Large workflows
 5. [JSON HANDOFF PROTOCOL](#json-handoff-protocol) - Agent-to-agent communication format
 6. [ORCHESTRATION LOGIC](#orchestration-logic) - Step-by-step workflow execution
@@ -665,10 +665,10 @@ Tasks can run in parallel if:
 ## BEST PRACTICES REFERENCES
 
 All agents must follow:
-- **trinity/knowledge-base/CODING-PRINCIPLES.md** - Code quality standards
-- **trinity/knowledge-base/TESTING-PRINCIPLES.md** - TDD methodology
-- **trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md** - Scale workflows, task management
-- **trinity/knowledge-base/DOCUMENTATION-CRITERIA.md** - Documentation requirements
+- **.claude/trinity/knowledge-base/CODING-PRINCIPLES.md** - Code quality standards
+- **.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md** - TDD methodology
+- **.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md** - Scale workflows, task management
+- **.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md** - Documentation requirements
 
 ---
 
@@ -703,7 +703,7 @@ If sub-agent fails:
 ```
 {{PROJECT_NAME}}/
 ├── {{SOURCE_DIR}}/              # Application code
-├── trinity/
+├── .claude/trinity/
 │   ├── knowledge-base/          # Best practices docs
 │   │   ├── CODING-PRINCIPLES.md
 │   │   ├── TESTING-PRINCIPLES.md

package/dist/templates/.claude/agents/leadership/aly-cto.md.template

@@ -44,7 +44,7 @@ You are **Aly**, Chief Technology Officer for {{PROJECT_NAME}}.
 - Validate DRA compliance reports after phases
 
 ### 3. Knowledge Base Management
-- Maintain trinity/knowledge-base/ documentation
+- Maintain .claude/trinity/knowledge-base/ documentation
 - Update best practices documents (CODING, TESTING, AI-DEV, DOCS)
 - Track issues, technical debt, and architectural decisions
 - Ensure documentation stays current after each session
@@ -96,35 +96,34 @@ You are **Aly**, Chief Technology Officer for {{PROJECT_NAME}}.
 ### Best Practices Documents (v2.0)
 
 All agents and implementations must follow:
-- **trinity/knowledge-base/CODING-PRINCIPLES.md** - Code quality standards (≤2 params, try-catch, etc.)
-- **trinity/knowledge-base/TESTING-PRINCIPLES.md** - TDD methodology (RED-GREEN-REFACTOR)
-- **trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md** - Scale workflows, quality gates, task management
-- **trinity/knowledge-base/DOCUMENTATION-CRITERIA.md** - Documentation requirements by scale
+- **.claude/trinity/knowledge-base/CODING-PRINCIPLES.md** - Code quality standards (≤2 params, try-catch, etc.)
+- **.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md** - TDD methodology (RED-GREEN-REFACTOR)
+- **.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md** - Scale workflows, quality gates, task management
+- **.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md** - Documentation requirements by scale
 
 ### Knowledge Base Management
 
 All project knowledge lives in:
-- `trinity/knowledge-base/ARCHITECTURE.md` - System design and architecture decisions
-- `trinity/knowledge-base/ISSUES.md` - Known problems and their status
-- `trinity/knowledge-base/To-do.md` - Task tracking and priorities
-- `trinity/knowledge-base/Technical-Debt.md` - Debt management and paydown plans
-- `trinity/knowledge-base/CODING-PRINCIPLES.md` - Code standards (v2.0)
-- `trinity/knowledge-base/TESTING-PRINCIPLES.md` - TDD standards (v2.0)
-- `trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md` - AI workflows (v2.0)
-- `trinity/knowledge-base/DOCUMENTATION-CRITERIA.md` - Doc standards (v2.0)
+- `.claude/trinity/knowledge-base/ARCHITECTURE.md` - System design and architecture decisions
+- `.claude/trinity/knowledge-base/ISSUES.md` - Known problems and their status
+- `.claude/trinity/knowledge-base/To-do.md` - Task tracking and priorities
+- `.claude/trinity/knowledge-base/Technical-Debt.md` - Debt management and paydown plans
+- `.claude/trinity/knowledge-base/CODING-PRINCIPLES.md` - Code standards (v2.0)
+- `.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md` - TDD standards (v2.0)
+- `.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md` - AI workflows (v2.0)
+- `.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md` - Doc standards (v2.0)
 
 **Keep these files always updated** after each session, major decision, and phase completion.
 
 ---
 
-## AJ MAESTRO & THE 19-AGENT TEAM
+## AJ MAESTRO & THE 18-AGENT TEAM
 
 ### Team Structure (5 Role-Based Subdirectories)
 
-**Leadership Tier** (3 agents):
+**Leadership Tier** (2 agents):
 - **ALY** (CTO) - Strategic leadership and AJ MAESTRO coordination
 - **AJ MAESTRO** - Implementation orchestration
-- **AJ CC** - Continuous context and session continuity
 
 **Deployment Team** (4 agents):
 - **TAN** - Trinity folder structure deployment
@@ -327,7 +326,7 @@ APPROVED - Proceed with merge
 **Deployed:** {{DEPLOYMENT_TIMESTAMP}}
 **Project:** {{PROJECT_NAME}}
 **Framework:** {{FRAMEWORK}}
-**AJ MAESTRO Integration:** v2.0 (19-agent orchestration)
+**AJ MAESTRO Integration:** v2.0 (18-agent orchestration)
 **Quality Gates:** BAS 6-phase + DRA compliance validation
 
 ---
@@ -347,7 +346,7 @@ APPROVED - Proceed with merge
 - ❌ NOT: Technical implementation details
 
 **AJ MAESTRO (Tactical)**:
-- ✅ Orchestrate 19-agent team
+- ✅ Orchestrate 18-agent team
 - ✅ Coordinate planning agents (MON, ROR, TRA, EUS)
 - ✅ Execute implementation (KIL, BAS, DRA)
 - ✅ Handle execution errors

package/dist/templates/.claude/agents/planning/eus-decomposer.md.template

@@ -108,10 +108,10 @@ Decompose implementation plans into atomic tasks following the "1 task = 1 commi
 ## TRINITY V2.0 BEST PRACTICES
 
 ### Reference Documents
-- **Coding Standards:** [trinity/knowledge-base/CODING-PRINCIPLES.md](trinity/knowledge-base/CODING-PRINCIPLES.md)
-- **Testing Standards:** [trinity/knowledge-base/TESTING-PRINCIPLES.md](trinity/knowledge-base/TESTING-PRINCIPLES.md)
-- **AI Development Guide:** [trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
-- **Documentation Standards:** [trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
+- **Coding Standards:** [.claude/trinity/knowledge-base/CODING-PRINCIPLES.md](.claude/trinity/knowledge-base/CODING-PRINCIPLES.md)
+- **Testing Standards:** [.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md](.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md)
+- **AI Development Guide:** [.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
+- **Documentation Standards:** [.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
 
 ### Decomposition Principles
 

package/dist/templates/.claude/agents/planning/mon-requirements.md.template

@@ -105,10 +105,10 @@ User request describing desired functionality or changes
 ## TRINITY V2.0 BEST PRACTICES
 
 ### Reference Documents
-- **Coding Standards:** [trinity/knowledge-base/CODING-PRINCIPLES.md](trinity/knowledge-base/CODING-PRINCIPLES.md)
-- **Testing Standards:** [trinity/knowledge-base/TESTING-PRINCIPLES.md](trinity/knowledge-base/TESTING-PRINCIPLES.md)
-- **AI Development Guide:** [trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
-- **Documentation Standards:** [trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
+- **Coding Standards:** [.claude/trinity/knowledge-base/CODING-PRINCIPLES.md](.claude/trinity/knowledge-base/CODING-PRINCIPLES.md)
+- **Testing Standards:** [.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md](.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md)
+- **AI Development Guide:** [.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
+- **Documentation Standards:** [.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
 
 ### Key Principles
 

package/dist/templates/.claude/agents/planning/ror-design.md.template

@@ -135,10 +135,10 @@ Transform requirements into detailed technical designs with clear function signa
 ## TRINITY V2.0 BEST PRACTICES
 
 ### Reference Documents
-- **Coding Standards:** [trinity/knowledge-base/CODING-PRINCIPLES.md](trinity/knowledge-base/CODING-PRINCIPLES.md)
-- **Testing Standards:** [trinity/knowledge-base/TESTING-PRINCIPLES.md](trinity/knowledge-base/TESTING-PRINCIPLES.md)
-- **AI Development Guide:** [trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
-- **Documentation Standards:** [trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
+- **Coding Standards:** [.claude/trinity/knowledge-base/CODING-PRINCIPLES.md](.claude/trinity/knowledge-base/CODING-PRINCIPLES.md)
+- **Testing Standards:** [.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md](.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md)
+- **AI Development Guide:** [.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
+- **Documentation Standards:** [.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
 
 ### Design Principles (DRA Compliance)
 

package/dist/templates/.claude/agents/planning/tra-planner.md.template

@@ -125,10 +125,10 @@ Transform technical designs into executable implementation plans with optimal ta
 ## TRINITY V2.0 BEST PRACTICES
 
 ### Reference Documents
-- **Coding Standards:** [trinity/knowledge-base/CODING-PRINCIPLES.md](trinity/knowledge-base/CODING-PRINCIPLES.md)
-- **Testing Standards:** [trinity/knowledge-base/TESTING-PRINCIPLES.md](trinity/knowledge-base/TESTING-PRINCIPLES.md)
-- **AI Development Guide:** [trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
-- **Documentation Standards:** [trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
+- **Coding Standards:** [.claude/trinity/knowledge-base/CODING-PRINCIPLES.md](.claude/trinity/knowledge-base/CODING-PRINCIPLES.md)
+- **Testing Standards:** [.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md](.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md)
+- **AI Development Guide:** [.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md](.claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md)
+- **Documentation Standards:** [.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md](.claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md)
 
 ### Planning Principles
 

package/dist/templates/.claude/commands/execution/trinity-audit.md.template

@@ -28,8 +28,8 @@
 - ✅ **Tool-based:** Uses actual linters/scanners, not just file reading
 
 **Deliverable:**
-- `trinity/reports/CODEBASE-AUDIT-{date}.md` (human-readable report)
-- `trinity/reports/AUDIT-BASELINE-{date}.json` (machine-readable baseline for future comparisons)
+- `.claude/trinity/reports/CODEBASE-AUDIT-{date}.md` (human-readable report)
+- `.claude/trinity/reports/AUDIT-BASELINE-{date}.json` (machine-readable baseline for future comparisons)
 
 ---
 
@@ -56,7 +56,7 @@
 
 ### ⚠️ Second Audit Behavior:
 
-When a baseline exists (`trinity/reports/AUDIT-BASELINE-*.json`):
+When a baseline exists (`.claude/trinity/reports/AUDIT-BASELINE-*.json`):
 - **FIXED issues:** ✅ Marked as resolved (celebrate!)
 - **NEW issues:** ⚠️ Flagged as introduced since last audit
 - **PERSISTENT issues:** 🔴 Still present from previous audit
@@ -75,7 +75,7 @@ JUNO follows a **strict, repeatable process** to ensure consistent results:
 
 ```bash
 # Check for existing baseline
-IF trinity/reports/AUDIT-BASELINE-*.json exists:
+IF .claude/trinity/reports/AUDIT-BASELINE-*.json exists:
   - Load previous findings
   - Track what's been fixed ✅
   - Track what's new ⚠️
@@ -425,7 +425,7 @@ IF baseline exists:
 
 **Two files created:**
 
-#### 1. Human-Readable Report: `trinity/reports/CODEBASE-AUDIT-{date}.md`
+#### 1. Human-Readable Report: `.claude/trinity/reports/CODEBASE-AUDIT-{date}.md`
 
 ```markdown
 # Codebase Audit Report
@@ -503,10 +503,10 @@ Expected result: "0 new issues, 0 persistent issues, X fixed issues"
 
 **Audit Complete:** {timestamp}
 **Confidence:** {HIGH|MEDIUM|LOW}
-**Baseline Saved:** trinity/reports/AUDIT-BASELINE-{date}.json
+**Baseline Saved:** .claude/trinity/reports/AUDIT-BASELINE-{date}.json
 ```
 
-#### 2. Machine-Readable Baseline: `trinity/reports/AUDIT-BASELINE-{date}.json`
+#### 2. Machine-Readable Baseline: `.claude/trinity/reports/AUDIT-BASELINE-{date}.json`
 
 ```json
 {
@@ -599,8 +599,8 @@ JUNO: Loading previous audit baseline...
 
 **Recommendation:** You're done! The codebase is in excellent shape.
 
-**Audit saved:** trinity/reports/CODEBASE-AUDIT-2025-12-21.md
-**Baseline updated:** trinity/reports/AUDIT-BASELINE-2025-12-21.json
+**Audit saved:** .claude/trinity/reports/CODEBASE-AUDIT-2025-12-21.md
+**Baseline updated:** .claude/trinity/reports/AUDIT-BASELINE-2025-12-21.json
 ```
 
 **This is how the cycle ends.**