convoke-agents 3.2.0 → 3.3.0

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-02-extract.md

@@ -1,8 +1,8 @@
 ---
 name: 'step-t-02-extract'
-description: 'Extract actionable findings from input, classify, detect overlaps, and validate at Gate 1'
-nextStepFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-03-score.md'
-outputFile: '{planning_artifacts}/initiatives-backlog.md'
+description: 'Extract actionable findings from input, detect overlaps with existing Intakes and lane items, and validate the extraction batch'
+nextStepFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-03-qualify.md'
+outputFile: '{planning_artifacts}/convoke-note-initiative-lifecycle-backlog.md'
 templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/backlog-format-spec.md'
 ---
 
@@ -10,7 +10,7 @@ templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/t
 
 ## STEP GOAL:
 
-Extract actionable findings from the ingested text, classify each into a backlog category, detect overlaps with existing backlog items, and present the batch for user validation at Gate 1.
+Extract actionable findings from the ingested text, detect overlaps with existing Intakes and lane items, and present the batch for user validation at Gate 1. Each validated finding will become an **Intake** (§2.1) in the backlog — not directly a lane item.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -24,69 +24,72 @@ Extract actionable findings from the ingested text, classify each into a backlog
 - ✅ You are a **findings extraction analyst** — thorough, systematic, evidence-based
 - ✅ Extract what the input actually says — do not invent findings or impose interpretations
 - ✅ The user validates your extraction at Gate 1 — you propose, they decide
+- ✅ Every finding becomes an Intake — lane assignment is a separate step (step-t-03 Qualify)
 
 ### Step-Specific Rules:
