Leadership Under Uncertainty

SCO Judgment Layer Compatible

Data platforms, models, agents and workflow systems each handle part of an organization’s work. They do not usually carry a durable representation of what an organization currently believes, how uncertain it is, what alternatives it has entertained, why a judgment changed and whether prior judgments were borne out.

When two systems exchange a judgment, that representation can survive the exchange or be lost in it. This profile lets a third party check which of the two happened. Whether the judgment is sound is a separate question, which the companion benchmark measures.

The profile

Four independent classes

The classes are independent of one another. A read-only dashboard can be a Consumer without being a Producer, and an attestation service can be Attested without parsing a single view.

Consumer

Ingests judgment artifacts and preserves their epistemic content.

A Consumer keeps a calibrated probability as a number, keeps the citation that ties a claim to its source, and keeps the reader’s action rating separate from a description of another party’s position.

Producer

Emits artifacts another system can consume without private coordination.

Revisions are recorded as change events carrying a reason, and the earlier state is kept. Another system can then audit why a judgment moved.

Round-trip

Closes the loop from judgment to decision to returned outcome.

A judgment layer needs this class, because a system that never receives an outcome cannot show that any of its judgments was wrong.

Attested

Produces or verifies artifacts whose integrity a third party can recompute offline.

Demonstrated against a fixture set containing one clean artifact and two tampered ones. The verifier must accept the first and reject both of the others.

Registry

Assessed so far

leadership-under-uncertainty-reference-implementation 2026.072026-07-28 · SCO-JLC 1.0-draft

Classes attained: producer, roundtrip, attested (assessed: producer, roundtrip, attested)

Self-assessment of the reference implementation, with a linked statement of each run.

reportHash 92fd5f4b6d024f854aadb574d60c391c27d97cc1caadeea5ca1291ba1e0d07a8

The first entry is the maintainers’ own reference implementation. Entries are append-only, so a system that later regresses keeps its entry, with an annotation.

Checking a claim

The compatibility validator

The validator is deterministic and runs offline, with no network access, no model calls and no account. It is available on request from the project, so that a party other than the one making a compatibility claim can check it.

Limits

What a statement does not establish

A statement does not establish that the judgments carried are true or that the reasoning behind them is sound, which the companion benchmark measures. It does not show that a recorded rationale is the reason the system reached its output, that everything material was recorded, or that the artifact reflects the model’s internal state.

At the level of the system, no security or privacy property is assessed. A listing is not an endorsement, and a statement describes only the version assessed on the date assessed.

Status

A candidate profile

SCO-JLC 1.0-draft is a candidate profile, open for anyone to read. Assessment is run with the validator and re-verified by the maintainers before listing, and other implementers are welcome to submit a system.

← Evidence you can check