3004 · Identity and context

Chapter 1 · From an object record to participation

Model identity, communication, relationships, history and accountability as distinct evidence requirements.

Participant identity Inspect participation evidence

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

Why this matters

A registered number is insufficient to describe what a thing can do or who may act on it.

The chapter’s citizenship analogy is useful when each participation property becomes an inspectable requirement.

Step by step

01
Build a participation checklist
Screen or control: Chapter 1 property table
Why: The analogy becomes useful through concrete requirements.
How: List evidence needed for identity, location, communication, relationships, history and accountability. Give each an explicit missing-evidence state.
What you should see: A six-property requirements matrix.
Verify: No property is marked verified merely because a key exists.
02
Compare the checklist with the demo
Screen or control: P1 inspector and complete graph JSON
Why: A demonstration’s limits should be visible to agents.
How: Inspect the asset’s assignment state and one relationship’s actor, scope and authority. Identify one property that the fixture illustrates and one it does not prove.
What you should see: A supported-versus-missing comparison.
Verify: Unknowns are retained as fields, not hidden behind a reassuring paragraph.

What is happening under the surface

Keep declared capabilities, measured observations and proposed relationships separate.

A participant may have rich context while important evidence remains unknown. Registration does not automatically satisfy all participation layers.

Common mistakes

Equating a registered record with an authenticated physical participant.
Treating the seven-layer conceptual model as seven automatically passed gates.

The records an agent needs

These software records illustrate participation structure. They do not establish legal citizenship, tested communication, sensing or physical accountability.

Exact retained identities

urn:epc:id:giai:0614141.4

Anonymous package occurrence pointers

#/P1/sourceAssertions#/P2/mhsSilaDriver#/P5/nodes#/P5/edges

Fields or record paths to inspect

statenativeSilaSupportauthorityEvidenceassertionTime

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

Apply what you learned

Assess an anonymous instrument against the participation matrix.

Prepare these outputs

Six evidence requirements
Two exact demo references
At least two unresolved evidence states

Review your work against these checks

Each requirement has a source or unknown
Accountability is not inferred from an identifier
Conceptual layers remain separate from implemented gates

Check your reasoning

Which description best fits a registered but untested instrument proposal?

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 1 · design principle. 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.

Citizenship and living-participant language is an architectural metaphor; no legal status or subjective experience is established.

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.