Skip to content

Read-only reduction of the default-on guard findings table from the 2026-10-13 to 2026-10-29 session event log #11299

Closed

Description

@kyle-sexton

Refs: #3756

Summary

This is the read-only reduction that the 2026-10-01 owner decision on #3756 says to file as its own item. It reads the per-session hook event log (source: envelope lines) from this repository's sessions dated 2026-10-12T21:53Z to 2026-10-29T23:59Z: 447 sessions and 1,117,580 lines, kept on the operator's machine at .work/3756-session-snapshot/. From them it builds the findings table for every guard that was default-on through the whole collection window. block-hook-bypass is only referenced, because #3721 owns it.

The reduction itself is done: the 2026-10-30 host run posted the table on #3756. Two things remain, both outside this item: the owner adjudicates each block on #3756, and every non-keep disposition becomes its own PR with the numbers in its body.

Acceptance criteria

  • The findings table is posted on guardrails: grade every default-on guard's precision from the per-session hook event log (ADR 0003) #3756 with these columns: guard, sessions observed, fires, blocks, and the quoted subject per block. Verdict and Disposition are left blank. Guards added during the window, guards off by default and non-guard hooks are listed as excluded.
  • The table states its date range and defines its counts. Sessions observed counts the distinct sessions in which the guard ran at least once. Fires counts every recorded invocation. Blocks counts invocations with status: blocked.
  • The subjects are public-safe. Each one is <tool>:<first command word>, and none needed redacting.

Deleting the snapshot is tracked on #3756, not here.

Work class

work-class: read-only. Nothing in the repository changes.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 30, 2026
  2. kyle-sexton commented on Oct 30, 2026

    @kyle-sexton
    MemberAuthor

    Done: the 2026-10-30 host run posted the findings table on #3756. The owner's verdicts and any non-keep dispositions continue on #3756.

  3. github-actions commented on Oct 30, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: read-only
    Basis: automated intake triage; a maintainer confirms or changes it.

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: none

    I understood this as a read-only reduction of the hook event log, from 2026-10-12 to 2026-10-29, into a per-guard findings table. The table is posted on #3756. The body says all three acceptance criteria are already checked off, and nothing in the repository changes. The adjudication of each block and any follow-up PRs are tracked on #3756. I found no duplicates among the open issues. I didn't check the posted table myself, so a maintainer can confirm it before closing.

    Automated triage. A maintainer reviews it.

  4. added and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 30, 2026
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

    No labels
    No labels

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions