Roadmap

What’s shipped, what’s next

Status is derived from the workflow manuals (Implemented / Partial / Upcoming) plus a short “Next” plan for the next demo cycle.

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

In Progress

Partial (6)
  • Item Availability
  • Org Member Invitation Missing: 2 items
  • Return > Validate > Clear Missing: 1 items
  • Return > Validate > Damaged Missing: 1 items
  • Return > Validate > Lost Missing: 1 items
  • User Invitation & Provisioning

Next

Upcoming (4)

From Manuals

  • Damaged > Escalate > Dropped
  • Damaged > Escalate > Judged
  • Lost > Escalate > Dropped
  • Lost > Escalate > Judged

Plan (Next Demo Cycle)

Demo hardening

  • Finalize permission edge-cases across owner/org-head/employee flows.
  • Stabilize charts and analytics rendering across roles.
  • Reduce remaining UI inconsistencies (mobile/tablet).

Auditability & logs

  • Expand log visibility with clearer filters and retention indicators.
  • Surface missing audit fields referenced in manuals/specs.

Manual coverage parity

  • Close gaps for manuals marked Partial.
  • Promote Upcoming manuals into implemented flows as features ship.