Why does the customer dashboard exist?

So the organization carrying the policy can see continuous evidence of its own control state instead of assembling screenshots at audit or renewal time. A control can drift silently between periodic audits; the dashboard makes that drift a recorded, timestamped event and hands you receipts you can pass to an auditor or carrier who verifies them independently.

HATS Enterprise — Customer Dashboard

Q: What does the HATS customer dashboard record?

The dashboard is the customer-facing view of HATS RECORDING and MONITORING operational evidence over time: the live state of your security controls, the running attestation score, the event stream, and the portable receipts each check produces. It shows whether your declared controls kept operating — protection staying provably true — rather than a point-in-time compliance snapshot. It records evidence; it does not by itself render the independent verdict.

Q: When should I use HATS versus Verification, HICS, or Agent-008?

Use HATS when you need continuous operational evidence that your controls stayed in force over time. Use Verification when you need an independent verdict on an existing artifact — each receipt on this dashboard is checked by the external verifier, so the dashboard's monitoring is not itself verification. Use HICS when you want a maturity SCORE of your code or controls rather than evidence they ran. Use Agent-008 when you need to GOVERN an AI decision under attested authority rather than record that controls operated.

Q: Is the proof stream on this dashboard real verified evidence?

The dashboard includes a demonstration proof stream. Any client-generated proof shown here is sample data: it carries verified:false and sample:true and is never presented as an independently verified verdict, because a browser cannot itself render the external verifier's judgment. A real HATS receipt is verified by the independent verifier, offline; the sample entries only illustrate the shape and cadence of the evidence.

Q: How is the dashboard different from independent verification?

The dashboard records and monitors and emits receipts; the independent verifier renders the verdict on those receipts. HATS supplies the record; it does not verify itself. You can drop any real receipt into the public verifier and check it offline, which is the trust boundary that keeps monitoring honest.

Q: What can I do with a receipt from this dashboard?

Hand it to an auditor, a cyber carrier, or a counterparty. Each receipt is a portable artifact of the same shape whether a control passed or failed, so the recipient verifies the evidence themselves rather than trusting an attestation — turning compliance from a quarterly performance into a stream of independently checkable evidence.

Related · tier-1 reading. For the evidence chain that supports the claim, see Claims Evidence.

Overview

Live

✓

Fully Verified — Continuous Verification Active

All security controls are verified and continuously monitored. Sensitive data remains protected — even when accessed by AI systems or automated workflows.

Controls: —

Updated: 2m ago

Continuous since: 47 days

Verification Score (CRV)

Verification Score

▲ +4 pts (30d)

VERIFIED_A

Based on connected systems and observed control state

30-Day Trend

Protection Level

VERIFIED_A

Your organization meets all criteria for the highest verification level. All six security controls are currently verified.

Compliance Status

COMPLIANT

All compliance conditions are satisfied. Maintaining verified controls helps preserve full policy protection.

Policy Status

VERIFIED

Your verification status is current. Maintaining verified controls helps preserve full policy protection.

Last Verified

2m ago

Most recent verification proof recorded

0x7f3a...9b2c

Activity

Verification History

Each entry confirms your system state was verified at that time.

0 verifications

Your Protection Journey

You've improved your protection level by 38% since activation. This improvement is continuously verified.

Initial Tier

UNVERIFIED

➔

Current Tier

VERIFIED_A

127

Days Since Onboarding

+38

Score Improvement

1,247

Proofs Generated

99.4%

Compliance Uptime

Tier Change Timeline

Policyholder Operational Integrity Scores

Live cryptographically attested operational integrity scores for your insured entities. Insurance-weighted components drive premium calculations — computed from evidence, not questionnaires.

5 policyholders

Average Grade: B

3 alerts active

Last scan: 2 minutes ago

Entity	Grade	Score	Exposure	Gov. Continuity	Historical	Decision	Infra	Trend	Last Updated

Insurance-Weighted Operational Integrity Breakdown

