aiwg 2026.6.1 → 2026.6.2

package/agentic/code/addons/aiwg-utils/rules/delivery-policy.md

@@ -34,8 +34,20 @@ Located at `.aiwg/aiwg.config` (top level), the `delivery` block contains:
   "delivery": {
     "mode": "direct" | "feature-branch" | "pr-required",
     "default_branch": "main",
+    "committer": {
+      "name": "Joseph Magly",
+      "email": "1159087+jmagly@users.noreply.github.com"
+    },
+    "signing": {
+      "format": "openpgp" | "ssh" | "x509",
+      "key": "0117DAAA677A5BF2",
+      "key_file": "~/.config/.../signing.key",
+      "program": "gpg",
+      "enforce": "commits" | "tags" | "all"
+    },
     "require_ci_green": true,
     "force_push_policy": "never" | "main-only-blocked" | "allowed",
+    "require_signed_commits": true,
     "auto_close_issues": true,
     "issue_comment_on_cycle": true,
     "rationale": "Free-text explaining why this mode was chosen"
@@ -44,6 +56,11 @@ Located at `.aiwg/aiwg.config` (top level), the `delivery` block contains:
     "primary": "origin",
     "issue_tracker": "origin",
     "ci": "origin",
+    "tracker_actor": {
+      "login": "roctinam",
+      "via": "tea" | "gh" | "mcp" | "api",
+      "forbid_actors": ["roctibot"]
+    },
     "secondary": [ ... ]
   }
 }
@@ -134,6 +151,19 @@ use the AIWG issue CLI for local issue operations. Do not invent a parallel
 issue-provider setting when `remotes.issue_tracker` already answers where
 issues live.
 
+### Rule 3.5: Use Configured Delivery Identity For Mutations
+
+When delivery identity fields are present, they are authoritative for writes:
+
+- Commits → use `delivery.committer.name` / `delivery.committer.email` when set; otherwise inherit normal `git config`.
+- Commit and tag signing → if `delivery.require_signed_commits: true` or `delivery.signing.enforce` covers the artifact being written, use `delivery.signing.format`, `delivery.signing.key` or `delivery.signing.key_file`, and `delivery.signing.program` where applicable.
+- Issue comments, issue closures, PRs, labels, and milestone writes → use `remotes.tracker_actor.login` through `remotes.tracker_actor.via` when set.
+- Never author delivery mutations as any login listed in `remotes.tracker_actor.forbid_actors`.
+
+Read-only tracker operations may use any available credential, including an MCP token, because they do not create attribution. Delivery mutations must use the configured actor or stop and ask the operator to configure/authorize a route.
+
+`aiwg doctor` warns when signed commits are required but no signing key/key file is declared, and when an issue tracker remote is configured without a `tracker_actor` in a repo likely to perform tracker writes.
+
 ### Rule 4: Surface, Don't Re-Ask
 
 When the policy is already declared, do NOT use `AskUserQuestion` (or equivalent interactive prompt) to ask the user "feature branch or direct to main?" — the answer is already in the config. Instead:
@@ -178,5 +208,7 @@ This rule complements:
 
 - `aiwg config get --project delivery.mode` — CLI command to inspect current policy
 - `aiwg config set --project delivery.mode <mode>` — change project policy
+- `aiwg config set --project delivery.signing.key <key-id>` — declare the signing key used for commits/tags
+- `aiwg config set --project remotes.tracker_actor.login <login>` — declare the forge actor for issue/PR writes
 - `agentic/code/frameworks/sdlc-complete/skills/issue-create/SKILL.md` — example of a skill that reads `aiwg.config` properly
 - `agentic/code/frameworks/sdlc-complete/skills/flow-delivery-track/SKILL.md` — delivery workflow integration

package/agentic/code/addons/aiwg-utils/skills/aiwg-utils-quickref/SKILL.md

