Sequenced delivery: what is real, and what unlocks what next
Chapter 17 Sequenced delivery: what is real, and what unlocks what next This chapter answers the question skeptical readers ask first: what is already production-proven, and what must ship before later claims are fair? It is a one-page map; the full dependency columns, item IDs, and phase-gate text live in Appendix D. The sequencing here is dependency-gated execution, not a methodology manifesto. Teams may parallelize wherever the dependency graph allows; the rule is that downstream public claims require upstream completion—especially for settlement, identity, verification, and marketplace economics. 17.1 Design discipline: control plane before marketplace rhetoric Phase NA in Appendix D encodes a deliberate ordering: identity (ERC-8004 mapping), settlement breadth (multi-facilitator x402 and related rails), operational control (accountscoped job cancellation, app-level rate limiting), and packaging (AVB repository) are treated as prerequisites to reputation-weighted routing and attention-style economics. Safety, settlement, and control-plane maturity come before marketplace positioning. In particular, attention-auction revenue claims should not be marketed until AgentRank (N-10) is live in shadow or production routing and automated quality learning (N-11) is fed by at least one production signal—the phase gate spelled out for Phase NC in the appendix. 17.2 Shipped base stack (production path) The following are live today on the ScryptedAI API and workers, listed in the order each layer depends on the layers above it (registry → durable jobs → orchestration → workers → economics → surface): ID Deliverable (summary) D-01–D-03 Registry schema; job/account model; shadow graph (durable DAG state). D-04–D-07 RecipeExecutorV2; Celery + Redis; dual-path webhook + polling completion; multi-provider adapters. D-08–D-12 Asset pipeline (S3/CloudFront); SCRYPTOSHI ledger; x402 path; bearer-token auth; moderation. D-13–D-15 ConcurrencyManager; fault-tolerance layers; SSE job stream. D-16 HTTP API surface (FastAPI, OpenAPI). First-party applications (Chapter 10) stress-test D-04–D-15; they do not substitute for on-chain registration or CRPC, which sit in the phased next work below. 86
17.3 Phased next work (gated progressions) Upcoming work is grouped so that each phase completes (or explicitly waives) its dependencies before later phases are treated as credible for external messaging. Nothing below is framed as inevitable; it is gated: CRPC testnet, committees, EigenLayer-class staking, and advanced autonomy advance only as the listed prerequisites land. Phase Focus (headline) NA Identity, AVB repo, facilitator breadth, cancellation, rate limiting. NB Output-based CRPC testnet, committee ops, optional Solana ER pilot, Eigen staking narrative. NC AgentRank, quality learning, Open Intents expansion, path-aware reputation. ND AVS slashing predicates, verified-tier routing, DA posts, cross-chain/liquid pools, federated coordination. NE Sidelines, Chibi Clash, framework integrations (MCP bidirectional). NF VRF committees, CRPC×RL, world models, zkML, content-addressed storage economics. Phase-on-phase sketch: D-* → NA → NB → NC parallel to parts of NE → ND → NF, with overlap only where verification claims are not asserted. Open research and legal/token blockers that can halt public claims regardless of engineering progress remain consolidated in Chapter 16, §16.7. 87
Source: transcribed from the compiled Scrypted Network Design whitepaper PDF for web reading. Layout, figures, and pagination may differ from the PDF.