Platform foundation
Judgement Object™: govern the consequential matter, not just the output
A Judgement Object is the governed lifecycle container for consequential work — where authority, evidence, human judgement and outcomes persist together.
Why isolated outputs are insufficient
A document, recommendation or model output alone does not preserve the matter being decided, the authority exercised or the evidence that informed judgement.
What a Judgement Object is
Judgement Object™ is the governed lifecycle container for consequential matters — cases, decisions, programmes and other work where human judgement, evidence and accountability must persist beyond a single interaction.
What it is not
- Not a synonym for GovernedWork or every routine task
- Not automatically created for every workflow
- Not a customer-available feature across the entire public pilot today
Matters, cases, decisions and programmes
Judgement Objects apply where the organisation must govern a consequential matter over time — not where a single ephemeral task suffices.
Lifecycle
Objects support lifecycle transitions — creation, progression, review, withdrawal and supersession — with server-authorised writes and canonical reads.
Links to governed work
Judgement Objects link to GovernedWork and the execution that prepared, supported or recorded consequential judgement — without collapsing the two concepts.
Links to Judgement Passports
Eligible outcomes may be associated with Judgement Passports that preserve provenance and accountability for the governed matter.
Review, withdrawal and supersession
Lifecycle operations support review, challenge and formal withdrawal or supersession when judgement or evidence changes.
Illustrative example
Illustrative only — not a deployed programme: a licensing case where multiple evidence submissions, policy interpretations and authorised decisions must persist as one governable matter rather than disconnected outputs.
Current maturity
Core persistence, lifecycle, authority, linkage and read foundations are implemented. Broader customer-facing lifecycle experiences continue to be developed.
Current maturity: Core persistence, lifecycle, authority, linkage and read foundations are implemented. Broader customer-facing lifecycle experiences continue to be developed.
Institutional direction
Broader customer-facing lifecycle tooling, institutional adapters and cross-agency orchestration remain direction — building on implemented persistence and authority foundations.