MAP-ADV-001: Adversarial Evidence Documentation Protocol

I. Purpose

Define a commit-safe documentation contract for adversarial engagement runs on v2 so evidence is always captured without storing raw runtime payloads.

II. Scope

This protocol applies to adversarial Phase 1 engagement runs and their documentation outputs under artifacts/adversarial/ and docs/TRACKING/.

III. Authority Level

Informative. This document is subordinate to SOP-DOC-000 and must not override invariant or constitutional directives.

IV. Dependencies

• docs/STANDARD_OPERATING_PROCEDURES/SOP-DOC-000_DOCUMENTATION_STANDARD.md
• scripts/adversarial/build_evidence_bundle.py

V. Documentation Rule

All adversarial runs must produce and preserve sanitized evidence artifacts for documentation. Raw engagement payload files are operational artifacts and should remain out of version control.

VI. Required Sanitized Artifacts

Generated under artifacts/adversarial/sanitized/<run_id>/:

• summary.json
• scorecard_sanitized.md
• manifest.json

Generated by:

• python3 scripts/adversarial/build_evidence_bundle.py --run-id <run_id>

VII. Allowed Content

Sanitized artifacts may include:

• check names
• PASS/FAIL status
• violation counts
• run id
• generation timestamp
• code SHA
• checksums for sanitized files

VIII. Disallowed Content

Do not commit:

• raw violations.jsonl
• raw runtime finding payload details with reproduction traces
• session-level context fields
• actor-identifying or account-identifying data
• environment or connection values

IX. Operational Workflow

1. Run adversarial phase (scripts/adversarial/run_phase1.sh).
2. Build evidence bundle (scripts/adversarial/build_evidence_bundle.py --run-id <run_id>).
3. Use sanitized outputs for tracker/docs updates.
4. Keep raw operational artifacts local/untracked.

X. Amendment

Revisions to this document must increment version, update effective date, and remain consistent with SOP-DOC-000.