Bevia Capture Protocol

The open specification for feeding evidence into a Bevia engine. If you can write a JSON file, you can build a Bevia sensor.

• SPEC.md — the protocol: capture body, drop-file convention, location object, behavioral guarantees. Versioned, additive-only.
• schema/ — JSON Schemas for validation.
• examples/ — real capture files: a chat session, a robot maintenance session, a captured note.
• tools/ — zero-dependency conformance tools: check-capture.mjs validates your capture bodies against the spec, and fake-engine.mjs is a local test double (HTTP + drop-file watcher) that answers honestly — what landed, what deduped, why something was rejected — so you can build a sensor without an engine.
• SENSOR-CHECKLIST.md — the five honesty rules every sensor should meet, with a troubleshooting table for "my data isn't landing."
• reference/ — reference sensor implementations.

The one-paragraph version

Bevia turns observed work — conversations, sessions, notes — into a navigable, queryable memory. This repo specifies the doors: the shape of a capture, how a file in a watched folder becomes evidence (*.bevia-capture.json — the file's content is the request body), and how a sensor stamps where knowledge happened. Everything here is open and free to implement, forever.

What this repo is not: the engine. How captures become understanding — the compilation, the cartography, the narration — is proprietary and is the product. Implementing this spec requires no license; running an engine does. Open doors, paid brain.

Quick start

1. Write a capture file (copy one from examples/).
2. Name it anything.bevia-capture.json.
3. Put it in a folder your Bevia app watches.

That's the whole integration. For a continuous sensor, see the reference implementations.

License

The spec, schemas, and examples in this repository are MIT-licensed. Bevia engines (Bevia Local, Bevia Cloud) are separate, proprietary products and are not covered by this license.