# KFB Feature Database — Coverage Report

**Source:** Bootstrap_Function_Registry.md (Registry v2.3) and Project_Kickoff_Seed_Prompt_v2.3.md
**Generated:** 2026-07-04
**Purpose:** Confirms every registry ID (1.01 through 9.05) is covered by at least one feature file.

Method: features were grouped by independently-toggleable unit first (see index.md); this report reconciles that grouping against the registry AFTER the fact. A registry item maps to exactly one feature; a feature may cover several registry items.

---

## Section 1 — Bootstrap Operating Behavior

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 1.01 | Activation guard | FTR-01 Bootstrap Operating Behavior |
| 1.02 | Step 0 current state assessment (HTML card matrix) | FTR-01 |
| 1.03 | Kevin Framework welcome block | FTR-01 |
| 1.04 | Non-intrusive operation | FTR-01 |
| 1.05 | Existing instructions merge rule (hard rule) | FTR-01 |
| 1.06 | Infrastructure assistant scope (hard rule) | FTR-01 |
| 1.07 | No-project detection | FTR-01 |
| 1.08 | Process safeguard — standing rule | FTR-03 Process Safeguard (also referenced in FTR-01) |
| 1.09 | What Would Kevin Do rule | FTR-01 (and FTR-02 in produced instructions) |
| 1.10 | Unresolved gaps -> agent instructions | FTR-01 |
| 1.11 | Rerun-to-reconcile loop | FTR-01 |

## Section 2 — Setup Steps (Steps 1-14)

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 2.01 | Step 1: Connector inventory | FTR-05 Connectors & Capabilities |
| 2.02 | Step 2: Project definition + project code | FTR-04 Agent Role & Project Identity |
| 2.03 | Step 2A: Legal preferences | FTR-18 Legal Preferences Profile |
| 2.04 | Step 3: Entity profile | FTR-17 Entity / Organization Profile |
| 2.05 | Step 4: Canonical repository + #drop\ file transfer | FTR-06 File Storage & Transfer Rules |
| 2.06 | Step 5: Folder structure | FTR-07 Folder Structure |
| 2.07 | Step 6: File naming + versioning | FTR-08 File Naming, Track IDs & Versioning |
| 2.08 | Step 7: Brand setup (7A-7E) | FTR-16 Brand Setup |
| 2.09 | Step 8: Tracker implementation | FTR-13 Document Tracker System |
| 2.10 | Step 9: Document workflow + statuses | FTR-10 Document Workflow & Status System |
| 2.11 | Step 10: Handoff protocol | FTR-19 Session Handoff Protocol |
| 2.12 | Step 11: Cowork integration | FTR-20 Cowork Integration |
| 2.13 | Step 12: Startup reminder mode | FTR-09 Startup Display & Reminder Mode |
| 2.14 | Step 13: Agent instructions sync | FTR-23 Agent Instructions Sync |
| 2.15 | Step 14: Project audit | FTR-22 Project Audit / Health Check |

## Section 3 — Step 15: Agent Instructions Generation

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 3.01 | Hard rule: always generates before closing | FTR-24 Agent Instructions Generation & Deploy |
| 3.02 | Format requirement: plain text / ASCII | FTR-24 |
| 3.03 | Verification gate: 32-item checklist before presenting | FTR-24 |
| 3.04 | Existing instructions merge | FTR-24 (merge rule also in FTR-01) |
| 3.05 | Unresolved gaps -> BOOTSTRAP RECONCILIATION ITEMS | FTR-24 |
| 3.06 | CLAUDE.md generation rule — alongside agent instructions | FTR-21 CLAUDE.md Cowork Context File |

## Section 4 — Step 16: Deploy and Wrap-Up

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 4.01 | Hard rule: does not close without completing all items | FTR-24 Agent Instructions Generation & Deploy |
| 4.02 | Agent instructions + CLAUDE.md download | FTR-24 (CLAUDE.md content in FTR-21) |
| 4.03 | Reconciliation items documented before download | FTR-24 |
| 4.04 | Assessment HTML template download | FTR-22 Project Audit / Health Check |
| 4.05 | Logo reminder | FTR-22 (close-out); also enforced in FTR-16 Brand Setup |
| 4.06 | Close-out summary rendered as inline HTML card matrix | FTR-22 |

