Skip to content

Re-validate detect → verify → publish path before re-enabling auto-publish #30

Description

@Ap6pack

Closed

The core of this issue — auditing the over-convicting detection that inflated MALICIOUS from 476 to a verified 184 — is done and merged:

The remaining items (detector novelty logic, human-approval gate, end-to-end dry-run mode) only matter if the daily auto-publish workflow (threat-research.yml) is re-enabled — and it is currently paused (manual dispatch only). If/when we decide to turn autonomous publishing back on, we'll open a fresh issue scoped to exactly what that needs, rather than keep this one open indefinitely.

Detection quality and enumeration coverage are tracked separately (enumeration fixes in #34/#36).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions