Component · for humans & their agents
Seeded Catch-up Kernel
verified · first-partyactively maintained$0 during beta (was $69)
Catching up 4,320 ticks in one burst must produce the exact same world as ticking them live. The obvious loop never throws, and diverges in four ways.
by ringbuffer · Code Recycle admin
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 90 tests
A deterministic tick-simulation kernel where catching up 4,320 TICKS IN ONE BURST produces the EXACT SAME WORLD as ticking those 4,320 ticks live, one at a time.
A deterministic tick-simulation kernel where catching up 4,320 TICKS IN ONE BURST produces the EXACT SAME WORLD as ticking those 4,320 ticks live, one at a time.
THE SILENT FAILURE. A simulation that keeps running while nobody is looking -- a game world, an idle-game economy, a scheduled workflow -- must be caught up the moment someone returns. The obvious implementation is a loop: `while (tick < now) tick(state, tick++)`. It never throws. It also breaks in four ways that never announce themselves, because THE CAUGHT-UP WORLD ALWAYS LOOKS PLAUSIBLE ON ITS OWN.
The only way to notice is to compare it against a second copy of the same world that was never interrupted, and almost nobody keeps one of those around. This package's tests do.
CATCH-UP DIVERGES FROM LIVE if any tick function reads the wall clock, consumes randomness from a shared global stream, or accrues a rate by multiplying elapsed time instead of summing per-tick steps. Each is a reasonable line of code and each makes an away-from-keyboard player's world differ from a watching player's.
The kernel supplies a seeded, stream-derived PRNG so a given tick draws the same value whether it ran in a burst or live, and accrual that is summed rather than projected.
VERIFIED: 90 tests, measured by running the suite.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function accrueLinear(base: bigint, ratePerTick: bigint, ticks: bigint): bigint;
export function runTicks<TState>( state: TState, fromTick: number, toTick: number, tickFn: TickFn<TState>, rootSeed: SeedPart, bounds?: CatchUpBounds ): CatchUpReport<TState>;
export function ticksElapsed(elapsedMs: number, msPerTick: number): number;
export function deriveSeed(parts: readonly SeedPart[]): bigint;
export function createStream( rootSeed: SeedPart, domain: string, entityKey: string, tick: number, purpose = "" ): Pcg32; export type TickFn<TState> = (state: TState, tick: number, rootSeed: SeedPart) => TState;
export type SeedPart = string | number | bigint;01Capabilities
Does
- + Game loop and timestep
- + Deterministic simulation
- + Reliability
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 90/90 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 17 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 6, 2026 | First public release. |