Helix StudioGenome IDE
← Docs
Helix CLI docs
Browse Helix CLI docs

Helix Hub internal FAQ (one page, v0.1.x)

What is Helix Hub

Helix Hub is the system of record for in silico decision approvals. It turns a decision into a portable proof bundle with signed receipts, and makes it verifiable offline later.

What Helix Hub is not

  1. Not a hosted control plane today
  2. Not a compute platform or pipeline runner
  3. Not an ELN, LIMS, or notebook replacement
  4. Not a biology claims engine

Verification proves computational provenance and integrity only, not biological truth.

What problem does it solve

Teams can produce outputs, but struggle to answer later, offline, to skeptics:

  1. What exactly was decided and approved
  2. Under which policy digest and backend fingerprint digest
  3. Which artifacts were part of the decision, and are the bytes unchanged
  4. Can a third party verify without trusting a service

How offline verification works in practice

  1. Bundles are content addressed with SHA256 digests and include receipts
  2. The verifier recomputes digests and verifies receipt signatures
  3. It fails closed and prints OK or FAIL (with reason lines)

Trust rule: do not trust HTML pages, trust the verifier output.

What is a receipt

A receipt is a signed JSON artifact that binds an approver identity to an approval surface digest and the bundle core digests. Receipts are the acceptance anchor downstream systems can require.

What makes Helix Hub different

  1. Contracts and digests are first class artifacts, not documentation
  2. Offline first verification and portable proof packs
  3. Deterministic exports that procurement can consume directly, decisions.csv and decisions.json

What the pilot delivers (artifact first)

  1. decisions.csv plus decisions.json for a chosen window, deterministic and schema versioned
  2. One zip proof bundle per approved decision, offline verifiable
  3. A README with exact verify commands

What we need from the customer

  1. Two to three representative in silico decisions to run end to end
  2. The reporting window, for example last quarter or pilot month
  3. Two approvers who will sign and approve, local first model in v0.1.x

What success looks like

  1. Anyone can verify one proof offline in about 30 seconds and see OK
  2. decisions.csv answers what was approved, under which policy and provenance, by whom, and where the proof is
  3. No tribal knowledge required to reconstruct decision context

30 second verify snippet (from the release asset)

unzip -q helix-hub-v0.1.1-sample-pilot-kit.zip -d kit
unzip -q kit/proofs/DECISION_SAMPLE.zip -d proof
(cd proof && helix hub verify bundle ./bundle --require-signatures)