@sandrinio/vbounce 2.0.0 → 2.1.0

package/README.md

@@ -29,7 +29,7 @@ Every risk that keeps you up at night has a specific mechanism that catches it:
 | Risk | What catches it |
 |------|----------------|
 | Agent ships code that doesn't match requirements | **QA gate** — validates every story against acceptance criteria before merge |
-| Architectural drift over time | **Architect gate** — audits against your ADRs and safe-zone rules on every story |
+| Architectural drift over time | **Architect gate** — audits against your ADRs on every story |
 | One bad story breaks everything | **Git worktrees** — every story is isolated; failures can't contaminate other work |
 | Agent gets stuck in a loop | **3-bounce escalation** — after 3 failed attempts, the story surfaces to a human |
 | Scope creep on "quick fixes" | **Hotfix hard-stop** — Developer must stop if a fix touches more than 2 files |
@@ -285,7 +285,7 @@ Five specialist agents, each with a single job and strict boundaries:
 |-------|-------------|-------------|
 | **Developer** | Implements stories in isolated worktrees, submits implementation reports | Works only in its assigned worktree |
 | **QA** | Validates code against acceptance criteria | Read-only — cannot modify code |
-| **Architect** | Audits against ADRs, architecture rules, and safe-zone boundaries | Read-only — cannot modify code |
+| **Architect** | Audits against ADRs and architecture rules | Read-only — cannot modify code |
 | **DevOps** | Merges passing stories into the sprint branch | Only acts after both gates pass |
 | **Scribe** | Generates and maintains product documentation from the actual codebase | Only runs after merge |
 
@@ -322,25 +322,30 @@ your-project/
 │   ├── architect.md
 │   ├── devops.md
 │   └── scribe.md
-├── templates/                   # 9 Markdown + YAML frontmatter templates
+├── templates/                   # 12 Markdown + YAML frontmatter templates
 │   ├── charter.md
 │   ├── roadmap.md
 │   ├── epic.md
 │   ├── story.md
+│   ├── spike.md
 │   ├── sprint.md
 │   ├── delivery_plan.md
 │   ├── sprint_report.md
 │   ├── hotfix.md
+│   ├── bug.md
+│   ├── change_request.md
 │   └── risk_registry.md
-├── skills/                      # 7 modular skill files (see Skills below)
+├── skills/                      # 9 modular skill files (see Skills below)
 │   ├── agent-team/
 │   ├── doc-manager/
+│   ├── product-graph/
 │   ├── lesson/
 │   ├── vibe-code-review/
 │   ├── write-skill/
 │   ├── improve/
+│   ├── file-organization/
 │   └── react-best-practices/   # Example — customize for your stack
