Following the AliExpress decision, this blueprint sets out how any very large platform can seal its detection and compliance-check timelines with an independent third party, before the fact.

The four categories of the SOURCE 0 Doctrine are not parallel classifications. They constitute a causal sequence — problem domain, methodological response, legal operationalization, normative constraint field — whose coherence depends on the formal articulation of three inter-layer interfaces. This article makes that architecture explicit, disambiguates its shared vocabulary across eleven distinct definitions, establishes the material modification threshold, closes the deliberate misclassification escape route, and maps each layer against its precise regulatory obligations. The four-layer architecture is not a model. It is a condition of proof.

Faced with Shadow Runs and systemic frontier model drift, standard downstream observability (SIEM/EDR) fails. The SOURCE 0 doctrine introduces Opposability-as-a-Service (OaaS): an ex-ante cryptographic baseline and judicial escrow designed to protect directors by shifting the burden of proof back to the regulator.