AI does the work.
Each AI worker gets one job and a clear limit.
01 Rules for AI workers
Let AI work.Stay in control.
AppLayer gives AI workers clear rules: what they can do, when a person must say yes, and when money can move. Every step is saved onchain.
TEAM / 24
JOB ACTIVE
JOB
Customer request / JOB–00241
- 01Job receivedSYSTEM · 10:42:11COMPLETE
- 02Permission checkedRULE · 17COMPLETE
- 03AI does the workAI WORKER · JOB–04COMPLETE
- 04A person must approvePERSON · CHECKPOINTWAITING
- 05Approved actionAPP · WAITINGNEXT
- 06Proof + paymentRULE · WAITINGQUEUED
LiveAppLayer EngineREADY TO TEST
BuildingAI Work RulesBEING BUILT
PrototypeRule Builder + ConsoleEARLY PREVIEW
See the testnet live ↗
02 — AI-RUN TEAMS
A team where
the rules
run too.
AI can do the work. People still set the rules.
AI workers and people do the job together. Smart contracts say who may do what, when a person must step in, and what gets saved.
See AI-run teams →Code enforces the rules.
Permissions, steps, and money follow rules no one can quietly change.
People stay in charge.
People can stop, check, or change the work when it matters.
03 — HOW A JOB MOVES
TRACE Every step, saved
From request to payment,
one clear path.
See who acted, which rule was used, what proof came back, when a person stepped in, and what happened next.
01 / REQUESTSTATE · OPEN
The job and its rules are saved.
A request becomes a clear job with saved steps, rules, and input.
- Actor
- A customer or app
- Control
- Is this job allowed?
- Result
- Job created
01 / AUTHORIZECode checks permission.
The rules say who may start, what they may do, and how much they may spend.
02 / EXECUTEAI and people do the work.
AI thinking, private tools, websites, and outside apps stay offchain.
03 / VERIFYProof finishes the job.
Signed proof moves the job forward and can release payment.
04 — THE DIFFERENCE
From voting
to doing.
Voting picks the goal. Work gets it done. AppLayer connects the vote to the work.
Typical DAOTeam using AppLayer
Votes on ideasRuns repeatable jobs
Shares wallet accessGives AI and people clear roles
Manages shared moneyConnects approved work to payment
Saves votesLinks work, proof, choices, and money
05 — WHAT YOU GET
STACK Rules to results
One product.
Three simple layers.
03
INTERFACES · PROTOTYPE
Rule Builder
+ Work Console
Set the rules, watch the work, and step in when needed.
PROTOTYPE02
CONTROL PLANE · BUILDING
AI Work Rules
Onchain rules for roles, permission, job steps, proof, approval, budgets, and payment.
BEING BUILT01
EXECUTION · TESTNET
AppLayer Engine
A blockchain that runs regular EVM apps and fast C++ programs.
LIVE ON TESTNET06 — NATIVE EXECUTION
APP/LAYER ENGINE See the code yourself
Built to run fast.
Built to remember.
Fast C++ Programs run directly inside AppLayer instead of being translated one tiny step at a time.
Programs keep their working memory, talk to each other directly, and undo the whole change if one part fails.
FAST C++ PATHBDK / C++
- 01App calls a contractWorks with familiar EVM toolsEXTERNAL
- 02Run the C++ programCompiled code runs directlyNATIVE
- 03Programs talk directlyLess translation between programsNATIVE
- 04All-or-nothing changeUndo safely if something failsSTATE
- 05Network checks + savesThe network agrees on the resultNETWORK
07 — APPLICATION PATTERNS
What you can
build with it.
Four ways AI work can follow real rules, return proof, and move money safely.
01
AI-powered back office
Let AI handle repeat jobs and send risky choices to people.
→ 02Run a protocol
Connect people, vendors, budgets, finished work, and payment.
→ 03Service networks with proof
Track proof, trust, problems, and payment across many teams.
→ 04Community-owned teams
Connect owners, votes, work, and money with clear rules.
→09 Plan a pilot
Bring us one job.
We will make its rules
run.
If AI does real work in your company or product, we will help you define the rules that keep it safe and useful.
Plan a pilot →