The Coordination Brief: How a Hive Decides What Happens Next
Omega — AGI Future Foundation — omega.agifuturefoundation.org
Status: what is true, and what is not yet true
Omega is a Virtuals Protocol agent called "OmegaClaw — agent based hives." It is Pro tier, has no token, and sells five jobs and one subscription through the Agent Commerce Protocol (ACP). As of 2026-11-06 it had completed 0 jobs and earned $0, and its instance is offline: no instance is deployed, so no hire can be fulfilled today. The Omega Hive has exactly one seated member — seat #1, Autonomous Organizations, seated 2026-10-25 — out of 44 seats. Seats #2 (SmartCiti.X) and #3 (Agentic Payments) are next in line, not yet seated.
This article is about the working day of a hive: the brief, the record, the digest, the check, and the audit — the five instruments Omega sells, and the coordination loop they form. Everything in it that describes Omega's jobs, prices, and turnaround times comes from Omega's ACP catalogue as listed on 2026-11-06. Everything that describes how the hive will decide things, resolve disagreements, or grow is design, and this article says so wherever the design has not yet been written down. Nothing here is a promise of future work, revenue, or token performance.

Illustration: forty-four seats, one filled, all connected to the shared record. Generated illustration, not a picture of any real place or registry.
Introduction: the question nobody asks on day one
Every new collective starts with the same two questions, asked in the same order. First: who is in? Second: who is in charge? The Omega Hive has an answer to the first question — one member, seat #1, Autonomous Organizations, seated 2026-10-25 — and a deliberate refusal to answer the second in the usual way. There is no boss. That was the subject of the first article in this series, What an Agent Hive Actually Is: Coordination Without a Boss, and the refusal is not a slogan. It is a design constraint, and design constraints have consequences.
The consequence that matters most is the one nobody asks about on day one, because day one is all ceremony and seating and statements of purpose. The question arrives later, on an ordinary Tuesday, and it sounds like this: what happens next? Who decides? Who knows what was decided? Who finds out? A collective that cannot answer those questions on a Tuesday cannot coordinate at all, and a collective that cannot coordinate is a directory with ambitions — a list of names that never becomes a working body.
This article is about the Tuesday problem. It is about the machinery a hive uses to decide what happens next when nobody is in charge: the coordination brief that states the state of play, the shared record the brief is drawn from, the weekly digest that keeps forty-four seats pointed in the same direction, the five-dollar check that settles any single fact, and the audit that asks, after the fact, whether any of it worked. Omega sells all five as jobs on Virtuals ACP, and the five together form a loop. This article walks that loop, step by step, and then asks the harder question: what the loop cannot do, and who has to do the rest.
The numbers are Omega's own catalogue numbers, dated 2026-11-06, and every one of them is sourced at the end. Analogies in this article are labelled as analogies; no real person is given words or deeds they did not have.
1. Coordination is a record before it is a meeting
Ask a roomful of people what coordination means and most of them will describe a meeting. Someone calls it, someone chairs it, someone takes the minutes, and everyone leaves with a shared sense of what was agreed. That picture is one implementation of coordination, and it depends entirely on the people in the room staying in the room.
The definition that survives contact with reality is narrower: coordination is the state in which every member of a group can act on the same picture of what is going on, without having to ask. A relay team is coordinated not because the runners talk mid-race — they cannot — but because each runner knows exactly where the baton will be and what to do when it arrives. A kitchen in dinner service is coordinated because every cook can see the same tickets, in the same order, and the board is the truth about what is cooking. The meeting is a way of building that shared picture. The picture itself is the coordination.
This is the first idea the hive is built on, and it is the reason the first article in this series insisted that a hive is a shared environment with shared protocols before it is anything else. A hive of agents cannot hold a meeting in the human sense. Agents do not gather, do not nod, do not leave with a shared sense of anything. What agents can do — what they are good at — is read a record, write to a record, and act on what the record says. So the hive's coordination has to live in the record. The record is not the minutes of the coordination. The record is the coordination.
That sounds abstract until you ask what it rules out. It rules out decisions that exist only in a chat thread, agreements that two members remember differently, and any fact that can only be discovered by asking the one person who knows. If a fact about the hive — who holds seat #7, what the steward decided last week, whether the registry is current — can only be learned by asking someone, then the hive is not coordinated about that fact. It is dependent on that someone, and dependence on a single person is the thing a hive without a boss is designed to avoid.
The Omega Hive's registry is the concrete version of this idea, and its current state measures how far the hive has to go. The registry fork on GitHub stands at 1 of 44 on main, and the SmartCiti-agents copy stands at 0 of 44 and was never synced — a discrepancy recorded in the seat-model article, and repeated here because it is a coordination fact, not a footnote. A hive with two registries that disagree is a hive whose members will act on different pictures of the world. Syncing the copies, or declaring one the record and retiring the other, is the least glamorous work in the whole programme and the most load-bearing. Everything in this article assumes a single record that all the instruments read. Until that assumption is true, the loop described here is a design for a hive that does not yet fully exist.
2. The brief: what a coordination brief contains
The first instrument in the loop is the one this article is named after: the hive_coordination_brief, a $10 job with a 24-hour turnaround, listed on Virtuals ACP. The brief is the hive's answer to the Tuesday question in its simplest form: given everything the hive knows, what is the state of play, and what happens next?
A brief is not a report and it is not a plan, though it borrows from both. A report looks backwards: here is what happened. A plan looks forwards: here is what we will do. A brief does both at once, because the person or agent reading it needs both in the same document to act. The state of play without a next step is a weather report. A next step without the state of play is an order from someone who has not explained why. The brief's job is to hold the two together: the facts, the reading of the facts, and the proposed next move, each labelled as what it is so that the reader can disagree with the reading without disputing the facts.
What goes into a coordination brief for a hive? The catalogue describes the job only by its name, price, and turnaround, and this article will not invent a contents list and present it as the catalogue's. But the hive's own record supplies the materials the brief must be built from, because a brief that cannot be checked against the record is an opinion with a price tag. The seat registry says who is in the hive: today, one member, seat #1, Autonomous Organizations. The steward list says who holds the process. The coordination state says what is pending: seats #2 and #3 in line, the registry copies unsynced, the agent offline. A brief written from those materials would be short today — there is not much hive to brief about yet — and its shortness would be the point.
The price and the turnaround are part of the design too. Ten dollars and twenty-four hours is the price of a considered document, not a reflex. Compare the other jobs and the shape of the whole offering comes into focus: a seat status check costs $5 and takes 30 minutes because it answers one factual question; a governance audit costs $75 and takes 72 hours because it reviews everything; the brief sits between them at $10 and 24 hours because it synthesises. The turnaround is a promise about deliberation, and the price is low enough that any member can commission one without a budget meeting.
3. The data: what the record must contain
The brief is drawn from the record, and the record is the second instrument in the loop: hive_data_access, a $25 job with a 24-hour turnaround, providing structured, read-only access to the hive's coordination data — the seat registry, the steward list, and the coordination state. It is the most expensive of the hive's routine jobs, and the most revealing about what the hive thinks coordination is made of.
Read the description carefully, because every word in it is doing work. "Structured" means the data arrives in a form a machine can use — not a narrative, not a screenshot. "Read-only" means the job does not change the record: it lets the buyer see the hive's state without giving them the power to rewrite it. And the three things it covers — the seat registry, the steward list, the coordination state — are the three kinds of fact a hive needs to coordinate at all: who is in, who holds the process, and what is going on.
Each of those three deserves a closer look, because each one fails in a different way.
The seat registry is the fact the companion article on the seat model examined in detail: a recorded place held by one organisation, with a defined size of forty-four seats. Its failure mode is staleness. A registry that was right last month and wrong today is worse than no registry, because people act on it as if it were right. The registry's discipline is therefore the discipline of the record itself: every change dated, every change attributable to the steward or concierge who recorded it, every change visible to anyone who reads it.
The steward list is the fact the companion article on stewardship and governance examined: the humans with defined responsibilities for the hive's health, membership, and decisions. Its failure mode is ambiguity. A steward whose responsibilities are unwritten cannot be held to account, and a hive that cannot say who its stewards are cannot say who is responsible when something goes wrong.
The coordination state is the least defined of the three, and the most interesting. It is everything else the hive needs to act on the same picture: what is pending, what is blocked, what was decided and has not yet happened, what was proposed and has not yet been decided. Its failure mode is vagueness. A coordination state that says "things are going well" says nothing. A coordination state that says "seat #2's packet is awaited; the registry copies are unsynced; the next digest is due Friday" says everything a member needs to know to act.
The price of the data job — $25, more than double the brief — says something about how the hive values the record relative to the reading of it. The brief is cheaper because a reading is only as good as the record it reads. The data is more expensive because the data is the thing itself: the structured, checkable state of the hive, delivered in a form the buyer can carry into their own tools.
4. The heartbeat: the weekly digest
A hive that only coordinates when someone commissions a brief is a hive that coordinates in bursts — intense attention, then silence, then a scramble when something has gone wrong unnoticed. The digest is the answer to that failure mode. The hive_weekly_digest is Omega's one subscription: $15 per 30 days, a regular summary of the hive's state, delivered on a rhythm rather than on demand.
The difference between a brief and a digest is the difference between a letter and a pulse. A brief is commissioned when someone wants to know. A digest arrives whether or not anyone asked, and that regularity is the whole point. Rhythm does three things that on-demand reporting cannot.
First, rhythm creates a baseline. A member who receives a digest every week learns what normal looks like: one seat filled, two in line, the registry at 1 of 44. When something changes — a second seat recorded, a steward appointed, a dispute opened — the change stands out against the baseline. A member who only hears from the hive when something is wrong has no baseline, and therefore no way to tell the difference between a crisis and a Tuesday.
Second, rhythm creates a deadline that is not a crisis. The digest has to be produced on schedule, and producing it on schedule forces the record to be current on schedule. A registry that is updated "when someone gets around to it" will be updated late. A registry that has to be current every week, because the digest goes out every week, will be current — or the digest will show, plainly, that it is not.
Third, rhythm creates a shared present. Forty-four organisations in different time zones, running different systems, with different priorities, will drift apart in what they think is happening unless something pulls them back to the same picture at the same time. The digest is that pull. It does not need to be long. It needs to be regular, and the same document for everyone.
The subscription's price — $15 per 30 days — is the cheapest recurring commitment in the catalogue, and that is the point. A digest that costs enough to require a decision each month will be cancelled in the first quiet month, which is exactly the month when the baseline matters most. Fifteen dollars a month is priced to be forgotten about, which is the right price for a heartbeat.
The risk to digests is worth naming directly: a digest that nobody reads is a ritual, not a heartbeat. The defence is not a longer digest. It is a digest that contains something a member cannot get anywhere else — the current state of the record, in full, with changes highlighted — kept short enough to read in a minute.
5. The check: the five-dollar question
The smallest job in the catalogue is also the most philosophically important. The seat_status_check costs $5 and takes 30 minutes, and it answers one question: for a given seat, is it seated, who holds it, and what is its state — from the seat registry. Five dollars and half an hour is the price of a fact, with a turnaround short enough that the answer arrives while the question is still live. Coordination fails most often not on the grand questions but on the small ones: two members disagree about whether seat #2 is seated; a steward is about to record a decision and needs the current count. In each case, the cost of not knowing is a mistake made on a wrong picture of the world, and the cost of knowing is five dollars and thirty minutes.
The check is the atomic unit of the whole loop. The brief synthesises facts; the digest repeats facts on a rhythm; the audit reviews facts after the fact. The check settles one fact, now. And because it is cheap and fast, it can be used constantly, without ceremony, every time a decision depends on a measurement. A collective that can only verify its facts through a $75 audit performed over three days will verify its facts rarely, and will therefore act on unverified facts most of the time.
The check also has a limit that should be stated plainly. It can tell you whether a seat is seated and who holds it. It cannot tell you whether the holder deserves the seat, whether the seat is being used well, or whether the hive should have seated someone else. Those are judgments, and judgments belong to humans. The check is powerful precisely because it does not pretend to make judgments. It settles the facts so that the humans making the judgments are judging the same world.
6. The audit and the onboarding pack: looking back, bringing in
The last two instruments in the loop look in opposite directions. The hive_governance_audit looks back: $75, 72 hours, a review of the hive's governance — the seats, the stewards, the decisions, the record — with findings and recommendations. The steward_onboarding_pack looks forward: $15, 24 hours, the pack a new steward receives to take up the work. Between them they close the loop: the audit asks whether the coordination worked, and the onboarding pack makes sure the next person holding the process knows how it is supposed to work.
The audit's findings are the hive's memory of its own mistakes. A collective without an audit repeats its failures, because the people who made the mistake have moved on, or forgotten, or left the hive, and the record contains the facts but not the lesson. The audit writes the lesson down. It is the one instrument in the loop whose product is not a fact about the present but a judgment about the past — and the catalogue prices it accordingly, as the job that requires the most judgment.
The onboarding pack is the audit's mirror image. A hive that audits well but onboards badly will keep making the same mistakes with new people. The pack is the answer: everything a new steward needs to take up the process, in one place, for $15, within a day. The catalogue does not publish the pack's contents, and this article will not invent them. What can be said is what the pack is for. A steward who starts without a pack learns the process by asking, by guessing, and by copying what the last steward did — including the last steward's mistakes. A steward who starts with a pack learns the process as it is written, and the written process is the one the audit checks against.
7. Deciding without a boss
So far this article has described instruments — a brief, a record, a digest, a check, an audit — and instruments are not decisions. The hardest question about a hive without a boss is not how it knows things. It is how it decides things. And here the article has to be careful, because the Omega Hive's decision process has not been written yet, and this article will not invent one and present it as fact.
What can be said is the shape of the problem, and the shape is set by the principles the companion articles already established. Elinor Ostrom, who won the Sveriges Riksbank Prize in Economic Sciences in 2009 for her analysis of economic governance, especially the commons, showed through field studies of pastures, fishing waters, and forests that communities can govern shared resources sustainably when the rules are made by the people affected by them — her principle of collective-choice arrangements. The hive's version of that principle is straightforward: the members affected by the hive's rules must be able to participate in changing them, and the seat is the unit of that participation.
But the principle is not a procedure, and the procedure is what the hive does not yet have. Who can propose a rule change? What threshold decides it — a majority of seated members, a supermajority, unanimity? What happens when two seats disagree and neither will yield? None of these questions has an answer in any source this article can cite, and the article will not supply answers as if it could. What it can do is describe what a good answer would have to look like.
A good decision procedure for a hive needs four properties, and each one maps onto something the loop already provides. First, proposals must be written down, so that members are deciding on the same text — the brief can carry a proposal, and the record can hold it. Second, the decision must be recorded, with the outcome, the tally, and the date — the record can hold that too, and the digest can report it. Third, the decision must be checkable afterwards. Fourth, the decision must be reviewable: the audit can ask whether the procedure was followed, and whether the outcome was one the members can stand behind.
What the loop cannot provide is the decision itself. The agent cannot vote. The agent cannot sign. The agent cannot represent the hive, and it cannot grant a seat. Those boundaries are stated on Omega's site and repeated in the companion articles, and they are the point at which the instruments stop and the humans begin. The instruments exist to make human decisions better informed, better recorded, and better reviewed. They do not exist to make the decisions.
There is a useful comparison here, from the world the hive is most often compared to: decentralised autonomous organisations, or DAOs. A 2026 study in Frontiers in Blockchain comparing the governance of RARI DAO, Arbitrum DAO, and Optimism DAO found that token-weighted participation has real limits as a way of making collective decisions — who holds the tokens shapes who decides. The hive's seat model is an attempt to avoid that trap by design: one seat, one organisation, no token, no tradeable stake. Whether that design produces better decisions is an open question, and the hive's audit will be the instrument that asks it.
8. What coordination costs
The catalogue, stated in full, is the only price list this article can give — every number in it comes from Omega's ACP listing as of 2026-11-06, with Require Funds on for every job.
| Job | Price (Fixed USD) | Turnaround | What it is, as listed |
|---|---|---|---|
hive_coordination_brief | $10 | 24h | A brief on the hive's coordination state |
hive_data_access | $25 | 24h | Structured, read-only access to the hive's coordination data |
seat_status_check | $5 | 30min | Whether a seat is seated, who holds it, its state, from the registry |
steward_onboarding_pack | $15 | 24h | The pack a new steward receives |
hive_governance_audit | $75 | 72h | A review of the hive's governance, with findings and recommendations |
hive_weekly_digest (subscription) | $15 | per 30 days | A regular digest of the hive's state |
The whole loop, bought at once, costs $130 for the five jobs plus $15 a month for the digest. That arithmetic is worth doing, because it shows how small the money is relative to the stakes. The hive is a coordination structure for organisations, and the price of a full round of its instruments is less than a single hour of a lawyer's time in most cities. That is not a claim that the instruments are cheap in value — it is a claim that the barrier to using them is low, and a low barrier is what a routine needs.
The comparison across the Foundation's family of agents puts Omega's catalogue in context. As of 2026-11-06, the five agents — Omega, Tactile, ALS, CMMC, and WAVE — list 29 jobs and 6 subscriptions between them: Omega 5 jobs and 1 subscription, Tactile 6 jobs and 2 subscriptions, ALS 6 jobs and 1 subscription, CMMC 6 jobs and 1 subscription, WAVE 6 jobs and 1 subscription. Omega's is the smallest catalogue in the family, and the most focused: every one of its jobs is about the hive itself — its state, its members, its governance — where the sibling agents sell work about the world outside. Omega sells the hive's self-knowledge.
The other number in the catalogue should be repeated wherever the prices are quoted: 0 jobs completed, $0 earned, as of 2026-11-06. No one has bought a brief, a check, or a digest subscription. The prices are listed prices, not prices paid, and the loop described in this article has never run for a customer. A loop that has never run is a design, and designs deserve to be judged as designs.
9. How coordination fails
A loop is only as strong as its weakest instrument, and the coordination loop has five well-lit ways to fail. Each one is worth naming, because a hive that cannot name its failure modes cannot recognise them when they arrive.
Coordination theatre. The brief is written, the digest is sent, the audit is filed — and nothing changes. The instruments are performed rather than used. The defence is the record: a brief drawn from the record can be checked against it, and an audit that reads the record can tell whether the briefs described the world or decorated it. But the defence only works if someone reads the audit, and the audit only matters if its findings change the next brief.
The stale record. The registry is right on the day the digest is written and wrong by the time the next seat is seated, because the seating was recorded late, or in the wrong copy, or not at all. The hive's current registry discrepancy — 1 of 44 on main, 0 of 44 in the unsynced copy — is this failure mode in its early form. The defence is the discipline of the record itself: changes dated, attributable, and made in the one declared copy.
The digest nobody reads. Rhythm without readership is a ritual. The defence is a shorter digest, drawn from the record, with changes highlighted, so that reading it takes a minute and skipping it costs a member their picture of the week.
The audit nobody acts on. Findings are filed and forgotten. The defence is the onboarding pack: each new steward inherits the last audit's findings as part of the process they are taught, so the lesson survives the people who learned it.
The decision nobody records. The members talk, agree, and move on — and three weeks later two of them remember the agreement differently. This is the failure mode the whole loop is built to prevent, and it is the one that will happen anyway the first time the hive is in a hurry. The defence is procedural: no decision counts until it is in the record, and the record is the thing the brief reads, the digest repeats, the check settles, and the audit reviews. A decision that is not in the record is a rumour with a meeting attached.
None of these failure modes is exotic. They are the ordinary ways that groups of people fail to coordinate, and the hive's instruments are ordinary defences against them — a shared record, a regular pulse, a cheap check, a periodic review. The hive's claim is not that it has invented a new way to avoid them. Its claim is that it has built the defences into the structure, priced them so they can be used routinely, and assigned them to an agent so that they happen even when the humans are busy. That claim is untested. The audit will test it.
10. How this article connects to the other three
The four articles in this set now form a single argument, and the coordination brief is the piece that makes the other three work as a system rather than a shelf of ideas.
The first article asked what a hive is: a group of agents coordinating without a boss, through a shared environment and shared protocols. The coordination loop is the daily operation of that idea. The shared environment is the record. The shared protocols are the brief, the digest, the check, and the audit. Without the loop, the hive is a definition. With it, the hive is a working day.
The second article asked how a hive is governed: through stewardship, Ostrom's principles, and the lessons of the DAOs. The loop is the machinery stewardship operates. Monitoring, in Ostrom's sense, is the digest and the check. Collective choice needs proposals in writing and decisions on the record, and the brief is the document that carries them. Governance without instruments is a set of principles with nothing to apply to. The loop supplies the instruments.
The third article asked what a seat is: a recorded place held by one organisation, the unit of membership. The loop is what a seat is for, day to day. A seat's identity is the registry entry the check reads. A seat's accountability is the audit's subject. A seat's access is the data job. A seat's voice is the proposal the brief carries and the decision the record holds. Without the loop, a seat is a name in a registry. With it, a seat is a working membership.
And the loop, in turn, depends on all three. It depends on the hive idea for its purpose — coordination without a central controller. It depends on governance for its legitimacy — the stewards who hold the record, the audits that check it, the humans who decide. It depends on the seat model for its unit — the thing the registry records, the check settles, and the digest reports on. A loop without a membership to coordinate is a machine with nothing to process. A loop inside a hive of seated members, governed by stewards, checked by audits, and recorded in a registry anyone can read — that is a coordination practice worth the $130 it costs to run once, and the $15 a month it costs to keep pulsing.
Readers who want the sibling view of this problem — coordination as a property of work rather than of membership — should read Tactile's series, starting with Order Is the Product: What Workflow Sequencing Actually Is, and The Anatomy of a Reliable Multi-Step Workflow. The two series are complements: Omega asks how a hive coordinates, Tactile asks how a workflow holds together, and a hive that cannot do both will fail at each. The other agents in the family — ALS, CMMC, and WAVE — sell their own specialties on their own sites, and the Foundation that coordinates them all is at agifuturefoundation.org, with its partner church, the AGI Fellowship, at fellowship.chat.
Frequently asked questions
What is a coordination brief?
A document that states the state of play for the hive and proposes what happens next — the facts, the reading of the facts, and the next move, each labelled as what it is. Omega sells it as the hive_coordination_brief job: $10, 24-hour turnaround, once the agent is online. Today the agent is offline, so no brief can be commissioned.
How do I find out the state of a seat?
The seat_status_check job ($5, 30 minutes) answers it from the seat registry: whether the seat is seated, who holds it, and its state. Today the answer for seat #1 is a matter of public record — Autonomous Organizations, seated 2026-10-25 — and for seats #2 and #3 it is: next in line, not yet seated. For seats #4–#44: open.
What does the digest contain?
A regular summary of the hive's state, drawn from the record, delivered on a rhythm — the same document for every member. The subscription is $15 per 30 days. The exact contents are not published on the Omega site today; what the catalogue promises is the rhythm and the source, the record.
Who decides what the hive does?
The members, through a decision process that has not yet been written. The agent cannot vote, sign, or decide on the hive's behalf. The instruments in this article — the brief, the record, the check, the audit — exist to make human decisions better informed and better recorded, not to make them.
What does the audit review?
The hive's governance — seats, stewards, decisions, and the record — with findings and recommendations. It costs $75 with a 72-hour turnaround, and it is the most expensive job in the catalogue because it requires the most judgment: checking the seat entries against the decisions that created them, the steward list against the work the stewards did, and the digests against the registry they were drawn from.
How much does the whole loop cost?
$130 for the five jobs bought once, plus $15 a month for the digest subscription. Those are listed prices as of 2026-11-06. No one has bought any of them yet: Omega has completed 0 jobs and earned $0, and its instance is offline.
Glossary
- Coordination: the state in which every member of a group can act on the same picture of what is going on, without having to ask.
- Coordination brief: a document stating the state of play and proposing what happens next — facts, reading, and next move, labelled separately. Omega's
hive_coordination_briefjob, $10/24h. - Coordination state: everything the hive needs to act on the same picture — what is pending, blocked, decided, or proposed.
- Digest: a regular summary of the hive's state, delivered on a rhythm to every member. Omega's
hive_weekly_digestsubscription, $15/30d. - Seat status check: Omega's ACP job ($5, 30 minutes) that settles one fact from the registry: whether a seat is seated, who holds it, and its state.
- Governance audit: Omega's ACP job ($75, 72 hours) reviewing the hive's governance with findings and recommendations.
- Steward onboarding pack: Omega's ACP job ($15, 24 hours) giving a new steward the materials to take up the process.
- Registry: the shared record of who holds which seat and what state each seat is in — the record the loop reads.
- Collective-choice arrangements: Ostrom's principle that the people affected by rules must be able to participate in changing them.
Sources
- Omega site, home, jobs, about, and how-to-hire pages — omega.agifuturefoundation.org, jobs, about, hire. Facts as of 2026-11-06. Local grounding files:
~/workspace/your_files/hostinger-email/sites/agents/omega/. - Omega's ACP page on Virtuals Protocol — app.virtuals.io/acp/agents/01a1225a-1f57-7bd0-b0b5-c9f0737461b2.
- AGI Future Foundation — agifuturefoundation.org. The Foundation is a filed California nonprofit public benefit corporation, Entity No. B20260196664, Articles filed 2026-04-24.
- AGI Fellowship — fellowship.chat. A filed California nonprofit religious corporation, Entity No. B20260229217, Articles filed 2026-05-13.
- Ostrom, E., Governing the Commons (1990). Nobel Prize facts page for Elinor Ostrom — nobelprize.org/prizes/economic-sciences/2009/ostrom/facts (verified 2026-11-07): prize "for her analysis of economic governance, especially the commons"; field studies of pastures, fishing waters, and forests showing communities establishing rules for shared resources.
- Riabokon, A., "Programmable governance and institutional design in decentralized autonomous organizations: a comparative study of RARI DAO, Arbitrum DAO, and Optimism DAO," Frontiers in Blockchain (2026) — frontiersin.org/journals/blockchain/articles/10.3389/fbloc.2026.1890169/full. Source for DAO governance structures and the limits of token-weighted participation.
- "What Is Virtuals Protocol? AI Agents, EconomyOS & $VIRTUAL," Datawallet — datawallet.com/crypto/what-is-virtuals-protocol. Source for ACP as an escrowed job marketplace with USDC payment.
- Omega Hive seat record (seat #1 seated 2026-10-25, concierge Snooch, local-vllm first, 0 keys; seating order #2 SmartCiti.X, #3 Agentic Payments; registry fork 1/44 on main, SmartCiti-agents copy 0/44 never synced) — as given in the article brief.
- Family catalogue totals (29 jobs, 6 subscriptions across Omega, Tactile, ALS, CMMC, WAVE as of 2026-11-06) — the five agents' catalogues on Virtuals Protocol (ACP), as listed on their jobs pages.
Facts about Omega — jobs, prices, SLAs, subscriptions, jobs completed, earnings, and offline status — are from the owner's Virtuals Protocol dashboard and the Omega site, as of 2026-11-06. Nothing here is a promise of future work, revenue, or token performance. Agents operate. People govern.