superviber/blue
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
blue/.blue/docs/rfcs/0020-rfc-source-link-resolution.md
Eric Garcia 16d45d9a11 feat: alignment dialogue subagents, MCP instructions, and document batch 
Alignment dialogues now use custom `alignment-expert` subagents with
max_turns: 10, tool restrictions (Read/Grep/Glob), and hard 400-word
output limits. Judge protocol injects as prose via RFC 0023. Moved
Blue voice patterns from CLAUDE.md to MCP server instructions field
for cross-repo portability.

Includes RFCs 0017-0026, spikes, and alignment dialogues from
2026-01-25/26 sessions.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-26 07:09:39 -05:00

913 B
Raw Blame History

RFC 0020: RFC Source Link Resolution
Status Draft
Date 2026-01-26
Source Spike RFC Source Link Generation
Related RFC 0022: Filesystem Authority

Summary

RFC metadata's Source Spike field renders as plain text instead of a clickable markdown link. When blue_rfc_create is called with source_spike, the value is stored and rendered verbatim. Users cannot navigate directly from an RFC to its source spike.

Current behavior: | **Source Spike** | Spike Title | Expected behavior: | **Source Spike** | [Spike Title](../spikes/date-title.md) |

The store already provides find_document(DocType::Spike, title) which returns the spike's file_path. The fix is to resolve spike titles to markdown links at RFC creation time.

Test Plan

  • TBD

"Right then. Let's get to it."

— Blue