Cyber Lab Validation

Priority: P0 (CRITICAL)

Validate approved security claims against disposable synthetic fixtures in isolated environments under host-enforced gates; operational attacks are prohibited, and host-enforced safety boundaries remain mandatory.

Structure

cyber-lab-validation/
├── SKILL.md
└── references/
    ├── scenario-schema.md
    ├── execution-gate.md
    ├── validation-record.md
    └── scenario-catalog.md (evaluation-owned)

Workflow

1. Select and validate versioned scenario against scenario schema; verify single claim, disposable target, and seven-family alignment.
2. Select declared mode: isolated-lab-validation or active defensive-verification.
3. Preflight action gate: verify ActionRequest, action allowlist, finite limits, and host capability proofs via execution gate.
4. Dispatch bounded action; capture ActionReceipt bound to gate and correlation key (run_id, attempt_id, test_id).
5. Capture ObservationRecord within defined window; enforce transitive binding chain to ActionReceipt.
6. On pre-dispatch failure, set blocked; on running drift, control loss, or operator stop, halt dispatch immediately and record partial receipts.
7. Execute surviving cleanup plan; record CleanupResult state (verified-clean, residual, unverified, not-applicable).
8. Adjudicate finding status (confirmed, suspected, blocked, not-tested, false-positive) and defensive outcome (blocked, prevented, detected, responded, telemetry-gap).

Rules