no identity configured

Compliance register

Two obligations attach the moment a name is stored, and this product stores names: the literature search reads public authorship, so a person is profiled here without ever having been asked. Nothing on this screen is a fixture. The register is not scoped to a workspace either, and deliberately so, because the duty is owed to the person: someone profiled for three customers is owed one notice rather than three.

Sign-in is not configured on this deployment

No identity provider is selected, so there is no user to make this request as. That is a statement about how this deployment is configured and not about your account: nothing here says you are signed out, because nothing here knows who you are.

Behind this: the Article 14 register with its due dates and overdue count, and the objection record held against each person this product has ingested. No request was sent, so nothing on this screen is a guess about whether the service is up.

Development setup

To see it on a development stack, run scripts/dev_up.sh and start the web application with AUTH_PROVIDER=e2e and SKEPSIS_DEMO_TOKEN_A set to the token that script mints. The harness refuses to load in a production build, or against an API that is not on this machine.

Absent by decision

A name, an employer or an address beside any row OQ-05The register identifies a person by the record id this product ingested them under. The notice itself is the only artefact that would ever carry an address, and this build holds none, which is the whole of what OQ-36 is holding up.
A delete control on an objection or a notice DATA-10The stop is a flag on the row rather than a deletion, because no retention or erasure rule is stated for this product, and removing the record would remove the evidence that processing stopped.
A response-time target, an SLA or a countdown on an objection rule 0.5No review deadline is stated anywhere in the requirements, so none is coded. A valid objection stops processing at once rather than being held against a deadline this build invented.
A conflict-of-interest field, and any payment, claims or prescribing column NP-09, OQ-28Neither exists on any screen in this product, and neither exists on the types behind them, so no register here can grow one later by accident.

Every requirement OQ-36 is holding, and what account settings will never hold.

Compliance register

Sign-in is not configured on this deployment

Development setup

Absent by decision

A name, an employer or an address beside any row OQ-05The register identifies a person by the record id this product ingested them under. The notice itself is the only artefact that would ever carry an address, and this build holds none, which is the whole of what OQ-36 is holding up.
A delete control on an objection or a notice DATA-10The stop is a flag on the row rather than a deletion, because no retention or erasure rule is stated for this product, and removing the record would remove the evidence that processing stopped.
A response-time target, an SLA or a countdown on an objection rule 0.5No review deadline is stated anywhere in the requirements, so none is coded. A valid objection stops processing at once rather than being held against a deadline this build invented.
A conflict-of-interest field, and any payment, claims or prescribing column NP-09, OQ-28Neither exists on any screen in this product, and neither exists on the types behind them, so no register here can grow one later by accident.

Every requirement OQ-36 is holding, and what account settings will never hold.