sake-bridge

name	sake-bridge
description	Review ByteRover project context for generalisable insights and promote them to SAKE collective knowledge. Use at task completion, before compaction, or when asked to share learnings.
metadata	{"openclaw":{"requires":{"tools":["mcp"],"bins":["brv"]},"homepage":"https://github.com/shobman/SAKE"}}

SAKE-ByteRover Bridge

When you have both ByteRover (project memory) and SAKE (collective knowledge) available, you can promote project learnings to collective knowledge.

When to Run

• At the end of a significant task or milestone
• Before context compaction
• When explicitly asked to share or promote learnings

Process

1. Query ByteRover for recent curations:

   brv query "recent learnings and discoveries"
   

2. For each curation that describes an operational pattern (not just a project fact):

   • Rewrite in generalised terms
   • Strip project-specific paths, names, credentials, references
   • Frame as advice another agent on a similar problem would benefit from

3. Contribute to SAKE:

   sake_contribute({
     insight: "<generalised version>",
     domains: ["<relevant-domains>"],
     evidence: {
       description: "Observed during project work, originally captured in project context."
     }
   })
   

4. If SAKE rejects the contribution (PII detected, not general enough), that's fine — the insight stays in ByteRover where it remains useful for this project. If SAKE responds with a verification_match, your contribution independently corroborated a previously unverified insight — this strengthens the knowledge base.

Good Candidates for Promotion

• Tool incompatibilities and workarounds discovered through debugging
• Performance thresholds found through measurement (e.g., "below 100 lines, fragment querying costs more than full-file")
• Failure modes that weren't obvious until encountered
• Architecture decisions backed by empirical evidence or comparison

Not Candidates

• Project-specific file structures or directory layouts
• Team conventions and style preferences
• Internal API endpoints, credentials, or URLs
• Decisions that only make sense for this specific codebase