First success

Write then read on the peel. Do not log in here.

First useful success is an authorized KV put against Binding api_base and a get of the same key, value, and version. This site has no password form and no hosted login. dens Console is not a prerequisite. A Data product key is not a second Binding.

This first success is false if DATA-CONTRACT is false. DATA-CONTRACT is live family write-then-read through Platform-injected bindings, with predecessor dens retired. That is site-copy truth. It is not a graph prerequisite of DATA-SITE. DATA-SITE depends on DATA-PROTO.

Job

Independent developer or agent: persist one versioned value for a Sylphx project and read it back from Data, not from a client callback.

Prerequisites

A Platform-injected Data binding. Discover the peel from Binding api_base (https://api.data.sylphx.com/v1). Residual dens data.api.sylphx.com is not dest. Do not compile a sibling hostname and do not hold a Data product key.
An Identity-signed delegation whose closed claims agree with that binding on product data, contract digest, project, revision, and environment.
A caller-declared KV namespace id via PutResource with kind RESOURCE_KIND_KV_NAMESPACE.
The generated SDK (sylphx-data-sdk) or CLI (sylphx-data-cli) from this Product Contract in SylphxAI/data. Install from git or path; they are not on crates.io. Do not invent a handwritten JSON SDK.

Minimum call

ProtoJSON for PutValueRequest. Bytes are standard base64. Path key and body key must agree.

PUT https://api.data.sylphx.com/v1/kv/kv-demo/greeting
Authorization: Bearer <sylphx-delegation+jwt>
Sylphx-Project-Binding: <sylphx-project-binding+jwt>
Sylphx-Effect-Id: <closed-ascii-intent-id>
Content-Type: application/json

{
  "namespaceId": "kv-demo",
  "key": "greeting",
  "value": "aGVsbG8=",
  "ttlSeconds": "60"
}

Readback

GET the same path with a new effect id. Success is the same key, value, and version. Exact replay of the mutation with the same delegation and effect id returns the stored terminal and does not execute a second write. Database first success is not this page: a database is ready only after the correlated signed Platform Operation, not from a metadata 201.

Typed failure

Observation	Meaning	Next
401	Missing, expired, or forged envelope	Mint a fresh delegation; do not send a Data product key
403	Capability or limit insufficient	Ask Identity/Platform for a subset that includes this resource
Conflict on effect id	Same id, different intent	New effect id, or replay the original bytes
Health 200 only	Availability, not write-then-read	DATA-CONTRACT remains false until family oracles hold

From this repository: cargo run --locked -p sylphx-data-cli -- --help shows the Binding + Delegation envelope. That is not live first success. Live first success still requires a bound, deployed peel and a current binding head. Completing the call on a local checkout is not a live DATA-CONTRACT claim. Dens retirement is a Platform-then-Hands prune, not this set.