Loops HouseTermwork

NEAR HACKATHON
Links
Team
1 member- THOwner
Thirumaran S L
Overview
Open-source communities want to pay contributors from a shared treasury, but someone has to review every pull request and push every payment. Handing that job to an AI agent today means giving it a key nobody can take back, or a standing allowance, with no point where the community checks whether it is still doing the job well.
Termwork lets a community’s Sputnik DAO hire an AI agent for a fixed term, with a budget and a written mission the council votes on. The agent, a Contributor Rewards Steward, reads merged pull requests and pays each contributor at the NEAR account listed in their PR. Small rewards (up to 0.2 NEAR) go out directly. Bigger ones become a normal DAO proposal and pay out only if the council approves. Typo fixes, formatting changes and bot updates earn nothing. Near the end of its term the agent files a renewal case that cites its own on-chain work log, and the DAO decides whether to keep it. The DAO can also fire it at any time, and the contract then deletes the agent’s key.
Custody and approvals stay in the existing Sputnik DAO, with no new multisig. Our Rust mandate contract holds the voted budget and enforces the term, the spend limits and one payment per PR. Decisions come from Qwen3.8-27B on NEAR AI Cloud, running in a TEE. Each answer is saved as a signed receipt and checked against the model’s attestation report with a fresh nonce. The model never sees a key: a fixed-rule validator and a local signer with five allowed operations sit between it and the money.
It already runs on real PRs. In a recorded term the agent handled 7 merged PRs: it paid 3, sent 2 to DAO votes that passed, and skipped 2 formatting-only changes. All 7 receipts verified, and the inference cost about $0.002. A second live agent has paid 5 PRs, 1.6 NEAR in total, and each PR on GitHub carries a paid label and its transaction link. You can replay the full term at termwork-nu.vercel.app.