The logic is simple on purpose. The data stays editable on purpose too.

CompWise uses a small decision engine backed by per-state records. Each state record carries a requirement basis, an employee threshold or trigger note, owner-election flags, carve-out categories, an as-of date, and official source links. That means the logic can stay stable while the data changes over time.

The tool does not try to recreate every statutory exception inside one giant rules file. Instead, it uses conservative branches. Clear triggers can return Required. Owner-only structures with no employees can return Likely Exempt. Edge cases and carve-outs land in Verify so the user has a reason to check the underlying state source before they skip coverage.

This tradeoff is deliberate. Compliance tools are more durable when they explain how to think, show what assumptions they used, and leave room for source-backed updates instead of burying fragile magic numbers inside the calculation code.