/cortex-broadcast

name: cortex-broadcast
description: >
  llm-wiki style broadcast ingest — conversational update of related existing
  pages when a Raw has been distilled. Use when the user says "broadcast",
  "跑 broadcast", "compound this into the vault", "merge pending-merge",
  "process broadcast queue", or when cortex-distill invokes broadcast inline
  after Step 8 commit (automatic dispatch for every new / pending-merge Raw).

Cortex Broadcast — Compounding Ingest

Propagate insights from a distilled Raw into related existing Notes/Projects pages through conversational per-page edits.

Resolve Vault Path and Config

Read `~/.cortex/config.json`:

jq -r '.vault_path' ~/.cortex/config.json
jq -r '.broadcast.target_top_n // 5' ~/.cortex/config.json
jq -r '.broadcast.target_min_score // 0.40' ~/.cortex/config.json

If the config file doesn't exist, tell the user to run `/cortexes:genesis` first.

Step 1: Resolve Arguments

The command supports three invocations:

| Form | Action | |------|--------| | `/cortexes:broadcast` (no args) | Pop the first (oldest) Raw from the eligible queue | | `/cortexes:broadcast <raw-path>` | Use the specified Raw (relative or absolute path) | | `/cortexes:broadcast --list` | Print the eligible queue and exit |

Step 2: Build Eligible Queue

A Raw is eligible iff its marker meets **all** of:

• Contains `<!-- distilled: YYYY-MM-DD → ... -->` (Phase 1 processed).
• Outcome is `new` or `pending-merge` (the marker content after `→` is

either a path like `Notes/X.md` / `Projects/Y/Z.md`, **or** starts with `pending-merge:`; anything else — `(skip: routine)`, `(no insight)`, or the pre-Phase-1 legacy `(no extractable content)` — is ineligible).

• Does not already contain any of: `| broadcast:`, `| merged:`,

`| no-broadcast:`.

Build the list via:

cortex-vec broadcast-queue --root <vault>/Raw

This applies the three criteria above against each Raw's authoritative marker (header marker, or last non-empty line) and returns the result FIFO by path. Do **NOT** `grep` the marker string — a meta-session's body quotes it many times, which fools a substring scan. To inspect one file, use `cortex-vec raw-state <file>`.

Step 3: Handle `--list`

If the user invoked `--list`, print each queued Raw with:

• Relative path from vault
• Outcome (extract from marker: `new` if target is a path; `pending-merge`

if marker contains `pending-merge:`)

• Original target (for `pending-merge` Raws; `—` for `new`)

Format:

Eligible queue (N Raws):

  1. Raw/2026/04/17/141013_session_webapi-Notification.md
     outcome: pending-merge → Projects/libsynosysnotify/synooauth flow chart.md (0.48)

  2. Raw/2026/04/17/163941_session_libsynosdk.md
     outcome: new → Projects/libsynosdk/build-flag-semantics.md

Run /cortexes:broadcast to process the first, or /cortexes:broadcast <path> for a specific one.

Exit after listing.

Step 4: Select Raw and Read Content

If no args: pick the first entry from the queue. If `<raw-path>` arg: verify it's eligible; abort with a clear error if not.

Read:

1. The Raw's full content (frontmatter + all sections). 2. The Raw's distilled marker; parse the outcome and (for pending-merge) the original target path and score.

Step 5: Find Candidate Pages

Pick the **most content-ful Discovery or Decision bullet** — the longest bullet with concrete referents (symbols, file paths, bug mechanisms). This is the same heuristic as cortex-distill Stage 2 uses.

Run:

cortex-vec search "<bullet text>" --n <target_top_n>

If the Raw's frontmatter has `repo:`, also pass `--repo <name>` when the query topic looks repo-specific. Omit otherwise.

Filter results to those with `score >= target_min_score`.

If no candidates pass the threshold

If `cortex-vec` ran successfully but zero results meet `score >= target_min_score`:

• For outcome `new`: skip Steps 6–8 entirely. Jump to Step 9 with `pages_touched = []` and tag the terminal state as `no-candidates` (distinct from `no-changes`). Step 9.1 will produce the marker `broadcast: <today> → (no candidates)`.
• For outcome `pending-merge`: the original pending-merge target is still pre-selected in Step 6 regardless of threshold (per Step 6's "absent" clause). Proceed to Step 7 as normal with a single-entry menu.

Announce to the user before jumping:

No candidate pages scored at or above <threshold> for this Raw.
Finalizing as broadcast: (no candidates). Marker will reflect this.

Fallback if `cortex-vec` is unavailable

If the command errors (not found, ECONNREFUSED, etc.):

1. Read `<vault>/_index.md`. 2. Use your own semantic judgment to pick up to `target_top_n` candidate pages that look related to the Raw. 3. Note `candidates_source: llm-fallback` for the log entry later.

Step 6: Pre-select Pending-Merge Target

If the Raw's outcome is `pending-merge`:

• Extract the target path from the marker.
• Find that path in the candidate list.
• If present: mark it as pre-selected `[x]`.
• If absent (score now below threshold, or file renamed): **still

include it** as a pre-selected entry at the top, with a note `(below current threshold)`. Original distill intent overrides current threshold.

Example of the menu line in this case:

[x] 1. Projects/libsynosysnotify/synooauth flow chart.md (0.48)  ← pending-merge target (below current threshold)
````

All other candidates default to unchecked `[ ]`.

## Step 7: Present Menu and Confirm

Display:

Broadcast target candidates for <raw-filename>:

[x] 1. <path> (<score>) ← pending-merge target (if applicable) [ ] 2. <path> (<score>) [ ] 3. <path> (<score>) ...

Toggle: number (1–N) to flip, 'a' all, 'n' none, then Enter to confirm. Cancel: type 'quit' to abort the menu without marking the Raw (no commits have been made yet).

Read the user's toggles until they confirm. Build the final selected list.
If the list is empty after confirmation, jump directly to