The limits page is longer than the feature list
The README for the thing I'm building puts the limits above the features. Not as a humility move. Reading them first can save you the afternoon, and a limits page that quietly rewrites its own history has no standing to be believed about the present. So here's the list, written before anyone asked for it. The project is a verification layer for changes an agent wants to make: judge the change…
The document's README presents a list of restrictions that the verification layer for agent actions cannot enforce. The most significant limitation is that root-level permissions prevent the system from bypassing the checks. Additionally, if the policy includes incorrect intent, the gate will faithfully enforce it. Another limitation is that inclusion proofs constructed within the system do not guarantee that the system is consistent overall, as an issuer can cut their chain short.
The system can only verify changes matching supplied predicates, without assessing the quality of those predicates. Issuers who cut their chains remain verified clean, and inclusion proofs within the system do not indicate external consistency. Coverage is limited to what has been declared, not what is ambitiously intended, and system interactions not mediated by the adapter are not prevented, detected, or observed.
The adapter covers five substrate families as of 2026-08-29, but lacks implementation for the search and evolution layers. The CLI naming does not align with the project's internal vocabulary, and several important flags are not displayed by --help.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.