---
id: T-305
name: "Inception: scope in-depth framework component walkthrough"
description: >
  The first-run experience (T-304) covers a basic governance cycle. But users also
  need a deeper guided tour of all framework components and functions: audit system,
  healing loop, context fabric, episodic memory, handover system, metrics, fabric,
  etc. This inception explores: what should be covered, what format (interactive tutorial,
  docs, video-style walkthrough), how deep, and whether it's one big tour or per-component
  guides. Separate from T-304 basic first-run. Source: T-294 dialogue — user requested
  separate inception for this scope.

status: work-completed
workflow_type: inception
owner: agent
horizon:
tags: []
components: []
related_tasks: [T-294]
created: 2026-03-04T16:27:41Z
last_update: '2026-06-11T22:24:18Z'
date_finished: 2026-03-09T07:24:40Z
target_blast_radius: 3   # T-2193 migration default (M=small-subsystem floor)
voi_score: 0.5            # T-2193 migration default (medium)
bvp_scores_proposed:
  - ts: '2026-06-11T22:24:18Z'
    estimator: bvp-estimator-v1-heuristic
    scores:
      D1: 2
      D2: 2
      D3: 2
      D4: 2
      F-RECALL: 2
      F-ORCH: 2
      F3: 2
      F1: 2
      F2: 2
    rationale: D1=2 (no-signal); D2=2 (no-signal); D3=2 (no-signal); D4=2 
      (no-signal); F-RECALL=2 (no-signal); F-ORCH=2 (no-signal); F3=2 
      (no-signal); F1=2 (no-signal); F2=2 (no-signal)
    rubric_sha: e4a00f38e801
---

# T-305: Inception: scope in-depth framework component walkthrough

## Problem Statement

Users need a guided path through all 12 framework subsystems beyond the basic first-run (T-304). Content already exists (127 component docs, 13 subsystem articles, 20 deep-dives) but there's no sequencing, audience routing, or progressive disclosure. The walkthrough is a **routing problem**, not a content creation problem. See `docs/reports/T-305-walkthrough-inception.md`.

## Assumptions

1. Existing generated docs (Layer 1 + Layer 2) are sufficient content — no need to write new subsystem explanations
2. Different audiences need different paths (new user vs. contributor vs. agent implementer)
3. Dependency-ordered sequencing (Task Mgmt → Git → Audit → Healing → Context) is more effective than alphabetical

## Exploration Plan

1. Survey existing documentation coverage (done — 127+13+20 docs exist)
2. Identify gaps between existing docs and walkthrough needs (done — sequencing/routing is the gap)
3. Propose format and scope for GO/NO-GO

## Technical Constraints

None significant. Existing infrastructure (Watchtower, fw CLI, markdown) can serve any format.

## Scope Fence

**IN:** Define walkthrough format, audience tracks, subsystem ordering. Scope the build task(s).
**OUT:** Actually building the walkthrough (that's the build task after GO). Not duplicating existing content.

## Acceptance Criteria

- [x] Problem statement validated (content exists, routing doesn't)
- [x] Assumptions tested (survey confirms 160+ docs, no guided path)
- [x] Go/No-Go decision made (GO)

## Go/No-Go Criteria

**GO if:**
- Content gap is routing/sequencing (confirmed — not content creation)
- Build effort is bounded (ordered markdown guides linking to existing docs)

**NO-GO if:**
- Existing docs need significant rewrite first (they don't)
- No clear audience differentiation (3 tracks identified)

## Verification

<!-- Shell commands that MUST pass before work-completed. One per line.
     Lines starting with # are comments. Empty lines ignored.
     The completion gate runs each command — if any exits non-zero, completion is blocked.
     For inception tasks, verification is often not needed (decisions, not code).
-->

## Decisions

**Decision**: GO

**Rationale**: Content exists (160+ docs). Gap is routing/sequencing, not content creation. Build: ordered markdown guides per audience track linking to existing generated docs. Bounded effort.

**Date**: 2026-03-09T07:24:40Z
## Decision

**Decision**: GO

**Rationale**: Content exists (160+ docs). Gap is routing/sequencing, not content creation. Build: ordered markdown guides per audience track linking to existing generated docs. Bounded effort.

**Date**: 2026-03-09T07:24:40Z

## Updates

<!-- Auto-populated by git mining at task completion.
     Manual entries optional during execution. -->

### 2026-03-09T07:21:57Z — status-update [task-update-agent]
- **Change:** owner: human → agent
- **Change:** horizon: later → now

### 2026-03-09T07:22:02Z — status-update [task-update-agent]
- **Change:** status: captured → started-work

### 2026-03-09T07:24:19Z — inception-decision [inception-workflow]
- **Action:** Recorded inception decision
- **Decision:** GO
- **Rationale:** Content exists (160+ docs). Gap is routing/sequencing, not content creation. Build: ordered markdown guides per audience track linking to existing generated docs. Bounded effort.

### 2026-03-09T07:24:40Z — inception-decision [inception-workflow]
- **Action:** Recorded inception decision
- **Decision:** GO
- **Rationale:** Content exists (160+ docs). Gap is routing/sequencing, not content creation. Build: ordered markdown guides per audience track linking to existing generated docs. Bounded effort.

### 2026-03-09T07:24:40Z — status-update [task-update-agent]
- **Change:** status: started-work → work-completed
- **Reason:** Inception decision: GO

## Reviewer Verdict (v1.5)

- **Scan ID:** R-6e266216
- **Timestamp:** 2026-06-02T15:02:02Z
- **Catalogue:** v1.3-seed
- **Overall:** PASS
- **Needs Human:** no
- **Findings:** none
