Skip to content
Theos Quantum TQ globe markTHEOS QUANTUM
Start here

Reading an illustrative exposure report

A synthetic estate of 42 assets shows how to inspect scope, evidence and the published scoring arithmetic

Reviewed 22 Sept 2026 2 min read
On this page — 5 sections

Illustrative example

This is a synthetic reference estate, not customer data or a measured pilot result. Its 42 assets and score of 75/100 illustrate the published method; they do not predict findings or accuracy on your systems.

Read scope and evidence before the headline score. This walkthrough explains a synthetic example of the published method; it is not a customer report or a promise of a current automated reporting feature.

What the three numbers mean

FigureMeaningLimit
42 assetsThe size of the synthetic reference estate.Not a discovered customer inventory or a typical estate size.
36 outside ContainedThe assets in Acute, Elevated and Watch in this example.Includes classical weaknesses as well as quantum exposure; not 36 quantum-vulnerable assets.
75/100The rounded criticality-weighted mean of the illustrative asset scores.Not a probability of compromise, a compliance verdict or migration progress.
All three belong to one educational example.

Check the arithmetic

text
weighted contribution = 6295
criticality-weighted asset count = 84
estate score = 6295 / 84 = 74.940...
round half-up = 75
tier = Elevated (65–84)

The distribution is 13 Acute, 16 Elevated, 7 Watch and 6 Contained. These counts sum to 42. The estate tier can change when a sufficiently influential cohort changes. The methodology publishes the cohort inputs and rounding rule.

Questions to ask of a real finding

  • Which input and revision produced the observation?
  • What evidence supports the algorithm and parameters? What remains unknown?
  • What was excluded from the scope?
  • Which parts are observed facts, which are declared context, and which are judgements?
  • Does the method version match any earlier result being compared?

Performance and accuracy require separate evidence

The earlier synthetic classifier evaluation does not establish accuracy on customer systems. No review-speed improvement is established by this worked example. A timing comparison needs a common scope, a documented manual baseline, run logs, software and hardware versions, repeated runs and quality checks.

Product status

Mapping, prioritisation and performance evaluation are planned modules. The published scoring method explains an approach; it does not establish the availability of automated scoring, integrations. Console: Announced (roadmap).

Distinguish recomputing an example from independently reproducing a product result.Inspect the evidence requirements