User guide — overview
Audience: people writing .nibli knowledge bases, using the REPL or playground, or embedding the engine.
| Page | What it covers |
|---|---|
| What Nibli guarantees | Four-valued verdicts, closed world/domain, trusted compute |
| Quickstart | Nix dev shell, just run, first claims |
| nibli KR cookbook | Surface syntax stubs + link to the full spec |
| Playground | Hosted triad UI and Formalize |
| GDPR walkthrough | A worked compliance KB — engine-checked verdicts and the consent-withdrawal flip |
| Drug-interactions walkthrough | A worked safety KB — the three-step mechanism and its negative controls |
| Belief revision | :retract, retract ≡ never-asserted, and edit-and-re-query in the playground |
| Authorization | Builtin policy, can / fields / explain, Rust + Python adapters |
Deeper sources (repo root)
| Topic | Where |
|---|---|
| Product overview | README.md |
| Formal contracts | GUARANTEES.md |
| Language (normative) | NIBLI_KR.md |
| Example corpora | gdpr.nibli, drug-interactions.nibli, readme.nibli |
| Host / WASM ship path | DEPLOY.md |
Query model: state a claim to check for entailment (e.g. dog(Adam).), not an interrogative. The playground’s decorative ? is not sent to the engine.
The developer guide covers the crate map, the IR, the WASM/host/compute path, the CI gates, and the WIT surface; published crate APIs are in the API index. Remaining docs work is tracked in TODO.md.