ORBITORBIT v0.1 · Draft
Agent SDLC ↗GitHub ↗

~/orbit/schemas

ORBIT RESOURCES & SCHEMAS · v0.1 DRAFT

Machine-readable contracts.

Four core portable record types define the ORBIT planning and reconciliation model.

Browse resourcesView the complete example →

RESOURCE MODEL

Records relate by reference.

                        ┌──────────────┐
                        │     Plan     │
                        │ durable      │
                        │ intent       │
                        └──────┬───────┘
                               │
                     planId + revision
                               │
                               ▼
┌───────────────────┐   ┌──────────────────┐
│ ProjectSnapshot   │   │  Reconciliation  │
│ observed state    │   │ assessment       │
└─────────┬─────────┘   └────────┬─────────┘
          │                       │
          │ projectSnapshotId     │ justifies
          └───────────────▶───────┘
                                  │
                                  ▼
                         ┌──────────────────┐
                         │ ExecutionSlice   │
                         │ bounded work     │
                         └──────────────────┘

REFERENCE SEMANTICS

Reconciliation references a Plan and Plan revision, a ProjectSnapshot, and canonical Acceptance Criteria.

ExecutionSlice references a Plan and Plan revision, the Reconciliation that justified it, an Outcome, contributing Acceptance Criteria, and relevant repository provenance.

Project
  └── 1..N Plans
        └── 1..N Outcomes

Plan
  └── 1..N Acceptance Criteria

RESOURCE INDEX

Four portable resources.

RESOURCE REFERENCES

ResourcePurposeReferences
PlanDurable planning intent and desired outcomes.Project
ProjectSnapshotPoint-in-time observed project and repository state.Project, repositories
ReconciliationStructured assessment of a Plan against current evidence.Plan revision, ProjectSnapshot, Acceptance Criteria
ExecutionSliceThe next bounded change justified by current evidence.Plan revision, Outcome, Reconciliation, Acceptance Criteria, repository provenance

COMPLETE EXAMPLE

Follow one outcome through the ORBIT model.

Plan
plan-sso @ revision 1
         │
         ▼
ProjectSnapshot
snapshot-2026-09-14
         │
         ▼
Reconciliation
reconciliation-001
         │
         ▼
ExecutionSlice
slice-001

Each node is a complete, schema-valid resource. Open the Plan, ProjectSnapshot, Reconciliation, or ExecutionSlice example.

plan-sso
├── outcome: sso
└── criterion: ac-1

snapshot-2026-09-14
└── web @ 81fee032

reconciliation-001
├── plan: plan-sso rev 1
├── snapshot: snapshot-2026-09-14
└── assesses: ac-1

slice-001
├── plan: plan-sso rev 1
├── outcome: sso
├── reconciliation: reconciliation-001
├── contributesTo: ac-1
└── web @ 81fee032

HOW TO READ ORBIT RESOURCES

GuideRead semantics and relationships.JSON SchemaInspect machine-valid structure.InvariantsCheck lifecycle meaning on each resource guide.ExamplesFollow a conforming resource.

JSON Schema validates structural conformance. ORBIT conformance may also depend on semantic invariants defined by the specification.