3023 · Graph and agent inspection

Chapter 20.3 · Evidence questions without legal conclusions

Construct a reproducible evidence trail for a past asset action while preserving missing time and authority.

Exact assertion and unknown provenance fields

Open a workspace beside this lesson. Protected links keep their existing access gates; no new permission is granted by this course.

Opening the fixed anonymous evidence graph…

Why this matters

A reviewer may need to know which exact unit, method version, operator and evidence supported a past action.

The chapter’s dispute scenario highlights why source and chronology should remain inspectable long after an event.

Step by step

01
Turn a dispute into evidence questions
Screen or control: Chapter 20.3 question-and-evidence table
Why: A broad allegation should not be answered with an unsupported verdict.
How: Ask about calibration at the relevant time, exact method revision, actor authority and result review. List the receipts needed for each question.
What you should see: A question-to-evidence map.
Verify: No court outcome, compliance verdict or legal advice is supplied.
02
Inspect unknowns honestly
Screen or control: P5 original record and relationship JSON
Why: A timeline cannot be completed from missing fields.
How: Inspect one assertion’s actor, source, timestamp and authority. Draft a timeline with unknown dates explicitly unplaced rather than guessed.
What you should see: A source-preserving audit sketch.
Verify: No ordering is invented from array position or display order.

What is happening under the surface

Separate what a source asserted, what was observed, the assessment made and the decision authorized.

Hashes bind bytes; they do not establish the truth of contents, authenticity of every assertion or legal admissibility.

Common mistakes

Calling a SHA-256 hash proof that an assertion is true.
Claiming immutable records alone guarantee legal acceptance or regulatory compliance.

The records an agent needs

The sample supplies inspectable context and unknowns. It does not contain signed court evidence, a complete past-state timeline or a legal admissibility determination.

Exact retained identities

urn:epc:id:giai:0614141.4

Anonymous package occurrence pointers

#/P5/nodes#/P5/edges

Fields or record paths to inspect

sourceassertingActorIdauthorityEvidenceassertionTimescope

Pointers locate records; hashes pin bytes; lesson numbers locate teaching material. None substitutes for an applicable assigned GS1 identity.

Apply what you learned

Prepare an evidence index for an anonymous past-action question.

Prepare these outputs

Four review questions
Exact source references
Unknown chronology and authority
Required provenance/verification receipts

Review your work against these checks

Source assertions are not rewritten
Unknown chronology is explicit
No legal or compliance determination is claimed

Check your reasoning

What does a matching document hash prove?

This answer stays in page memory, is cleared when you leave, and is not sent or recorded as certification, validation or authority.

Source and current boundaries

Chapter 20.3 · future vision. Adapted, anonymous teaching prose; not a quotation or independent verification of the author’s assertions.

Source part word/document.xml; original document SHA-256 71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f. Exact paragraph/table locators are retained; page numbering is not verified.

This is evidence-literacy education, not legal advice or proof of admissibility, compliance, qualified past state or court acceptance.

Current governance adds exact-source retention, unknown-state, disclosure, validation and scoped-authority safeguards. Those safeguards are not represented as quotations from the historical book.

Numeric lesson numbers are educational content locators, not GS1 identities. Linked public screens use an anonymous non-issued fixture; reading, retrieval and practice do not authorize physical/cloud execution or constitute model-weight training.