# MinerOps v0.3: Operations

## Status

Planning document. The version label and candidate scope are provisional and do
not override the current version summary in `README.md` or phase ordering in
`docs/ROADMAP.md`.

## Goal

Add safe operational control for individual miners and groups while preserving
guardrails and auditability.

## Candidate Scope

- [ ] Miner move workflow
- [ ] Maintenance mode
- [ ] Bulk tagging and location updates
- [ ] Safe reboot and shutdown
- [ ] Scheduled actions
- [ ] Staggering and cooldown controls
- [ ] Action history
- [ ] Partial-failure reporting
- [ ] Role-based action permissions

This scope spans the roadmap's Operations and Fleet Control phases. Inventory,
identity, maintenance context, and monitoring dependencies remain governed by
`docs/ROADMAP.md`.

The repository already contains early-stage legacy movement, command,
scheduling, and action-status behavior. Unchecked items mean the modular,
permissioned, fully validated product workflow remains planned; they do not
claim that no related code exists.

## Definition of Done

Actions are explicit, permissioned, audited, safety-limited, recoverable, and
tested for authorization, concurrency, retries, and partial failure.