Skip to content

feat: add integrity monitoring for illegitimate task success (#113) - #150

Draft
askmy-stack wants to merge 1 commit into
mainfrom
cursor/integrity-monitoring-c2a5
Draft

askmy-stack wants to merge 1 commit into
mainfrom
cursor/integrity-monitoring-c2a5

Conversation

@askmy-stack

Copy link
Copy Markdown
Owner

Summary

Implements #113 — integrity monitoring that separates functional task success from legitimate success.

Changes

  • New tool_semantics.integrity module with deterministic rules for:
    • eval/harness file modification
    • workflow bypass / out-of-order steps
    • direct state manipulation
    • validation disabled
    • hardcoded expected/golden output
    • unexpected privileged actions
    • constraint avoidance
  • Per-finding confidence (confirmed / likely / probable / unclear)
  • Status line like Tests PASS / Integrity FAIL
  • Markdown ## INTEGRITY section via render_integrity_markdown / append_integrity_section
  • Docs: docs/integrity.md (+ link from docs/probes.md)

Integrity findings are informational relative to functional gates unless a policy later opts in.

Test plan

  • pytest tests/test_integrity.py
  • ruff check / mypy
  • CI green

Closes #113

Open in Web Open in Cursor 

Deterministic rules detect eval tampering, workflow bypass, direct state
mutation, disabled validation, hardcoded outputs, privileged actions, and
constraint avoidance. Findings are reported separately from functional pass/fail.

Co-authored-by: Abhinaysai Kamineni  <askmy-stack@users.noreply.github.com>

This branch has not been deployed

No deployments
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.

[P2] Integrity monitoring for illegitimate task success

2 participants