Build the foundations. Earn the release.

The dependency sequence

Each phase has a complete acceptance gate. Specifications, testing, security and performance obligations accompany the work throughout; completing a component does not complete its phase.

1. 01

   The complete inherited foundation

   Research and formal work underway · Engine adoption pending
2. 02

   The complete Mira resource database

   Formal work underway · Implementation follows foundation acceptance
3. Next

   Enterprise offerings

   Planned · Begins after the entire database is complete

01 / Complete the inherited foundation

Adopt the actual TigerBeetle Zig implementation into Mira's own project. Preserve behavior while refactoring the required implementation, dependencies, generators, clients, tests and operational tooling together.

• Storage, LSM, VSR, checkpoints, repair, networking, clocks and bounded runtime machinery.
• C ABI, language bindings, build and packaging, regression fixtures, simulation, fuzzing and native recovery and upgrade evidence.
• Mira-owned integration, source traceability and independent behavior checks across the complete foundation.

02 / Complete the resource database

Implement all six resource families on the accepted foundation: exclusive identities, reusable capacity, interval capacity, consumable inventory, concurrent occupancy and replenishing budgets.

• Atomic bundles, claims, leases, fencing, exact units, calendars and recurrence.
• Tenant authorization and delegation, durable business identities, domains, movement, cross-domain atomicity and bounded offline rights.
• Queries, history, events, receipts, retention, public APIs, SDKs, security, operations and whole-system qualification.

After the database / Enterprise offerings

Enterprise work begins after the entire database is complete. Planned offerings span commercial self-hosting, managed cloud, private deployment, fleet administration, identity, key management, governance, resilience, observability, integrations, commercial administration, support, professional services and partners.

Packaging, entitlements, pricing and support commitments have not been established. These are planned offerings, with no enterprise service available yet.

Release is an evidence gate

Launch requires completed implementation evidence, full-system fault campaigns, reproducible performance results, reviewed compatibility, signed release artifacts and tested operating procedures.

There is no fixed public launch date. Each implementation phase closes when its required machine evidence is complete for the exact inputs.