licensing-record-review

• SKILL.mdcore · 8,532 bytes

# Licensing Record Review

## Core Workflow

1. Read the prompt, the answer template, and the current environment instructions before querying data.
2. Extract the target identifiers, review date or release boundary, required queue size, ordering requirements, allowed enum values, and summary fields from the prompt/template.
3. Query only authorized data sources for target records and directly related records. Prefer targeted joins or filters over broad dumps, and keep distractor rows out unless the task's matching rules explicitly allow close-address or successor matches.
4. Build a trace table before writing JSON: one row per target application, license, or location with policy thresholds, current records, adverse history, evidence gaps, risk tier, and summary membership.
5. Emit only JSON that matches the provided template. Use exactly the requested keys, allowed enum values, empty arrays instead of nulls, required ordering, and summary counts that reconcile with item-level decisions.

## Contractor Eligibility Batches

Use the current contractor policy row for the application's trade/class. Parse policy details for minimum bond, insurance, years of experience, required endorsement, and serious-violation blocking rules.