Schema validator
Use any JSON Schema implementation. The published schemas define machine-valid structure.
Browse schemas →ORBIT v0.1 · CONFORMANCE
Show what your implementation produces and consumes.
ORBIT conformance is capability-based. An implementation can produce, observe, reconcile, or execute without adopting a particular agent, tracker, repository, or CI system.
CAPABILITY MATRIX
Four implementation roles.
| Role | Produces | Consumes | Minimum evidence |
|---|---|---|---|
| Producer | One or more valid ORBIT records. | Plan context or source inputs. | Schema-valid fixture and stable identity. |
| Observer | ProjectSnapshot. | Repository and project facts. | Traceable observations and capture time. |
| Reconciler | Reconciliation. | Plan and ProjectSnapshot. | Criterion assessments linked to evidence. |
| Executor | Execution result outside ORBIT. | ExecutionSlice. | Scope, exclusions, and provenance are preserved. |
VALIDATION LAYERS
Use three checks.
- Structure. Validate JSON against the published resource schema.
- Semantics. Check invariants that JSON Schema cannot express.
- Interoperability. Run cross-record fixtures and verify references resolve.
Draft status
ORBIT v0.1 schemas and invariants may change before 1.0. Report the version tested by an implementation.
TOOLING PATH
Keep validators small and replaceable.
Invariant checker
Run semantic rules for IDs, revisions, references, provenance, and lifecycle meaning.
Read the specification →Fixture suite
Test minimal and complete records together so references and version claims remain visible.
Open examples →CONFORMANCE CLAIM
Make support easy to assess.
Publish the ORBIT version, roles supported, resources produced or consumed, validator version, and known limitations.
implementation: example-orbit-adapter orbitVersion: 0.1 roles: [observer, reconciler] resources: [ProjectSnapshot, Reconciliation] validation: schema + invariants + fixtures
NEXT
Start with the evidence you can show.
Choose one role, validate one complete fixture, and document the boundary between ORBIT records and provider-specific execution.