Development plan
What we ship, in order.
Forge Layer is a protocol first. This roadmap is the sequence we will not skip: make the contract the source of truth, make the record citable, then widen what can be inspected. Dates move. Order does not.
Phase 0
The forge
Shipping · NowA complete, Studio-deployable registry: Intelligent Contract, rehearsal engine, public docket, and wallet-signed writes.
- submit / challenge / resolve with GEN stakes and specific reverts
- Validator inspection via gl.nondet + Equivalence Principle consensus
- Public registry, citable docket pages, admin pause/fee/withdraw
- Vercel-ready frontend; graceful degradation until PUBLIC_CONTRACT_ADDRESS is set
Phase 1
On the record
Next · Q4 2026Take the rehearsal off the critical path. Make every closed docket something a newsroom or rights desk can actually cite.
- Studio deploy on studionet, then Bradbury testnet, then mainnet
- Read-through indexer so pagination stays fast past a few thousand dockets
- Shareable citation cards and an embeddable docket widget
- Content-ref allowlist / size probe before an image URL is accepted on-chain
Phase 2
Chamber
Later · H1 2027Richer evidence, a bounded appeals path, and a reputation that follows wallets without turning into a social graph.
- Audio and short-video content types (same stake machine, new inspect path)
- One-shot appeal window after an inconclusive or disputed verdict
- Optional watcher bonds so spam filings become expensive
- Warden reputation: win/loss/inconclusive history, never a credit score
Phase 3
Attestation
Horizon · H2 2027Forge Layer as a primitive other contracts and courts can call — not a destination website.
- Cross-registry attestations other Intelligent Contracts can read
- Legal export packs: signed PDF + on-chain receipt for a closed docket
- Watch GenVM SDK headers and re-verify exec_prompt image attachment
- Permissionless mirrors: anyone can host a read-only registry against the same contract