Build on it
Extend, embed and verify the engine, from new readers and rules to the gate and the evidence habits.
These guides are for people extending Agni. Most assume you read Go.
- Adding a format reader shows how to wire a new EDA format into the neutral IR.
- Authoring a check rule follows one rule from a checklist item to a shipped rule.
- Adding a library member covers the derived relations agni ships in Datalog, when a question belongs there, and the edits that ship one.
- Extending and embedding the engine builds a private module with your own readers and house rules, depending on the public engine without forking it.
- Calling agni from another language covers the typed Python client over the CLI or a server, and what the same contract offers any other language.
- Driving an embedded viewer frames the viewer in your own page and moves it over postMessage, and gives the contract for what a link carries.
- Native verification checks a reader against the format’s own EDA tool as an oracle.
- Running the gate says what
make testallcovers, and the three ways it reads green when it is not. - Evidence is about measuring, testing, and the habits that keep a result falsifiable.