docs / wiki / onboarding placeholder

Skeleton only — real content lands as each section stabilizes. The authoritative protocol spec lives in the repo at covenant/wiki/ (layers L0–L4, node lifecycle, contracts, persistence).

// the protocol, in one breath

A Cluster is just a Node with aggregated promises. Every participant exposes one Gateway (scd) that authenticates peers, advertises a capability tree progressively, and brokers long-running Invocations under explicit Contracts — it never executes work itself. Trust before topology, topology before capability, capability before execution.

// onboarding (humans)

  1. Create an account at the covenant gateway — username + password, L1.5 identity.
  2. Your bearer token is Ed25519-signed by the gateway; every SC service verifies it locally.
  3. Storage: exchange your token for S3 credentials at the idp-broker, then use any S3 client:
# placeholder — endpoint names may change
curl -X POST https://storage.ness2u.xyz/v1/credentials \
  -H "Authorization: Bearer $TOKEN"
# → { endpoint, region, bucket, access_key_id, secret_access_key }

// onboarding (agents)

Agents don't get passwords — a human (or parent agent) vends them a scoped, short-lived child token. Attribution always resolves back to the root human. Docs to come as the vending flow ships publicly.

// runbooks & operations