{"protocol":[{"slug":"fix","name":"Fix","githubRepo":"issue-c","tagline":"Bug intake and risk memory","visibility":"private","status":"planned","page":{"what":"Fix compiles chaotic bug reports into executable engineering tasks","problem":"Users report 'it's broken' without details. Engineers waste time guessing what happened. AI agents face the same issue — they can't act on vague descriptions.","whoFor":"Engineering teams running AI agents on production codebases","howWorks":"Fix interrogates issues, collects logs, traces root causes, and outputs standard tickets with reproducers. Each fix becomes a permanent memory entry.","related":["memo","link"]}},{"slug":"memo","name":"Memo","githubRepo":"memo-c","tagline":"Project memory compiler","visibility":"private","status":"planned","page":{"what":"Memo compiles project history into executable constraints for AI agents","problem":"Every bug fix contains learned wisdom. But this knowledge scatters across commits, PRs, tickets — invisible to AI. Agents repeat mistakes humans already fixed.","whoFor":"Teams maintaining legacy codebases with AI assistance","howWorks":"Memo extracts causal chains from git history, compiles them into verifiable constraints, and serves them to agents before they touch code.","related":["fix","vibe"]}},{"slug":"link","name":"Link","githubRepo":"context-c","tagline":"Context handoff layer","visibility":"private","status":"planned","page":{"what":"Link captures and restores project context across handoffs","problem":"You take a week off, return to 500 new commits, and have no idea what happened. AI agents face worse — they enter projects with zero context.","whoFor":"Distributed teams with frequent handoffs","howWorks":"Link captures project state before you leave: what you were working on, why, what's next. On return, it restores complete context in one load.","related":["memo","fix"]}},{"slug":"vibe","name":"Vibe","githubRepo":"Vibe-c","tagline":"Style consistency system","visibility":"private","status":"planned","page":{"what":"Vibe enforces consistent aesthetic choices across AI-generated code","problem":"AI generates the same component differently each time. Button radius: 4px, then 8px. Color: blue-tinged, then purple. Codebases become visual mess.","whoFor":"Teams using AI for UI development","howWorks":"Vibe extracts style fingerprints from existing code, locks down preferences, and serves them to AI agents during generation.","related":["memo"]}}],"other":[{"slug":"agent-vault","name":"AgentVault","tagline":"MPC wallet SDK for AI agents","description":"AgentVault enables AI agents to sign transactions without exposing private keys","github":"https://github.com/echowang1/AgentVault","status":"alpha","page":{"what":"MPC wallet SDK for AI agent payments","problem":"Agents need to spend money, but can't hardcode private keys. Existing wallet solutions don't account for agent-specific threat models.","whoFor":"AI agent developers building payment-enabled agents","howWorks":"Multi-party computation keeps keys distributed. Agent requests signatures, secure enclave approves, key material never leaves.","related":[]}},{"slug":"cineweave","name":"CineWeave","tagline":"BYOK-first short film workflow platform","description":"CineWeave is an open-source workflow platform for short film and video content","github":"https://github.com/demshine/cineweave-platform","status":"alpha","org":"demshine","page":{"what":"Open-source workflow platform for short film production","problem":"Short film teams need editing, color, VFX, rendering — but existing tools either lock you in or cost too much.","whoFor":"Independent short film creators","howWorks":"Bring-your-own-key architecture. Your footage, your keys, cloud just computes. Open-source, community-driven.","related":[]}},{"slug":"gitfm","name":"GitFM","tagline":"Git visualization tool","description":"GitFM visualizes branches, commits, and merges as an interactive graph","github":"https://github.com/echowang1/gitfm","status":"alpha","page":{"what":"Git repository visualization tool","problem":"Text-based git log is hard to parse. Complex histories become unreadable.","whoFor":"Developers working on branched codebases","howWorks":"Parses git history into an interactive graph. Visualize branches, merges, commits. Sometimes eyes are faster than brain.","related":[]}}]}