Evidence graph · EG-LOCAL-20260909-001

Trace the claim
to the file.

Every visible outcome connects to a versioned scope, permission context, case and artifact. Missing prerequisites remain visible endpoints.

Relationship map

One run is the spine.

Fictional authorized loopback only

CONTEXT

HARNESS0.1.0

CONTRACT1.0.0

CLIENTNOT PRESENT

RUN

LOCAL-HARNESS20260909-001FAIL

ENVIRONMENT127.0.0.1

AUTHORIZATIONSELF-OWNED

OUTCOMES

CASES4 PASS · 1 FAIL

WORKFLOWBLOCKED

ARTIFACTS5 HASHED

Case → artifact

No execution, no artifact.

The blocked workflow ends without a file. That missing edge is evidence of restraint, not a gap filled by inference.

CON-L01PASSEV-001

DSC-L01PASSEV-002

TOL-L01PASSEV-003

AUT-L01PASSEV-004

ERR-L01FAILEV-005

WRK-L01BLOCKEDNO ARTIFACT

Typed relationships

Context is part of the result.

run: executed byharness 0.1.0
run: governed bycontract 1.0.0
run: targetedfixture-2
run: executed in127.0.0.1
run: client contextNOT PRESENT
run: authorized byself-owned fixture

Authorization and permissions

Allowed and denied paths are distinct.

The self-owned fixture authorized the run. The reader role supported the document-return case; the denied role supported the access-control case. The public fixture marker was redacted in captured requests.

READER ROLEALLOWEDTOL-L01 → EV-003

DENIED ROLEDENIEDAUT-L01 → EV-004

Missing-client boundary

The client node says NOT PRESENT.

No named MCP client participated. The search–read–cite workflow therefore remains BLOCKED and produces no execution artifact. The graph cannot be read as client compatibility evidence.

A later, separate run now exercises that sequence with a deterministic local driver. It does not alter this frozen graph.

Inspect the later workflow run Open graph record Inspect evidence run