TriportRPC
DashboardDocs

What is missing before Base publication

This card reaches code_complete at most. It does not establish preprod_verified or deployed_verified.

  • Canonical publication is complete: docs/api/chains.registry.json contains the unique Base mainnet descriptor. Runtime publication remains readiness-filtered.
  • Runtime evidence: CAPABILITIES marks every runtime_capability_pass false. Handler/schema presence is not readiness.
  • Writes and simulation: accepted evidence is parser-only; there is no signed successful submission, bundle/private/4337 admission, simulation result, inclusion, or finality proof (Q02).
  • Blink: the executable bundle profile is key_required; provider credential and finite quota are absent from this staging card.
  • Capacity and params: minimum tiers and RPS are enforced product policy. Provider ceilings, historical depth/range, bundle maximum, and numeric AA/private budgets remain unknown.
  • Archive: old-block observations do not prove archive state or an archive SLA.

Exact regeneration

After a canonical registry or final tier annotation change, rerun without an override:

node docs/api/guide/base/generate-method-pages.mjs

Then regenerate/recheck these exact owned outputs:

  • docs/api/guide/base/json-rpc/index.md
  • all 61 docs/api/guide/base/json-rpc/<method>.md files listed by docs/api/json-rpc/base.openrpc.json
  • docs/api/guide/base/limits.md if budget values or minimum tiers changed
  • docs/api/guide/base/index.md and docs/api/guide/base/what-is-missing.md when canonical publication/runtime status changes
  • docs/api/guide/base/contract-guards.mjs only if the accepted evidence vocabulary or contract invariants change

Downstream N7-base-22 must regenerate docs navigation/search/LLM artifacts from the published registry and these pages; exact consumer inputs are triport-web/lib/docs/tree.ts::buildDocsTree, triport-web/scripts/gen-search-index.ts, and triport-web/scripts/gen-llms-txt.ts. Those files are outside this card's ownership.