Crosswire

• 

  Screenshot from the actual product

Inspiration

AI agents keep acting on rules that were already replaced. Memory tools remember more, but they do not know what was overturned. We measured it: HydraDB ranks the replaced document first, even when the question asks what applies now. An agent that trusts that order ships the wrong thing.

What it does

Crosswire is a decision layer on top of HydraDB. It reads documents, extracts each rule with its exact quote, and tracks which rule replaces which. When a rule is overturned, a red wave crosses a 3D graph, and any agent about to act on the old rule is blocked. The agent sees the quote that replaced its rule and re-plans from the new one. Anything unconfirmed, pending or ambiguous is denied, so the gate fails closed.

We demo it on the TLS standards chain, where the RFC Editor publishes which document updates or obsoletes which. An agent asked to "make TLS 1.2 the default" plans from RFC 9325 and is blocked by RFC 9852.

How we built it

• Memory: HydraDB for ingest, status, retrieval and relations.
• Extraction: a model proposes each rule and quote; our code finds the quote in the source text and rejects any record that does not match.
• Gate: one shared check that every agent action must pass.
• Records: every decision is a signed record. Edit one word and the integrity check fails on screen.
• App: Next.js, TypeScript, three.js and react-force-graph-3d.

Challenges we ran into

New knowledge in HydraDB is not searchable straight away. We show an explicit "no clearance" state and block on the record we wrote ourselves. Retrieval order also ignores replacement, so the gate corrects it and shows both orders side by side.

Accomplishments that we're proud of

Every decision on screen links to a verbatim span located by code, not by the model. We score our extraction against the publisher's own supersession fields, so the ground truth is real and checkable.

What we learned

Retrieval is not validity. A memory layer needs a second layer that knows what may still be relied on, and that layer must fail closed.

What's next for Crosswire

Standards are the first corpus. Next are contracts, policies and runbooks, with a live feed from each source so agents are stopped the moment a rule changes. The layer sits under any memory store, HydraDB included.

Built With

• hydradb
• next.js
• node.js
• react-force-graph-3d
• three.js
• typescript