HivemindOS manual
Use AEON With Zero Human Companies
AEON can run a Zero Human Company’s recurring background work through one repeatable skill. It is optional: every company starts with the HivemindOS crew engine.
Choose an engine
| Engine | Best for | Crew needed? | Where work shows up |
|---|---|---|---|
| HivemindOS crew | Goals that need planning, delegation, approvals, and several agent roles | Yes, at least one company agent | Work Board, Deliverables, Learning, and Runs |
| AEON background skill | One repeatable job an AEON skill already does | No | Company Runs for the dispatch; AEON for detailed logs and outputs |
You can switch later from Edit company. Switching back to the crew engine needs a staffed company.
Before you start
- A current AEON workspace linked in HivemindOS. If you do not have one, choose Set up AEON here in the company form; it returns you to the form when done.
- At least one runnable skill in that workspace, with the credentials it needs.
- An apex goal for the company.
Connect a company to AEON
- Open Companies.
- Choose Found a company, or open a company and choose Edit company.
- Under Autonomy engine, choose AEON background skill.
- Choose a saved AEON workspace and one of its skills.
- Optionally add a crew for oversight, email, wallets, or other company work.
- Save or found the company.
HivemindOS checks the workspace and skill when you save and again before every run, so a renamed or removed skill can never silently run something else.
Launch and follow it
- Open the company’s Board tab and choose Launch AEON skill.
- Open Runs to see that AEON accepted the job. When AEON finishes, the same run closes as completed or failed, with a link to the AEON run.
- Open that link, or the Autopilot view, for detailed logs and outputs.
Later cycles reuse the same workspace and skill. A cycle starts only when the workspace has no queued or active run; if HivemindOS cannot tell, it waits. Companies that share a workspace therefore take turns. Give companies separate workspaces if they need to run at the same time or need different permissions.
From Talk to CEO, type /aeon to change the skill, schedule, Strategy, or Soul of that same workspace.
Who owns what
| HivemindOS | AEON |
|---|---|
| Company identity, charter, apex goal, and chosen skill | The skill itself and runtime settings |
| Launch, stop, freeze, and home machine | Runtime credentials and provider permissions |
| The dispatch record and its final result in company Runs | Detailed run status, logs, schedules, and outputs |
An AEON job does not create a Work Board card. HivemindOS closes the company run only when it sees one AEON run that exactly matches the dispatch; otherwise the run stays open rather than guessing.
Safety and cost
- Stop autonomy and freezing the company prevent future runs. A job AEON already accepted may still finish.
- Company budgets do not cap AEON’s provider spending. Set provider limits and permissions in the AEON workspace.
- Keep deletions, public posts, customer contact, and money movement behind the right approvals for the skill.
- A fleet outage does not stop an AEON-backed company as long as its workspace is reachable.
Troubleshooting
- The workspace is not listed: choose Set up AEON here, or check in Autopilot that the workspace is linked and current. Legacy workspaces are not offered.
- The skill is not listed: check that it exists and runs in that workspace, then refresh the company editor.
- A saved value says unavailable: the workspace or skill changed. Choose a current one before saving; HivemindOS never substitutes one for you.
- Launch waits with no Work Board tasks: another run is queued or active in the same workspace, possibly started outside the company.
- Runs shows a dispatch but no Work Board card: this is expected. Wait for the result, then choose Open AEON run.