ORBITORBIT v0.1 · Draft

ORBIT v0.1 · Draft

Planning and Reconciliation Specification.

An ORBIT Plan is a portable declaration of durable software intent and outcomes designed to be reconciled against current reality before execution work is materialised.

A Plan is not a backlog.
ORBIT keeps intent durable while deriving only the next bounded execution slice from current reality.

Conventions

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY express normative requirements in this draft.

Artefacts

A Plan MUST contain durable intent, outcomes and acceptance criteria. A Project Snapshot records repository state at a point in time. A Reconciliation compares the two and records observations, assessments and evidence. An Execution Slice describes one bounded software change and its provenance.

Revision and staleness

A Plan revision changes when durable intent or planning knowledge changes. Repository revisions belong to snapshots and reconciliations. An executor MUST block a slice when a relevant repository commit differs from the slice provenance.

Execution neutrality

ORBIT does not define coding agents, issue trackers, branch workflows, CI/CD, model providers, source-control hosting, or orchestration systems.

View the draft schemas · Read the concepts