Prashanthvara 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
- 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).
- Map each intent to the catalog taxonomy using
scripts/map_restrictions.py. Ambiguous mappings go to a review queue, never silently applied. - Emit the configuration artifact (JSON) plus a human-readable audit table: restriction, source clause, taxonomy nodes affected, and review status.
- 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.