Trace completeness
The share of required lifecycle transitions whose actor, inputs, outputs, control result and authority decision are linked in the audit trail.
EVIDENCE / CLAIMS LEDGER
Claims should havea survival curve.
This is where Solario will publish the outcomes, definitions, baselines and limitations behind its claims. We are opening the ledger before every dataset is ready so the standard is visible from the start.
01 / CLIENT OUTCOME
One result.
And its boundary.
A live Java 6 insurance SaaS platform, remediated in its existing codebase. The baseline is the client’s own estimate for a conventional programme: approximately one year.
Insurance SaaS · Java 6 estate · CSP remediation
10,000
violations,
in weeks.
Estate-wide remediation of a business-critical platform, in the existing codebase, without migration. Delivered in weeks against a twelve-month estimate for conventional delivery.
SYSTEMLive Java 6 SaaS platform
Insurance software; remediation performed in the existing codebase without a platform migration.
OUTCOME10,000 violations removed
Delivery completed in weeks against the client’s conventional-delivery estimate of roughly one year.
PUBLICATION STATUSCase note in preparation
Client identity remains private. Method, boundary and acceptance evidence will be published at the level permitted.
02 / FACTORY MEASUREMENTS
Measure the controls.
Not token volume.
Factory telemetry is designed around whether work remains governed and whether artefacts survive independent validation, not how much model activity was generated.
Control survival curve
How candidate artefacts move through deterministic checks, repair loops, human checkpoints and final acceptance, showing rejection as well as success.
03 / PUBLICATION STANDARD
A number without a boundary
is marketing copy.
Every result Solario publishes must make the comparison legible enough for a technical buyer to challenge it.
- 01Define the workload
Repository boundary, starting state, target state and acceptance criteria.
- 02Name the baseline
Human estimate, previous delivery, competing process or no-baseline, including who supplied it.
- 03Expose the factory setup
Models, compute, policies, gates, human checkpoints and any manual intervention.
- 04Publish failures and exclusions
Rejected artefacts, repair loops, incomplete evidence and what the result does not prove.
04 / See the system behind the claims
Inspect the factory. Then challenge the evidence.
See how governance, controls and production records are designed, or start with a bounded system whose outcome can be measured.