Measured, not asserted.
The Foresight Ledger is the product-grade record of engineering foresight: five structural dimensions, named provenance, a dated trail and a CFO-signed evidence row for every figure that leaves the building. If a number cannot be attested, it is not published.
A calculator, not a survey.
Most engineering measurement is a survey: a periodic exercise in asking the organisation to describe itself, reconciled against memory and sentiment. The result is asserted, not measured. It cannot be challenged, because it cannot be reproduced.
The Foresight Ledger is a calculator. Each figure has a defined input set, a named computation, a dated source and a reviewer of record. Two readers, given the same record, produce the same number. That is the bar a measurement must clear before it earns a place in a board pack.
Six commitments, held in every row.
- 01Reads the engineering record you already produce, in place, inside your perimeter.
- 02Computes the five structural dimensions against the estate’s own twelve-week baseline.
- 03Writes every foresight with named provenance, a dated trail, and the action it implies.
- 04Tracks each foresight to resolution, deferral or dismissal — and records the reason.
- 05Produces a CFO-signed evidence row for any figure that leaves the Ledger.
- 06Refuses to publish a number that has not been named, dated and attested.
Five dimensions. One method. The estate’s own baseline.
- What it measures
How tightly systems are bound to one another, how change in one component propagates to its neighbours, and where the architecture has drifted from its stated boundaries.
How it is baselinedTwelve weeks of historical commit, dependency and ownership data, normalised against the estate’s own structural mean. Industry benchmarks are referenced but never substituted for the customer’s own record.
- What it measures
Whether the verification surface has kept pace with the code it protects, where assertion strength has thinned, and which change paths are entering production with materially less evidence than they once did.
How it is baselinedPer-system verification ratios are baselined against the same system’s prior twelve weeks, not against an external standard. A drop is measured against the team’s own established floor.
- What it measures
Who knows the system, how concentrated that knowledge is, and where ownership has thinned to the point that a single departure would materially raise delivery risk.
How it is baselinedContributor graphs are computed across rolling twelve-week windows, with named owners reconciled against your directory. Stewardship thinning is reported, never inferred from sentiment.
- What it measures
How predictable the system is in flight: cycle time, lead time, latency variance and incident frequency, measured at the boundary of the delivery line rather than at the individual contributor.
How it is baselinedVariance is calibrated against the line’s own twelve-week mean and standard deviation. Anomalies are flagged only when they exceed the line’s historical band, not a generic threshold.
- What it measures
The gap between the work that was committed to and the work that actually shipped — scope drift, silent re-prioritisation, and the rate at which originally-named outcomes survive to release.
How it is baselinedIntent is reconciled against your own ticketing and roadmap record, not against a model of what Qeino thinks you should be doing. Alignment is reported as the customer’s own commitment-to-delivery ratio.
Every euro is traceable to a signal.
The Ledger is auditable end-to-end. Each figure is reachable from the signal that produced it through the timestamp at which it was observed, the action it implied, and the financial outcome that followed. Your reviewers — internal or named external — can challenge any row at any time. Withdrawn figures stay on the record, marked as withdrawn, with a reason.
The board-pack row.
Foresight that does not survive contact with a board pack is not foresight. The Ledger exports as a single attested row per delivery line, with the figure, the signal trail behind it, and the CFO signature that puts it in front of the board.
From customer-signed to independently attested.
- 01Today
Customer-attested evidence
Every figure that leaves the Ledger is named, dated and CFO-signed by the customer. Qeino does not publish numbers it cannot attribute.
- 022026
Independent challenge rights
Customers can nominate an internal or external reviewer with read-only access to the underlying signal trail and the right to challenge any figure published from their estate.
- 03Beyond
Third-party attestation
We are scoping an independent attestation regime — a recognised auditor verifying the platform’s measurement discipline against a published standard. We will publish progress in Resources.
“Measurement is a discipline before it is a number. The Ledger exists because we refuse to publish anything we cannot reconstruct — and because the people we build for cannot afford to either.”
A figure your CFO will sign. In eight weeks.
Run a Foresight Pilot on a single delivery line. Named evidence — or we walk away.