Calculated from published rules

See how the facts
change the obligation.

Every page below represents a different legal result, deadline, required action, or evidence path produced by a maintained ProseID schema. Choose the legal task, inspect a scenario, then run the same rules with your own facts.

920distinct rule paths
18published schemas
1:1schema-version binding
Freeto inspect
01US
105rule paths

CCPA request-handling scenarios

Tracks intake, verification, acknowledgement, extension, disposition, downstream action, confirmation, and response timing for California delete, correct, know, sale-or-sharing opt-out, and sensitive-information limit requests. ADMT rights with a 1 January 2027 compliance date are outside this version.

Version 1.0.0Explore scenarios →
02US
120rule paths

California pay-data reporting scenarios

Determines whether a private employer must file a Payroll Employee Report, a Labor Contractor Employee Report, or both, and records the annual deadline, California workforce data, certification, and contractor-data controls.

Version 2026.07.26Explore scenarios →
03US
7rule paths

CPSC Section 15(b) reporting scenarios

Determines whether a manufacturer, importer, distributor, or retailer must report product-safety information to CPSC within 24 hours and records the investigation, initial report, and supporting product information.

Version 2026.07.26Explore scenarios →
04US
11rule paths

EPCRA annual inventory and Tier II request scenarios

Determines whether federal or state and Tribal hazardous-chemical inventory reporting is triggered and separately tracks the annual Tier I or state-required Tier II filing, requested Tier II information, an LEPC-requested SDS, Section 311 updates, recipients, and supporting threshold record.

Version 2026.07.26Explore scenarios →
05EU
100rule paths

EU withdrawal-right scenarios

Records an online consumer contract, the applicable national implementation, withdrawal window and exceptions, a consumer's withdrawal request, and the resulting refund obligation.

Version 2026.06.19Explore scenarios →
06EU
140rule paths

EU internal-report handling scenarios

Tracks the EU Article 9 baseline for securely handling an internal whistleblowing report: acknowledgement within seven days, assignment to an impartial handler, diligent follow-up, and reasoned feedback within three months.

Version 2026.07.24Explore scenarios →
07US
20rule paths

FDA food-facility registration scenarios

Determines whether a domestic or foreign food facility must register with FDA, renew during the even-year window, update changed information, cancel and re-register after ownership changes, or document an exemption.

Version 2026.07.26Explore scenarios →
08US
7rule paths

FTC notification-event scenarios

Determines whether a covered financial institution's security event enters the FTC's 500-consumer notification track and records the required report content and timing.

Version 1.0.0Explore scenarios →
09EEA
12rule paths

GDPR breach-notification scenarios

A controller must notify the supervisory authority of a personal-data breach **without undue delay and within 72 hours** of becoming aware, *unless* the breach is **unlikely to risk** individuals' rights. The notification must state the **nature, categories and rough number affected, likely consequences, and measures taken**; a late filing must carry **reasons for the delay**.

Version 2025.01.01Explore scenarios →
10US
38rule paths

HIPAA breach-notification scenarios

Documents the threshold assessment for a suspected breach of unsecured protected health information and records the individual, HHS, media, or covered-entity notices that follow.

Version 1.0.0Explore scenarios →
11US
34rule paths

OSHA immediate-reporting scenarios

Determines whether a workplace outcome falls into the federal OSHA immediate-reporting track and records the facts, report status, and deadline outcome.

Version 1.0.0Explore scenarios →
12US
14rule paths

PHMSA hazardous-material incident reporting scenarios

Determines whether a transportation incident requires a National Response Center call within 12 hours, DOT Form F 5800.1 within 30 days, an FAA copy, a one-year update, and two-year retention.

Version 2026.07.26Explore scenarios →
13US
44rule paths

SEC Item 1.05 disclosure scenarios

Tracks the materiality determination, Form 8-K Item 1.05 content, filing deadline, permitted Attorney General or FCC-rule delay, and amendment status for a material cybersecurity incident.

Version 1.0.0Explore scenarios →
14SE
8rule paths

Swedish chemical-product register scenarios

Determines whether a Swedish Chemicals Agency activity report, product notification, annual quantity report, PFAS or nanomaterial review, or separate pesticide authorization action is due.

Version 2026.07.26Explore scenarios →
15SE
120rule paths

Swedish Cybersecurity Act scenarios

Records the documented applicability decision for Sweden's Cybersecurity Act, then captures a potentially significant incident and tracks the applicable 24-hour initial notice, 24- or 72-hour incident notification, and final or status report.

Version 2026.01.15Explore scenarios →
16SE
9rule paths

Swedish posted-worker reporting scenarios

Determines the immediate reporting, contact-person, proof-delivery, recipient-notice, update, and long-term-posting actions for a worker sent to perform a service in Sweden.

Version 2026.07.26Explore scenarios →
17SE
11rule paths

Swedish serious workplace-event scenarios

Determines whether a workplace event requires prompt notice to the Swedish Work Environment Authority and records the event information, timing, acknowledgement, and follow-up investigation.

Version 2026.07.26Explore scenarios →
18SE
120rule paths

Swedish staff-register duty on business premises scenarios

Determines whether a non-construction business premises must keep a personalliggare and records the daily-entry, availability, family-exemption, mixed-operation, and retention controls.

Version 2026.07.26Explore scenarios →

Why these pages differ

Inputs are not swapped into boilerplate.

Each URL has a distinct semantic fingerprint: its calculated outcome, activated rules, required actions, deadline path, and evidence requirements. Input combinations that produce the same fingerprint collapse into one canonical page.