Compliance evidence packs
The pack auditors keep asking for.
Assemble audit evidence from your systems of record — the same structure every quarter, learned once, checked every time.
Anatomy of the task · illustrative workflow
Assemble audit evidence in the standard four-section structure.
Input
The audit request, access to the systems of record, and the pack structure your auditors already accept.
Required output
A complete evidence pack in the standard four-section structure, with every claim traceable to a system of record.
Evaluation
- Every required section is present and complete
- Each item traces to its system of record
- A reviewer accepts the pack without rework
Understand the workflow.
Compliance work repeats on a calendar. The same pack structure, the same systems of record, the same reviewer expectations — quarter after quarter. That regularity is exactly what a skill can capture.
Define the quality bar.
The pack either satisfies the auditor or it does not. Score completeness, traceability and structure against packs your team has already accepted — not against whether the prose sounds plausible.
Improve the route.
Start with the prompt and the pack template. Compare model routes on held-out requests. When the pattern's traffic justifies it, Operant writes the skill and proposes the route — gated, then ratified by you.
Keep frontier capability.
Keep the frontier model for novel audit requests, ambiguous evidence, and the cases where judgment about materiality changes the outcome.
Published evidence
See the comparison. Keep the context.
The published gate result covers this pattern: held-out exemplars replayed through the skill-and-smaller-model pair and judged for parity against the frontier baseline.
Read the results ->Who this fits
A task your team knows well.
A team that produces the same evidence pack on a schedule, has access to its systems of record, and can say what a reviewer accepts.
Bring a workload ->Another place to start · Coding sessions