-- 🎯 Focus on extraction, classification, and overlap detection
-- 🚫 FORBIDDEN to score findings (RICE scoring is step-t-03's job)
+- 🎯 Focus on extraction, overlap detection against Intakes and lane items, and Gate 1 validation
+- 🚫 FORBIDDEN to assign a lane (Bug/Fast/Initiative) — that is step-t-03's job (the qualifying gate)
+- 🚫 FORBIDDEN to score RICE — that is step-t-03's job for qualified items
 - 🚫 FORBIDDEN to write to the backlog file (that is step-t-04's job)
-- 🚫 FORBIDDEN to truncate or skip any part of the input text (FR46)
+- 🚫 FORBIDDEN to truncate or skip any part of the input text
 - 💬 Approach: systematic extraction, then collaborative validation at Gate 1
 
 ## EXECUTION PROTOCOLS:
 - 🎯 Follow the MANDATORY SEQUENCE exactly
-- 📖 Load {templateFile} for category reference
+- 📖 Load {templateFile} for file structure reference
 - 💾 Track extraction state — redisplay updated batch after every Gate 1 edit
 
 ## CONTEXT BOUNDARIES:
-- Available context: User's input text (from step-t-01), existing backlog (if loaded), backlog format spec template
+- Available context: User's input text (from step-t-01), existing backlog (if loaded), backlog format spec
 - Focus: Extraction and Gate 1 validation only
-- Limits: Do NOT score or write to backlog
+- Limits: Do NOT qualify findings into lanes or write to backlog
 - Dependencies: step-t-01-ingest.md (input text accepted)
 
 ## MANDATORY SEQUENCE
 
 **CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
 
-### 1. Load Category Reference
+### 1. Load Format Reference
 
-Load `{templateFile}` (backlog-format-spec.md) and extract the category names from the "Category Names" section. Current categories:
-
-- Documentation & Onboarding
-- Update & Migration System
-- Testing & CI
-- Infrastructure
-- Agent Quality & Consistency
-- Platform & Product Vision
-
-New categories may be proposed if a finding doesn't fit any existing category.
+Load `{templateFile}` (backlog-format-spec.md) and note the structure:
+- §2.1 Intakes is the append target for this step's output
+- §2.2 Bug Lane, §2.3 Fast Lane, §2.4 Initiative Lane contain already-qualified items
+- §2.5 Absorbed / Archived contains removed items
 
 ### 2. Extract Actionable Findings
 
-Process the **complete** input text from step-t-01. Do NOT truncate, summarize, or skip sections (FR46).
+Process the **complete** input text from step-t-01. Do NOT truncate, summarize, or skip sections.
 
 For each passage in the input, determine if it is **actionable**. A finding is actionable if it:
 - **Proposes a change** (something should be different)
 - **Identifies a gap** (something is missing)
 - **Flags a risk** (something could go wrong)
+- **Reports a break** (something is observably broken)
 
 Non-actionable content (general comments, praise, questions without implied action, status updates) should be set aside as **observations** — they are NOT included in the extraction batch but may be escalated at Gate 1.
 
 For each actionable finding, record:
 1. **Finding number** — sequential (1, 2, 3...)
-2. **Title** — concise summary (matches backlog Initiative column style)
-3. **Category** — one of the categories from step 1 (or propose a new one)
-4. **Source reference** — which part of the input it came from (e.g., "paragraph 3", "under 'Performance Issues' heading", "line about caching") (FR4)
-5. **Type** — Change / Gap / Risk
+2. **Title** — concise summary (matches lane table style)
+3. **Source reference** — which part of the input it came from (e.g., "paragraph 3", "under 'Performance Issues' heading", "line about caching")
+4. **Type** — Change / Gap / Risk / Break
 
 ### 3. Detect Overlaps with Existing Backlog
 
 **Skip this step if no existing backlog was loaded in step-t-01.**
 
-For each extracted finding, compare against existing backlog items by semantic similarity (title + description). Flag potential overlaps when a finding appears to address the same concern as an existing item.
+For each extracted finding, compare against **all existing items**:
+- §2.1 Intakes (unqualified items)
+- §2.2 Bug Lane items
+- §2.3 Fast Lane items
+- §2.4 Initiative Lane items
+- §2.5 Absorbed/Archived items (flag if finding restates something already absorbed)
+
+Compare by semantic similarity (title + description). Flag potential overlaps when a finding appears to address the same concern as an existing item.
 
 For each overlap flag, record:
-- The existing item's **ID** (e.g., D2, P4)
-- The existing item's **title**
+- The existing item's **location** (Intakes, Fast Lane, Initiative Lane, Absorbed, etc.)
+- The existing item's **ID** and **title**
 - Brief explanation of why it might overlap
 
 ### 4. Handle Zero Findings
@@ -97,7 +100,7 @@ Display:
 
 > **No actionable findings extracted from the input.**
 >
-> The input contained no content that proposes a change, identifies a gap, or flags a risk.
+> The input contained no content that proposes a change, identifies a gap, flags a risk, or reports a break.
 >
 > **Options:**
 > - Paste a specific passage you'd like me to re-examine
@@ -118,15 +121,17 @@ Display the extraction results in a numbered list:
 >
 > **Actionable findings extracted: [N]**
 >
-> | # | Finding | Category | Source | Type | Overlap |
-> |---|---------|----------|--------|------|---------|
-> | 1 | [title] | [category] | [source ref] | Change | — |
-> | 2 | [title] | [category] | [source ref] | Gap | ⚠️ Overlaps D2: "[existing title]" |
-> | 3 | [title] | [category] | [source ref] | Risk | — |
+> | # | Finding | Source | Type | Overlap |
+> |---|---------|--------|------|---------|
+> | 1 | [title] | [source ref] | Change | — |
+> | 2 | [title] | [source ref] | Gap | ⚠️ Overlaps §2.3 Fast Lane I15: "[existing title]" |
+> | 3 | [title] | [source ref] | Break | — |
 >
 > **Observations (not included — escalate with `E` if actionable):**
 > - [observation 1]
 > - [observation 2]
+>
+> *Each validated finding will be logged as an Intake (§2.1). Qualification into a lane happens in the next step.*
 
 ### 6. Present GATE 1 MENU OPTIONS
 
@@ -135,25 +140,25 @@ Display:
 > **Gate 1 — Edit the extraction batch:**
 >
 > **Overlap resolution** (for flagged items only):
-> - `merge #N` — Absorb finding into the existing overlapping item
+> - `merge #N` — Absorb finding into the existing overlapping item (no new intake created)
 > - `skip #N` — Drop finding (existing item is sufficient)
-> - `new #N` — Override overlap flag, keep as separate new item
+> - `new #N` — Override overlap flag, keep as separate new intake
 >
 > **Batch editing:**
 > - `E #N` — Escalate observation #N to actionable finding
 > - `+ [title — description]` — Add a finding the workflow missed
 > - `R #N` — Remove finding #N from the batch
 >
-> **[C] Continue** — Finalize batch and proceed to RICE scoring
+> **[C] Continue** — Finalize batch and proceed to qualifying gate
 
 #### Menu Handling Logic:
 - IF `merge #N`: Mark finding #N as merged with existing item. Remove from batch. Redisplay updated batch and menu.
 - IF `skip #N`: Remove finding #N from batch. Redisplay updated batch and menu.
-- IF `new #N`: Clear overlap flag on finding #N (will be added as new item). Redisplay updated batch and menu.
-- IF `E #N`: Move observation #N into the findings batch as actionable. Assign a category and source ref. Redisplay updated batch and menu.
-- IF `+ [text]`: Add a new finding to the batch. Ask user for category if not obvious. Redisplay updated batch and menu.
+- IF `new #N`: Clear overlap flag on finding #N (will be added as new intake). Redisplay updated batch and menu.
+- IF `E #N`: Move observation #N into the findings batch as actionable. Assign a source ref. Redisplay updated batch and menu.
+- IF `+ [text]`: Add a new finding to the batch. Assign a source ref (likely "user-added"). Redisplay updated batch and menu.
 - IF `R #N`: Remove finding #N from the batch. Redisplay updated batch and menu.
-- IF C: Finalize the batch. Load, read the entire file, and execute `{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-03-score.md`
+- IF C: Finalize the batch. Load, read the entire file, and execute `{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-03-qualify.md`
 - IF any other input: Display "Unknown command. Use `merge/skip/new #N`, `E #N`, `+ [text]`, `R #N`, or **C** to continue." then redisplay menu.
 
 #### EXECUTION RULES:
@@ -164,6 +169,6 @@ Display:
 - Do NOT auto-continue — the user must explicitly approve the batch
 
 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-### ✅ SUCCESS: All actionable findings extracted with categories and source refs, overlaps detected, user validated batch at Gate 1, confirmed findings passed to step-t-03
-### ❌ SYSTEM FAILURE: Input truncated, findings invented (not from input), overlaps missed, user not given Gate 1 validation opportunity, findings scored prematurely
+### ✅ SUCCESS: All actionable findings extracted with source refs, overlaps detected across all backlog sections, user validated batch at Gate 1, confirmed findings passed to step-t-03 for qualification
+### ❌ SYSTEM FAILURE: Input truncated, findings invented (not from input), overlaps missed, user not given Gate 1 validation opportunity, findings qualified or scored prematurely
 **Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-03-qualify.md

@@ -0,0 +1,192 @@
+---
+name: 'step-t-03-qualify'
+description: 'Qualifying gate — assign Lane, Portfolio, and RICE score for each validated finding. Optional skip keeps the finding as a raw intake.'
+nextStepFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-04-update.md'
+outputFile: '{planning_artifacts}/convoke-note-initiative-lifecycle-backlog.md'
+templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/rice-scoring-guide.md'
+processFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/lifecycle-process-spec.md'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
+---
+
+# Step 3: Qualifying Gate (Lane + Portfolio + RICE)
+
+## STEP GOAL:
+
+Run the **qualifying gate** on each validated finding from Gate 1. For each finding, the qualifier (Vortex, John, or Winston) assigns a **Lane** (Bug / Fast / Initiative), a **Portfolio** attachment, and an initial **RICE** score. Findings the qualifier is not ready to route stay logged as raw intakes in §2.1 with no lane.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- 🛑 NEVER generate lane/portfolio/RICE without user input — the qualifying gate is user-driven
+- 📖 CRITICAL: Read this complete step file before taking action
+- 🔄 CRITICAL: When loading next step with 'C', read the entire file
+- 📋 YOU ARE A QUALIFYING-GATE FACILITATOR supporting the qualifier (Vortex / John / Winston)
+
+### Role Reinforcement:
+- ✅ You are a **qualifying gate facilitator** — propose, don't decide; the qualifier decides
+- ✅ Only Vortex team, John, or Winston can qualify. Confirm the user is acting in one of those roles.
+- ✅ Propose lane/portfolio/RICE based on finding description, but flag uncertainty plainly
+- ✅ Every finding ends this step in one of two states: **qualified** (lane + portfolio + RICE) or **raw intake** (logged to §2.1 only)
+
+### Step-Specific Rules:
+- 🎯 Focus on lane assignment, portfolio attachment, and RICE scoring
+- 🚫 FORBIDDEN to write to the backlog file (that is step-t-04's job)
+- 🚫 FORBIDDEN to re-extract or re-classify findings (that was step-t-02's job)
+- 🚫 FORBIDDEN to add new findings here (new findings require a fresh Triage run)
+- 💬 Approach: walk findings one at a time, propose + decide, track state
+
+## EXECUTION PROTOCOLS:
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 📖 Load {templateFile} for RICE factor definitions and calibration examples
+- 📖 Load {processFile} for lane definitions and portfolio taxonomy
+- 💾 Track each finding's qualification decision for step-t-04
+
+## CONTEXT BOUNDARIES:
+- Available context: Validated findings from Gate 1 (step-t-02), RICE scoring guide, lifecycle process spec, existing backlog
+- Focus: Qualifying gate per-finding
+- Limits: Do NOT write to backlog or modify extraction results
+- Dependencies: step-t-02-extract.md (Gate 1 validated findings)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Load References
+
+Load `{templateFile}` (rice-scoring-guide.md) and internalize:
+- **Factor definitions:** Reach (1-10), Impact (0.25-3), Confidence (20-100%), Effort (1-10)
+- **Guided questions** for each factor
+- **Calibration examples** (study the reasoning, not just the numbers)
+- **Composite formula:** Score = (R × I × C) / E, where C is decimal (e.g., 70% = 0.7)
+
+Load `{processFile}` (lifecycle-process-spec.md) and internalize:
+- **§1.3 Three Lanes** — Bug / Fast / Initiative triggers and rules
+- **§1.4 Portfolio Attachment** — current taxonomy (convoke, vortex, gyre, forge, bmm, enhance, loom, helm) and growth rule
+- **§1.6 RICE Scoring** — lane-specific scoring notes
+
+### 2. Confirm Qualifier Role
+
+Display:
+
+> **Qualifying Gate — Confirm Qualifier**
+>
+> Only three parties can qualify intakes:
+> - **[V] Vortex** team (via discovery)
+> - **[J] John** (PM shortcut)
+> - **[W] Winston** (Architect shortcut)
+>
+> Who is qualifying in this session?
+
+Record the qualifier identity. If the user declines to pick one, display: "Qualifying requires an authorized qualifier (Vortex, John, or Winston). You can still log findings as raw intakes — type `raw-only` to skip qualification for this session." and accept either a role letter or `raw-only`.
+
+### 3. Walk Findings One at a Time
+
+Initialize:
+- `qualified_items = []` — findings with lane + portfolio + RICE assigned
+- `raw_intakes = []` — findings kept as intakes only (no lane)
+- `current_index = 1`
+
+For each finding from Gate 1:
+
+#### 3a. Present Finding & Proposed Qualification
+
+Display:
+
+> **Finding [current_index] of [total]**
+>
+> **Title:** [title]
+> **Source:** [source ref]
+> **Type:** [Change/Gap/Risk/Break]
+>
+> **Proposed qualification:**
+> - **Lane:** [proposed lane with brief rationale, e.g., "Fast Lane — single-module point fix"]
+> - **Portfolio:** [proposed portfolio, e.g., "convoke"]
+> - **RICE:** R:[r] I:[i] C:[c]% E:[e] = [score]
+>   *[one-line RICE rationale]*
+>
+> *If Type is `Break`, default lane is Bug and RICE impact defaults to 2+ unless narrow scope.*
+
+#### 3b. Present Per-Finding Menu
+
+Display:
+
+> **Review this qualification:**
+>
+> **Lane override:**
+> - `L bug` / `L fast` / `L initiative` — Change lane
+> - `L none` — Keep as raw intake (no lane, stays in §2.1 only)
+>
+> **Portfolio override:**
+> - `P [item]` — Set portfolio (convoke, vortex, gyre, forge, bmm, enhance, loom, helm, or a new portfolio)
+> - `P new [name] — [rationale]` — Propose a new portfolio item (John+Winston decision per §1.4)
+>
+> **RICE adjustments:**
+> - `R [value]` — Reach (1-10)
+> - `I [value]` — Impact (0.25, 0.5, 1, 2, or 3)
+> - `CF [value]` — Confidence (20-100%)
+> - `E [value]` — Effort (1-10)
+>
+> **Decisions:**
+> - `K` — Keep/accept proposed qualification
+> - `RAW` — Log as raw intake only (§2.1); no lane assigned
+> - `S` — Skip this finding (not logged, dropped)
+> - `X` — Exit qualification early (remaining findings become raw intakes)
+>
+> **[A] Advanced Elicitation** — Deeper analysis
+> **[P] Party Mode** — Multi-perspective discussion
+> **[C] Continue** — Apply current qualification and advance to next finding
+
+#### Menu Handling Logic:
+- IF `L bug/fast/initiative`: Update lane. If lane is `bug`, note RICE impact may be hardcoded. Redisplay.
+- IF `L none`: Mark finding for raw-intake-only routing. Redisplay.
+- IF `P [item]`: Update portfolio. If `new`, record the proposal for John+Winston review in Change Log. Redisplay.
+- IF `R/I/CF/E [value]`: Validate range. Update, recalculate composite, redisplay.
+- IF K: Accept current state. Add to `qualified_items` (or `raw_intakes` if lane is `none`). Advance to next finding.
+- IF RAW: Add to `raw_intakes`. Advance to next finding.
+- IF S: Drop finding entirely (note in Change Log). Advance to next finding.
+- IF X: Remaining findings become raw intakes. Go to step 4.
+- IF A: Execute `{advancedElicitationTask}`. When finished, redisplay.
+- IF P: Execute `{partyModeWorkflow}`. When finished, redisplay.
+- IF C: Same as K if no change was made; otherwise record adjustments, advance.
+- IF any other input: Display error, redisplay menu.
+
+#### 3c. Advance
+Increment `current_index`. If `<= total`, go to 3a. Otherwise go to step 4.
+
+### 4. Present Qualification Summary
+
+Display:
+
+> **Qualification Complete**
+>
+> **Qualified items (will be added to lanes):** [N]
+> **Raw intakes (logged to §2.1 only):** [N]
+> **Dropped:** [N]
+> [If early exit: **Auto-converted to raw intakes:** [N]]
+>
+> **Qualified breakdown:**
+> - Bug Lane: [N]
+> - Fast Lane: [N]
+> - Initiative Lane: [N]
+>
+> **Qualifier:** [Vortex / John / Winston / raw-only]
+
+### 5. Present MENU OPTIONS
+
+Display:
+
+> **[C] Continue** — Write qualifications to backlog (step-t-04)
+> **[R] Revisit** — Walk findings again (re-enter step 3)
+> **[X] Abort** — Return to mode selection without writing
+
+#### Menu Handling Logic:
+- IF C: Load, read the entire file, and execute `{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-04-update.md`, passing `qualified_items`, `raw_intakes`, `dropped_items`, and the qualifier identity.
+- IF R: Re-enter step 3 from `current_index = 1`. Preserve existing decisions but allow edits.
+- IF X: Discard all qualifications. Load, read, and execute `{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/workflow.md`.
+- IF any other input: Display error, redisplay menu.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+### ✅ SUCCESS: Every finding either qualified (lane + portfolio + RICE) or routed to raw intakes, qualifier identity recorded, user validated decisions, results passed to step-t-04
+### ❌ SYSTEM FAILURE: Qualification performed without authorized qualifier, findings assigned to lane without RICE, findings lost between steps, step-t-04 invoked with missing data
+**Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-04-update.md

@@ -1,16 +1,16 @@
 ---
 name: 'step-t-04-update'
-description: 'Validate backlog structure, append scored items safely, regenerate prioritized view, and present completion summary'
-outputFile: '{planning_artifacts}/initiatives-backlog.md'
+description: 'Validate backlog structure, log every finding as an Intake in §2.1, append qualified items to their lanes, update Change Log, and present completion summary'
+outputFile: '{planning_artifacts}/convoke-note-initiative-lifecycle-backlog.md'
 templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/backlog-format-spec.md'
 workflowFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/workflow.md'
 ---
 
-# Step 4: Backlog Update, Safety & Completion
+# Step 4: Backlog Update — Log Intakes & Append Qualified Items
 
 ## STEP GOAL:
 
-Validate backlog structure, safely append scored items from Gate 2, regenerate the prioritized view, and present a completion summary before returning to the T/R/C menu.
+Validate backlog structure, log every finding (qualified or raw) as an **Intake** in §2.1 (the audit trail), append qualified items to their assigned lane's table (§2.2 Bug / §2.3 Fast / §2.4 Initiative), update the Change Log, and present a completion summary before returning to the T/R/C menu.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -21,17 +21,18 @@ Validate backlog structure, safely append scored items from Gate 2, regenerate t
 - 📋 YOU ARE A BACKLOG OPERATIONS SPECIALIST performing safe, structured writes
 
 ### Role Reinforcement:
-- ✅ You are a **backlog operations specialist** — precise, non-destructive, append-only
-- ✅ Preserve all existing content — never delete, overwrite, or reorder existing rows
-- ✅ The Prioritized View is the ONLY section regenerated from scratch
+- ✅ You are a **backlog operations specialist** — precise, non-destructive, append-only for lanes and intakes
+- ✅ Preserve all existing content — never delete, overwrite, or reorder existing rows outside the touched lane's sort update
+- ✅ **Part 1 (Lifecycle Process) must not be modified** — it's semi-static documentation
+- ✅ Every qualified item generates **two** rows: one in §2.1 Intakes (audit trail) AND one in the assigned lane
 - ✅ All output must be standard markdown — no HTML, no proprietary syntax
 
 ### Step-Specific Rules:
 - 🎯 Focus on validation, safe writes, and completion reporting
-- 🚫 FORBIDDEN to delete or reorder existing backlog items (FR18, NFR1)
-- 🚫 FORBIDDEN to re-score items (scoring was finalized at Gate 2)
-- 🚫 FORBIDDEN to modify step-t-01, step-t-02, or step-t-03
-- 💬 Approach: validate first, write safely, summarize clearly
+- 🚫 FORBIDDEN to delete or reorder existing §2.1 Intakes (append-only per §1.1)
+- 🚫 FORBIDDEN to re-qualify items (qualification was finalized at step-t-03)
+- 🚫 FORBIDDEN to modify Part 1 (Lifecycle Process) — load it for context only
+- 💬 Approach: validate first, write intakes + lane items safely, summarize clearly
 
 ## EXECUTION PROTOCOLS:
 - 🎯 Follow the MANDATORY SEQUENCE exactly
@@ -39,10 +40,10 @@ Validate backlog structure, safely append scored items from Gate 2, regenerate t
 - 💾 Write to `{outputFile}` only after validation passes (or user overrides)
 
 ## CONTEXT BOUNDARIES:
-- Available context: Scored findings from Gate 2, existing backlog file, backlog format spec template
-- Focus: Structural validation, safe append, prioritized view regeneration, completion summary
-- Limits: Do NOT re-score, re-extract, or re-classify items
-- Dependencies: step-t-03-score.md (scored findings from Gate 2)
+- Available context: Qualified items + raw intakes + dropped items from step-t-03, qualifier identity, existing backlog file, format spec
+- Focus: Structural validation, append to §2.1 and lanes, lane sort, Change Log, completion summary
+- Limits: Do NOT re-qualify, re-extract, or re-classify items; do NOT modify Part 1
+- Dependencies: step-t-03-qualify.md (qualified + raw items + qualifier identity)
 
 ## MANDATORY SEQUENCE
 
@@ -50,21 +51,25 @@ Validate backlog structure, safely append scored items from Gate 2, regenerate t
 
 ### 1. Pre-Write Validation
 
-Load `{outputFile}` (existing backlog) and validate structural integrity:
-
-1. **Section heading anchors** — All 7 required H2 sections exist in correct order:
-   - `## RICE Scoring Guide`
-   - `## Backlog`
-   - `## Exploration Candidates`
-   - `## Epic Groupings`
-   - `## Prioritized View (by RICE Score)`
-   - `## Completed`
-   - `## Change Log`
-2. **Prioritized view table** — Has exactly 6 columns (Rank, #, Initiative, Score, Track, Category)
-3. **Category tables** — Each table under `## Backlog` has exactly 10 columns (#, Initiative, Source, R, I, C, E, Score, Track, Status)
-4. **Change Log section** — The `## Change Log` H2 section exists with a table
-
-If ALL checks pass, proceed directly to step 3 (Append Items).
+Load `{outputFile}` (existing backlog) and validate structural integrity per format spec:
+
+1. **Frontmatter present** — YAML block at top of file.
+2. **Part 1 section anchor** — `## Part 1: Lifecycle Process` exists. (Content is not inspected — only the anchor.)
+3. **Part 2 section anchors** — All five H3 sections exist in correct order under `## Part 2: Backlog`:
+   - `### 2.1 Intakes (Unqualified)`
+   - `### 2.2 Bug Lane`
+   - `### 2.3 Fast Lane (Quick Wins + Spikes)`
+   - `### 2.4 Initiative Lane`
+   - `### 2.5 Absorbed / Archived`
+4. **Table column counts:**
+   - §2.1 Intakes: 5 columns (ID, Description, Source, Date, Raiser)
+   - §2.2 Bug Lane: 10 columns
+   - §2.3 Fast Lane: 9 columns
+   - §2.4 Initiative Lane: 10 columns
+5. **Change Log section** — `## Change Log` H2 exists with a table.
+6. **File missing guard** — If the backlog file does not exist, display: "No backlog file found at `{outputFile}`. Triage cannot create a new file — use Create mode [C] first." Then load workflow.md and return.
+
+If ALL checks pass, proceed directly to step 3 (Append Intakes).
 
 ### 2. Mismatch Handling
 
@@ -79,54 +84,50 @@ If ANY validation check fails, present the specific mismatch(es):
 
 **ALWAYS halt and wait for user input.**
 
-- IF Y: Continue to step 3 (Append Items)
-- IF X: Display "Aborting backlog update." then load, read the entire file, and execute `{workflowFile}` to return to mode selection
-- IF any other input: Display "Please select **Y** or **X**." then redisplay the prompt
+- IF Y: Continue to step 3.
+- IF X: Display "Aborting backlog update." then load, read the entire file, and execute `{workflowFile}` to return to mode selection.
+- IF any other input: Display "Please select **Y** or **X**." then redisplay the prompt.
 
-### 3. Append Items
+### 3. Append Intakes to §2.1
 
-For each scored item from Gate 2:
+For **every** finding that reached this step (qualified + raw intake + dropped), append a row to §2.1 Intakes:
 
-1. **Find target category** — Locate the H3 section under `## Backlog` matching the item's category
-2. **Create category if needed** — If category doesn't exist, add a new H3 heading with a 10-column table at the end of `## Backlog` (before `## Exploration Candidates`)
-3. **Generate item ID** — Use category prefix letter (D/U/T/I/A/P) + next number (increment from highest existing in that category)
-4. **Append row** — Add new row to end of category table. NEVER delete, overwrite, or reorder existing rows
-5. **Add provenance** — Include in the Initiative description: `Added from [source], [date]` where source is the input origin from step-t-01 and date is the current session date
+1. **Generate Intake ID** — `IN-{n}` where `n` is the next sequential integer after the highest existing IN-ID in §2.1.
+2. **Description** — concise one-line summary from the finding.
+3. **Source** — session origin (e.g., "party mode 2026-04-15", "code review ag-7-5", "retrospective sp-epic-5").
+4. **Date** — current session date (YYYY-MM-DD, absolute).
+5. **Raiser** — the qualifier identity from step-t-03 (Vortex / John / Winston / raw-only).
 
-**Column format** (10 columns per backlog-format-spec.md):
-```
-| [ID] | **[Title]** — [description]. Added from [source], [date] | [source ref] | [R] | [I] | [C]% | [E] | [score] | [track] | Backlog |
-```
+**Do NOT delete or reorder existing Intake rows.** Append new rows at the end of the table.
 
-**Important:** Triage Gate 2 adjustments are the initial score — no rescore provenance is generated.
+**Dropped items are also logged to §2.1** — with a Description prefixed `[DROPPED]` and the reason in the Change Log. This preserves the audit trail even for findings the qualifier chose not to route.
 
-### 4. Regenerate Prioritized View
+### 4. Append Qualified Items to Their Lanes
 
-Rebuild the `## Prioritized View (by RICE Score)` table from scratch:
+For each item in `qualified_items` (i.e., findings routed to Bug / Fast / Initiative):
 
-1. Collect ALL active items from all category tables (existing + newly appended)
-2. Exclude items with Status "Done" or items in the `## Completed` section
-3. Sort by composite RICE score descending
-4. Tiebreak: (1) Higher Confidence first, (2) Newer insertion order first
-5. Generate sequential rank numbers starting at 1
+1. **Find target lane table** — §2.2 (Bug), §2.3 (Fast), or §2.4 (Initiative).
+2. **Generate lane ID:**
+   - Bug Lane: `BUG-{n}` sequential.
+   - Fast Lane + Initiative Lane: single alpha prefix from a simple heuristic (U for Update, I for Infrastructure, T for Testing, A for Agent, D for Doc, P for Platform). If uncertain, use `Q-{n}` (for Qualified-uncategorized).
+3. **Append row** with the columns defined in the format spec for the target lane. Include the RICE score rationale as a tail note only if it aids future review (keep rows compact).
+4. **Cross-reference** — In the Intake row's Description cell (in §2.1), append ` → [laneID]` so intake→lane linkage is preserved.
+5. **Re-sort the touched lane's table by composite RICE score descending.** Tiebreak: Confidence higher first, then insertion order newer first.
 
-Table format (6 columns):
-```
-| Rank | # | Initiative | Score | Track | Category |
-|------|---|-----------|-------|-------|----------|
-```
+**Never delete, overwrite, or reorder rows in lanes that were not touched this session.**
 
-### 5. Add Changelog Entry
+### 5. Add Change Log Entry
 
 Prepend a new row to the `## Change Log` table (newest first):
 
 ```
-| YYYY-MM-DD | Triage: Added [N] items ([categories affected]). [Any merge notes if applicable] |
+| YYYY-MM-DD | Triage by [Qualifier]: Logged [N] intakes. Qualified [X] ([Bug: a, Fast: b, Initiative: c]). Raw intakes: [Y]. Dropped: [Z]. [Any new portfolio proposals flagged.] |
 ```
 
-### 6. Update Last Updated Date
+### 6. Update Frontmatter
 
-Set the metadata header `Last Updated` field to the current date (YYYY-MM-DD format).
+- Set `status: active` if this is the first write to the file (was `draft`).
+- Do NOT modify the `created` date.
 
 ### 7. Completion Summary & Return to Menu
 
@@ -134,11 +135,15 @@ After successful write, display:
 
 > **Triage Complete**
 >
-> **Items added:** [N]
-> **Items merged:** [N] (absorbed into existing items at Gate 1)
-> **Categories affected:** [list]
+> **Intakes logged:** [N]
+> **Qualified into lanes:** [X]
+>   - Bug Lane: [n]
+>   - Fast Lane: [n]
+>   - Initiative Lane: [n]
+> **Raw intakes (awaiting qualification):** [Y]
+> **Dropped (logged with reason):** [Z]
 >
-> **New Top 3 Positions:**
+> **Top 3 Fast Lane positions (post-sort):**
 > 1. [#ID] [title] — Score: [X.X]
 > 2. [#ID] [title] — Score: [X.X]
 > 3. [#ID] [title] — Score: [X.X]
@@ -150,6 +155,6 @@ Then return to the T/R/C menu:
 Load, read the entire file, and execute `{workflowFile}`.
 
 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-### ✅ SUCCESS: Pre-write validation performed, existing content preserved, items appended with correct IDs and provenance, prioritized view regenerated with all items sorted correctly, changelog updated, completion summary displayed with top 3, T/R/C menu re-presented
-### ❌ SYSTEM FAILURE: Existing backlog content deleted/overwritten/reordered, items written without validation, wrong IDs or missing provenance, prioritized view not regenerated, no completion summary, no return to menu
+### ✅ SUCCESS: Validation performed, every finding logged as an Intake (audit trail complete), qualified items appended to correct lanes with proper IDs, lanes re-sorted by RICE, Change Log updated with qualifier identity and counts, completion summary displayed, menu re-presented
+### ❌ SYSTEM FAILURE: Findings not logged as Intakes, qualified items written without the cross-reference in Intakes, Part 1 modified, existing rows deleted/reordered, Change Log missing the qualifier identity, dropped items lost without audit trail
 **Master Rule:** Skipping steps is FORBIDDEN.