Core Concepts
Fundamental architectural principles behind Addressables release staging, runtime probes, and honest evidence matrices.
PatchProof approaches asset delivery verification differently than traditional unit testing frameworks. Rather than mocking Addressables APIs or testing individual prefabs in Editor isolation, PatchProof treats content delivery as a state machine distributed across networks and storage caches.
Conceptual Sections
- The Rehearsal Model: The 5-stage lifecycle (Register → Declare → Set Conditions → Execute → Evidence).
- Client Modes: Deep dive into Instrumented Binary, Release Twin, and External Observation execution modes.
- Evidence & Unverified States: Why an empty green matrix is refused, and how partial denominators preserve truth.
- Cache States & Invariants: How Fresh, WarmOld, and MixedPartial cache sandboxes simulate real-world player devices.
- Byte-Boundary Faults: The mechanics of injecting network faults at specific packet offsets.
- Semantic Content Contracts: Beyond string keys — asserting type safety and schema compatibility across releases.