Expound/Platform/Account & Verdict
The Account, and the Verdict read from it
The Account is the full case file for one decision: every requirement, what discharged it, what blocked, each kept separate and never averaged into a score. The Verdict is the answer read from it for one exact question. Nobody can set it by hand.
The Account
Nothing averaged, nothing discarded at write time.
For every required obligation, the Account keeps what is known, where things stand, how strong the proof is, where the proof came from, when it applies, and what question was asked. It is a case file, not a log line and not a score.
An audit log≠A worked-out answer
An audit log records what a system did. An Account records what the system concluded and from what, including the parts that did not resolve.
The question, exactly as posed
Relying party, result, purpose, moment. A verdict cannot be reinterpreted against a different question if the original question travels with it.
Every dimension kept separate
Averaging is the thing the Account exists to refuse. A single number cannot say which obligation blocked.
Blockers named
Which obligation failed, and on what: strength of proof, independence, or current validity.
Proof roots retained
So a second party can walk back to primary evidence rather than to a summary of it.
The Verdict
One question, one answer, and nobody can set it by hand.
A required obligation is not discharged. One blocked obligation blocks the result regardless of strength elsewhere.
Something material is unresolved rather than negative. The question cannot be answered as posed.
Evidence aged, an observer failed, or a provider degraded, and a compensating obligation, declared in advance and independent of what failed, is itself discharged. The failing obligation is named and reliance narrows to the exact decisions affected. Without such an obligation the result does not reach DEGRADED.
Every required obligation is met on both strength of proof and independence, for this exact question, now.
A word like final or passed, detached from the question it answered, means nothing on its own.
One Account, many questions
The same Account. Two questions. Two answers.
Asked may this analyst cite the result in an internal memo, an Account may answer VERIFIED. Asked may this release manager route customer traffic on it, the same Account answers BLOCKED, because the second roster requires occurrence evidence and an authority the first never needed.
Neither answer is the status of the work. Each answers one reliance question.
A verdict≠A status
A verdict without its question is not a shorter verdict. It is meaningless. This is why a single status field cannot represent the situation: one determination can be relied upon for one decision and refused for another at the same instant, with nothing stale about it.
Next steps
A verdict is true when it is computed.
Keeping it true is the next job.
Continuous Finality
Who relied on what is recorded at the time, so finding what a change affects is a lookup, not an investigation.
Explore →NextClaim and reliance licenses
What may be said about a result, and who may act on it.
Explore →TestThe Four-Corners Test™
Whether a conclusion can be reconstructed from the evidence its four corners cite.
Explore →