docs: document Gall's five undocumented vane scries - #276
Open
sigilante wants to merge 1 commit into
Open
Conversation
Against urbit/docs.urbit.org@08026c84b2. The Gall vane scry arm (sys/vane/gall.hoon:2897-3160) dispatches 15 cares; gall/scry.md documented 10. Adding the missing five, in alphabetical position: %b blocked moves (map term (qeu blocked-move)) gall.hoon:2936 %g flubbed apps (jug ship app=term) gall.hoon:2984 %h halted apps (jug app=term [ship =duct]) gall.hoon:2993 %i flub ducts (map ship duct) gall.hoon:3001 %y live agents (map term yoke) gall.hoon:3138 Types and descriptions are taken from the `+$ state` definition (gall.hoon:78-90) and its own field comments. %y filters the yoke map to live agents only. %g, %h and %i are the observability surface for the Ames/Gall backpressure protocol: %g is which agents have refused a $plea, %h is which flows are halted because an agent is missing or suspended, and %i is the duct used to send %flub notifications per ship. VERIFICATION NOTE, stated plainly: unlike the other PRs in this series, these five were NOT verified by live scry. Each attempt to type a vane-scry path ended up wedging the dojo's line editor -- the `$` path element did not survive send-keys or paste-buffer, and repeated attempts left the input line unusable until the ship was restarted. Rather than keep fighting the terminal or, worse, write a plausible-looking example I had not actually run, the entries are documented from the dispatch conditions and return marks in gall.hoon, which are unambiguous, and the example blocks show only the invocation, not a fabricated product. %y is exercised indirectly and does work: the +vats generator scries it (`.^(yokes ... %gy ...)`) on every run, and +vats was verified live in an earlier PR in this series. Deliberately avoided a cross-PR link: an earlier draft pointed %g at [%halt](../ames/tasks.md#halt), but that anchor is added by the Ames backpressure PR and does not exist on master. If these merged in the wrong order the link would break, so the reference is prose instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 4, 2026
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.
Eleventh PR from the audit against
urbit/urbit@08026c84b2. The Gall vane scry arm (sys/vane/gall.hoon:2897-3160) dispatches 15 cares;gall/scry.mddocumented 10.Companion PRs: #266, #267, #268, #269, #270, #271, #272, #273, #274, #275.
The five missing cares
%b(map term (qeu blocked-move))gall.hoon:2936%g(jug ship app=term)gall.hoon:2984%h(jug app=term [ship =duct])gall.hoon:2993%i(map ship duct)gall.hoon:3001%y(map term yoke)gall.hoon:3138Types and descriptions come from the
+$ statedefinition (gall.hoon:78-90) and its own field comments.%yfilters the yoke map to live agents only.%g,%hand%iare the observability surface for the Ames/Gall backpressure protocol documented in #269:%gis which agents have refused a$plea,%his which flows are halted because an agent is missing or suspended, and%iis the duct used to send%flubnotifications per ship.Verification note — please read
Unlike the other PRs in this series, these five were not verified by live scry. Every attempt to type a vane-scry path wedged the dojo's line editor: the
$path element did not survivesend-keysorpaste-buffer, and repeated attempts left the input line unusable until the ship was restarted.Rather than keep fighting the terminal — or, worse, write a plausible-looking example product I had not actually observed — the entries are documented from the dispatch conditions and return marks in
gall.hoon, which are unambiguous, and the example blocks show only the invocation, not a fabricated output. Every other PR in this series contains real captured output; these deliberately do not, and I would rather say so than have a reviewer assume otherwise.%yis exercised indirectly and does work: the+vatsgenerator scries it (.^(yokes ... %gy ...)) on every run, and+vatswas verified live in #268.Avoided a cross-PR link
An earlier draft pointed
%gat[%halt](../ames/tasks.md#halt), but that anchor is added by #269 and does not exist onmaster. If these merged in the wrong order the link would break, so the reference is prose instead.Test-merged against the ten open companion PRs — all clean.
🤖 Generated with Claude Code