Understand planned Waputu-only inventory rooms

Before you start

This is a planned Inventory-package capability, not an active room-creation instruction.
State reporting obligations remain governed by the adopted rules and your authorized state workflow.

Where to click

Illustrated navigation sequence. Exact controls appear in the numbered instructions below.

1Read the roadmap
The proposed local-room layer describes shelves, bins or staging areas managed in Waputu.
2Separate identifiers
A local room will have its own internal identity. It must never be presented as a newly created NMS2S room.
3Understand moves
A local allocation changes the operational overlay. A state room movement changes NMS2S and requires a separate authorized, audited action.
4Preserve totals
The proposed design keeps local allocations bounded by the source lot quantity and identifies unallocated or conflicting quantities.
5Request the workflow
Use Contact to describe the actual rooms, staff tasks and reporting requirements. The feature requires entitlement and integration acceptance before release.

What success looks like

The local-room concept is understood as an operational overlay, not a substitute for state tracking.

You cannot create a room today

The feature is planned and not yet enabled.

A local room is being used as state evidence

Stop and review the workflow. Internal location naming must not imply a state movement occurred.

Send the workspace, facility, safe error and approximate time. Keep credentials and private activation links out of the message.