What Compute owns.

Authority

Discovery is this site and Binding api_base. The public API is https://api.compute.sylphx.com/v1. Production customer calls present a Platform-signed Ed25519 Project Binding and a short-lived Identity Delegation. Compute verifies Binding; it does not mint it. Caller project headers do not change the partition. COMPUTE_API_KEY is local scaffold only and is not production admission.

Platform supplies Binding, the Work provider, and the Journal Wake spec Compute commands. Hands/Clock HTTP-POSTs the opaque Wake URL. Those dependencies may make Compute unready or an execution truthfully blocked. They do not become a second writer of Compute records.

Time is not this process

Compute is an HTTP service and may sleep. The Cell Clock cannot sleep. Compute owns the Schedule row and the Tick ledger. Creating or updating a Schedule commands Platform to place a Journal Wake. After :tick, Compute POSTs the customer HTTP target or admits a Run, then places the next dueAt.

A Tick is recorded at :tick. A failed HTTP target is a bounded dead-letter on the Schedule, not Job success and not a fabricated receipt. A due Tick is not terminal Job success.

Lifecycle

• Job — revisioned, artifact-backed definition. Create returns a durable mutation Operation. Update and delete are revision-fenced.
• Schedule — its own resource: calendar, timezone field, overlap, catch-up, target http or execute, retry, pause. Not an alias of Job.
• Tick — unique (schedule_id, intended_at). Exact replay returns that Tick. intended_at does not change on retry.
• Operation — every mutation and :execute is readable. Terminal states never reopen.
• Receipt — accepted at most once, bound to generation. No success-shaped receipt without a provider receipt.

Boundaries

• This host is the product site. Customer operations live on the API at https://api.compute.sylphx.com/v1.
• Compute does not mint Binding, Delegation, or a product API key.
• A local executor, in-process metronome, or Kubernetes CronJob is not the customer Schedule. Clock is Cell fabric.
• Functions are not a Compute pack. POST /v1/functions is not a create path.
• Public SDK and CLI are generated from this Product Contract (compute-sdk, binary compute). They are not Platform sylphx-sdk / sylphx-cli.

Where to go next

Start with first success. Bind fields against the Product Contract. Session isolation is a contract resource; the HTTP Session lifecycle is documented there, not as first success.