Schemas reference

Schemas are registered on-chain via x/registry (MsgCreateSchema, MsgSetSchemaActive, MsgSetSchemaMinters). Normative definitions live in ADRs and x/registry/types/devnet.go fixtures.

scope3_business_travel_v1

Field	Value
Version	v1
Domain	Emissions (Domain_EMISSIONS)
is_supply	false — does not mint J
Required roles	OPERATOR, INTEGRATOR
Parameters	co2e (gCO₂e, scale 0), scope (=3), distance (metres)
Rules	DUPLICATE_SUBJECT_WINDOW_V1, TIME_BOUNDS_V1
Fixture minter	p:zevo-integrator
Example subject asset	a:zevo-fleet-1 (owner p:zevo-host)

Writer API issues this schema via ingest (scope3SchemaName in services/ingest/submitter/trip_submitter.go).

ev_charge_quarterly (supply contrast)

Field	Value
is_supply	true — mints J from energy parameter
Claim unit	energy / unit J (see docs/spec/02-attest.md)

Listing schemas via REST

curl -s https://rest.testnet.carbon12.network/c12/registry/v1/schemas/list | jq .

Creating new schemas

Production schemas require governance and ADR-backed spec updates. Module messages:

• MsgCreateSchema
• MsgSetSchemaActive
• MsgSetSchemaMinters

See proto/c12/registry/v1/tx.proto and docs/spec/02-attest.md.