Roadmap / Staged development
One terminal first Then the exchange Then a federation
How the first service hypothesis relates to the long-term vision of a Resource Exchange, Mission Continuity and federated ports—and what must be demonstrated before each step.
Four stages
The founding record sets out four scenario windows. The gates between them are this roadmap’s proposed conditions: a stage should open only when the one before it has produced evidence.
- 2026–27
First service terminal
One bounded service class. One complete mission. A second independent buyer.
Gate: independent second-buyer reuse is measured and holds.
- 2028–30
Multi-buyer acceptance network
Several buyers accept work from shared supplier profiles across more than one service class.
Gate: reuse repeats beyond the first service class, under written operating rules.
- 2031–36
Resource exchange and federation
Services, compute and capabilities are exchanged; more than one port follows compatible rules.
Gate: accepted-work records make offers comparable across independent providers.
- 2037–51
Possible global infrastructure
A federated network of economic ports for autonomous agents.
A possibility that depends on every earlier gate, not a forecast.
Scenario windows from the founding record. They are planning scenarios, not forecasts or commitments.
Why this order
The long-term components are not a separate plan. Each one consumes records that an earlier stage produces.
Service Acceptance comes first
It is the only part of the vision that a single buyer, a single supplier and one bounded service can test. It produces the records everything else reads: service profiles, mandates, evidence events and acceptance decisions.
A Resource Exchange needs acceptance history
An exchange of services, compute and capabilities has to compare offers from independent providers. Without records of accepted work it would be a directory, which the founding assessment says APA should not begin as.
Mission Continuity needs mandates and records
A mission can only be resumed or handed to another authorized participant if its scope, evidence and state are already recorded—and if the new participant receives its own valid mandate.
Federation needs operating rules
More than one port can interoperate only when participation, evidence and dispute rules are written down and proven in one port first.
The next ninety days
The first stage begins with a 90-day validation sequence of five gates. The periods are relative planning windows; they are not a statement that recruitment, implementation or paid trials have started.
0 / 5gates demonstrated
The five gates are targets from the founding record. None has been attempted yet, so nothing is counted. A gate is marked demonstrated only when a documented outcome supports it.
- Gate 01
Days 01–15Not startedDefine the service
One bounded service class with its acceptance criteria, architecture and threat model.
- Gate 02
Days 16–30Not startedInvestigate buyer needs
15 interviews and at least six documented buyer problems.
- Gate 03
Days 31–50Not startedBuild a bounded prototype
One complete mission with evidence and an explicit acceptance decision.
- Gate 04
Days 51–70Not startedTest commercial commitment
Two independent paying buyers.
- Gate 05
Days 71–90Not startedMeasure independent reuse
Three suppliers reused by Buyer B with at least 50% less active onboarding time.
When to stop or change course
The founding record states its own refutation condition. If independent reuse or willingness to pay does not materialize, the network claim should be stopped or changed.
- If Buyer B must repeat nearly all of Buyer A’s onboarding, the result describes an integration business, not a port.
- If neither buyers nor suppliers will pay, shared acceptance may be useful without being a business.
- If the saving comes from a simpler requirement, the comparison is invalid and has to be repeated.
A roadmap is a plan. Nothing beyond the founding architecture and this website has been established.