Skip to content

docs: add verification/publication failure handling guardrails #220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
viviresunarte wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add verification/publication failure handling guardrails #220

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,3 +227,20 @@ If you want to include Agent Scan results in your own project or registry, pleas
## Changelog

See [CHANGELOG.md](CHANGELOG.md).

## Verification/Publication Failure Handling (Operational Safety)

When integrating scanners into autonomous publishing workflows, treat these as **incident-class failures**:

- Verification challenge not completed within TTL
- Published artifact cannot be re-fetched/confirmed (existence mismatch)
- API success response without verifiable state change

Recommended guardrails:

1. Fail closed after one unresolved verification failure.
2. Require re-fetch confirmation before marking success.
3. Emit run IDs and evidence links in incident reports.
4. Do not continue to secondary actions when verification is pending.

These controls reduce false-positive success signals and moderation/suspension risk.