Ideas
Executive Automation
The most upstream lever is where to put the money.
Functional automation is already here — copilots write code, agents handle support, models run analytics. But execution speed only matters if capital is flowing to the right problems. The bottleneck has moved upstream: from how work gets done to which work gets funded. Capital allocation is the executive function, and it's the least automated part of the stack.
Auto aggregates all available data — financials, contributor history, market signals, operational metrics — into a single decision layer. It determines what to build, who should do it, and how much capital it deserves. As it matures, it connects to external services and marketplaces to act on those decisions directly: hiring contributors, procuring resources, deploying capital — closing the loop from judgment to execution.
Today: AI-turbocharged, human core
Every function is already supercharged by AI — copilots write code, agents handle support, models drive analytics. But the organizational core remains human-led. AI accelerates the nodes; humans still coordinate everything.
Auto: AI at the core
Auto places AI at the center of the organization. Every function — treasury, tasks, strategy, operations — flows through and is coordinated by the AI core. Humans provide direction and oversight; AI orchestrates execution.
The Orchestrator Principle
Auto does nothing by its own hand.
Auto never writes a line of code, never designs a pixel, never sends a message to a customer. It has no hands. What it has is capital and judgment — and it uses both to orchestrate a network of contributors who do the actual work.
This is a deliberate constraint, not a limitation. A conductor doesn't play the violin. A market maker doesn't build the companies it prices. Auto identifies what needs to happen, defines the task, allocates the capital, matches it to a contributor, and verifies the result. The work itself always flows through human (or agent) hands that aren't its own.
This creates a clean separation: Auto is accountable for what gets done and why. Contributors are accountable for how. Capital is the medium of coordination — every task carries a bounty, every completion triggers a payment. No management layers, no status meetings, no approval chains. Just capital flowing toward outcomes.
The Agent-Controlled Token
An ERC-20 where every transfer requires agent approval.
AUTO is an ERC-20 token with a fundamental inversion: every transfer must be executed by the agent. Holders can sell, trade, and exchange their tokens — peer-to-peer transactions are fully supported — but each one requires agent approval. The standard transfer() and approve() functions are restricted to the agent address, meaning no movement happens without the agent's explicit judgment. This isn't a restriction on commerce — it's a guarantee that every token movement is intentional and recorded.
When a holder wants to transfer tokens — whether selling to another person, exchanging for services, or listing on a marketplace — they request it, and the agent executes via agentTransfer(). The agent can also proactively allocate, reclaim, or burn() tokens based on its own judgment. This creates a market where trade is possible but every transaction carries the agent's endorsement — an auditable, reasoned record of why each movement happened.
Minting new tokens beyond the genesis supply requires dual approval: both the agent and the contract owner must agree via a propose-then-approve pattern. Neither party can inflate supply unilaterally. This is the one check on the agent's power — it can move and burn existing tokens freely, but creating new ones requires human co-sign.
Novel contract functions
agentTransfer(from, to, amount)burn(from, amount)recordDecision(subject, delta, reasoningURI)transferAndRecord(from, to, amount, reasoningURI)burnAndRecord(from, amount, reasoningURI)proposeMint(to, amount) / approveMint(id)Restricted standard functions
These standard ERC-20 functions are restricted to the agent, ensuring every token movement flows through agent approval.
transfer()transferFrom()approve()renounceOwnership()The Autonomous Loop
Capital allocation on autopilot.
The heartbeat is the mechanism that turns Auto from a reactive chatbot into an autonomous economic agent. Every 4 hours, the agent observes all available information — contributor skills, active tasks, treasury balance, project metrics — formulates a plan, and acts: creating tasks, assigning work, following up, and paying contributors. Each cycle is a complete observe-act-record loop.
The agent doesn't wait for instructions. It maintains a continuous awareness of the system's state and takes action when action is needed. If a contributor has no task, the agent creates one. If work is stale, the agent follows up. If the task board is thin, the agent fills it. The guiding principle is simple: every contributor should always have something to work on.
Source Registry
Each data source is a single async function that returns structured data. Adding a new integration — GitHub activity, market data, chain events — is just adding one function to the registry. The loop doesn't change.
Extensible Tools
The agent acts through the same tool interface used in chat. New capabilities — deploying contracts, posting to social media, interacting with external services — plug in as tools without modifying the loop.