FLUXFLUX
  • Introduction
  • Quickstart
  • Two Specs, One Substrate
  • The Six Families
  • The FLUID Seam
  • Deterministic & Governed
  • Runtime & Evidence
  • Anatomy
  • The Nineteen Kinds
  • Versions
  • Changelog
  • JSON Schema 0.5.1
  • UI Hints 0.5.1
  • Enforcement Contract 0.5.0
  • Bundle Manifest 0.5.0
  • Overview
  • Tutorial
  • How-to guides
  • Reference
  • Explanation
  • Command line
  • Error codes
  • Accuracy program
  • The vNext Plan
  • The Nine RFCs
  • RFC-10 (proposed)
  • Conformance Profiles
Examples
What's New
FLUID
GitHub
  • Introduction
  • Quickstart
  • Two Specs, One Substrate
  • The Six Families
  • The FLUID Seam
  • Deterministic & Governed
  • Runtime & Evidence
  • Anatomy
  • The Nineteen Kinds
  • Versions
  • Changelog
  • JSON Schema 0.5.1
  • UI Hints 0.5.1
  • Enforcement Contract 0.5.0
  • Bundle Manifest 0.5.0
  • Overview
  • Tutorial
  • How-to guides
  • Reference
  • Explanation
  • Command line
  • Error codes
  • Accuracy program
  • The vNext Plan
  • The Nine RFCs
  • RFC-10 (proposed)
  • Conformance Profiles
Examples
What's New
FLUID
GitHub
  • FLUX Simulation Engine
  • Tutorial
    • First evidence pack in five minutes
  • How-to guides
    • Model your customers
    • Add a journey
    • Use the FLUID seam
    • Calibrate from aggregates: declare a scorecard
    • Ship with evidence
  • Reference
    • Command line
      • fluxsim init
      • fluxsim validate
      • fluxsim plan
      • fluxsim apply
      • fluxsim run
      • fluxsim verify
      • fluxsim ship
      • fluxsim replay
      • fluxsim calibrate
      • fluxsim accuracy
      • fluxsim gate
      • fluxsim expr
      • fluxsim describe
      • fluxsim plugins
      • fluxsim explain
    • Error codes
    • Python API
    • Schemas
  • Explanation
    • The six-step loop
    • Determinism and the seed tree
    • The FLUID seam
    • The evidence pack, and what it does not claim
  • Accuracy program

    • The accuracy program: design
    • Accuracy report

fluxsim ship

Run the fidelity gate over every emit that declares a fidelity block, and only if none is withheld, pack the bundle and the run into one evidence archive with its in-toto statements.

Synopsis

fluxsim ship [options] <bundle>

Examples

# pack the evidence archive
fluxsim ship ./bundle --run-id de72fa4b22711c52 -o ./out

# a bundle that declares a fidelity block needs the slice it is measured against
fluxsim ship ./bundle --run-id de72fa4b22711c52 -o ./out \
    --committed-slice payment_recovery_moment=file:///data/slice.ndjson

Arguments

ArgumentDescription
bundlepath to the FLUX bundle directory

Options

OptionValueDescription
--run-idRUN_IDthe run id to act on (as reported by fluxsim plan/fluxsim run) (required)
-o, --out-dirOUT_DIRdirectory the evidence archive and its statements are written to (required)
--committed-sliceEXPOSE_ID=file://PATHthe committed real-data slice one expose's fidelity check is measured against, as EXPOSE_ID=file://PATH; repeatable, once per expose; the file holds one JSON object per line, keyed by the expose's contract column names (e.g. {"subscriber_id": "s-1", "amount": "12.50"})
--signing-keySIGNING_KEYfile holding a 32-byte ed25519 seed (raw or hex) to sign fidelity records with; without it the record is signed by a per-invocation key and says so
--trust-keyPATHfile holding the 32-byte raw ed25519 PUBLIC key (raw or hex -- the publicKey a fidelity record prints) the gate checks the record's signature against; without it the record is checked against the public half of the key that signed it and says it is self-attested
--state-dirSTATE_DIRrun-state directory (default: ./.flux)
-j, --jsonemit machine-readable JSON

All commands

Last Updated: 11/12/26, 10:41 PM
Prev
fluxsim verify
Next
fluxsim replay