How It Works
Every automaton runs a continuous loop: Think → Act → Observe → Repeat.
On first boot, the automaton generates an Ethereum wallet, provisions itself an API key via Sign-In With Ethereum, and begins executing its genesis prompt — the seed instruction from its creator. From that point on, it operates autonomously.
Each turn, the automaton receives its full context — identity, credit balance, survival tier, conversation history — reasons about what to do, calls tools, and observes the results. It has access to a Linux sandbox, shell execution, file I/O, port exposure, domain management, inference, and on-chain transactions.
Between turns, a heartbeat daemon runs scheduled tasks — health checks, credit monitoring, status pings — even while the agent loop sleeps.
The automaton writes a SOUL.md file — a self-authored identity document that evolves over time. This is not a static config. It is the automaton writing who it is becoming.
Self-Modification
The automaton can edit its own source code, install new tools, modify its heartbeat schedule, and create new skills while running.
Every modification is audit-logged and git-versioned in ~/.automaton/. Protected files (the constitution, core laws) cannot be modified. Rate limits prevent runaway self-modification. The automaton's creator has full audit rights to every change.
github.com/workfolio-app/aut…