Frontend
Matoi: Selective Revalidation of Consequence Evidence for Agent Authorization
arXiv cs.CR0 views
arXiv:2610.21394v1 Announce Type: new Abstract: Matoi separates reusable consequence evidence from current execution authority and durable occurrence history. Its finite query-aware contract covers branches, ordered collections and negative lookups. A consumer reuses only its own checked evidence whose observations remain valid; signed requests, live grants, quota and uncertain outcomes remain separate obligations. Conditional correctness arguments distinguish locally serialized claims from nontransactional remote effects. Two studies strengthen cost attribution and domain evaluation. A 1,440-cell matched-wire study repeats 144 authored inputs. With compact input bytes identical, reuse reduces complete lifecycle cost by 3.49 percent in JS and 1.79 percent in Python. Combined representation/reuse reductions against full proof are 10.87 and 16.53 percent; five of twelve family intervals for the matched comparison cross one in each language. A prospectively frozen AgentDojo Banking mapping covers 5/16 user plans and 7/9 attack plans. Both governed strategies preserve five exact benign transfers and refuse 35 reused attack-plan/policy crosses. Pre-satisfied utility predicates are reported separately from completed work. These are original scripted synthetic tools, not autonomous agents or a real bank. Earlier studies retain cheaper protected-cache alternatives, policy-compatible phishing, provider duplication and post-claim revocation. Separate JS/Python consumers establish finite-profile interoperability within the same project; durable recovery rechecks evidence and retains uncertain reservations. The results support a bounded, auditable reuse and execution contract, not a new general incremental algorithm, arbitrary-tool closure, atomic third-party commitment or production superiority.
Source:https://arxiv.org/abs/2610.21394PreviousEvaluating and Improving Static Application Security Testing Tools for RustNextBenchmarking Post-Quantum Key Encapsulation in S3-Compatible Object Storage under Client Concurrency
Related posts
What a forward deployed AI engineer actually does
0dev.to
How to Get Your First Freelance Client When You Have No Experience
0dev.to
Best shadcn registries for ready-made blocks in 2026
0dev.to
How we score an election forecast (and what the score does not measure)
0dev.to
Handling Failures as Values in Agent-Generated Code
0dev.to
My Favourite Laptop
0Hacker News