Roadmap

What’s shipped, what’s next

Functional manuals indicate our progress, while the Approved Build Order establishes our rigorous, foundation-first execution pipeline.

Done

Implemented (9)

Consumables RegistrationRegister a `Consumable` as an item type and record its initial stock as a `ConsumableBatch`. The number of active `Consumables` is controlled by the `Owner` via `AccountConfig`. Ea
Deactivate UserDeactivate `User` because:
Equipment RegistrationThis is to setup `Equipment` as one of the `Item Classification`. Number of Active `Equipment` controlled by `Owner` are set in `AccountConfig`
Location RegistrationThis is to setup `Location` as one of the `Item Classification`. Number of Active `Location` controlled by `Owner` are set in `AccountConfig`
Organization SetupThis is to set up `Organization` to establish resource boundaries. The number of active `Organization` controlled by `Owner` is defined in `AccountConfig`
Reactivate UserReactivate `User` because:
Request > Cancel FlowFrom Employee Request to Cancel of the Item
Request > Reject FlowFrom Employee Request Reject of the Item
Request > Approval > Allocation > Return FlowFrom Employee Request to Return of the Item

Partial (6)

Upcoming (4)

From Manuals

Approved build order

Talara MVP enforces a strict security & telemetry foundation first sequence to prevent mock analytics.

Approved MVP Build Sequence

Reconciled against docs/road map.md. We sequence security, telemetry, and traceability before feature scaling to ensure high reliability.

🔒

Phase 0 Specifications

Prevent leaking sensitive diagnostic data before observability expands. We secure the environment so no diagnostics are exposed in the wild.