Skip to content

🐛 Activity Monitor: no consistent way to settle a human gate — scattered needs-human chevron, sentinel chip, Approve and Let hive decide; sentinel and decision gates have no verb #17504

Closed

Description

@clubanderson

Maintainer screenshots 2026-11-10 01:44Z / 01:50Z (full board): "I don't see a consistent way to settle each of these using the UI. Some are confusing, others have no controls to take action, others have too many."

Observed across six rows:

Spec (decision made):

  1. Exactly ONE human-gate control per gated row: a segmented pill 👤 Needs human · <reasons> (reasons review / decision / sentinel / hold, comma-separated when stacked; hover = the reviewer's question or the sentinel rule; the question stays in the expander line too).
  2. Verbs fixed per reason — review: Approve · Request changes… · Let hive decide; decision: Decide… (question pre-filled) · Approve as-is · Let hive decide; sentinel: Confirm safe · Let hive decide; hold: Release hold · Let hive decide. Stacked reasons union, de-duplicated, max 3 visible + … overflow menu.
  3. "Needs human" / "Held · …" / "Sentinel alert · needs human" are never chevron words; the lit chevron is the real stage with the amber ham-human-gated outline as the bar's only cue (one lit chevron, 🐛 Activity Monitor: exactly one lit stage chevron per row #17337).
  4. Secondary rows of a shared PR render no gate and no needs-human chevron; the decision pending on #N chip links to the primary row (✨ Activity Monitor: shared-PR issues group under their primary row #17333 anchoring).
  5. In-app modals/toasts only; optimistic settling… until the next snapshot. A sentinel confirmation endpoint next to the approve path, audited.
  6. Docs: a "Settling a human gate" table (reason → verbs → what gets posted); tests per reason's verb set, stacking, secondary suppression, and fixtures for 🌱 dco: waive the #17464 squash whose sign-off address differs from its author #17481 and crux Clickable repo cards + fix vanishing intensity gauge #140.

Related: #17334, #17337, #17457, #17453, #17327.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 10, 2026
  2. github-actions commented on Nov 10, 2026

    @github-actions
    Contributor

    @clubanderson this issue was closed by @hivecommons-hive[bot] as completed.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

  3. added a commit that references this issue on Nov 10, 2026
    a725f11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions