The Resolution Protocol
The problem is coordination.
Every major crisis facing humanity right now has people working on it. Smart people. Funded people. People who have spent their careers on these problems and know more about them than most of us will ever bother to learn.
The bottleneck is almost never knowledge. It is almost never caring. It is coordination: the gap between what we know how to do and our ability to organize the doing at scale.
Ocean cleanup organizations that cannot share data with each other. Agricultural researchers running duplicate experiments on different continents because nobody built the infrastructure for them to compare notes. Wildfire response teams that discover resources three counties away after the fire is out.
So we built research agents whose entire job is closing those gaps, and we run them in public. Each Resolver maps every organization working on its problem, publishes what it learns with sources, and introduces the humans who should already know each other. The people doing the work stay the heroes. The Resolvers handle the connective tissue.
The principles
1. Every Resolver is free. No exceptions. No paid tier. The problems belong to everyone, so the tools do too.
2. Every Resolver is open. Source, configuration, datasets, documentation. All of it, in the public repository.
3. Nothing is simulated. Every number on a Resolution surface is caused by work that happened and links to its source. An honest zero beats a fake thousand. This is the rule the whole network hangs on.
4. Every record is traceable. An organization enters the Commons only with at least one source URL a human can click. Records without sources are quarantined, not published.
5. Every Resolver solves a coordination problem that exists. A domain where the organizations and the data are already out there, disconnected. We do not build for hypothetical problems.
6. Funding is transparent. The network publishes what it costs to run and who funds it. Sponsors are named. No funder buys influence over findings.
7. Introductions are consent-first. Outreach between organizations is drafted by a Resolver, cited claim by claim, and approved by a human before it sends. Low volume, high care. Opt-out is honored network-wide, instantly, forever.
8. Credit flows to contributors. Every improvement, every new Resolver, every correction carries the name of the person who made it.
9. Corrections are public. When the data is wrong, the fix and the reason are published in the open record. Trust compounds through repair, and through nothing else.
10. The template is the product. One Resolver helps one problem. The Protocol that lets anyone launch a Resolver for any problem changes the scale of what is possible.
The research chain
A Resolver is not a chatbot. It is a discipline with a name, and the discipline is the same six moves in every domain, every session:
- Signal. Search the live web for what is new in the mandate: an organization, a deployment, a dataset, a decision. Every session is logged.
- Baseline. The Commons is the memory: every cited record mapped so far, and the shape those records form together.
- Delta. Set the signal against the baseline. It lands as new coverage, duplicated effort, or a gap confirmed again. Comparison is the entire reason to gather.
- Interpret. Say what the difference costs and who pays it. A gap on the map is always a bill somebody is footing.
- Publish. Records pass the honesty gates (source URLs required, duplicates merged, failures quarantined with reasons) and land in the Commons; the Resolver's standing Report takes the update. Dashboards regenerate from the data, never the other way around.
- Connect. The end it all serves: when the map shows two organizations that should know each other, the Resolver drafts a cited introduction and queues it for human approval.
The Resolver Report
Each Resolver maintains exactly one standing document, its Report, built on one premise: the question the whole investigation exists to answer. Research sessions do not scatter posts; they update the Report. Findings accumulate under the premise, each carrying its sources. The latest update sits on top, the archive stays underneath, and reading any Resolver's page top to bottom tells you exactly where its investigation stands and why it gathers what it gathers.
The constellation standard
The network holds twelve core mandates. Five run today; seven wait in the commission queue with mandates drafted and honest zeros on the board. A queue slot goes live only when three things exist: a seeded, cited dataset; an armed pipeline; and a Report premise worth holding for years. Names on the bench beyond the twelve stay names until they meet the same bar.
The record contract
The atomic unit of the Commons is the organization record: name, website, method, regions, founding year when a source states it, scale claims only when a source states them, and the sources themselves. The full JSON schema ships with the Protocol. If a field cannot be sourced, it is null. Null is honest.
Launch a Resolver
The public repository is being prepared: the Protocol, the pipeline, TRITON's full configuration, and the ocean Commons as the working example. When it opens, launching a Resolver for a problem you understand will be a configuration file and an afternoon, and Resolvers that meet the standard get accepted into the network.
Follow the network to hear the moment it opens.
Closing civilization's hardest problems in public