Arkhai maintains SCM source and documentation plus only services explicitly identified as Arkhai-operated. Operators configure registry read and write gates independently, schema and search, policy chains, settlement assets and networks, provider and registry sets, seller-provisioning integrations, topology, optional private reachability, and deployment economics. Sellers publish to one or more configured operator registries and control seller-originated offers and rates, inventory claims, infrastructure, provisioning, credentials handoff, and delivery. Buyers control registry and seller selection, workload suitability, credentials, transaction decisions, aggregation choices, and negotiation policy. Signing-publisher provenance is not legal identity, KYB, or capacity verification. In the current compute VM path, amount-based policies vary one scalar amount; supported amountless and non-ERC20 escrow shapes are exact-match, while non-amount terms remain pinned or validated. Sellers provision KVM VMs and hand off SSH access; GPU passthrough is optional where supported and proves no inventory or hosted service. Other resource adapters require separate implementation. No single mandatory matching broker is required across configured registries. SCM quickstarts document an Arkhai preproduction HTTP registry, but that does not prove liveness, production status, inventory, or a stable, approved public HTTPS website source.