FTR-38 duped-pattern match count: 1 FTR-37 duped-pattern match count: 1 FTR-35 duped-pattern match count: 1 FTR-34 duped-pattern match count: 1 # 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.
Rebrand/FTR-02 rewrite note (added 2026-07-16): FTR-02 was renamed from "Agent Identity & Framework Personality" to "Agent Personality & Tone" and rewritten to a generic, unnamed personality (no "Kevin," no personal email), as part of a whole-line rebrand from Kevin Framework to Claude Project Assistant. Every registry_refs mapping to FTR-02 below (1.09, 5.01, 5.02, 5.25, 7.01-7.05) was rechecked against the rewritten content and still holds — the underlying behavior each registry item describes is still present, just under generic framing. A few of this report's own "Item" label columns (1.03, 1.09, 7.01, 7.04) named the old Kevin-specific mechanic directly; those labels are updated below to describe the behavior generically, matching how the rewritten FTR-02 actually implements them now. No registry ID's coverage changed — only the label wording for items that used to name a mechanic that no longer carries a personal name.
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 | Project assistant 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 | Fallback decision heuristic ("find the next right thing") | 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 | APPROACH & WHY IT WORKS | FTR-02 Agent Personality & Tone |
| 5.02 | FALLBACK DECISION HEURISTIC | 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 Personality & Tone |
| 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 | Product branding & identity framing | FTR-02 Agent Personality & Tone |
| 7.02 | Tone | FTR-02 |
| 7.03 | Email draft capability | FTR-02 |
| 7.04 | Named fallback rule (now generic, unnamed) | 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 |
Section 10 — Additions Beyond the Original Bootstrap Registry
Eighteen features in this database have no registry ID and no entry in Sections 1-9, because none of them come from Project_Kickoff_Seed_Prompt_v2.3.md or Bootstrap_Function_Registry.md at all:
| ID | Title | Source |
|---|---|---|
| FTR-25 | Directory Cleanup & Inventory | Directory_Cleanup_Inventory_Prompt_v1.0.md (not Project_Kickoff_Seed_Prompt_v2.3.md) |
| FTR-26 | Install Manifest & Reconciliation | New capability, no prior source document — built for this database's hosted-catalog model, since the original Bootstrap's rerun-to-reconcile loop (registry item 1.11) assumed the whole seed prompt got re-dropped into a conversation each time, which doesn't apply once installs happen one feature at a time from a hosted site |
| FTR-27 | Legal Citation Management System | Supplied directly by the user, developed and refined in an active litigation project — not extracted from any Bootstrap source document |
| FTR-28 | Multi-AI Research Synthesis System | Supplied directly by the user, generalized from a tool built and used in an active legal casework project — not extracted from any Bootstrap source document |
| FTR-29 | Legal Case Research Synthesis | Supplied directly by the user, de-identified from the same source tool as FTR-28 (original case name, court, and docket replaced with a generic example throughout) — not extracted from any Bootstrap source document |
| FTR-30 | Cascading Research Pipeline | Supplied directly by the user, generalized from a real multi-step campaign-research pipeline they built and ran end-to-end (illustrative example only — no client-identifying specifics carried into the feature) — not extracted from any Bootstrap source document |
| FTR-31 | Preferred MCP Instance | New capability, no prior source document — supplied as a much larger draft spec (full MCP fingerprint detection, engagement modes, capability-map-as-a-service architecture) by the user, then deliberately trimmed to a light version on the user's own explicit direction; only the plain preference-naming mechanic survives into this feature |
| FTR-32 | Cowork Orchestrated Research | Supplied directly by the user as a complete, already-well-structured spec — a third execution mode for the FTR-28 research family, running on Cowork's own batch-tasking ability instead of manual multi-platform submission; not extracted from any Bootstrap source document |
| FTR-33 | Paste-Driven Provenance Archive | Supplied directly by the user, generalized and de-identified from a workflow built and used live in an active legal casework project (original case name and internal tracking reference replaced with generic placeholders throughout) — original use case was building a verbatim statute library from a paywalled legal database; generalized to any access-controlled or agent-unreachable source; not extracted from any Bootstrap source document |
| FTR-34 | Repository Ledger Visualization | Supplied directly by the user as a complete, already-well-structured spec, including a full raw HTML/CSS template — not extracted from any Bootstrap source document. Its raw template and a fabricated live-preview example are packaged as separate non-feature reference assets (see index.md's own table) rather than embedded/escaped inline |
| FTR-35 | Prompt Vetting Checklist | Supplied directly by the user, drafted from a real gap found in production use on the Sluix AEPM pipeline project — not extracted from any Bootstrap source document |
| FTR-36 | Excel Tracker (Base Capability) | Supplied directly by the user, drafted from real production testing in the Chambers v Chambers project — not extracted from any Bootstrap source document |
| FTR-37 | Legal Discovery Tracking | Supplied directly by the user, drafted from real production testing in the Chambers v Chambers project — not extracted from any Bootstrap source document |
| FTR-38 | Multi-Sub-Project Awareness | Supplied directly by the user, drafted from real production use in the S.D project — not extracted from any Bootstrap source document |
| FTR-39 | EML Archiver (Base Capability) | Supplied directly by the user, drafted from real production use in the Cascades UOA (CUOA) Offboarding Response project — not extracted from any Bootstrap source document |
| FTR-40 | Email Topic Discovery | Supplied directly by the user, drafted from real production use in the Cascades UOA (CUOA) Offboarding Response project — not extracted from any Bootstrap source document |
| FTR-41 | Georgia Appellate Rules & Statutes Reference | Supplied directly by the user, built for the TCA (Tripodis v. City of Atlanta) matter — not extracted from any Bootstrap source document |
| FTR-42 | Email Account Awareness & Signature Management | Supplied directly by the user as SPEC_04_IMAP_Email_Awareness_and_Signature_Management.md, developed and validated in a separate "Claude IMAP" project, plus a same-day addendum resolving its three original open items and adding two new requirements -- not extracted from any Bootstrap source document |
If more standalone prompts or new capabilities get added this way in the future, they belong in this section too, not folded into Sections 1-9.
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: 42 — 24 mapped to the 91 registry items above (Sections 1-9), plus 18 (FTR-25, FTR-26, FTR-27, FTR-28, FTR-29, FTR-30, FTR-31, FTR-32, FTR-33, FTR-34, FTR-35, FTR-36, FTR-37, FTR-38, FTR-39, FTR-40, FTR-41, FTR-42) from outside it entirely (Section 10).
- Coverage of the original 91-item registry: 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.