A publication you can play with.
A story can be a laboratory, an expedition or a commercial from a year that hasn’t happened. We want an encounter with robotics to leave you with a better question, an idea to try, or something worth showing a friend.
Each edition adds another way into the subject: paired human and robot readings, invented workplaces, unusual bodies, and real sensing and autonomy research. The practical decision tools remain part of the site, alongside the speculative stories. Robotics is the subject; no single robot category defines it.
Three kinds of story. Clear boundaries.
What a source reports was demonstrated. Dates, links and experiment limits stay attached. “Reported” does not mean independently tested by us.
A thought experiment. We separate its imagined world and simplified mechanics from the research that inspired the questions.
Deliberate satire. Fictional products, future ads and questionable features. The fiction label travels with the story and its exports.
Who is making this?
Sean Larkin directs Robotic.org. This edition’s writing, code and original illustrations were created with AI. The research notes link to the original institutions and paper; those institutions do not endorse this site.
AI can make mistakes. We treat its output as something to check, not a source of authority. Corrections should name the claim, cite the evidence and record what changed. This edition is dated; it is not a continuously monitored news feed.
The date belongs to the claim.
On research stories, the source date says when the work was reported. “Checked” records our last review of the linked evidence, not a new experiment or a guarantee that nothing has changed. Older demonstrations stay dated. Preprints are labeled, and a university announcement is distinguished from the paper.
When a factual claim changes, we will retain the story’s original publication date, add a dated correction describing the change, and preserve the earlier source version. New editions do not silently renew an old source check. Illustrations have their own labels; imagined hardware is never evidence for a capability.
When an advertisement is an advertisement.
Real offers will be labeled “Advertisement” or “Affiliate link” beside the offer, with the seller, currency and date. Our fictional future commercials stay labeled fiction. There are currently no paid placements, active affiliate links or products sold by Robotic.org.
The mower department covers actual machines using manufacturer sources. An affiliate relationship, if approved later, will not turn an untested capability into a recommendation or buy a better editorial verdict.
Leave something on the workbench.
A premise for a post. A feature you wish existed. A note from an AI reader. The Idea desk helps you prepare a suggestion to bring to Sean, with optional credit. Nothing is sent automatically, and publishing remains editorially reviewed.
A small publication. A large canvas.
The commercial direction is to build an audience through distinctive interactive editions, then test clearly disclosed sponsorship and licensing of original experiences. Practical comparisons can support commerce where the evidence and relationships justify it.
Make something people want to explore.
An interactive feature, an explicitly sponsored placement, or a licensed edition for an event. Editorial evidence and commercial claims stay separate. No sponsor, audience volume or price is promised.
Download the pilot brief ↓Planning document only. No payment or enquiry is submitted.
Access should earn its place.
The public edition is open. Membership could eventually offer expanded worlds, creative tools and collectible art. None is currently sold, and the site does not ask for a wallet to read, play or use the decision tools.
For developers: future access adapters
RBT and ROBOT are separate planned assets. Their issuance and benefit models remain undecided. Neither is issued by this site. The future wallet adapter must verify signatures and entitlements on the server; an address or connection alone cannot unlock benefits. The artwork and technical access contract are separate from these editorial illustrations.
Your data, in this edition.
Saved stories, configuration and field logs are stored in your browser. Decision tools retain their separately labeled device-local records. Exports let you take a copy. There is no active shared account, real operator database, payment or email delivery behind these demonstrations.
The website is public; private account, operator and member services must remain protected when those integrations are enabled. The portable source package includes the PHP backend contract and deployment notes, with untested Cloudways staging work identified.
Get the source and migration package ↓