checkId: doctor.evidence.timestamp.eidas.trust-list-fresh family: doctor-check/v1 service: evidence-web scope: installation severity: warning tags: [timestamping, eidas, trusted-list, freshness, evidence]

Trusted List Fresh

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.

Checks that the trusted-list material in use is signature-verified, not past its declared next update, and inside its age budget. Signature-SHAPED XML is not verification: an unverified pack is a hard failure, not a warning about its age. Default severity when it fails: warning. 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

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

Every value is a bounded measurement or pointer; no token bytes, trust material or credentials appear in evidence.

Common causes

Configuration

Interpreting an ETSI trusted list needs the Cryptography eIDAS plugin, and the plugin ABI exposes no trusted-list contract to Evidence yet; this check therefore reports unavailable with reason source-not-configured on every estate today, even when the OfflineKit bundle carries a trust-list part. Transporting the material and interpreting it are separate problems.

Thresholds live in Evidence__TimestampAssurance__Policy__* and default to the values the retired Doctor plugin used (carried verbatim so a cadence or threshold change is always a visible edit).

How to verify

Resolve the installation’s actual Evidence service or gateway origin and use its admitted operational identity. The SDK derives a service-scoped path from EvidenceSchemaTopology.ServiceName (evidence) through ServiceDoctorRoute.ChecksPathFor. The older flat /doctor/checks collision does not describe the current service-scoped Evidence route; no compatibility alias or fixed host is supplied here.

The Evidence host explicitly binds its Doctor health policy to ops.health. A generic SDK adopter supplies its own policy. The mapped handler invokes RunAllAsync for every registered service check, then returns the execution envelope; selecting one result client-side does not restrict which checks run. Confirm service=evidence, contractVersion=doctor-check/v1 and the selected check’s healthy, severity, message and evidence. A missing result, unavailable source or empty selection is not a passing measurement. An authorized GET can invoke configured source probes; this source review issues no request or timestamp operation.

The original direct-origin construction remains explicit data, including its exact options, bearer header and distinct result selector:

Source-contract fieldLiteral data / runtime unverified
Observation1
RoleEvidence installation timestamp result: doctor.evidence.timestamp.eidas.trust-list-fresh
MethodGET
Original targethttp://evidence-web.stella-ops.local:8080/doctor/evidence/checks
Intended outputdoctor-check/v1 envelope service=evidence, contractVersion, checks[]; selected doctor.evidence.timestamp.eidas.trust-list-fresh
Consumeroperator inspection of doctor.evidence.timestamp.eidas.trust-list-fresh
Classificationoriginal direct-origin request intention; source-mapped route, installed outcome unverified
Check Iddoctor.evidence.timestamp.eidas.trust-list-fresh
Current Owner PathServiceDoctorRoute.ChecksPathFor(EvidenceSchemaTopology.ServiceName): /doctor/evidence/checks
Configured Originoperator-selected immediate Evidence service or gateway origin; old host/port are illustrative
Original Client Options-sS
Header TemplateAuthorization: Bearer $OPS_HEALTH_TOKEN
Projectionjq '.checks[] &#124; select(.checkId == "doctor.evidence.timestamp.eidas.trust-list-fresh")'
Request Bodynone
AuthorizationEvidence DoctorHealthPolicy=evidence.ops.health binds OpsHealth claim ops.health; generic SDK policy remains host-supplied
Source ClassTrustListFreshCheck
Source ReadGetTrustListAsync
EvaluatorTrustListFresh
Sourcesrc/__Libraries/StellaOps.Doctor.Plugin.Abstractions/ServiceDoctorHosting.cs; src/Evidence/StellaOps.Evidence.WebService/Program.cs
Execution BoundaryGET invokes all registered service checks through RunAllAsync before client-side selection; no passive-cache or single-selected-check execution claim
Result Boundarycheck-specific healthy,severity,message,evidence and source-unavailable state must be inspected; missing selected check or zero output is not success
Registration BoundaryDoctor:Registration is a separate default-off opt-in; registration/heartbeat claims do not prove aggregation pull or execution success

Platform registration is a separate opt-in (Doctor:Registration:Enabled defaults to false), independent of whether the service-local mapper is composed. The aggregator sees only registered claims and its own actual pull results; a successful registration or heartbeat does not establish a successful authenticated pull. Inspect that deployment’s per-service result/error/freshness rather than assuming visibility or a pass.

Source review verified against d6865baa31b34ab3389c35daa01822c77fca9cac; installed route availability and check outcomes were not rechecked. Credential-free source re-verification from the repository root:

rg -n "ChecksPathFor|RunAllAsync|DoctorHealthPolicy|AddTimestampAssuranceInstallationChecks|MapServiceDoctorEndpoints|ServiceName" src/__Libraries/StellaOps.Doctor.Plugin.Abstractions/ServiceDoctorHosting.cs src/Evidence/StellaOps.Evidence.WebService/Program.cs src/Evidence/StellaOps.Evidence.WebService/Doctor/EvidenceSchemaTopology.cs

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.