Pay for execution work. Trust the receipt.

What is commercially meaningful

Chargeable customer work is admitted execution Operations and their attempts — work that can produce a receipt and usage facts. Process liveness, readiness, and Ticks without a receipt are not billable success and are not the product oracle.

A published list price, included volume, or overage appears only through the current Commerce catalog revision. If this site and checkout ever disagree, Commerce is the money authority and this page is wrong.

Trust contract

• No silent success. Admission, Tick, attempt, and receipt are distinct facts.
• No product keys. Binding plus Identity Delegation is the envelope. Compute does not mint Binding.
• No fabricated receipts. An unavailable provider is blocked. Usage facts require a terminal receipt.
• Generation fences. Replay of a claim returns original fences. An ordinary late receipt from an old generation is rejected.
• One writer. Compute authors Compute rows. Platform does not. Hands does not.
• This site is content. The product site is documentation and trust. The API is https://api.compute.sylphx.com/v1.

Leaving and support

Project-scoped export and deletion follow Platform and Identity lifecycle plus Compute receipts for in-flight executions. Support reads the same Operations the contract exposes. Support does not SQL a receipt into success and does not issue a Compute key.