Internet of Intelligence

IIP-066: Routing receipts and fee eligibility

IIP-066 is recorded on the decentralized.* roadmap with status Evidence-gated in Horizon 5 — public commitments: Routing receipts and fee eligibility. RoutingDecisionReceipts with fee eligibility only when real candidates were compared, under marketplace neutrality.

IIP-066 Roadmap Record

IIP-066: Routing receipts and fee eligibility is an IOI roadmap record for the decentralized.* surface. Its status is Evidence-gated in Horizon 5 — public commitments and it belongs to the Routing track. Blocked on explicit prerequisite, conformance, safety, demand, or settlement evidence. The canonical scope is: RoutingDecisionReceipts with fee eligibility only when real candidates were compared, under marketplace neutrality.

Surface Context

This record should be read as part of the decentralized.* roadmap, not as a replacement for source papers or product pages. The parent surface gives the broader context for why this milestone exists, what it depends on, and which IOI surfaces it supports. The parent decentralized.* surface depends on runtime, wallet. The parent surface does not currently unblock another roadmap surface directly.

Evidence And Verification

The record is designed to make roadmap evidence crawlable and separable from research claims. This item also names item-level dependencies: IIP-030. Evidence links below point to the paper, release, repository, developer documentation, or product page that supports this milestone.

Canonical Relationship

This page is the canonical roadmap record for IIP-066, while the parent roadmap surface and linked research pages remain the canonical sources for broader product and protocol context. Internal links point here when the milestone status, horizon, dependencies, or evidence trail for Routing receipts and fee eligibility matters.

Roadmap Role

IIP-066 exists to clarify roadmap status, bounded scope, horizon placement, and evidence relationships. Technical concepts flow through this page to canonical research pages, while product or runtime context flows to the relevant surface page. This preserves a complete status and evidence trail without making roadmap records compete with deeper IOI papers.