feat: add return to service workflow
This commit is contained in:
1 parent
72ad19a071
commit
f2b736b08e
19 files changed
+2883
-46
No files matched your search
+5
-5
@@ -99,11 +99,11 @@ durable asset record. Repairs, maintenance, work orders, parts usage, equipment
|
||||
movement, testing, and return-to-service history become coherent operational
|
||||
records rather than disconnected actions.
|
||||
|
||||
The Begin Repair and read-only Repair Timeline workflows are complete. An
|
||||
authorized actor can open a repair against a durable miner UUID, record
|
||||
sequenced starting events, and move the miner into repair atomically. Authorized
|
||||
readers can inspect the repair and its ordered immutable events. Later repair
|
||||
lifecycle workflows remain planned.
|
||||
The Begin Repair, read-only Repair Timeline, and Return to Service workflows are
|
||||
complete. An authorized actor can open a repair against a durable miner UUID,
|
||||
record sequenced events, and move the miner into or out of repair atomically.
|
||||
Authorized readers can inspect the repair and its ordered immutable events.
|
||||
Later repair lifecycle workflows remain planned.
|
||||
|
||||
Technician experience is a priority. Responsive and QR-assisted workflows may
|
||||
reduce lookup and data-entry effort where they reinforce the same asset record.
|
||||
|
||||
Reference in new issue
Block a user