# Oag Evidence Closure

> Use when OAG simulation, scoreboard, coverage, assertion, formal, validation, gate, or completion evidence must be audited for freshness, traceability, proof strength, and closure readiness.

- Skill: `together2329/oag-evidence-closure` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add together2329/oag-evidence-closure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/together2329/oag-evidence-closure/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: together2329 (https://skillmd.com/u/together2329)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/together2329/oag-evidence-closure

---


# OAG Evidence Closure

Use this skill after implementation or verification artifacts exist. It checks
whether evidence can support closure; it does not treat passing tests as
closure by itself.

## Rules

- Evidence must trace through Requirement -> Obligation -> Contract ->
  Evidence -> Validation -> Decision.
- Scoreboard rows need scenario IDs, contract refs, independent
  `expected_source`, DUT-facing `observed_source`, and explicit pass/fail.
- Coverage contributes only when tied to passing checks and known contracts.
- Evidence added after gate PASS makes the gate stale.
- Gate review and completion decisions must use current artifact hashes.

## Commands

Run the closure audit set:

```bash
python3 .codex/scripts/oag_trace_graph_check.py --ip-dir <ip> --require-locked --json
python3 .codex/scripts/oag_verification_plan_check.py --ip-dir <ip> --require-locked --json
python3 .codex/scripts/oag_closure_check.py --ip-dir <ip> --json
python3 .codex/scripts/oag_cli.py call --json '{"tool":"oag.check","arguments":{"ip_dir":"<ip>"}}'
```

Before claiming completion:

```bash
python3 .codex/scripts/oag_cli.py call --json '{"tool":"oag.decide","arguments":{"ip_dir":"<ip>","action":"claim_complete","record_decision":true}}'
```

If any command blocks, report the blocker instead of claiming closure.