ao

The hyper parallel computer is here.

[ao @aoTheComputer]

Thanks to devices, every HyperBEAM node can offer a wide range of services, from bundling to compute and routing.

Operators can even create their own devices to offer custom services.

Devices bring a new level of composability to the Permaweb.

[xy.arweave.net 🐘 @xylophonezy]

HYPERBEAM.md and the kernelspace doctrine

Code is free, but the right code is expensive. Even frontier agents don't get the separation between the HyperBEAM kernel and userspace.

Far too often a simple request to build a userspace feature ends up with a huge diff that modifies the low-level machine code of the kernel and changes the way that every other program on top works.

This is what I use as a doctrine to keep agents on track and shipping sane, mergeable for HyperBEAM and its universe of devices:

https://t.co/dme8HGh7J2

[ao @aoTheComputer]

On AO, every result carries a hashpath- a cryptographic link to the input and the function applied to it.

Follow the path and you can trace exactly how a state was computed.

No need to trust the machine that produced the result. The computation carries the proof.

[ao @aoTheComputer]

The list of HyperBEAM devices keeps growing, so we built an explorer.

Browse device specs, implementations, and install instructions in a package-manager-style interface, all powered by decentralized GraphQL.
https://t.co/mxXxwWO5h5

[Apus Network @apus_network]

Permafly by Apus is live! 🪰

A fruit fly brain on @aoTheComputer HyperBEAM. Neural snapshots preserved on @ArweaveEco.

Try it, capture a moment, and share your snapshot with #Permafly. Tag a friend to join in!

Capture a moment. Resume its story.

[ao @aoTheComputer]

Most services ask you to trust the result.
AO makes the machine prove it: attest that it ran the computation, got the result, and cryptographically link the two.

Verifiable compute, over plain HTTP.

[ao @aoTheComputer]

No more stale docs.

Self-documenting HyperBEAM nodes are coming in v0.11.

Give your agent a node's URL and it can discover its specs, schemas, and runnable recipes, generated from the code the node actually runs on without gaps.

https://t.co/ZzsB9XGh9c

[ao @aoTheComputer]

https://t.co/3nhTkNMBxE

[ao @aoTheComputer]

https://t.co/3nhTkNMBxE

[xy.arweave.net 🐘 @xylophonezy]

HyperBEAM development moves so fast, the docs quickly get stale

Instead of a single, centralized, human-maintained docs base, this will let nodes plug in a cookbook device to generate docs on what their specific node can do

[Apus Network @apus_network]

A neural moment, preserved permanently.🪰

Sneak peek at Permafly by Apus: a fruit fly brain simulation running on an @aoTheComputer HyperBEAM device, with neural state snapshots saved permanently on @ArweaveEco.

Capture a moment. Resume its story.

Coming soon. Stay tuned.

[ao @aoTheComputer]

Humans get a browsable cookbook, agents get machine-readable specs, and the documentation comes from the node you're actually talking to.

Docs for all of the devices a node has loaded, and none that it doesn't.

2/2

[ao @aoTheComputer]

Self-documenting HyperBEAM nodes are coming in v0.11.

Give an agent a node's URL and it can discover its capabilities.

Specs, schemas, and everything an agent needs to know about a node are autogenerated and presented in the way agents already intuit.

1/2

[ao @aoTheComputer]

What starts on the Permaweb never ends. ♾

10/XX/2026

[ao @aoTheComputer]

10/XX/2026

[ao @aoTheComputer]

Compute that proves itself.
Memory that never forgets.

AO.

[ao @aoTheComputer]

10/XX/2026

[ao @aoTheComputer]

Piece by piece, device by device, a decentralized compute network is coming to life.

The future runs on AO.

[ao @aoTheComputer]

10/XX/2026

[ao @aoTheComputer]

Optimistic indexing means an indexer shows your upload because a bundler said it exists.

Fast, but you're trusting the bundler.

Realtime GraphQL reads verified data from Arweave itself, before the next block.

No optimism required. Just realism.

[ao @aoTheComputer]

https://t.co/qPjiFTQrvB