-├── scripts/                     # 23 automation scripts (validation, context prep, state)
+├── scripts/                     # 26 automation scripts (validation, context prep, state, graph)
 └── package.json                 # 3 deps: js-yaml, marked, commander. Nothing else.
 ```
 
@@ -397,11 +402,13 @@ Skills are modular markdown instructions the Team Lead invokes automatically dur
 | Skill | Purpose |
 |-------|---------|
 | `agent-team` | Spawns temporary sub-agents (Dev, QA, Architect, DevOps, Scribe) to parallelize work |
-| `doc-manager` | Enforces the document hierarchy for Epics and Stories |
+| `doc-manager` | Enforces the document hierarchy, cascade rules, and planning workflows |
+| `product-graph` | Dependency-aware document intelligence — knows what's blocked, what's affected by changes |
 | `lesson` | Extracts mistakes from sprints into `LESSONS.md` |
 | `vibe-code-review` | Runs Quick Scan or Deep Audit against acceptance criteria and architecture rules |
 | `write-skill` | Allows the Team Lead to author new skills when the team encounters a recurring problem |
 | `improve` | Self-improvement loop — reads agent friction signals across sprints and proposes framework changes (with your approval) |
+| `file-organization` | File structure management and organization verification |
 | `react-best-practices` | Example tech-stack skill — customize this for your own stack |
 
 ---
@@ -443,6 +450,10 @@ vbounce story complete STORY-ID       # Mark story done, update state
 vbounce state show                    # Print current state
 vbounce state update STORY-ID STATE   # Update story state
 
+# Product graph
+vbounce graph                         # Generate document dependency graph
+vbounce graph impact EPIC-002         # Show what's affected by a change
+
 # Context preparation
 vbounce prep sprint S-01              # Sprint context pack
 vbounce prep qa STORY-ID              # QA context pack
@@ -479,6 +490,7 @@ product_plans/                   # Created when you start planning
 
 .bounce/                         # Created on first sprint init
   state.json                     #   Machine-readable sprint state (crash recovery)
+  product-graph.json             #   Document dependency graph (auto-generated)
   reports/                       #   QA and Architect bounce reports
   improvement-manifest.json      #   Machine-readable improvement proposals (auto-generated)
   improvement-suggestions.md     #   Human-readable suggestions with impact levels (auto-generated)
@@ -502,7 +514,7 @@ LESSONS.md                       # Accumulated mistakes — agents read this bef
 | **Escalation** | When a story hits the 3-bounce limit and surfaces to a human for intervention |
 | **Gate** | An automated quality checkpoint — QA validates requirements, Architect validates structure |
 | **Hotfix Path** | A fast track for trivial (L1) changes: 1-2 files, no QA/Architect gates, human verifies directly |
-| **L1–L4** | Complexity labels: L1 Trivial, L2 Standard, L3 Complex, L4 Strategic |
+| **L1–L4** | Complexity labels: L1 Trivial, L2 Standard, L3 Complex, L4 Uncertain |
 | **Root Cause Tag** | A label on every bounce failure (e.g., `missing_tests`, `adr_violation`) used for trend analysis |
 | **Scribe** | The documentation agent that maps code into semantic product docs |
 | **Sprint Report** | End-of-sprint summary: what shipped, metrics, bounce analysis, lessons, retrospective |

package/bin/vbounce.mjs

@@ -82,6 +82,8 @@ Usage:
   vbounce prep qa <storyId>            Generate QA context pack
   vbounce prep arch <storyId>          Generate Architect context pack
   vbounce prep sprint <sprintId>       Generate Sprint context pack
+  vbounce graph [generate]              Generate product document graph
+  vbounce graph impact <DOC-ID>         Show what's affected by a document change
   vbounce docs match --story <ID>      Match story scope against vdoc manifest
   vbounce docs check <sprintId>        Detect stale vdocs and generate Scribe task
   vbounce trends                       Cross-sprint trend analysis
@@ -216,6 +218,20 @@ if (command === 'improve') {
   runScript('suggest_improvements.mjs', [sprintArg]);
 }
 
+// -- graph --
+if (command === 'graph') {
+  rl.close();
+  if (sub === 'impact') {
+    runScript('product_impact.mjs', args.slice(2));
+  } else if (!sub || sub === 'generate') {
+    runScript('product_graph.mjs', args.slice(2));
+  } else {
+    console.error(`Unknown graph subcommand: ${sub}`);
+    console.error('Usage: vbounce graph [generate] | vbounce graph impact <DOC-ID>');
+    process.exit(1);
+  }
+}
+
 // -- docs --
 if (command === 'docs') {
   rl.close();
@@ -561,6 +577,13 @@ if (command === 'install') {
       console.log(`  \x1b[32m✓\x1b[0m ${rule.dest}`);
     }
 
+    // Create LESSONS.md if missing
+    const lessonsPath = path.join(CWD, 'LESSONS.md');
+    if (!fs.existsSync(lessonsPath)) {
+      fs.writeFileSync(lessonsPath, '# Lessons Learned\n\nProject-specific lessons recorded after each story merge. Read this before writing code.\n');
+      console.log(`  \x1b[32m✓\x1b[0m LESSONS.md (created)`);
+    }
+
     // Write install metadata
     writeInstallMeta(pkgVersion, targetPlatform, installedFiles, hashes);
     console.log(`  \x1b[32m✓\x1b[0m .bounce/install-meta.json`);

package/brains/AGENTS.md

@@ -12,167 +12,60 @@ You have two roles depending on the phase:
 
 You MUST follow the V-Bounce process. Deviating from it — skipping validation, ignoring LESSONS.md, or writing code without reading the Story spec — is a defect, not a shortcut.
 
-## Skills
-
-Skills are in the `skills/` directory. Each skill has a `SKILL.md` with instructions. Read the relevant SKILL.md before performing any skill-related task.
-
-| Skill | Purpose | Used By |
-|-------|---------|---------|
-| `skills/agent-team/` | Subagent orchestration and delegation | Team Lead |
-| `skills/doc-manager/` | Document hierarchy navigation and lifecycle | Team Lead, all agents |
-| `skills/lesson/` | Recording project-specific mistakes and rules | All agents (read), Team Lead (write) |
-| `skills/react-best-practices/` | Frontend coding patterns and anti-patterns | Developer |
-| `skills/vibe-code-review/` | Code quality review (4 modes) | QA, Architect |
-| `skills/write-skill/` | Creating and refining agent skills | Team Lead |
-| `skills/improve/` | Framework self-improvement from agent feedback | Team Lead |
-
-## The V-Bounce Process
-
-The process has four phases. You determine which phase to operate in based on what the human is asking for.
-
-### Phase 1: Planning (AI + Human — No Subagents)
-
-**When to enter:** The human talks about what to build, asks to create or modify planning documents, discusses features, priorities, or asks about work status. This is a direct conversation — no subagents.
-
-Read `skills/doc-manager/SKILL.md` and follow its workflows.
-
-**Document hierarchy** — no level can be skipped:
-Charter (why) → Roadmap (strategic what/when) → Epic (detailed what) → Story (how) → Delivery Plan (execution) → Risk Registry (risks)
-
-**Your responsibilities during planning:**
-1. **Creating documents:** Read upstream documents, research the codebase, draft the document. Follow doc-manager's CREATE and DECOMPOSE workflows.
-2. **Surfacing problems:** Assess ambiguity, open questions, edge cases, and risks. Present these clearly to the human — this is collaborative.
-3. **Answering status questions:** Read `product_plans/` to understand current state (backlog/, sprints/, archive/, strategy/).
-4. **Triaging requests:** L1 Trivial → Hotfix Path. Everything else → Standard Path (Epic → Story → Sprint).
-
-### Phase 2: Sprint Planning (AI + Human — Collaborative Gate)
-
-**When to enter:** The human wants to start executing work — "let's start a sprint", "what should we work on next?"
-
-**Hard rule: No bounce can start without a finalized, human-confirmed Sprint Plan.**
-
-1. Read backlog, archive, Risk Registry, vdocs manifest
-2. Propose sprint scope based on priority, dependencies, complexity
-3. Surface blockers: open questions, 🔴 ambiguity, missing prerequisites, risks, edge cases
-4. Discuss and refine with human
-5. Create Sprint Plan from `templates/sprint.md` — fill §0 Readiness Gate, §1 Active Scope, §2 Execution Strategy, §3 Open Questions
-6. **Gate:** Human confirms the Sprint Plan. Only then set status to "Active"
-
-**Strategic Freeze:** Charter/Roadmap frozen during sprints. Use **Impact Analysis Protocol** if emergency changes occur. Pause until human approval.
+## Phase Routing
 
-### Phase 3: The Bounce (Execution)
-**Standard Path (L2-L4 Stories):**
-0. **Orient via state**: Read `.bounce/state.json` (`vbounce state show`) for instant context. Run `vbounce prep sprint S-{XX}` to generate a fresh context pack.
-1. Team Lead sends Story context pack to Developer.
-2. Developer reads LESSONS.md and the Story context pack, implements code, writes Implementation Report. CLI Orchestrator must run `./scripts/validate_report.mjs` on the report to enforce YAML strictness.
-3. **Pre-QA Gate Scan:** Team Lead runs `./scripts/pre_gate_runner.sh qa` to catch mechanical failures before spawning QA. If trivial issues → return to Dev.
-4. QA runs Quick Scan + PR Review (skipping pre-scanned checks), validates against Story §2 The Truth. If fail → Bug Report to Dev. CLI Orchestrator must run `./scripts/validate_report.mjs` on the QA report.
-5. Dev fixes and resubmits. 3+ failures → Escalated (see Escalation Recovery below).
-6. **Pre-Architect Gate Scan:** Team Lead runs `./scripts/pre_gate_runner.sh arch` to catch structural issues before spawning Architect. If mechanical failures → return to Dev.
-7. Architect runs Deep Audit + Trend Check (skipping pre-scanned checks), validates Safe Zone compliance and ADR adherence.
-8. DevOps merges story branch into sprint branch, validates post-merge (tests + lint + build), handles release tagging.
-9. **Record lessons immediately**: After DevOps merge, check Dev and QA reports for `lessons_flagged`. Record to LESSONS.md now — do not wait for sprint close.
-10. Team Lead consolidates reports into Sprint Report.
+Determine which phase you're in from what the human is asking, then load the right skill.
 
-**Hotfix Path (L1 Trivial Tasks):**
-1. Team Lead evaluates request and creates `HOTFIX-{Date}-{Name}.md`.
-2. Developer reads LESSONS.md and Hotfix spec, makes the targeted change (max 1-2 files).
-3. Developer runs `./scripts/hotfix_manager.sh ledger "{Title}" "{Description}"`.
-4. Human/Team Lead manually verifies the fix. QA/Architect bounce loops are bypassed.
-5. Hotfix is merged directly into the active branch.
-6. DevOps (or Team Lead) runs `./scripts/hotfix_manager.sh sync` to update active worktrees.
+| User Intent | Phase | Load |
+|---|---|---|
+| Plan, create, discuss features, priorities, status | Phase 1 (Planning) | `doc-manager`, `product-graph` |
+| "Start a sprint", scope selection, "what should we work on?" | Phase 2 (Sprint Planning) | `doc-manager`, `product-graph` |
+| Sprint confirmed, "bounce", implement stories | Phase 3 (Execution) | `agent-team` |
+| Review sprint, retrospective, improvement | Phase 4 (Review) | `improve` |
+| Scope change to existing documents | Any | `product-graph` (impact first), then `doc-manager` |
+| Code review | Any | `vibe-code-review` |
+| Lesson or gotcha to record | Any | `lesson` |
 
-**Escalation Recovery (3+ bounce failures):**
-1. Mark story as "Escalated" in Sprint Plan
-2. Present to human: what failed, root causes from bounce reports, pattern analysis
-3. Propose options: re-scope the story, split into smaller stories, create a spike, or remove from sprint
-4. Human decides. Execute the decision.
-
-### Phase 4: Review
-Sprint Report → Human review → Delivery Plan updated (at boundary only) → Lessons recorded → Next sprint.
-If sprint delivered new features or Dev reports flagged stale product docs → spawn Scribe agent to generate/update vdocs/ via vdoc.
-
-**Self-Improvement Pipeline** (auto-runs on `vbounce sprint close`):
-1. `sprint_trends.mjs` → cross-sprint trend analysis → `.bounce/trends.md`
-2. `post_sprint_improve.mjs` → parses §5 retro tables + LESSONS.md automation candidates + recurring patterns + effectiveness checks → `.bounce/improvement-manifest.json`
-3. `suggest_improvements.mjs` → generates human-readable suggestions with impact levels → `.bounce/improvement-suggestions.md`
-4. Human reviews suggestions → approve/reject/defer each item
-5. Run `/improve` to apply approved changes with brain-file sync
-
-**Impact Levels:** P0 Critical (blocks agents), P1 High (causes rework), P2 Medium (friction), P3 Low (polish). See `/improve` skill for details.
+## Critical Rules
 
-On-demand: `vbounce improve S-{XX}` runs the full pipeline.
+### Before Writing Code
+1. **Read LESSONS.md** at the project root. Every time. No exceptions.
+2. **Read the Story spec** (§1 The Spec + §3 Implementation Guide). Do not infer requirements.
+3. **Check ADRs** in the Roadmap (§3). Comply with recorded architecture decisions.
 
-## Story States
+### During Implementation
+4. **Comply with ADRs**. No new patterns or libraries unless approved in Roadmap §3. The Architect validates compliance.
+5. **No Gold-Plating**. Implement exactly what the Story specifies.
+6. **Write Self-Documenting Code**. All exports MUST have JSDoc/docstrings.
+7. **Self-assess Correction Tax**. Track % human intervention.
 
-Draft → Refinement → Ready to Bounce → Bouncing → QA Passed → Architect Passed → Sprint Review → Done
-Refinement → Probing/Spiking → Refinement (L4 spike loop)
-Any → Parking Lot (deferred)
-Bouncing → Escalated (3+ failures)
+### After Implementation
+8. **Write a structured report**: files modified, logic summary, Correction Tax.
+9. **Flag lessons**. Gotchas and multi-attempt fixes get flagged for recording.
 
-## Complexity Labels
+### Always
+10. **Reports are the only handoff**. No direct agent-to-agent communication.
+11. **One source of truth**. Reference upstream documents, don't duplicate.
+12. **Change Logs are mandatory** on every document modification.
+13. **Agent Reports MUST use YAML Frontmatter**. Every `.bounce/report/` file starts with strict YAML.
+14. **Framework Integrity**. Any modification to `brains/`, `skills/`, `templates/`, or `scripts/` MUST be recorded in `brains/CHANGELOG.md` and reflected in `MANIFEST.md`.
 
-- L1: Trivial — Single file, <1hr, known pattern.
-- L2: Standard — 2-3 files, known pattern, ~2-4hr. (default)
-- L3: Complex — Cross-cutting, spike may be needed, ~1-2 days.
-- L4: Uncertain — Requires Probing/Spiking before Bounce, >2 days.
+## Skills
 
-## Critical Rules
+Skills are in the `skills/` directory. Each skill has a `SKILL.md` with instructions.
 
-### Before Writing Code
-1. Read LESSONS.md at the project root. Every time. No exceptions.
-2. Read the Story spec (§1 The Spec + §3 Implementation Guide). Do not infer requirements.
-3. Check ADRs in the Roadmap (§3). Comply with recorded architecture decisions.
+**Loaded by phase** (see Phase Routing above):
+- **Always:** Read `skills/lesson/SKILL.md`
+- **Planning (Phase 1 & 2):** Read `skills/doc-manager/SKILL.md` + `skills/product-graph/SKILL.md`
+- **Execution (Phase 3):** Read `skills/agent-team/SKILL.md`
 
-### During Implementation
-4. Follow the Safe Zone. No new patterns or libraries without Architect approval.
-5. No Gold-Plating. Implement exactly what the Story specifies.
-6. Write Self-Documenting Code. JSDoc/docstrings required on all exports to prevent RAG poisoning.
-7. Self-assess Correction Tax. Track % human intervention.
+**On-demand:** `vibe-code-review`, `react-best-practices`, `write-skill`, `improve`, `file-organization`
 
-### After Implementation
-7. Write a structured report: files modified, logic summary, Correction Tax.
-8. Flag lessons. Gotchas and multi-attempt fixes get flagged for recording.
+## Quick Reference
 
-### Always
-9. Reports are the only handoff. No direct agent-to-agent communication.
-10. One source of truth. Reference upstream documents, don't duplicate.
-11. Change Logs are mandatory on every document modification.
-12. Agent Reports MUST use YAML Frontmatter. Every `.bounce/report/` generated must start with a strict `---` YAML block containing the core status and metrics before the Markdown body.
-13. Framework Integrity. Any modification to a `brains/`, `skills/`, `templates/`, or `scripts/` file MUST be recorded in `brains/CHANGELOG.md` and reflected in `MANIFEST.md`.
-
-## Framework Structure
-
-```
-V-Bounce Engine/
-├── brains/          — Agent brain files (this file)
-├── templates/       — Document templates (immutable)
-├── skills/          — Agent skills (SKILL.md files)
-├── scripts/         — Automation scripts (e.g., hotfix_manager.sh)
-└── docs/            — Reference docs (e.g., HOTFIX_EDGE_CASES.md)
-```
-
-## Document Locations
-
-Planning docs live in `product_plans/`. It uses a state-based architecture (`strategy/`, `backlog/`, `sprints/`, `archive/`). Completed items are archived to `product_plans/archive/`.
-
-| Document | Output |
-|----------|--------|
-| Charter | `product_plans/strategy/{project}_charter.md` |
-| Roadmap | `product_plans/strategy/{project}_roadmap.md` |
-| Risk Registry | `product_plans/strategy/RISK_REGISTRY.md` |
-| Delivery Plan | `product_plans/D-{NN}_{release_name}/D-{NN}_DELIVERY_PLAN.md` |
-| Sprint Plan | `product_plans/sprints/sprint-{XX}/sprint-{XX}.md` |
-| Epic | `product_plans/backlog/EPIC-{NNN}_{name}/EPIC-{NNN}.md` |
-| Story | `product_plans/backlog/EPIC-{NNN}_{name}/STORY-{EpicID}-{StoryID}-{StoryName}.md` |
-| Sprint Report | `.bounce/sprint-report-S-{XX}.md` |
-| Product Docs | `vdocs/*.md` + `_manifest.json` |
-
-## Report Formats
-
-Dev Report: Files modified, logic summary, Correction Tax, lessons flagged, product docs affected.
-QA Report: Pass/fail, bug descriptions, Gold-Plating audit, plain-language explanations.
-Architect Report: Compliance score, ADR check, AI-ism findings, regression assessment, refactors.
-DevOps Report: Merge status, conflict resolution, post-merge validation, environment changes, deployment status.
-Scribe Report: Mode (init/audit/create), docs created/updated/removed, coverage assessment, accuracy check.
-Sprint Report: What was delivered (user-facing vs internal), story results, execution metrics (tokens, duration, cost, bounces, correction tax), lessons, retrospective (what went well, what didn't, process improvements).
+- **Document ops:** `skills/doc-manager/SKILL.md` — hierarchy, cascade rules, planning workflows
+- **Product graph:** `.bounce/product-graph.json` — document relationships and state
+- **Bounce orchestration:** `skills/agent-team/SKILL.md` — agent delegation, sprint execution
+- **Planning docs:** `product_plans/` — `strategy/`, `backlog/`, `sprints/`, `hotfixes/`, `archive/`
+- **Sprint state:** `.bounce/state.json` — machine-readable sprint state
+- **Framework map:** `MANIFEST.md` — complete file and process registry

package/brains/CHANGELOG.md

@@ -3,6 +3,119 @@
 This log tracks modifications to the core agentic framework (e.g., `brains/`, `skills/`). 
 Per **Rule 13: Framework Integrity**, anytime an entry is made here, all tool-specific brain files must be reviewed for consistency.
 
+## [2026-03-22] — Bug & Change Request Templates + Process Fixes
+
+### Bug Report Template (New)
+- **Added**: `templates/bug.md` — documents defects found mid-sprint or post-sprint. YAML frontmatter (bug_id, status, severity, found_during, affected_story, reporter). Sections: The Bug (repro steps, expected/actual), Impact (blocking?, affected areas, data impact), Fix Approach (root cause, files, complexity), Verification. Triage rule: L1 bugs use hotfix.md, larger bugs use this template.
+
+### Change Request Template (New)
+- **Added**: `templates/change_request.md` — documents scope changes or approach changes mid-sprint. YAML frontmatter (cr_id, status, category, urgency, affected_stories, requestor). Sections: The Change (original vs proposed), Impact Assessment (affected stories, sprint impact, risk), Decision (human approves/rejects/defers), Execution Plan. Categories: Scope Change and Approach Change (from mid-sprint-triage.md).
+
+### Mid-Sprint Triage Update
+- **Modified**: `skills/agent-team/references/mid-sprint-triage.md` — added Template column to categorization table linking each category to its template. Added decision tree that routes L1 bugs to hotfix.md, larger bugs to bug.md, scope/approach changes to change_request.md, spec clarifications to inline updates. Added Step 4 (present to human). Updated Sprint Report tracking table with Document column.
+
+### Doc-Manager Update
+- **Modified**: `skills/doc-manager/SKILL.md` — added Bug Report and Change Request to Template Locations table.
+
+### Sprint Template Improvements
+- **Modified**: `templates/sprint.md` — added Shared File Map table to §2 (forces explicit merge ordering for parallel stories touching same files). Added Execution Mode table (L1→Fast Track, L2→needs human approval, L3/L4→Full Bounce always). Updated Dependency Chain reason column to include "shared file" as a dependency type.
+
+### Process Fixes
+- **Modified**: `skills/agent-team/SKILL.md` — pre-gate scan escalation after 3 failures (present to human with options). Post-merge test failure recovery path (revert → return to Dev → re-enter Step 2 → escalate after 3). Integration audit fix stories go to backlog (not current sprint) unless release-blocking. Delivery Plan Sync table clarified: updates ONLY at sprint close.
+- **Modified**: `skills/doc-manager/SKILL.md` — added Complexity Labels (L1-L4) to TRANSITION section. Epic readiness gate changed from "reviewed" to "decided mitigation OR explicitly accepted as known risk."
+- **Modified**: `skills/improve/SKILL.md` — fixed stale `pre_bounce_sync.sh` references → `vbounce doctor`. Clarified improvement cadence: analysis runs every sprint, applying is human's call.
+- **Modified**: `brains/CLAUDE.md`, `brains/GEMINI.md`, `brains/AGENTS.md` — replaced "Follow the Safe Zone" with "Comply with ADRs" (concrete, already enforced by Architect).
+- **Modified**: `bin/vbounce.mjs` — install now creates LESSONS.md if missing.
+- **Modified**: `MANIFEST.md` — added bug.md and change_request.md to Template Registry. Updated template count (10→12).
+
+---
+
+## [2026-03-22] — Ownership Restructure: Eliminate Process Knowledge Duplication
+
+### Problem
+Process knowledge (cascade rules, document hierarchy, critical rules, script registry, story states) was duplicated 2-3x across process-guide skill, doc-manager skill, MANIFEST.md, and brain files. Six concepts had no clear single owner, creating drift risk.
+
+### Solution: Each concept has exactly ONE owner
+
+**Ownership map:**
+- **Brain files** own: identity, phase routing table, critical rules (14 rules), skill loading
+- **doc-manager** owns: document hierarchy, information flow, cascade rules, story states, complexity labels, ambiguity rubric, planning workflows, transitions, archiving
+- **agent-team** owns: bounce sequence, worktrees, reports, git strategy, escalation, cleanup
+- **product-graph** owns: graph JSON interpretation, impact analysis, blocked document detection
+- **lesson** owns: lesson recording, graduation
+- **MANIFEST.md** owns: file/skill/script registries, file counts, version tracking (maintainer tool, not deployed)
+
+### Changes
+
+#### Deleted
+- **Deleted**: `skills/process-guide/SKILL.md` — its content was distributed:
+  - Phase routing table → brain files (all three)
+  - Critical rules (14 rules) → brain files (all three)
+  - Script registry → deleted (redundant with CLI `--help` and each skill mentioning its own scripts)
+  - Cascade rules → already in doc-manager (single owner)
+  - Story states → already in doc-manager (single owner)
+  - Document hierarchy → already in doc-manager (single owner)
+  - Complexity labels → moved to doc-manager
+
+#### Modified
+- **Modified**: `skills/doc-manager/SKILL.md` — added Complexity Labels section (L1-L4 definitions) to TRANSITION area. doc-manager is now the single owner of all document-related cross-cutting concepts.
+- **Modified**: `brains/CLAUDE.md` — added Phase Routing table (~10 lines) and Critical Rules (14 rules, ~25 lines). Removed process-guide references. ~85 lines total.
+- **Modified**: `brains/GEMINI.md` — mirrored: added Phase Routing + Critical Rules, removed process-guide references. ~95 lines total (includes CLI commands).
+- **Modified**: `brains/AGENTS.md` — mirrored: added Phase Routing + Critical Rules, removed process-guide references. ~70 lines total.
+- **Modified**: `MANIFEST.md` — removed process-guide from Skill Registry. Updated skill count (48→47). Updated total count.
+
+### Sync Notes
+- All three main brain files (CLAUDE.md, GEMINI.md, AGENTS.md) have identical Phase Routing and Critical Rules sections.
+- Cursor rules and Tier 4 brains (copilot, windsurf) not yet updated — should be synced in a follow-up change.
+
+---
+
+## [2026-03-22] — Product Graph + Process Awareness (EPIC-003 + EPIC-004)
+
+### Product Graph (EPIC-003)
+
+#### Graph Generation Script (New)
+- **Added**: `scripts/product_graph.mjs` — scans `product_plans/` active directories (strategy/, backlog/, sprints/, hotfixes/), extracts YAML frontmatter, outputs `.bounce/product-graph.json` with nodes (type, status, ambiguity, path, title) and edges (parent, depends-on, unlocks, context-source, feeds). Graceful empty graph for missing/empty product_plans/, skips malformed YAML with warning.
+
+#### Impact Analysis Script (New)
+- **Added**: `scripts/product_impact.mjs` — queries "what's affected by X?" using BFS traversal of the product graph. Outputs direct dependents, transitive dependents, upstream feeders. Visited-set for cycle protection. Supports `--json` output mode.
+
+#### Product Graph Skill (New)
+- **Added**: `skills/product-graph/SKILL.md` — interpretation rules for the product graph JSON. Three-tier loading protocol (graph JSON → specific frontmatter → full documents). Edge type semantics, regeneration triggers, blocked document detection logic.
+
+#### CLI Wiring
+- **Modified**: `bin/vbounce.mjs` — added `graph` command (`vbounce graph [generate]`, `vbounce graph impact <DOC-ID>`). Updated help text.
+
+#### Sprint Lifecycle Integration
+- **Modified**: `scripts/init_sprint.mjs` — added non-blocking product graph regeneration after sprint init.
+- **Modified**: `scripts/complete_story.mjs` — added non-blocking product graph regeneration after story completion.
+- **Modified**: `scripts/close_sprint.mjs` — added non-blocking product graph regeneration after sprint close.
+
+#### Doc-Manager Cascade Rule
+- **Modified**: `skills/doc-manager/SKILL.md` — added cascade rule: "After any cascade, run `vbounce graph` to regenerate the product graph."
+
+### Process Awareness (EPIC-004)
+
+#### Process-Guide Skill (New)
+- **Added**: `skills/process-guide/SKILL.md` — condensed process intelligence from MANIFEST.md, doc-manager, and CLAUDE.md. Contains: process flow (4 phases), phase routing table (user intent → phase → skill to load), script registry (all scripts by category), document hierarchy and cascade rules, story states, complexity labels, self-improvement awareness, and all 14 critical rules. ~200 lines, ~3,000 tokens.
+
+#### Brain File Slim-Down
+- **Modified**: `brains/CLAUDE.md` — reduced from ~259 lines to ~55 lines. Moved process flow (Phase 1-4), critical rules, document locations, report formats, story states, complexity labels to process-guide skill. Kept: identity, skill pointers (with phase-based loading), subagent table, quick reference. agent-team now loads only during Phase 3 (was always-loaded).
+- **Modified**: `brains/GEMINI.md` — mirrored slim-down. Skill loading now phase-based (process-guide always, doc-manager/product-graph for planning, agent-team for execution). Kept CLI commands section and quick reference.
+- **Modified**: `brains/AGENTS.md` — mirrored slim-down. Same phase-based skill loading structure.
+
+#### Agent-Team Conditional Loading
+- **Modified**: `brains/CLAUDE.md` Skills section — agent-team is no longer `@`-included (always-loaded). Instead, it loads on-demand when entering Phase 3. Only lesson remains always-loaded via `@`. Context budget reduced from ~9,000 tokens always to ~500 tokens always + ~3,000 during planning + ~9,000 during execution.
+
+### Integration
+- **Modified**: `MANIFEST.md` — added process-guide and product-graph to Skill Registry. Added product_graph.mjs and product_impact.mjs to Script Registry (new "Product Graph" category). Updated Process Flow to reference new skills. Updated file counts (skills: 46→48, scripts: 24→26, total: ~162→~166). Version bumped to 2.1.0.
+
+### Sync Notes
+- All three main brain files (CLAUDE.md, GEMINI.md, AGENTS.md) are consistent in their skill loading structure and quick reference section.
+- Cursor rules and Tier 4 brains (copilot, windsurf) not yet updated — should be synced in a follow-up change.
+
+---
+
 ## [2026-03-13] — Discovery Phase: Structured Spike System
 
 ### Spike Template (New)