Geo

Geo is a knowledge-graph application in which each topic community, called a space, decides by on-chain vote what goes into its part of the graph. Its app, Geo Genesis, opened to early access on 10 January 2025 with one space, Crypto News, where editors structure news stories and check the facts attached to them (Aragon). It is a working example of a wiki whose edits pass through a DAO: a change to a space's content is a proposal, and it lands only if the space's editors approve it.

How a space works

Geo stores information as a graph in which every data point is a triple of an entity, an attribute and a value (Geo). It follows GRC-20, a standard The Graph proposed so that different applications can share one knowledge graph (The Graph). A space holds one community's part of the graph, and anyone can see who added each entry and which vote accepted it.

A space has two roles. Members propose changes. Editors vote on proposals and execute the ones that pass, and the space's DAO contract, not any individual, holds the permission to publish (Aragon). A personal space, owned by one account, publishes without a vote.

Two speeds for an edit

Geo's second-generation contracts, specified in October 2025, give a DAO space two paths (Geo). On the fast path, a single action is proposed from a short list: add or remove a member, publish an edit, or flag or unflag content. It executes as soon as the yes votes reach a fixed count, and a single no vote moves it to the slow path, which restarts the voting period under a percentage threshold. On the slow path, several actions can be proposed at once, and the proposal needs a majority and a quorum. Adding or removing editors and changing the voting settings happen only through a passed proposal, and an editor or member can be restricted, which removes their access to the fast path until a passed slow-path proposal lifts it.

Two changes in February 2026 moved both paths, and the page that described them in October 2025 no longer matches the code. The fast path is no longer editors-only: members may use it where the space’s own default setting allows, any editor can restrict any member or editor from it, and only editors still vote (Geo). And the slow path no longer waits out its window. A second threshold, measured as a share of all editors rather than of votes cast, executes a well-supported proposal at once, with the old percentage-and-quorum test after the window as the fallback; the reason given is that in a space with one editor the delay serves no purpose (Geo). The shipped contract states it plainly in its own header: both paths execute immediately on a yes vote if the threshold is met (DAOSpace.sol).

The split is the one this wiki describes under typed versus arbitrary execution: routine edits run on a narrow, enumerated path, and anything that changes who holds power goes through the general, slower one.

There is now a third class that skips governance entirely. Beside the GOVERNANCE. actions, the contracts declare a PERMISSIONLESS. namespace – upvote, downvote, agree, disagree, verify, dispute and comment – whose allowlist the registry owner maintains. A reader’s stance on an entry, and their assertion that it is true or disputed, are recorded without a proposal and without an editor. So the claim that a change to a space’s content is a proposal holds for what the graph says, and not for what its readers say about it.

Leaving Aragon

Geo launched on Aragon OSx. Each space was an Aragon DAO with governance plugins written for Geo (aragon/geo-browser-contracts), and Aragon presented the launch as a showcase for its framework. Ten months later the design document that specifies the two paths opens by requiring the complete removal of Aragon OSx, which it says had added significant complexity (Geo). In its place, one registry contract becomes the entry point for every space and emits a single standard event, so Geo's indexer follows one contract instead of many; spaces become upgradeable contracts of their own, and personal spaces become ordinary accounts. The upgradeability is worth stating precisely: a DAO space is a beacon proxy produced by a factory (Geo), so one beacon change moves every space at once rather than each space deciding for itself.

The move was still not finished on 20 October 2026. Geo's app plan, last updated on 23 July 2026, keeps the app on testnet, lists the switch to the new contracts on testnet as waiting on the backend team, and leaves mainnet for later (Geo). The app itself is in active development, with changes merged into October 2026, and its network module still has no gas-sponsorship endpoint for mainnet (geo-network.ts; geobrowser/geogenesis).

Two things sit beside the governance work and are easy to miss. Geo publishes skills for coding agents to query the graph and publish to it, so an agent can create a space entry without opening the app – the vendor-side agent surface this wiki treats under the machine-readable DAO. And GRC-20, which the infobox above once attributed to The Graph, is now Geo’s own: The Graph’s copy is still a draft from November 2024, while Geo’s specification is marked Final and dated February 2026, published under its own @geoprotocol npm scope.

How Caper approaches this

A caper's own wiki takes the opposite order. Anyone who currently holds the caper's token, its vote token or its founder badge can save an edit, and it takes effect at once, with no vote. Every save writes a revision, and restoring an earlier version is recorded as another revision, so the history only grows (src/domains/wiki/actions.ts). Geo puts the vote before the edit; a caper keeps the edit and its history and leaves correction to the next holder.

The record sits in different places too. Geo publishes each accepted edit on-chain, as a pointer to its content; a caper's wiki lives in Caper's database, and what a caper puts on the ledger is its proposals and ballots.

References

• Aragon, Geo Genesis: A Breakthrough in Governing Knowledge Onchain (January 2025).
• The Graph, GRC-20 Hackathon Recap (June 2025) – GRC-20 and Geo Genesis.
• Geo, Geo singleton architecture (design document dated 22 October 2025) – removal of Aragon OSx, the space registry, fast and slow paths.
• Geo, v2 contracts cutover plan (updated 23 July 2026).
• Aragon, aragon/geo-browser-contracts – the OSx plugins Geo launched with.
• geobrowser/geogenesis – the Geo Genesis app.
• Geo, fast path for members and slow-path early execution (RFCs, February 2026); DAOSpace.sol and ActionsConstants.sol as shipped.