Joy
Interface specification: Joy CLI. Node integration and acceptance are owned by cyber's worker contract. Both specs distinguish the implemented baseline from the planned interface.
Joy compiles and executes Trident programs on nox. Supported public programs can also produce a Zheng execution certificate whose input, output, program and reduction count are checked by the verifier.
Public proving uses zheng-nox-public-execution-v2: Zheng derives the global
CCS from the canonical program, authenticates the complete public witness and
checks all constraints and public coordinates. This certificate discloses the
witness and has linear verification cost. Verification does not run nox.
--secret automatically selects joy-nox-ccs-triton7-zk-v3; --zk selects it
explicitly. Trisha supplies Triton7's randomized STARK for an independently
regenerated checker of the exact Zheng CCS. Private columns are absent from
the artifact. Checked atom calls, fixed-shape branches, arithmetic, words,
structural hashes and equality are supported within the bounded relation.
Inactive branch errors do not invalidate a successful selected path.
--state state.json loads a bounded authenticated public BBG certificate.
Public state proofs use joy-nox-public-state-execution-v1; each actual lookup
binds namespace, index, returned value and all four root limbs to execution.
Private state proving (--state ... --zk or --secret) selects cells inside
the proved CCS, hiding query coordinates. It requires all ten public namespaces
and at most2048 total fields; it does not expose private BBG dimensions.
Dynamic continuations and variable branch shapes remain unsupported. Budgets must cover the authenticated cost of the selected execution path. The relation also bounds every possible cost below the field modulus. See Zheng's exact contract and proof backend/state contract.
Public inputs bind as [p_last [... [p_first 0]]]. Proof verification checks
requested --claim and --input-values; --budget bounds the certificate's
budget. Self-contained artifacts carry the program; passing a source/bundle
with --proof also checks that the certificate belongs to that program.
Target ownership
joy describe --target nox exports the installed versioned Trident target
package as JSON without executing user code. cyber currently names the same
nox adapter; it does not advertise a network SDK or deployment.
Machine constants come from the canonical nox contract through Trident;
Joy owns runtime capabilities, including the
execution and proof restrictions. No checkout or ambient machine descriptor
is needed. State files are authenticated certificates, not live network sync.
Legacy trace statements
Old zheng-hypernova-tensor-merkle-v2 artifacts do not establish execution
or emitted values. Inspection requires an explicit opt-in:
This mode labels execution/output unverified and refuses requested IO, state
or secret constraints. There is no automatic proof downgrade. The old
prove_zheng/verify_zheng/verify_artifact library methods remain legacy
statement APIs; the Prover/Verifier traits use execution certificates.
Build and status
Use coordinated sibling checkouts of Trident, Trisha, Zheng, Lens, BBG, nox, Hemera and strata. Bootstrap pinned Triton dependencies first:
The coordinated CPU release is Joy 0.5.0, Trident 0.3.0 and Trisha 0.3.0. Download native macOS, Linux and Windows archives or use the coordinated source archive. The supported public/private/state paths pass on all six native targets and in the complete cross-platform proof exchange. Broader nox execution and live node/database integration remain roadmap work. See release notes and the published validation report. State commitment v2 changes all BBG roots; regenerate certificates and proofs.
Cyber License: Don't trust. Don't fear. Don't beg.