Continuous compliance execution
Compliance, continuously executed.
Sentience watches regulatory sources for change, determines what applies to your entities, executes the work the change creates, detects the operational conditions that create exposure, and preserves the proof of all of it.
One system, running continuously, instead of a quarterly scramble.
Designed to watch every US state and the District of Columbia.
Highlighted tiles are an illustrative sweep, not verified coverage.
R0 — No jurisdiction verified
No deployment reported a measurement to this build, so the lowest rung is shown.
Why Sentience exists
Compliance doesn't stop.
Nothing in this sequence waits for a compliance calendar. Each step is already happening while the last one is still being read.
- 01Regulations changeAgencies amend, supersede and re-publish. The change is public the moment it lands, and nobody sends you a copy.
- 02Obligations emergeAn amendment two states away becomes work you owe — but only if someone determines that it applies to you.
- 03Deadlines moveA revised effective date silently invalidates the plan built around the old one.
- 04Operations create riskA licence lapses, a threshold is crossed, a filing window opens against an entity nobody was tracking.
- 05Discovery comes too lateTraditional compliance finds all of it during the audit — after the exposure has already accrued.
The Sentience operating model
Four movements of one continuous loop.
These are not four features. They are the order in which the system works, and each one is only possible because the one before it recorded what it did.
- 01WATCHKnow what changed. Know what matters.Retain every version of a source, detect the difference, determine applicability, and record the obligation that results.
- 02FILESentience executes the work.Prepare the filing from the obligation, validate it against policy and authority, submit it, and close the obligation against the receipt.
- 03FLAGCatch problems while they can still be fixed.Watch operational signals for the conditions that create compliance exposure, and route each one to a disposition.
- 04REPORTThe proof already exists.Every determination, action and receipt was written to a tamper-evident chain as it happened. The report reads it.
WATCH → FILE → FLAG → REPORT → WATCH. The loop does not have an end state.
WATCH
Know what changed. Know what matters.
A change is only useful once someone has decided whether it reaches you. Sentience follows recorded impact, not resemblance: a determination that merely cites the version that changed is reported as unassessed, never as clear.
- 01Regulatory SourceOriginal bytes retained, version hashed
- 02Change DetectedDiff between two retained versions
- 03Applicability DeterminationRule version, inputs, citation, timestamp
- 04ObligationOwner, due date, lineage back to the source
Governed review queue
The console reads this queue from the product API. It is read-only by design: nothing in the browser opens, closes or reclassifies a review item, because no governed path exists to take that decision in a browser.
- TX00:12 agoThreshold amended, effective date advanced7 TAC §83.3001 — Licensing thresholds Renew lending licence — Texas OCCCApplies
FILE
Sentience executes the work.
An obligation is not a reminder. Sentience prepares the filing it implies, validates it against policy and the authority held for that jurisdiction, and carries it through to a receipt that closes the obligation.
- DueThe obligation exists with its lineage, owner and date.Measured from the product · Implemented
- PreparedThe payload is built from the obligation and bound to an approval.Measured from the product · Implemented
- ValidatedPolicy, standing and per-jurisdiction authority are checked before anything leaves.Measured from the product · Implemented
- FiledTransmission is held by the authority gate. Connectors refuse to transmit and say so, rather than pretending to file.Planned capability
- AcceptedThe regulator receipt closes the obligation and enters the evidence chain.Planned capability
Why the last two stages are still marked planned
Nothing external executes without authority. Until per-jurisdiction filing authority is recorded and the gate is closed, the connectors refuse the write and return a stated refusal. That refusal is a control working, not a defect — and it is the reason this page will not show you a production receipt that does not exist.
FLAG
Catch problems while they can still be fixed.
Regulatory text is only half of the exposure. The other half is what the business is doing right now — and it is visible long before it becomes a finding.
- 01Operational SignalEntity, licence, threshold and filing telemetry
- 02Anomaly DetectedSeverity scored against the recorded baseline
- 03Compliance ConsequenceThe obligation or authority the signal puts at risk
- 04ActionRouted to a named disposition, with the decision recorded
Signals under watch
Illustrative product view · Demo data- High
Licence register: Ohio entity not renewed 41 days before expiry
Anomaly
Renewal window opened with no prepared filing
Compliance consequence
Licence lapse would suspend origination in Ohio
Action
Obligation raised and routed to the licensing owner
- High
Transaction volume in Georgia crossed the registration threshold
Anomaly
Threshold crossing without a nexus re-evaluation
Compliance consequence
Unregistered activity in a jurisdiction with a filing duty
Action
Nexus re-evaluation queued for review
- Medium
Evidence upload for Q2 attestation missing two artefacts
Anomaly
Incomplete custody chain for a closed obligation
Compliance consequence
The obligation would not survive an audit read
Action
Obligation reopened pending artefacts
REPORT
The proof already exists.
Audit readiness is not a project that starts when the auditor calls. Every step above wrote its evidence to a tamper-evident, tenant-scoped chain at the moment it happened. The report is a read of that chain.
- Citations
- Decisions
- Actions
- Filing receipts
- Timestamps
- Evidence chain
Output
Audit report
Each event is hashed over the previous one, so a record that changed after the fact fails verification instead of quietly replacing the truth.
Command centre
Now the numbers mean something.
This is the operator console, shown last on purpose. By this point every panel on it is a view of a step you have already seen.
Operator console
Illustrative product view · Demo dataChanges watched
1,284
Source versions retained and diffed
Filings prepared
96
Payloads built and validated
Anomalies flagged
23
Signals routed to a disposition
Reports generated
14
Reads of the evidence chain
Recent activity
- WATCHTX 7 TAC §83.3001 — new version retained, diff recorded09:42:11
- FILERenewal payload prepared for Florida OFR, awaiting validation09:41:58
- FLAGOhio licence renewal window opened with no prepared filing09:40:02
- REPORTEvidence chain verified for 1,284 events, no breaks09:38:47
- WATCHCA 10 CCR §1422 — applicability determined for 3 entities09:36:20
50-state watch map
Highlighted tiles carry a change in this demonstration. Verified coverage is reported separately, below.
Upcoming deadlines
- Annual report — schedule B amendmentCA · Preparedin 3 days
- Money services renewalFL · Validatedin 9 days
- Lending licence renewalTX · Duein 14 days
- Surety bond confirmationIL · Duein 22 days
Measured, not demonstrated
Measured from the product · GET /api/v1/coverageThe product reports its own coverage rung from verified rules. A jurisdiction counts once a rule has been verified against a cited source version — not once a source has been read.
- Coverage rung
- R0
- No jurisdiction verified
- Jurisdictions verified
- 0
- Verified against a cited source version
- Measurement
- Not measured
- No deployment reported a measurement to this build
One system continuously watching what changed, determining what it means, executing what must happen, and proving that it happened.
Sentience is in pilot with a small number of organisations. Bring the jurisdictions and obligations you already struggle to track, and we will run them.