— INDUSTRIES
Your industry's controls, compiled into the gate.
Maker–checker is the default control language of business software: a junior operator prepares a high-risk change, a qualified approver checks it, and only then does the system submit. Vertical Approval Policy Packs turn your industry's control patterns into executable rules for AI-driven operations — installed, compiled against your app's operation manifest, and enforced before anything mutates state.
TEN VERTICAL PACKS, V1 CATALOG
01
Banking, fintech & treasury
04
Retail, QSR & e-commerce
05
Manufacturing & industrial
06
Logistics, supply chain & 3PL
07
Procurement, AP & shared services
09
Government & public sector
Each pack contains real, executable policies — operation keys, maker and checker roles, approval thresholds, evidence requirements, separation-of-duty constraints, postconditions, and standards mappings. Not prose.
GROUNDED IN PUBLISHED STANDARDS
NIST SP 800-53
Access control, audit & accountability, least privilege, separation of duty
FDIC & FFIEC guidance
Segregation of duties, joint custody, two-person approval, exception reporting
HIPAA & 21 CFR Part 11
Audit controls, authority checks, sequence checks, accountable signatures
PCI DSS, COSO & NIST AI RMF
Need-to-know access, control activities, AI risk-governance lifecycle
Packs use these standards as explicit design anchors. Installing a pack does not, by itself, make you legally compliant — and we won't tell you otherwise.
HOW A PACK ENFORCES
01 INSTALL
Pick the pack for your vertical — roles, thresholds, and constraints included.
02 COMPILE
The pack binds to your application's operation manifest — abstract controls become concrete rules over your real operations.
03 EVALUATE
Every proposed AI-driven operation is checked before your application mutates state: maker role, checker role, threshold, separation of duty.
04 EVIDENCE
Decisions, approvals, and postconditions land in the same signed, hash-chained record as everything else Lore governs.