Objective-facts settlement
Nothing in Dynamo accepts, stores, or acts on subjective quality signals. Settlement, SLA enforcement, refunds, and hard stops run on verified-value settlement on objective facts - measurable, signed, reproducible quantities:
- latency (p50/p95/p99), error rate, availability
- duration, unit counts, completion counts
- explicit acceptance events, system-of-record events
A "quality score", a rating, a model-judged grade - none of these exist anywhere in the protocol's types, schemas, or configs. This is a hard boundary, audited in code review and enforced by schema: an oracle type with a subjective field is rejected, not discouraged.
Why the boundary is drawn here
Money that moves on subjective signals moves on disputable signals - and a dispute about taste cannot be settled by cryptography. Objective facts can be attested, signed, re-verified offline, and carried into an evidence bundle that a third party can check without trusting either side. The protocol confines itself to claims that survive that treatment.
The corollary: Dynamo never claims your counterparty's work was good. It proves the work was delivered within declared objective thresholds - or that it was not, in which case the failed units are never paid.
Oracles under this doctrine
Oracle adapters are built against open-source interfaces only - never a vendor account, API key, or business relationship. Adapters emit SIGNED objective-fact attestations exclusively, and facts are evaluated fresh and in-band: a missing, stale, or unverifiable fact fails closed at the point of decision - the action does not proceed, and the gap is logged. There is no "assume healthy" path.
SLA hooks
Status: Preview. SLA terms are part of the engine's verified runtime. They are declared as objective thresholds (for example: p95 latency under a bound, error rate under a bound, availability over a bound, within a measurement window). Attested degradation triggers the objective ladder - throttle after a declared number of breached windows, then stop, then an attested break-point from which degraded units are refunded buyer-whole-first. SLA-failed units are never paid. make demo-sla runs one degraded stream end-to-end on every backend, closing with the engine==settlement reconciliation to the unit.
A core's owner API takes no SLA terms. On a core, a stream's objective terms come from a terms catalogue (CORE_TERMS_CATALOGUE_FILE, which needs CORE_VERIFIED=1; both off by default; with the stablecoin or credit card mode on, the catalogue must be signed and its signer pinned with CORE_TERMS_CATALOGUE_SIGNER, or the core refuses to start with catalogue_signer_required): an accepted, signed breach report stops the stream, and inside the holdback window the value streamed after the breach is refunded buyer-whole-first.