Build specification

Schemas#

The schemas/ directory contains 22 JSON Schema 2020-12 contracts:

• actor.schema.json
• ally.schema.json
• asset.schema.json
• avatar.schema.json
• decision.schema.json
• entity.schema.json
• event.schema.json
• funding-decision.schema.json
• funding-request.schema.json
• island.schema.json
• level.schema.json
• orientation.schema.json
• portal.schema.json
• project-space.schema.json
• project.schema.json
• quest-state.schema.json
• quest.schema.json
• relationship.schema.json
• resource.schema.json
• role.schema.json
• scene-instance.schema.json
• scene.schema.json

Schemas define portable interchange. Runtime invariants that span objects—exactly one accountable Organization, no secret preview leakage, Role coverage, quest reachability, ledger balance, one canonical Actor identity—are enforced by validation and command policy rather than pretending a single JSON document can prove them.

Stable IDs are external identity. AGE vertex IDs, renderer component pointers, and client object addresses never leave their storage/runtime boundary. Schema changes require semantic version, migration note, fixtures, and backward-compatibility decision.