Enumerate a blueprint's declared taps on the public surface (introspect view or refusal roster) #333
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fieldtest of the #310 cycle (fold-selector, 2026-07-24): no public surface enumerates a blueprint's DECLARED taps, so the undeclared-tap refusal (
--tap nope=mean) is not self-actionable — the author must reopen the blueprint JSON to learn the valid tap names. Direction: either agraph introspect --taps <bp.json>view (name + source wire + kind), or the refusal enumerating the blueprint's declared taps the way the fold refusal enumerates its roster (C29 idiom: refusals name the closed set they check against).refs #310
Derived decision (tracker harvest, 2026-07-24)
Direction: extend the undeclared-tap refusal to enumerate the blueprint's declared taps — the C29 idiom (a refusal names the closed set it checks against) — instead of a new
graph introspect --tapsview. Rationale: the refusal path is where the missing knowledge actually bites, it needs no new surface or flag, and it matches how the unknown-fold refusal already behaves. A dedicated introspect view stays available as a follow-up if authoring (rather than recovery) turns out to need one.