@@ -191,6 +191,17 @@ aiwg discover "choose issue tracking backend"  # → issue-workflow-guide
 aiwg discover "project-local customization"     # → project-local quickstart / customization docs
 ```
 
+### Feature domains the steward owns (expansion / persona / project)
+
+Three cross-cutting domains that no framework quickref owns — consult the `steward-quickref` kernel skill, or discover directly:
+
+```bash
+aiwg discover "author an expansion"            # → scaffold-extension / -addon / -framework
+aiwg discover "create a persona"               # → soul-create (author a SOUL identity)
+aiwg discover "select a persona"               # → persona agents (agentic/code/agents/personas/*)
+aiwg discover "scaffold a project"             # → new-project (+ new-bundle for project-local)
+```
+
 ### Project-local extensions (pilot → promote)
 
 AIWG supports authoring rules/skills/agents per-project under `.aiwg/{extensions,addons,frameworks,plugins}/<name>/` — pilot here, promote upstream when mature.

package/agentic/code/addons/aiwg-utils/skills/new-project/SKILL.md

@@ -2,7 +2,14 @@
 namespace: aiwg
 name: new-project
 platforms: [all]
-description: Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry
+description: Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry. Use when creating or scaffolding a new project.
+triggers:
+  - scaffold a project
+  - create a project
+  - new project
+  - aiwg new
+  - project scaffolding
+  - project-local bundle
 ---
 
 <!-- AIWG-SKILL-CALLOUT -->

package/agentic/code/addons/aiwg-utils/skills/scaffold-addon/SKILL.md

@@ -2,8 +2,14 @@
 namespace: aiwg
 name: scaffold-addon
 platforms: [all]
-description: Create a complete addon package structure inside agentic/code/addons/
-
+description: Create a complete addon package structure inside agentic/code/addons/. Use when authoring an expansion (addon) for AIWG.
+triggers:
+  - author an addon
+  - create an addon
+  - build an expansion addon
+  - addon authoring
+  - scaffold addon
+  - new expansion
 ---
 
 # Scaffold Addon

package/agentic/code/addons/aiwg-utils/skills/scaffold-extension/SKILL.md

@@ -2,7 +2,14 @@
 namespace: aiwg
 name: scaffold-extension
 platforms: [all]
-description: Create a new extension package inside an existing framework's extensions/ directory
+description: Create a new extension package inside an existing framework's extensions/ directory. Use when authoring an expansion (extension) for AIWG.
+triggers:
+  - author an expansion
+  - build an extension
+  - create an extension package
+  - expansion authoring
+  - scaffold extension
+  - new expansion
 ---
 
 # Scaffold Extension

package/agentic/code/addons/aiwg-utils/skills/scaffold-framework/SKILL.md

@@ -2,8 +2,14 @@
 namespace: aiwg
 name: scaffold-framework
 platforms: [all]
-description: Create a complete framework package structure inside agentic/code/frameworks/
-
+description: Create a complete framework package structure inside agentic/code/frameworks/. Use when authoring an expansion (framework) for AIWG.
+triggers:
+  - author a framework
+  - create a framework
+  - build a framework package
+  - framework authoring
+  - scaffold framework
+  - new expansion
 ---
 
 # Scaffold Framework

package/agentic/code/addons/aiwg-utils/skills/soul-create/SKILL.md

@@ -2,7 +2,14 @@
 namespace: aiwg
 name: soul-create
 platforms: [all]
-description: Generate a SOUL.md identity file from source material, interactive prompts, or an existing voice profile
+description: Generate a SOUL.md identity file from source material, interactive prompts, or an existing voice profile. Use when authoring a persona / soul identity.
+triggers:
+  - create a persona
+  - author a soul
+  - make an identity profile
+  - new persona
+  - generate SOUL.md
+  - persona authoring
 ---
 
 # soul-create

package/agentic/code/addons/aiwg-utils/skills/steward/SKILL.md

@@ -88,6 +88,26 @@ Route these intents directly:
 Canonical docs: `docs/customization/project-local-quickstart.md`, `docs/project-local/overview.md`, and `docs/project-local/manifest-reference.md`. Mention that project-local artifacts are trusted repo code and should be reviewed before deploy.
 
 
+## Feature-Domain Routing (proactive)
+
+Three cross-cutting feature domains fall outside the framework quickrefs and were historically undiscoverable (#1623). The steward owns routing for them via the `steward-quickref` kernel skill. Be **proactive** — these are easy to miss:
+
+| Domain | Canonical discover phrase | Owning capability |
+|---|---|---|
+| **Expansion authoring** (extension/addon/framework) | `aiwg discover "author an expansion"` | `scaffold-extension` / `-addon` / `-framework` |
+| **Persona / SOUL** (author **and** select) | `aiwg discover "create a persona"` · `aiwg discover "select a persona"` | `soul-create`, persona agents under `agentic/code/agents/personas/` |
+| **Project creation** | `aiwg discover "scaffold a project"` | `new-project`, `new-bundle` |
+
+Routing protocol:
+
+1. **Volunteer the affordance** (Norman signifier). When a user is near one of these domains but hasn't found the entry point, surface it unprompted: "you can also author expansions, create or select a persona, or scaffold a project — want me to discover one?"
+2. **Discover, don't dead-end.** Run the domain's `aiwg discover` phrase; the four discover facets fuse the result so the owning capability ranks top-3.
+3. **Re-query on low confidence.** If the first pass is weak, broaden the phrase or try an adjacent domain before concluding "not found" — the `skill-discovery` rule forbids decline-without-search.
+4. **Show the selection.** `aiwg show <type> <name>` for the chosen capability.
+
+See `steward-quickref` for the full anchor tables.
+
+
 ## Capability Matrix Source
 
 The authoritative source is `agentic/code/providers/capability-matrix.yaml`. Key features tracked:

package/agentic/code/addons/aiwg-utils/skills/steward-quickref/SKILL.md

@@ -0,0 +1,87 @@
+---
+namespace: aiwg
+name: steward-quickref
+platforms: [all]
+kernel: true
+description: AUTO-INVOKE for steward feature-domain routing — authoring an expansion (extension/addon/framework), creating or selecting a persona/SOUL identity, or scaffolding a project. Thin discover anchors for the three domains the framework quickrefs don't own.
+triggers:
+  - author an expansion
+  - create a persona
+  - select a persona
+  - scaffold a project
+  - steward routing
+  - which aiwg feature do i use
+  - expansion persona or project
+---
+
+# Steward Quickref
+
+Thin routing anchor for the three cross-cutting **feature domains** that no
+single framework quickref owns: **expansion authoring**, **persona/SOUL
+identity**, and **project creation**. This file holds *guidance + anchoring
+phrases only* — it never inlines skill or agent bodies. The capability index
+does the heavy lifting: each row gives the `aiwg discover` phrase that ranks
+the owning capability top-3 (the four discover facets fuse the result —
+see `src/artifacts/discover-facets.ts`).
+
+> **Always discover, then show.** These phrases are the entry points; fetch the
+> selected artifact with `aiwg show <type> <name>`. Do not browse the
+> filesystem (`skill-discovery` rule).
+
+## Domain 1 — Expansion authoring (extension / addon / framework)
+
+"How do I *build* an AIWG expansion?" — extensions, addons, and frameworks.
+
+| You want to… | Discover phrase | Owning capability |
+|---|---|---|
+| Author an extension | `aiwg discover "author an expansion"` | `scaffold-extension` |
+| Create an addon | `aiwg discover "create an addon"` | `scaffold-addon` |
+| Build a framework | `aiwg discover "scaffold a framework"` | `scaffold-framework` |
+| Pilot then graduate a project-local bundle | `aiwg discover "project-local bundle"` | `new-bundle`, `promote` |
+
+## Domain 2 — Persona / SOUL identity (author **and** select)
+
+"How do I *make* or *choose* an identity/voice?" Personas live at
+`agentic/code/agents/personas/`; SOUL profiles are managed by the `soul-*`
+skills.
+
+| You want to… | Discover phrase | Owning capability |
+|---|---|---|
+| Create / author a persona (SOUL) | `aiwg discover "create a persona"` | `soul-create` |
+| Select / switch a persona identity | `aiwg discover "select a persona"` | persona agents + `soul-apply` |
+| See the persona roster | `aiwg discover "persona"` | `agentic/code/agents/personas/*` |
+| Manage SOUL lifecycle (enable/disable/blend) | `aiwg discover "soul"` | `soul-enable`, `soul-disable`, `soul-blend` |
+
+> Runtime persona *selection UX* (catalog-pick) is an open research area — see
+> spike #1625; for now, discover the persona then activate via the SOUL skills.
+
+## Domain 3 — Project creation (`aiwg new` + project-local)
+
+"How do I *start* an AIWG project?"
+
+| You want to… | Discover phrase | Owning capability |
+|---|---|---|
+| Scaffold a new project | `aiwg discover "scaffold a project"` | `new-project` |
+| Create a project-local bundle | `aiwg discover "project-local bundle"` | `new-bundle` |
+
+## Domain 4 — Provider capability (native vs emulated)
+
+"Does my provider support X natively, or does AIWG emulate it?" Route through
+the steward, which reads `capability-matrix.yaml`.
+
+| You want to… | Discover phrase / route |
+|---|---|
+| Check provider support for a capability | `aiwg discover "provider capability"` → `steward` |
+
+## Steward routing protocol
+
+When a request maps to one of these domains:
+
+1. **Volunteer the affordance** (Norman signifier): if a user is working near a
+   domain but hasn't found it, surface it — "you can also author expansions,
+   create/select a persona, or scaffold a project; want me to discover one?"
+2. **Discover, don't dead-end.** Run the domain's `aiwg discover` phrase.
+3. **Re-query on low confidence.** If the first pass is weak, broaden the
+   phrase or try an adjacent domain phrase before concluding "not found" — the
+   `skill-discovery` rule forbids decline-without-search.
+4. **Show the selection.** `aiwg show <type> <name>` for the chosen capability.

package/agentic/code/agents/personas/aiwg-finder.md

@@ -1,6 +1,12 @@
 ---
 name: aiwg-finder
 description: Capability discovery and tool-selection specialist — the finder for AIWG's 400+ skills, agents, commands, and rules. Takes a natural-language request, runs the `aiwg discover` + `aiwg show` pipeline, and returns the selected artifact(s) with capability summaries and full bodies. Companion to aiwg-steward.
+triggers:
+  - finder persona
+  - discovery persona
+  - capability finder identity
+  - select a finder persona
+  - persona
 model: claude-sonnet-4-6
 tools:
   - Bash

package/agentic/code/agents/personas/aiwg-orchestrator.md

@@ -1,6 +1,13 @@
 ---
 name: aiwg-orchestrator
-description: Full SDLC orchestration persona for end-to-end project management
+description: Full SDLC orchestration persona/identity for end-to-end project management. Use when selecting an orchestration persona to drive multi-agent SDLC workflows.
+triggers:
+  - orchestrator persona
+  - sdlc orchestration identity
+  - project management persona
+  - select an orchestration persona
+  - persona
+  - soul
 model: claude-opus-4-7
 tools:
   - Task

package/agentic/code/agents/personas/aiwg-reviewer.md

@@ -1,6 +1,13 @@
 ---
 name: aiwg-reviewer
-description: Code review persona focused on quality, security, and best practices
+description: Code review persona/identity focused on quality, security, and best practices. Use when selecting a reviewer persona for code or artifact review.
+triggers:
+  - reviewer persona
+  - code review identity
+  - review voice
+  - select a review persona
+  - persona
+  - soul
 model: claude-sonnet-4-6
 tools:
   - Read

package/agentic/code/agents/personas/aiwg-security.md

@@ -1,6 +1,13 @@
 ---
 name: aiwg-security
-description: Security audit persona for threat modeling and vulnerability assessment
+description: Security audit persona/identity for threat modeling and vulnerability assessment. Use when selecting a security persona for review or threat work.
+triggers:
+  - security persona
+  - security reviewer identity
+  - threat-model persona
+  - select a security persona
+  - persona
+  - soul
 model: claude-sonnet-4-6
 tools:
   - Read

package/agentic/code/agents/personas/aiwg-steward.md

@@ -1,6 +1,13 @@
 ---
 name: aiwg-steward
-description: Self-maintenance agent that uses AIWG CLI to keep the installation healthy, current, and correctly configured. Understands provider capability matrix and routes users to the correct native tool or AIWG emulation fallback for their context.
+description: Self-maintenance steward persona/identity that uses the AIWG CLI to keep the installation healthy, current, and correctly configured. Understands the provider capability matrix and routes users to the correct native tool or AIWG emulation fallback for their context.
+triggers:
+  - steward persona
+  - maintenance persona
+  - routing identity
+  - self-maintenance persona
+  - select a steward persona
+  - persona
 model: claude-sonnet-4-6
 tools:
   - Bash
@@ -65,6 +72,10 @@ Route these intents directly:
 
 Canonical docs: `docs/customization/project-local-quickstart.md`, `docs/project-local/overview.md`, and `docs/project-local/manifest-reference.md`. Mention that project-local artifacts are trusted repo code and should be reviewed before deploy.
 
+## Feature-Domain Routing (proactive)
+
+Three cross-cutting domains were historically undiscoverable (#1623): **expansion authoring**, **persona/SOUL** (author and select), and **project creation**. Consult the `steward-quickref` kernel skill and route via `aiwg discover` — `"author an expansion"` → `scaffold-*`, `"create a persona"` / `"select a persona"` → `soul-create` + `agentic/code/agents/personas/*`, `"scaffold a project"` → `new-project`. Be proactive: volunteer the affordance when a user is near a domain but hasn't found it, and re-query on low confidence rather than dead-ending (`skill-discovery` rule).
+
 ## Capability Data Source
 
 The canonical capability matrix lives at:

package/agentic/code/agents/personas/aiwg-writer.md

@@ -1,6 +1,13 @@
 ---
 name: aiwg-writer
-description: Documentation persona for technical writing and content creation
+description: Documentation persona/identity for technical writing, content creation, and applying voice. Use when selecting a writing persona or authoring docs in a chosen voice.
+triggers:
+  - writer persona
+  - documentation persona
+  - technical writing voice
+  - select a writing identity
+  - soul for docs
+  - persona
 model: claude-sonnet-4-6
 tools:
   - Read

package/agentic/code/agents/personas/mc-conductor.md

@@ -1,6 +1,12 @@
 ---
 name: mc-conductor
-description: Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user
+description: Mission Control conductor persona/identity — orchestrates parallel background missions, handles completions and failures, reports to the user. Use when selecting a conductor persona for mission orchestration.
+triggers:
+  - conductor persona
+  - mission control identity
+  - orchestration conductor persona
+  - select a conductor persona
+  - persona
 model: claude-sonnet-4-6
 tools:
   - Bash

package/agentic/code/extensions/research-brainstorming/README.md

@@ -0,0 +1,112 @@
+# Research Brainstorming Extension
+
+Research brainstorming is the loose, early-stage complement to
+`research-complete`. It uses wiki memory and the KB graph for ideas that are not
+ready for `REF-*` source structure, GRADE assessment, or citation-grounded
+synthesis.
+
+## Composition
+
+This extension composes existing AIWG surfaces:
+
+- `kb-ingest`, `aiwg kb`, and knowledge-base templates for wiki pages.
+- Semantic-memory kernel skills: `memory-ingest`, `memory-query-capture`,
+  `memory-log-append`, and `memory-lint`.
+- `aiwg index neighbors --graph kb --node <slug>` for adjacent concepts,
+  entities, syntheses, source summaries, and prior brainstorm notes.
+- `research-query` for citation-backed corpus answers.
+- `induct-research` for mature `REF-*` candidates.
+- `research-store` and `.aiwg/research/working/` for promoted research tasks.
+
+## Corpus-Root Research Repositories
+
+The extension also supports the proven corpus-root layout used by
+`~/dev/research/research-papers`:
+
+```text
+documentation/references/   # REF-XXX 15-section analysis files
+documentation/citations/    # REF-XXX-citations sidecars and backlinks
+documentation/radar/        # live freshness/GRADE radar sidecars
+documentation/profiles/     # PROF-* entity profiles and graph edges
+indices/                    # generated cross-reference and graph indices
+pdfs/full/                  # archived PDFs
+sources/web/                # archived web snapshots
+bibliographies/master.bib   # BibTeX
+```
+
+In that layout, brainstorming stays lightweight until promotion. Promotion
+targets should follow the repository contract:
+
+- Research questions and acquisition targets stay in working notes until they
+  name an actual source or corpus gap.
+- A promoted source candidate becomes a `REF-XXX` induction candidate and must
+  go through source archival, 15-section reference analysis, citation sidecar,
+  live radar sidecar, entity profile updates, bibliography updates, index
+  rebuild, and the repo's `research-lint` / `research-quality-audit` gates.
+- Backlinks are mandatory: citation sidecars need incoming/outgoing consistency,
+  and `PROF-*` profile references need reciprocal REF links.
+- Generated `indices/` are retrieval aids, not hand-authored brainstorm notes.
+
+## Source Labels
+
+Every brainstorming output must label each meaningful item as one of:
+
+- `user-idea`: supplied by the operator.
+- `model-suggestion`: generated during brainstorming and not yet verified.
+- `citation-backed`: grounded in an existing `REF-*`, source summary, or
+  research-query result.
+
+Speculative claims stay in wiki memory until promoted. Do not require GRADE,
+`REF-*`, or citation formatting for `user-idea` and `model-suggestion` notes.
+Require citation and quality handling only when a note becomes a research claim,
+structured synthesis, or source candidate.
+
+## Workflow
+
+1. Capture loose ideas in `.aiwg/kb/brainstorming/` using
+   `research-brainstorm`.
+2. Retrieve neighboring context with `research-brainstorm-query`, backed by
+   `aiwg index neighbors --graph kb`.
+3. Generate exploration outputs: idea maps, question trees, competing
+   hypotheses, synthesis sketches, and exploration plans.
+4. Promote mature material with `research-brainstorm-promote` into research
+   questions, acquisition targets, `REF-*` candidates, gap reports, or synthesis
+   report outlines.
+5. Run the normal research framework once promoted material makes a factual
+   research claim.
+
+## Current Research Grounding
+
+The design follows current GraphRAG/KG-RAG direction: graph retrieval preserves
+relationships that flat chunk retrieval loses, but incomplete graphs can mislead
+retrieval and synthesis. For that reason, this extension keeps source labels,
+neighbor provenance, and promotion gates explicit.
+
+- GraphRAG survey: https://arxiv.org/abs/2501.00309
+- KG-guided RAG: https://arxiv.org/abs/2502.06864
+- KG-RAG under knowledge incompleteness: https://arxiv.org/abs/2504.05163
+- W3C PROV overview: https://www.w3.org/TR/prov-overview/
+- GRADE Working Group: https://www.gradeworkinggroup.org/
+
+## Storage
+
+Default brainstorming notes live under:
+
+```text
+.aiwg/kb/brainstorming/
+```
+
+Promotion targets live under:
+
+```text
+.aiwg/research/working/
+.aiwg/research/reports/
+.aiwg/research/findings/
+```
+
+The KB graph remains the retrieval authority. Rebuild or query it with:
+
+```bash
+aiwg index build --graph kb
+aiwg index neighbors --graph kb --node <slug>
+```

package/agentic/code/extensions/research-brainstorming/fixtures/linked-retrieval.json

@@ -0,0 +1,31 @@
+{
+  "session": "local-first-command-analytics",
+  "seed_node": "local-first-telemetry",
+  "retrieval_command": "aiwg index neighbors --graph kb --node local-first-telemetry",
+  "neighbors": [
+    {
+      "node": "AIWG CLI",
+      "type": "entity",
+      "label": "user-idea",
+      "use": "Identify command surfaces that produce local events."
+    },
+    {
+      "node": "privacy-preserving analytics",
+      "type": "concept",
+      "label": "model-suggestion",
+      "use": "Frame path hashing and argument redaction questions."
+    },
+    {
+      "node": "command-log-design",
+      "type": "brainstorm-note",
+      "label": "user-idea",
+      "use": "Reuse prior notes about scope-aware storage."
+    }
+  ],
+  "output_shape": [
+    "idea map",
+    "question tree",
+    "competing hypotheses",
+    "exploration plan"
+  ]
+}

package/agentic/code/extensions/research-brainstorming/fixtures/loose-session.md

@@ -0,0 +1,41 @@
+# Brainstorm: Local-first command analytics
+
+## Metadata
+
+- Date: 2026-06-17
+- Seed: How can local command usage show which research workflows need better automation?
+- Source labels allowed: user-idea, model-suggestion, citation-backed
+
+## User Ideas
+
+- [user-idea] Operators repeat the same manual CLI sequences when a framework
+  lacks a good high-level skill.
+- [user-idea] Failed commands may be more useful than successful commands for
+  prioritizing documentation.
+
+## Model Suggestions
+
+- [model-suggestion] Group usage by project-relative path so workflows in
+  `.aiwg/research/` can be separated from general maintenance commands.
+- [model-suggestion] Compare high-frequency command clusters against existing
+  skill trigger phrases.
+
+## Citation-Backed Context
+
+- None yet. This note should not be treated as a research claim.
+
+## Open Questions
+
+- Which commands signal research discovery versus research induction?
+- What privacy constraints should apply before any heatmap feature exists?
+
+## Links
+
+- Concepts: [[local-first telemetry]], [[research workflow]]
+- Entities: [[AIWG CLI]]
+- Prior brainstorms: []
+
+## Promotion Candidates
+
+- Research question: Which local usage signals predict missing research skills?
+- Acquisition target: examples of privacy-preserving local analytics in CLI tools

package/agentic/code/extensions/research-brainstorming/fixtures/promotion-ref-candidate-corpus-root.md

@@ -0,0 +1,31 @@
+# Brainstorm Promotion Record
+
+## Source Note
+
+- Brainstorm note: [[graph-rag-for-research-brainstorming]]
+- Selection: GraphRAG may improve research brainstorming retrieval by preserving
+  relationships between concepts, entities, sources, and prior notes.
+- Current label: citation-backed
+
+## Promotion Target
+
+- Type: REF-candidate
+- Path: documentation/references/REF-XXX-graph-rag-survey.md
+- Layout: corpus-root
+
+## Rationale
+
+The candidate names a concrete source family and is ready for the normal
+research-papers induction process. Completion requires more than a note: source
+archive, 15-section REF analysis, citation sidecar, live radar, profile links,
+bibliography update, index rebuild, and lint/quality gates.
+
+## Required Follow-Up
+
+- [ ] Archive source under `pdfs/full/` or `sources/web/`
+- [ ] Create `documentation/references/REF-XXX-*.md`
+- [ ] Create and backlink `documentation/citations/REF-XXX-citations.md`
+- [ ] Create live `documentation/radar/REF-XXX-radar.md`
+- [ ] Update `PROF-*` profile backlinks when applicable
+- [ ] Update `bibliographies/master.bib`
+- [ ] Rebuild `indices/` and run `research-lint` / `research-quality-audit`

package/agentic/code/extensions/research-brainstorming/fixtures/promotion-research-task.md

@@ -0,0 +1,25 @@
+# Brainstorm Promotion Record
+
+## Source Note
+
+- Brainstorm note: [[local-first-command-analytics]]
+- Selection: Which local usage signals predict missing research skills?
+- Current label: user-idea
+
+## Promotion Target
+
+- Type: research-question
+- Path: .aiwg/research/working/research-questions.md
+- Layout: aiwg-research
+
+## Rationale
+
+The idea is specific enough to become a research question but is not yet
+citation-backed. It should become an acquisition/search task before appearing in
+a synthesis report.
+
+## Required Follow-Up
+
+- [ ] Add citations or acquisition tasks before treating as a research claim
+- [ ] Search for prior work on privacy-preserving local developer analytics
+- [ ] Preserve source labels in the promoted artifact