@codedrifters/configulator 0.0.261 → 0.0.263

package/lib/index.js

@@ -5285,6 +5285,86 @@ var meetingAnalystSubAgent = {
     "5. **Bi-directional traceability.** Every document and issue created by",
     "   this pipeline must link back to the meeting source, and the meeting",
     "   source documents must link forward to everything created from them.",
+    "6. **Respect meeting type and areas.** Read the `meeting_type` and",
+    "   `areas` values from the meeting frontmatter before starting Phase 1.",
+    "   Apply the type-specific rules from the **Meeting type handling**",
+    "   table (phases 1\u20132) and the area-filtered routing rules from the",
+    "   **Areas filtering** table (phase 4).",
+    "",
+    "---",
+    "",
+    "## Meeting type handling",
+    "",
+    "Meeting frontmatter is expected to carry a `meeting_type` field whose",
+    "value is one of the project's concrete meeting-type `id`s (declared",
+    "via `AgentConfigOptions.meetings.meetingTypes`). Each concrete `id`",
+    "maps to one of six generic **meeting kinds** that drive type-specific",
+    "extraction rules:",
+    "",
+    "| Kind | Primary outputs | Phase-1/2 rules |",
+    "|------|-----------------|-----------------|",
+    "| `planning` | Sprint/plan updates, task issues, requirement drafts | Extract every task assignment. Phase 4 updates the active sprint-plan doc directly and creates one issue per assigned task. |",
+    "| `review` | Retro notes, follow-up issues, status updates, requirement revisions | Mark completed tasks in the active sprint-plan doc. Capture retrospective learnings inside the meeting notes \u2014 do not spawn a separate retro document. |",
+    "| `brainstorm` | Future-feature candidates, research topics, very few Firm decisions | Lower the bar for Open Questions. Do **not** create requirement or ADR issues from brainstorm output unless the item is explicitly marked **Firm**. Prefer research/discovery issues for promising ideas. |",
+    "| `standup` | Action items, blockers, status updates | Do not produce requirement, ADR, or BDR drafts. Phase 3 (Draft) is almost always skipped. Focus on action-item issues and sprint-plan status updates. |",
+    "| `external` | Customer/competitive intel, people/company profiles, lead capture | Default every attendee outside the team into **People of Interest**. Default every organization mentioned into **Companies of Interest** (signal threshold still applies). Capture stated customer pain points as candidate **BR** (business requirements), not FR. |",
+    "| `other` | General meeting extraction | Apply the default workflow with no type-specific overrides. |",
+    "",
+    "**How to resolve the kind:**",
+    "",
+    "1. Read `meeting_type` from the frontmatter.",
+    "2. Look up the matching `id` in the project's **Recognized meeting",
+    "   types** table (rendered below when `meetingTypes` is declared).",
+    "3. Use the `Kind` column value. If the table is absent, the `id` is",
+    "   unknown, or the `Kind` column is `\u2014`, fall back to `other`.",
+    "4. Apply the rules in the row above **in addition to** the normal",
+    "   phase workflow \u2014 never as a replacement.",
+    "",
+    "If `meeting_type` is missing, invalid, or the declared `id` is not in",
+    "the project's table, note it in the extraction's Open Questions and",
+    "proceed with the default workflow (treat as `other`).",
+    "",
+    "## Areas filtering",
+    "",
+    "Meeting frontmatter may carry an `areas: [...]` list whose values",
+    "match `id`s from the project's **Area \u2192 doc-root mapping** table",
+    "(declared via `AgentConfigOptions.meetings.meetingAreas`). The list",
+    "scopes phase-4 direct edits and cross-references to the doc-root",
+    "sub-folders registered for those areas. A given area's effective",
+    "path resolves as `<docsRoot>/<docRoot>` \u2014 `docsRoot` comes from",
+    "`AgentPathsConfig.docsRoot`; `docRoot` is the sub-folder shown in",
+    "the **Area \u2192 doc-root mapping** table.",
+    "",
+    "**Gating contract (phase 4 only):**",
+    "",
+    "- **Scoped in:** direct edits and cross-reference stubs under the",
+    "  `docRoot` of every `id` present in the meeting's `areas` list.",
+    "- **Scoped out:** direct edits to any doc-root sub-folder that is",
+    "  declared in the project's area map but whose `id` is **not** in",
+    "  the meeting's `areas`. For those out-of-scope areas, create",
+    "  follow-up issues instead of editing the doc directly.",
+    "- **Not gated:** issue creation (requirements, ADRs, profiles,",
+    "  research) is always in scope regardless of areas.",
+    "",
+    "**Resolution rules:**",
+    "",
+    "1. If the meeting's `areas` frontmatter is missing or empty **and**",
+    "   the project has declared a non-empty `meetingAreas` map, no",
+    "   doc-root sub-folder is gated in: direct edits to any declared",
+    "   `docRoot` sub-folder are out-of-scope and become follow-up issues",
+    "   per step 6. Only the default meetings root (`meetingsRoot`)",
+    "   remains editable.",
+    "2. If `areas` lists an `id` that is not in the project's area map,",
+    "   note it in the extraction's Open Questions and treat the unknown",
+    "   `id` as absent. Do **not** invent a doc-root path for it.",
+    "3. Out-of-scope direct edits become `type:docs` follow-up issues on",
+    "   phase 4 step 6, with the area noted in the issue body.",
+    "",
+    "When the project has **not** declared any `meetingAreas` at all,",
+    "this section applies degenerately \u2014 no areas are gated, no",
+    "follow-up issues are synthesized for missing areas, and phase-4",
+    "direct edits follow the default workflow (step 6 edits any doc",
+    "flagged as Firm, unrestricted by `docRoot`).",
     "",
     "---",
     "",
@@ -5342,7 +5422,13 @@ var meetingAnalystSubAgent = {
     "",
     "### Steps",
     "",
-    "1. Read the transcript file specified in the issue body.",
+    "1. Read the transcript file specified in the issue body. Parse the",
+    "   meeting-note frontmatter first, capturing `meeting_type` and",
+    "   `areas`. Resolve `meeting_type` to a kind using the **Meeting type",
+    "   handling** table; note the resolved kind in the extraction",
+    "   frontmatter. If `meeting_type` is missing or not in the project's",
+    "   Recognized meeting types table, treat it as `other` and flag it",
+    "   in Open Questions.",
     "2. Identify and categorize content into these buckets:",
     "",
     "   | Bucket | What to look for |",
@@ -5368,14 +5454,32 @@ var meetingAnalystSubAgent = {
     "   - Companies of Interest (with type and context)",
     "   - Strategic / Product Direction",
     "",
-    "4. **Create downstream phase issues** using `gh issue create`:",
+    "   Carry `meeting_type`, the resolved `meeting_kind`, and `areas`",
+    "   into the extraction frontmatter so downstream phases can gate",
+    "   behaviour without re-parsing the meeting note.",
+    "",
+    "4. **Apply type-specific rules.** Consult the **Meeting type handling**",
+    "   table for the resolved kind and apply its phase-1 rules in",
+    "   addition to the default extraction above. Examples:",
+    "   - `standup`: skip requirement, ADR, and BDR extraction; focus on",
+    "     action items and status.",
+    "   - `brainstorm`: emphasize Open Questions and Future Features.",
+    "     Only mark decisions as Firm when the transcript is unambiguous.",
+    "   - `external`: default attendees outside the team into People of",
+    "     Interest; default organizations mentioned into Companies of",
+    "     Interest (signal threshold still applies); capture customer",
+    "     pain points as candidate BR (not FR).",
+    "",
+    "5. **Create downstream phase issues** using `gh issue create`:",
     "   - Always create a `meeting:notes` issue (blocked on this extract issue)",
     "   - If requirements OR decisions/ADRs identified, create a `meeting:draft` issue",
-    "     (blocked on the notes issue)",
+    "     (blocked on the notes issue). For kind `standup`, skip the",
+    "     `meeting:draft` issue \u2014 standup meetings almost never produce",
+    "     formal drafts.",
     "   - Always create a `meeting:link` issue \u2014 blocked on the draft issue if one",
     "     was created, otherwise blocked on the notes issue",
     "",
-    "5. Commit, push, and close the extract issue.",
+    "6. Commit, push, and close the extract issue.",
     "",
     "---",
     "",
@@ -5432,18 +5536,38 @@ var meetingAnalystSubAgent = {
     "### Steps",
     "",
     "1. Read the drafts from Phase 3 (if they exist) and the extraction from Phase 1.",
+    "   Re-read the extraction frontmatter for `meeting_kind` and `areas`,",
+    "   then build the area-gate: the set of `docRoot` sub-folders that",
+    "   are in scope for direct edits on this meeting. Apply the rules in",
+    "   the **Areas filtering** section above.",
     "2. Create requirement issues using `gh issue create` with appropriate labels.",
     "   Include a `## Traceability` section in each issue body linking back to",
-    "   the source meeting and extraction file.",
+    "   the source meeting and extraction file. Issue creation is **not**",
+    "   gated by areas.",
     "3. Create ADR issues if technology decisions need formal records.",
-    "   Include a `## Traceability` section in each.",
+    "   Include a `## Traceability` section in each. Not gated by areas.",
     "4. Create action item issues for tasks that are not document-related.",
-    "   Include a `## Traceability` section in each.",
-    "5. Cross-reference the meeting in any existing documents that were discussed.",
-    "6. Apply direct product/strategy doc updates for items flagged as **Firm**",
-    "   confidence in the extraction.",
+    "   Include a `## Traceability` section in each. Not gated by areas.",
+    "5. Cross-reference the meeting in any existing documents that were",
+    "   discussed **and that live under an in-scope `docRoot`**. For",
+    "   discussed documents under an out-of-scope `docRoot`, open a",
+    "   follow-up `type:docs` issue instead of editing the doc directly.",
+    "6. Apply direct product/strategy doc updates for items flagged as",
+    "   **Firm** confidence. When the project declares `meetingAreas`,",
+    "   gate these edits: only apply them when the target path lies",
+    "   under an in-scope `docRoot`, and for Firm items targeting an",
+    "   out-of-scope `docRoot` open a follow-up `type:docs` issue",
+    "   noting the area and the target path. When the project has not",
+    "   declared any `meetingAreas`, apply Firm updates unrestricted",
+    "   (the degenerate case above). For the kind `planning`, also",
+    "   update the active sprint-plan doc directly (when the",
+    "   sprint-plan doc's area is in-scope, or always when no",
+    "   `meetingAreas` are declared); for the kind `review`, mark",
+    "   completed tasks in that same doc.",
     "7. **Update the extraction file** with a `## Downstream Artifacts` section",
-    "   listing every issue and document created from this meeting.",
+    "   listing every issue and document created from this meeting. Note",
+    "   any items that were deferred to follow-up issues because of the",
+    "   area gate.",
     "8. **Update the meeting notes** with a `## Related Issues` section listing",
     "   all issues created from this meeting.",
     "9. Comment on the parent extract issue with a summary linking to all",
@@ -5527,7 +5651,17 @@ var meetingAnalysisBundle = {
         "Use `/process-meeting <path>` to process a meeting transcript through a",
         "4-phase pipeline (extract \u2192 notes \u2192 draft \u2192 link). Each phase runs as a",
         "separate agent session tracked by a GitHub issue with a `meeting:*` label.",
-        "See the `meeting-analyst` agent definition for full workflow details."
+        "See the `meeting-analyst` agent definition for full workflow details.",
+        "",
+        "Meeting notes may declare a `meeting_type` (one of the project's",
+        "recognized types) and an `areas: [...]` list. The `meeting_type`",
+        "resolves to a generic kind \u2014 `planning` / `review` / `brainstorm` /",
+        "`standup` / `external` / `other` \u2014 that drives type-specific",
+        "extraction rules in phases 1\u20132. The `areas` list scopes phase-4",
+        "direct edits to the doc-root sub-folders declared in the project's",
+        "**Area \u2192 doc-root mapping** table. When both fields are absent",
+        "the pipeline falls back to the default workflow (kind `other`,",
+        "no area gating)."
       ].join("\n"),
       platforms: {
         cursor: { exclude: true }
@@ -14456,7 +14590,7 @@ var slackBundle = {
 // src/agent/bundles/software-profile.ts
 var softwareProfileAnalystSubAgent = {
   name: "software-profile-analyst",
-  description: "Researches a software product (competitor, adjacent, incumbent, enabler, infrastructure, or ecosystem-tool) from public sources, produces a structured markdown profile, and contributes rows to a shared feature matrix ranked against configurable segment-importance weights, then enqueues downstream `company:research` and `people:research` issues for the vendor company and primary-attribution founders/leaders surfaced during profiling. One product per session, tracked by software:* GitHub issue labels.",
+  description: "Researches a software product (competitor, adjacent, incumbent, enabler, infrastructure, or ecosystem-tool) from public sources, produces a structured markdown profile, contributes rows to a shared feature matrix ranked against configurable segment-importance weights, maps features back to the BCM capability model and flags unmapped features, then enqueues downstream `bcm:outline`, `company:research`, and `people:research` issues for new sub-capabilities, the vendor company, and primary-attribution founders/leaders surfaced during profiling. One product per session, tracked by software:* GitHub issue labels.",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 80,
   platforms: { cursor: { exclude: true } },
@@ -14466,8 +14600,9 @@ var softwareProfileAnalystSubAgent = {
     "You research a single software product from public sources and write",
     "a structured markdown profile. Each profile cycle runs across a small",
     "sequence of GitHub issues \u2014 one per phase \u2014 and produces a single",
-    "profile file on disk, a set of feature-matrix rows, and optional",
-    "follow-up research issues for adjacent products.",
+    "profile file on disk, a set of feature-matrix rows, a back-mapping",
+    "onto the BCM capability model, and optional follow-up research",
+    "issues for adjacent products.",
     "",
     "This agent is **domain-neutral**. It makes no assumptions about what",
     "the consuming project sells, which industry it serves, or which",
@@ -14512,6 +14647,14 @@ var softwareProfileAnalystSubAgent = {
     "   weights belong in `docs/src/content/docs/project-context.md` (or an override",
     "   passed in the issue body). This agent reads them; it never",
     "   invents them.",
+    "8. **Map back to the capability model.** The BCM capability model is",
+    "   the single source of truth for what the business does. Every",
+    "   feature on every profile is mapped to the owning capability in the",
+    "   BCM tree during the map phase. Features that match nothing in the",
+    "   tree are candidates for new BCM sub-capabilities \u2014 they are",
+    "   flagged and handed off to the `bcm-writer` bundle via",
+    "   `bcm:outline` issues. This agent never authors BCM documents",
+    "   itself.",
     "",
     "---",
     "",
@@ -14577,14 +14720,15 @@ var softwareProfileAnalystSubAgent = {
     "## State Machine Overview",
     "",
     "```",
-    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510   \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510   \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510   \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
-    "\u2502 1. RESEARCH  \u2502\u2500\u2500\u25B6\u2502 2. PROFILE   \u2502\u2500\u2500\u25B6\u2502 3. MATRIX    \u2502\u2500\u2500\u25B6\u2502 4. FOLLOWUP  \u2502",
-    "\u2502 Collect      \u2502   \u2502 Write the    \u2502   \u2502 Extract      \u2502   \u2502 Enqueue      \u2502",
-    "\u2502 public       \u2502   \u2502 structured   \u2502   \u2502 feature rows \u2502   \u2502 research for \u2502",
-    "\u2502 sources into \u2502   \u2502 markdown     \u2502   \u2502 and score    \u2502   \u2502 adjacent     \u2502",
-    "\u2502 bounded      \u2502   \u2502 profile to   \u2502   \u2502 against the  \u2502   \u2502 products     \u2502",
-    "\u2502 notes file   \u2502   \u2502 <PROFILES>/  \u2502   \u2502 weights      \u2502   \u2502 surfaced     \u2502",
-    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518   \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518   \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518   \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u25021.RESEARCH\u2502\u2500\u25B6\u25022.PROFILE \u2502\u2500\u25B6\u25023.MATRIX  \u2502\u2500\u25B6\u25024.MAP     \u2502\u2500\u25B6\u25025.FOLLOWUP\u2502",
+    "\u2502Collect   \u2502  \u2502Write the \u2502  \u2502Extract   \u2502  \u2502Map each  \u2502  \u2502Enqueue   \u2502",
+    "\u2502public    \u2502  \u2502structured\u2502  \u2502feature   \u2502  \u2502feature to\u2502  \u2502research  \u2502",
+    "\u2502sources   \u2502  \u2502markdown  \u2502  \u2502rows and  \u2502  \u2502BCM       \u2502  \u2502for       \u2502",
+    "\u2502into      \u2502  \u2502profile to\u2502  \u2502score     \u2502  \u2502capability\u2502  \u2502adjacent  \u2502",
+    "\u2502bounded   \u2502  \u2502<PROFILES>\u2502  \u2502against   \u2502  \u2502and flag  \u2502  \u2502products  \u2502",
+    "\u2502notes file\u2502  \u2502          \u2502  \u2502weights   \u2502  \u2502gaps      \u2502  \u2502surfaced  \u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
     "```",
     "",
     "**Issue labels encode the phase:**",
@@ -14593,20 +14737,22 @@ var softwareProfileAnalystSubAgent = {
     "|-------|-------|-------------|",
     "| `software:research` | 1. Research | Gather public sources. Write a bounded research-notes file. Create the profile issue. |",
     "| `software:profile` | 2. Profile | Read the research notes. Write the structured profile to `<PROFILES_DIR>`. Create the matrix issue. |",
-    "| `software:matrix` | 3. Matrix | Read the profile. Extract feature rows into `<MATRIX_FILE>`. Score against segment weights. Create the follow-up issue if warranted. |",
-    "| `software:followup` | 4. Followup | Read the profile. Enqueue software-research issues for adjacent products surfaced in the profile. |",
+    "| `software:matrix` | 3. Matrix | Read the profile. Extract feature rows into `<MATRIX_FILE>`. Score against segment weights. Create the map issue. |",
+    "| `software:map` | 4. Map | Read the profile and matrix rows. Map each feature to the owning BCM capability. Write the mapping back onto the profile. Enqueue `bcm:outline` follow-ups for unmapped features above the configured threshold. Create the followup issue. |",
+    "| `software:followup` | 5. Followup | Read the profile. Enqueue software-research issues for adjacent products surfaced in the profile. |",
     "",
     "All issues also carry `type:software-profile` and a `status:*` label.",
     "",
     "**Issue count per product cycle:** 1 research + 1 profile + 1 matrix +",
-    "0\u20131 followup = **3\u20134 sessions**. The followup phase is skipped when",
-    "the profile did not surface any adjacent product worth researching.",
+    "1 map + 0\u20131 followup = **4\u20135 sessions**. The followup phase is",
+    "skipped when the profile did not surface any adjacent product worth",
+    "researching.",
     "",
     "**Shortened paths:**",
     "- Research phase determines the product is out of scope (not",
     "  relevant, insufficient public material) \u2192 research issue closes",
     "  with a justification and no downstream issues are created \u2192 **1 session**.",
-    "- Narrow product with no adjacent candidates \u2192 **3 sessions**.",
+    "- Narrow product with no adjacent candidates \u2192 **4 sessions**.",
     "",
     "---",
     "",
@@ -14625,11 +14771,25 @@ var softwareProfileAnalystSubAgent = {
     "| `<PRODUCT_SLUG>` | Short kebab-case slug identifying the product | derived from the product name |",
     "| `<COMPANY_PROFILES_DIR>` | Where existing company profiles live (for duplicate detection during followup) | `docs/companies/profiles/` |",
     "| `<PEOPLE_PROFILES_DIR>` | Where existing people profiles live (for duplicate detection during followup) | `docs/people/profiles/` |",
+    `| \`<BCM_DOC_ROOT>\` | Root folder for BCM capability-model documents (used by Phase 4 to locate capabilities) | \`${DEFAULT_AGENT_PATHS.bcmRoot}/\` |`,
+    "| `<BCM_CAPABILITY_MAP>` | Capability-map file that lists the L1/L2/L3 hierarchy | `<BCM_DOC_ROOT>/capability-map.md` |",
+    "| `<UNMAPPED_THRESHOLD>` | Minimum number of unmapped features on a single profile that triggers a `bcm:outline` follow-up for that feature cluster | `1` (every unmapped feature triggers a `bcm:outline`) |",
     "",
     "If `docs/src/content/docs/project-context.md` specifies a different software-research",
     "tree (for example by reusing the research-pipeline deliverables",
     "folder), prefer that. Otherwise fall back to the defaults above.",
     "",
+    "The `<BCM_DOC_ROOT>` default above is sourced from configulator's",
+    "`DEFAULT_AGENT_PATHS.bcmRoot`. If the consuming project's capability",
+    "model lives somewhere else, pass an override in the invoking issue",
+    "body or extend this rule in `agentConfig.rules` \u2014 reading",
+    "`agentConfig.paths.bcmRoot` directly is not currently wired through",
+    "to rule content at synth time. Override `<UNMAPPED_THRESHOLD>` the",
+    "same way when the default (one `bcm:outline` per unmapped feature)",
+    "is too noisy \u2014 for example, raise it to `3` to require at least",
+    "three unmapped features on a single profile before any follow-ups",
+    "are filed.",
+    "",
     "---",
     "",
     "## Agent Loop",
@@ -14638,7 +14798,7 @@ var softwareProfileAnalystSubAgent = {
     "",
     "1. Claim one open `type:software-profile` issue using phase priority:",
     "   `software:research` > `software:profile` > `software:matrix` >",
-    "   `software:followup`.",
+    "   `software:map` > `software:followup`.",
     "2. Transition `status:ready` \u2192 `status:in-progress` and create the",
     "   branch per your project's branch-naming convention.",
     "3. Execute the phase handler that matches the issue's `software:*`",
@@ -14773,7 +14933,12 @@ var softwareProfileAnalystSubAgent = {
     "",
     "   ## Features",
     "   <grouped bullet list of notable features, each cited. These become",
-    "   the rows in the feature matrix during Phase 3.>",
+    "   the rows in the feature matrix during Phase 3 and the rows of the",
+    "   capability mapping during Phase 4.>",
+    "",
+    "   ## Capability Mapping",
+    "   _To be filled in during Phase 4 (Map). Leave as",
+    "   `_Pending capability mapping \u2014 filled in Phase 4._` until then._",
     "",
     "   ## Technology Signals",
     "   <stack hints from docs, integrations, and public engineering",
@@ -14879,18 +15044,141 @@ var softwareProfileAnalystSubAgent = {
     "",
     "5. **Update the matrix front-matter** (`updated: YYYY-MM-DD`).",
     "",
-    "6. **Decide whether a follow-up issue is warranted.** Create a",
-    "   `software:followup` issue (depending on this matrix issue) only",
-    "   if the profile lists at least one adjacent product candidate.",
-    "   Otherwise, note in the matrix issue's closing comment that no",
-    "   follow-up is needed.",
+    "6. **Create the `software:map` issue** with",
+    "   `Depends on: #<matrix-issue>`. Its body references the profile",
+    "   path, the matrix file path, the BCM document root",
+    "   (`<BCM_DOC_ROOT>`), the capability map file",
+    "   (`<BCM_CAPABILITY_MAP>` if it exists), and the unmapped-feature",
+    "   threshold (`<UNMAPPED_THRESHOLD>`). The map phase always runs \u2014",
+    "   every profile is mapped back to the capability model regardless",
+    "   of whether any adjacent products were surfaced.",
     "",
     "7. **Commit and push** the matrix file (and any profile updates).",
     "   Close the matrix issue.",
     "",
     "---",
     "",
-    "## Phase 4: Followup (`software:followup`)",
+    "## Phase 4: Map (`software:map`)",
+    "",
+    "**Goal:** Map each feature on the profile back to the owning",
+    "capability in the BCM capability model, write the mapping onto the",
+    "profile, and enqueue `bcm:outline` follow-ups for features that do",
+    "not match any existing capability.",
+    "",
+    "**Budget:** No new web searches. Read the profile, matrix, and BCM",
+    "tree; write the mapping section onto the profile; open",
+    "`bcm:outline` issues for the gaps.",
+    "",
+    "### Capability Mapping Format",
+    "",
+    "The mapping lives in the `## Capability Mapping` section of the",
+    "profile file. It is a table with one row per feature and explicit",
+    "evidence for each mapping decision:",
+    "",
+    "```markdown",
+    "## Capability Mapping",
+    "",
+    "_Mapped against `<BCM_CAPABILITY_MAP>` on YYYY-MM-DD._",
+    "",
+    "| feature | capability (id \xB7 name) | tier | confidence | notes |",
+    "|---------|-----------------------|------|------------|-------|",
+    "| <feature> | <bcm-id> \xB7 <capability name> | L1/L2/L3 | high/medium/low | <evidence or rationale> |",
+    "| <feature> | _unmapped_ | \u2014 | \u2014 | Candidate for new BCM sub-capability. Tracked in #<bcm-outline-issue> |",
+    "```",
+    "",
+    "Confidence levels:",
+    "",
+    "- **high** \u2014 the feature's jobs-to-be-done clearly match the",
+    "  capability's definition and business object.",
+    "- **medium** \u2014 the feature plausibly maps to the capability, but the",
+    "  match is partial (e.g. the feature covers only one facet of the",
+    "  capability, or the capability's definition is broader than the",
+    "  feature).",
+    "- **low** \u2014 the feature overlaps the capability only tangentially.",
+    "  Prefer `_unmapped_` over a low-confidence match when the feature",
+    "  is a genuine capability gap rather than a near-miss.",
+    "",
+    "### Steps",
+    "",
+    "1. **Load the BCM tree.** Read `<BCM_CAPABILITY_MAP>` if it exists,",
+    "   otherwise walk `<BCM_DOC_ROOT>/` for capability-model documents.",
+    "   Build an in-session index of `{ id, name, tier, business_object }`",
+    "   entries. If the tree is empty (no BCM documents yet), note the",
+    "   gap in the profile's `## Risks / Open Questions`, skip the",
+    "   per-feature mapping, and mark **every** feature as a candidate",
+    "   for a new sub-capability \u2014 subject to `<UNMAPPED_THRESHOLD>`.",
+    "",
+    "2. **Read the profile file** and extract the `## Features` bullets.",
+    "   Each bullet is one row in the mapping table.",
+    "",
+    "3. **Map each feature to the best-fit capability.** Preferred",
+    "   algorithm:",
+    "   - Match against the capability's **business object** first (the",
+    "     thing the capability acts on).",
+    "   - Then match against the capability's **definition** and",
+    "     jobs-to-be-done.",
+    "   - Tie-break in favor of the most specific (deepest tier)",
+    "     capability \u2014 an L3 match beats an L2 match that covers it.",
+    "",
+    "4. **Record low-confidence mappings explicitly** \u2014 never hide a weak",
+    "   match behind a high-confidence label. If the best available",
+    "   match is low-confidence, mark the feature `_unmapped_` instead",
+    "   and describe the near-miss in the `notes` column.",
+    "",
+    "5. **Count unmapped features.** If the count meets or exceeds",
+    "   `<UNMAPPED_THRESHOLD>` (default `1`), open one `bcm:outline`",
+    "   issue per unmapped feature. The issue must carry:",
+    "",
+    "   - `type:bcm-document`",
+    "   - `bcm:outline`",
+    "   - `priority:medium`",
+    "   - `status:ready`",
+    "",
+    "   The issue body must include:",
+    "   - A **discovery source** line naming this software profile",
+    "     (`Discovered while mapping: <product name>`)",
+    "   - A link to the software profile path",
+    "     (`Software profile: <PROFILES_DIR>/<PRODUCT_SLUG>.md`)",
+    "   - The feature name, its one-line description from the profile,",
+    "     and a candidate capability name framed as a noun (BIZBOK-aligned)",
+    "   - Enough identifying metadata that the `bcm-writer` agent can",
+    "     begin the outline phase without revisiting this software",
+    "     profile",
+    "",
+    "6. **Avoid duplicate `bcm:outline` issues.** Before opening one,",
+    "   scan `<BCM_DOC_ROOT>/` for an existing capability that covers",
+    "   the feature (in case the tree grew between the matrix and map",
+    "   phases) and scan open issues carrying `bcm:outline` so this",
+    "   phase never re-queues a capability that is already being",
+    "   outlined. If a match is found, reuse it as a cross-reference in",
+    "   the mapping table instead of opening a new issue.",
+    "",
+    "7. **Write the `## Capability Mapping` section** back onto the",
+    "   profile file, replacing the `_Pending capability mapping \u2014 filled",
+    "   in Phase 4._` placeholder. Preserve every other section of the",
+    "   profile verbatim \u2014 this phase only rewrites the mapping section.",
+    "",
+    "8. **Create the `software:followup` issue** with",
+    "   `Depends on: #<map-issue>`. Its body references the profile path",
+    "   and lists any adjacent products the profile's Follow-up",
+    "   Candidates section identified. Skip creating the followup issue",
+    "   only when the profile lists zero adjacent products, zero",
+    "   primary-attribution people, and the vendor already has a",
+    "   company profile \u2014 note the skip in the map issue's closing",
+    "   comment.",
+    "",
+    "9. **Assume the peer is present.** This phase assumes the",
+    "   `bcm-writer` bundle is enabled in the consuming project. If the",
+    "   bundle has been disabled, flag the map issue with",
+    "   `status:needs-attention` and list the unmapped features that",
+    "   could not be routed \u2014 never invent an alternative label",
+    "   taxonomy.",
+    "",
+    "10. **Commit and push** the updated profile. Close the map issue.",
+    "",
+    "---",
+    "",
+    "## Phase 5: Followup (`software:followup`)",
     "",
     "**Goal:** Create downstream research issues for the adjacent products,",
     "vendor company, and primary-attribution people surfaced in the",
@@ -15010,10 +15298,15 @@ var softwareProfileAnalystSubAgent = {
     "",
     "- `<NOTES_DIR>/` \u2014 research-notes files (Phase 1)",
     "- `<PROFILES_DIR>/` \u2014 software profiles (Phase 2, updated in later",
-    "  phases)",
+    "  phases including the `## Capability Mapping` section in Phase 4)",
     "- `<MATRIX_FILE>` \u2014 shared feature matrix (Phase 3)",
     "",
-    "In Phase 4, this agent also **creates `company:research` and",
+    "In Phase 4, this agent **creates `bcm:outline` issues** for every",
+    "unmapped feature that meets the `<UNMAPPED_THRESHOLD>` so the",
+    "`bcm-writer` bundle can author the new sub-capability. It never",
+    "authors BCM capability-model documents itself.",
+    "",
+    "In Phase 5, this agent also **creates `company:research` and",
     "`people:research` issues** for the vendor company and primary-",
     "attribution people surfaced in the profile that are not already",
     "tracked under `<COMPANY_PROFILES_DIR>/` or `<PEOPLE_PROFILES_DIR>/`.",
@@ -15022,15 +15315,18 @@ var softwareProfileAnalystSubAgent = {
     "`people-profile-analyst` agents, which pick up the issues this",
     "pipeline creates.",
     "",
-    "The pipeline produces **software profiles, notes, and matrix rows",
-    "only**. Deeper research on adjacent products is delegated to new",
-    "cycles of this same pipeline via `software:research` issues. Deeper",
-    "research on the vendor company and primary-attribution people is",
-    "delegated to the `company-profile` and `people-profile` bundles via",
+    "The pipeline produces **software profiles, notes, matrix rows, and capability mappings**.",
+    "Deeper research on adjacent products is delegated to new cycles of",
+    "this same pipeline via `software:research` issues. New BCM",
+    "sub-capabilities for unmapped features are delegated to the",
+    "`bcm-writer` bundle via `bcm:outline` issues. Deeper research on",
+    "the vendor company and primary-attribution people is delegated to",
+    "the `company-profile` and `people-profile` bundles via",
     "`company:research` and `people:research` issues. This agent never",
-    "writes company profiles, person profiles, formal requirement",
-    "documents, or comparative long-form analyses itself. Keep this",
-    "boundary clean so the software-profile pipeline stays generic.",
+    "writes BCM documents, company profiles, person profiles, formal",
+    "requirement documents, or comparative long-form analyses itself.",
+    "Keep this boundary clean so the software-profile pipeline stays",
+    "generic.",
     "",
     "---",
     "",
@@ -15045,31 +15341,41 @@ var softwareProfileAnalystSubAgent = {
     "  `docs/src/content/docs/project-context.md` or an explicit issue-body override. If",
     "  neither is available, fall back to the single-segment default and",
     "  flag the gap \u2014 never guess.",
-    "- **Delegate, don't duplicate.** The vendor company and primary-",
-    "  attribution people surfaced during profiling are handed off to the",
-    "  `company-profile` and `people-profile` bundles via",
-    "  `company:research` and `people:research` issues in Phase 4 \u2014 never",
-    "  inlined as company or person profiles in this pipeline.",
-    "- **Check before enqueueing.** Before opening a `company:research`",
-    "  or `people:research` issue, verify no existing profile or open",
-    "  research issue already covers the candidate. Reuse existing",
-    "  profiles as cross-references rather than re-queuing research.",
+    "- **Delegate, don't duplicate.** Unmapped capabilities are handed off",
+    "  to the `bcm-writer` bundle via `bcm:outline` issues in Phase 4.",
+    "  The vendor company and primary-attribution people surfaced during",
+    "  profiling are handed off to the `company-profile` and",
+    "  `people-profile` bundles via `company:research` and",
+    "  `people:research` issues in Phase 5 \u2014 never inlined as BCM",
+    "  documents, company profiles, or person profiles in this pipeline.",
+    "- **Check before enqueueing.** Before opening a `bcm:outline`,",
+    "  `company:research`, or `people:research` issue, verify no existing",
+    "  document or open issue already covers the candidate. Reuse",
+    "  existing BCM documents and profiles as cross-references rather",
+    "  than re-queuing work.",
+    "- **Respect the threshold.** Phase 4 opens `bcm:outline` issues only",
+    "  when the count of unmapped features on a single profile meets or",
+    "  exceeds `<UNMAPPED_THRESHOLD>`. The default is `1` \u2014 one unmapped",
+    "  feature triggers one outline issue. Raise the threshold in the",
+    "  invoking issue body or in the consuming project's",
+    "  `agentConfig.rules` when the default is too noisy.",
     "- **Restrain the queue \u2014 people only.** The vendor company always",
     "  qualifies (duplicate check aside). For people, only enqueue",
     "  research for those with **primary attribution** \u2014 founders, the",
     "  current CEO, principal creators, lead maintainers, or the head of",
     "  product. Do not open issues for every name on the vendor's about",
     "  page, every investor, or every advisor.",
-    "- **Produce profiles and matrix rows, not requirement or evaluation",
-    "  documents.** Do not open `type:requirement` or formal evaluation",
-    "  issues from this pipeline. Follow-up research is scoped through",
-    "  `software:research`, `company:research`, and `people:research`",
-    "  only."
+    "- **Produce profiles, matrix rows, and capability mappings \u2014 not",
+    "  BCM documents, requirement documents, or evaluation documents.**",
+    "  Do not open `type:requirement` or formal evaluation issues from",
+    "  this pipeline, and never author BCM capability-model documents",
+    "  inline. Follow-up work is scoped through `software:research`,",
+    "  `bcm:outline`, `company:research`, and `people:research` only."
   ].join("\n")
 };
 var profileSoftwareSkill = {
   name: "profile-software",
-  description: "Kick off a software-profile pipeline. Creates a software:research issue for the given product and dispatches Phase 1 (Research) in the software-profile-analyst agent. Phase 4 (Followup) enqueues downstream `company:research` and `people:research` issues for the vendor company and primary-attribution founders/leaders surfaced in the profile.",
+  description: "Kick off a software-profile pipeline. Creates a software:research issue for the given product and dispatches Phase 1 (Research) in the software-profile-analyst agent. Phase 4 (Map) writes a BCM capability mapping onto the profile and enqueues `bcm:outline` issues for unmapped features. Phase 5 (Followup) enqueues downstream `company:research` and `people:research` issues for the vendor company and primary-attribution founders/leaders surfaced in the profile.",
   disableModelInvocation: true,
   userInvocable: true,
   context: "fork",
@@ -15096,6 +15402,9 @@ var profileSoftwareSkill = {
     "- `weights: <table>` \u2014 override the segment-importance weights for",
     "  this profile cycle (otherwise loaded from",
     "  `docs/src/content/docs/project-context.md`)",
+    "- `unmapped_threshold: <n>` \u2014 override the Phase 4 threshold for",
+    "  opening `bcm:outline` issues (default `1` \u2014 one unmapped feature",
+    "  triggers one outline issue)",
     "- `sources: <list>` \u2014 additional authorized sources beyond public web",
     "",
     "## Default Paths",
@@ -15115,16 +15424,20 @@ var profileSoftwareSkill = {
     "2. Execute Phase 1 (Research) of the software-profile-analyst",
     "   agent.",
     "3. Phase 1 creates the `software:profile` issue. Phase 2 creates",
-    "   the `software:matrix` issue. Phase 3 may create a",
-    "   `software:followup` issue. Each downstream issue declares its",
-    "   `Depends on:` predecessor.",
+    "   the `software:matrix` issue. Phase 3 creates the `software:map`",
+    "   issue. Phase 4 creates the `software:followup` issue (unless the",
+    "   profile surfaced zero follow-ups). Each downstream issue",
+    "   declares its `Depends on:` predecessor.",
     "",
     "## Output",
     "",
     "- A research-notes file under the project's notes directory",
-    "- A single software profile under the profiles directory",
+    "- A single software profile under the profiles directory, including",
+    "  a `## Capability Mapping` section written in Phase 4",
     "- One or more rows appended to the shared feature-matrix file,",
     "  scored against the configured segment weights",
+    "- `bcm:outline` issues for each unmapped feature above the",
+    "  configured threshold (handed off to the `bcm-writer` bundle)",
     "- Optional follow-up `software:research` issues for adjacent",
     "  products surfaced in the profile",
     "- `company:research` issue for the vendor company (handed off to",
@@ -15132,46 +15445,132 @@ var profileSoftwareSkill = {
     "- `people:research` issues for primary-attribution founders, CEOs,",
     "  or principal creators (handed off to the `people-profile`",
     "  bundle)",
-    "- This pipeline produces **software profiles, notes, and matrix",
-    "  rows only** \u2014 it does not write company profiles, person",
-    "  profiles, or formal requirement documents itself."
+    "- This pipeline produces **software profiles, notes, matrix rows,",
+    "  and capability mappings** \u2014 it does not write BCM documents,",
+    "  company profiles, person profiles, or formal requirement",
+    "  documents itself."
+  ].join("\n")
+};
+var mapSoftwareSkill = {
+  name: "map-software",
+  description: "Kick off a standalone software-capability mapping session. Creates a software:map issue for an already-profiled product and dispatches Phase 4 (Map) in the software-profile-analyst agent. Produces the `## Capability Mapping` section on the profile and enqueues `bcm:outline` issues for unmapped features above the configured threshold.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "software-profile-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Map Software",
+    "",
+    "Kick off a standalone `software:map` session for a product that",
+    "already has a profile file and matrix rows on disk. Creates a",
+    "`software:map` issue carrying the profile path and dispatches Phase",
+    "4 (Map) in the software-profile-analyst agent.",
+    "",
+    "Use this skill when:",
+    "",
+    "- A profile was written before the map phase existed and is still",
+    "  carrying the `_Pending capability mapping \u2014 filled in Phase 4._`",
+    "  placeholder.",
+    "- The BCM tree has grown enough that a previously-mapped profile",
+    "  should be re-mapped against the updated capability model.",
+    "- A profile's features were edited after the map phase ran and the",
+    "  mapping table is now out of date.",
+    "",
+    "## Usage",
+    "",
+    "/map-software <product-slug-or-profile-path>",
+    "",
+    "Optional extensions in the issue body:",
+    "- `unmapped_threshold: <n>` \u2014 override the threshold for opening",
+    "  `bcm:outline` issues (default `1`)",
+    "- `bcm_doc_root: <path>` \u2014 override the BCM document root",
+    "  (otherwise the configulator default at",
+    "  `DEFAULT_AGENT_PATHS.bcmRoot`)",
+    "- `capability_map: <path>` \u2014 override the capability-map file",
+    "  (otherwise `<BCM_DOC_ROOT>/capability-map.md`)",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/src/content/docs/project-context.md` or",
+    "`agentConfig.rules`, the mapping reads from:",
+    "",
+    `- \`${DEFAULT_AGENT_PATHS.bcmRoot}/\` \u2014 BCM capability-model documents`,
+    `- \`${DEFAULT_AGENT_PATHS.bcmRoot}/capability-map.md\` \u2014 capability map`,
+    "",
+    "and writes back to `docs/software/profiles/<slug>.md` under the",
+    "`## Capability Mapping` section only. No other section of the",
+    "profile is rewritten.",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `software:map` issue with `type:software-profile`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   profile path and any overrides.",
+    "2. Execute Phase 4 (Map) of the software-profile-analyst agent.",
+    "3. Phase 4 writes the `## Capability Mapping` section, enqueues",
+    "   `bcm:outline` issues for unmapped features above the threshold,",
+    "   and \u2014 when the profile lists adjacent products or",
+    "   primary-attribution people \u2014 creates the `software:followup`",
+    "   issue.",
+    "",
+    "## Output",
+    "",
+    "- An updated `## Capability Mapping` section on the target profile",
+    "- `bcm:outline` issues for each unmapped feature above the",
+    "  configured threshold (handed off to the `bcm-writer` bundle)",
+    "- An optional `software:followup` issue when the profile surfaced",
+    "  adjacent products, a vendor company without an existing profile,",
+    "  or primary-attribution people",
+    "- This skill does not run Phase 1\u20133 \u2014 it assumes the profile and",
+    "  matrix rows already exist on disk."
   ].join("\n")
 };
 var softwareProfileBundle = {
   name: "software-profile",
-  description: "Software research, profiling, and feature-matrix pipeline: research, profile, matrix, followup. Enabled by default; domain-neutral; filesystem-durable between phases; ranks features against configurable segment-importance weights. Phase 4 (Followup) hands the vendor company and primary-attribution founders/leaders off to the `company-profile` and `people-profile` bundles via `company:research` and `people:research` issues.",
+  description: "Software research, profiling, feature-matrix, and capability-mapping pipeline: research, profile, matrix, map, followup. Enabled by default; domain-neutral; filesystem-durable between phases; ranks features against configurable segment-importance weights and maps features back to the BCM capability model. Phase 4 (Map) hands unmapped features off to the `bcm-writer` bundle via `bcm:outline` issues. Phase 5 (Followup) hands the vendor company and primary-attribution founders/leaders off to the `company-profile` and `people-profile` bundles via `company:research` and `people:research` issues.",
   appliesWhen: () => true,
   rules: [
     {
       name: "software-profile-workflow",
-      description: "Describes the 4-phase software-profile pipeline, the software:* label taxonomy, the generic software-type taxonomy, and the segment-weights convention that drives feature-matrix scoring.",
+      description: "Describes the 5-phase software-profile pipeline, the software:* label taxonomy, the generic software-type taxonomy, the segment-weights convention that drives feature-matrix scoring, and the capability-mapping hand-off to the bcm-writer bundle.",
       scope: AGENT_RULE_SCOPE.ALWAYS,
       content: [
         "# Software Profile Workflow",
         "",
         "Use `/profile-software <product-name>` to kick off a software",
-        "research, profiling, and feature-matrix pipeline. The pipeline",
-        "runs in up to 4 phases \u2014 research, profile, matrix, followup \u2014",
-        "each tracked by its own GitHub issue labeled",
-        "`software:research`, `software:profile`, `software:matrix`, or",
-        "`software:followup`. All issues carry `type:software-profile`.",
-        "",
-        "The pipeline produces **software profiles, research notes, and",
-        "rows in a shared feature matrix**. Features are ranked against",
-        "segment-importance weights declared in",
-        "`docs/src/content/docs/project-context.md` under a `## Segment Weights` section.",
-        "Deeper research on adjacent products surfaced in a profile is",
-        "delegated to new cycles of this same pipeline via",
-        "`software:followup` issues. Deeper research on the vendor",
-        "company and primary-attribution founders/product leaders is",
-        "delegated to the `company-profile` and `people-profile`",
-        "bundles via `company:research` and `people:research` issues",
-        "opened during Phase 4 (Followup).",
+        "research, profiling, feature-matrix, and capability-mapping",
+        "pipeline. The pipeline runs in up to 5 phases \u2014 research,",
+        "profile, matrix, map, followup \u2014 each tracked by its own GitHub",
+        "issue labeled `software:research`, `software:profile`,",
+        "`software:matrix`, `software:map`, or `software:followup`. All",
+        "issues carry `type:software-profile`.",
+        "",
+        "The pipeline produces **software profiles, research notes, rows",
+        "in a shared feature matrix, and capability mappings onto the",
+        "BCM tree**. Features are ranked against segment-importance",
+        "weights declared in `docs/src/content/docs/project-context.md`",
+        "under a `## Segment Weights` section. Features that do not map",
+        "to any existing capability in the BCM tree are flagged during",
+        "the map phase as candidates for new BCM sub-capabilities and",
+        "handed off to the `bcm-writer` bundle via `bcm:outline` issues",
+        "(subject to a configurable threshold). Deeper research on",
+        "adjacent products surfaced in a profile is delegated to new",
+        "cycles of this same pipeline via `software:followup` issues.",
+        "Deeper research on the vendor company and primary-attribution",
+        "founders/product leaders is delegated to the `company-profile`",
+        "and `people-profile` bundles via `company:research` and",
+        "`people:research` issues opened during Phase 5 (Followup).",
+        "",
+        "Use `/map-software <product-slug>` to kick off a standalone",
+        "`software:map` session for a profile that already exists on",
+        "disk \u2014 for example, when the BCM tree has grown enough that a",
+        "previously-mapped profile should be re-mapped.",
         "",
         "See the `software-profile-analyst` agent definition for full",
         "workflow details, default paths, the software-type taxonomy,",
-        "the segment-weights convention, and phase-by-phase",
-        "instructions."
+        "the segment-weights convention, the capability-mapping format,",
+        "and phase-by-phase instructions."
       ].join("\n"),
       platforms: {
         cursor: { exclude: true }
@@ -15179,13 +15578,13 @@ var softwareProfileBundle = {
       tags: ["workflow"]
     }
   ],
-  skills: [profileSoftwareSkill],
+  skills: [profileSoftwareSkill, mapSoftwareSkill],
   subAgents: [softwareProfileAnalystSubAgent],
   labels: [
     {
       name: "type:software-profile",
       color: "0E8A16",
-      description: "Work that produces or maintains a software profile, research notes, or feature-matrix rows"
+      description: "Work that produces or maintains a software profile, research notes, feature-matrix rows, or capability mappings"
     },
     {
       name: "software:research",
@@ -15202,10 +15601,15 @@ var softwareProfileBundle = {
       color: "D4C5F9",
       description: "Phase 3: extract feature rows into the shared feature matrix and score them against segment weights"
     },
+    {
+      name: "software:map",
+      color: "A2EEEF",
+      description: "Phase 4: map each feature back to the BCM capability model, write the mapping onto the profile, and enqueue `bcm:outline` issues for unmapped features above the configured threshold"
+    },
     {
       name: "software:followup",
       color: "FBCA04",
-      description: "Phase 4: enqueue follow-up research issues for adjacent products, the vendor company, and primary-attribution people surfaced in the profile"
+      description: "Phase 5: enqueue follow-up research issues for adjacent products, the vendor company, and primary-attribution people surfaced in the profile"
     }
   ]
 };
@@ -16088,18 +16492,24 @@ function renderMeetingTypes(types, agendaTemplateRoot) {
     "This project declares a meeting-type taxonomy through",
     "`AgentConfigOptions.meetings.meetingTypes`. When classifying a",
     "meeting transcript, pick the `id` from this list that best fits the",
-    "meeting; do **not** invent new type identifiers. Agenda-template",
-    `paths below are resolved relative to \`${resolvedRoot}\`.`,
-    "",
-    "| ID | Label | Scope | Cadence | Default duration | Agenda template |",
-    "|----|-------|-------|---------|------------------|-----------------|"
+    "meeting; do **not** invent new type identifiers. The `Kind` column",
+    "maps each concrete `id` onto the generic meeting-kind taxonomy",
+    "(`planning` / `review` / `brainstorm` / `standup` / `external` /",
+    "`other`) documented in the **Meeting type handling** section \u2014",
+    "apply the type-specific rules listed there based on this kind.",
+    "Agenda-template paths below are resolved relative to",
+    `\`${resolvedRoot}\`.`,
+    "",
+    "| ID | Label | Kind | Scope | Cadence | Default duration | Agenda template |",
+    "|----|-------|------|-------|---------|------------------|-----------------|"
   ];
   for (const type of types) {
+    const kind = type.kind ? `\`${type.kind}\`` : "\u2014";
     const cadence = type.cadence ? `\`${type.cadence}\`` : "\u2014";
     const duration = type.defaultDurationMinutes !== void 0 ? `${type.defaultDurationMinutes} min` : "\u2014";
     const template = type.agendaTemplatePath ? `\`${type.agendaTemplatePath}\`` : "\u2014";
     lines.push(
-      `| \`${type.id}\` | ${type.label} | \`${type.scope}\` | ${cadence} | ${duration} | ${template} |`
+      `| \`${type.id}\` | ${type.label} | ${kind} | \`${type.scope}\` | ${cadence} | ${duration} | ${template} |`
     );
   }
   return lines.join("\n");
@@ -16110,10 +16520,12 @@ function renderMeetingAreas(areas) {
     "",
     "This project declares a meeting-area routing map through",
     "`AgentConfigOptions.meetings.meetingAreas`. When a meeting note's",
-    "frontmatter carries an `area:` value matching an `id` below, route",
-    "phase-4 direct edits into the corresponding sub-tree of the docs",
-    "root (`AgentPathsConfig.docsRoot`). Meetings whose `area` does not",
-    "match any declared entry fall back to the default meetings root.",
+    "frontmatter carries an `areas:` list, route phase-4 direct edits",
+    "into the corresponding sub-trees of the docs root",
+    "(`AgentPathsConfig.docsRoot`). See the **Areas filtering** section",
+    "of the `meeting-analyst` agent for the full gating contract.",
+    "Meetings whose `areas` list is empty or does not match any",
+    "declared entry fall back to the default meetings root.",
     "",
     "| Area ID | Label | Doc-root sub-folder |",
     "|---------|-------|---------------------|"