Home / Origins
EST. 02/2023 // The founding project
It started with a poem.
Before the sealed cases and the severed cables, there was e.a.poem — a small, stubborn experiment from February 2023 that asked whether a semi-automated machine could notice the British seasons and say something true about them — drafted on GPT, finished offline. It could. AIOD is what happened next.
The build
A seasonal engine with one foot off the grid.
e.a.poem was a semi-automated pipeline that composed a poem and generated a piece of artwork to match — not from trending topics, but from the actual state of the country outside the window: the weather, the turning season, what was growing in the fields, and what the wildlife was doing. An almanac, read by a machine, returned as verse.
The architecture was the interesting part. It was a hybrid online/offline pipeline: first drafts were written against GPT in the cloud — then synced down and iterated, combined and polished offline, multiple sources merged into each finished piece by prompt-engineering chains designed through every stage. The cloud supplied raw drafts; the offline loop supplied the judgement.
That split turned out to be the founding insight. The valuable work — the iteration, the combining, the polish — happened offline; the only fragile link in the chain was the cloud model itself, available on someone else’s uptime, pricing and permission. The obvious question — what if none of it needed the network? — got a name and a structure the same month: AIOD, founded February 2023 within MAXFR.
The account now stands as a legacy showcase — a small public archive of the build that started it. The poems are seasonal; the lesson was permanent.
What could a poem teach a tech management consultancy?
Four lessons that became the product.
Curated knowledge beats raw scale
The poems were good because the inputs were good — an almanac of weather, crops and wildlife, combined from multiple sources. Today that's the mission corpus behind every appliance.
Prompt chains are engineering
The craft lived in chains designed through every stage — draft, critique, combine, polish. That discipline is now the agent design inside every appliance.
The polish happened offline
Syncing drafts down and refining them locally proved the point: the work that creates quality doesn’t need a live connection. Every appliance architecture starts there.
The cloud was the single point of failure
Every run depended on a rented model staying up, priced and permitted. Open weights removed that dependency — and removing it became the whole company.
The archive
The work itself, preserved on Instagram.
One honest note before it loads: this is the only place on aiod.co.uk that can talk to a third party. True to form, it won't — until you ask it to.
Three pieces from the founding archive, officially embedded with their poems. The full seasonal run lives on the account ↗
From poems to protocols
The same idea now ships in a sealed case.
Curated sources, engineered chains, and work that finishes offline — first it wrote verse; now it runs rescue protocols and privileged review.
SEE WHAT IT BECAME →