Schemas and profiles

These are the exact contracts included in the RC1 implementation candidate. Download the source package for schemas, examples, validators, fixtures and clients. The Python wheel contains Python modules and packaged profiles; it does not contain the separate Node clients or all documentation.

Select the contract first

Layer	Identity
Candidate edition	1.2.0-rc.1
Native policy	1.2.0-draft.1
Current service, authority and asset envelopes	1.2.0-draft.3
Python distribution	0.0.0.dev3
Historical service	1.2.0-draft.2

These identities are not interchangeable. A service version alone does not select payment, storage, asset or archive capabilities. Unknown fields in a closed schema and unselected profiles must be rejected; changing a version string does not convert a signed message.

Policy and current profiles

The current set contains the native policy schema and 16 profile schemas.

Contract	Exact schema
Resource scope, actions, purposes and duties	Native policy
Service authority, delegation, keys and operations	Delegation
Free offers, acceptance, receipts, access and reports	Free exchange
fixed-quote-v1 quote, mandate and verification	Payment
Paid offer, agreement and access messages	Paid agreements
asset_evidence_v1 manifests and source closure	Asset evidence
Explicit storage selection in signed agreement messages	Storage agreements
storage_sessions_v1 custody and checkpoint reports	Storage sessions
observation_coverage_v1 declarations and known expectations	Observation coverage

Archive variants are separately selected contracts. An ordinary archive cannot silently omit storage parents, asset manifests or payment proofs.

Included capabilities	Free archive	Paid archive
Ordinary agreement	Free	Paid
Continuing storage	Storage/free	Storage/paid
Native assets	Assets/free	Assets/paid
Assets and continuing storage	Assets/storage/free	Assets/storage/paid

The specification lists each exact profile identifier. The field inventory helps locate definitions; the schemas and semantic contracts govern their meaning. Helper objects do not imply public HTTP endpoints.

Structure is only one check

These Draft 2020-12 schemas describe decoded JSON structure. Implementations must also validate strict JSON encoding, original signed bytes, authority and key roles, resource scope, timestamps, cross-message bindings, lifecycle transitions and durable retry behavior. JSON Schema alone does not enforce the protocol’s lexical integer rules or establish trusted signatures.

Start with a static free policy example, the policy core and the standalone quickstart. See validation for the distinct structural and semantic evidence.

Legacy contracts remain separate

The published draft-2 schema guide and draft-2 reference download describe the historical same-origin free implementation and its 17 envelope schemas. They remain available unchanged. Use their original validators for historical evidence; follow upgrade guidance for new deployments.