enterprise-verify

Files (3)

• SKILL.md
• evals.json · evals/
• verification-report-template.md · references/

SKILL.md (first lines)

# Enterprise Verify

Final evidence gate for enterprise work.

## Required Background

- `verification-before-completion`

## Required Workflow

1. Run the agent-bound verify gate in [agent-stage-gates.md](../enterprise/references/agent-stage-gates.md) before accepting stage entry.
2. Run the full relevant verification commands now, not from memory.
3. Trace contract items or task claims to actual test evidence.
4. Classify the final diff as `required`, `enabling`, or `drift`.
5. Map every changed runtime file to code-level execution proof.
6. Trace every cross-layer behavior source-to-consumer, including edge cases from plan/contract.
7. Require live DB proof for schema/query/data claims and headless browser proof for UI/PDF/file/upload/rendered workflows.
8. Run the repo gate matrix locally before final signoff: PR body/delivery gate, no-new-mock guard, DB ownership gate, live-proof registry, and required CI mirrors.
9. Confirm review/forge evidence covers the current final diff, not a pre-pivot version.
10. Write the report using [verification-report-template.md](references/verification-report-template.md).
11. Record the verification report in the current agent session.
12. State the proof-scope verdict explicitly.
13. Only after fresh verification passes should work move to `enterprise-harness` for the final ship gate.

For non-trivial, schema-sensitive, tenant-sensitive, money/order/inventory/invoice, or UI workflow changes, verification should be multi-agent when available: split evidence freshness, schema/live DB proof, E2E/workflow trace, and headless browser/UI proof. If delegation is unavailable, run the same checks sequentially and label the limitation.

## Completion Reliability

- The verification document is the exit artifact. Write it before polishing optional prose or summaries.
- If time or context is tight, write a minimal but valid verification report first, then enrich it only if time remains.
- Update contract traceability statuses from `pending` to `passed` or `failed` based on the fresh evidence you just ran.
- If review already finished and fresh commands already ran in this session, move straight into the report and verdict. Do not reopen upstream design or discovery work.
- For bounded work, prefer a short, concrete report over a long narrative.

## Rules

- No `should work`
- No `probably fine`
- No completion claim without fresh output
- No `full-system` verdict unless the evidence actually covers the full system
- Do not invoke `enterprise-harness` as a substitute for fresh verification evidence
- No mocked DB proof for schema/query/data claims
- No GUI/manual browser proof as required evidence; UI verification must remain headless
- No stale review/forge proof after a CI or gate-driven code pivot
- No final claim while repo gate matrix commands are unrun, missing, or only assumed

From anotherben/agentic-governance, MIT.

More from anotherben/agentic-governance