ORBITORBIT v0.1 · Draft

~/orbit/adopter-guide

ORBIT v0.1 · ADOPTER GUIDE

Adopt one planning loop.

Start with one meaningful outcome. Keep intent durable, observe the project, reconcile the evidence, and hand an executor one bounded change.

Move one outcome through the loop.

  1. Choose an outcome.State the durable result in plain language.
  2. Create a Plan.Add stable outcome and acceptance-criterion IDs.
  3. Capture a Project Snapshot.Record only the repository facts relevant to that Plan.
  4. Reconcile.Assess each criterion with evidence, including unknowns and changes.
  5. Create one Execution Slice.Define the smallest justified change with explicit exclusions.
  6. Execute and observe again.Use the executor you already have, then capture the resulting state.

Keep the contracts portable.

ORBIT defines four records. Store them in a repository, database, or another system that preserves their identity and references.

Keep provider mechanics outside ORBIT.

ORBIT stops at the portable Execution Slice. Your local policy decides whether it becomes a GitHub issue, branch, agent run, CI workflow, or direct developer handoff.

ORBIT recordsPlan → Snapshot → Reconciliation → Execution Slice
↓
Your executorIssue tracker, agent, CI, or developer workflow

Require human approval for the first slice.

Human approval is a practical adoption choice. It is outside the ORBIT core and can change as confidence grows.

Keep the boundary clear.

Plans and Outcomes are durable. Slices, tickets, and jobs are derived work.

Ready to try it?

Open the schemas, create one Plan, and complete one observe → reconcile → slice cycle.