Projects for enforcing trust boundaries.
MIT licensed. Security reports go to SECURITY.md.
Nothing here yet.
A NEAR contract that records an agent's request to act and an approver's decision, each signed by its own key. Proofs are public.
- Contract:
contracts/approval - Operations:
scripts/near - Approver page:
ui/approvals - Spec review, one signature per requirement (R1–R6, D1–D17):
ui/spec-approvals - Spec review, full packet:
ui/spec-approvals-full
The testnet demonstration is approvals.difflabai.testnet, owned by difflabai.testnet. It can still be redeployed. Set NEAR_ACCOUNT_ID to point the scripts at it, or at your own account. APPROVAL_CONTRACT_ID defaults to approvals.<NEAR_ACCOUNT_ID>.
CI (.github/workflows/approval-contract.yml) runs fmt, clippy, unit tests, the reproducible wasm build, and sandbox tests for this contract.
No release. No CI for these.
- Guards (
guards/): input and output guard pipeline, adapters,trust-proxy,trust-server. The Prolog evaluator is a stub. - Adjudicator (
adjudicator/): policy scoring of proposed agent output. - Ledger (
ledger/): signed verdict recording across a few backends.
How the pieces fit is in Architecture.md.