Skip to content

Add privacy-safe automation failure signals - #6

Merged
abrichr merged 2 commits into
mainfrom
feat/privacy-safe-failure-signals
Jul 27, 2026
Merged

Add privacy-safe automation failure signals#6
abrichr merged 2 commits into
mainfrom
feat/privacy-safe-failure-signals

Conversation

@abrichr

@abrichr abrichr commented Jul 27, 2026

Copy link
Copy Markdown
Member

Outcome

  • adds a closed categorical openadapt.automation-failure-signal/v1 envelope for recurring runtime, drift, identity, actuation, effect, and over-halt discovery
  • derives the recurrence signature only from enums; application, tenant, workflow, step, origin, free text, inputs, screenshots, exception detail, and evidence never enter the API
  • groups aggregate events by the failure signature rather than the installation/user distinct ID
  • preserves DO_NOT_TRACK and existing telemetry opt-out semantics
  • explicitly keeps repair authorization and promotion outside telemetry

Verification

  • PYTHONPATH=src python -m pytest -q (122 passed)
  • PYTHONPATH=src python -m ruff check src tests
  • focused tests cover deterministic coarse signatures, fail-closed inputs, no installation ID egress, and opt-out

Boundary

This is the public mechanism/interface only. Cross-customer corpus, recurrence thresholds, ranking, and repair recipes remain private.

@abrichr
abrichr merged commit 76a5131 into main Jul 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant