spec: Add Bluespeed architecture spec (v0.1) for local-first AI on Bluefin#236
Open
lazypower wants to merge 8 commits intoprojectbluefin:mainfrom
Open
spec: Add Bluespeed architecture spec (v0.1) for local-first AI on Bluefin#236lazypower wants to merge 8 commits intoprojectbluefin:mainfrom
lazypower wants to merge 8 commits intoprojectbluefin:mainfrom
Conversation
dosubot
bot
added
the
size:XS
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
dosubot
bot
added
area/bluespeed
Contributor
|
This is awesome! I made it all the way through but have some follow up questions, I'd like to merge this and tweak along the way. |
Contributor
|
I'm going to merge this now so we don't slow down (sorry I'm at kubecon!). And then we'll open a discussion. Thanks for working on this chuck! |
castrojo
approved these changes
Mar 25, 2026
dosubot
bot
added
the
kind/enhancement
auto-merge was automatically disabled
March 31, 2026 13:05
Head branch was pushed to by a user without write access
lazypower
force-pushed
the
specs/bluespeed
branch
2 times, most recently
from
d02031e to
e707a6b
Compare
…uefin Comprehensive specification for the Bluespeed initiative (common#100): local-first AI diagnostics and knowledge retrieval for the Bluefin desktop, built on Goose, ramalama, and the MCP server ecosystem. Covers architecture, component stack, knowledge pipeline (crawl → chunk → embed → sqlite-vec), bluefin-knowledge-mcp interface spec, context window management with hard governors, tool routing with visibility filtering, model evaluation criteria and candidates, system prompt design, safety model, prompt injection mitigations, failure modes, resource budgets, testing plan, and phased rollout. Research directory includes distilled reference material from all upstream dependencies (linux-mcp-server, okp-mcp, ramalama, goose, gnome-mcp-server, dosu) and Bluefin docs crawl analysis. Ready for architectural review — open questions flagged inline.
- Remove apple hardware - s/cron/systemd timers - s/podman-compose/quadlets
…wledge layer (v0.2) Follows the spec: prefix pattern from the v0.1 commit. Captures both the addition and the architectural consolidation without getting wordy.
…etrieval isolation, error contract (v0.2)
…g mitigation (v0.2)
lazypower
force-pushed
the
specs/bluespeed
branch
from
e707a6b to
86a5c2d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Comprehensive specification for the Bluespeed initiative (common#100): local-first AI diagnostics and knowledge retrieval for the Bluefin desktop, built on Goose, ramalama, and the MCP server ecosystem.
Covers architecture, component stack, knowledge pipeline (crawl → chunk → embed → sqlite-vec), bluefin-knowledge-mcp interface spec, context window management with hard governors, tool routing with visibility filtering, model evaluation criteria and candidates, system prompt design, safety model, prompt injection mitigations, failure modes, resource budgets, testing plan, and phased rollout.
Research directory includes distilled reference material from all upstream dependencies (linux-mcp-server, okp-mcp, ramalama, goose, gnome-mcp-server, dosu) and Bluefin docs crawl analysis.
Ready for architectural review — open questions flagged inline.