That single line is the discipline behind every Compliance Crucible tool. The goal is not to replace professional judgment — it is to give that judgment a clear, structured, defensible record. Every tool is built inside defined limits, and those limits travel with every record it produces.
On a real job, the work gets talked through. Hazards get considered. Decisions get made by the people responsible for making them. What too often goes missing is the record — the clear account of what was reviewed, what was selected, what was relied on, and what was preserved.
Compliance Crucible exists to close that gap without crossing a line. The competent person still recognizes the hazard. The employer still authorizes the work. The qualified person still makes the call. The tool's only job is to turn that real work into a record that holds up when someone asks, later, what actually happened.
That is what "authority-bounded" means: the authority to decide stays with the people and standards that hold it. The tool stays inside its lane — on purpose, by design, on every screen and every output.
A Compliance Crucible tool documents. It does not certify, approve, authorize, or declare anything safe.
It organizes what the employer enters. It does not perform inspection, measurement, or field hazard assessment.
It preserves the record behind a decision. It does not make the decision.
The judgment is yours. The record is ours to keep straight.
Each tool is paired with a defined regulatory scope: the regulatory baseline it is built on, the citation set it references, the scenarios it includes and excludes, and the limitations statement it 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 — so a record always shows the authority basis that was in effect when it was made.
The posture is a federal baseline. State Plan requirements, owner and client requirements, insurance specifications, and more protective local requirements must be independently verified by the employer for every project.
| 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 |
Every live tool carries a scope record like this one. The flagship Fatal Four framework, LOTO, and JHA/AHA each declare their own baseline and citation set the same way.
Most software hides its disclaimers. Here, the boundary is the product. A record that is honest about what it is — and what it is not — is worth more in a review than one that overclaims and collapses under a question.
Scope and limitation language isn't written once and buried. It's repeated wherever a record or a claim could be made — so there are no surprises between the sales page, the tool, and the output in an auditor's hands.
Field packages, review and auditor bundles, and JSON exports 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 — the same posture from first impression to locked record.
Tool versions and User Agreement revisions are tracked in versioned registries. Acceptance records cite the active revision in effect at the time of subscriber assent.
Founders Beta opens the full live tool set on one license. Every tool is built to this same discipline.