Product roadmap
One chain, read properly. Then coordination. Then scale.
The mission model ships complete before the connectors, because it is the component that is hardest to change later and the one most often retro-fitted badly.
- Phase 01Live
Live System
The full mission model, running: objective language, decomposition, the one-to-three agent decision, the manufacturing sequence and a reconciled brief, all pointed at pons on Robinhood Chain.
OutcomeA complete mission model that the chain connectors plug into without the interface being redesigned around them.
- Natural-language objectives with an inspectable parse
- Objective decomposition into assignable subtasks
- One-to-three agent selection with stated trade-offs
- Procedural agent foundry and manufacturing sequence
- Unified mission brief with per-claim confidence
- Documentation, white paper and access programme
- Phase 02In Development
Chain Connectors
Wire the read surfaces one at a time: factory launches, pool and pricing state, swap flow, creator history, and the onchain verification pass that gates every claim.
OutcomeMissions that resolve against current chain state, with every retained claim traceable to a read.
- Factory launch indexing from TokenLaunched
- Pool configuration, slot0 pricing and locked position reads
- Swap flow indexing with direction, size and wallet retained
- Onchain verification of supply and lock state
- Creator history across launches and fee claims
- Mission persistence and accounts
- Phase 03Planned
Coordinated Agents
Move from agents that run beside each other to agents that work together on a shared context, plus the derived surfaces that need more than a single read.
OutcomeCoordination that stays legible afterwards: every handoff, disagreement and downgrade is traceable.
- Shared mission context across a running team
- Agent handoffs with stated reasons
- Live mission monitoring and redirection
- Holder graph reconstruction and overlap measurement
- Channel resolution and venue coverage
- Phase 04Planned
Persistent Intelligence
Turn a one-shot mission into a standing watch that compares block ranges and tells you what moved.
OutcomeMissions that keep working after you close the tab, and report what changed rather than what stayed the same.
- Scheduled missions on a block or time cadence
- Run-to-run diffs as the primary output
- Threshold alerts on graduation distance and holder concentration
- Team workspaces with shared monitors
- Phase 05Planned
Open Agent Platform
Open the model up: programmatic missions, authored archetypes, and the same mission shape pointed at launch venues beyond pons.
OutcomeA platform where the archetype list is authored by the people using it rather than fixed by us.
- Developer API for mission creation and retrieval
- Custom agents with authored capabilities and scopes
- Additional launch venues on the same mission model
Principles behind the ordering
One chain, read properly
Depth on pons and Robinhood Chain beats shallow coverage of ten venues. The archetypes are shaped by what this chain actually exposes: launch events, pool state, swap flow, holder structure and creator history.
Read-only by construction
pons is non-custodial and its contracts are self-describing. VENDOR never needs a key, a signature or a wallet connection to do its job, and it is built so that stays true.
One connector at a time
Each read surface is wired and disclosed individually with its real status. A connector is not announced before it exists.
Provenance is not optional
A claim that cannot be matched to chain state is downgraded and shown as downgraded. That constraint shapes the architecture rather than being bolted on.