flybrain/services/flysim/Cargo.toml
acamilo 5defb6766d feat(session): fly-session, the SESSION-01 synthetic sequential transaction over flybus
The lockstep coordinator, its phase machine and a synthetic composition, as a new
workspace member. Every worker method is a Flybus RPC to an incarnation-pinned
service; the domain request ids and result caches of ipc-v1 section 5 sit in front of
every mutation.

- coordinator: the step-v1 section 3 transaction in order -- prepare every agent
  concurrently, run one executor per agent in sorted agent-id order, assemble all port
  controls in descriptor order, send exactly one Environment.Advance, evaluate the task
  once, commit every agent concurrently, and move the committed boundary only when all
  of them succeeded. Sequential, concurrent and reversed dispatch are selectable and
  must agree.
- phase: the section 2 machine as an explicit edge table, Paused and Failed included,
  with a committed-boundary predicate that gates pauses, captures and publication.
- clock: checked rational accumulation. A 60 Hz world with a 1 ms model tick runs
  16, 17, 17 ticks and comes back to a remainder of exactly zero.
- dedup: operation keys, the cached reply with its own artifact holds, CONFLICT,
  IN_PROGRESS, RESULT_EXPIRED, STALE_STEP, the lifecycle bound and Worker.Acknowledge.
- worker: the dispatch shell. Admission order and the result cache live here; the
  endpoint mutex is the worker's simulation lock, so one mutation runs at a time while
  Worker.Status answers from a separate cell.
- agent, environment, task: a fake model with an explicit seed and a mutation counter
  the tests read, a fixed readout stub, a counter arena that seals one immutable frame
  per boundary, a deterministic task and the identity executor.
- fly_session_types: the CONTRACT-01 domain types as a local stand-in, reconciled with
  the shared crate in a following commit.

Tests run twice, over the in-memory transport and over a Unix socket, through the same
router: the SESSION-01 acceptance bullets and every section 4 failure-injection row
that applies to this slice.
2026-09-22 11:46:57 +00:00

41 lines
1.2 KiB
TOML

[workspace]
resolver = "3"
members = [
"crates/flybrain-core",
"crates/flybrain-gb",
"crates/flybus",
"crates/fly-session",
"crates/flysim",
]
[workspace.package]
version = "0.1.1"
rust-version = "1.94"
license = "Apache-2.0"
publish = false
[workspace.dependencies]
base64 = "0.22"
cc = "1.4.2"
flate2 = "1"
cudarc = { version = "0.19.9", default-features = false, features = [
"std",
"driver",
"nvrtc",
"dynamic-loading",
"cuda-12080",
] }
indexmap = { version = "2", features = ["serde"] }
libm = "0.2"
ryu-js = "1"
serde = { version = "1.0.229", features = ["derive"] }
# `float_roundtrip` is not optional: without it serde_json's fast float parser can land 1 ulp off
# the value `JSON.parse` produces, which is enough to break a golden comparison.
serde_json = { version = "1.0.151", features = ["preserve_order", "float_roundtrip"] }
sha2 = "0.10.9"
# Bit-exactness with the TypeScript oracle is the whole point of this workspace, so the
# release profile must not be allowed to reassociate or contract float arithmetic. Rust does
# neither by default; these settings only pin the parts we do care about.
[profile.release]
debug = 1