checkId: doctor.evidence.timestamp.eidas.qualified-status family: doctor-check/v1 service: evidence-web scope: installation severity: critical tags: [timestamping, eidas, qualified-status, claim-gate, evidence]
Qualified Status (Claim-Gated)
Stella Ops is self-hosted software. It does not issue electronic time stamps or provide any qualified trust service. This deployment performs local verification using operator-supplied evidence. Unless an approved jurisdiction-, provider-, service-, and deployment-specific claim profile applies, qualified status is not determined.
Evaluates the technical qualified-status classification of the configured TSA and whether the operator claim gate permits saying anything about it. Three gates apply: technical verification, regulatory classification, and rights/claim publication. Every operator-facing sentence comes from the counsel-approved wording set, verbatim. Default severity when it fails: critical. Installation-scoped: one result per estate, served on the Evidence doctor path and probed on the worker schedule trust-list-refresh (daily).
What it measures
- Healthy only when the technical gate passed and any supplied regulatory evidence could be classified.
- Renders the machine-readable classification fields as evidence; consumers read those, never the prose.
- While the claim gate is closed the product-wide notice is carried on the result and positive wording is suppressed.
The check never reports a pass for a value it does not have. When its source cannot be read it reports unhealthy with the message Source unavailable (<reason>): <detail>. No verdict can be reported. and the evidence keys source.state=unavailable, source.reason (one of source-not-configured, source-configuration-invalid, unavailable-by-sealed-policy, source-material-invalid, source-read-failed) and source.detail.
Evidence keys
claim.disclaimerclaim.closedGateNoticeclaim.positiveWordingSuppressedqualified.pluginIdqualified.pluginVersionqualified.pluginDigestqualified.trustMaterialDigest
Every value is a bounded measurement or pointer; no token bytes, trust material or credentials appear in evidence.
Common causes
- No qualified-status source is wired (current state everywhere).
- Once wired: supplied regulatory evidence that does not authenticate.
Configuration
No qualified-status source exists yet (the eIDAS plugin ABI exposes none), so the check reports unavailable with reason source-not-configured. The claim gate stays closed by default; opening it requires an approved jurisdiction-, provider-, service- and deployment-specific claim profile.
How to verify
The 17 installation checks are served by evidence-web on the shared doctor-check/v1 path and need the ops.health scope. Probe the service DIRECTLY from inside the estate network: the gateway’s unprefixed /doctor/evidence/checks resolves to whichever service registered that template first, not to Evidence.
curl -sS -H "Authorization: Bearer $OPS_HEALTH_TOKEN" \
http://evidence-web.stella-ops.local:8080/doctor/evidence/checks \
| jq '.checks[] | select(.checkId == "doctor.evidence.timestamp.eidas.qualified-status")'
Once the Evidence doctor registration is activated (it is off by default in a sealed estate), the same result is also visible through the Platform doctor aggregator under the evidence service.
Related checks
- Trusted List Fresh (
doctor.evidence.timestamp.eidas.trust-list-fresh) - Qualified Status Change (
doctor.evidence.timestamp.eidas.status-change)
This is a local evidentiary classification of the token and issuing service at the stated time. It is not the output of a qualified validation or qualified preservation service and does not determine the legal effect of the underlying release, document, or transaction.
