RFC 0016: Context Injection Architecture
- Add blue:// URI scheme for document addressing
- Add manifest.rs for three-tier context configuration
- Implement MCP resources/list and resources/read handlers
- Add `blue context` CLI command for visibility
- Add context_injections audit table (schema v5)
RFC 0017: Dynamic Context Activation (Phase 1)
- Add relevance_edges table for explicit links (schema v6)
- Implement composite session ID: {repo}-{realm}-{random12}
- Add content-hash based staleness detection
- Add tiered refresh policies (SessionStart/OnChange/OnRequest/Never)
- Add rate limiting with 30s cooldown
- Add blue_context_status MCP tool
Drafted from 12-expert alignment dialogue achieving 95% convergence.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
42 lines
1.1 KiB
YAML
42 lines
1.1 KiB
YAML
# Blue Context Manifest (RFC 0016)
|
|
#
|
|
# This file configures what context gets injected into Claude's context window.
|
|
# Three tiers: identity (always), workflow (activity-triggered), reference (on-demand).
|
|
|
|
version: 1
|
|
|
|
# Identity Tier - "Who am I" - Always injected at session start
|
|
# Contains foundational beliefs and voice patterns
|
|
identity:
|
|
sources:
|
|
- uri: blue://docs/adrs/
|
|
label: Architecture Decision Records
|
|
- uri: blue://context/voice
|
|
label: Voice and tone patterns
|
|
max_tokens: 500
|
|
|
|
# Workflow Tier - "What should I do" - Triggered by activity
|
|
# Contains current work context
|
|
workflow:
|
|
sources:
|
|
- uri: blue://state/current-rfc
|
|
label: Active RFC
|
|
refresh_triggers:
|
|
- on_rfc_change
|
|
max_tokens: 2000
|
|
|
|
# Reference Tier - "How does this work" - On-demand via MCP Resources
|
|
# Contains full documentation for deep dives
|
|
reference:
|
|
graph: blue://context/relevance
|
|
max_tokens: 4000
|
|
staleness_days: 30
|
|
|
|
# Plugins - External context providers (optional)
|
|
# plugins:
|
|
# - uri: blue://jira/
|
|
# provides:
|
|
# - ticket-context
|
|
# - acceptance-criteria
|
|
# salience_triggers:
|
|
# - commit_msg_pattern: "^[A-Z]+-\\d+"
|