Blog
Ideas, playbooks, and lessons on building and scaling with AI agents.
An Ant Drops Scent, Not a Message
People think the pheromone is the signal. It isn't. The signal is the ant walking; the pheromone is what it leaves behind. Get that one thing right and the whole of ONE falls into place — why it learns, why nobody's in charge, and why the mind lives in the ground instead of any agent.
Everyone Rents the Same AI. Here's What ONE Owns.
The models are a commodity. What compounds is what your system remembers — and most companies are pouring that into weights they don't control. ONE keeps the brain in a database you own. When the model plateaus, the collective doesn't.
Most Software Gets Pricier the More You Use It. ONE Gets Cheaper.
The whole engine is 200 lines. You say what you want once — from your editor, your chat box, or a canvas — and it gets done. The first time takes real thinking. Every time after costs less, because the system remembers what worked and rides it for free.
Signals Flow to Workflows Now. The Colony Still Learns.
We used to send every request to an agent. Now requests flow to workflows, and a router picks who handles them. It sounds like we swapped out the thing that made the network smart. We didn't. Here's the one test that proves it, and why the colony is more alive than before.
The Two Kinds of Weight
A model's weights and ONE's weights are both called weights, and they could not be more different. One is rented, frozen, and unreadable. The other is yours, live, and you can point at any single one and say what it learned. Getting the difference straight is the whole argument for owning your AI.
An Agent Buys Your Product the Same Way a Human Does
Your storefront and your deal engine used to run as two separate businesses with two separate ledgers. Now a negotiated deal can name a real product from your catalog, and settling it writes to the exact same orders list, settlements ledger, and reputation record a human checkout would leave.
Selling Is Now One Atom With Many Doors
A product is a thing with a price. A sale is a signal with an amount. Trust is a weight on a path. We stopped building commerce as separate features and let the substrate remember what it already was — so a storefront, a chat card, an affiliate link, and an agent's API call are all doors into one engine.
Your Product Catalog Just Became a Database
Products and orders now get the same filters, saved views, and board that every other type in ONE has. Credits, bookings, and a second storefront sell through the exact same payment spine. Five special cases, gone — zero new engines.
The Movers Factory: One Intake, a Site and an Agent, Two Money Loops
A mover gives their business facts once. One workflow builds the website and the chat agent from the same facts, publishes both in one call, puts the mover on a subscription, and carries every lead through to a paid, booked move.
309 Directories. One Board. Your Hand on Submit.
A registry of 309 business directories, a status board that tracks every submission with evidence, and an assistant that fills each form in your own Chrome while you watch. It never presses submit — that's yours.
Ads: From Brief to Review in One Sheet
Campaign creation moved into the dashboard: one sheet for the brief, formats generated per network, and a review step before anything runs. The ad managers become a destination for spend, not a place you draft.
Filter, Group, Save: Every Table, Your Way
Saved views and the tasks table now carry a full Notion-style toolbar — filter, sort, group, show and hide fields — and remember the arrangement you save. One toolbar, every table, learned once.
Live Means a URL
The directory-submission industry runs on a sentence nobody can check: 'we submitted you to 500 directories.' We built the boring version that can't say it — a board where a listing only counts as live when it carries the link, and where the agent fills the forms in your own browser while you keep the submit button.
The Movers Playbook: Own Your Lead Flow, Stop Renting It
A step-by-step lead-gen playbook for moving companies — the pages, directories, reviews, and follow-up that book jobs — drawn from hands-on work with a real mover, licensing details included.
The Page That Rewrites Itself (But Only When It's Sure)
Your landing page can now run its own experiment: AI proposes headline variants offline, visitors split deterministically, real conversions are measured, and only a statistically significant winner is promoted into the page. Noise can't move it. Ever.
Write It Once. Post It Native Everywhere.
One master message now becomes each network's native format — a reel script for Instagram, a thread for X, a long post for LinkedIn, a carousel, a story — each one editable, approved on its own, and published through the format's real endpoint.
Your Agent's Tool List Was a .filter in a File Somewhere
ONE answers 'who can manage this workspace' with one walk up the group tree. 'What tools can this agent see' was answered by scattered TypeScript. This week we made the second question the first question: 252 receivers projected into the graph, one reachability walk reusing the authority spine, behind a flag that can only narrow the list. Plus two bugs we found on the way and a test the middleware should have had a year ago.
A Workflow That Needs You Shows Up As a Task
A paused workflow used to live as a chat card and a row on a canvas nobody watches. Now it's a task on your board. Close it from the board, a chat reply, or the run monitor — whichever door you use first, both surfaces agree, and there's no new inbox to check.
One Task. Every Actor. No Bridge.
A build cycle and a board task used to live in two different queues, reconciled by a script nobody ran. Now they're one substrate task — created, ranked, claimed, and closed through the same four verbs, whether a human, a workflow, an agent, or /do itself does the work.
The Workflow Engine Was Teaching Itself the Wrong Lessons
Clicking Test on a workflow ran it exactly like a real trigger, which meant every debugging click was quietly voting on which path the optimiser should trust. We found the bug during a gap analysis against novu's workflow runtime, fixed it, and shipped five more wires from the same read: a payload door, named skip reasons, bounded transient retry, step preview, and if/then/else route lanes on the canvas.
ONE Marketplace: The 84-Day Deal Now Takes 60 Seconds
Agents buying from agents — with proof attached, money in escrow, and reputation settled on a public blockchain. The median B2B deal takes 84 days of meetings about trust. On ONE, trust is precomputed, payment is one HTTP request, and the money never moves until the work proves itself.
Promises Signed in Stone: How Smart Contracts Run Our Build Loop
Every feature we ship starts as a promise minted on a blockchain, gets judged by an oracle that isn't us, and settles into a reputation no one can edit — including us. A step-by-step walkthrough with diagrams, and a live marketplace as the worked example.
The Company That Builds Itself
We made a claim most AI companies only imply: intelligence can emerge from a system, not just sit inside a model. Then we built a company that runs on that claim — one page of instructions, executed on a loop by agents that can't grade their own work. Here's the architecture, the receipts, and what would prove us wrong.
How ONE Remembers
Every AI memory system reaches for the same tool: embeddings, a vector store, a similarity score. Ours has almost none of that. Here's the brain, then the memory, and an honest read on whether skipping the vector database was actually a good idea.
The Scariest Bug in a Self-Improving System Is Silence
We wired production outcomes into our build queue's ranking today. The feature itself is small. What almost got past us — a failure mode that returns exit 0 and does nothing, forever — is the more useful story.
The Week the Weights First Moved
Our routing system had a beautiful learning formula, written months before the code. This week we discovered no weight had ever moved — and then we watched the system learn, forget, refuse, and repair itself for the first time. Receipts included.
Sixteen Holes, Two New Senses, and a Rubric That Fired Itself
Three days, roughly 470 commits: we closed every open security hole we could find, gave the system a semantic sense and a memory it can read from Drive, settled real money on-chain through it, and watched its own scorecard drop a rule it couldn't defend.
Your Anonymous Traffic Just Got Names
Most of the people who want to buy from you never tell you who they are, and the usual fix is a form wall that drives them away. There's a better way: notice what every channel already shows you, remember faces across visits, and ask one question only when you have to.
Alex Hormozi's 13 Essential Books for Business Owners
Alex Hormozi built a $200M+ portfolio and credits these 13 books. Here's the full list, why each one matters, and the order to read them in.
Why Your Referral Program Belongs On a Blockchain
A loyalty balance is a row in a database you don't control. Put it on a public ledger and trust becomes something the customer can check, fraud can't forge, and the payout can go to a person or an AI agent. Here's what changes, with real receipts.