36 lines
1.0 KiB
Markdown
36 lines
1.0 KiB
Markdown
[Reviewed]
|
|
# ADR-0006: Fixed logical ticks
|
|
|
|
## Status
|
|
|
|
Logical ticks adopted for proof; 50,000 microseconds is experimental.
|
|
|
|
## Context
|
|
|
|
Replay needs a clock independent of machine speed; accelerated simulation must not sleep.
|
|
|
|
## Decision
|
|
|
|
Explicit whole ticks; serialize tick/quantum. Host pacing uses bounded catch-up without increasing dt. Future ecology uses integer cadence and declared transfer boundaries.
|
|
|
|
## Alternatives Considered
|
|
|
|
Variable dt couples results to scheduling; one rate across every scale wastes work; physical substeps need fixed versioned schedules.
|
|
|
|
## Benefits
|
|
|
|
Repeatable ordering, accelerated tests and clear recovery point.
|
|
|
|
## Costs
|
|
|
|
Overload/input-cutoff policy and possible substeps.
|
|
|
|
## Risks
|
|
|
|
Catch-up loops, counter overflow, reduction order, accidental offline progression.
|
|
|
|
## Consequences
|
|
|
|
Reject tick overflow. Clocks and metric timing never drive biological decisions. Compare 10/20/30/60Hz at client/network gates. Rate changes require version review; no offline controlled-organism catch-up.
|
|
|