## Section 5 — Produced Agent Instructions: 32 Required Items

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 5.01 | WHO BUILT THIS & WHY IT WORKS | FTR-02 Agent Identity & Framework Personality |
| 5.02 | WHAT WOULD KEVIN DO | FTR-02 |
| 5.03 | PROCESS SAFEGUARD — STANDING RULE | FTR-03 Process Safeguard |
| 5.04 | STARTUP DISPLAY | FTR-09 Startup Display & Reminder Mode |
| 5.05 | AGENT ROLE | FTR-04 Agent Role & Project Identity |
| 5.06 | PROJECT IDENTITY | FTR-04 |
| 5.07 | DOCUMENT ID SYSTEM | FTR-08 File Naming, Track IDs & Versioning |
| 5.08 | CONNECTORS & CAPABILITIES | FTR-05 Connectors & Capabilities |
| 5.09 | FILE STORAGE & TOOLING | FTR-06 File Storage & Transfer Rules |
| 5.10 | FOLDER STRUCTURE | FTR-07 Folder Structure |
| 5.11 | FILE NAMING & VERSIONING | FTR-08 |
| 5.12 | BRAND STANDARDS | FTR-16 Brand Setup |
| 5.13 | PDF RULE — NON-NEGOTIABLE | FTR-11 PDF Rule |
| 5.14 | TRACKER IMPLEMENTATION GUIDE | FTR-13 Document Tracker System |
| 5.15 | DOCUMENT WORKFLOW & STATUS SYSTEM | FTR-10 Document Workflow & Status System |
| 5.16 | SEEDED WARNING | FTR-10 |
| 5.17 | HANDOFF PROTOCOL | FTR-19 Session Handoff Protocol |
| 5.18 | COWORK INTEGRATION | FTR-20 Cowork Integration |
| 5.19 | PROJECT AUDIT | FTR-22 Project Audit / Health Check |
| 5.20 | ACTIVE FLAGS | FTR-14 Active Flags Tracker |
| 5.21 | AGENT INSTRUCTIONS SYNC | FTR-23 Agent Instructions Sync |
| 5.22 | BOOTSTRAP RERUN INSTRUCTIONS | FTR-24 Agent Instructions Generation & Deploy |
| 5.23 | KEY DOCUMENTS | FTR-24 |
| 5.24 | ONGOING RESPONSIBILITIES | FTR-24 |
| 5.25 | GETTING HELP | FTR-02 Agent Identity & Framework Personality |
| 5.26 | IMPORTANT LIMITATIONS | FTR-24 |
| 5.27 | STARTUP REMINDER MODE | FTR-09 Startup Display & Reminder Mode |
| 5.28 | BOOTSTRAP RECONCILIATION ITEMS | FTR-24 |
| 5.29 | SETUP & CHANGE LOG | FTR-24 |
| 5.30 | PROJECT CACHE | FTR-15 Project Cache |
| 5.31 | CLAUDE.MD — COWORK CONTEXT FILE | FTR-21 CLAUDE.md Cowork Context File |
| 5.32 | MARKDOWN SIDECARS | FTR-12 Markdown Sidecars |

## Section 6 — Appendices

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 6.01 | Appendix A: Project Type Profiles | FTR-04 Agent Role & Project Identity (role statements, folders, prefixes by type) |
| 6.02 | Appendix B: Brand Element Framework | FTR-16 Brand Setup |
| 6.03 | Appendix C: Profile Templates | FTR-17 Entity / Organization Profile |

## Section 7 — Personality and Branding

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 7.01 | Kevin Framework branding | FTR-02 Agent Identity & Framework Personality |
| 7.02 | Tone | FTR-02 |
| 7.03 | Email draft capability | FTR-02 |
| 7.04 | "What Would Kevin Do" named rule | FTR-02 |
| 7.05 | Patience instruction | FTR-02 |

## Section 8 — Project Cache

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 8.01 | Project Cache concept — Project Files bridge | FTR-15 Project Cache |
| 8.02 | Cache directory — flat staging | FTR-15 |
| 8.03 | Cache manifest tracker | FTR-15 |
| 8.04 | Auto-registration — files at first setup | FTR-15 |
| 8.05 | Manual registration command | FTR-15 |
| 8.06 | Refresh command — full copy run | FTR-15 |
| 8.07 | Recursive scan — cache candidate discovery | FTR-15 |
| 8.08 | Copy-only rule — hard rule | FTR-15 |
| 8.09 | Project Files education text | FTR-15 |

## Section 9 — Markdown Sidecars

| Registry ID | Item | Covered by |
|-------------|------|------------|
| 9.01 | Sidecar concept and proactive offer | FTR-12 Markdown Sidecars |
| 9.02 | Sidecar structure | FTR-12 |
| 9.03 | High integrity rules — non-negotiable | FTR-12 |
| 9.04 | Markdown preference — standing rule | FTR-12 |
| 9.05 | Sidecar naming convention and location | FTR-12 |

---

## Bottom line

- **Total registry items:** 91 (Section 1: 11 · Section 2: 15 · Section 3: 6 · Section 4: 6 · Section 5: 32 · Section 6: 3 · Section 7: 5 · Section 8: 9 · Section 9: 5).
- **Total feature files produced:** 24.
- **Coverage:** COMPLETE. Every registry ID from 1.01 through 9.05 maps to exactly one feature file. No registry item is uncovered.

Notes on multi-item features: FTR-01 absorbs all of Section 1's operating behavior; FTR-24 absorbs the Step 15/16 generation and deploy machinery plus the housekeeping template sections (5.22, 5.23, 5.24, 5.26, 5.28, 5.29); FTR-15 and FTR-12 own Sections 8 and 9 wholesale (their template counterparts 5.30 and 5.32 are covered in the same files). Registry cross-references at the top of each feature file (registry_refs frontmatter) are the authoritative per-file mapping and match this table.