The latency model for one touchpoint: banded distributions
(fast/slow/timeout) with deterministic band selection. Latency is
VIRTUAL time — the world advances its clock, never wall time.
The partial-write marker the runtime injects into a response when a
partial-write storm fires: the write half-landed, honest consumers
must detect and repair it.
Whether the application was compiled with an explicit real-backend
define. Used only to surface conflicts with kSimulationMode loudly
(FR-012); on its own it has no simulation semantics.
Append a hash-chained world evidence entry to the feature's cycle
log (<featureDir>/tdd/cycle-log.md), schema-1 chain format — the
same format the run driver, doctor, and fixture commitment already
parse. kind is world-cert / world-run; hash is the entry's
chain hash (the world hash for certification, the run digest for
runs).
The simulation family for a declared dependency name: known
certified families resolve by name; everything else is generic
(corpus-served, contract-pinned).
Scaffold a world manifest for scenario from the declared
dependency rows: touchpoints (parsed contracts), the time model
(seed), certified default latency bands per touchpoint, a default
failure-storm schedule (the issue's storm classes for the declared
touchpoint shapes), the golden corpus per method, and a default
behavior program exercising every method once.
The storm that fires for touchpoint's method on call
callIndex (1-based), or null when the schedule is silent there.
A storm with a null method matches every method of the
touchpoint; a method-scoped storm fires only on its method (how
mid-flow storms stay surgical). When several storms overlap, the
LAST declared wins (later entries refine earlier ones — the
manifest reads as an ordered schedule).
Thrown when code running under NetworkIsolationGuard attempts to
open a real socket. Extends Error (not Exception) so catch (e)
blocks that are not explicitly isolating network access do not
silently swallow the certification failure.
Raised at simulation boot when an entity's committed fixtures are
missing or corrupt. The message always names the affected entity and
the fixture file path (FR-009).
Raised when the manifest's behavior program references an unknown
touchpoint or method — the world refuses to run a program that does
not match its declared contracts (never a silent no-op).
