Owned core · Zig · Deterministic execution
Built around the durable decision.
Mira's foundation will adopt the actual TigerBeetle Zig implementation into a Mira-owned project. The full resource model will run on that integrated storage, replication and execution foundation.
An ordered transaction stream
Within a replication group, admitted commands enter one ordered stream. The deterministic command kernel applies resource rules and atomic business groups against that order. Batching amortizes transport, replication and storage costs while preserving each request's identity.
Replica count is a durability and availability choice, not a throughput multiplier. Replicas hold the same history; they are not horizontal shards.
Storage designed with the protocol
The adoption plan retains TigerBeetle's actual journal, superblocks, checkpoints, Grid block storage, repair, scrubbing and LSM machinery. These components will be refactored with their dependencies and tests while preserving their algorithms and behavior.
Corrupt blocks, torn writes, exhausted disks and crashes during recovery belong in the failure model. Repair and state synchronization depend on surviving trustworthy copies.
VSR, recovery and replicated time
The foundation includes the actual Viewstamped Replication implementation, batching, client sessions, clocks, simulation and operational tooling. It will be integrated into Mira's own build, with upstream accounting and echo workloads retained as internal regression fixtures.
Normal operation, view changes, quorum intersections and state transfer have distinct contracts. Clock uncertainty and stale leadership must not create resource authority. Progress depends on the stated network, storage, quorum and time assumptions.
Boundaries stay visible
The baseline is crash and recovery tolerance with modeled corruption. It is not Byzantine consensus. A logical lease also cannot stop a physical machine by itself: an external system must enforce fencing.
Mira's resource semantics, authorization, business idempotency, calendars, cross-domain bundles and offline rights require their own implementation and evidence. Foundation acceptance includes inherited recovery, upgrade, client and operational paths; resource-level guarantees are completed in Phase 2.
Help shape what comes next.
Talk to the founder