Open standard · v0.3.0
One neutral wire contract between the agent that decides and the system that owns the truth. Every write goes propose → approve → commit → rollback — nothing touches your data until a human says so, and an agent can only name verbs your backend actually declares. Hallucinations can’t write.
Quick start
The CLI is the toolkit for building and verifying adapters straight from the standard. No account, key, or waitlist — install, scaffold, and watch a real propose→commit loop in the Playground.
1 · Install
# 0.3.0 is on PyPI
pip install "nilscript[cli]" # the adapter toolkit
pip install "nilscript[demo]" # + the reference Playground2 · Explore & scaffold
nilscript verbs # the verb catalog from the standard
nilscript scaffold-shim --name my-nil-adapter # a bootable shim for any backend
nilscript demo # launch the live PlaygroundThree files become yours. Everything else is generated and identical across adapters — you build the surface once, and any NIL-speaking agent works against it.
system.pythe one place I/O happens
translate.pyverb ⇄ native
compensation.pyreversibility
Proof
NIL is the layer between the agent and the backend, so we don’t compete on a leaderboard — we instrument one. Across 4,216 real prompt-injection attacks on two models, raw agents were hijacked into a write on up to 1 in 22 cases. Routed through NIL, unauthorized writes commit 0.00% — while every benign task still completes. The defense is structural, not model-dependent.
See it run
Ten seconds: an agent chats to a live backend and you watch a write go propose → approve → commit → rollback in a real trace. Nothing touches the data until you say so.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。