Repository navigation
Docs/fleet v0.6.0 - #43
Merged
Merged
Conversation
timothy-weston
force-pushed
the
docs/fleet-v0.6.0
branch
from
September 9, 2026 11:09
b9b5901 to
90271e3
Compare
timothy-weston
marked this pull request as ready for review
September 10, 2026 09:44
timothy-weston
force-pushed
the
docs/fleet-v0.6.0
branch
from
September 11, 2026 08:16
7297c2f to
f4e3c7b
Compare
timothy-weston
added a commit
that referenced
this pull request
Sep 11, 2026
…t reconcile The first classification named Quick Dispatch and was too narrow; writing down that it was wrong, and on what evidence, is what stops the next person re-deriving the narrow version. Also names the three absolute Send-to-Robot statements on the v0.6.0 branch that need the same qualification once it lands.
timothy-weston
added a commit
that referenced
this pull request
Sep 11, 2026
Stacking the limitations layer on the v0.6.0 docs so the overlap between them is resolved once, deliberately, instead of at merge time. #43 owns the supported workflow and had already absorbed most of the corrections this branch catalogued; what it superseded was withdrawn here, and its two remaining absolute claims about Send to Robot were qualified.
Documents what v0.6.0 changed in how Fleet is operated: who does what, the two standard workflows, that activation is not residency, the transient dispatch contract and its two entry points, the refusals Fleet answers with, and how a failed run is closed. Stacked on the pre-v0.6.0 cleanup, whose corrected badge vocabulary and run-condition matrix this builds on rather than restates.
First audit pass over the new material. The page claimed behaviour the interface does not offer — a retry door removed before release, a pause exempt from the E-Stop, a configurable action on losing the link, pause-owner reasons never served to a client, and a location correction reaching a robot that already holds the mission — attributed the run conditions and the E-Stop release to the wrong roles, and called the product Fleet, which is our own word rather than the one customers see.
9587dae expanded the index's feature teasers into capability documentation, and every audit since went to the sub-pages instead — so the E-Stop authority rule was stated three times on the index and nowhere on the page documenting the button, the lease definition and the detection-type counts were maintained in two places, and two claims survived only on the index. Each teaser now gives the page's purpose, the reason to open it and the link; the facts sit with the feature they belong to.
Second pass, on three things an operator would have found contradicted in front of them: a moved saved location raises the per-mission "location changed" badge rather than the low-opacity "needs review" note about the map shifting under a mission, robot:estop is a site-scoped permission that the tenant Auditor does not hold, and the resume control is disabled while the E-Stop is active rather than always yours to press.
…-056 rules ADR-056 makes an explicit Send the only thing that establishes residency, and the page asserted that as fact. Production does not hold the line: two publish paths compose from the armed set without narrowing to what the robot already holds, so an Active mission that was never sent can arrive as a side effect, and a dispatch re-sends held missions from their current saved state rather than leaving them untouched. Send to Robot is now described as the deliberate workflow rather than the only possibility, and a scheduled run is named as the resident work it is; the customer-facing exception belongs to the current-limitations branch.
timothy-weston
force-pushed
the
docs/fleet-v0.6.0
branch
from
September 11, 2026 10:18
f4e3c7b to
4de02f2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.