COMPUTED — The question was answered from the rules

For LLMs4 sections

What it means

The engine ran the package against the facts of the case and reached an answer through the normal path: rules fired, the result was derived, and the proof is recorded. This is the healthy outcome — every other status in this chapter names a specific reason the engine could NOT do the same.

A scenario that expects this status pins the healthy path: if a later edit to the package breaks derivation, the expectation fails and the breakage is visible where it happened.

When you see it

language "law.core" version "0.2";
package demo.diagnostics version "0.1.0";
namespace "urn:law:demo:diagnostics";

entity Applicant;
relation resident(a: Applicant) kind institutional;
relation permit_eligible(a: Applicant) kind institutional;

rule PermitEligibility strict {
    for a: Applicant;
    when resident(a);
    then permit_eligible(a);
}

language "law.core" version "0.2";
package demo.diagnostics version "0.1.0";
namespace "urn:law:demo:diagnostics";

test "a resident is eligible" {
    given {
        context { legal_time @2026-03-01; decision_time @2026-03-01T09:00:00Z; knowledge_time @2026-03-01T09:00:00Z; timezone "UTC"; }
        assert resident(entity_ref("urn:demo:diagnostics:ann")) { origin case_input; }
    }
    evaluate truth(permit_eligible(entity_ref("urn:demo:diagnostics:ann")));
    expect truth_status == TRUE_ONLY;
    expect evaluation_status == COMPUTED;
}

What to do

Nothing — this is the outcome a working package produces. Keep the expectation in the scenario: it guards the derivation against silent regressions when the package grows new rules or new exceptions.

Documentation for Arxo. Writings — blog.arxo.io.

Anonymous visit counts on stats.arxo.io, no cookies.