Methodology and authority
The evidence is useful only when its boundary travels with it.
This ledger documents public evidence about workflow changes. It does not claim that AI alone caused every observed outcome. Each result keeps its attribution caveat, source condition, review date, and freshness status.
Evidence tiers
- verified
- Verified means the central outcome is supported by peer-reviewed, independent, or otherwise directly checkable public evidence.
- mixed
- Mixed means the case combines stronger evidence with material company-reported, forecast, modeled, or scope-limited claims.
- reported
- Reported means the outcome is attributed to the deploying organization or vendor and has not been independently measured.
Negative and mixed evidence stays visible
Publication is not a success-story filter. Null effects, adverse outcomes, model failures, discriminatory effects, and mixed evidence remain in scope when the public record is strong enough. Their presence is a control against overstating transferability or causal certainty.
Freshness policy
- Current
- Reviewed against the cited public evidence on the displayed review date.
- Watch
- Still publishable, but a material claim, deployment condition, or source needs closer monitoring. Watch status: verify the cited source and deployment condition before reusing this case.
- Stale
- The case remains historically useful, but its evidence has passed the review window or no longer describes current operation. Stale status: use this as historical evidence, not as a current operating claim.
- Superseded
- A later public record or operating model replaces this version; the prior version remains visible for traceability. Superseded status: cite the replacement where available and use this version only for history.
Update and version policy
Every publication bundle has a deterministic version and fingerprint. The public history ledger records added, changed, and retired stable IDs. A case cannot disappear from a subsequent bundle without an explicit retirement reason; prior slugs and canonical URLs remain in the public history. Private claim ledgers, source excerpts, confidence annotations, and internal research IDs are never published through the machine routes.
Bundle 1.0.0 · fingerprint sha256:c23c6cc2b88153d008ea8fda928f632ce0011fc2d4c5036672a16e5d895bab93 · reviewed 2026-08-23