Jig

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.

Status

The approved product and redesign documents passed the final empty-repository implementation- readiness gate on 2026-07-18. Phase 0 is merged and landed as 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. That landing does not activate Phase 1 or establish acceptance 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 and its active delivery-track stop line remains in force, 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.

Governing documents

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.

Repository checks

Requires Node >=22 and pnpm >=11.9.0.

pnpm install --frozen-lockfile
pnpm check

The check is a single Turbo run: every workspace package builds, lints, and tests itself, and the tools/repo-guard package runs narrow structure, package-boundary, documentation-link, and formatting gates. Runtime topology stays with the package that implements it. Use pnpm check:affected to restrict the same graph to what the current branch changed — a local convenience whose selection is only as complete as the comparison base, so pnpm check stays the gate. Phase orchestration runs pnpm delivery:check before consuming track.json; it is not part of the universal repository check.

Next implementation prerequisites

An explicit current request from Arye Kogan or a named delegate to implement a named phase or story is sufficient implementation authorization. The session must use the active greenfield delivery track and:

1. record the authorized phase/story scope and explicit constraints in an external operational ledger when delivery begins;
2. resolve the target ref's then-current commit/tree as the story execution base rather than treating immutable planning provenance as a rolling base;
3. verify current product/design/track authority, declared predecessor containment, and any selected bounded DR-* realization;
4. freeze the exact committed candidate, final-verification posture, policy-selected required check-class set, verification configuration/environment, and candidate binding for independent implementation review; after Accepted, deterministic requires a passing, subject-matching EV-CHECK-OBSERVATION for every required class and the complete set inside Finalizing before any target-changing Operation, while none is an explicit no-op. Those unchanged-binding observations are authorized continuation evidence, not a new review subject; drift requires a fresh tuple and review;
5. treat docs/product/ and docs/redesign/design/ as governing;
6. use the readiness gate's 44 commitment routes, R1–R7 obligations, and constrained-choice register as planning inputs; and
7. avoid the retired generation unless an already-specified active story needs a bounded lookup.

The four landed private packages establish only Phase 0; they do not themselves request Phase 1 implementation. Once the owner explicitly requests Phase 1, delivery does not require a separate delivery-package qualification, delivery-surface digest approval, external activation issue, or landed-commit equivalence record. Merged predecessors, exact candidate evidence, delegated-choice gates, provider qualification, independent review, required CI, and Definition of Ready/Done remain mandatory.

License

MIT License. See LICENSE.