Measured usage. Governed baselines. Customer-validated outcomes.
Locs produces operational, assurance and commercial evidence showing what it was used for, what improved, what stayed the same and which assumptions support the conclusions. It never automatically claims it resolved an incident or generated financial savings.
Append-only usage events
Incidents analysed, vendor cases and handovers prepared, assurance runs, unsafe actions blocked, knowledge gaps closed — recorded automatically as counts and durations, never content.
Labelled, assumption-based
Any financial figure is an estimate that requires a customer-approved cost assumption and is always labelled estimated — never blended into a single headline number.
Customer-confirmed outcomes
Material and financial contributions start awaiting validation and are confirmed, disputed or corrected by an authorised validator. Corrections retain history.
A baseline is a governed reference value for one metric on one deployment, labelled by kind (measured, estimated or customer_supplied). Baselines require two-person approval, are immutable once approved (a correction forks a new version), and every calculation names exactly which baseline version it used.
Contribution categories — for example helped locate evidence, helped identify a known error, helped prevent an unsafe action — are validated by the customer. They are never auto-inferred from usage.
Signed pilot-completion and renewal reports
Reports are assembled from measurement events, validated outcomes, active baselines and assurance runs. Each states its period, deployment, software version, data sources, validation status and assumptions, embeds the baseline versions used, keeps measured and estimated separate, and is signed and offline-verifiable.
Establish your baseline before you deploy.
The pilot begins by agreeing measurable success criteria and operational baselines, so value is evidenced rather than asserted.