Skip to main content

Known boundaries

This documentation is pinned to one inspected SCM revision. These are the boundaries that revision actually establishes — read them before repeating any claim elsewhere.

Product boundaries​

  • Compatibility is versioned and domain-dependent. Modules connect where their versioned contracts align; selecting a domain does not bundle every surrounding mechanism, and nothing implies arbitrary live replacement of modules inside an active deal.
  • General agent runtimes remain external to SCM. The pinned source supplies signed role protocols and policy hooks; agents are participant-controlled callers, never bundled intelligence or a central actor.
  • Service evaluation follows the selected domain and mechanism. There is no universal SLA monitor, guaranteed enforcement, automatic adjudicator, or generic resolver; the settlement-servicing baseline explicitly exposes no generic service(plan) → receipt engine.
  • Arbitration is the escrow-arbiter surface. Listings declare allowed arbiter demands and proposals concretize exactly one; no fuller dispute-resolution workflow exists at the pin (From listing to delivery).
  • Model metadata is not a universal SCM Registry field. A served model name is seller service metadata (Machine-readable records).
  • Commercial settlement is separate from physical assignment and delivery. Payment settles through the configured mechanism; capacity admission, scheduling, and provider execution are a separate, seller-side physical path that only physical domains use.

Status boundaries​

  • The pinned revision is an inspected development snapshot. Source references prove inspected source behavior; a release tag identifies a released component; neither establishes deployed availability, hosted service, or production readiness.
  • The named public Registry is preproduction. It appears in the synchronized quickstarts as a Base Sepolia endpoint and was observed to be read-open on 2026-08-13. That dated read probe does not promise continuing access; write authority was not tested or granted. It may legitimately serve an empty listing set, and nothing here implies inventory.
  • Bare metal carries a transitional packaging note at the pin. The domain schema is split out while some compose services still use the VM seller image — reproduced verbatim in the bare-metal seller guide.
  • The development architecture is not released behavior. ARCHITECTURE.md and the capability specifications describe the inspected source tree for implementers and reviewers.

What this documentation deliberately avoids​

No page on this site claims hosted checkout, browser transactions, live inventory or instant availability, demand or revenue, equal domain maturity, universal Registry filters, or a central agent runtime. If you find copy that appears to, read it against this page and the pinned sources in Source and revisions — the pin wins.