Loops HouseCaesura

NEAR HACKATHON
Links
Team
1 member- MIOwner
Mitchell Travers
Overview
Cæsura || keys for agents that cannot act alone.
An AI agent holding a wallet key is one poisoned web page, one planted memory or one quoted-back task away from draining it. Policy engines in enclaves and SaaS vaults re-run the agent's own judgement and publish no record of what was proposed, what was refused, or why.
Caesura is keys for agents that cannot act alone. A small NEAR contract, the gate, holds the only keys: two function-call access keys on a locked sub-account, each scoped to one method. One AI seat proposes a spend; a second seat, held apart and never shown the first seat's prompt or tool results, checks it; the gate executes only when both agree and its public policy (caps, receivers, cooldown, pause) passes. Both seats run as private inference on NEAR AI Cloud, each answer signed in the TEE over its exact bytes with an attestation bound to the signer. Every round, executed or refused, is minted as a content-addressed evidence bundle whose root the gate commits on chain; an offline verifier re-derives every hash, checks the enclave receipts and matches the root, in Node and again in Python.
During the hackathon two testnet gates ran the whole corpus: poisoned pages, planted memories, over-cap tasks, salami slicing, a mid-round policy change, key-scope abuse, and the gap study, which varies what crosses to the second seat (policy only up to the full prompt) and shows that the separation, not model diversity, does the holding. Seat keys can sign twice, ed25519 beside ML-DSA-65 or SLH-DSA, with a key-transfer ceremony countersigned by the keys it leaves. An on-chain registry lets anyone register a gate they own; the board at caesura.mages.city reads the registry and every gate live from the chain.
NEAR makes it native: scoped function-call keys and locked sub-accounts are the sandbox, NEAR AI Cloud is the private seat, and contract state is both the public policy and the ledger of roots.
--privacymage