Specification / Reference
Method, classes and boundaries.
What each instrument can determine, how confident it is entitled to be, and what it explicitly does not observe. This route is documentation, and is written as such.
- Version
- Status
- Updated
Evidence classes
Every field in a record carries a class. The classes exist so that a reader can tell, without asking, which statements were measured and which were concluded.
- Directly present in the public response. Quotable, and reproducible by anyone issuing the same request.
- Computed from the observed response by a fixed rule. The same input yields the same result on every run, including yours.
- Concluded from observed signals but not directly stated. Carries lower confidence and is always labelled as inference.
- Assessed by the principal rather than by the instrument. Professional judgement, attributed as such.
- A proposed action. Never an observation, and never counted as evidence of a condition.
Stated boundaries
An instrument is only useful if its limits are published alongside its findings. These are the Machine Surface Inspector’s.
- The Inspector evaluates public, externally verifiable conditions only. It does not authenticate, and it does not see anything a visitor could not.
- It cannot infer private workflows, internal processes or organisational readiness.
- It does not measure analytics accuracy, and it does not verify that a measurement system reports the truth.
- It does not claim a market benchmark. A condition is reported against a stated method, not against competitors.
- It does not predict ranking, traffic or revenue, and no record will assert a change in them.