Publication Policy

Depth does not sell semantic privilege.

Public semantics stay public. Operational layers may improve timeliness, continuity, monitoring, or delivery, but they must not change what the payload means.

Depth has a narrow trust model.

Authoritative layer — The authoritative public layer is the oracle-committed artifact and its associated payload semantics. This is the layer that determines what was published, which versions apply, and which chain and commitment provenance applies.

Convenience layers — Convenience layers may include the explorer UI, the public API gateway, and cached or transformed views. These layers may improve usability, but they must not silently change semantics.

A public commitment attests that the referenced payload was produced and anchored under explicit semantics. At a high level, it provides:

• payload identity and integrity
• commitment provenance
• chain context
• version-linked interpretation surface

A public commitment does not attest to:

• that execution based on the payload will succeed
• that the payload is an exhaustive market view
• that the downstream consumer interpreted the payload correctly

Early beta oracle commitments were recorded on Base Sepolia. Canonical live commitments now occur on Base mainnet.

The underlying payload domain did not change across that transition. In both cases, the payload describes Base mainnet liquidity and execution context. What changed was the network used to anchor the proof.

Consumers should interpret mixed historical rows using oracle_chain_id:

• 8453 — canonical live commitments on Base mainnet
• 84532 — historical beta commitments on Base Sepolia

This distinction is about commitment provenance, not a change in the underlying liquidity domain.

The public API is a convenience layer over public artifacts. Its responsibilities are:

• make committed payloads easier to query
• preserve provenance and version fields
• avoid implying stronger guarantees than the underlying public layer provides

The public API should not imply:

• real-time guarantees
• SLA-backed delivery
• semantic differences from the public committed artifact

The explorer is a legibility layer. Its responsibilities are:

• make the oracle output understandable
• surface qualification, refusal, and commitment clearly
• preserve the meaning of the underlying artifact

The explorer should not imply recommendations, hidden scoring, or stronger guarantees than the underlying payload attests to.

Depth may offer operational layers around the public qualification surface. These may include higher-cadence delivery, continuity monitoring, retention, support expectations, and production-oriented access layers.

These layers are acceptable only if they preserve one rule:

they improve operations, not semantics.

A paid layer must not change:

• what the payload means
• how policy eligibility is interpreted
• what public reason categories mean
• what a commitment attests to

Public token coverage may be baseline-funded or operationally underwritten. If underwritten coverage exists, underwriting may fund operations around publication and continuity. It must not buy:

• semantic privilege
• explorer featuring as a truth signal
• altered policy outcomes

Public artifacts must remain public artifacts.

Consumers should interpret public artifacts together with:

• spec_version
• execution_policy.policy_version
• the public methodology and policy docs that correspond to those versions

Publication and access improvements do not override those semantic boundaries. If publication semantics themselves change materially, the publication policy version should move.