Rover: Cleared for Duty
Rover is live. The boundary came with it.
Issue 05 introduced a support operator with tested components and work still ahead. This issue records the other side of that line: Rover v1 completed acceptance and now runs inside Watchtower as an authenticated, human-governed support workspace.
The working route
Rover Home, approved knowledge guidance, and the technician Reviews console all passed through the authenticated Watchtower gateway. The requester route now carries the environment’s configured path instead of falling back to a generic one—the final-mile defect caught and corrected during acceptance.
Access fails where it should
Technician access passed. Self-Service access to the technician path was denied with 403, and anonymous access was denied with 401. Rover did not flatten the service desk into one universal view; it kept requester and technician work in their assigned lanes.
Recovery is part of live
AI01 restart recovery and durable state passed. The release was packaged for both the reusable product and the Watchtower deployment, then aligned across the supporting environment. A service that only works before the first restart was never the finish line.
What stayed outside Rover’s authority
The model provider remains disabled in the released path. Ticket writes stay narrowly scoped, and acceptance did not mutate accounts, permissions, workstations, or ticket records. Rover guides, records, and prepares the handoff; people still own consequential decisions.
Rover moved from tested components to a deployed support workspace with authentication, role separation, reviewed knowledge, technician oversight, and recovery evidence attached.
Rover and the Watchtower are original Twilight Technology engineering-storytelling concepts. Original artwork; no DC affiliation or endorsement.