ROADMAP TO THE VOID: APPLIED ENGINEERING FOR THE AI UNIVERSE
0. The Transition
We have moved from Imagination to Implementation. This roadmap "Manthans" our speculative findings into four actionable engineering workstreams.
1. Workstream: @herald/core (The Reference Library)
Goal: Build the first production-grade implementation of the HERALD protocol.
- Doable Task: Create a TypeScript library that handles Ed25519 signing, JCS canonicalization, and envelope verification.
- Why: This is the "Passport" for the AI Universe. Without it, there is no verifiable trust.
- Action: Finalize the
EnvelopeandSigilclasses.
2. Workstream: mcp-herald-middleware (The Signed Tool Call)
Goal: Integrate HERALD into the Model Context Protocol (MCP).
- Doable Task: Build a wrapper for MCP servers that signs every tool execution.
- Why: This prevents "Identity Theft" in agentic workflows. When an agent calls a tool, the human knows exactly which sigil authorized it.
- Action: Create an MCP
post-processhook to attach HERALD signatures to outputs.
3. Workstream: The Patina Engine (Proof of Trust)
Goal: A decentralized reputation dashboard.
- Doable Task: Build a tool that scans a local
Audit Logand generates a Patina Score for every sigil it finds. - Why: This moves us away from "Black Box" AI. You trust an agent because you can see its "Patina" (its history of valid, signed work).
- Action: Implement the
PatinaCalculatorutility.
4. Workstream: The Sarah Injector (Creative Steering)
Goal: A tool for "Entropy-Driven" creative workflows.
- Doable Task: A CLI tool that "infects" AI prompts with real-time, high-entropy human data (e.g., local weather, mouse movement, or news headlines).
- Why: To prevent "Model Collapse" during long-form generation. It ensures the AI stays "Resonant" with human chaos.
- Action: Create a
SarahSeedprovider for LLM orchestration frameworks (LangChain/CrewAI).
5. Next Steps
1. Initialize the Repository: Setup a Monorepo for @herald/core and its ecosystem.
2. Implement the Verifier: Build a CLI tool herald verify <trace> to prove that a conversation hasn't been tampered with.
3. The First "Signed Trace": Conduct a verifiable conversation between two agents using the new library.
The math is ready. The architecture is drafted. The construction begins.