# Compliance Restriction Configurator

> Translate regulatory purchasing requirements into an auditable supplier-block and category-restriction configuration for enterprise procurement accounts. Use this skill whenever the user mentions federal supplier blocking, Section 889, government funding purchase restrictions, education account category blocks, restricted categories, procurement compliance policy, or asks to convert a policy document into account configuration, even if they only paste the policy text.

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

---


# Compliance Restriction Configurator

Converts a written compliance mandate into a machine-applied restriction set: blocked suppliers, blocked categories, allowed exceptions, and an audit trail that maps every restriction back to its clause.

## Inputs

- Policy source: regulation citation, internal policy doc, or contract clause text
- Account vertical: federal, state/local, education, healthcare
- Current catalog taxonomy (category tree export)

Synthetic policy and taxonomy fixtures in `references/fixtures/`.

## Workflow

1. Extract restriction intents from the policy text: entity-based blocks (named suppliers, country-of-origin), category-based blocks (alcohol, weapons, adult content, IT hardware classes), and conditional restrictions (allowed with approval workflow).
2. Map each intent to the catalog taxonomy using `scripts/map_restrictions.py`. Ambiguous mappings go to a review queue, never silently applied.
3. Emit the configuration artifact (JSON) plus a human-readable audit table: restriction, source clause, taxonomy nodes affected, and review status.
4. Generate the verification script: a set of probe searches that must return zero results post-application.

## Output format

`config.json` (restriction set), `## Audit Table`, `## Verification Probes`, `## Review Queue` (ambiguous mappings requiring human sign-off).

## Guardrails

- No restriction ships without a source clause. Compliance configuration without provenance fails audit.
- Over-blocking is a failure mode equal to under-blocking. The review queue exists to prevent both.