Operations

Operations covers the runtime contracts the engine and the platform hold open to the buyer. Tiers and limits describes the buyer ladder. Data retention describes the memory-only law. Reports and attestation language describes the verbatim framing under which every diagnosis and validation artefact is structured.

What Operations covers

This section is the operational contract between the platform and the buyer. Each page documents one runtime contract. The contracts hold across every tier and every substrate; the tier table changes the caps and the lens unlocks, but it does not change the data-retention law or the attestation framing.

The three surfaces

Tiers and limits

Five tiers, set at runtime. Monthly counts, upload caps, and lens unlocks per tier, sourced directly from the engine gates and the counter ladder.
Read Tiers and limits
Data retention

Memory-only is law. Raw uploads are held for sixty minutes per session and removed. Nothing is written to disk, to Postgres, or to logs.
Read Data retention
Reports and attestation language

The verbatim five-framework attestation strip and the locked disclaimer framing carried on every diagnosis and validation PDF.
Read Reports and attestation language

Where to start

The spine of this section runs Tiers and limits, Data retention, Reports and attestation language. Tiers and limits is the first page because it is the contract every buyer hits at sign-up. Read in order, or jump to the page that answers the question in front of you.