{"schemaVersion":"thingdaddy.learning-course/1.0","title":"Physical AI deep dive","governance":{"scope":"Anonymous educational course; private source examples require their existing authorization","referenceKind":"educational-content-locator-not-gs1-identity","sourcePackageSha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","demonstrationPrefix":"0614141","assignmentState":"demo_non_issued","companyAuthorityEvidence":null,"identifierIssuancePerformed":false,"physicalExecutionAuthorized":false,"scientificValidationPerformed":false,"cloudCommissioningPerformed":false,"modelWeightTrainingPerformed":false,"knowledgeCheckIsCertification":false,"learnerAnswersStoredOrSent":false,"privateCorpusRead":false,"sourceBooksModified":false,"registeredMcpToolsAdded":false},"bookCoverage":{"sourceLabel":"ThingDaddy book","sourceSha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","sourcePart":"word/document.xml","paginationVerified":false,"actualBodyHeading1Sections":30,"numberedChaptersPresent":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,20,21,22,23,24],"missingBodyChapters":[17,18,19],"absentBodyAppendices":["A","B","C","D","E","F","G"],"gaps":["The supplied body jumps from Chapter 16 to Chapter 20. Chapters 17–19 are not reconstructed from the contents list.","Appendices A–G listed in the contents are not present as supplied body sections; no appendix content is invented.","The six Chapter 20 Heading1 subsections are separate reading stops, not six additional numbered chapters. Section 20.7 is included in the 20.6 stop.","Source locators are exact OOXML addresses. Rendered page numbers are unknown and not used as citations.","Original company examples, private paths, protected implementation mechanisms and unsupported scale, patent, pricing and performance claims are excluded from public teaching."],"sections":[{"lessonNumber":"3001","section":"Foreword","title":"Foreword · Why the physical world needs context","headingPointer":"/w:document/w:body/w:p[208]","sourcePointers":["/w:document/w:body/w:p[208]","/w:document/w:body/w:p[211]","/w:document/w:body/w:p[213]","/w:document/w:body/w:p[219]"],"classification":"design_principle"},{"lessonNumber":"3002","section":"Prologue","title":"Prologue · Integration heritage without losing meaning","headingPointer":"/w:document/w:body/w:p[221]","sourcePointers":["/w:document/w:body/w:p[221]","/w:document/w:body/w:p[225]","/w:document/w:body/w:p[229]","/w:document/w:body/w:p[235]","/w:document/w:body/w:p[243]","/w:document/w:body/w:p[246]","/w:document/w:body/w:p[248]","/w:document/w:body/w:p[252]"],"classification":"author_history"},{"lessonNumber":"3003","section":"Identity preface","title":"Identity preface · Standards, carriers and exact keys","headingPointer":"/w:document/w:body/w:p[254]","sourcePointers":["/w:document/w:body/w:p[254]","/w:document/w:body/w:p[255]","/w:document/w:body/w:p[260]","/w:document/w:body/w:tbl[2]","/w:document/w:body/w:tbl[3]","/w:document/w:body/w:p[274]"],"classification":"design_principle"},{"lessonNumber":"3004","section":"Chapter 1","title":"Chapter 1 · From an object record to participation","headingPointer":"/w:document/w:body/w:p[282]","sourcePointers":["/w:document/w:body/w:p[282]","/w:document/w:body/w:p[285]","/w:document/w:body/w:p[289]","/w:document/w:body/w:p[294]","/w:document/w:body/w:tbl[4]","/w:document/w:body/w:p[303]","/w:document/w:body/w:p[313]"],"classification":"design_principle"},{"lessonNumber":"3005","section":"Chapter 2","title":"Chapter 2 · Sensing as a contextual event","headingPointer":"/w:document/w:body/w:p[317]","sourcePointers":["/w:document/w:body/w:p[317]","/w:document/w:body/w:p[320]","/w:document/w:body/w:p[322]","/w:document/w:body/w:p[334]","/w:document/w:body/w:p[337]","/w:document/w:body/w:p[338]","/w:document/w:body/w:p[339]","/w:document/w:body/w:p[340]","/w:document/w:body/w:p[343]"],"classification":"author_history"},{"lessonNumber":"3006","section":"Chapter 3","title":"Chapter 3 · Context beyond the registry","headingPointer":"/w:document/w:body/w:p[351]","sourcePointers":["/w:document/w:body/w:p[351]","/w:document/w:body/w:p[352]","/w:document/w:body/w:p[356]","/w:document/w:body/w:tbl[5]","/w:document/w:body/w:p[361]","/w:document/w:body/w:p[363]","/w:document/w:body/w:p[365]","/w:document/w:body/w:p[368]","/w:document/w:body/w:p[371]"],"classification":"design_principle"},{"lessonNumber":"3007","section":"Chapter 4","title":"Chapter 4 · Local operation and shared memory","headingPointer":"/w:document/w:body/w:p[379]","sourcePointers":["/w:document/w:body/w:p[379]","/w:document/w:body/w:p[382]","/w:document/w:body/w:p[385]","/w:document/w:body/w:p[393]","/w:document/w:body/w:p[397]","/w:document/w:body/w:p[401]","/w:document/w:body/w:p[405]","/w:document/w:body/w:p[409]","/w:document/w:body/w:tbl[7]","/w:document/w:body/w:p[412]"],"classification":"future_vision"},{"lessonNumber":"3008","section":"Chapter 5","title":"Chapter 5 · Design, model and physical unit","headingPointer":"/w:document/w:body/w:p[420]","sourcePointers":["/w:document/w:body/w:p[420]","/w:document/w:body/w:p[421]","/w:document/w:body/w:p[423]","/w:document/w:body/w:p[427]","/w:document/w:body/w:p[428]","/w:document/w:body/w:p[429]","/w:document/w:body/w:tbl[8]"],"classification":"future_vision"},{"lessonNumber":"3009","section":"Chapter 6","title":"Chapter 6 · Commercial records without identity replacement","headingPointer":"/w:document/w:body/w:p[436]","sourcePointers":["/w:document/w:body/w:p[436]","/w:document/w:body/w:p[439]","/w:document/w:body/w:tbl[9]","/w:document/w:body/w:p[444]","/w:document/w:body/w:p[445]","/w:document/w:body/w:p[447]","/w:document/w:body/w:p[450]","/w:document/w:body/w:p[453]"],"classification":"future_vision"},{"lessonNumber":"3010","section":"Chapter 7","title":"Chapter 7 · Remote monitoring needs governed scope","headingPointer":"/w:document/w:body/w:p[461]","sourcePointers":["/w:document/w:body/w:p[461]","/w:document/w:body/w:p[468]","/w:document/w:body/w:tbl[10]","/w:document/w:body/w:p[470]","/w:document/w:body/w:p[477]","/w:document/w:body/w:p[480]","/w:document/w:body/w:p[483]"],"classification":"future_vision"},{"lessonNumber":"3011","section":"Chapter 8","title":"Chapter 8 · Discovery starts with an observation","headingPointer":"/w:document/w:body/w:p[491]","sourcePointers":["/w:document/w:body/w:p[491]","/w:document/w:body/w:p[494]","/w:document/w:body/w:p[498]","/w:document/w:body/w:tbl[11]","/w:document/w:body/w:p[501]","/w:document/w:body/w:p[509]","/w:document/w:body/w:tbl[12]"],"classification":"future_vision"},{"lessonNumber":"3012","section":"Chapter 9","title":"Chapter 9 · Ground reasoning without pretending to know everything","headingPointer":"/w:document/w:body/w:p[519]","sourcePointers":["/w:document/w:body/w:p[519]","/w:document/w:body/w:p[522]","/w:document/w:body/w:p[525]","/w:document/w:body/w:p[526]","/w:document/w:body/w:p[527]","/w:document/w:body/w:p[528]","/w:document/w:body/w:p[529]","/w:document/w:body/w:p[530]","/w:document/w:body/w:p[534]","/w:document/w:body/w:p[536]"],"classification":"future_vision"},{"lessonNumber":"3013","section":"Chapter 10","title":"Chapter 10 · Participation across institutions","headingPointer":"/w:document/w:body/w:p[543]","sourcePointers":["/w:document/w:body/w:p[543]","/w:document/w:body/w:p[546]","/w:document/w:body/w:p[548]","/w:document/w:body/w:p[552]","/w:document/w:body/w:tbl[13]"],"classification":"future_vision"},{"lessonNumber":"3014","section":"Chapter 11","title":"Chapter 11 · Turn the civilization thesis into checkpoints","headingPointer":"/w:document/w:body/w:p[556]","sourcePointers":["/w:document/w:body/w:p[556]","/w:document/w:body/w:p[557]","/w:document/w:body/w:p[559]","/w:document/w:body/w:p[565]","/w:document/w:body/w:p[567]","/w:document/w:body/w:p[569]","/w:document/w:body/w:p[571]","/w:document/w:body/w:p[572]"],"classification":"design_principle"},{"lessonNumber":"3015","section":"Chapter 12","title":"Chapter 12 · A corpus about particular things","headingPointer":"/w:document/w:body/w:p[583]","sourcePointers":["/w:document/w:body/w:p[583]","/w:document/w:body/w:p[584]","/w:document/w:body/w:p[586]","/w:document/w:body/w:p[589]","/w:document/w:body/w:p[591]","/w:document/w:body/w:p[594]","/w:document/w:body/w:tbl[14]"],"classification":"future_vision"},{"lessonNumber":"3016","section":"Chapter 13","title":"Chapter 13 · From integration heritage to a reusable method","headingPointer":"/w:document/w:body/w:p[605]","sourcePointers":["/w:document/w:body/w:p[605]","/w:document/w:body/w:p[608]","/w:document/w:body/w:p[611]","/w:document/w:body/w:p[613]","/w:document/w:body/w:p[615]","/w:document/w:body/w:p[618]","/w:document/w:body/w:p[621]","/w:document/w:body/w:p[623]","/w:document/w:body/w:p[627]","/w:document/w:body/w:tbl[15]"],"classification":"author_history"},{"lessonNumber":"3017","section":"Chapter 14","title":"Chapter 14 · Plan customer value in service layers","headingPointer":"/w:document/w:body/w:p[633]","sourcePointers":["/w:document/w:body/w:p[633]","/w:document/w:body/w:p[636]","/w:document/w:body/w:p[638]","/w:document/w:body/w:tbl[16]","/w:document/w:body/w:p[640]","/w:document/w:body/w:p[641]","/w:document/w:body/w:tbl[17]"],"classification":"future_vision"},{"lessonNumber":"3018","section":"Chapter 15","title":"Chapter 15 · Methodology and responsible disclosure","headingPointer":"/w:document/w:body/w:p[646]","sourcePointers":["/w:document/w:body/w:p[646]","/w:document/w:body/w:p[647]","/w:document/w:body/w:p[649]","/w:document/w:body/w:p[653]"],"classification":"future_vision"},{"lessonNumber":"3019","section":"Chapter 16","title":"Chapter 16 · Relationships turn transactions into ecosystems","headingPointer":"/w:document/w:body/w:p[663]","sourcePointers":["/w:document/w:body/w:p[663]","/w:document/w:body/w:p[668]","/w:document/w:body/w:p[672]","/w:document/w:body/w:p[673]","/w:document/w:body/w:p[675]","/w:document/w:body/w:p[677]","/w:document/w:body/w:p[678]","/w:document/w:body/w:p[680]"],"classification":"future_vision"},{"lessonNumber":"3020","section":"Chapter 20","title":"Chapter 20 · A protocol is a concert of exact participants","headingPointer":"/w:document/w:body/w:p[690]","sourcePointers":["/w:document/w:body/w:p[690]","/w:document/w:body/w:p[693]","/w:document/w:body/w:p[695]","/w:document/w:body/w:p[697]","/w:document/w:body/w:p[699]","/w:document/w:body/w:p[701]"],"classification":"future_vision"},{"lessonNumber":"3021","section":"Chapter 20.1","title":"Chapter 20.1 · Medicine-making as evidence-linked stages","headingPointer":"/w:document/w:body/w:p[703]","sourcePointers":["/w:document/w:body/w:p[703]","/w:document/w:body/w:p[704]","/w:document/w:body/w:tbl[20]","/w:document/w:body/w:p[707]"],"classification":"future_vision"},{"lessonNumber":"3022","section":"Chapter 20.2","title":"Chapter 20.2 · Food provenance across transformation and hand-off","headingPointer":"/w:document/w:body/w:p[709]","sourcePointers":["/w:document/w:body/w:p[709]","/w:document/w:body/w:p[710]","/w:document/w:body/w:tbl[21]","/w:document/w:body/w:p[713]"],"classification":"future_vision"},{"lessonNumber":"3023","section":"Chapter 20.3","title":"Chapter 20.3 · Evidence questions without legal conclusions","headingPointer":"/w:document/w:body/w:p[715]","sourcePointers":["/w:document/w:body/w:p[715]","/w:document/w:body/w:p[716]","/w:document/w:body/w:p[718]","/w:document/w:body/w:p[720]","/w:document/w:body/w:tbl[22]","/w:document/w:body/w:p[723]"],"classification":"future_vision"},{"lessonNumber":"3024","section":"Chapter 20.4","title":"Chapter 20.4 · Assembly keeps component origins","headingPointer":"/w:document/w:body/w:p[725]","sourcePointers":["/w:document/w:body/w:p[725]","/w:document/w:body/w:p[726]","/w:document/w:body/w:tbl[23]","/w:document/w:body/w:p[729]"],"classification":"future_vision"},{"lessonNumber":"3025","section":"Chapter 20.5","title":"Chapter 20.5 · Healthcare context and selective disclosure","headingPointer":"/w:document/w:body/w:p[731]","sourcePointers":["/w:document/w:body/w:p[731]","/w:document/w:body/w:p[732]","/w:document/w:body/w:tbl[24]"],"classification":"future_vision"},{"lessonNumber":"3026","section":"Chapter 20.6 and 20.7","title":"Chapter 20.6–20.7 · One reading, several contextual meanings","headingPointer":"/w:document/w:body/w:p[735]","sourcePointers":["/w:document/w:body/w:p[735]","/w:document/w:body/w:p[736]","/w:document/w:body/w:p[738]","/w:document/w:body/w:tbl[25]","/w:document/w:body/w:p[741]","/w:document/w:body/w:p[743]","/w:document/w:body/w:p[745]","/w:document/w:body/w:p[746]","/w:document/w:body/w:p[751]","/w:document/w:body/w:p[753]","/w:document/w:body/w:tbl[26]","/w:document/w:body/w:p[756]"],"classification":"design_principle"},{"lessonNumber":"3027","section":"Chapter 21","title":"Chapter 21 · Reuse the method, not an untested promise","headingPointer":"/w:document/w:body/w:p[768]","sourcePointers":["/w:document/w:body/w:p[768]","/w:document/w:body/w:p[769]","/w:document/w:body/w:p[771]","/w:document/w:body/w:p[775]","/w:document/w:body/w:tbl[27]"],"classification":"future_vision"},{"lessonNumber":"3028","section":"Chapter 22","title":"Chapter 22 · Read the manual before proposing the driver","headingPointer":"/w:document/w:body/w:p[779]","sourcePointers":["/w:document/w:body/w:p[779]","/w:document/w:body/w:p[780]","/w:document/w:body/w:p[782]","/w:document/w:body/w:tbl[28]","/w:document/w:body/w:p[785]","/w:document/w:body/w:tbl[29]","/w:document/w:body/w:p[787]"],"classification":"design_principle"},{"lessonNumber":"3029","section":"Chapter 23","title":"Chapter 23 · Change one dimension and preserve the evidence","headingPointer":"/w:document/w:body/w:p[791]","sourcePointers":["/w:document/w:body/w:p[791]","/w:document/w:body/w:p[792]","/w:document/w:body/w:p[794]","/w:document/w:body/w:tbl[30]","/w:document/w:body/w:p[796]","/w:document/w:body/w:tbl[31]","/w:document/w:body/w:p[798]","/w:document/w:body/w:p[799]","/w:document/w:body/w:tbl[32]","/w:document/w:body/w:p[802]","/w:document/w:body/w:tbl[33]"],"classification":"future_vision"},{"lessonNumber":"3030","section":"Chapter 24","title":"Chapter 24 · The edge village needs local evidence and authority","headingPointer":"/w:document/w:body/w:p[806]","sourcePointers":["/w:document/w:body/w:p[806]","/w:document/w:body/w:p[807]","/w:document/w:body/w:p[809]","/w:document/w:body/w:p[811]","/w:document/w:body/w:p[814]","/w:document/w:body/w:p[816]","/w:document/w:body/w:p[818]","/w:document/w:body/w:p[820]","/w:document/w:body/w:p[822]","/w:document/w:body/w:tbl[34]","/w:document/w:body/w:p[826]","/w:document/w:body/w:p[828]"],"classification":"future_vision"}]},"surfaceCoverage":[{"routes":["/demo/verify"],"lessons":[],"scope":"Conditional one-time token gateway. Not a bare-page setup exercise; disabled or missing-token states remain explicit"},{"routes":["/","/introduction","/tour","/learn","/access","/resolve","/registry"],"lessons":["2021"],"scope":"Introduction and discovery; protected results require their existing account scope"},{"routes":["/thingsites/create","/demo/build","/demo","/demo/[slug]","/thing-demo/[slug]"],"lessons":["2022"],"scope":"Educational setup and handoff; the public course never allocates a prefix or grants access"},{"routes":["/blueprints","/universe"],"lessons":["2023"],"scope":"Protected library and atlas; inspect authorized model instances without copying private sources"},{"routes":["/thingsites/[slug]","/thingsites/[slug]/[pillar]","/pharma","/pharma/[ordinal]","/pharma/[ordinal]/[pillar]"],"lessons":["2024"],"scope":"Private source overview and five-pillar route templates; detailed named worked example stays protected"},{"routes":["/pillars/p1","/pillars/p2","/pillars/p3","/pillars/p4","/pillars/p5"],"lessons":["2001","2002","2003","2004","2005","2006","2007","2008","2009","2010","2011","2012","2013","2014","2015","2016","2017","2018","2019","2020"],"scope":"Detailed page and control lessons over the fixed anonymous package"},{"routes":["/demo/configure"],"lessons":["2025","2026"],"scope":"Protected browser-local proposal tool; no immutable server-save or execution claim"},{"routes":["/thingsites/[slug]/configure","/pharma/[ordinal]/configure"],"lessons":["2027"],"scope":"Authorized private source-bound save and history review; no public copy of its company record"},{"routes":["/pharma/[ordinal]/samples","/scenarios","/practice"],"lessons":["2028","2029"],"scope":"Separate protected synthetic fixtures and practice; not observations from the anonymous public composition"},{"routes":["/readiness"],"lessons":["2030"],"scope":"Readiness discussion; actual private operational dashboard remains governed"},{"routes":["/admin"],"lessons":[],"scope":"Internal administration reference only, not a client-learning exercise or authorization change"}],"lessons":[{"number":"2021","track":"site","module":"practice","title":"Start at the front door and choose a scope","goal":"Distinguish identity discovery, educational viewing and permission to inspect a private workspace.","why":["The front door helps a human find a context. It does not decide which company owns an identity, and it does not grant an agent access to the records behind a result.","A client needs to know whether they are exploring the fixed anonymous sample or entering a protected source library before making any design decisions."],"model":["A search term is a discovery input, not a new identifier. Preserve the original prefix, key and source assertion returned by the selected record.","The account principal, the selected record and the authority to amend that record are separate facts. A signed-in account is not automatically a company-authorized decision maker."],"steps":[{"action":"Orient yourself in the introduction","control":"Home, Products and the five pillar links","why":"The menu expresses the solution stack, while the introductory page supplies the purpose. Neither proves an implemented physical connection.","how":"Read the five pillar labels and follow the learning link before selecting a protected library. Keep the current easy introduction available as your orientation.","expected":"You can explain what each pillar contributes to one composition.","verify":"Name one record needed at each pillar without naming a company or inventing a key."},{"action":"Compare discovery with exact resolution","control":"Prefix & identity and Resolve context","why":"A display label can lead to several distinct source records. Selecting a label cannot establish equivalence between them.","how":"Use the anonymous P1 resolver for the supplied GIAI. Compare its source occurrences with the same object in P5 rather than treating the result count as a count of machines.","expected":"The sample retains its demonstration prefix and exact existing identity.","verify":"Check the source pointer on every result and retain the non-issued state."},{"action":"Read the access boundary","control":"Account and the private workspace gate","why":"The platform must protect client context while allowing public education to remain useful.","how":"If a protected page refuses access, record that limitation and continue in the anonymous sample. Do not change roles or substitute another customer record to finish an exercise.","expected":"Public education remains available; private records remain scoped.","verify":"A refusal is not evidence that the company has no data, and a successful login is not company authority."}],"machine":{"pointers":["#/P1/prefixEvidence"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["source_prefix","state","allocation_authority_evidence"],"explanation":"Discovery is a human navigation step. An agent still needs the exact retained identity, source occurrence and authorization scope; none is inferred from the search label."},"pitfalls":["Counting matched occurrences as separate physical units.","Using navigation or account ownership as evidence of customer authority."],"exercise":{"prompt":"Draw a short route from introduction to exact sample identity to source evidence.","deliverables":["A five-pillar role description.","The exact sample GIAI and at least one source pointer.","A sentence distinguishing discovery from permission."],"success":["The prefix and identifier are unchanged.","Private access remains unchanged.","No company, installation or execution claim is inferred."]},"question":{"prompt":"What does finding a source record by name establish?","choices":[{"text":"A discovery result that still needs exact identity and authority inspection.","explanation":"Correct. The human label helps navigation; the retained record and its evidence determine context."},{"text":"Ownership of every matching asset.","explanation":"A shared name is not ownership evidence."},{"text":"Permission to edit the company’s records.","explanation":"Editing requires its separate authorized scope."}],"correctIndex":0},"screens":[{"title":"Easy introduction","href":"/learn"},{"title":"Exact sample resolution","href":"/pillars/p1#pillar-workspace"},{"title":"Account scope","href":"/access"}],"sourceNotes":["Authored teaching about the current navigation and protected source boundary. The anonymous resolver searches only its fixed educational model."],"lessonLocator":"/learn/deep-dive/2021","recordReference":"#/lessons/0","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/0","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2022","track":"site","module":"practice","title":"Follow educational setup without registering a company","goal":"Understand the setup, verification and overview pages as an educational handoff, not identity allocation.","why":["Onboarding is where a believable sample can accidentally become an asserted company deployment. The setup must keep those meanings separate.","A role, facility or workflow description is useful before a physical unit is confirmed, but missing assignment and review evidence must remain explicit."],"model":["The fixed demonstration prefix 0614141 comes from the retained sample. It is not a new customer allocation.","Setup describes a proposed participant role and operating context. Issuance, company access, reviewed publication and commissioned execution have separate gates."],"steps":[{"action":"Read the educational route","control":"Build a ThingSite and the demo setup page","why":"The label “build” can describe a local teaching flow or an authorized customer editor; those are not interchangeable.","how":"Open the educational build route if your account is authorized. Read its non-issued and no-access-grant boundary before entering any practice role.","expected":"You understand that the setup uses demonstration context.","verify":"Do not replace the sample prefix with a guessed customer prefix."},{"action":"Review the proposed context","control":"Setup fields and overview handoff","why":"A plausible role or location does not supply allocation or company authority.","how":"Inspect the retained key types and the stated scope. Keep absent authorization, local site binding and identity verification in your exercise notes.","expected":"You have a description of a proposed educational context, not a real installation.","verify":"Check that no “verified unit” or “company approved” conclusion was introduced."},{"action":"Use the overview as a navigation handoff","control":"Demo overview and its pillar links","why":"The overview is useful because the same context can be explored from several pillars. It is not a completion certificate.","how":"Continue to the anonymous public pillar pages. Compare the identity, capability, procedure, environment and graph views without changing their identifiers.","expected":"The five views describe one sample composition.","verify":"Record which evidence is present and which is still missing."}],"machine":{"pointers":["#/P1/prefixEvidence","#/P4/deploymentGates"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["issued","customer_review","deploymentPerformed","executionAuthorized"],"explanation":"Treat setup output as a proposed context. Identity issuance and authorization remain false or unknown; an overview link is not a provenance-bearing customer decision."},"pitfalls":["Treating a successful form as GS1 issuance.","Calling the demonstration namespace a newly allocated company prefix."],"exercise":{"prompt":"Prepare a handoff note for a client moving from the educational setup to P1.","deliverables":["The demonstration scope.","A list of the separate real-customer evidence requirements.","Links to the five anonymous pillar pages."],"success":["No real company is named or assigned.","Unknown authority is still unknown.","The note distinguishes setup from commissioning."]},"question":{"prompt":"Does completing the demo setup create a customer ThingSite allocation?","choices":[{"text":"Yes, because the overview can be opened.","explanation":"Navigation does not allocate an identity."},{"text":"No. It is an educational handoff with separate assignment and authority requirements.","explanation":"Correct. The real customer process requires its own evidence and governed decision."},{"text":"Only if a cloud provider is selected.","explanation":"A design choice cannot create namespace authority."}],"correctIndex":1},"screens":[{"title":"Educational setup · existing access required","href":"/demo/build"},{"title":"Public identity workspace","href":"/pillars/p1#pillar-workspace"}],"sourceNotes":["Setup uses its existing access gate; verification is a conditional one-time-token handoff, not a bare-page setup exercise. Account access remains unchanged."],"lessonLocator":"/learn/deep-dive/2022","recordReference":"#/lessons/1","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/1","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2023","track":"site","module":"practice","title":"Read graphic models and the vocabulary atlas","goal":"Use model selection as a semantic design aid without substituting a model for a particular asset.","why":["A model library helps a learner compare structures and requirements. A particular installed unit still needs its own exact identity and evidence.","The useful question is what a selected vocabulary term or model contributes to the composition, not whether a tile makes the whole configuration compliant."],"model":["Model slots, variants and source packages are separately retained design contexts. A shared technique does not prove interchangeability.","AFO vocabulary, ADM schema selection, derived structural checks and formal SHACL validation are distinct layers. Keep their exact references and results rather than summarizing them as one green badge."],"steps":[{"action":"Open the library under your current scope","control":"Graphic models","why":"The library can include protected supplier and enterprise source context.","how":"Open the gallery only if the existing gate permits it. If not, use the public sample and its methodology states; the exercise does not require wider access.","expected":"You see the permitted model context or an explicit access limit.","verify":"Never select another customer just to bypass a refusal."},{"action":"Compare a model with its source package","control":"Model slot, variant and evidence drill-down","why":"The model name is a human label; the source package and exact references preserve its applicability.","how":"Select a permitted tile. Record its model/version, evidence state, participant requirements and unresolved constraints before considering alternatives.","expected":"A comparison that retains both original contexts.","verify":"Do not relabel one variant’s source data as another variant’s evidence."},{"action":"Separate vocabulary from validation","control":"AFO relationship atlas and Allotrope model & validation context","why":"A relationship map describes semantic context; formal conformance needs an applicable pinned schema/shape and a recorded result.","how":"Trace a term back to its exact retained reference. Compare the public P3 not-run/not-mapped states with a real validation receipt’s required inputs and outputs.","expected":"You can state precisely which modeling and checking layer is demonstrated.","verify":"A tile, graph edge or successful structural check is not an official conformance claim."}],"machine":{"pointers":["#/P3/protocolTemplates/0"],"identifiers":[],"fields":["modelSlot","schemaVersion","sourceSha256","validationState"],"explanation":"A model is a governed reference for describing a composition. An exact physical asset identity and its source evidence remain separate from that model reference."},"pitfalls":["Using a model slot as a serial identity.","Assuming similar inputs and outputs prove hardware compatibility."],"exercise":{"prompt":"Write a model comparison with one unresolved applicability question.","deliverables":["Two separately identified model/version contexts, or one context and an explicit access limit.","Exact source references where supplied.","A list separating mapping, structural checks and formal conformance."],"success":["No asset is flattened into a model name.","No unsupported official term or validation result is invented.","The applicability question remains addressable."]},"question":{"prompt":"What does selecting an ADM tile prove?","choices":[{"text":"That the laboratory uses that instrument.","explanation":"A modeling choice is not an adoption assertion."},{"text":"That all connected assets are compatible.","explanation":"Compatibility needs relationship-specific evidence and tests."},{"text":"That a model context is selected for inspection.","explanation":"Correct. Mapping, formal validation and physical use need separate evidence."}],"correctIndex":2},"screens":[{"title":"Graphic model library · existing access required","href":"/blueprints"},{"title":"Vocabulary atlas · existing access required","href":"/universe?view=atlas"},{"title":"Public methodology states","href":"/pillars/p3#pillar-workspace"}],"sourceNotes":["Teaching follows current protected gallery/atlas navigation and the public sample’s explicit methodology states."],"lessonLocator":"/learn/deep-dive/2023","recordReference":"#/lessons/2","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/2","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2024","track":"site","module":"practice","title":"Read a private ThingSite one page at a time","goal":"Understand the overview and five private pillar pages without merging source records.","why":["A private ThingSite is a scoped deployment of context, not simply a company profile. Its overview must lead to independently inspectable source records.","Different source prefix rows can carry different evidence even when their labels look similar. A convenient main view cannot erase either row."],"model":["The overview summarizes the selected source context. P1–P4 expose particular evidence, and P5 exposes the retained values and relationships.","An exact source pointer is an occurrence locator, not a GS1 key. A containment/reference graph is not automatically a verified physical configuration."],"steps":[{"action":"Enter the authorized worked example","control":"Private worked example","why":"Named source material belongs in the protected learning area.","how":"Use the private course gateway. Existing platform-admin authorization is required; an access-denied page is a valid boundary, not a reason to change permissions.","expected":"A protected source example or an explicit refusal.","verify":"No named content is copied into the anonymous course."},{"action":"Read overview, then P1 through P4","control":"ThingSite sections navigation","why":"Each page answers a different question about the same selected source.","how":"For each page record what is supplied, its original assertion and the current assessment. Keep proposed identifiers and historical notes distinct from assignment and validation.","expected":"A page-by-page evidence inventory.","verify":"Do not transfer a method or driver to a sibling prefix based on its name."},{"action":"Follow one exact source occurrence into P5","control":"Follow this exact record into P5 and its return link","why":"Same-record navigation prevents a label search from substituting a different assertion.","how":"Open a source occurrence, inspect original JSON and relationship provenance, then return to that exact evidence record.","expected":"The same pointer is visible in both views.","verify":"Original fields and unknowns remain intact; source pairing does not imply validation."}],"machine":{"pointers":[],"identifiers":[],"fields":["sourcePointer","assertingActor","authorityEvidence","status","scope","supersessionHistory"],"explanation":"Private original records and derived occurrence relationships stay separately retrievable. This lesson uses no public copy of a protected company record."},"pitfalls":["Treating a primary navigation label as identity equivalence.","Copying historical evidence onto a different prefix row."],"exercise":{"prompt":"Produce a private page-by-page review of one authorized source record.","deliverables":["An overview/P1–P5 inventory.","One exact source occurrence and its P5 return route.","A separate source assertion/current assessment comparison."],"success":["Private material stays private.","Original records are not merged.","Unknown authority and missing transformation evidence are retained."]},"question":{"prompt":"When two source rows have similar names, what should happen to their evidence?","choices":[{"text":"Keep each original row and attribute its evidence separately.","explanation":"Correct. Any cross-link needs its own evidenced relationship and scope."},{"text":"Move all content to the longer prefix.","explanation":"Digit containment cannot establish attribution."},{"text":"Hide the historical row.","explanation":"A historical assessment does not erase the source record."}],"correctIndex":0},"screens":[{"title":"Private worked-example gateway","href":"/learn/deep-dive/private"},{"title":"Public graph practice","href":"/pillars/p5#pillar-workspace"}],"sourceNotes":["This lesson describes the protected source-mirror method without exposing a named company record. The private course preserves historical and current source contexts separately."],"lessonLocator":"/learn/deep-dive/2024","recordReference":"#/lessons/3","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/3","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2001","module":"p1","title":"Resolve an exact identity without inventing a match","goal":"Use the public identity workspace to distinguish a prefix-scoped list of assertions from an exact EPC identity lookup.","why":["An agent needs an address, not a familiar product label.","A result count may describe repeated source assertions about one identity; it is not a count of verified physical units."],"model":["The supplied example prefix is 0614141, retained with ownership unknown. It is not a party identifier; PGLN is banned as a ThingDaddy ID type.","P1 and P2 retain separate assertion occurrences even when their urn values are equal. A source-pointer occurrence and an asset identity answer different questions."],"steps":[{"action":"Open the identity workspace","control":"P1 · Open workspace","why":"Start in the same educational namespace as the lesson.","how":"Open the P1 screen link and scroll to Find an identity. Read the educational source bar before searching.","expected":"The page identifies an educational, non-issued sample using prefix 0614141.","verify":"Confirm the page says real company records are not queried; do not sign in to a private site for this exercise."},{"action":"Inspect the prefix result","control":"Demonstration prefix or exact EPC URN · Resolve context","why":"A prefix scopes assertions but does not identify one physical asset.","how":"Enter 0614141 and select Resolve context. Inspect the listed urn values and their source-pointer labels.","expected":"The educational resolver lists all retained candidate assertion occurrences in this prefix-scoped sample.","verify":"Identify at least two different occurrence pointers. Do not relabel the match count as installed instruments or valid allocations."},{"action":"Resolve the exact cycler address","control":"Demonstration prefix or exact EPC URN · Resolve context","why":"Exact equality prevents a label-based identity substitution.","how":"Replace the input with urn:epc:id:giai:0614141.4 and resolve again. Compare any repeated occurrences carrying that exact urn.","expected":"Only assertions carrying the exact sample GIAI match; repeated assertions can refer to the same address.","verify":"Record each occurrence pointer separately and confirm the full urn, including the leading zero, is unchanged."},{"action":"Test an unknown address","control":"Demonstration prefix or exact EPC URN · Resolve context","why":"A failed lookup should expose uncertainty, not guess a nearby thing.","how":"Search for urn:epc:id:giai:0614141.999999, then restore the exact cycler address.","expected":"The unknown address produces no exact identity in this sample. Restoring the known address restores its assertions.","verify":"Capture both outcomes and confirm the unknown address was not mapped to Thermal cycler by its name."}],"machine":{"pointers":["#/P1/demo_giai","#/P2/modules/0/candidateIdentifier","#/P2/modules/0/identifiers/0","#/P1/prefixEvidence"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["urn","source_prefix","state","issued","allocation_authority_evidence","identity_equivalence_asserted"],"explanation":"The resolver compares exact retained urn strings in the loaded public model. The three example pointers identify three assertions, not three independently verified units. allocation_authority_evidence is null and issued is false."},"pitfalls":["Trimming the leading zero changes the address.","A prefix match is not proof of prefix ownership.","The result links open the public graph; they do not authenticate or allocate a private ThingSite."],"exercise":{"prompt":"Prepare an exact-resolution receipt for the known and unknown addresses.","deliverables":["Input strings and visible outcomes.","The exact known GIAI and three distinct occurrence pointers.","A one-sentence explanation of assertion count versus asset count."],"success":["The unknown lookup remains unknown.","Every copied urn keeps 0614141 exactly.","No issuance, ownership or real installation claim is made."]},"question":{"prompt":"Three source occurrences carry the same sample GIAI. What can you conclude?","choices":[{"text":"Three physical instruments have been verified.","explanation":"Incorrect. An occurrence is a source assertion, not a physical inspection."},{"text":"The same exact identity is asserted in three separately addressable occurrences.","explanation":"Correct. Preserve the occurrences and their evidence without multiplying the physical asset."},{"text":"The occurrences should be merged and their pointers discarded.","explanation":"Incorrect. That would erase assertion provenance needed by agents."}],"correctIndex":1},"screens":[{"title":"P1 exact identity resolver","href":"/pillars/p1#pillar-workspace"},{"title":"Read the complete anonymous package","href":"/api/demo/pillars"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"},{"kind":"standard","label":"GS1 identification keys","href":"https://www.gs1.org/standards/id-keys","classification":"Primary standards reference; not allocation or issuance evidence for this sample"},{"kind":"standard","label":"GS1 EPC Tag Data Standard","href":"https://www.gs1.org/standards/tds","classification":"Primary representation reference; original sample assertions and assignment states remain separate"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2001","recordReference":"#/lessons/4","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/4","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2002","module":"p1","title":"Choose the key role and inspect the assignment","goal":"Compare asset, product-instance and physical-location roles without turning a displayed sample into an issued identifier.","why":["The object’s role determines the applicable key type.","The EPC representation, GS1 element string and assignment state must travel together."],"model":["GIAI identifies the example asset; SGTIN represents a serialized trade-item context; SGLN represents a physical location. PGLN is banned as a ThingDaddy ID type.","The key palette includes 14 supported EPC scheme roles. Its labels are teaching aids, not an assignment service. Original PGLN assertions remain excluded provenance, never active identities.","urn, value and element_string are distinct retained representations. The source prefix remains the namespace context rather than a composed party identifier."],"steps":[{"action":"Select an asset role","control":"GIAI · Individual asset","why":"An asset record must not be replaced by a product-model label.","how":"Select GIAI in the key palette. Read Retained assignment, the full urn, source prefix, key type and GS1 element string.","expected":"The first retained GIAI candidate uses urn:epc:id:giai:0614141.4 and element string (8004)06141414.","verify":"Record the selected assertion source pointer and the non-issued state beside the urn."},{"action":"Inspect another occurrence","control":"Retained assignment","why":"Repeated assertions may use the same identity but retain different source locations.","how":"Open the assignment menu. Choose another cycler GIAI assertion occurrence and compare its source pointer with the first.","expected":"The urn can remain equal while the assertion source pointer changes.","verify":"Explain why equal urn bytes do not authorize deleting one source occurrence."},{"action":"Compare roles","control":"SGTIN · SGLN","why":"A serialized product and physical location are not interchangeable identities.","how":"Select each of these palette buttons in turn and record its urn and role. Read the source prefix independently.","expected":"The representation changes with the selected role while the namespace is still 0614141. PGLN is not offered.","verify":"Confirm PGLN cannot be selected. Do not use an SGLN as a person, organization or machine identity."},{"action":"Copy without assigning","control":"Copy retained EPC URN","why":"Copying a string is not issuing or verifying a key.","how":"Return to GIAI and use Copy retained EPC URN. Paste it into the resolver input and resolve the exact string.","expected":"A successful clipboard action changes the control to Copied; the model remains non-issued.","verify":"Check issued:false and allocation_authority_evidence:null in the package JSON. No new assignment record should be claimed."}],"machine":{"pointers":["#/P1/demo_giai","#/P1/demo_sgtin","#/P1/demo_sgln","#/P1/manufacturerPrefix"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:sgtin:0614141.812345.6789","urn:epc:id:sgln:0614141.41414.41"],"fields":["key_type","role","urn","value","element_string","state","issued","customer_review"],"explanation":"Compare the identity object at each exact pointer. PGLN is excluded by ThingDaddy policy, with no active identity, generation or resolution. The chosen UI scheme and its retained key_type can differ in vocabulary: CPI is the EPC scheme while the fixture records the component key as CPID. Do not silently rewrite either field."},"pitfalls":["The identifier is opaque; product behavior cannot be inferred from its digits.","A successful copy or syntax-shaped display does not establish allocation authority.","Optional logistics and coupon examples do not prove those roles apply to this PCR composition."],"exercise":{"prompt":"Create a three-row role map for GIAI, SGTIN and SGLN, with a separate PGLN exclusion note.","deliverables":["Role, full urn, source pointer and element string for each supported row.","Assignment state and authority evidence for each.","Explain why PGLN is not selectable and original assertions must remain excluded evidence."],"success":["The three supported roles remain distinct.","All assignment evidence stays false or unknown as supplied.","No missing field is filled using a familiar label."]},"question":{"prompt":"What does Copy retained EPC URN establish?","choices":[{"text":"That the string was copied from the selected assertion.","explanation":"Correct. Copying preserves an existing value; it is not allocation or verification."},{"text":"That the selected sample has been issued by an authorized namespace owner.","explanation":"Incorrect. The example remains non-issued and authority evidence is absent."},{"text":"That every key in the palette describes the same physical object.","explanation":"Incorrect. Different schemes address different roles and contexts."}],"correctIndex":0},"screens":[{"title":"P1 key-role and assignment inspector","href":"/pillars/p1#pillar-workspace"},{"title":"Inspect retained identity objects","href":"/api/demo/pillars"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"},{"kind":"standard","label":"GS1 identification keys","href":"https://www.gs1.org/standards/id-keys","classification":"Primary standards reference; not allocation or issuance evidence for this sample"},{"kind":"standard","label":"GS1 EPC Tag Data Standard","href":"https://www.gs1.org/standards/tds","classification":"Primary representation reference; original sample assertions and assignment states remain separate"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2002","recordReference":"#/lessons/5","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/5","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2003","module":"p1","title":"Follow the sensor identity into its component context","goal":"Traverse the retained GIAI-to-CPI-to-parent pattern without erasing the incoming sensor asset identity or inventing an installation event.","why":["A thing can become part of another thing without losing its original identity.","An installed-context proposal and observed physical installation need different evidence."],"model":["The sample sensor GIAI is distinct from its CPI occurrence and from the parent cycler GIAI.","The graph preserves installed-as-context and component-of as separately identified directed assertions.","These example assertions are authored, with unknown authority and null assertion time. This public fixture does not supply an observed EPCIS installation event or replacement history."],"steps":[{"action":"Inspect the component identity","control":"CPI · Component / part","why":"The installed occurrence is not a replacement for the incoming asset.","how":"In P1 choose CPI and inspect the retained thermal sensor context. Record the urn and CPID key-type value exactly as displayed.","expected":"The CPI urn is urn:epc:id:cpi:0614141.414141.41.","verify":"Keep the CPI context separate from both sensor and parent GIAIs in your notes."},{"action":"Open the exact CPI graph context","control":"Lesson link · CPI focused graph","why":"Exact node addressing avoids resolving a similar sensor label.","how":"Open the focused CPI graph link below. Inspect its exact source ID and source occurrence pointer.","expected":"P5 selects the existing CPI node and shows an explicit direct-neighbor viewport subset.","verify":"The selected node is #/P5/nodes/3 in the package and the complete graph count remains 329/231."},{"action":"Traverse the original sensor bond","control":"Original direct relationships · installed as context","why":"The supplier asset identity must survive the new context.","how":"In the CPI inspector open the incoming installed-as-context relationship. Read Subject, Destination, asserting actor, scope and assertion time. Open Subject to inspect the sensor GIAI.","expected":"The source subject is urn:epc:id:giai:0614141.100002; the destination is urn:epc:id:cpi:0614141.414141.41.","verify":"Record relationship GDTI 00900.2 and #/P5/edges/1; authority stays unknown and assertion time stays unknown, not “now”."},{"action":"Traverse to the parent","control":"Original direct relationships · component of · Destination","why":"Parent membership is a typed assertion, not identity equivalence.","how":"Return to the CPI context, open component-of, then inspect its destination cycler.","expected":"The parent is urn:epc:id:giai:0614141.4; relationship GDTI 00900.3 remains separately addressable.","verify":"Show three nodes and two directed relationships in your receipt. State that the fixture proves retained structure, not physical installation."}],"machine":{"pointers":["#/P5/nodes/2","#/P5/nodes/3","#/P5/nodes/1","#/P5/edges/1","#/P5/edges/2","#/P2/modules/1"],"identifiers":["urn:epc:id:giai:0614141.100002","urn:epc:id:cpi:0614141.414141.41","urn:epc:id:giai:0614141.4","urn:epc:id:gdti:0614141.00900.2","urn:epc:id:gdti:0614141.00900.3"],"fields":["a","b","t","id","provenance.sourceId","provenance.assertingActorId","provenance.assertionTime","provenance.authorityState"],"explanation":"The incoming GIAI → CPI → parent GIAI path references original nodes. Do not collapse it into one “sensor” row. Current installation validity, observed event time and supersession history are not supplied here and remain gaps."},"pitfalls":["The word installed in a candidate label is not observed-installation proof.","Do not invent an EPCIS event or removal date because the relationship type suggests a lifecycle.","Do not use a shared prefix or label as evidence of ownership or sensor compatibility."],"exercise":{"prompt":"Write a bond-traversal receipt that would let an agent retrieve both the incoming identity and component context.","deliverables":["All three node IDs and two relationship IDs.","Directed endpoints, source/actor, assertion time and authority states.","The additional observed event, validity and installation evidence needed for a real deployment."],"success":["The sensor GIAI remains recoverable.","The CPI is represented as context, not identity replacement.","Missing temporal or physical evidence remains explicitly unknown."]},"question":{"prompt":"Does the sample installed-as-context edge prove a sensor was physically installed?","choices":[{"text":"Yes, because the graph has an installation-shaped relationship.","explanation":"Incorrect. The edge is fictional authored structure with unknown authority and time."},{"text":"No; it preserves a candidate identity bond, while observed installation evidence remains missing.","explanation":"Correct. Preserve the pattern and the evidence boundary together."},{"text":"No, so the incoming sensor GIAI should be deleted.","explanation":"Incorrect. Missing physical evidence does not justify erasing original identities or safe context."}],"correctIndex":1},"screens":[{"title":"P1 CPI assignment","href":"/pillars/p1#pillar-workspace"},{"title":"Exact CPI and identity-bond graph","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context&from=%23%2FP2%2Fmodules%2F1#pillar-workspace"}],"graph":{"node":"urn:epc:id:cpi:0614141.414141.41","from":"#/P2/modules/1"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"},{"kind":"standard","label":"GS1 identification keys","href":"https://www.gs1.org/standards/id-keys","classification":"Primary standards reference; not allocation or issuance evidence for this sample"},{"kind":"standard","label":"GS1 EPC Tag Data Standard","href":"https://www.gs1.org/standards/tds","classification":"Primary representation reference; original sample assertions and assignment states remain separate"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2003","recordReference":"#/lessons/6","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/6","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2004","module":"p1","title":"Separate service relationships, run bindings and document versions","goal":"Explain GSRN, SRIN, protocol-family GDTI, protocol-version GDTI and configuration GDTI as different identities with different jobs.","why":["An agent must know which exact configuration a service instance concerns.","Versioning a document must not overwrite a service relationship or turn a file hash into a GS1 identity."],"model":["A GSRN addresses a service relationship; SRIN qualifies a particular instance of that relationship using AI 8019. SRIN is not a standalone invented EPC Pure Identity scheme.","The family, exact protocol version, configuration design and service-binding document have separate GDTIs in this sample.","The public anonymous package exposes the binding-document GDTI but does not expose an assigned SRIN value or a service-instance AI 8019 field. Treat that absence as a visible implementation boundary, not a hidden allocation."],"steps":[{"action":"Inspect the service relationship","control":"GSRN · Service relationship","why":"A relationship identity does not by itself authorize an operator.","how":"Choose GSRN in P1. Record the operator relationship urn, assignment state and source assertion pointer.","expected":"The retained GSRN is urn:epc:id:gsrn:0614141.4343434343, non-issued with authority evidence absent.","verify":"Do not infer employment, competence or execution permission from this record."},{"action":"Inspect the document identities","control":"GDTI · Retained assignment · Public package link","why":"Family, version and configuration documents have separate purposes.","how":"In the GDTI assignment menu inspect configurationGdti and serviceBindingGdti. Open the public package link below to inspect protocolFamilyGdti and candidate_workflow_gdti under P3; those two are not entries in this P1 assignment menu.","expected":"Four separate document references remain available through their actual screen and package locations; selecting one does not replace the others.","verify":"Compare #/P3/protocolTemplates/0 protocolFamilyGdti and candidate_workflow_gdti with #/P1/configurationGdti and #/P1/serviceBindingGdti in package JSON."},{"action":"Follow the exact version lineage","control":"Protocol-version focused graph · Original direct relationships","why":"An explicit version-of edge is stronger than a similar title.","how":"Open the protocol-version graph link and inspect version-of-protocol-family, then open its family destination.","expected":"The version urn:epc:id:gdti:0614141.00011.1 points to family urn:epc:id:gdti:0614141.42424.42 through relationship GDTI 00900.9.","verify":"Record #/P5/edges/8 and keep family/version IDs separate. No version is inferred from the display name."},{"action":"Inspect the missing run-instance boundary","control":"Service-binding focused graph · Inspect exact JSON · Public package link","why":"The binding-document GDTI must not be misreported as an SRIN.","how":"Open the binding graph link and inspect the relationship to the exact configuration. Check the public package for an actual SRIN field; note that none is supplied.","expected":"The binding document urn:epc:id:gdti:0614141.00013.1 references configuration urn:epc:id:gdti:0614141.01200.1, but the public record does not assign an SRIN value.","verify":"Write “SRIN binding value not exposed in this public fixture”. Do not generate an urn:epc:id:srin address or invent a run."}],"machine":{"pointers":["#/P1/demo_gsrn","#/P1/serviceBindingGdti","#/P1/configurationGdti","#/P3/protocolTemplates/0/protocolFamilyGdti","#/P3/protocolTemplates/0/candidate_workflow_gdti","#/P5/edges/8","#/P5/edges/11","#/P5/edges/12"],"identifiers":["urn:epc:id:gsrn:0614141.4343434343","urn:epc:id:gdti:0614141.42424.42","urn:epc:id:gdti:0614141.00011.1","urn:epc:id:gdti:0614141.01200.1","urn:epc:id:gdti:0614141.00013.1"],"fields":["key_type","role","urn","t:version-of-protocol-family","t:has-service-relation-instance-record","t:runs-exact-configuration-gdti","SRIN value: not exposed in public fixture"],"explanation":"The graph retains document and service-link structure. For a future authorized run, the SRIN must qualify its parent GSRN and reference the exact configuration; it does not replace either protocol/configuration GDTI. No new key or run is created in this lesson."},"pitfalls":["A GDTI identifying a binding document is not the SRIN itself.","A configuration hash binds bytes but does not replace a typed document identity.","One relationship may have many run instances; do not overwrite its GSRN to represent a new run."],"exercise":{"prompt":"Produce a five-purpose identity map and mark the missing public run-instance field.","deliverables":["GSRN, family GDTI, version GDTI, configuration GDTI and binding-document GDTI.","Two exact directed lineage relationships.","A distinct row for SRIN purpose with public value not exposed."],"success":["Each identity keeps its own purpose.","The SRIN row does not contain an invented EPC scheme or number.","All existing examples remain non-issued, with no recorded experiment execution claimed."]},"question":{"prompt":"Which description of SRIN is correct for this walkthrough?","choices":[{"text":"It is the protocol-version GDTI with a new label.","explanation":"Incorrect. Service-instance and document identities serve different purposes."},{"text":"It is a new EPC urn scheme supplied by the public key palette.","explanation":"Incorrect. This palette does not offer an SRIN EPC scheme, and this public package does not expose an assigned SRIN value."},{"text":"It qualifies a GSRN service instance; the exact configuration and document GDTIs stay separate.","explanation":"Correct. The current public field gap must still be recorded rather than fabricated."}],"correctIndex":2},"screens":[{"title":"P1 service and document roles","href":"/pillars/p1#pillar-workspace"},{"title":"Protocol version and family graph","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00011.1&focus=context#pillar-workspace"},{"title":"Service-binding document graph","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00013.1&focus=context#pillar-workspace"},{"title":"Public package and field boundary","href":"/api/demo/pillars"}],"graph":{"node":"urn:epc:id:gdti:0614141.00013.1"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"},{"kind":"standard","label":"GS1 identification keys","href":"https://www.gs1.org/standards/id-keys","classification":"Primary standards reference; not allocation or issuance evidence for this sample"},{"kind":"standard","label":"GS1 EPC Tag Data Standard","href":"https://www.gs1.org/standards/tds","classification":"Primary representation reference; original sample assertions and assignment states remain separate"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2004","recordReference":"#/lessons/7","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/7","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2005","module":"p2","title":"Read a component as an evidenced record, not a product card","goal":"Use the P2 component library to connect a selected source occurrence, candidate identity and exact graph record.","why":["A component label alone cannot identify a physical unit.","Every proposed capability must remain connected to its evidence and assessment."],"model":["The eight component records include instruments, component contexts and an edge host. They are not eight verified installed units.","candidateIdentifier describes the proposed typed address; physicalUnitVerification remains not-performed and hardwareCompatibility unknown.","The evidence object supplies an authored source locator and scope, not an external installation certificate."],"steps":[{"action":"Open the full component list","control":"Components","why":"The category count describes retained records, not commissioning.","how":"Open P2 and select Components. Read the count, then inspect Thermal cycler.","expected":"Eight component records are listed; the detail contains the exact candidate GIAI and educational state.","verify":"Record #/P2/modules/0 as the source occurrence and do not replace it with a model name."},{"action":"Search without changing identity","control":"Search Components","why":"Search is presentation filtering, not a new source mapping.","how":"Search for sensor and select Thermal sensor. Compare its CPI context with the cycler GIAI, then clear the search.","expected":"The filtered list changes while original component records and identifiers remain unchanged.","verify":"The sensor occurrence is #/P2/modules/1 even though it is the first visible filtered result; do not record filtered index 0 as its source index."},{"action":"Read source-to-candidate context","control":"Evidence locator · What / How / Why","why":"The evidence and derived representation must stay visibly distinguishable.","how":"Read the authored evidence locator, selected identity and compact explanation. Note which fields establish context and which are unknown.","expected":"The UI keeps source occurrence, identity and authored evidence separately readable.","verify":"Verify allocation authority is absent and no native device support or observed installation was added by the explanation."},{"action":"Inspect and export the same exact record","control":"Open this exact record in P5 · Download this source record","why":"A reviewer should be able to reproduce the selected occurrence.","how":"Open the selected record in P5; return to P2 and download its source record. Read the JSON wrapper and record fields.","expected":"The graph selects the original exact node. The P2 export carries sourcePackage, sourcePrefix, submissionSha256 and the original record.","verify":"Compare the export record.candidateIdentifier.urn with the P5 exact ID and record.evidence.sourceLocator with the visible locator."}],"machine":{"pointers":["#/P2/modules/0","#/P2/modules/1","#/P2/modules/1/candidateIdentifier","#/P2/modules/1/evidence","#/P5/nodes/3"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:cpi:0614141.414141.41"],"fields":["name","role","candidateIdentifier","physicalUnitVerification","hardwareCompatibility","evidence.sourceLocator","evidence.assertionScope"],"explanation":"Library search preserves the original index used by the exact-occurrence link. The export wrapper is a teaching download around the original record, not an installation or driver-test receipt."},"pitfalls":["A filtered row number is not a source occurrence pointer.","Eight records is not eight independently verified physical devices.","The word candidate must not disappear when a source record is copied into another view."],"exercise":{"prompt":"Create one component review receipt using the thermal sensor record.","deliverables":["The exact CPI, original #/P2/modules/1 pointer and evidence locator.","A saved source-record JSON with the package SHA.","A list of unresolved physical-unit and compatibility assessments."],"success":["The export and P5 selection resolve to the same exact candidate address.","The original source occurrence is retained through filtering.","No transport, physical inspection or approval is claimed."]},"question":{"prompt":"A search makes Thermal sensor the first visible item. Which pointer identifies its original record?","choices":[{"text":"#/P2/modules/1","explanation":"Correct. The original array occurrence stays stable when the viewport is filtered."},{"text":"#/P2/modules/0 because it is now first on screen","explanation":"Incorrect. Screen order is not source occurrence identity."},{"text":"The text Thermal sensor is sufficient","explanation":"Incorrect. A label is not an exact machine address or provenance pointer."}],"correctIndex":0},"screens":[{"title":"P2 component browser and evidence","href":"/pillars/p2#pillar-workspace"},{"title":"Selected thermal-sensor context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context&from=%23%2FP2%2Fmodules%2F1#pillar-workspace"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2005","recordReference":"#/lessons/8","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/8","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2006","module":"p2","title":"Inspect material roles and retain missing lot evidence","goal":"Read the material/BOM list while preserving exact candidate instances, unknown quantities and distinct controls.","why":["Materials and controls are participants in a configuration, not decorative inventory.","A plausible reagent name does not establish a validated lot, expiry, dose or compatibility."],"model":["The public list contains eleven materials/BOM records. Most use sample SGTINs; the reusable rack uses GRAI.","quantity, lot and expiry are null. compatibilityState is unknown.","The positive control and no-template control are separate material-role records, not observed positive or negative measurements."],"steps":[{"action":"Open the BOM roles","control":"Materials & BOM","why":"Material instances need their own identities and evidence.","how":"Select Materials & BOM in P2. Inspect PCR plate, then compare it with Reusable rack.","expected":"The plate has an SGTIN candidate and the reusable rack a GRAI candidate; both are non-issued.","verify":"Record #/P2/bom/0 and #/P2/bom/10, without treating either name as compatibility proof."},{"action":"Keep the controls separate","control":"Search Materials & BOM","why":"A positive-control role and a no-template-control role cannot be merged.","how":"Search for control. Select Positive control and No-template control in turn and copy the full candidate urns into separate rows.","expected":"Two original records remain separately selectable, with different candidate IDs and original pointers.","verify":"Record #/P2/bom/6 and #/P2/bom/7; no measured signal or assay result is displayed."},{"action":"Inspect fields not promoted by the visible summary","control":"Download this source record","why":"Omitted summary fields must not become invented defaults.","how":"Download one control source record. Inspect quantity, lot, expiry and compatibilityState in its record object.","expected":"The first three values are null and compatibilityState is unknown.","verify":"Write unknown rather than zero, an empty lot string, a guessed expiry date or a default material quantity."},{"action":"Open the exact material context","control":"Open this exact record in P5","why":"The graph can expose how this material is referenced by protocol steps.","how":"From the selected control record open P5 and inspect its retained direct relationships. Read each relationship type and exact step destination/source.","expected":"P5 uses the exact SGTIN node and authored step-participant relationships.","verify":"Keep relationship provenance and unknown authority attached; do not convert references into an assay approval."}],"machine":{"pointers":["#/P2/bom/0","#/P2/bom/6","#/P2/bom/7","#/P2/bom/10"],"identifiers":["urn:epc:id:sgtin:0614141.000101.1","urn:epc:id:sgtin:0614141.000102.1","urn:epc:id:sgtin:0614141.000108.1","urn:epc:id:grai:0614141.00301.1"],"fields":["candidateIdentifier.urn","quantity","lot","expiry","compatibilityState","evidence"],"explanation":"The downloadable original record exposes null fields that the small UI summary does not render as measured values. Preserve explicit unknowns when building a downstream material requirement table."},"pitfalls":["A control role is not a control result.","Missing quantity is not zero quantity.","A rack and reaction-container label cannot establish fit, contamination control or physical compatibility."],"exercise":{"prompt":"Make a material readiness checklist for plate, rack and both controls.","deliverables":["Four exact identities with original source pointers.","Unknown quantity/lot/expiry and compatibility fields.","Specific evidence requests needed before a real site could select these materials."],"success":["Positive and no-template controls remain separate.","No missing value is invented.","The checklist is a design review, not scientific instructions or product-performance evidence."]},"question":{"prompt":"What does lot:null in a control record mean?","choices":[{"text":"Use any available lot because the material role is present.","explanation":"Incorrect. Role presence does not supply lot or approval evidence."},{"text":"The lot information is not supplied and must remain an explicit gap.","explanation":"Correct. Unknown data stays unknown until attributable evidence is added."},{"text":"The lot number is zero.","explanation":"Incorrect. Null is not a numeric zero or a physical lot identifier."}],"correctIndex":1},"screens":[{"title":"P2 materials/BOM and record export","href":"/pillars/p2#pillar-workspace"},{"title":"Positive-control graph context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Asgtin%3A0614141.000102.1&focus=context&from=%23%2FP2%2Fbom%2F6#pillar-workspace"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2006","recordReference":"#/lessons/9","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/9","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2007","module":"p2","title":"Separate illustrative setting values from approved parameters","goal":"Inspect setting definitions, units and source ranges without treating them as an approved assay procedure or an instrument setting command.","why":["A parameter needs its identity, unit, applicability and approval state.","A value can be syntactically numeric while scientifically inapplicable or unapproved."],"model":["Three setting records describe illustrative extension target, reaction volume and replicate count.","The displayed values 68°C, 10µL and 3 are fictional teaching values, not laboratory recommendations.","minimum, maximum and increment belong to the authored setting design; approvedForUse is false and protocolScope educational-design-only."],"steps":[{"action":"Read the setting with its unit","control":"Settings · Illustrative extension target","why":"A naked number is not a complete parameter definition.","how":"Select Settings, then Illustrative extension target. Read value, unit, protocol scope, identity and source occurrence.","expected":"The source record is #/P2/configurationSettings/0 with value 68 and unit °C.","verify":"Label the value illustrative and unapproved; do not instruct an instrument or a scientist to use it."},{"action":"Compare a different parameter kind","control":"Illustrative reaction volume · Illustrative replicate count","why":"Physical units and counts must not be confused.","how":"Select the other two setting records and note their units and exact GDTIs.","expected":"The volume uses µL and replicate count uses count; both retain separate definitions.","verify":"Record #/P2/configurationSettings/1 and /2 with their own identities rather than one generic settings row."},{"action":"Read the full constraint fields","control":"Download this source record","why":"The summary shows values but does not establish validation.","how":"Download the extension-target record and inspect minimum, maximum, increment, approvedForUse and protocolScope.","expected":"The retained range is 65–72°C with increment 1, but approvedForUse remains false.","verify":"Explain that an authored range is not an approved biological procedure, a calibrated device range or a SHACL conformance verdict."},{"action":"Trace the definition into graph context","control":"Open this exact record in P5","why":"A setting definition should remain connected to the steps that reference it.","how":"Open the exact setting in P5 and inspect uses-setting-definition relationships.","expected":"The original setting GDTI remains distinct from the protocol step GDTI and cycler GIAI.","verify":"Save one directed edge ID and the unknown-authority provenance. Do not state that the value was applied to hardware."}],"machine":{"pointers":["#/P2/configurationSettings/0","#/P2/configurationSettings/1","#/P2/configurationSettings/2","#/P3/protocolTemplates/0/ordered_steps/4"],"identifiers":["urn:epc:id:gdti:0614141.00301.1","urn:epc:id:gdti:0614141.00302.1","urn:epc:id:gdti:0614141.00303.1"],"fields":["value","unit","minimum","maximum","increment","protocolScope","approvedForUse"],"explanation":"Setting definition, parameter requirement and measured observation are different record roles. These records have teaching defaults; application-specific protocol requirements and validation remain unresolved."},"pitfalls":["Do not turn illustrative values into medical or experimental guidance.","A displayed setting is not a current measured temperature or volume.","The read-only library has no parameter-apply control; this lesson does not create one."],"exercise":{"prompt":"Produce a three-row setting definition sheet and a readiness gap list.","deliverables":["Exact GDTI, value/unit, source pointer and authored range for each.","Approval and applicability states.","The evidence needed before a site could approve or apply a parameter."],"success":["All values are identified as illustrative.","No command or measurement is claimed.","Definitions, application requirements and observations remain separate."]},"question":{"prompt":"Does a setting falling inside its displayed range prove assay validity?","choices":[{"text":"Yes, range membership is equivalent to scientific validation.","explanation":"Incorrect. The range is authored demo metadata and no application validation has run."},{"text":"Yes, because the record has a GDTI.","explanation":"Incorrect. A document identity does not approve its contents."},{"text":"No; unit, applicability, approved procedure and validation evidence are still needed.","explanation":"Correct. The numeric check and scientific approval are distinct."}],"correctIndex":2},"screens":[{"title":"P2 illustrative setting definitions","href":"/pillars/p2#pillar-workspace"},{"title":"Exact extension-setting context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00301.1&focus=context&from=%23%2FP2%2FconfigurationSettings%2F0#pillar-workspace"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2007","recordReference":"#/lessons/10","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/10","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2008","module":"p2","title":"Read candidate operations and the missing transport boundary","goal":"Distinguish a proposed capability description from a tested MHS/SiLA driver, device endpoint or executable command.","why":["An agent can plan using capability requirements before hardware access exists.","Planning metadata must not inherit permission or proof of native protocol support."],"model":["The library contains six authored operation descriptions. Their state is candidate_non_executable.","An operation’s GDTI identifies its definition; inputs/outputs describe required context, not a live request/response trace.","No native or adapter transport, endpoint, credentials or hardware test is supplied; executable and executionAuthorized are false."],"steps":[{"action":"Select the capability category","control":"Driver operations","why":"Operation count is definition coverage, not tested-driver coverage.","how":"Open Driver operations in P2. Select Describe a thermal-cycle request.","expected":"The definition has operationClass proposeThermalCycle, a candidate GDTI and a no-tested-transport boundary.","verify":"Record #/P2/mhsSilaDriver/operations/2 and do not relabel this as Start run."},{"action":"Inspect its declared inputs and output","control":"Download this source record","why":"A request requires context and approval evidence, not just an operation name.","how":"Download the operation and read inputs, outputs, componentRoles, transportBoundary and executionAuthorized.","expected":"Inputs include Reaction layout and Approved profile required; the output is a Thermal-cycle request draft.","verify":"There is no measured amplification curve, command receipt or native endpoint in this record."},{"action":"Compare export and inspection definitions","control":"Describe a result export · Describe temperature / lid checks","why":"Different capability purposes must keep separate identities and evidence requirements.","how":"Inspect these two operation records and download either one. Compare their operationClass, inputs and outputs.","expected":"A result-export description is distinct from required sensor/interlock evidence.","verify":"Do not count required sensor evidence as sensors responding or a result package definition as actual measured results."},{"action":"Read the driver-wide boundary","control":"MHS / SiLA capability model banner","why":"A library-wide missing transport affects every proposed hardware operation.","how":"Scroll to the driver banner and read Native SiLA support and transportBoundary. Check the public package driver fields.","expected":"Native support is not asserted; driverHardwareState is unknown; no physical dispatch has been supplied.","verify":"Write a transport-readiness checklist instead of attempting a hardware call or claiming a connected driver."}],"machine":{"pointers":["#/P2/mhsSilaDriver","#/P2/mhsSilaDriver/operations/2","#/P2/mhsSilaDriver/operations/3","#/P2/mhsSilaDriver/operations/5"],"identifiers":["urn:epc:id:gdti:0614141.00200.1","urn:epc:id:gdti:0614141.00212.1","urn:epc:id:gdti:0614141.00213.1","urn:epc:id:gdti:0614141.00215.1"],"fields":["operationClass","inputs","outputs","componentRoles","transportBoundary","nativeSilaSupport","driverHardwareState","executable","executionAuthorized"],"explanation":"These are read-only definitions for design review. A real executable driver needs an evidenced interface, bound endpoint, adapter/native implementation, qualified tests and scoped authorization. None is established by selecting a record."},"pitfalls":["Never infer native SiLA support from a capability label.","Do not rename a request draft as an executed experiment.","A test plan, generated driver document and successful hardware test are different milestones."],"exercise":{"prompt":"Draft a non-executable capability review for one operation.","deliverables":["Exact definition ID, source pointer, input/output list and referenced component roles.","Explicit missing endpoint, adapter, credentials, acceptance tests and authority.","A safe next step limited to evidence collection and review."],"success":["The review makes no hardware-dispatch claim.","Transport and authorization gates remain separate.","All original operation definitions remain unchanged."]},"question":{"prompt":"What can Describe a thermal-cycle request do in this public library?","choices":[{"text":"Dispatch a thermal cycle through a tested adapter.","explanation":"Incorrect. No adapter or hardware transport has been supplied or tested."},{"text":"Describe the context and draft output needed for a future governed request.","explanation":"Correct. It is an authored, non-executable operation definition."},{"text":"Validate an assay because the operation name contains thermal-cycle.","explanation":"Incorrect. A label does not provide application or scientific validation."}],"correctIndex":1},"screens":[{"title":"P2 driver operation definitions","href":"/pillars/p2#pillar-workspace"},{"title":"Exact thermal-cycle definition in P5","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00212.1&focus=context&from=%23%2FP2%2FmhsSilaDriver%2Foperations%2F2#pillar-workspace"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2008","recordReference":"#/lessons/11","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/11","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2009","module":"p3","title":"Read the ordered method without claiming a run","goal":"Follow eight identified step definitions and distinguish a layout change from a protocol-order change or executed procedure.","why":["A workflow needs ordered, addressable steps rather than an unstructured paragraph.","A human-friendly diagram is a projection of retained definitions and directed relationships."],"model":["The one retained protocol template is Illustrative PCR composition, with eight ordered_steps and ordinal 1–8.","Each step has a distinct stepDefinitionGdti, procedureDetail and evidence locator.","The public P3 page is read-only. Compact flow changes presentation; it does not reorder definitions, add steps or execute them."],"steps":[{"action":"Read the complete sequence","control":"Choose the retained protocol · Show every step","why":"The full sequence is needed before inspecting one participant.","how":"Open P3. Read all eight step cards from Identify & scope to Package results & provenance. If the track is compact, choose Show every step.","expected":"All eight definitions remain available in their original ordinal order.","verify":"Record ordinals1,6 and 8 with their titles; do not treat diagram position as a new ordering assertion."},{"action":"Inspect the selected definition","control":"Propose the PCR run · Procedure & evidence","why":"A step title must be anchored to the exact definition.","how":"Select Propose the PCR run and read its retained procedure, step GDTI and evidence locator.","expected":"The selected definition is urn:epc:id:gdti:0614141.00105.1; the procedure explicitly says no instrument command is dispatched and no amplification result is generated.","verify":"Record #/P3/protocolTemplates/0/ordered_steps/5, not /6: source arrays are zero-indexed while the displayed ordinal is 6."},{"action":"Change the view, not the method","control":"Compact flow · Show every step","why":"UI convenience must not silently remove or reorder source definitions.","how":"Toggle Compact flow and inspect the step-track behavior, then restore Show every step.","expected":"The same eight source definitions and original order remain; only presentation changes.","verify":"Re-select step 6 and confirm its GDTI and procedure are unchanged."},{"action":"Inspect order as a typed assertion","control":"Open selected step in P5 · Original direct relationships","why":"Explicit graph relationships make ordering inspectable to agents.","how":"Open the exact selected step in P5 and inspect a precedes-step relationship to an adjacent definition.","expected":"Both step endpoints and the relationship ID remain distinct authored records.","verify":"Read original a, b and t fields in exact JSON; a visible arrow is not evidence that either step ran."}],"machine":{"pointers":["#/P3/protocolTemplates/0","#/P3/protocolTemplates/0/ordered_steps/0","#/P3/protocolTemplates/0/ordered_steps/5","#/P3/protocolTemplates/0/ordered_steps/7","#/P5/edges/187","#/P5/edges/205"],"identifiers":["urn:epc:id:gdti:0614141.00100.1","urn:epc:id:gdti:0614141.00105.1","urn:epc:id:gdti:0614141.00107.1"],"fields":["ordinal","stepDefinitionGdti","procedureDetail","evidence.sourceLocator","t:precedes-step"],"explanation":"Step definitions are documents, not run events. The displayed step 5→step 6 edge is index 187 and step 6→step 7 edge index 205 in this pinned graph; indices are zero-based source locations, while relationship GDTIs remain the exact addresses."},"pitfalls":["Displayed ordinal 6 is source-array index 5.","Compact flow is not protocol reordering.","The phrase Propose the PCR run describes a request design, not observed amplification or execution."],"exercise":{"prompt":"Produce an order-and-definition receipt for three adjacent steps.","deliverables":["Displayed ordinal, exact step GDTI and zero-based source pointer for each.","Two exact directed precedes-step edges.","A screenshot pair before/after presentation toggle."],"success":["The order and source identities remain unchanged.","Definition and execution-event roles are separated.","No scientific run or approval is claimed."]},"question":{"prompt":"What changes when Compact flow is selected?","choices":[{"text":"The retained protocol order is rewritten.","explanation":"Incorrect. This public control changes only presentation."},{"text":"The graphical view changes while all original step definitions remain.","explanation":"Correct. The source protocol and graph are preserved."},{"text":"The method is executed in a simulator.","explanation":"Incorrect. No simulator execution is performed by this control."}],"correctIndex":1},"screens":[{"title":"P3 complete method and step tabs","href":"/pillars/p3#pillar-workspace"},{"title":"Select exact step 6 in P3","href":"/pillars/p3?step=urn%3Aepc%3Aid%3Agdti%3A0614141.00105.1#pillar-workspace"},{"title":"Step6 order and participant graph","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00105.1&focus=context&from=%23%2FP3%2FprotocolTemplates%2F0%2Fordered_steps%2F5#pillar-workspace"}],"graph":{"node":"urn:epc:id:gdti:0614141.00105.1","from":"#/P3/protocolTemplates/0/ordered_steps/5"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2009","recordReference":"#/lessons/12","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/12","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2010","module":"p3","title":"Open the exact participant and role behind a step","goal":"Use the Participants & materials tab to carry the same exact step, participant and directed assertion into P5 and back.","why":["Role labels alone do not establish an identity binding.","Exact cross-pillar continuity lets an agent inspect the referenced unit/context and its assertion provenance."],"model":["componentRoles and bomRolesUsed are retained teaching labels; the exact participant list is derived only from directed references-step-participant graph assertions.","The selected run-step list includes a cycler GIAI, component CPIs, material SGTINs and separate operator/configuration-agent GSRNs.","The link carries node, from and via. The receiver verifies the exact step pointer and directed relationship instead of matching a name."],"steps":[{"action":"Open the intended step","control":"Select exact step 6 in P3 · Participants & materials","why":"Different steps reference different participants.","how":"Open the exact step 6 screen link and select Participants & materials. Read both the role chips and Exact participant & service-role assertions.","expected":"The selected procedure occurrence is #/P3/protocolTemplates/0/ordered_steps/5.","verify":"Do not use a similarly named card from another step as a substitute."},{"action":"Inspect the exact cycler assertion","control":"Thermal cycler asset in the exact participant list","why":"The participant node and the step-participant assertion are separate objects.","how":"Select the exact cycler entry. Read Same object. Exact context in P5 and the incoming source occurrence and directed assertion ID.","expected":"The target node is urn:epc:id:giai:0614141.4; via is urn:epc:id:gdti:0614141.00900.190.","verify":"Record #/P5/edges/189 and verify a is the selected step GDTI and b is the exact cycler GIAI."},{"action":"Inspect service roles without granting permission","control":"Return to the same protocol step · Operator service relationship","why":"A service role must remain distinct from the physical asset and authorization.","how":"Return to step 6, reopen Participants & materials and select the operator service relationship. Inspect its exact GSRN and authored relationships.","expected":"The operator node is urn:epc:id:gsrn:0614141.4343434343; its record does not establish employment or execution permission.","verify":"Read unknown authority and null/unknown time. Do not translate “referenced” into “authorized”."},{"action":"Verify reversible continuity","control":"Return to the same protocol step","why":"A drill-down should preserve the original learning context.","how":"Use the P5 return link. Confirm the selected step title and source occurrence before opening another participant.","expected":"P3 selects the original exact step definition rather than its first/default step.","verify":"Compare the before/after GDTI and pointer. The tab may return to its default Procedure & evidence; re-open Participants & materials explicitly."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps/5","#/P5/edges/189","#/P5/nodes/1","#/P5/nodes/23"],"identifiers":["urn:epc:id:gdti:0614141.00105.1","urn:epc:id:giai:0614141.4","urn:epc:id:gsrn:0614141.4343434343","urn:epc:id:gdti:0614141.00900.190"],"fields":["node query parameter","from query parameter","via query parameter","a","b","t","provenance"],"explanation":"The query is a navigation request, not an identity assertion. Only an existing directed step-to-participant edge qualifies. Unknown parameters, mismatched endpoints and other source lanes are rejected within this public model."},"pitfalls":["A role chip cannot by itself resolve an exact asset.","Do not infer compatibility, installation, ownership or permission from a step-participant reference.","The return link restores the exact definition, not every transient tab or scroll setting."],"exercise":{"prompt":"Trace one physical participant and one service role from step 6 to P5 and back.","deliverables":["Two target IDs, exact from pointer and via relationship IDs.","Original edge endpoint/provenance fields.","A return-check screenshot showing the exact step selected."],"success":["Both target nodes come from retained directed assertions.","No join is based on a label.","The original step GDTI remains the return address."]},"question":{"prompt":"Why does the participant link carry a via relationship ID?","choices":[{"text":"To establish ownership of the participant.","explanation":"Incorrect. Navigation and reference assertions do not prove ownership."},{"text":"To replace the participant’s original identity.","explanation":"Incorrect. The participant and relationship both keep their exact identities."},{"text":"To validate and inspect the original directed step-to-participant assertion.","explanation":"Correct. Its provenance is available separately from the target node."}],"correctIndex":2},"screens":[{"title":"P3 exact step 6 and participant controls","href":"/pillars/p3?step=urn%3Aepc%3Aid%3Agdti%3A0614141.00105.1#pillar-workspace"},{"title":"Cycler context from step 6 assertion","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context&from=%23%2FP3%2FprotocolTemplates%2F0%2Fordered_steps%2F5&via=urn%3Aepc%3Aid%3Agdti%3A0614141.00900.190#pillar-workspace"}],"graph":{"node":"urn:epc:id:giai:0614141.4","from":"#/P3/protocolTemplates/0/ordered_steps/5","via":"urn:epc:id:gdti:0614141.00900.190"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2010","recordReference":"#/lessons/13","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/13","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2011","module":"p3","title":"Keep procedure, evidence, decisions and exceptions together","goal":"Review a step’s source statement and constraints while distinguishing expected outputs from observations and approval decisions.","why":["A procedure needs requirements, exceptions and evidence, not only its happy-path action.","The same source occurrence must support every tab so a reader can reproduce the review."],"model":["procedureDetail preserves the authored instruction. evidence identifies its source locator and fictional scope.","decisionRules, qualityChecks and exceptionHandling remain distinct arrays.","expectedOutputs names definitions or expected artifacts; it does not assert that a measured result exists."],"steps":[{"action":"Read the actual instruction","control":"Review controls & exceptions · Procedure & evidence","why":"Begin with what the retained source actually says.","how":"In P3 select step 7, Review controls & exceptions. Read its instruction, GDTI and evidence locator.","expected":"The selected record is #/P3/protocolTemplates/0/ordered_steps/6 and step GDTI 00106.1.","verify":"Copy the locator as a locator, not an external laboratory record or historical execution receipt."},{"action":"Inspect the required roles and expected records","control":"Participants & materials","why":"Expected control evidence is not an observed control result.","how":"Switch to Participants & materials. Read exact material and service references plus Expected outputs.","expected":"Referenced controls and output definitions remain separate identities.","verify":"State which displayed records are definitions and which actual observations are not present."},{"action":"Read the exception path","control":"Checks & decisions","why":"Failures and missing evidence must affect the proposed action.","how":"Read decisions, quality checks and exception handling. Identify the instruction to hold a proposed action when exact site evidence is missing.","expected":"The step retains a review/hold boundary rather than fabricating a successful result.","verify":"Record at least one requirement and one exception path, with their array pointers in the selected step."},{"action":"Inspect the exact step source","control":"Open selected step in P5 · Inspect exact JSON · Public package link","why":"The graph definition and full procedure record are complementary views.","how":"Inspect the step node in P5, then read the package step object for full arrays. Compare the source ID and zero-based occurrence.","expected":"P5 exposes exact identity and relationship provenance; the package retains the detailed procedure/check arrays.","verify":"Do not claim the small graph node JSON contains all protocol text. Retain both source locations in your receipt."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps/6","#/P3/protocolTemplates/0/ordered_steps/6/procedureDetail","#/P3/protocolTemplates/0/ordered_steps/6/decisionRules","#/P3/protocolTemplates/0/ordered_steps/6/qualityChecks","#/P3/protocolTemplates/0/ordered_steps/6/exceptionHandling","#/P3/protocolTemplates/0/ordered_steps/6/expectedOutputs"],"identifiers":["urn:epc:id:gdti:0614141.00106.1"],"fields":["procedureDetail","evidence","decisionRules","qualityChecks","exceptionHandling","requiredInputRoles","expectedOutputs"],"explanation":"An output definition, a required observation, a measured observation and a reviewer decision must not be flattened into one “result”. This lesson reviews authored procedure context only."},"pitfalls":["An expected output is not evidence that it was produced.","The graph node is not a replacement for the source step object.","A review rule is not a completed reviewer approval."],"exercise":{"prompt":"Write a readiness review for step 7, including its failure path.","deliverables":["Selected definition identity and evidence locator.","One procedure requirement, one quality check and one exception-handling statement.","An explicit list of missing observed control data and approvals."],"success":["The same exact step supports all notes.","Expected and observed records remain distinct.","No assay validity or control-performance claim is made."]},"question":{"prompt":"The page lists an expected output record. What does that establish?","choices":[{"text":"The definition describes what a future step should produce.","explanation":"Correct. Actual production needs a separately recorded observation or execution receipt."},{"text":"The instrument already generated the result.","explanation":"Incorrect. No physical command or measured result is supplied by this fixture."},{"text":"The result has passed a reviewer’s approval.","explanation":"Incorrect. Output definitions and approval evidence are separate."}],"correctIndex":0},"screens":[{"title":"Select the control-review definition","href":"/pillars/p3?step=urn%3Aepc%3Aid%3Agdti%3A0614141.00106.1#pillar-workspace"},{"title":"Full procedure/check source arrays","href":"/api/demo/pillars"}],"graph":{"node":"urn:epc:id:gdti:0614141.00106.1","from":"#/P3/protocolTemplates/0/ordered_steps/6"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2011","recordReference":"#/lessons/14","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/14","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2012","module":"p3","title":"Read ADM, AFO and SHACL states precisely","goal":"Distinguish model applicability, ontology mapping, published-shape validation and custom structural checks.","why":["Standards vocabulary needs exact versioned references and measured validation results.","A populated diagram or closed graph is not formal conformance or scientific approval."],"model":["ADM-046 is a candidate model-slot label here; governedModel.applicabilityState is unassessed, revision and schemaId are null.","The protocol AFO term status is not-mapped. Published ADM schema validation is not-run; published SHACL valueState is unknown.","ThingDaddy custom checks cover educational structural invariants only and conformanceClaim is false."],"steps":[{"action":"Read the model context","control":"Allotrope model & validation context · Allotrope ADM schema","why":"A candidate label must not stand in for a pinned published model.","how":"Open P3 and scroll to Keep semantics and validation inspectable. Read the ADM card and its requirement.","expected":"The page reports not-run and asks for an applicable published schema/revision before validation.","verify":"In package JSON confirm governedModel.revision:null, schemaId:null and applicabilityState:unassessed."},{"action":"Inspect the ontology gap","control":"AFO method binding","why":"Mapping needs exact ontology terms, not similar words.","how":"Read the AFO card and compare its status with the selected protocol object.","expected":"The status remains not-mapped and the requirement asks for exact published AFO URIs.","verify":"Do not create an ontology URI from the displayed method title or claim mapping coverage from labels."},{"action":"Separate published and custom validation","control":"SHACL validation","why":"Custom graph checks do not inherit published-shape authority.","how":"Read Published Allotrope shape and ThingDaddy derived checks separately. Open the package and read the retained custom checks.","expected":"Published-shape validation has not run; structural-demo-checks-only reports conformance claim false.","verify":"Record the two validation states in different rows with their own source pointers."},{"action":"Prepare evidence-backed next steps","control":"Public package link · P3 open requirements count","why":"Gaps should guide safe work without manufacturing a pass.","how":"Inspect typedGaps alongside validation objects and list the exact schema, terms, shapes, engine/version and result receipts needed next.","expected":"The gap list remains explicit; no approval, driver test or physical execution becomes true.","verify":"Your readiness plan must retain the original unknown/not-run states until actual evidence is recorded."}],"machine":{"pointers":["#/P3/governedModel","#/P3/protocolTemplates/0/method_AFO_term_status","#/P3/publishedAllotropeSchemaValidation","#/P3/publishedAllotropeShapeValidation","#/P3/thingDaddyCustomShaclValidation","#/P3/typedGaps"],"identifiers":["urn:epc:id:gdti:0614141.00011.1"],"fields":["applicabilityState","revision","schemaId","method_AFO_term_status","state","valueState","conformanceClaim","checks"],"explanation":"Schema selection, ontology mapping, constraint execution and scientific validation are distinct. The public fixture supplies structural demonstration context; it does not supply a formal published ADM/AFO/SHACL validation result."},"pitfalls":["A model-slot label is not an applicability verdict.","A closed 329-node graph is not a SHACL pass.","No schema-opening button is shown when schemaId is null; do not invent that control."],"exercise":{"prompt":"Prepare a four-row semantic-validation readiness matrix.","deliverables":["ADM applicability/schema, AFO mapping, published shapes and custom structural checks as separate rows.","Exact source pointers and current states.","Required evidence and a proposed verification step for each gap."],"success":["No unknown is converted to passed.","Custom checks are not described as published conformance.","The plan is evidence collection, not assay or regulatory approval."]},"question":{"prompt":"The custom checks say all graph endpoints resolve. What may you report?","choices":[{"text":"The assay is scientifically validated.","explanation":"Incorrect. Structural closure says nothing about biological performance."},{"text":"The selected published Allotrope shapes passed.","explanation":"Incorrect. Published shapes have not run in this fixture."},{"text":"The retained educational structural closure check is distinct from still-unrun published validation.","explanation":"Correct. Keep the measured/retained scope and unresolved states explicit."}],"correctIndex":2},"screens":[{"title":"P3 semantic and validation state cards","href":"/pillars/p3#pillar-workspace"},{"title":"Typed gaps and exact validation fields","href":"/api/demo/pillars"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2012","recordReference":"#/lessons/15","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/15","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2013","module":"p4","title":"Compare environment patterns without deploying anything","goal":"Compare the two retained cloud patterns as local design options with separate proposed services and missing site bindings.","why":["A composition needs an operating environment in addition to hardware and method context.","Selecting a cloud label must not create resources or imply tenant authority."],"model":["This anonymous fixture supplies AWS and Azure only, each with its own design-document GDTI.","selectionState is illustrative-design-option. resourcesCreated, credentialsPresent, deploymentValidated and executionAuthorized are false.","Provider selection in this workspace is local preview state, not an updated immutable configuration or commissioned deployment."],"steps":[{"action":"Read the default pattern","control":"AWS provider card","why":"The source mapping must be read before making a comparison.","how":"Open P4, select AWS and inspect the service mappings and environment diagram.","expected":"The AWS pattern lists IoT Core, S3 and Lambda as retained design services.","verify":"Record #/P4/cloud/candidatePatterns/0 and its GDTI 00401.1; do not record a created resource ARN."},{"action":"Compare the alternative","control":"Azure provider card","why":"An alternative is a separate design option rather than the same identity renamed.","how":"Select Azure and compare the displayed mappings and diagram label.","expected":"Azure lists IoT Hub, Blob Storage and Functions, using separate design GDTI 00402.1.","verify":"Keep both source patterns; do not overwrite the AWS record or claim automated equivalence between the two service sets."},{"action":"Check boundaries while switching","control":"Provider selection is a local design preview","why":"A visible selected card does not establish resource binding.","how":"Read the evidence strip and the site-binding requirements below the pattern.","expected":"Customer authorization, bind testing and deployment remain separate and unresolved.","verify":"Confirm there is no deployment control or success receipt created by switching provider cards."},{"action":"Restore a reproducible comparison","control":"AWS provider card · Download design preview","why":"A reviewer should know which pattern the exported proposal concerns.","how":"Return to AWS and download the local design preview. Inspect providerPattern and its originalSelectionState.","expected":"The export records the chosen pattern and preview-only boundary without creating cloud resources.","verify":"Keep your two-pattern comparison and the selected preview separate from the original package snapshot."}],"machine":{"pointers":["#/P4/cloud/candidatePatterns/0","#/P4/cloud/candidatePatterns/1","#/P4/deploymentGates"],"identifiers":["urn:epc:id:gdti:0614141.00401.1","urn:epc:id:gdti:0614141.00402.1"],"fields":["provider","selectionState","designDocument","resourcesCreated","credentialsPresent","deploymentValidated","executionAuthorized"],"explanation":"The source package describes both patterns. The browser-selected pattern is a local view and download choice; it is not evidence of a cloud account, endpoint, tenant permission or deployment."},"pitfalls":["Only the two retained provider patterns belong to this lesson; do not invent additional cards.","A selected state is not a provisioning result.","Technology service names do not grant any vendor account or customer authority."],"exercise":{"prompt":"Write a two-pattern comparison and one explicitly scoped design preview.","deliverables":["Provider, exact design GDTI and service list for both patterns.","Unresolved site/account and test requirements.","A selected-pattern JSON labeled local preview only."],"success":["Both original patterns remain separately cited.","No resources-created or deployment-validated state becomes true.","The selected preview is not described as a persisted site deployment."]},"question":{"prompt":"What happens when Azure is selected?","choices":[{"text":"The browser previews the retained Azure design pattern.","explanation":"Correct. The source option remains unbound and no cloud action is performed."},{"text":"An authorized Azure tenant is provisioned.","explanation":"Incorrect. No tenant or credentials are supplied by the fixture."},{"text":"The AWS source record is deleted.","explanation":"Incorrect. Selection does not rewrite or erase the original package."}],"correctIndex":0},"screens":[{"title":"P4 AWS/Azure design comparison","href":"/pillars/p4#pillar-workspace"},{"title":"Exact AWS design-document graph","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00401.1&focus=context#pillar-workspace"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2013","recordReference":"#/lessons/16","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/16","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2014","module":"p4","title":"Read service mappings and proposed data paths","goal":"Connect the physical composition, edge proposal, cloud pattern and provenance graph while retaining unbound endpoints and design-only flow states.","why":["A service name needs a role in the composition, not just a logo.","Data movement needs identity, source, sink, runtime and governance context."],"model":["The diagram shows Physical composition → Edge runtime proposal → selected cloud option → Provenance & MCP.","The source serviceBindings are generic retained mappings, not actual endpoints or operational integrations.","Three flow records retain source, sink and currentState. Two are design-only and provenance projection is local-fixture-only."],"steps":[{"action":"Read the chain left to right","control":"P4 environment map","why":"Each layer contributes context without replacing the previous layer’s identities.","how":"Open P4 and follow the four diagram boxes. Read the text under Edge runtime proposal.","expected":"The edge stage is a runtime/adapter/local-data proposal, not a qualified deployed host.","verify":"Do not rewrite the proposal label as an installed adapter or verified edge service."},{"action":"Inspect the selected mappings","control":"AWS · retained service mappings","why":"Service names alone do not establish a physical-to-cloud integration.","how":"Read service1–service3 under AWS. Compare the list with #/P4/cloud/candidatePatterns/0/serviceBindings in package JSON.","expected":"IoT Core, S3 and Lambda remain retained pattern names.","verify":"Note that an account, region, endpoint, credentials and binding-test receipt are not supplied."},{"action":"Read proposed data-path states","control":"Retained data paths","why":"A flow diagram must retain whether movement is proposed or observed.","how":"Scroll to the three data-path rows. Read source, sink and current state for each.","expected":"Identity/state observation and protocol/result context are design-only; provenance projection is local-fixture-only.","verify":"Record #/P4/flows/0, /1 and /2 separately. Do not state that observations were transmitted."},{"action":"Trace the exact environment definition","control":"AWS design-document graph link · Inspect exact JSON","why":"A P4 design artifact must remain an addressable document in P5.","how":"Open the exact AWS design-document node in P5 and inspect its retained relationships and source evidence.","expected":"The design GDTI remains part of the same anonymous graph, with authored evidence and unknown authority.","verify":"Distinguish this document identity from a real cloud resource identifier or deployment event."}],"machine":{"pointers":["#/P4/cloud/candidatePatterns/0/serviceBindings","#/P4/flows/0","#/P4/flows/1","#/P4/flows/2","#/P5/nodes/36"],"identifiers":["urn:epc:id:gdti:0614141.00401.1","urn:epc:id:giai:0614141.100003"],"fields":["serviceBindings","source","sink","currentState","designDocument","authorityState"],"explanation":"The edge-host GIAI candidate is an identified participant in the broader composition, not proof that an adapter or service is running. The proposed flow records are separate from observed network transfers."},"pitfalls":["A source/sink label is not a configured URL or host.","A cloud-pattern GDTI does not identify a created cloud resource.","A proposed provenance projection is not a live MCP connection or executed upload."],"exercise":{"prompt":"Create a proposed data-flow review with explicit gaps at every boundary.","deliverables":["Three source/sink/state rows with exact source pointers.","The selected provider mappings and design-document GDTI.","Missing endpoint, runtime, security and transfer-evidence requirements."],"success":["Every flow remains design-only or local-fixture-only as supplied.","No observed traffic or live service is invented.","Physical identities are not replaced by generic cloud service labels."]},"question":{"prompt":"A data-path row says currentState:design-only. What does it mean?","choices":[{"text":"The data has already moved successfully.","explanation":"Incorrect. The row describes a proposed flow, not an observed transfer."},{"text":"The flow is a retained design that still needs binding and verification.","explanation":"Correct. Preserve its source/sink proposal and missing operating evidence."},{"text":"The physical instrument identity is no longer relevant.","explanation":"Incorrect. Operating context must remain connected to exact participants."}],"correctIndex":1},"screens":[{"title":"P4 diagram, mappings and data paths","href":"/pillars/p4#pillar-workspace"},{"title":"Read the original flow records","href":"/api/demo/pillars"},{"title":"AWS design-document context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00401.1&focus=context#pillar-workspace"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2014","recordReference":"#/lessons/17","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/17","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2015","module":"p4","title":"Review site gates without broadening authority","goal":"Turn the four explicit deployment requirements into a scoped readiness checklist while preserving all false and unknown states.","why":["Ordinary design publication and physical/cloud operation are separate permissions.","Missing deployment evidence should block dependent actions without suppressing safe source inspection."],"model":["The source gateResult is blocked because authorized site/account context, endpoints, policies and testing evidence are missing.","customerAuthorized, resourcesCreated, deploymentValidated and executionAuthorized are all false.","The public page supplies a review view, not forms to submit credentials, approve commissioning or deploy resources."],"steps":[{"action":"Read the site requirements","control":"Complete these site bindings","why":"A provider choice is insufficient operating context.","how":"Open P4 and read all four numbered requirements without skipping the account/tenant/region/site-owner row.","expected":"Missing authority, device/edge endpoints, policies and acceptance/recovery testing are explicit.","verify":"Copy each requirement into a separate checklist row and preserve the original wording and scope."},{"action":"Inspect the exact gate data","control":"Public package link · P4 deploymentGates","why":"The machine-readable gate must match the visible warning.","how":"Open the public package and inspect #/P4/deploymentGates including gateResult and all four boolean states.","expected":"gateResult is blocked and every authorization/deployment boolean remains false.","verify":"Record exact values rather than treating a visible warning as the only gate evidence."},{"action":"Assign evidence needs, not fictitious approvals","control":"Requirements list · Design preview evidence strip","why":"A readiness plan should say what is needed and who must authorize it.","how":"For each row, name the evidence needed and its future reviewer scope in your exercise notes. Do not enter secrets into this read-only sample.","expected":"The plan remains an evidence request; the source still records missing bindings.","verify":"An imagined reviewer or a platform-owner preference is not authority evidence for a real customer or cloud account."},{"action":"Confirm safe inspection remains available","control":"Open exact design graph · Complete graph JSON","why":"A blocked dependent action should not hide the underlying evidence.","how":"Open the selected design graph and inspect/export its original public source context.","expected":"The source remains retrievable despite blocked deployment state.","verify":"Confirm there is no deployment success or execution receipt; unrelated read-only work can continue."}],"machine":{"pointers":["#/P4/deploymentGates","#/P4/deploymentGates/unresolvedRequirements","#/authority","#/boundaries"],"identifiers":["urn:epc:id:gdti:0614141.00401.1","urn:epc:id:gdti:0614141.00402.1"],"fields":["gateResult","customerAuthorized","resourcesCreated","deploymentValidated","executionAuthorized","unresolvedRequirements"],"explanation":"The source requirements distinguish authority, runtime/network binding, operating policy and verification. Marking one requirement planned does not make any gate true. The lesson performs no credentials submission, provisioning or physical dispatch."},"pitfalls":["Do not treat site-owner approval as automatic company or vendor authority.","Do not enter credentials into a teaching exercise.","“Blocked deployment” does not mean the evidence should be hidden or merged away."],"exercise":{"prompt":"Create a four-gate readiness matrix with unknowns and scoped next actions.","deliverables":["One row per original unresolved requirement with its exact source pointer.","Needed evidence, responsible reviewer role and dependent action.","The current false/unknown gate values copied unchanged."],"success":["No approval or validation is invented.","The matrix distinguishes content publication from operational execution.","All original read-only source records remain accessible."]},"question":{"prompt":"A provider is selected but site/account authority and binding tests are absent. What is the safe next step?","choices":[{"text":"Deploy anyway because the cloud service names are familiar.","explanation":"Incorrect. Familiar labels do not grant authority or validate bindings."},{"text":"Hide the design and all its source evidence.","explanation":"Incorrect. Safe inspection should remain available while dependent actions are gated."},{"text":"Record the gaps and gather scoped authority, binding and test evidence before the dependent action.","explanation":"Correct. Preserve the proposal and the separate gate requirements."}],"correctIndex":2},"screens":[{"title":"P4 site-binding and readiness gates","href":"/pillars/p4#pillar-workspace"},{"title":"Machine-readable authorization/deployment boundaries","href":"/api/demo/pillars"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2015","recordReference":"#/lessons/18","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/18","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2016","module":"p4","title":"Export a design preview with its scope intact","goal":"Produce a reproducible local environment proposal while retaining original package provenance and explicit no-deployment flags.","why":["A useful export needs the chosen source option and its lineage, not a screenshot alone.","A browser-local proposal must not be mistaken for a newly issued or deployed configuration."],"model":["The Download design preview control exports a wrapper containing sourceLane, sourcePackage, sourcePrefix and submissionSha256.","providerPattern and originalSelectionState describe the chosen retained option; configurationGdti is the existing sample configuration reference.","previewOnly is true; customerAuthorized, deploymentPerformed and executionAuthorized are false. This export does not mutate the source package."],"steps":[{"action":"Choose the intended source option","control":"AWS or Azure provider card","why":"The export should reflect the pattern you actually reviewed.","how":"Open P4, select Azure and read its mapping and missing binding requirements.","expected":"The view previews the retained Azure option without creating resources.","verify":"Record the selected design GDTI 00402.1 and confirm it differs from the AWS option."},{"action":"Download the scoped preview","control":"Download design preview","why":"The machine-readable proposal should preserve lineage and gates.","how":"Select Download design preview and open the downloaded thingdaddy-cloud-edge-design-preview.json.","expected":"The wrapper contains providerPattern, originalSelectionState, configurationGdti and requiredBindings.","verify":"Check providerPattern.provider is Azure and sourcePrefix is the exact string 0614141."},{"action":"Verify boundary flags and source pin","control":"Downloaded JSON · originalSelectionState and submissionSha256","why":"A file should not imply more than the operation actually performed.","how":"Check previewOnly:true and the no-authorization/no-deployment flags. Compare submissionSha256 with b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94.","expected":"The file is a pinned source-derived proposal, not a provisioning receipt or new identifier assignment.","verify":"configurationGdti remains the supplied sample reference; the export does not assign a new GDTI or SRIN."},{"action":"Confirm the source remains unchanged","control":"AWS provider card · Public package link","why":"UI choice and immutable source must stay distinct.","how":"Switch back to AWS and read the original public package. Compare its two candidatePatterns and boundaries with your exported preview.","expected":"Both original options remain in the package and resources/deployment states remain false.","verify":"Keep the original package and exported selection separate in your deliverables. Do not report the preview as a saved private-site version."}],"machine":{"pointers":["#/P4/cloud/candidatePatterns/1","#/P4/deploymentGates/unresolvedRequirements","#/P1/configurationGdti","#/boundaries"],"identifiers":["urn:epc:id:gdti:0614141.01200.1","urn:epc:id:gdti:0614141.00402.1"],"fields":["export.sourcePrefix","export.submissionSha256","export.previewOnly","export.providerPattern","export.originalSelectionState","export.configurationGdti","export.requiredBindings","export.deploymentPerformed"],"explanation":"Export-prefixed field names describe the download wrapper, not new fields inserted into the source package. A download does not create an immutable private-site history revision, cloud deployment or execution event."},"pitfalls":["The existing configuration GDTI is not newly assigned by the export.","A file hash or downloaded filename is not a new physical-asset identity.","Do not imply the private version-save or publication workflow was exercised by this local preview."],"exercise":{"prompt":"Prepare an environment-design handoff bundle that a reviewer could inspect safely.","deliverables":["The downloaded Azure preview.","The original package SHA and exact source option pointer.","A plain-language handoff identifying unresolved bindings and no-deployment scope."],"success":["The package lineage and source prefix match exactly.","All preview/authorization/deployment flags retain their actual values.","Original source and selected preview are preserved separately."]},"question":{"prompt":"What is configurationGdti in this design-preview file?","choices":[{"text":"The retained sample configuration reference carried into the scoped proposal.","explanation":"Correct. The download does not issue a new key or commission that configuration."},{"text":"A new authorized cloud deployment identity generated by the download.","explanation":"Incorrect. No new allocation or deployment occurs."},{"text":"A replacement for the provider design-document GDTI.","explanation":"Incorrect. Configuration and environment-option identities keep different purposes."}],"correctIndex":0},"screens":[{"title":"P4 provider preview and export control","href":"/pillars/p4#pillar-workspace"},{"title":"Original source package for comparison","href":"/api/demo/pillars"}],"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2016","recordReference":"#/lessons/19","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/19","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2017","module":"p5","title":"Inspect one exact node inside the complete graph","goal":"Use exact node selection, the bounded inspector and original JSON to distinguish identity, source occurrence, state and evidence.","why":["P5 makes all other pillars addressable to agents.","A readable node card is only the entry to the record and its provenance, not a replacement for them."],"model":["The complete public graph contains 329 nodes and 231 directed relationships, retained from the same pinned package.","A focused URL selects an existing exact node and its direct-neighbor viewport; the full graph remains available.","id, identity and source occurrence pointer are different fields. The sample node has authored evidence, non-issued state and unknown authority."],"steps":[{"action":"Open an exact component record","control":"Exact CPI graph link","why":"The lesson should begin with a known address rather than a name search.","how":"Open the CPI graph link. Read Same object. Exact context, incoming P2 occurrence and the selected inspector.","expected":"The selected node is urn:epc:id:cpi:0614141.414141.41, linked from #/P2/modules/1.","verify":"Verify Exact source ID and Source occurrence pointer#/P5/nodes/3; do not interpret the source pointer as a new EPC identity."},{"action":"Inspect fields rather than labels","control":"Exact graph record inspector","why":"A title alone does not expose assignment, evidence or authority.","how":"Read reference kind, state, source, evidence locator, asserting actor, authority evidence, assertion time and scope. Scroll within the inspector if needed.","expected":"The record remains demo_non_issued and fictional authored; missing actor/authority/time values stay Unknown.","verify":"Do not manufacture a timestamp or actor for a node whose source object lacks those fields."},{"action":"Open the original node JSON","control":"Inspect exact JSON","why":"Machine consumers need original structured fields, not only human summaries.","how":"Select Inspect exact JSON and read id, identity, referenceKind, evidence and authorityState.","expected":"The JSON is the original selected node object, not a newly edited interpretation.","verify":"Compare its exact id with the selected address. Record null/unknown fields as supplied rather than filling them from neighboring edges."},{"action":"Restore the complete model","control":"Show complete graph · Fit view","why":"A focused subset must not become hidden data loss.","how":"Choose Show complete graph, then Fit view. Compare visible counts with the complete model.","expected":"The full 329-node/231-relationship view is restored; selection/focus is cleared.","verify":"The full graph JSON remains unchanged before and after inspection. No source node is deleted by closing the inspector."}],"machine":{"pointers":["#/P5/nodes/3","#/P2/modules/1","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:cpi:0614141.414141.41","urn:epc:id:giai:0614141.100002","urn:epc:id:giai:0614141.4"],"fields":["id","identity","referenceKind","state","evidence.source","evidence.sourceLocator","authorityState"],"explanation":"The selected graph record, P2 source occurrence and asserted EPC identity are preserved separately. Focus is a visual direct-neighbor projection over original records; source counts and JSON remain complete."},"pitfalls":["A missing node actor cannot be inferred from a related relationship’s actor.","Unknown authority is not a grant of permission.","Zoom, fit and closing an inspector do not alter the source model."],"exercise":{"prompt":"Produce an exact node-inspection receipt before and after restoring the complete graph.","deliverables":["Node ID, source pointer, reference kind and assignment state.","Evidence locator and explicit unknown authority/time fields.","Focused and complete counts with a note that the original JSON is unchanged."],"success":["The exact original CPI remains addressable.","No field is invented from labels or nearby records.","The complete graph restores 329/231."]},"question":{"prompt":"Why can the node show Unknown for asserting actor while a related edge names an actor?","choices":[{"text":"The node is corrupted and must inherit the edge actor.","explanation":"Incorrect. A node and relationship have separately scoped evidence; do not fill missing node fields by inference."},{"text":"The node and edge preserve different original assertions, so absent node fields remain unknown.","explanation":"Correct. Context does not authorize silently copying provenance between records."},{"text":"Actors are only needed for human readers.","explanation":"Incorrect. Agent-facing provenance needs the original actor and explicit unknowns."}],"correctIndex":1},"screens":[{"title":"Exact CPI inspector and graph","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context&from=%23%2FP2%2Fmodules%2F1#pillar-workspace"},{"title":"Complete original graph JSON","href":"/api/demo/pillars?view=graph"}],"graph":{"node":"urn:epc:id:cpi:0614141.414141.41","from":"#/P2/modules/1"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2017","recordReference":"#/lessons/20","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/20","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2018","module":"p5","title":"Read a directed relationship as its own provenance record","goal":"Inspect a protocol-version relationship, its exact ID, endpoints and authority scope without inferring identity equivalence or current approval.","why":["Relationships carry claims about two records and need their own evidence.","Agent traversal must preserve direction, actor, source, time and scope rather than a generic “connected” label."],"model":["The protocol-version GDTI points to its family through version-of-protocol-family.","The relationship has its own GDTI 00900.9, original source-pointer occurrence and provenance object.","The assertion is fictional authored, scope educational-composition-only, assertionTime:null, authorityState:unknown and executionAuthorized:false."],"steps":[{"action":"Select the version, not a similar title","control":"Protocol-version graph link","why":"Family and version labels can look similar while their identities differ.","how":"Open the exact version graph link and read its exact source ID.","expected":"The selected node is urn:epc:id:gdti:0614141.00011.1; the family urn:epc:id:gdti:0614141.42424.42 remains a distinct node.","verify":"Do not choose a node by title similarity or replace the version ID with its family ID."},{"action":"Open the original lineage edge","control":"Original direct relationships · version of protocol family","why":"The edge, not the node title, supplies the lineage assertion.","how":"Select the version-of-protocol-family relationship from the node inspector.","expected":"The inspector changes to Typed relationship and the selected edge label appears on the canvas.","verify":"Read exact relationship IDurn:epc:id:gdti:0614141.00900.9 and occurrence#/P5/edges/8."},{"action":"Read the directed endpoints and provenance","control":"Subject · Destination · Inspect exact JSON","why":"The direction and scope define what was actually asserted.","how":"Inspect Subject, Destination, asserting actor, source, time and scope. Open exact JSON to confirm a, b and t.","expected":"a is the version, b is the family, t is version-of-protocol-family; original unknowns remain unchanged.","verify":"Record the named source/asserting-actor IDs without treating them as verified real company authority."},{"action":"Traverse without identity replacement","control":"Destination","why":"A relationship connects records without merging them.","how":"Select Destination to inspect the protocol family, then locate its incoming version relationship.","expected":"The family’s own exact ID appears; the original version and relationship remain retrievable.","verify":"Your receipt must preserve all three addresses. No approval, ownership transfer or current-version designation is inferred."}],"machine":{"pointers":["#/P5/nodes/31","#/P5/nodes/30","#/P5/edges/8","#/P5/edges/8/provenance"],"identifiers":["urn:epc:id:gdti:0614141.00011.1","urn:epc:id:gdti:0614141.42424.42","urn:epc:id:gdti:0614141.00900.9","urn:epc:id:gdti:0614141.60001.1","urn:epc:id:gsrn:0614141.0000000002"],"fields":["id","a","b","t","provenance.sourceId","provenance.assertingActorId","provenance.scope","provenance.assertionTime","provenance.authorityState","provenance.executionAuthorized"],"explanation":"The graph exposes original directed assertions. A version-of relationship is not a statement that the family and version are identical, that the version is currently approved, or that any physical run is authorized."},"pitfalls":["Do not reverse a and b based on visual position.","Do not invent a timestamp, validity interval or supersession event absent from the source.","A relationship GDTI is not one of its endpoint identities."],"exercise":{"prompt":"Write a relationship provenance receipt suitable for exact agent traversal.","deliverables":["Relationship ID and zero-based occurrence pointer.","Original subject/destination/type and source/asserting-actor IDs.","Unknown authority/time and no-execution states, with a complete traversal back to both endpoints."],"success":["All original addresses remain separate.","Direction and source scope are reproduced exactly.","No inferred current approval, ownership or identity equivalence is added."]},"question":{"prompt":"What does version-of-protocol-family establish here?","choices":[{"text":"An authored directed lineage assertion between two separate document records.","explanation":"Correct. Its provenance and non-issued scope remain attached."},{"text":"That both endpoints are the same identity.","explanation":"Incorrect. A typed relationship is not identity equivalence."},{"text":"That the version has been approved for physical execution.","explanation":"Incorrect. Execution authority and validation are explicitly absent."}],"correctIndex":0},"screens":[{"title":"Protocol-version lineage inspector","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agdti%3A0614141.00011.1&focus=context#pillar-workspace"},{"title":"Original relationship fields in graph JSON","href":"/api/demo/pillars?view=graph"}],"graph":{"node":"urn:epc:id:gdti:0614141.00011.1"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2018","recordReference":"#/lessons/21","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/21","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2019","module":"p5","title":"Filter the viewport without losing the complete source","goal":"Use exact search, pillar/type filters, focus and the accessible browser while proving exports remain complete.","why":["Large graphs need navigable views, but agents still need every original fact.","Subset counts and reset behavior prevent a convenient visual slice from becoming a misleading total."],"model":["Search, pillar, type and focused direct-neighbor context are viewport projections only.","The displayed numerator is visible records; the denominator is the complete 329-node/231-edge source.","The keyboard-accessible node browser pages 40 visible matches per page. Complete graph JSON exports the original full graph, even while a visual subset is active."],"steps":[{"action":"Start from the complete model","control":"Show complete graph · Fit view","why":"A stable baseline makes subset behavior measurable.","how":"Open P5 and restore the complete graph before filtering.","expected":"The view reports 329/329 nodes and 231/231 relationships.","verify":"Record both node and relationship counts; do not use the minimap’s tiny squares as a different source count."},{"action":"Filter one pillar and type","control":"Graph pillar · Graph node type","why":"A filter should declare what it excludes.","how":"Select P3 as Graph pillar. Then choose a visible step-definition-document type. Read Explicit visual subset and the count denominators.","expected":"Only matching nodes and edges between visible endpoints are drawn; original source facts remain available.","verify":"Do not describe the visible relationship count as the full protocol relationship total. Restore the complete graph before the next test."},{"action":"Search an exact address and test an empty result","control":"Search graph nodes","why":"Search is navigation, not identity assignment or approximate substitution.","how":"Search urn:epc:id:giai:0614141.4, then search no-such-context-123456. Read the resulting subset or no-match state.","expected":"The exact search retains matches by record/address context; the unknown text yields no nodes rather than selecting a similar label.","verify":"Clear the search or use Restore the complete graph. Exact selection for identity-sensitive work should use the validated context link, not substring matching alone."},{"action":"Compare focused view and full export","control":"Exact asset graph link · Complete graph JSON","why":"The export must preserve nodes excluded from the viewport.","how":"Open the exact asset graph link to focus its direct context. Download Complete graph JSON and inspect P5.nodes/P5.edges in the wrapper.","expected":"The focused view has a smaller visible subset; the file still contains 329 nodes and 231 original directed edges.","verify":"Record visible and complete counts separately. The raw graph API uses top-level nodes/edges, unlike the UI export wrapper’s P5 object."},{"action":"Verify every node remains reachable","control":"Keyboard-accessible node browser · Next nodes","why":"Accessibility must not silently truncate the source model.","how":"Restore the complete graph and open the accessible node browser. Use Next nodes through the nine pages; inspect a record near the end.","expected":"Every visible source node remains listed across 40-per-page groups, with the final page containing the remainder.","verify":"Confirm Page 9/9 and that a listed exact node opens its inspector. Paging changes UI only, not JSON or original data."}],"machine":{"pointers":["#/P5/nodes","#/P5/edges","#/P5/nodes/1"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["viewport.query","viewport.kind","viewport.pillar","viewport.focusedId","nodes","edges","a","b"],"explanation":"Viewport-prefixed names are presentation filter state, not extra fields written into the source package. Focus includes the selected node, its direct neighbors and original edges between visible endpoints, not every two-hop record. Complete exports are independent of that projection."},"pitfalls":["Substring search is not proof of identity equivalence.","A visible numerator must not replace a complete denominator.","The source JSON shape differs between package, raw graph view and UI download wrapper; identify the container before counting."],"exercise":{"prompt":"Produce a filter/reset/export verification receipt.","deliverables":["Complete, P3/type-filter and focused view counts.","An empty-result test and successful reset.","A complete graph export showing 329 nodes/231 edges and the accessible browser’s final page."],"success":["All exclusions are labeled visual subsets.","Full source and directed edges survive every view operation.","No unknown search result is replaced with a guessed node."]},"question":{"prompt":"You download Complete graph JSON while a focused subset is displayed. What should the file contain?","choices":[{"text":"Only the nodes currently visible on screen.","explanation":"Incorrect. The action explicitly exports the complete original graph."},{"text":"The complete original 329 nodes and 231 relationships, not the viewport subset.","explanation":"Correct. Preserve source completeness independently of presentation."},{"text":"A new simplified graph with provenance removed.","explanation":"Incorrect. Simplifying the view must not erase source facts or relationship provenance."}],"correctIndex":1},"screens":[{"title":"P5 complete graph and filters","href":"/pillars/p5#pillar-workspace"},{"title":"Exact cycler focused context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context&from=%23%2FP2%2Fmodules%2F0#pillar-workspace"},{"title":"Raw complete graph view","href":"/api/demo/pillars?view=graph"}],"graph":{"node":"urn:epc:id:giai:0614141.4","from":"#/P2/modules/0"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2019","recordReference":"#/lessons/22","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/22","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2020","module":"p5","title":"Read the agent contract without claiming an installed MCP tool","goal":"Compare the public package, graph and read-method contract while distinguishing fixture declarations from registered live MCP or authorized action tools.","why":["Agent-first learning requires structured context and explicit interface maturity.","A method name in JSON is not evidence that a tool was registered, called or connected to an instrument."],"model":["The fixture declares three educational read methods: inspect_anonymous_demo_package, inspect_anonymous_demo_graph and inspect_anonymous_demo_evidence.","registrationState is fixture-descriptions-only-not-registered. The public endpoint exposes bounded package, graph and mcp JSON views.","mutationTools is empty in P5.mcpFixture and executionAuthorized is false. The mcp projection is a read-method description, not the website’s separately registered and authorized private MCP implementation."],"steps":[{"action":"Read the declaration boundary","control":"Agent interface · educational read-only views","why":"Tool maturity must be explicit before an agent relies on it.","how":"Open P5 and read the educational agent-interface panel below the graph.","expected":"The panel explicitly says these declarations are not registered live MCP tools.","verify":"Record the three method names as descriptions only; do not report three successful tool calls."},{"action":"Inspect all three public views","control":"Open complete graph JSON · Open read-method contract · Public package link","why":"Each representation has a defined scope and shape.","how":"Open package, graph and mcp views in separate browser tabs. Compare schema, lane, status, nodes/edges container and boundaries.","expected":"All views expose only the anonymous fixture; package has P1–P5, graph uses top-level nodes/edges, and mcp nests graph nodes/edges.","verify":"Confirm none of these links carries a tenant, private lane or company resource selector."},{"action":"Verify registration and action boundaries","control":"Open read-method contract · Download read-method contract","why":"The original machine-readable state must support the visible warning.","how":"Read registrationState in the mcp view and inspect P5.mcpFixture in the package or downloaded contract. Check mutationTools and executionAuthorized.","expected":"Registration is descriptions-only-not-registered, mutations are absent, and execution authority remains false.","verify":"Do not claim the public mcp projection has a mutationTools field if absent from that projection; its empty list is retained in the package contract."},{"action":"Prepare a bounded agent inspection request","control":"Exact step-participant graph link · Inspect exact JSON","why":"Useful agent work can remain read-only and identity-specific.","how":"Open the exact cycler-from-step 6 context link. Write a proposed inspection request naming its exact node, source occurrence and relationship, plus the required return data.","expected":"The graph exposes the original selected record and provenance without executing a command.","verify":"Your request must ask for evidence/unknowns only. It cannot grant physical/cloud action or assert that a declared method was installed or invoked."}],"machine":{"pointers":["#/P5/mcpFixture","#/P5/mcpFixture/tools","#/P5/mcpFixture/registrationState","#/P5/mcpFixture/mutationTools","#/boundaries","#/P5/edges/189"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:gdti:0614141.00105.1","urn:epc:id:gdti:0614141.00900.190"],"fields":["schema","endpoint","views","tools","registrationState","mutationTools","executionAuthorized","boundaries"],"explanation":"The public JSON endpoint is a bounded educational data view. The fixture-method declaration and the site’s actual registered MCP tools have different contracts and authorization. This lesson proves readable source context, not live MCP registration, hardware control or model-weight training."},"pitfalls":["Do not call a JSON view an installed MCP server merely because view=mcp appears in its URL.","A declared method count is not a successful invocation count.","An exact identity or readable graph does not authorize mutation or execution."],"exercise":{"prompt":"Produce a read-only agent contract review and exact inspection request.","deliverables":["Three view URLs and their data-container differences.","Registration/mutation/execution states with source pointers.","A bounded request for the exact step-participant node and directed assertion, including explicit unknowns."],"success":["No private company lane is requested.","Declarations are not mislabeled as installed or invoked tools.","No hardware/cloud action or adaptive-learning outcome is claimed."]},"question":{"prompt":"The mcp view lists three method names. What has been demonstrated?","choices":[{"text":"Three live MCP tools were registered and called.","explanation":"Incorrect. The registration state explicitly says fixture descriptions only."},{"text":"A driver controlled the instrument through MCP.","explanation":"Incorrect. No driver transport or execution authority is supplied."},{"text":"Three educational read-method declarations are machine-readable, with live registration still not established.","explanation":"Correct. Interface description and actual registered/authorized behavior must be verified separately."}],"correctIndex":2},"screens":[{"title":"P5 agent-interface boundary and graph","href":"/pillars/p5#pillar-workspace"},{"title":"Anonymous package view","href":"/api/demo/pillars"},{"title":"Complete graph view","href":"/api/demo/pillars?view=graph"},{"title":"Educational read-method contract","href":"/api/demo/pillars?view=mcp"},{"title":"Exact step 6 cycler assertion","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context&from=%23%2FP3%2FprotocolTemplates%2F0%2Fordered_steps%2F5&via=urn%3Aepc%3Aid%3Agdti%3A0614141.00900.190#pillar-workspace"}],"graph":{"node":"urn:epc:id:giai:0614141.4","from":"#/P3/protocolTemplates/0/ordered_steps/5","via":"urn:epc:id:gdti:0614141.00900.190"},"track":"site","references":[{"kind":"demo","label":"Anonymous public five-pillar fixture","href":"/api/demo/pillars","sha256":"b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94","classification":"fictional authored, non-issued, read-only"}],"sourceNotes":["Screen basis: the anonymous public educational fixture at /api/demo/pillars, namespace 0614141. No private company record is read by this course.","Pinned assessed package SHA-256: b06ee255d0943a048511092595db4b98281b9b761d1910d19e6c3dba82591d94. Its complete graph contains 329 nodes and 231 directed relationships; original excluded assertions remain separately retained provenance. Lesson locators are educational numbers, not issued GS1 keys.","Scope: fictional authored records, non-issued identity proposals, unknown authority, no physical command, assay validation, cloud deployment or execution authorization."],"lessonLocator":"/learn/deep-dive/2020","recordReference":"#/lessons/23","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/23","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2025","track":"site","module":"practice","title":"Edit a local workflow proposal and inspect the command","goal":"Create a reversible teaching change without overwriting the original procedure.","why":["The workflow tool describes order and roles. Changes must be inspectable as proposals rather than silently becoming approved procedures.","A human canvas action and an agent command should use the same governed editing operation; a diagram alone is not an audit trail."],"model":["The demo configuration studio is a protected browser-local teaching tool. Its local editing addresses are not issued GS1 identities.","The original source steps and identifiers survive beside new proposed steps. A local title can change without changing the original manufacturer/source procedure."],"steps":[{"action":"Inspect the starting draft","control":"Workflows and Protocols in the graphical configuration tool","why":"Without a baseline you cannot tell which facts a proposed change altered.","how":"Open the demo studio if your existing account permits it. Inspect its current local draft before editing; do not assume it is a blank or the same baseline as an earlier screenshot.","expected":"A recorded starting step count and exact source references.","verify":"Separate source steps from any earlier local proposals."},{"action":"Add one educational review checkpoint","control":"Add step","why":"A review step illustrates composition while avoiding physical command dispatch.","how":"Add a proposed review checkpoint in the workflow tool. Inspect the new step’s local address, position and unassigned document identity. The title is a human label, not an identifier.","expected":"One additional proposed step in the local design.","verify":"Original source-step references are still present; no identity or approval was issued."},{"action":"Compare graphical and structured operations","control":"Structured command editor and Export","why":"The same design operation should have the same semantics for a human and an agent.","how":"Inspect the command method and exported draft. Identify the proposed operation and its target without submitting any unrelated command or changing the source data.","expected":"An inspectable proposal and command representation.","verify":"The export still states that no physical or cloud action was sent."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps"],"identifiers":[],"fields":["draft.steps[*].sourceId","draft.steps[*].id","draft.commandLog[*].command"],"explanation":"These are local proposal and command fields. Their presence is not proof of server persistence, scientific validation or assigned GS1 identity."},"pitfalls":["Calling a local edit a customer-approved protocol.","Replacing the original procedure with the new title."],"exercise":{"prompt":"Add one review checkpoint and document exactly what changed.","deliverables":["Before/after source and proposed step counts.","The new local step address and its identity state.","An exported draft or a read-only description if the account cannot enter the tool."],"success":["Only the intended proposal changed.","The original procedure remains addressable.","No execution or durable server-save claim is made."]},"question":{"prompt":"What does adding a step in the local demo establish?","choices":[{"text":"An approved procedure revision.","explanation":"Approval is a separate evidenced decision."},{"text":"A local configuration proposal.","explanation":"Correct. The design can be inspected without commissioning or approving it."},{"text":"A newly issued protocol GDTI.","explanation":"A local editing address is not GS1 issuance."}],"correctIndex":1},"screens":[{"title":"Graphical configuration studio · existing access required","href":"/demo/configure"},{"title":"Read-only anonymous protocol","href":"/pillars/p3#pillar-workspace"}],"sourceNotes":["The local studio and public read-only protocol are separate experiences. An edit in the studio does not mutate the anonymous pillar fixture."],"lessonLocator":"/learn/deep-dive/2025","recordReference":"#/lessons/24","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/24","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2026","track":"site","module":"practice","title":"Bind an exact participant and compare undo, redo and reload","goal":"Understand reversible local configuration state without confusing it with server history.","why":["A role requirement and a selected asset are different objects. The chosen participant needs its exact identity and a proposed binding, not just a matching label.","Undo/redo and local restoration are useful editing behaviors. They must not be described as durable private server version history."],"model":["The asset library retains exact references. Adding an asset or binding is a proposal, not installed-use or compatibility proof.","A browser-local persisted draft, session undo history and an immutable server receipt are distinct kinds of state."],"steps":[{"action":"Inspect an existing asset requirement","control":"In-Context Asset Configuration and the selected step","why":"A model-level need does not select a particular physical unit.","how":"Read the step’s role and requirements. Inspect an exact library item and its identifier before using an Add or binding control. If applicability is unknown, preserve that gap.","expected":"A separately identified role, candidate participant and proposed association.","verify":"No name-only join or inferred compatibility is introduced."},{"action":"Make one reversible proposal","control":"Add binding, Undo design change and Redo design change","why":"The learner needs to see the recorded change, not only a new line on the canvas.","how":"Use one available safe educational binding operation. Record the target and participant, undo it, then redo it. Do not remove or reset a pre-existing unrelated draft.","expected":"The local proposal changes and returns as expected.","verify":"The original source identities and values are unchanged in each state."},{"action":"Inspect restoration and export","control":"Export and reload","why":"Restoration tests a particular persistence layer. It does not prove every other layer.","how":"Export the local draft before reloading. Compare the restored draft and the session undo controls. Explain that durable server-save lineage needs a separate immutable receipt and protected retrieval test.","expected":"A precise account of local restoration behavior.","verify":"Do not call a local reload an authenticated server-save proof."}],"machine":{"pointers":[],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["draft.assets[*].urn","draft.assets[*].sourceId","draft.bindings[*].id","draft.bindings[*].stepId","draft.bindings[*].assetId","draft.bindings[*].requirementId","draft.commandLog[*].command"],"explanation":"Selected identities and proposed bindings must stay distinct. This browser-local exercise is separate from server-owned private configuration receipts."},"pitfalls":["Treating a drawn edge as installation evidence.","Counting redo as a second scientific experiment."],"exercise":{"prompt":"Make one local participant proposal and compare its three editing states.","deliverables":["Exact role, candidate identity and binding target.","Before, after, undo and redo observations.","A statement identifying the persistence layer actually tested."],"success":["Original source facts survive.","Unresolved applicability remains unresolved.","Only local behavior is claimed."]},"question":{"prompt":"Does local restoration prove immutable server version history?","choices":[{"text":"Yes, because the diagram reappeared.","explanation":"A browser can restore its own draft without contacting durable private storage."},{"text":"Yes, if undo was available.","explanation":"Session editing history is not a server receipt."},{"text":"No; the server history needs its own save and retrieval evidence.","explanation":"Correct. Test and describe each persistence layer separately."}],"correctIndex":2},"screens":[{"title":"Local participant studio · existing access required","href":"/demo/configure"},{"title":"Exact public asset context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"}],"sourceNotes":["The exercise requires an already-authorized local educational studio; it changes no company source or online permissions."],"lessonLocator":"/learn/deep-dive/2026","recordReference":"#/lessons/25","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/25","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2027","track":"site","module":"practice","title":"Distinguish private saved versions from local drafts","goal":"Read save, version, reopening and history evidence without inventing a durable lineage.","why":["A saved configuration has to say which source snapshot and editing engine produced it. Otherwise a later tool change can silently reinterpret an earlier design.","A new publication or storage receipt does not authorize the proposed instrument or cloud action."],"model":["Private configuration recipes preserve the selected source, exact commands, parent version and replay-engine version. Hashes bind bytes; they do not replace a typed protocol, service or document identity.","The page-by-page private save exercise must be performed in an authorized selected context. The anonymous public sample is read-only, and the browser-local demo has a different persistence model."],"steps":[{"action":"Read the selected private configuration","control":"Authorized configuration maker and source/lineage view","why":"A title alone cannot establish which source or parent a design derives from.","how":"In an already-authorized private maker, inspect the selected source and saved version. Record its exact recipe/engine pin and parent before making any teaching proposal. If access is absent, write the required evidence checklist instead.","expected":"A source-bound baseline or an explicit access limit.","verify":"No foreign source or earlier version is substituted."},{"action":"Separate preview from save","control":"Preview and Save new version","why":"A preview proves a proposed projection, while save must prove an immutable stored envelope.","how":"Review proposed commands and the projected graph. Save only an intended authorized educational proposal in that context. Capture the actual returned version and receipt; do not create a company decision or approval record.","expected":"A preview result or an actual save receipt, clearly labelled.","verify":"Source facts are retained, and execution remains disabled."},{"action":"Reopen the exact version","control":"Commands and versions and the saved-version link","why":"A later “latest” page cannot prove the earlier recipe still exists.","how":"Reopen the exact returned version under its scope. Compare its parent, recipe, engine, original graph and unknown fields with the saved receipt. Retain any failed retrieval rather than declaring success.","expected":"An exact readback result with its verification limit.","verify":"No local draft or changed engine is silently presented as the saved design."}],"machine":{"pointers":[],"identifiers":[],"fields":["versionHash","parentVersionHash","replayEngineSha256","baseHash","sourceArchives","commands"],"explanation":"Content hashes and internal version locators support integrity and retrieval. They do not issue a GDTI or GSRN/SRIN, and publication is not execution."},"pitfalls":["Describing a displayed preview as a successful immutable save.","Replaying an earlier recipe through an unpinned changed engine."],"exercise":{"prompt":"Write a durable-save acceptance checklist, then use actual receipts only if the existing private scope permits it.","deliverables":["Source, parent and engine pins.","Preview/save/readback distinctions.","An explicit list of authority and execution gates not granted by saving."],"success":["No successful save is claimed without an actual receipt.","Original versions remain addressable.","Private source data stays within its authorized context."]},"question":{"prompt":"What is the strongest evidence that a specific version survived saving?","choices":[{"text":"Scope-bound readback matching its immutable receipt and pinned recipe.","explanation":"Correct. It connects the actual stored bytes to the exact source and interpretation."},{"text":"A screenshot of a preview.","explanation":"A preview can exist without durable storage."},{"text":"The same title on a latest-version page.","explanation":"A title does not identify the saved byte-level lineage."}],"correctIndex":0},"screens":[{"title":"Private learning gateway","href":"/learn/deep-dive/private"},{"title":"Public complete evidence graph","href":"/pillars/p5#pillar-workspace"}],"sourceNotes":["This is a governed private acceptance exercise, not a claim that a learner has already performed an immutable save or company-authorized amendment."],"lessonLocator":"/learn/deep-dive/2027","recordReference":"#/lessons/26","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/26","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2028","track":"site","module":"practice","title":"Inspect synthetic observations without changing their meaning","goal":"Keep expected roles, generated observations, calculated results and missing context separate.","why":["A result can look convincing while its method, producing participant or sample context is absent. The learning value comes from preserving those differences.","Synthetic fixture values test software behavior; they do not qualify an assay or establish that the anonymous composition executed."],"model":["A declared blank, a supplied negative-control observation and an absent curve are different states. Missing data remains null rather than being replaced by zero.","The separate sample workspaces retain their own model, scenario, exact configuration and provenance. They must not be relabelled as observations from the public 0614141 composition."],"steps":[{"action":"Identify the fixture’s own context","control":"Sample model and scenario selectors","why":"The producer and configuration matter as much as the visible curve.","how":"Open the sample workspace only under existing authorized access. Read its synthetic scope and exact stored configuration/model references before interpreting a displayed observation.","expected":"A source-bound synthetic fixture, or an explicit access limit.","verify":"No real instrument measurement or clinical finding is claimed."},{"action":"Compare present, absent and fault cases","control":"Observation/result inspector and scenario selector","why":"Observed behavior and expected role cannot be collapsed into a single pass label.","how":"Compare a declared blank, supplied negative observation and missing result. Then inspect one fault or missing-context scenario. Record which raw values remain present and which fields are null.","expected":"Separate observation, result, expectation and assessment records.","verify":"Do not turn missing into negative or remove a failure to improve the result."},{"action":"Trace the result’s lineage","control":"Complete P5 graph and exact JSON","why":"A chart is only one human view of the fixture.","how":"Follow the result to its exact producing model/configuration and raw observation record. State the software test actually performed and the scientific validation not performed.","expected":"An inspectable synthetic lineage.","verify":"The public demo and the separate fixture remain separate contexts."}],"machine":{"pointers":[],"identifiers":[],"fields":["replicates.role","expectations.expectedSyntheticSignal","observations.availability","observations.observedSyntheticSignal","results","assessments.state","recipe.modelVersion","recipeSha256","profile.configuration","profile.source"],"explanation":"These are distinct fixture facts. The lesson does not transfer synthetic results between configurations or manufacture physical measurements."},"pitfalls":["Relabelling a separate synthetic dataset as the public demo’s run.","Replacing absent observations with plausible curves."],"exercise":{"prompt":"Classify three fixture states and one missing-context case without giving scientific advice.","deliverables":["A present observation, a declared control/blank and an absent result.","The exact fixture’s producing context where supplied.","The current assessment and its remaining evidence gaps."],"success":["Null stays null.","Expected role and observed value remain separate.","No assay qualification or patient interpretation is made."]},"question":{"prompt":"How should an absent curve be represented?","choices":[{"text":"As a zero-valued negative result.","explanation":"Zero and absence have different meanings."},{"text":"As missing/null with its expected role and context retained.","explanation":"Correct. Preserve the absence instead of fabricating an observation."},{"text":"With a generated replacement curve.","explanation":"That would hide the original missing state."}],"correctIndex":1},"screens":[{"title":"Synthetic sample library · existing access required","href":"/pharma/8/samples"},{"title":"Role scenarios · existing access required","href":"/scenarios"},{"title":"Practice workspace · existing access required","href":"/practice"}],"sourceNotes":["The sample workspaces are separate synthetic software fixtures. Their actual producing configuration and access controls govern the data, not this course label."],"lessonLocator":"/learn/deep-dive/2028","recordReference":"#/lessons/27","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/27","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2029","track":"site","module":"practice","title":"Turn a failed scenario into a measured tool improvement","goal":"Plan a test/inspect/adjust/retest comparison with exact before/after evidence.","why":["Thousands of generated designs do not show learning unless a measured weakness produces an evaluated adjustment.","A failure can expose a missing diagnostic rather than a proven hardware incompatibility. Preserve the original source state while improving the tool’s assessment."],"model":["Pin inputs, source snapshot, engine version, commands and expected invariants before comparing outcomes. Keep the failure, adjustment and replay result as separate records.","Structural replay, simulated observations, formal conformance, physical acceptance and model-weight training are different activities. Success in one does not establish the others."],"steps":[{"action":"Choose a reproducible weakness","control":"Practice or source-bound scenario evidence","why":"A vague goal such as “make it work” cannot show whether an adjustment helped.","how":"Select one retained software failure or diagnostic gap. Write the exact inputs and measurable expected difference before changing anything. If no supported failure is available, plan the comparison without inventing one.","expected":"A specific baseline with its verification limit.","verify":"Do not describe an inactive source choice as proven method incompatibility."},{"action":"Propose the narrow adjustment","control":"Recorded change and regression case","why":"The tool should improve its diagnosis without rewriting the source to look better.","how":"Describe a specific assessment or validation change and the regression input that exercises it. Keep the source values, rejected proposal and old engine/version evidence.","expected":"A testable improvement hypothesis.","verify":"No missing fact or compatibility proof is fabricated."},{"action":"Retest the same pinned inputs","control":"Before/after receipts and P5 history","why":"A new unrelated scenario cannot measure improvement in the original case.","how":"Compare the same recipes and source pins through the before and after tools. Count actual distinct inputs, executions and checks separately. Record unresolved outcomes and the measured diagnostic change.","expected":"A reproducible comparison, not only a new screenshot.","verify":"A successful structural replay is not a scientific experiment or weight-training result."}],"machine":{"pointers":[],"identifiers":[],"fields":["inputs","sourcePins","engineVersion","commands","failure","adjustment","replayResult","measurement"],"explanation":"Feedback is an attributed comparison over pinned inputs. The new assessment must not overwrite the original source or silently reinterpret earlier versions."},"pitfalls":["Counting repeated checks as new configurations.","Lowering a gap count by inventing a missing assertion."],"exercise":{"prompt":"Design one measured regression experiment for a configuration tool.","deliverables":["An exact baseline and one proposed narrow change.","The same-input retest plan.","Separate configuration, execution, structural and scientific counts."],"success":["The old failure and source survive.","The measured outcome corresponds to the stated weakness.","Adaptive learning is not claimed without recorded feedback and evaluated adjustment."]},"question":{"prompt":"What demonstrates a tool improvement?","choices":[{"text":"Generating more configurations.","explanation":"Volume alone does not identify an evaluated change."},{"text":"A lower gap count after filling unknown fields.","explanation":"Invented fields conceal rather than repair evidence gaps."},{"text":"A recorded narrow adjustment with measured same-input retest results.","explanation":"Correct. Preserve before/after evidence and regression coverage."}],"correctIndex":2},"screens":[{"title":"Scenario workspace · existing access required","href":"/scenarios"},{"title":"Evidence graph","href":"/pillars/p5#pillar-workspace"}],"sourceNotes":["Current configuration-feedback operating rule. This lesson is a comparison exercise, not proof that a learner’s new tool adjustment has been executed."],"lessonLocator":"/learn/deep-dive/2029","recordReference":"#/lessons/28","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/28","referenceKind":"educational-content-locator-not-gs1-identity"},{"number":"2030","track":"site","module":"practice","title":"Complete an end-to-end evidence review","goal":"Produce an inspectable explanation of one composition and its readiness limits.","why":["A client should finish able to explain the solution through its records, not only repeat the five pillar names.","The next appropriate action depends on the evidence actually present. A well-documented hold is often more useful than an unsupported “ready” label."],"model":["The evidence review retains exact participants, their capabilities and source documents, protocol family/version, selected configuration, operating design and provenance.","Identity assignment, customer authority, method validation, executable transport, environment binding and physical action are separate decisions with separately recorded evidence."],"steps":[{"action":"Choose the exact composition","control":"Propose the PCR run and Participants & materials","why":"An exact step and directed participant assertion make the review reproducible.","how":"Open the named educational step. Select its exact thermal-cycler participant and record the retained step GDTI, asset GIAI, relationship identifier and source pointer.","expected":"A precise entry into the composition.","verify":"Do not replace any identity with a model name or a file hash."},{"action":"Follow the complete context","control":"P5 node/edge inspector and complete JSON","why":"A focused graph can clarify the context while preserving all original facts.","how":"Inspect the selected record and a directed relationship. Record actor, authority, time, scope and unknowns, then restore the complete graph and compare its total with the focused subset.","expected":"A source-bound explanation and a known viewport scope.","verify":"No original records were discarded by focus or filtering."},{"action":"State the next governed step","control":"Readiness discussion and evidence checklist","why":"Publication and education must not be mistaken for commissioning.","how":"List what the sample demonstrates, what requires customer review and what requires actual instrument/cloud testing. Choose one missing evidence item to request within its proper authority scope; do not send the request or grant access from this exercise.","expected":"A concrete review package with explicit limits.","verify":"The next step does not infer ownership, approval or execution permission."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps/5","#/P5/nodes/1","#/P5/edges/189"],"identifiers":["urn:epc:id:gdti:0614141.00105.1","urn:epc:id:giai:0614141.4","urn:epc:id:gdti:0614141.00900.190"],"fields":["state","provenance","assertingActorId","authorityEvidence","assertionTime","scope"],"explanation":"These exact retained references identify the illustrative step, participant and directed assertion. They stay non-issued and do not represent an executed service instance."},"pitfalls":["Using a green presentation state as an execution permit.","Claiming the capstone checked a private fixture it did not inspect."],"exercise":{"prompt":"Write a one-composition review that an agent and a client can both follow.","deliverables":["Exact P1–P5 references and source pointers.","A distinction between full and focused graph scope.","Original assertions, current assessments and explicit missing evidence.","One scoped next-step recommendation."],"success":["Every claimed relationship is inspectable.","Unknowns and non-issued states remain explicit.","No hardware/cloud action, scientific approval or authority grant is claimed."]},"question":{"prompt":"What is the capstone’s completion evidence?","choices":[{"text":"An exact, inspectable review with retained gaps and a scoped next step.","explanation":"Correct. This is a learning/review outcome, not a commissioning or certification claim."},{"text":"A claim that the instrument is ready to run.","explanation":"Real readiness needs separate evidence and execution gates."},{"text":"The total number of graph nodes.","explanation":"Graph size alone is not solution readiness."}],"correctIndex":0},"screens":[{"title":"Start the exact public review","href":"/pillars/p3?step=urn%3Aepc%3Aid%3Agdti%3A0614141.00105.1#pillar-workspace"},{"title":"Inspect the exact participant and assertion","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context&from=%23%2FP3%2FprotocolTemplates%2F0%2Fordered_steps%2F5&via=urn%3Aepc%3Aid%3Agdti%3A0614141.00900.190#pillar-workspace"}],"sourceNotes":["Capstone over the fixed anonymous sample. No real unit, scientific result or new service instance is created."],"graph":{"node":"urn:epc:id:giai:0614141.4","from":"#/P3/protocolTemplates/0/ordered_steps/5","via":"urn:epc:id:gdti:0614141.00900.190"},"lessonLocator":"/learn/deep-dive/2030","recordReference":"#/lessons/29","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/29","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"practice","title":"Foreword · Why the physical world needs context","goal":"Turn the book’s participation thesis into questions an agent can answer with evidence.","why":["A device reading says little when its exact source, method and circumstances are unknown.","The foreword connects identity, sensing, communication and memory; a useful system must explain their relationships, not merely display their names."],"model":["Treat the civilization analogy as a design lens, not a claim of legal citizenship or biological consciousness.","For an anonymous instrument, distinguish its identity record, proposed role, observation evidence, operating permission and history. Each is a separate question."],"steps":[{"action":"Translate the thesis into inspectable questions","control":"Book source references below","why":"Broad ambition needs measurable boundaries.","how":"Read the foreword’s identity-and-participation argument. Write separate questions for which thing, which activity, which evidence and whose authority.","expected":"A four-question context checklist.","verify":"Every question asks for a source or an explicitly unknown value."},{"action":"Test the questions against one record","control":"Open the exact sample asset graph","why":"The sample shows how context is inspected without pretending to be a real unit.","how":"Select the asset, inspect its state and source, then inspect one directed relationship and its authority evidence.","expected":"The asset and relationship remain distinct records.","verify":"Non-issued state and unknown authority are retained in your notes."}],"machine":{"pointers":["#/P1/sourceAssertions","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["state","evidenceState","authorityEvidence","scope"],"explanation":"The sample record is educational software evidence. The foreword is a source for the design thesis, not verification of this asset or an execution grant."},"pitfalls":["Reading an authored future as proof that all capabilities already exist.","Treating the “living thing” metaphor as measured consciousness."],"exercise":{"prompt":"Write an evidence-first introduction for a new anonymous instrument.","deliverables":["Four context questions","One exact demo record address","One observed unknown and its consequence"],"success":["Identity, evidence and authority are separate","The introduction does not claim a verified unit or live execution"]},"question":{"prompt":"What would make the foreword’s thesis testable?","correctIndex":0,"choices":[{"text":"Specific context questions with evidence and unknown states.","explanation":"They turn a broad vision into independently inspectable requirements."},{"text":"A larger graph picture.","explanation":"Size does not establish evidence, authority or completeness."},{"text":"Calling every identified object a live agent.","explanation":"An identifier does not prove sensing, agency or permission."}]},"screens":[{"title":"Exact educational asset and context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"}],"number":"3001","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Foreword","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[208]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Foreword","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[211]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Foreword","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[213]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Foreword","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[219]","classification":"design_principle"}],"sourceNotes":["Foreword · 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.","The foreword contains broad authored deployment assertions. This lesson does not adopt those assertions as current proof.","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."],"lessonLocator":"/learn/deep-dive/3001","recordReference":"#/lessons/30","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/30","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"practice","title":"Prologue · Integration heritage without losing meaning","goal":"Explain the author’s historical path from document translation to physical identity continuity.","why":["A purchase instruction has business meaning beyond its field positions.","The author’s supply-chain story asks how one physical identifier can remain meaningful across sensing and business records."],"model":["The book attributes the idea to enterprise semantic translation, event propagation and physical tracking experience.","History motivates the architecture; it does not independently prove today’s deployment, scale or proprietary claims."],"steps":[{"action":"Separate semantic meaning from format","control":"Prologue source paragraphs","why":"Copying fields can lose a transaction’s meaning.","how":"Sketch an anonymous order in two different formats. Preserve the item, parties, conditions and requested action; mark a field with no exact counterpart as unresolved.","expected":"A source-to-target meaning comparison.","verify":"No field is guessed merely to complete the target."},{"action":"Follow continuity rather than a company name","control":"P1 source assertions and P5 inspector","why":"The architectural lesson concerns exact references, not brand labels.","how":"Inspect the sample asset identifier in P1 and reopen that exact address in P5. Note what persists and what belongs to a separate source occurrence.","expected":"The same retained identifier across two views.","verify":"No shared label is used as an identity join."}],"machine":{"pointers":["#/P1/demo_giai","#/P1/sourceAssertions","#/P5/nodes"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["urn","source_prefix","evidenceState","sourceLocator"],"explanation":"Public learning uses an anonymous fixture. The historical accounts remain attributed to the author; their private company examples are not copied into this course."},"pitfalls":["Turning an author’s recollection into a verified business-history claim.","Treating semantic translation as permission to overwrite a source identifier."],"exercise":{"prompt":"Describe the heritage in three anonymous stages.","deliverables":["Document-meaning stage","Physical-reference continuity stage","Present-day evidence boundary"],"success":["The historical account is attributed","The current demonstration is described separately","Unmatched semantics remain unknown"]},"question":{"prompt":"What is the safest lesson to carry forward from the prologue?","correctIndex":1,"choices":[{"text":"All older platform integrations are live today.","explanation":"The book’s history does not verify current endpoints."},{"text":"Preserve meaning and exact references while systems differ.","explanation":"This is a design principle that can be tested without endorsing historical scale claims."},{"text":"Matching names prove the records are equivalent.","explanation":"Names are human labels, not identity or authority evidence."}]},"screens":[{"title":"Identity and source assertions","href":"/pillars/p1#pillar-workspace"},{"title":"The same asset in P5","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"}],"number":"3002","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[221]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[225]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[229]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[235]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[243]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[246]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[248]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Prologue","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[252]","classification":"author_history"}],"sourceNotes":["Prologue · author history. 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.","Enterprise and supply-chain examples are the author’s historical account; commercial scale and first-in-history assertions are not independently verified here.","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."],"lessonLocator":"/learn/deep-dive/3002","recordReference":"#/lessons/31","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/31","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p1","title":"Identity preface · Standards, carriers and exact keys","goal":"Distinguish a standard identifier, its carrier, a lookup location and namespace authority.","why":["Physical systems already contain identifiers; integration must preserve them rather than replace them with labels.","A carrier transports a value. A URL locates a resource. Neither alone proves an identity allocation or an authorized relationship."],"model":["Read the preface as an argument for persistent, typed references, not proof of exclusive superiority over every other system.","Use the current key-role palette and explicit assignment state. The book’s older key inventory and examples are not the current construction specification."],"steps":[{"action":"Classify what each representation does","control":"P1 key-type controls","why":"Different representations answer different questions.","how":"Inspect GIAI, GDTI and SGLN examples. Describe the physical unit, document or location role; separately identify the prefix and non-issued state.","expected":"Three typed-role explanations.","verify":"PGLN is banned as a ThingDaddy ID type. The prefix is never treated as a company-authority grant."},{"action":"Separate address from access","control":"Exact sample P5 inspector","why":"Resolvable context and permitted action are separate gates.","how":"Compare an exact EPC URN with the page URL used to inspect it. Record which identifies a proposed participant and which locates a view.","expected":"A key-versus-location distinction.","verify":"The page URL is never substituted for the retained EPC identity."}],"machine":{"pointers":["#/P1/manufacturerPrefix","#/P1/prefixEvidence","#/P1/demo_giai","#/P1/demo_gdti","#/P1/demo_sgln"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["key_type","state","allocation_authority_evidence","identity_equivalence_asserted"],"explanation":"Current demo state and current governance supersede older illustrative construction examples. This lesson does not mint a key, infer allocation or introduce a new public routing mechanism."},"pitfalls":["Copying alphanumeric or obsolete book examples as valid current ThingDaddy proposals.","Assuming an identifier’s digits establish owner, legal party or permission."],"exercise":{"prompt":"Create a representation table for one anonymous asset.","deliverables":["Identifier role","Carrier role","View URL role","Allocation/authority unknowns"],"success":["Key, carrier and URL are distinct","Original supplied identifiers are preserved","No allocation is inferred from a label or digit pattern"]},"question":{"prompt":"A scanner reads an asset identifier. What has been established?","correctIndex":2,"choices":[{"text":"The scanner has granted remote operation.","explanation":"A carrier observation is not authorization."},{"text":"The page URL becomes the asset’s permanent key.","explanation":"A resource location does not replace the asset identity."},{"text":"An observed value requiring exact resolution and evidence review.","explanation":"Reading a value does not by itself authenticate a unit, allocation or permission."}]},"screens":[{"title":"Typed identity roles","href":"/pillars/p1#pillar-workspace"},{"title":"Asset record rather than page address","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"}],"number":"3003","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Identity preface","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[254]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Identity preface","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[255]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Identity preface","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[260]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Identity preface","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[2]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Identity preface","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[3]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Identity preface","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[274]","classification":"design_principle"}],"sourceNotes":["Identity preface · 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.","The preface includes older syntax examples, scale claims and routing assertions. They are preserved in the original source, not promoted into current rules or public mechanisms.","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."],"lessonLocator":"/learn/deep-dive/3003","recordReference":"#/lessons/32","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/32","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p1","title":"Chapter 1 · From an object record to participation","goal":"Model identity, communication, relationships, history and accountability as distinct evidence requirements.","why":["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."],"model":["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."],"steps":[{"action":"Build a participation checklist","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.","expected":"A six-property requirements matrix.","verify":"No property is marked verified merely because a key exists."},{"action":"Compare the checklist with the demo","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.","expected":"A supported-versus-missing comparison.","verify":"Unknowns are retained as fields, not hidden behind a reassuring paragraph."}],"machine":{"pointers":["#/P1/sourceAssertions","#/P2/mhsSilaDriver","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["state","nativeSilaSupport","authorityEvidence","assertionTime"],"explanation":"These software records illustrate participation structure. They do not establish legal citizenship, tested communication, sensing or physical accountability."},"pitfalls":["Equating a registered record with an authenticated physical participant.","Treating the seven-layer conceptual model as seven automatically passed gates."],"exercise":{"prompt":"Assess an anonymous instrument against the participation matrix.","deliverables":["Six evidence requirements","Two exact demo references","At least two unresolved evidence states"],"success":["Each requirement has a source or unknown","Accountability is not inferred from an identifier","Conceptual layers remain separate from implemented gates"]},"question":{"prompt":"Which description best fits a registered but untested instrument proposal?","correctIndex":0,"choices":[{"text":"An identified proposal with explicit capability and authority gaps.","explanation":"Identification enables addressing; the remaining participation evidence still needs checking."},{"text":"A fully trusted participant in every system.","explanation":"Registration cannot prove every relationship and runtime capability."},{"text":"An unusable record that must be hidden.","explanation":"Uncertainty should remain addressable while unrelated safe learning proceeds."}]},"screens":[{"title":"Participant identity","href":"/pillars/p1#pillar-workspace"},{"title":"Inspect participation evidence","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"}],"number":"3004","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[282]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[285]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[289]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[294]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[4]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[303]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[313]","classification":"design_principle"}],"sourceNotes":["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."],"lessonLocator":"/learn/deep-dive/3004","recordReference":"#/lessons/33","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/33","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p2","title":"Chapter 2 · Sensing as a contextual event","goal":"Describe why a carrier read needs exact object, place, activity and event evidence.","why":["A scan is an observation of a value in a particular setting, not a complete business conclusion.","The chapter’s supply-chain account connects movements and states to a durable asset reference."],"model":["Separate observed value, observer, time, location, quality and workflow interpretation.","Two reads of the same identifier are two observations; they do not create two physical units or prove a custody transfer."],"steps":[{"action":"Decompose a hypothetical receiving scan","control":"Chapter 2 sensing and movement passages","why":"Business interpretation depends on more than the scanned digits.","how":"Write an anonymous dock-read record with value, observer, time, location and observation quality. Add a separate proposed receiving interpretation.","expected":"An observation plus a distinct interpretation.","verify":"Unknown timestamps and authority remain unknown rather than invented."},{"action":"Check what the demo actually contains","control":"P2 components and P5 source assertions","why":"The fixture’s source records are not live carrier measurements.","how":"Inspect the thermal sensor context and its source. Identify which fields describe a proposal and which real observation fields are absent.","expected":"A source-versus-observation inventory.","verify":"No generated fixture value is described as a physical scan."}],"machine":{"pointers":["#/P2/modules","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:cpi:0614141.414141.41"],"fields":["physicalUnitVerification","evidenceState","assertionTime","scope"],"explanation":"The demo illustrates asset/component relationships. A carrier-observation record with sensor quality, observer and observed time would be additional evidence, not something inferred from this fixture."},"pitfalls":["Repeating the chapter’s scan volumes as current measured platform throughput.","Inferring transfer of ownership from an observed movement."],"exercise":{"prompt":"Draft a receiving-event evidence envelope without executing anything.","deliverables":["Observed-value record","Workflow-interpretation proposal","Missing-evidence list"],"success":["The observation and interpretation are separate","No custody or ownership is inferred","The draft is clearly hypothetical"]},"question":{"prompt":"What does a repeated read of the same identifier imply?","correctIndex":1,"choices":[{"text":"A second physical asset was manufactured.","explanation":"Read count is not asset count."},{"text":"Another observation whose context must be retained.","explanation":"Each read has its own observer, time and interpretation; neither identity nor custody should be guessed."},{"text":"Ownership changed at the read point.","explanation":"Ownership requires an evidenced, authorized relationship."}]},"screens":[{"title":"Candidate sensing participants","href":"/pillars/p2#pillar-workspace"},{"title":"Source context for the sensor","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context#pillar-workspace"}],"number":"3005","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[317]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[320]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[322]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[334]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[337]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[338]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[339]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[340]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[343]","classification":"author_history"}],"sourceNotes":["Chapter 2 · author history. 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.","The supply-chain history and throughput figures remain authored assertions; no live sensing or event-ingestion capability is verified by these screens.","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."],"lessonLocator":"/learn/deep-dive/3005","recordReference":"#/lessons/34","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/34","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p3","title":"Chapter 3 · Context beyond the registry","goal":"Carry an exact participant from a proposed protocol into its evidence graph without creating a new identity.","why":["The chapter argues that identity alone does not supply workflows, semantics, provenance or authority.","An agent needs the relationship between a participant and a particular step, not just a catalogue name."],"model":["A step definition, a participant and their directed assertion are three separate addresses.","Required role labels do not bind physical participants. A retained assertion can be inspected without being promoted to compatibility or execution permission."],"steps":[{"action":"Inspect the proposed run-step context","control":"P3 selected step and participants tab","why":"The workflow is where an identifier acquires a specific proposed role.","how":"Open the proposed run step and compare its definition GDTI with the participant IDs and exact directed assertion IDs.","expected":"Separate step, participant and relationship addresses.","verify":"The occurrence pointer is not relabeled as a GS1 asset key."},{"action":"Traverse and return","control":"Open exact participant in P5; return to the same protocol step","why":"Continuity matters only if the receiver validates the precise references.","how":"Follow one participant link, inspect its original record and incoming assertion, then return to the original step.","expected":"Exact navigation with no name-based substitution.","verify":"The participant address and step definition match before and after navigation."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps/5","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:gdti:0614141.00105.1"],"fields":["stepDefinitionGdti","a","b","t","id","authorityEvidence"],"explanation":"The current public walkthrough demonstrates exact directed relationship traversal inside an authored sample. It does not run a protocol or establish a physical binding."},"pitfalls":["Joining a participant by a similarly named record.","Treating a source assertion as a tested or company-approved configuration."],"exercise":{"prompt":"Record one complete step-to-participant inspection trail.","deliverables":["Step GDTI and occurrence pointer","Participant address","Directed assertion address","Authority and validation gaps"],"success":["All three records remain distinct","The return link opens the same definition","No proposed edge is called a verified physical bond"]},"question":{"prompt":"Why is the directed step-participant assertion needed?","correctIndex":2,"choices":[{"text":"It replaces the participant’s original identity.","explanation":"A relationship must preserve both original endpoints."},{"text":"It grants instrument execution.","explanation":"A contextual assertion is not an execution authorization."},{"text":"It preserves the specific role claim and its provenance.","explanation":"Endpoints alone do not explain why a particular step references a participant."}]},"screens":[{"title":"Proposed PCR run step","href":"/pillars/p3?step=urn%3Aepc%3Aid%3Agdti%3A0614141.00105.1#pillar-workspace"},{"title":"Complete connected graph","href":"/pillars/p5#pillar-workspace"}],"number":"3006","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[351]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[352]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[356]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[5]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[361]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[363]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[365]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[368]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[371]","classification":"design_principle"}],"sourceNotes":["Chapter 3 · 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.","The demonstrated operation is read-only context traversal. Cross-system orchestration and physical action still require their own implementation, validation and authorization evidence.","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."],"lessonLocator":"/learn/deep-dive/3006","recordReference":"#/lessons/35","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/35","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p4","title":"Chapter 4 · Local operation and shared memory","goal":"Assign proposed edge, site and cloud responsibilities without claiming deployment.","why":["A physical process has local timing and safety needs; shared history has different retention and disclosure needs.","The chapter warns against treating edge and cloud as the same responsibility at different sizes."],"model":["Separate proposed local evaluation, site oversight, long-term storage and authorized cross-party sharing.","Local authority must be recorded; the edge-versus-cloud distinction is not a bypass around permission or safety gates."],"steps":[{"action":"Allocate responsibilities","control":"Chapter 4 jurisdiction discussion","why":"An operating design should say where and under whose authority work happens.","how":"For a hypothetical instrument, assign sensing, allowed local response, audit retention and external disclosure to separate responsibilities.","expected":"A responsibility and authority matrix.","verify":"Every consequential response names a required delegation and test gate."},{"action":"Inspect the proposed environment","control":"AWS and Azure design options","why":"Selecting a pattern is not provisioning an account or runtime.","how":"Compare two environment choices and list missing site, runtime, security, binding and deployment receipts.","expected":"An unbound deployment checklist.","verify":"No selected provider is described as commissioned infrastructure."}],"machine":{"pointers":["#/P4"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["state","cloudResourcesCreated","cloudDeploymentValidated","executionAuthorized"],"explanation":"P4 records educational operating patterns. Real endpoints, account ownership, deployed adapters, authority and bind-test outcomes need separately supplied evidence."},"pitfalls":["Promising the chapter’s latency or optimization figures without measurements.","Calling a cloud pattern an installed, secure runtime."],"exercise":{"prompt":"Draft a local-versus-shared-memory plan for one anonymous configuration.","deliverables":["Responsibility matrix","Missing binding evidence","Authorized-disclosure scope"],"success":["Local action is scoped and tested","Shared storage does not imply universal access","All infrastructure remains proposed"]},"question":{"prompt":"What changes when an environment pattern is selected?","correctIndex":0,"choices":[{"text":"The proposed design choice, not deployment or action authority.","explanation":"The choice needs binding, validation and authorization receipts before it can describe a working environment."},{"text":"All required cloud resources are created.","explanation":"The demo does not provision infrastructure."},{"text":"The local runtime no longer needs permission.","explanation":"Local autonomy requires recorded, scoped delegation."}]},"screens":[{"title":"Unbound cloud and edge designs","href":"/pillars/p4#pillar-workspace"}],"number":"3007","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[379]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[382]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[385]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[393]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[397]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[401]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[405]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[409]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[7]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[412]","classification":"future_vision"}],"sourceNotes":["Chapter 4 · 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.","Local sensing, safety responses and global lifecycle memory are architectural responsibilities, not measured runtime capabilities of this sample.","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."],"lessonLocator":"/learn/deep-dive/3007","recordReference":"#/lessons/36","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/36","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p1","title":"Chapter 5 · Design, model and physical unit","goal":"Plan a design-to-unit evidence chain while keeping a design proposal distinct from manufacture.","why":["A design describes a family or intended construction; a physical unit has its own identity and observation history.","The chapter’s birth-certificate metaphor encourages provenance from design onward, but manufacture cannot be inferred from a drawing."],"model":["Retain the design document, its revision, intended model, candidate unit and component-role records separately.","A commissioning or first-observation event is a later record with its own actor, time and evidence. The current walkthrough has no CAD or manufacture receipt."],"steps":[{"action":"Draw a design-to-unit record map","control":"Chapter 5 design and manufacture discussion","why":"Lifecycle continuity must not flatten a model into its units.","how":"Sketch an anonymous design revision, a model description, two prospective units and one component role. Mark every link as a proposal until supported.","expected":"Distinct design, model, unit and role records.","verify":"Two units never share a single substituted model identity."},{"action":"Compare asset and installed context","control":"P1 GIAI/CPI controls and P5 sensor view","why":"A component’s source identity survives an installed-context role.","how":"Inspect the GIAI role and the supplied CPI context. Locate the original supplier-asset relationship and record its unknown physical verification.","expected":"A preserved source identity and separate context.","verify":"No design-stage proposal is described as issued or installed."}],"machine":{"pointers":["#/P1/demo_giai","#/P1/demo_cpi","#/P2/modules","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:cpi:0614141.414141.41"],"fields":["physicalUnitVerification","state","authorityEvidence","assertionTime"],"explanation":"The sample demonstrates record distinctions. CAD files, manufacturing events and exact physical-unit verification are absent and must remain explicitly absent."},"pitfalls":["Using the book’s genetic analogy to merge design, model and unit identity.","Inventing manufacture dates or treating a first observed startup as the first-ever startup."],"exercise":{"prompt":"Specify an evidence chain for two units built from one proposed design.","deliverables":["Design/model/unit diagram","Manufacture-event evidence requirements","Component origin/context distinction"],"success":["Both units remain individually addressable","Missing dates stay unknown","No CAD or manufacture integration is claimed"]},"question":{"prompt":"Two units share a design. Which record may safely be shared?","correctIndex":1,"choices":[{"text":"One physical-unit identity for both.","explanation":"That would flatten two assets into one record."},{"text":"A referenced design or model record, while unit identities remain separate.","explanation":"Common design does not erase the physical units’ individual histories."},{"text":"One invented manufacture event.","explanation":"Manufacture needs specific observed and authorized evidence."}]},"screens":[{"title":"Physical unit and installed-context roles","href":"/pillars/p1#pillar-workspace"},{"title":"Separate component context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context#pillar-workspace"}],"number":"3008","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[420]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[421]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[423]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[427]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[428]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[429]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[8]","classification":"future_vision"}],"sourceNotes":["Chapter 5 · 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.","CAD integration, manufacture, commissioning and lifecycle timestamps are future requirements, not implemented proof from this fixture.","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."],"lessonLocator":"/learn/deep-dive/3008","recordReference":"#/lessons/37","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/37","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p1","title":"Chapter 6 · Commercial records without identity replacement","goal":"Distinguish product, unit, shipment, logistics and document references in a hypothetical hand-off.","why":["A commercial transaction refers to several different things: the product ordered, the unit shipped, the packaging, parties and documents.","Continuity across records should preserve these distinctions rather than invent an interchangeable universal number."],"model":["Use typed roles for a unit, trade item, logistics unit, shipment, consignment and document.","A shipment record is evidence about movement, not proof of custody, ownership or payment. Exact commercial formats require their governed implementation guides."],"steps":[{"action":"Separate the transaction participants","control":"Chapter 6 commercial chain and hierarchy tables","why":"A shipping hierarchy has multiple objects, not one flattened asset.","how":"Sketch an anonymous order, one instrument unit, its product record, a logistics container and a shipment. Assign role labels without generating new keys.","expected":"A role-specific commercial graph draft.","verify":"Documents and packaging are not substituted for the physical unit."},{"action":"Use the current role palette carefully","control":"P1 GDTI, SSCC, GINC and GSIN controls","why":"The real demo can illustrate key roles, not a commercial transaction.","how":"Inspect the roles and assignment states. List the source interchange, partner guide, actor and receipt needed before connecting a real order to a real unit.","expected":"A commercial-evidence requirements list.","verify":"No historical segment example is used as a current partner specification."}],"machine":{"pointers":["#/P1/demo_gdti","#/P1/demo_sscc","#/P1/demo_ginc","#/P1/demo_gsin"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["key_type","state","customer_review","allocation_authority_evidence"],"explanation":"The palette shows non-issued identifier roles. It does not demonstrate EDI integration, delivery, payment, custody transfer or an authorized commercial relationship."},"pitfalls":["Saying one identifier replaces product, packaging and unit identities.","Copying book segment examples as universally correct implementation instructions."],"exercise":{"prompt":"Prepare a proposed evidence map for an instrument shipment.","deliverables":["Six separate object/document roles","Required partner-profile evidence","Custody/ownership unknowns"],"success":["Unit and packaging remain distinct","The exact original interchange would be retained","No shipment, payment or legal transfer is claimed"]},"question":{"prompt":"A logistics container has an identifier. Does it identify every contained instrument?","correctIndex":2,"choices":[{"text":"Yes; the container key replaces every unit key.","explanation":"That loses the units and their individual histories."},{"text":"Yes, if the company names match.","explanation":"Names do not establish object equivalence."},{"text":"No; containment references individually identified contents.","explanation":"Container identity and contained-unit identity have different purposes."}]},"screens":[{"title":"Document, shipment and logistics roles","href":"/pillars/p1#pillar-workspace"}],"number":"3009","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[436]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[439]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[9]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[444]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[445]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[447]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[450]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 6","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[453]","classification":"future_vision"}],"sourceNotes":["Chapter 6 · 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.","Commercial integration, partner profiles, signed transactions and transfer authority are not demonstrated. Older hierarchy examples are not a current conformance specification.","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."],"lessonLocator":"/learn/deep-dive/3009","recordReference":"#/lessons/38","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/38","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p4","title":"Chapter 7 · Remote monitoring needs governed scope","goal":"Plan a narrow instrument-health sharing scope without treating identity or a contract label as access permission.","why":["Instrument-health observations and process/customer data can have different disclosure requirements.","The chapter identifies network, platform, ownership, multi-provider and validation problems; common addressing alone cannot close those gates."],"model":["Model the requesting party, resource, fields, time window, intended use, authority evidence and revocation separately.","A prefix or warranty document reference is not itself a technical grant, legal conclusion or tested security boundary."],"steps":[{"action":"Draft a minimal sharing request","control":"Chapter 7 problem table","why":"A safe integration starts with the scope of data and action.","how":"Describe anonymous health telemetry and separately list excluded sample/process data. Specify recipient, purpose, duration and approval evidence required.","expected":"A narrow disclosure proposal.","verify":"No ownership or recipient authority is inferred from a prefix."},{"action":"Identify the missing operating evidence","control":"P4 binding requirements and P5 authority fields","why":"The design must remain unbound until security and authorization are evidenced.","how":"Compare the request with the sample’s unknown environment and authority states. List required access-policy tests, revocation tests and audit receipts.","expected":"A validation and authorization gate list.","verify":"The proposal makes no claim of bypassing network controls."}],"machine":{"pointers":["#/P4","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["authorityEvidence","scope","executionAuthorized"],"explanation":"The fields illustrate the need for scoped authority. They do not establish a live remote monitor, legal access right, network exception or enforced data filter."},"pitfalls":["Repeating “zero firewall rules” as a verified security capability.","Assuming an instrument identifier establishes ownership of its process data."],"exercise":{"prompt":"Write a read-only health-data sharing proposal.","deliverables":["Included/excluded fields","Recipient and purpose","Authority, expiry and revocation evidence required"],"success":["Process data is not silently included","Identity and permission remain separate","No remote connection or legal right is claimed"]},"question":{"prompt":"What is needed before sharing a customer instrument’s telemetry?","correctIndex":0,"choices":[{"text":"Recorded scope and authority plus tested technical controls.","explanation":"An address identifies the subject; authorization and security enforcement require separate evidence."},{"text":"A matching manufacturer prefix only.","explanation":"A prefix does not grant access to customer resources."},{"text":"A page labeled warranty.","explanation":"A document label alone is not a legal or technical access grant."}]},"screens":[{"title":"Proposed operating scope","href":"/pillars/p4#pillar-workspace"},{"title":"Unknown relationship authority","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"}],"number":"3010","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[461]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[468]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[10]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[470]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[477]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[480]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[483]","classification":"future_vision"}],"sourceNotes":["Chapter 7 · 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 lesson teaches disclosure planning, not security/legal advice or internal access mechanisms. Remote monitoring and claimed network outcomes are not verified here.","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."],"lessonLocator":"/learn/deep-dive/3010","recordReference":"#/lessons/39","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/39","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p2","title":"Chapter 8 · Discovery starts with an observation","goal":"Separate a carrier observation, identity resolution, contextual relationship and allowed response.","why":["Sensing can reveal a participant’s presence, but presence is not a verified installation or permission.","The book’s awakening metaphor emphasizes the transition from a static record to time-bound observations."],"model":["An observation has its own value, observer, time, place and quality.","A discovered identifier can lead to inspection of existing context. Any proposed friendship, installation or action needs a separate assertion and authority state."],"steps":[{"action":"Describe a hypothetical startup encounter","control":"Chapter 8 discovery table and passages","why":"One observed startup is not an asset’s whole history.","how":"Draft a startup observation with the existing asset address. Preserve unknown prior history and mark any inferred location or relationship as a proposal.","expected":"An observation plus proposed context.","verify":"The timestamp is unknown unless an actual observation supplies it."},{"action":"Inspect the relationship rather than assume it","control":"P5 sensor context and exact relationship inspector","why":"A relation’s source and state matter as much as its endpoints.","how":"Open the component context and inspect its original directed links. Record why they are illustrative rather than observed installation evidence.","expected":"A contextual relationship assessment.","verify":"No permanent physical bond is created by a sensor label or graph line."}],"machine":{"pointers":["#/P2/modules","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:cpi:0614141.414141.41"],"fields":["physicalUnitVerification","assertionTime","authorityEvidence","scope"],"explanation":"The current graph is an authored educational composition. Real startup/carrier observations and responses would be additional separately identified records."},"pitfalls":["Treating a first recorded startup as the first startup ever.","Equating sensing or “friend” language with identity equivalence, installation or consciousness."],"exercise":{"prompt":"Make an observation-to-resolution flow with two stopping gates.","deliverables":["Observation envelope","Exact resolution target","Relationship-evidence gate","Action-authorization gate"],"success":["Resolution does not execute anything","Prior history is preserved","Inferences remain distinct from observations"]},"question":{"prompt":"A carrier reveals an unfamiliar identifier. What is the next safe action?","correctIndex":1,"choices":[{"text":"Install its driver and execute immediately.","explanation":"Transport, compatibility, safety and authority are not established."},{"text":"Resolve and inspect its exact context and unknowns.","explanation":"Discovery supplies a value to investigate, not a verified relationship or action grant."},{"text":"Merge it with a familiar model name.","explanation":"That would erase exact-asset distinctions."}]},"screens":[{"title":"Inspect the proposed sensor context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context#pillar-workspace"},{"title":"Candidate sensing descriptions","href":"/pillars/p2#pillar-workspace"}],"number":"3011","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 8","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[491]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 8","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[494]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 8","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[498]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 8","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[11]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 8","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[501]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 8","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[509]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 8","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[12]","classification":"future_vision"}],"sourceNotes":["Chapter 8 · 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.","Startup chips, sensor-triggered discovery and automated responses are vision examples, not current hardware evidence. Digital-life language remains a metaphor.","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."],"lessonLocator":"/learn/deep-dive/3011","recordReference":"#/lessons/40","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/40","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p5","title":"Chapter 9 · Ground reasoning without pretending to know everything","goal":"Answer a narrow asset question using exact context, cited evidence and explicit unknowns.","why":["General model knowledge cannot establish a particular unit’s calibration, location or current method.","The chapter’s ambition of complete operational awareness becomes useful when framed as questions whose evidence can be checked."],"model":["Separate retrieved source fact, current assessment, inference and consequential recommendation.","A confident answer does not close missing observations, authorization or validation. Complete awareness is an aspiration, not this fixture’s state."],"steps":[{"action":"Convert a broad question into a scoped one","control":"Chapter 9 requirement list","why":"“Is this instrument safe?” is too broad to prove with a graph label.","how":"Ask which exact asset, which proposed method version, which source evidence and what decision is intended. List the records needed to answer.","expected":"A bounded question and evidence plan.","verify":"The question does not demand a clinical, regulatory or operational decision from demo data."},{"action":"Produce an evidence-bounded answer","control":"P5 exact JSON and directed relationships","why":"Grounding includes reporting what is absent.","how":"Inspect the asset and a method relation. Cite addresses, state what the fixture asserts and list the missing calibration/runtime/authority evidence.","expected":"An answer with separate facts and unknowns.","verify":"No sample source assertion is called a measured result."}],"machine":{"pointers":["#/P5/nodes","#/P5/edges","#/P3/typedGaps"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["evidenceState","authorityEvidence","assertionTime","state"],"explanation":"Current graph inspection supports evidence-bounded retrieval. It does not prove predictive maintenance, automated release, regulatory filing or omniscience."},"pitfalls":["Using a language-model confidence score as a substitute for validation.","Reporting unobserved current state as known because historical context exists."],"exercise":{"prompt":"Answer: “What can we establish about this exact sample asset’s proposed protocol role?”","deliverables":["Exact addresses","Source-supported statements","Explicit unknowns","Safe next evidence request"],"success":["Facts and inferences are labeled","No action is authorized","The answer can be reproduced from retained JSON"]},"question":{"prompt":"A graph has a method relationship but no calibration evidence. What may the agent conclude?","correctIndex":2,"choices":[{"text":"The instrument is calibrated because the graph is connected.","explanation":"Graph connectivity is not calibration evidence."},{"text":"A high confidence answer can fill the gap.","explanation":"Confidence does not manufacture observations or authority."},{"text":"The method relationship is inspectable; calibration remains unknown.","explanation":"Each proposition needs its own evidence. One relationship cannot prove another state."}]},"screens":[{"title":"Evidence-bounded asset context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"},{"title":"Protocol gaps and constraints","href":"/pillars/p3#pillar-workspace"}],"number":"3012","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[519]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[522]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[525]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[526]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[527]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[528]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[529]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[530]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[534]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 9","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[536]","classification":"future_vision"}],"sourceNotes":["Chapter 9 · 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.","Operational omniscience, autonomous recommendations and high-stakes decisions remain vision claims, not demonstrated or authorized outcomes.","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."],"lessonLocator":"/learn/deep-dive/3012","recordReference":"#/lessons/41","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/41","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p5","title":"Chapter 10 · Participation across institutions","goal":"Map commercial, scientific and accountability questions to distinct evidence records.","why":["One asset may appear in a purchase, a laboratory procedure, a maintenance record and an audit.","An identity can connect those references without making each institution’s authority interchangeable."],"model":["Keep each institution’s asserted record, purpose, audience and governing authority separate.","A shared asset address is a continuity anchor, not a legal, regulatory, security or scientific approval."],"steps":[{"action":"Construct an institutional evidence matrix","control":"Chapter 10 participation matrix","why":"The chapter’s broad analogy should become a set of scoped requirements.","how":"Choose commerce, science and audit as three contexts. List the document, actor, version, time and authority evidence each would require for the same asset.","expected":"Three distinct evidence scopes.","verify":"A record supporting one scope is not promoted to another."},{"action":"Locate the current demonstration boundary","control":"P5 complete graph and exact inspector","why":"The sample can show structure without institutional acceptance.","how":"Inspect one asset and one document relation. Identify what record structure exists and which signed or validated institutional evidence is absent.","expected":"A current-versus-required comparison.","verify":"No standards label is called a certification."}],"machine":{"pointers":["#/P5/nodes","#/P5/edges","#/P1/sourceAssertions"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["scope","authorityEvidence","evidenceState","state"],"explanation":"The demo retains source scope and unknown authority. It has no court determination, regulatory acceptance, commercial execution or issued credential."},"pitfalls":["Treating a document identifier as a valid signature or legal right.","Claiming one registration automatically activates all institutions."],"exercise":{"prompt":"Prepare a three-audience context matrix for an anonymous asset.","deliverables":["Commercial evidence needs","Scientific evidence needs","Audit evidence needs","Disclosure boundaries"],"success":["Every audience has scoped evidence","No acceptance or rights are implied","The original asset reference remains unchanged"]},"question":{"prompt":"Why should institutional scopes remain separate?","correctIndex":0,"choices":[{"text":"Each conclusion depends on different evidence and authority.","explanation":"Continuity does not make commercial, scientific and legal requirements equivalent."},{"text":"One identity grants every institutional right.","explanation":"Identification is not approval or permission."},{"text":"Each institution must rename the physical asset.","explanation":"Distinct scope does not require erasing the original identity."}]},"screens":[{"title":"Connected records with explicit scope","href":"/pillars/p5#pillar-workspace"}],"number":"3013","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 10","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[543]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 10","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[546]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 10","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[548]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 10","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[552]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 10","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[13]","classification":"future_vision"}],"sourceNotes":["Chapter 10 · 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.","Institutional citizenship is a design metaphor; the sample does not establish legal standing, scientific validation, regulatory acceptance or security credentials.","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."],"lessonLocator":"/learn/deep-dive/3013","recordReference":"#/lessons/42","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/42","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"practice","title":"Chapter 11 · Turn the civilization thesis into checkpoints","goal":"Make the book’s synthesis measurable without adopting its universal deployment claims.","why":["A strategy statement is valuable when it guides a build-and-test decision.","Persistent identity, meaningful context, selective disclosure and retained history each require their own acceptance evidence."],"model":["Treat the chapter’s synthesis as a set of architectural goals, not an all-or-nothing activation claim.","Evaluate source retention, exact navigation, evidence distinctions and authority gates separately from hardware, conformance and deployment."],"steps":[{"action":"Write measurable acceptance questions","control":"Chapter 11 synthesis and principles","why":"A powerful statement should not conceal missing implementation.","how":"Choose identity continuity, disclosure and history. Write one testable question for each and define what a passing receipt would contain.","expected":"Three bounded acceptance criteria.","verify":"No criterion passes on a marketing label alone."},{"action":"Run the inspectable checks","control":"Public P3-to-P5 links and complete JSON","why":"The current software can demonstrate only its implemented scope.","how":"Follow a participant link, return to the step and compare focused versus complete graph counts. Record which criteria this inspection supports and which remain untested.","expected":"A measured software inspection report.","verify":"Hardware and formal conformance are not counted as inspected."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:gdti:0614141.00105.1"],"fields":["id","a","b","t","authorityEvidence"],"explanation":"Exact relationship traversal is implemented software behavior. It is distinct from the book’s full civilization architecture and from physical execution."},"pitfalls":["Treating a one-registration statement as proof of every gate.","Combining generated record counts with verified deployment counts."],"exercise":{"prompt":"Create a three-check release rubric for a proposed ThingSite.","deliverables":["Criteria and required receipts","One current software result","Two untested capability boundaries"],"success":["Evidence is appropriate to each claim","Generated and validated states are separate","Unknowns do not silently pass"]},"question":{"prompt":"Which evidence can support a claim of exact context navigation?","correctIndex":1,"choices":[{"text":"The chapter’s universal architecture statement.","explanation":"Authored ambition is not a runtime receipt."},{"text":"A reproducible selected-record and directed-relationship inspection.","explanation":"It tests the claimed software behavior within its exact scope."},{"text":"A count of generated configurations.","explanation":"Generation count does not measure exact navigation or deployment."}]},"screens":[{"title":"Inspect a proposed run step","href":"/pillars/p3?step=urn%3Aepc%3Aid%3Agdti%3A0614141.00105.1#pillar-workspace"},{"title":"Compare focused and complete evidence","href":"/pillars/p5#pillar-workspace"}],"number":"3014","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[556]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[557]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[559]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[565]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[567]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[569]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[571]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 11","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[572]","classification":"design_principle"}],"sourceNotes":["Chapter 11 · 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.","The chapter’s deployment and universal-activation assertions are not treated as proof. The course records only the current anonymous software’s inspectable behavior.","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."],"lessonLocator":"/learn/deep-dive/3014","recordReference":"#/lessons/43","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/43","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p5","title":"Chapter 12 · A corpus about particular things","goal":"Distinguish retrieval, tool use, scenario evaluation and actual model-weight training.","why":["Knowing what a type of instrument is differs from knowing a particular unit’s evidence and history.","The chapter imagines structured physical-world facts as a corpus; corpus growth must preserve provenance and permission."],"model":["A contextual example links exact objects, source assertions and assessment state; it is not automatically a verified fact.","Retrieval reads evidence. A tool performs a scoped operation. Scenario evaluation measures a method. Weight training requires a separate governed training run and evaluation."],"steps":[{"action":"Construct an evidence-bounded example","control":"P5 asset and relationship JSON","why":"A useful corpus example should retain the proposition and how it is known.","how":"Write a short anonymous context statement with exact addresses, source state and unknown authority. Include a missing-field case rather than silently completing it.","expected":"One attributed positive example and one uncertainty example.","verify":"Neither is described as measured hardware truth."},{"action":"Classify the learning activity","control":"Chapter 12 integration-layer table","why":"Different learning activities need different receipts.","how":"Label the example’s use as retrieval, tool input, scenario evaluation or proposed weight-training data. List additional approval and evaluation evidence needed for the latter.","expected":"An activity classification and gate list.","verify":"No weight update is claimed from reading or generating the example."}],"machine":{"pointers":["#/P5/nodes","#/P5/edges","#/P1/sourceAssertions"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["id","state","evidenceState","authorityEvidence","scope"],"explanation":"The course teaches structured, source-bound examples. It does not claim a universal verified corpus, immunity to hallucination or completed model-weight training."},"pitfalls":["Calling all generated sentences verified physical facts.","Equating thousands of simulations with adaptive learning without measured feedback."],"exercise":{"prompt":"Design a two-example corpus entry and its evaluation plan.","deliverables":["Attributed context example","Explicit uncertainty example","Intended use and disclosure scope","Feedback and evaluation requirements"],"success":["Exact assets are not collapsed into model names","Synthetic/source/observed states are labeled","Training claims require separate receipts"]},"question":{"prompt":"An agent retrieves graph context before answering. Has model-weight training occurred?","correctIndex":2,"choices":[{"text":"Yes, because the context contains structured facts.","explanation":"Data format does not establish a training run."},{"text":"Yes, if many configurations were generated.","explanation":"Generation volume is not evidence of evaluated weight updates."},{"text":"No; retrieval and weight updates are different activities.","explanation":"Reading current evidence can ground an answer without changing the model’s weights."}]},"screens":[{"title":"Exact asset rather than model-name knowledge","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Agiai%3A0614141.4&focus=context#pillar-workspace"},{"title":"Complete source-bound graph","href":"/pillars/p5#pillar-workspace"}],"number":"3015","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 12","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[583]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 12","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[584]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 12","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[586]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 12","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[589]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 12","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[591]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 12","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[594]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 12","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[14]","classification":"future_vision"}],"sourceNotes":["Chapter 12 · 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.","Corpus scale, verification universality and hallucination-immunity claims are not adopted. Retrieval and scenario learning remain distinct from model-weight training.","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."],"lessonLocator":"/learn/deep-dive/3015","recordReference":"#/lessons/44","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/44","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"practice","title":"Chapter 13 · From integration heritage to a reusable method","goal":"Apply the historical semantic-translation lesson to an evidence-preserving mapping exercise.","why":["A source transaction and a target system may describe the same proposed activity using different structures.","The heritage chapter emphasizes continuity of meaning and physical reference; preserving the source is essential when a translation cannot be exact."],"model":["Keep source payload, intended target meaning, mapping rationale, transformation receipt and unresolved differences separate.","A shared identifier can anchor references, but it does not make source and target records interchangeable or automatically compatible."],"steps":[{"action":"Map meaning without copying private history","control":"Chapter 13 semantic-translation paragraphs","why":"Anonymity can preserve the lesson without republishing the named historical examples.","how":"Choose an anonymous equipment-request record. Map its participant, requested activity, conditions and response to a second hypothetical vocabulary; retain any mismatch.","expected":"An attributed, anonymous mapping proposal.","verify":"No source value is changed to make the target look complete."},{"action":"Separate mapping from proof","control":"P2 operation evidence and P5 original JSON","why":"A transformation needs its own measured receipt.","how":"Inspect a candidate operation and list what a real conversion receipt would record: source bytes, mapping version, target output and validation result.","expected":"A reproducible transformation checklist.","verify":"A URL, title or mapped field is not called a tested adapter."}],"machine":{"pointers":["#/P2/mhsSilaDriver/operations","#/P5/nodes"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["candidateIdentifier","inputs","outputs","evidence","transportBoundary"],"explanation":"The current capability design is inspectable but non-executable. Transformation receipts and tested target interfaces would be additional evidence."},"pitfalls":["Promoting the historical story’s scale or uniqueness assertions into verified facts.","Calling an approximate semantic map an identity reconciliation or compatibility proof."],"exercise":{"prompt":"Prepare one source-to-target mapping with a deliberate mismatch.","deliverables":["Original source representation","Proposed target representation","Meaning-preservation rationale","Unresolved difference and test plan"],"success":["Original source remains recoverable","The mismatch is explicit","No live integration or historical performance is claimed"]},"question":{"prompt":"A source field has no exact target counterpart. What should the mapping do?","correctIndex":0,"choices":[{"text":"Preserve it and record the unresolved translation.","explanation":"Semantic continuity depends on retaining meaning rather than inventing a target equivalent."},{"text":"Drop it because the target cannot use it.","explanation":"That silently loses source evidence."},{"text":"Choose a similarly named field.","explanation":"Name similarity is not proof of equivalent meaning."}]},"screens":[{"title":"Candidate operations and evidence","href":"/pillars/p2#pillar-workspace"},{"title":"Exact retained representations","href":"/pillars/p5#pillar-workspace"}],"number":"3016","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[605]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[608]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[611]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[613]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[615]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[618]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[621]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[623]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[627]","classification":"author_history"},{"kind":"book","label":"ThingDaddy book · Chapter 13","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[15]","classification":"author_history"}],"sourceNotes":["Chapter 13 · author history. 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 lesson paraphrases the author’s historical account and teaches a mapping proposal. It does not expose internal mapping mechanisms or claim a verified live enterprise integration.","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."],"lessonLocator":"/learn/deep-dive/3016","recordReference":"#/lessons/45","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/45","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"practice","title":"Chapter 14 · Plan customer value in service layers","goal":"Translate the proposed business architecture into a governed customer journey without pricing or market claims.","why":["Identity discovery alone does not deliver a customer’s complete working solution.","The chapter proposes layers around registration: capabilities, workflows, operating context and agent-readable knowledge. Each layer should solve a specific need with a clear evidence gate."],"model":["Separate discovering a source record, proving customer authority, editing a draft, previewing the graph and authorizing publication.","A retained prefix row is not an activated paying customer, a license entitlement or proof of company control. Proposed service layers are not current commercial offers."],"steps":[{"action":"Map a customer need to a layer","control":"Chapter 14 service-layer table","why":"A service should be evaluated by the customer’s job, not by an unverified market projection.","how":"Choose three needs: identify equipment, compare protocol participants and inspect provenance. State the useful output and evidence required for each.","expected":"A need-to-output service map.","verify":"No prices, revenue projections or customer-count claims are copied."},{"action":"Separate onboarding from authority","control":"P1 assignment state and P5 source scope","why":"A source record may exist before a customer has reviewed it.","how":"Inspect the sample’s non-issued state and unknown authority. Draft an onboarding checklist separating discovery, representation, review and permission.","expected":"A governed customer-journey sketch.","verify":"Finding a prefix does not pass identity issuance or publication authorization."}],"machine":{"pointers":["#/P1/prefixEvidence","#/P1/sourceAssertions","#/P5/nodes"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["state","customer_review","allocation_authority_evidence","scope"],"explanation":"The public demo illustrates context discovery and inspection. It does not activate a customer, create a commercial entitlement or set a price."},"pitfalls":["Treating source-record population as customer adoption.","Presenting the book’s proposed commercial tiers as committed offers."],"exercise":{"prompt":"Design a three-stage value proposition for an anonymous customer.","deliverables":["Customer need and useful output at each stage","Evidence/authority gate","A measurable acceptance criterion"],"success":["Every layer solves a defined problem","Publication and physical action are distinct","No pricing, scale or paid entitlement is invented"]},"question":{"prompt":"A company’s prefix appears in a source registry. What may a service planner infer?","correctIndex":1,"choices":[{"text":"The company is already a paying ThingSite customer.","explanation":"Population is not adoption or a commercial relationship."},{"text":"There is a source record to inspect; customer authority and adoption remain separate.","explanation":"Source presence supports discovery, not activation, entitlement or permission."},{"text":"All assets under the prefix are authorized for operation.","explanation":"Namespace context is not action authority."}]},"screens":[{"title":"Discoverable context with review state","href":"/pillars/p1#pillar-workspace"},{"title":"Customer-value evidence inspection","href":"/pillars/p5#pillar-workspace"}],"number":"3017","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 14","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[633]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 14","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[636]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 14","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[638]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 14","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[16]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 14","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[640]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 14","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[641]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 14","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[17]","classification":"future_vision"}],"sourceNotes":["Chapter 14 · 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 strategy planning. Prices, market sizes, customer counts, distribution guarantees and present commercial offers are not established by the book or this course.","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."],"lessonLocator":"/learn/deep-dive/3017","recordReference":"#/lessons/46","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/46","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"practice","title":"Chapter 15 · Methodology and responsible disclosure","goal":"Distinguish public design principles, protected implementation detail, validation evidence and permission to use.","why":["The chapter argues that value lies in a coordinated method, not an identifier alone.","Teaching the purpose of a method does not require exposing internal mechanisms or endorsing legal protection claims."],"model":["Public standards, authored methodology, tested implementation and commercial/legal rights are different records.","An authored protection strategy does not establish a granted patent, a license, novelty, exclusivity or operational permission. Those conclusions need independent authority and scope."],"steps":[{"action":"Write a public principle-level explanation","control":"Chapter 15 heading and methodology discussion","why":"A useful public story can explain why coordination matters without exposing private mechanisms.","how":"Explain how identity, context and provenance support a proposed solution. Keep the account conceptual and omit claim enumerations, internal mappings and confidential implementation details.","expected":"An anonymous public explanation.","verify":"The explanation makes no patent-status or exclusivity claim."},{"action":"Create a disclosure boundary checklist","control":"P5 source and authority inspection","why":"Visibility and permission must be governed independently of a document’s label.","how":"List which evidence may be public, which technical details need approved access, and which rights remain unknown. Use the sample’s null authority as an explicit stop for unsupported permission claims.","expected":"A three-category disclosure plan.","verify":"A visible record is not treated as a license to implement or execute."}],"machine":{"pointers":["#/P1/sourceAssertions","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["scope","authorityEvidence","evidenceState"],"explanation":"The sample exposes educational context only. Patent, license and confidential-methodology evidence is not part of this public fixture; no such rights are inferred."},"pitfalls":["Claiming a patent grant, novelty or legal coverage from an authored chapter.","Republishing confidential engineering mechanisms merely because the book discusses their purpose."],"exercise":{"prompt":"Prepare a public/private/unknown disclosure decision for a proposed solution.","deliverables":["Public principle paragraph","Restricted-detail categories","Rights and authority evidence still required"],"success":["No internal implementation mechanism is exposed","Legal status is not asserted","Public teaching and execution permission stay separate"]},"question":{"prompt":"What does an authored methodology-protection chapter establish by itself?","correctIndex":2,"choices":[{"text":"A granted patent covering every implementation.","explanation":"Patent status and scope need authoritative evidence."},{"text":"Permission for agents to implement or operate it.","explanation":"A public narrative does not grant use or execution authority."},{"text":"The author’s stated strategy, not a verified legal right or license.","explanation":"The source can be attributed without turning its claims into independently verified legal conclusions."}]},"screens":[{"title":"Inspect scope rather than assume permission","href":"/pillars/p5#pillar-workspace"}],"number":"3018","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 15","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[646]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 15","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[647]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 15","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[649]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 15","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[653]","classification":"future_vision"}],"sourceNotes":["Chapter 15 · 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.","No legal advice, patent-status verification, claim detail, protected mechanism or license grant is supplied. This lesson teaches responsible public disclosure only.","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."],"lessonLocator":"/learn/deep-dive/3018","recordReference":"#/lessons/47","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/47","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p5","title":"Chapter 16 · Relationships turn transactions into ecosystems","goal":"Plan a multi-party graph that preserves sources, roles, assessments and history.","why":["A participant can be a supplier, customer, reviewer and service recipient in different relationships.","The ecosystem chapter emphasizes the continuing value of an asset’s evidence trail beyond one transaction."],"model":["Typed relationships reference original participants; they do not merge identities or infer ownership.","A historical assertion, current assessment and later authorized decision are separate records. Unknown intervals, actors and authority remain explicit."],"steps":[{"action":"Sketch multiple roles for one asset","control":"Chapter 16 ecosystem and provenance passages","why":"Roles change while exact participants and source history must remain.","how":"Draft anonymous manufacturer, laboratory and service-provider roles around one asset. Give each proposed relationship its own type, scope and missing-evidence state.","expected":"A role-specific ecosystem diagram.","verify":"No relationship is derived from a shared name or prefix containment."},{"action":"Inspect a first-class relationship","control":"P5 relationship selection and original JSON","why":"Agents need the assertion itself, not just a human-readable line.","how":"Select a directed edge and record its address, endpoints, actor, source, time and authority. Identify fields that remain unknown.","expected":"A relationship evidence envelope.","verify":"No unknown provenance is silently normalized into current verified state."}],"machine":{"pointers":["#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["id","a","b","t","provenance","authorityEvidence","assertionTime"],"explanation":"The current sample has separately inspectable directed assertions. It does not contain a complete operational, legal, calibration or commercial history."},"pitfalls":["Calling a connected graph a complete verified lifecycle.","Deleting older assertions when a later assessment differs."],"exercise":{"prompt":"Draft a supersession scenario for one proposed relationship.","deliverables":["Original assertion","New assessment","Required authorized decision","History-preserving links and unknowns"],"success":["Original endpoints and assertions remain addressable","Authority is scoped","No customer discrepancy is resolved on the customer’s behalf"]},"question":{"prompt":"A new assessment disagrees with an older source assertion. What should happen?","correctIndex":0,"choices":[{"text":"Preserve both and link the assessment with its evidence and scope.","explanation":"Agents need the original assertion and the later interpretation; disagreement is not identity replacement."},{"text":"Overwrite the source so the graph has one answer.","explanation":"That erases provenance and uncertainty."},{"text":"Merge all similarly named participants.","explanation":"Name similarity does not establish equivalence."}]},"screens":[{"title":"First-class relationship evidence","href":"/pillars/p5#pillar-workspace"}],"number":"3019","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[663]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[668]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[672]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[673]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[675]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[677]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[678]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 16","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[680]","classification":"future_vision"}],"sourceNotes":["Chapter 16 · 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.","Complete lifecycle and institutional-value outcomes are a future direction. The supplied book body proceeds from Chapter 16 to Chapter 20; Chapters 17–19 are not present and are not invented.","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."],"lessonLocator":"/learn/deep-dive/3019","recordReference":"#/lessons/48","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/48","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p3","title":"Chapter 20 · A protocol is a concert of exact participants","goal":"Model a workflow’s participants, stages, contributions and evidence recipients without flattening them.","why":["A result may depend on several machines, components, materials, people and documents contributing at different times.","The concert metaphor emphasizes coordination: a reading becomes useful in the context of its role, method and audience."],"model":["Define ordered stages and required roles before choosing exact participants.","Retain each selected participant, directed role assertion, governing method version and output reference. A coherent design is not automatically compatible, validated or executed."],"steps":[{"action":"Identify contributions to a proposed stage","control":"P3 proposed run step and participant assertions","why":"A stage’s outcome must be traceable to the records it references.","how":"List the component, material, human/service and document roles used by the step. Separate required roles from the exact retained participant references.","expected":"A role-versus-binding matrix.","verify":"A label alone never fills an exact participant requirement."},{"action":"Trace one contribution into evidence","control":"Open exact participant in P5","why":"The concert remains inspectable only if every contribution keeps its source.","how":"Follow a participant link and inspect the directed assertion, original endpoints and unknown authority. Return to the same stage.","expected":"A stage-to-contribution evidence path.","verify":"No graph edge is upgraded to permission or a measured performance."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps","#/P5/edges"],"identifiers":["urn:epc:id:gdti:0614141.00105.1"],"fields":["ordinal","requiredInputRoles","expectedOutputs","stepDefinitionGdti","a","b","t"],"explanation":"The public sample demonstrates retained step-participant references. Timing of real contributions and execution results are not supplied."},"pitfalls":["Treating one instrument model as the entire workflow.","Describing the book’s end-to-end outcomes as implemented vertical solutions."],"exercise":{"prompt":"Prepare a concert map for one proposed stage.","deliverables":["Stage definition","Required roles","Exact supplied references","Outputs and evidence recipients","Missing bindings"],"success":["Every participant remains separate","Roles and bindings are distinct","The map is explicitly proposed and non-executable"]},"question":{"prompt":"What makes the concert metaphor technically useful?","correctIndex":1,"choices":[{"text":"A conductor label automatically authorizes every participant.","explanation":"Coordination labels do not grant authority."},{"text":"Separate contributions with exact identities, roles and evidence.","explanation":"It turns a narrative into traceable composition rather than a single anonymous process box."},{"text":"All similar instruments can share one unit record.","explanation":"That loses exact assets and their histories."}]},"screens":[{"title":"A proposed stage and its exact participants","href":"/pillars/p3?step=urn%3Aepc%3Aid%3Agdti%3A0614141.00105.1#pillar-workspace"},{"title":"Contribution provenance","href":"/pillars/p5#pillar-workspace"}],"number":"3020","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 20","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[690]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[693]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[695]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[697]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[699]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[701]","classification":"future_vision"}],"sourceNotes":["Chapter 20 · 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 a design exercise, not a coordinated physical execution. The preceding missing-body Chapters 17–19 are not reconstructed.","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."],"lessonLocator":"/learn/deep-dive/3020","recordReference":"#/lessons/49","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/49","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p3","title":"Chapter 20.1 · Medicine-making as evidence-linked stages","goal":"Learn how a high-stakes process requires distinct stage, participant, result and review evidence.","why":["Manufacturing, measurement, review and distribution have different responsibilities and evidence needs.","The chapter’s pharmaceutical example shows why an aggregate result should not obscure its contributing instruments, materials and methods."],"model":["Use a proposed stage graph: preparation, process, measurement, review and hand-off. Do not prescribe real process settings.","Method definition, exact configuration, service relationship, run binding, observation and reviewer decision must remain separate; current governance clarifies these distinctions beyond the book’s older examples."],"steps":[{"action":"Map stages without claiming an assay","control":"Chapter 20.1 contribution table; P3 procedure view","why":"A training composition can describe evidence needs without being an approved manufacturing instruction.","how":"Outline five anonymous stages and list each stage’s inputs, exact participant requirements, outputs and review gate.","expected":"A stage/evidence responsibility matrix.","verify":"No process recipe, approval or batch release is inferred."},{"action":"Inspect the sample’s validation gaps","control":"P3 rules and checks; P5 exact relationship","why":"Scientific and regulatory conclusions need evidence beyond structural connectivity.","how":"Record the sample’s unresolved model applicability, role mapping and formal validation states. Identify where a qualified reviewer would need real observations.","expected":"A separate structural/scientific/authority gap list.","verify":"A demo structural check is not labeled assay or regulatory conformance."}],"machine":{"pointers":["#/P3/typedGaps","#/P3/governedModel","#/P3/publishedAllotropeShapeValidation","#/P5/edges"],"identifiers":["urn:epc:id:gdti:0614141.00105.1"],"fields":["applicabilityState","method_AFO_term_status","state","authorityEvidence"],"explanation":"The available screens are anonymous PCR education, not a deployed medicine-making solution. Protocol/configuration GDTIs and GSRN/SRIN purposes remain separate current rules."},"pitfalls":["Treating an illustrative result as a clinical or manufacturing release decision.","Claiming regulatory filing or legal co-signature from graph structure."],"exercise":{"prompt":"Prepare a non-executable medicine-process evidence plan.","deliverables":["Five proposed stages","Exact-participant requirements","Observation/review requirements","Formal validation and authority gaps"],"success":["No clinical or process advice is given","Each result has a required method and source trail","Release remains an authorized, validated decision outside the demo"]},"question":{"prompt":"A proposed stage graph is structurally complete. Can it release a real batch?","correctIndex":2,"choices":[{"text":"Yes, if all participant nodes resolve.","explanation":"Resolvable addresses cannot prove a measured outcome."},{"text":"Yes, if an agent is named in the graph.","explanation":"A named service role does not grant release authority."},{"text":"No; scientific validation, real evidence and authorized review remain separate.","explanation":"Structural coherence does not establish assay validity or release authority."}]},"screens":[{"title":"Educational procedure and validation gaps","href":"/pillars/p3#pillar-workspace"},{"title":"Retained contribution evidence","href":"/pillars/p5#pillar-workspace"}],"number":"3021","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 20.1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[703]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[704]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[20]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.1","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[707]","classification":"future_vision"}],"sourceNotes":["Chapter 20.1 · 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.","The medicine story is a high-level design example, not medical advice, a process instruction, assay validation, regulatory compliance or an authorized release workflow.","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."],"lessonLocator":"/learn/deep-dive/3021","recordReference":"#/lessons/50","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/50","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p3","title":"Chapter 20.2 · Food provenance across transformation and hand-off","goal":"Keep input material, output lot, packing unit and location relationships distinct in an anonymous food scenario.","why":["A transformation creates a new output context; it does not make input and output identities equivalent.","Packing and movement evidence must preserve the product/lot trail without assuming what each later recipient knows or may disclose."],"model":["Sketch input-lot to process to output-lot references, then separate packing and hand-off relationships.","A potential concern can prompt an evidence request. It is not a verified contamination, recall decision or guaranteed trace-time outcome."],"steps":[{"action":"Draft a transformation trail","control":"Chapter 20.2 field, packing and transit table","why":"Input, output and packaging answer different provenance questions.","how":"Use an anonymous produce scenario. List input material, output lot, packing unit, processing location and observer; mark missing identifiers and dates unknown.","expected":"A proposed transformation/packing graph.","verify":"No input identity is overwritten by the output identity."},{"action":"Transfer the method, not the vertical claim","control":"P3 material-role and step views","why":"The PCR sample illustrates composition mechanics but is not a live food platform.","how":"Compare required input roles and output descriptions in one demo step. State what food-specific vocabulary, observations and validation would need to be added.","expected":"A domain-transfer requirements list.","verify":"The laboratory fixture is not described as a food safety or recall system."}],"machine":{"pointers":["#/P2/bom","#/P3/protocolTemplates/0/ordered_steps","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["requiredInputRoles","expectedOutputs","lot","quantity","scope"],"explanation":"Current material and workflow fields are illustrative. Real food lots, transformations, custody evidence and authorized notifications are not implemented by these screens."},"pitfalls":["Inferring an output lot from a product catalogue identifier alone.","Repeating the book’s recall timings or safety outcomes as verified performance."],"exercise":{"prompt":"Build a hypothetical food provenance envelope with one missing hand-off.","deliverables":["Distinct input/output roles","Packing relationship","Missing hand-off evidence","Affected-scope investigation questions"],"success":["No contamination or recall is asserted","Missing custody remains explicit","Domain-specific requirements are not borrowed from PCR"]},"question":{"prompt":"A process transforms one material lot into an output lot. What should the graph preserve?","correctIndex":0,"choices":[{"text":"Separate input and output references plus the transformation evidence.","explanation":"Their relationship matters; they are not the same physical or product context."},{"text":"Replace the input record with the output.","explanation":"That erases origin and process history."},{"text":"Use the packing-unit key for all products.","explanation":"Packaging is a separate object role."}]},"screens":[{"title":"Transferable input/output composition mechanics","href":"/pillars/p3#pillar-workspace"},{"title":"Illustrative material records","href":"/pillars/p2#pillar-workspace"}],"number":"3022","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 20.2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[709]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[710]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[21]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.2","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[713]","classification":"future_vision"}],"sourceNotes":["Chapter 20.2 · 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 an anonymous design exercise, not food-safety guidance, a legal recall instruction or proof of food-system deployment or traceability speed.","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."],"lessonLocator":"/learn/deep-dive/3022","recordReference":"#/lessons/51","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/51","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p5","title":"Chapter 20.3 · Evidence questions without legal conclusions","goal":"Construct a reproducible evidence trail for a past asset action while preserving missing time and authority.","why":["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."],"model":["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."],"steps":[{"action":"Turn a dispute into evidence questions","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.","expected":"A question-to-evidence map.","verify":"No court outcome, compliance verdict or legal advice is supplied."},{"action":"Inspect unknowns honestly","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.","expected":"A source-preserving audit sketch.","verify":"No ordering is invented from array position or display order."}],"machine":{"pointers":["#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["source","assertingActorId","authorityEvidence","assertionTime","scope"],"explanation":"The sample supplies inspectable context and unknowns. It does not contain signed court evidence, a complete past-state timeline or a legal admissibility determination."},"pitfalls":["Calling a SHA-256 hash proof that an assertion is true.","Claiming immutable records alone guarantee legal acceptance or regulatory compliance."],"exercise":{"prompt":"Prepare an evidence index for an anonymous past-action question.","deliverables":["Four review questions","Exact source references","Unknown chronology and authority","Required provenance/verification receipts"],"success":["Source assertions are not rewritten","Unknown chronology is explicit","No legal or compliance determination is claimed"]},"question":{"prompt":"What does a matching document hash prove?","correctIndex":1,"choices":[{"text":"Every statement in the document is true.","explanation":"Truth requires proposition-specific evidence."},{"text":"That the compared bytes match the pinned bytes.","explanation":"A byte-integrity check does not independently establish truth, authority or legal acceptance."},{"text":"The document is automatically admissible.","explanation":"Legal acceptance depends on governing requirements and authoritative decisions."}]},"screens":[{"title":"Exact assertion and unknown provenance fields","href":"/pillars/p5#pillar-workspace"}],"number":"3023","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 20.3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[715]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[716]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[718]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[720]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[22]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.3","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[723]","classification":"future_vision"}],"sourceNotes":["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."],"lessonLocator":"/learn/deep-dive/3023","recordReference":"#/lessons/52","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/52","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p1","title":"Chapter 20.4 · Assembly keeps component origins","goal":"Preserve an incoming component’s durable identity across installed context, removal and replacement.","why":["A parent assembly’s history depends on its individually identified components and their changing roles.","The aerospace story motivates long-lived traceability, but a current list of parts is not a complete installation history."],"model":["Current governance preserves supplier GIAI → installed CPI → parent GIAI as distinct records with a first-class bond.","Installation, removal and replacement need separate events, actors, evidence and validity intervals. Old identities and bonds remain addressable after a change."],"steps":[{"action":"Inspect an origin/context bond","control":"P1 GIAI/CPI roles and P5 sensor context","why":"Installed role must not erase the incoming physical asset.","how":"Locate the supplied sensor context and its source-asset relationship. Record both addresses and the missing real installation evidence.","expected":"A two-identity-plus-bond explanation.","verify":"The supplier identity is not renamed into the installed CPI."},{"action":"Draft a replacement history","control":"Chapter 20.4 assembly and service table","why":"A replacement changes the active role, not the existence of the former component.","how":"Sketch old-component removal and new-component installation as appended proposed transitions. Include actor, time, work-order, source and validity fields as requirements.","expected":"A history-preserving change plan.","verify":"Old records remain retrievable and no dates are invented."}],"machine":{"pointers":["#/P1/demo_cpi","#/P2/modules","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:cpi:0614141.414141.41"],"fields":["id","a","b","t","authorityEvidence","assertionTime"],"explanation":"The sample illustrates the identity bond but has no verified installed aircraft part, removal event or temporal service history. Current rules add explicit transition requirements."},"pitfalls":["Flattening all components under the parent’s model name.","Replacing an original physical identity when a component is removed or reused."],"exercise":{"prompt":"Design a two-component replacement timeline with preserved origins.","deliverables":["Old/new physical identities","Installed contexts","Proposed transition events and intervals","Missing verification/authority evidence"],"success":["The original source identities survive","Removal is not deletion","No aircraft safety or service qualification is claimed"]},"question":{"prompt":"A component leaves its installed role. What happens to its source identity?","correctIndex":2,"choices":[{"text":"It is deleted with the old installation.","explanation":"That destroys provenance needed for later inspection."},{"text":"It becomes the parent’s identity.","explanation":"Parent and component remain different physical participants."},{"text":"It remains; the role’s active interval changes through recorded transitions.","explanation":"Changing context must not erase the component’s origin or prior history."}]},"screens":[{"title":"Educational source/installed-context bond","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context#pillar-workspace"},{"title":"Durable asset and context roles","href":"/pillars/p1#pillar-workspace"}],"number":"3024","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 20.4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[725]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[726]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[23]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.4","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[729]","classification":"future_vision"}],"sourceNotes":["Chapter 20.4 · 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.","The assembly story is a conceptual exercise, not aerospace engineering guidance, airworthiness proof, certified parts data or an implemented aircraft system.","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."],"lessonLocator":"/learn/deep-dive/3024","recordReference":"#/lessons/53","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/53","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p3","title":"Chapter 20.5 · Healthcare context and selective disclosure","goal":"Separate a hypothetical diagnostic contribution from clinical interpretation and permission to disclose.","why":["A healthcare result may refer to an instrument, reagent, method and patient-related service context.","Sensitive relationships require a purpose and audience; linking records must not become unrestricted sharing or a treatment decision."],"model":["Keep measured observation, method, interpretation, reviewer decision and disclosure authorization separate.","Use anonymous design roles only. A service identifier does not supply consent, qualification, clinical efficacy or the right to expose personal data."],"steps":[{"action":"Map a diagnostic contribution at principle level","control":"Chapter 20.5 diagnosis and monitoring table","why":"A training example should describe evidence needs without prescribing care.","how":"List anonymous instrument, material, method and reviewer roles for a hypothetical result. Specify missing validation and provenance, not a diagnosis or dose.","expected":"A non-clinical evidence map.","verify":"No patient record, personal information or medical recommendation is created."},{"action":"Define the disclosure envelope","control":"P3 role assertions and P5 scope/authority fields","why":"A graph can be connected while access remains narrow.","how":"Identify which roles might need instrument-health context and which might need a reviewed result. For each, list purpose, required authorization and excluded data.","expected":"A purpose-limited sharing matrix.","verify":"Co-occurrence or a service-role key is not treated as consent."}],"machine":{"pointers":["#/P3/protocolTemplates/0/ordered_steps","#/P5/edges"],"identifiers":["urn:epc:id:gdti:0614141.00105.1"],"fields":["actorRole","requiredInputRoles","authorityEvidence","scope"],"explanation":"The linked screens are an anonymous laboratory composition, not a patient-care workflow. Clinical validation and personal-data permissions are outside the demo."},"pitfalls":["Turning an illustrative laboratory output into a diagnosis or treatment.","Assuming an identifier or relationship grants consent to share sensitive data."],"exercise":{"prompt":"Write a non-clinical context/disclosure plan for a hypothetical diagnostic contribution.","deliverables":["Separate observation and interpretation roles","Evidence requirements","Audience/purpose matrix","Missing authorization"],"success":["No medical advice or personal data is produced","Consent/authority is not inferred","Clinical conclusions remain outside the training fixture"]},"question":{"prompt":"A service relationship links a person to a device. Does that grant data-sharing consent?","correctIndex":0,"choices":[{"text":"No; consent and disclosure authority require separate scoped evidence.","explanation":"A contextual relationship identifies a role, not every permission associated with sensitive data."},{"text":"Yes, because the relationship is visible.","explanation":"Visibility is not consent."},{"text":"Yes, if the device has a valid identifier.","explanation":"Device identity does not authorize disclosure of personal information."}]},"screens":[{"title":"Anonymous role-based composition","href":"/pillars/p3#pillar-workspace"},{"title":"Relationship scope and unknown authority","href":"/pillars/p5#pillar-workspace"}],"number":"3025","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 20.5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[731]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[732]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 20.5","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[24]","classification":"future_vision"}],"sourceNotes":["Chapter 20.5 · 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 lesson is not medical advice, a care instruction, patient-data processing, clinical validation or evidence of a live healthcare integration.","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."],"lessonLocator":"/learn/deep-dive/3025","recordReference":"#/lessons/54","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/54","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p2","title":"Chapter 20.6–20.7 · One reading, several contextual meanings","goal":"Explain why a value needs units, source, method stage, time and role before interpretation.","why":["The same temperature can be expected in one stage and concerning in another.","The book’s music analogy distinguishes the note itself from its placement in a method and a stakeholder’s responsibility."],"model":["Observation value/unit, exact observer, measured participant, stage, governing version and interpretation are separate.","A method-specific acceptance limit cannot be invented from a generic setting, a model name or a temperature value. The repeated cross-industry pattern still needs domain evidence."],"steps":[{"action":"Separate a value from its interpretation","control":"Chapter 20.6 context-layer table","why":"A number without its context cannot establish pass/fail.","how":"Use the book’s temperature example only as an illustrative value. Write two hypothetical stages with different expected conditions; keep the actual governing limits unknown.","expected":"One value and two contextual interpretations.","verify":"No illustrative temperature becomes an approved process setpoint."},{"action":"Inspect the sample’s rule and sensor requirements","control":"P2 settings, P3 rules and P5 sensor record","why":"The current sample can show required context without real observations.","how":"Compare setting constraints with required sensor evidence and method gaps. Identify what must be known before assessing a real reading.","expected":"A reading-context requirements list.","verify":"Settings and proposed rules are not called measured sensor results."}],"machine":{"pointers":["#/P2/configurationSettings","#/P2/modules","#/P3/typedGaps","#/P5/nodes"],"identifiers":["urn:epc:id:cpi:0614141.414141.41"],"fields":["value","unit","protocolScope","approvedForUse","physicalUnitVerification"],"explanation":"Sample settings and component roles are educational designs. Real observations, their timestamps and a pinned approved method are not supplied."},"pitfalls":["Declaring pass/fail from a temperature without the governing method stage.","Assuming a reusable context pattern makes every industry’s thresholds interchangeable."],"exercise":{"prompt":"Draft a contextual observation envelope and two non-operational interpretations.","deliverables":["Value/unit and source requirements","Stage and method-version requirements","Unknown limit/time fields","Audience-specific questions"],"success":["No safe limit or clinical verdict is invented","Observation and interpretation remain separate","The cross-industry pattern is a method, not a performance guarantee"]},"question":{"prompt":"Is a temperature within specification if the method stage and limit are unknown?","correctIndex":1,"choices":[{"text":"Yes, if it resembles the book’s example.","explanation":"An illustration is not the actual governing specification."},{"text":"It cannot be assessed from that value alone.","explanation":"Conformance needs the governing version, stage, limit and measured context."},{"text":"Yes, if the sensor has an EPC identity.","explanation":"Identity does not establish measurement validity or acceptance criteria."}]},"screens":[{"title":"Settings versus sensing requirements","href":"/pillars/p2#pillar-workspace"},{"title":"Stage-specific rules and gaps","href":"/pillars/p3#pillar-workspace"},{"title":"Exact proposed sensor context","href":"/pillars/p5?node=urn%3Aepc%3Aid%3Acpi%3A0614141.414141.41&focus=context#pillar-workspace"}],"number":"3026","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[735]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[736]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[738]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[25]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[741]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[743]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[745]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[746]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[751]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[753]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[26]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 20.6 and 20.7","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[756]","classification":"design_principle"}],"sourceNotes":["Chapter 20.6 and 20.7 · 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.","This stop also covers the source’s 20.7 reuse discussion beneath the 20.6 heading. It teaches contextual interpretation, not a measured result, approved threshold or live multi-industry implementation.","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."],"lessonLocator":"/learn/deep-dive/3026","recordReference":"#/lessons/55","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/55","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p3","title":"Chapter 21 · Reuse the method, not an untested promise","goal":"Define reusable context invariants while identifying what must change and be revalidated in a new domain.","why":["A consistent way to record identity, observations, rules and evidence makes comparisons easier.","Different instruments and industries still have different semantics, interfaces, safety constraints and authority."],"model":["Reuse the requirement to preserve exact participants, sources, versioned methods and scoped decisions.","Do not assume unchanged transport, event semantics, ontology terms or acceptance criteria. Reuse is a testable proposal, not automatic compatibility."],"steps":[{"action":"Identify structural invariants","control":"Chapter 21 invariant table","why":"Common structure should not flatten domain facts.","how":"List what an anonymous PCR composition and a hypothetical monitoring composition both need: exact identities, attributed inputs, method/rule scope and output provenance.","expected":"A shared context checklist.","verify":"The checklist describes requirements, not a functioning second vertical."},{"action":"Specify the domain-specific changes","control":"P3 governed model and formal validation states","why":"The sample’s explicit gaps show where reuse requires new evidence.","how":"List new vocabulary, units, interface support, constraints and formal validation inputs for the hypothetical domain. Keep all unknowns explicit.","expected":"A domain-adaptation test plan.","verify":"No copied role term or structural test is claimed as published-model conformance."}],"machine":{"pointers":["#/P3/governedModel","#/P3/typedGaps","#/P3/publishedAllotropeSchemaValidation","#/P3/thingDaddyCustomShaclValidation"],"identifiers":["urn:epc:id:gdti:0614141.00105.1"],"fields":["applicabilityState","state","conformanceClaim","checks"],"explanation":"The current sample has structural demo checks and unresolved formal model work. A reusable contract does not imply Allotrope, AFO, SHACL or hardware validation."},"pitfalls":["Saying a driver works in every industry after changing a few values.","Treating domain ontology labels as proven mappings."],"exercise":{"prompt":"Prepare a reuse assessment for a hypothetical second domain.","deliverables":["Reusable evidence invariants","Changed domain facts","Missing interface/model evidence","Retest criteria"],"success":["Exact domain participants remain distinct","No compatibility is assumed","Formal and structural validation states are separate"]},"question":{"prompt":"What can a reused context contract guarantee by itself?","correctIndex":2,"choices":[{"text":"The new instrument is executable immediately.","explanation":"Transport and authorization must be established separately."},{"text":"The old domain’s thresholds remain valid.","explanation":"Acceptance criteria are context- and method-specific."},{"text":"A consistent representation requirement, not domain compatibility.","explanation":"The structure can be reused while semantics, transport and safety remain subject to evidence and testing."}]},"screens":[{"title":"Governed model and separate validation states","href":"/pillars/p3#pillar-workspace"}],"number":"3027","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 21","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[768]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 21","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[769]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 21","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[771]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 21","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[775]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 21","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[27]","classification":"future_vision"}],"sourceNotes":["Chapter 21 · 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.","Universal reuse is the proposed direction. No unchanged-code, universal compatibility or cross-industry execution guarantee is made.","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."],"lessonLocator":"/learn/deep-dive/3027","recordReference":"#/lessons/56","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/56","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p2","title":"Chapter 22 · Read the manual before proposing the driver","goal":"Extract candidate behavior with exact source scope and record what is required for a tested interface.","why":["A manual may describe user actions, states, sensors, limits and exceptions without supplying an executable API.","The chapter’s construction method is useful when every proposed behavior remains traceable to the correct revision and scope."],"model":["Read five dimensions: requested actions, state transitions, sensor outputs, conditional rules and participant context.","Separate manual-supported behavior, candidate machine representation, real transport implementation, conformance and hardware validation. A candidate driver does not pass all five."],"steps":[{"action":"Make a source-scoped behavior inventory","control":"Chapter 22 construction table and P2 operations","why":"The original source is the evidence for a proposal, not for native interface support.","how":"Choose one candidate demo operation. Write the command intent, inputs, outputs, relevant states and exception evidence a real manual would need to provide.","expected":"A source-requirement inventory.","verify":"Missing manual pages and responses remain explicit rather than fabricated."},{"action":"Define the adapter test boundary","control":"P2 operation transport boundary","why":"A representation cannot dispatch a command until a real interface is tested and authorized.","how":"Record native-interface evidence, endpoint, adapter version, credentials scope, safe test environment and expected response needed for implementation.","expected":"A non-executable driver test plan.","verify":"No hardware endpoint or execution permission is inferred from operation names."}],"machine":{"pointers":["#/P2/mhsSilaDriver","#/P2/mhsSilaDriver/operations"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["nativeSilaSupport","transportBoundary","executable","inputs","outputs","executionAuthorized"],"explanation":"The demo’s MHS/SiLA operations are candidate descriptions. Transport, native support, hardware behavior and formal conformance are not supplied."},"pitfalls":["Turning a UI action in a manual into a claimed native API.","Repeating the book’s one-day driver or universal-interface claims as measured performance."],"exercise":{"prompt":"Draft one candidate operation with a five-dimension evidence plan.","deliverables":["Intent and input/output requirements","State/sensor/rule evidence","Exact source revision and locator requirements","Transport and safety test gates"],"success":["Manual evidence and candidate representation are separate","No executable support is asserted","The proposed behavior can be traced and independently tested"]},"question":{"prompt":"A user guide describes a thermal cycle. Does that prove a native SiLA endpoint exists?","correctIndex":0,"choices":[{"text":"No; behavior evidence and transport implementation are distinct.","explanation":"A manual can inform a candidate model without proving its machine interface."},{"text":"Yes, because the action can be named as a command.","explanation":"Naming a command does not create an endpoint."},{"text":"Yes, after attaching an asset identifier.","explanation":"Context identity does not implement transport or grant authority."}]},"screens":[{"title":"Candidate operations and explicit transport boundary","href":"/pillars/p2#pillar-workspace"}],"number":"3028","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 22","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[779]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 22","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[780]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 22","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[782]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 22","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[28]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 22","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[785]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 22","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[29]","classification":"design_principle"},{"kind":"book","label":"ThingDaddy book · Chapter 22","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[787]","classification":"design_principle"}],"sourceNotes":["Chapter 22 · 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.","This is a public source-reading method, not disclosure of protected implementation machinery or proof of a tested driver, native support, conformance or construction time.","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."],"lessonLocator":"/learn/deep-dive/3028","recordReference":"#/lessons/57","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/57","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"practice","title":"Chapter 23 · Change one dimension and preserve the evidence","goal":"Plan a versioned change to participants, sensing, rules or environment with a scoped retest.","why":["Changing a sensor or rule can alter what an observation means or which response is permitted.","The chapter’s modularity ambition is strongest when changes are recorded and compared rather than silently declared equivalent."],"model":["Separate four change classes: exact participant, sensing context, governing rule and operating environment.","A new proposal preserves parent version, original participant references, change reason, evidence, unknowns and replay results. Changing a platform handle never replaces the asset identity."],"steps":[{"action":"Choose one bounded change","control":"Chapter 23 four change discussions","why":"A narrow change makes cause and effect inspectable.","how":"Choose a proposed sensor substitution, rule revision or cloud-pattern change. State which records change and which original references must remain unchanged.","expected":"A scoped version-difference plan.","verify":"No source record is overwritten and no identity equivalence is inferred."},{"action":"Define a before-and-after evaluation","control":"P3 rules and P4 unbound design","why":"Counting generated configurations is not measured improvement.","how":"Specify pinned inputs, expected behavior, missing evidence, a failure case and a comparison metric. Preserve both hypothetical outcomes until an actual evaluation is run.","expected":"A reproducible retest specification.","verify":"Improvement is not claimed without a measured receipt."}],"machine":{"pointers":["#/P3/protocolTemplates/0","#/P3/typedGaps","#/P4","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4","urn:epc:id:gdti:0614141.00105.1"],"fields":["protocolFamilyGdti","configurationGdti","state","authorityEvidence"],"explanation":"Protocol family/version and configuration remain distinct. The demo supports inspection; proposed versioning and retest plans do not imply saved run history or adaptive training."},"pitfalls":["Assuming a changed setting is safe because the architecture is reusable.","Counting many generated alternatives as learning without feedback and measured adjustment."],"exercise":{"prompt":"Prepare a controlled change-and-retest plan.","deliverables":["Parent/child proposal distinction","One changed dimension","Preserved exact references","Pinned inputs and before/after metric","Failure and authority gates"],"success":["Old evidence is retained","Changed semantics are reviewed","Compatibility and learning are not claimed from generation alone"]},"question":{"prompt":"A rule was changed and many configurations generated. What proves improvement?","correctIndex":1,"choices":[{"text":"The number of generated alternatives.","explanation":"Volume is not an outcome measure."},{"text":"A measured comparison on pinned inputs with retained failures and feedback.","explanation":"Generation supplies proposals; improvement requires evaluated outcomes and a recorded adjustment."},{"text":"The architecture remaining structurally unchanged.","explanation":"Stable structure cannot prove safer or more effective behavior."}]},"screens":[{"title":"Method and rule context","href":"/pillars/p3#pillar-workspace"},{"title":"Environment is a separate proposal","href":"/pillars/p4#pillar-workspace"},{"title":"Preserved participants and relationships","href":"/pillars/p5#pillar-workspace"}],"number":"3029","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[791]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[792]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[794]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[30]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[796]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[31]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[798]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[799]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[32]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[802]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 23","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[33]","classification":"future_vision"}],"sourceNotes":["Chapter 23 · 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.","Modularity is a design goal, not a guarantee that any replacement works or any platform is supported without implementation and retesting.","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."],"lessonLocator":"/learn/deep-dive/3029","recordReference":"#/lessons/58","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/58","referenceKind":"educational-content-locator-not-gs1-identity"},{"module":"p4","title":"Chapter 24 · The edge village needs local evidence and authority","goal":"Design a proposed local operating context with explicit delegation, failure handling and shared-history requirements.","why":["Local processes may need bounded responses when shared services are unavailable.","The final chapter brings identity, sensing, rules and orchestration into one local context while preserving a shared record of what occurred."],"model":["A proposed edge context needs exact participants, trusted observations, approved rules, tested interfaces and scoped local authority.","Local operation is not permission-free operation. Shared storage receives evidence only within authorized disclosure; it cannot retroactively supply missing local authority."],"steps":[{"action":"Specify local prerequisites","control":"Chapter 24 local-identity, sensing, rules and orchestration discussion","why":"A village metaphor must become operational requirements before it can describe a working site.","how":"List identities, sensor evidence, governing versions, delegation, transport tests and safe stop conditions for a hypothetical anonymous lab context.","expected":"A local-readiness checklist.","verify":"Missing prerequisites remain blocking only for the dependent action."},{"action":"Plan failure and history handling","control":"P4 unbound requirements and P5 provenance fields","why":"Disconnection or unknown authority must not trigger unapproved improvisation.","how":"Draft a scenario with unavailable shared storage and expired local authority. Specify what may be inspected, what must stop, what evidence is retained and when it may be shared.","expected":"A scoped offline/failure plan.","verify":"No live runtime, automatic safety response or cloud commissioning is claimed."}],"machine":{"pointers":["#/P4","#/P5/nodes","#/P5/edges"],"identifiers":["urn:epc:id:giai:0614141.4"],"fields":["state","executionAuthorized","authorityEvidence","scope","assertionTime"],"explanation":"Current screens are proposed environment context and educational provenance. Local resolvers, execution runtimes, measured latency, offline orchestration and shared event delivery are not demonstrated."},"pitfalls":["Reading “local knowledge” as a bypass around authorization.","Claiming latency, autonomy or cloud sharing from a static environment choice."],"exercise":{"prompt":"Write a local-readiness and failure-handling plan for one anonymous composition.","deliverables":["Prerequisite evidence matrix","Permitted inspection versus prohibited action","Expired-authority stop condition","Retained-event/disclosure requirements"],"success":["Local authority is explicit and scoped","Unrelated safe inspection remains possible","No execution or performance is invented","The book’s future is translated into testable requirements"]},"question":{"prompt":"The cloud is unavailable and local authority has expired. What may the proposed runtime do?","correctIndex":2,"choices":[{"text":"Act because the rule is stored locally.","explanation":"A local rule is not a current authorization."},{"text":"Delete incomplete observations until reconnection.","explanation":"That erases the evidence needed for recovery and review."},{"text":"Retain evidence and permit safe inspection; hold actions requiring that authority.","explanation":"Offline capability does not extend expired delegation or justify improvising physical action."}]},"screens":[{"title":"Unbound local and shared operating context","href":"/pillars/p4#pillar-workspace"},{"title":"Retained evidence and authority gaps","href":"/pillars/p5#pillar-workspace"}],"number":"3030","track":"book","references":[{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[806]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[807]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[809]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[811]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[814]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[816]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[818]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[820]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[822]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:tbl[34]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[826]","classification":"future_vision"},{"kind":"book","label":"ThingDaddy book · Chapter 24","sha256":"71e6f7f572534c88a701043b60d5f3f842434a8880c34894eb4fe66177f68d9f","pointer":"/w:document/w:body/w:p[828]","classification":"future_vision"}],"sourceNotes":["Chapter 24 · 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 the final actual body chapter in the supplied source. Local execution, autonomy, timing and commissioning claims remain unverified vision; appendices A–G are absent from the supplied body.","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."],"lessonLocator":"/learn/deep-dive/3030","recordReference":"#/lessons/59","completeCourseReference":"/api/demo/learning-course?view=full#/lessons/59","referenceKind":"educational-content-locator-not-gs1-identity"}]}