Score History (30 days)

H33-74 Attestation

Operational Integrity Scores are continuously computed from cryptographically attested evidence. Score changes are reflected in premium adjustments within the current billing period. All scores are independently verifiable via h33.ai/verify. Below 70: automatic insurer notification, elevated approval required, governance escalation triggered.

What this dashboard is

The HATS customer dashboard is the organization's own view of HATS RECORDING and MONITORING operational evidence over time — the live state of your security controls, the running attestation score, and the portable receipts each check produces — so protection stays provably true across the policy period, not asserted once at audit. It records the evidence; it does not by itself render the independent verdict.

Why this dashboard exists

Compliance has traditionally meant assembling screenshots at audit or renewal time — a point-in-time snapshot that is stale the moment it is captured, with no record of what happened in between. The dashboard exists so the organization carrying the policy sees continuous evidence of its own control state: a control that drifts becomes a recorded, timestamped event, and every check yields a receipt you can hand to an auditor or carrier who verifies it independently. H33 keeps this as a distinct component because recording operational evidence over time is a different job from scoring maturity, rendering verdicts, or governing decisions.

When to use HATS — and when not

›Use HATS when you need continuous operational evidence that your controls stayed in force over time — reproduced from receipts, not asserted.
›Use Verification when you need an independent verdict on an existing artifact — each receipt here is checked by the external verifier. Do not treat this dashboard's monitoring as its own verification.
›Use HICS when you want a maturity score of your code or controls — how good they are — rather than operational evidence that they ran.
›Use Agent-008 when you need to govern an AI decision under attested authority; HATS only records that governed controls held.

Sample data note: the live proof stream on this dashboard is a demonstration. Any client-generated proof carries verified:false and sample:true and is never shown as an independently verified verdict — a real receipt is checked by the independent verifier, offline. Parent standard: the HATS standard — which defines the evidence record this dashboard displays and RECORDS operational evidence against. Related: HATS hub · Pricing · Carrier monitoring surface.

Frequently asked

What does the HATS customer dashboard record?

The live state of your security controls, the running attestation score, the event stream, and a portable receipt for each check — HATS RECORDING and MONITORING operational evidence over time, so protection stays provably true rather than snapshotted. It records evidence; it does not by itself render the independent verdict.

Why does the dashboard exist?

So you see continuous evidence of your own control state instead of assembling screenshots at audit or renewal. Drift becomes a recorded event, and every check yields a receipt an auditor or carrier can verify independently.

When should I use HATS versus Verification, HICS, or Agent-008?

Use HATS for continuous operational evidence over time; use Verification for an independent verdict on an existing artifact; use HICS for a maturity score; use Agent-008 to govern an AI decision. The dashboard's monitoring is not itself verification.

Is the proof stream on this dashboard real verified evidence?

The live stream is a demonstration. Client-generated proofs carry verified:false and sample:true and are never presented as an independently verified verdict — a browser cannot render the external verifier's judgment. A real receipt is verified by the independent verifier, offline.

How is the dashboard different from independent verification?

The dashboard records, monitors, and emits receipts; the independent verifier renders the verdict on them. HATS supplies the record and does not verify itself — that separation is the trust boundary.

What can I do with a receipt from this dashboard?

Hand it to an auditor, carrier, or counterparty. Each receipt is a portable artifact of the same shape whether a control passed or failed, so the recipient verifies the evidence themselves rather than trusting an attestation.

HATS Enterprise — Customer Dashboard

Activity

Verification History

Your Protection Journey

Policyholder Operational Integrity Scores

Remediation

Why this dashboard exists

When to use HATS — and when not

Frequently asked

What does the HATS customer dashboard record?

Why does the dashboard exist?

When should I use HATS versus Verification, HICS, or Agent-008?

Is the proof stream on this dashboard real verified evidence?

How is the dashboard different from independent verification?

What can I do with a receipt from this dashboard?