Workloads we are designing for
Where getting the last unit right matters.
These scenarios guide Mira's contracts and future qualification. We are looking for people with real allocation problems to help test the assumptions.
Seats and rooms
Coordinate temporary holds, confirmed reservations and cancellations without selling the same availability twice.
A booking flow needs to distinguish a hold from a confirmed claim, settle an expired hold deterministically and recover the original result after a lost reply.
Inventory and orders
Reserve a basket together, consume stock once and make returns and corrections explicit.
An order that needs several items should succeed as one business bundle or leave all of them available. A retry of the same order must recover its prior outcome.
Compute capacity
Admit work against shared GPU, memory and worker capacity in one resource decision.
A job may need several kinds of capacity at once. Placement software chooses a candidate; Mira is intended to decide whether the proposed allocation is valid and durable.
Appointments
Reserve a person, a room and equipment over the same time window.
Interval rules must handle overlap, civil calendars and capacity changes. Multi-resource bundles connect those requirements to a single booking outcome.
Concurrent work
Keep active jobs within tenant limits and distinguish current owners from expired workers.
A crashed worker may resume after its lease expires. A downstream service must enforce the fencing token for Mira's logical ownership decision to protect physical work.
API and spending limits
Share an allowance across callers with accountable debits, retries and replenishment.
Budgets need exact units and explicit reset or refill rules. External billing and payment settlement remain separate integrations with their own failure boundaries.
Help shape what comes next.
Talk to the founder