Topic 05
What the Status Actually Means
Jena4 separates what the current conditions support, whether that basis is still current, and whether evaluation has finished.
Why one status is not enough
A red or green label cannot tell you the whole story.
A team reviewing production access needs to know more than pass or fail. It needs to know what the current conditions support, whether those conditions changed, and whether Jena4 has finished evaluating the update.
The five validity meanings
The same conclusion can carry very different signals.
- Established
Current approvals and controls support the conclusion that production access is certified.
- Unresolved
The conclusion could still be supported, but a required access review is missing or incomplete.
- Not established
Nothing currently supplied establishes the certification. This does not prove that access was expressly prohibited.
- Contradicted
Current opposing support says the certification should not stand.
- Unknown
Jena4 has not yet meaningfully evaluated the conclusion.
These meanings describe Jena4’s recorded conclusion. Production-access certification is an example of the kind of decision an organization could govern, not a packaged template.
Two other signals matter
A result can be valid but stale—or still waiting for evaluation.
Stale keeps the previous validity visible for context, but a changed condition means that old result is no longer a current basis for reliance.
Pending and error tell you Jena4 has not completed updated reasoning. They must not look like a finished answer.
An important boundary
A status is not a command to another system.
A status reports Jena4’s recorded conclusion and whether it needs attention. It does not grant or remove access, and it does not prove that an external system acted correctly.