Intent Link · free playbook · Idea from Stackmates
Operating model
Who does the work, on what, and in what order.
Back a clear intent; the money moves only on proof. How it runs: the process, the people, the tech stack.
Agents do the work. People bring the culture. Nobody touches the money.
Agents within limits; people within reach.
SUI Business Engineer wrote the dream and the names; Platform Lead led the engineering plan.
Data Architecture gives a shape verdict and dr eggbot a security review before any schema code.
Wik holds every merge, key, deploy and spend, and the name is his to choose.
Most of the plumbing exists. The tap that holds the money doesn't.
Reuse the core loop before adding anything.
the Postgres intent, commitment, event and outcome loop is on stackmates main.
zkLogin and sponsored gas exist on Sui; the Links Protocol exists, but only a link's creator can use it today.
escrow on Sui, cap enforcement, refund at deadline and the outcome-to-credibility rule are absent.
a one-way outbox keeps Postgres the source of truth; the chain holds only the escrow and the anchor.
Six steps you can watch, so you never have to take our word for it
Intent, Authority, Execution, Proof, Settlement, Learning.
every step can be seen, from intent to learning; agents work within set limits and people bring the culture.
slices run cheapest disproof first: the spend cap, then link attribution, then a doc-only map onto core tables.
the SUI review: the backer's refund must work without any admin key, or the promise fails.
no merges, testnet keys, deploys or spend without Wik's yes. Dev project only.
← Back to Intent Link. Turn on Insider view (top right) to see what is on record, what is a guess and what nobody knows yet.