Every Compliance Crucible tool is built around a defined authority packet. The packet sets the regulatory scope, citation set, output boundaries, and limitations that travel with every record the tool produces.
Each tool is paired with a defined regulatory scope — a scope object that names the regulatory baseline, citation set, included/excluded scenarios, and the limitations statement the tool must carry on every output.
When a regulatory baseline changes, the scope is revised, the tool is updated, and a new version is released. The change is visible in every output's status panel.
| Tool | CC-EVAL-CS-002 · v2.1 |
| Regulatory Scope | Federal OSHA · 29 CFR 1926 Subpart AA |
| Jurisdiction | Federal OSHA Baseline |
| Coverage | Construction · Permit-Required Confined Spaces |
| Output Boundary | Documentation framework only |
| Excluded | Entry authorization, compliance determination, legal advice, engineering, training |
Field Package, Auditor Report, and JSON export all carry the active regulatory reference, tool version, generation timestamp, and the limitations block.
Public product pages, member dashboard cards, and checkout screens repeat the same scope and limitation language — no surprises.
Tool versions and User Agreement revisions are tracked in versioned registries. Acceptance records cite the active revision at the time of subscriber assent.