What it does
Cockroach Kernel is a deterministic developer-work recovery prototype. When an agent workspace disappears, it evaluates surviving, hash-bound representations and creates a fresh successor only when the evidence is valid. Tampered, conflicting, malformed, unsupported, replayed, or unsafe inputs fail closed.
How it uses CockroachDB and AWS
CockroachDB provides the persistent memory layer: transactional task, trajectory, receipt, checkpoint, and vector records, with Distributed Vector Indexing for receipt-linked retrieval. The Managed MCP Server is used only for bounded read-only receipt inspection. AWS Lambda runs a bounded advisory worker. The local deterministic verifier remains the sole authority for promotion, refusal, and invalid results.
What we learned
The important boundary is proof, not prediction: the system recovers only what survives in an allowed representation and never invents missing bytes. The evidence is bounded to synthetic/disposable workflows and one region; it does not claim arbitrary undelete, production-scale durability, multi-region resilience, or MCP write/DDL authority.
Try it
The clean-clone commands and public demo routes are documented in the README.
Built With
- aws-lambda
- cockroachdb
- distributed-vector-indexing
- managed-mcp-server
- python
Log in or sign up for Devpost to join the conversation.