Jig is the deterministic execution engine for approved software plans: it runs work under policy, records evidence, and stops in inspectable states when autonomy is not allowed.
The approved product and redesign documents passed the final empty-repository implementation- readiness gate on 2026-07-18. This local Phase 0 implementation candidate contains four private, pure packages: the canonical identity and boundary codec; the runtime topology and semantic port contracts; the private conformance harness; and the pure authority kernel. It does not establish landing, acceptance, activation, or release. No provider, adapter, storage or ledger implementation, controller process, transport, CLI, MCP surface, credential, real external effect, or public package is authorized or implemented. The greenfield delivery track remains authoritative, while archive material remains non-governing.
The retired implementation generation is preserved at
archive/jig-v0-pre-greenfield-2026-07-18, which resolves to commit
1731251d866b15b63131a0c3c580e7b563226cf3. Its recovery and story-scoped lookup rules are in the
generation archive manifest. It is
historical reference only and does not govern the next implementation.
| Area | Purpose |
|---|---|
| Product | Audience, promise, workflows, guarantees, and boundaries. |
| Approved redesign | Authorities, runtime units, ports, lifecycle, data, failure, operations, and conformance contracts. |
| Greenfield delivery track | Documentation-only sequencing, story contracts, fixed inventories, and independent review expectations. |
| Readiness gate | Exact reviewed subject, review coverage, findings, delegated choices, checks, and archive authorization. |
| Archive | Historical provenance and the retired-generation recovery manifest. |
Requires Node >=22 and pnpm >=11.9.0.
pnpm install --frozen-lockfile
pnpm checkThe check runs lint, formatting, documentation-link, delivery-track, repository-structure,
typecheck, package-boundary, runtime-topology, and test validation. Run pnpm delivery:check for
the focused delivery validator and its mutation tests.
The next owner-authorized implementation session must use the active greenfield delivery track and:
- resolve the approved delivery package
P = Q + durable R identifier + PASSand verify that package's landing on the target ref; when landing produced a different commit, verify the authoritative landing-equivalence record without treating the landed commit as the reviewed subject; - resolve the target ref's then-current commit/tree as the story execution base rather than treating immutable planning provenance as a rolling base;
- independently verify the exact external owner-ratification/activation record binding
P, planning/authority provenance, target scope, selected realization tuple, and expiry/revocation; - freeze the final-verification posture, policy-selected required check-class set, verification
configuration/environment, and candidate binding for independent implementation review; after
Accepted,deterministicrequires a passing, subject-matchingEV-CHECK-OBSERVATIONfor every required class and the complete set insideFinalizingbefore any target-changing Operation, whilenoneis an explicit no-op. Those unchanged-binding observations are authorized continuation evidence, not a new review subject; drift requires a fresh tuple and review; - treat
docs/product/anddocs/redesign/design/as governing; - use the readiness gate's 44 commitment routes, R1–R7 obligations, and constrained-choice register as planning inputs; and
- avoid the retired generation unless an already-specified active story needs a bounded lookup.
The four private packages above are local-candidate implementation only; they do not establish a landed or activated story and do not authorize downstream implementation. The active track remains a planning stop line until a story's merged predecessors, exact evidence, delegated-choice gate, external activation, and independent review requirements are met.
MIT License. See LICENSE.