Specifications people and software can read together.

Start with the job in front of you

A schema describes the accepted shape of a file. Examples show that shape in use. Orientation pages explain who owns the meaning and how a version can change.

• Build or validate Open an exact schema and use its identifier or public route in your tooling.
• Learn the structure Read an example beside its schema to see the relationship between fields.
• Check meaning and authority Use the human orientation when interpretation or adoption carries a consequential decision.
• Move a real question Follow a finite collaboration loop from source through evidence, stopping point, and re-entry.

Published contracts

These links expose every contract in the current public build. Exact-version files retain their published bytes; a later byte change receives a new version or route.

• Repository collection 1.0.0

  Describes repository entry points, related families, source and delivery roles, and lived use.

  Schema · Example

• Context Canvas 1.0.0

  Describes collections, visitor surfaces, prototypes, reference artifacts, and the experience each one is designed to support.

  Orientation · Schema · JSON-LD context

  Examples: collection · visitor surface · prototype

• Collaboration Skills 0.1.0

  Describes portable collaboration instructions and the observations that can change how those instructions are routed.

  Public skills · Orientation · Skill schema · Account schema

  Examples: portable skill · completed task projection · collaboration account

• A3 Expanded 0.2

  Four related structures describe change, a rendered view, source registration, and coverage.

  Change record · View model · Source registry · Coverage record

• A3 state 0.1

  Describes the saved state of an A3 stacked-cube decision instrument.

  State schema

• Visualization Fidelity Atlas 0.1

  Describes visual treatments and the evidence used to compare or select them.

  Atlas schema

• Strategy Canvas 0.2

  Describes factors, plotted offerings, weighting, comparison state, and exchange behavior for a strategy canvas.

  Strategy Canvas schema

• Local prototype manifest

  Describes the files and relationships needed to open a self-contained prototype locally.

  Manifest schema

See two contracts in practice

The public examples below let a visitor move from a machine contract to a working decision surface.

Identity, delivery, and use