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 run

Plan and apply in one call, then optionally verify and ship. Stops at the first stage that exits non-zero; the artifacts of every stage that did run are still returned under that stage's own key.

Synopsis

fluxsim run [options] <bundle>

Examples

# plan, apply, verify and ship in one command
fluxsim run ./bundle --verify --ship -o ./out

# plan and apply only
fluxsim run ./bundle

Arguments

ArgumentDescription
bundlepath to the FLUX bundle directory

Options

OptionValueDescription
--simulation-idSIMULATION_IDwhich Simulation document to resolve (default: the bundle's only one)
--zoneZONEdeclared run zone, for sovereignty checks
--verifyrun fluxsim verify on the applied run
--shiprun fluxsim ship on the applied run; requires -o
-o, --out-dirOUT_DIRdirectory the evidence archive and its statements are written to (required with --ship)
--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"})
--update-goldenrecord this run as the golden baseline (requires --reason)
--reasonREASONwhy the golden baseline is being updated
--allow-declared-baseline-driftexit 0 even when the bundle's declared golden.baselineDigest does not match this run's runDigest
--signing-keySIGNING_KEYfile holding a 32-byte ed25519 seed (raw or hex) to sign fidelity records with; without it ship signs with a per-invocation key attributable to nobody
--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 apply
Next
fluxsim verify