◉ ThingDaddy

P1 · The enduring anchor

Name the thing. Preserve its context.

An In-Context ID uses the applicable standard identity and semantic key type. Meaning comes from attributed records and relationships—not from guessing what an identifier’s characters mean.

General introduction · no private company records. Local candidate, not an AWS deployment. Reading or publishing context never authorizes physical execution.

Context connects; identity survivesA supplier asset remains separately identified when linked to an installed component context and a parent instrument. Documents, materials and location retain their own identities. Installation, removal and replacement append history.Typed bondsHistory preservedSupplier asset · GIAIInstalled component · CPIDParent instrument · GIAIDocuments · GDTIMaterials · GTIN contextLocation · SGLN
Conceptual map · not source graph data. A supplier asset remains separately identified when linked to an installed component context and a parent instrument. Documents, materials and location retain their own identities. Installation, removal and replacement append history.
Read the diagram as text
  • Supplier asset · GIAI
  • Installed component · CPID
  • Parent instrument · GIAI
  • Documents · GDTI
  • Materials · GTIN context
  • Location · SGLN

The role determines the key.

An individual asset can use a GIAI; a document can use a GDTI; product, serialized-unit and lot contexts use their applicable trade-item representations. A location, component or service relationship keeps its own semantic type.

Keep a protocol family, protocol version and selected configuration as separate document identities. A GSRN service relationship and its SRIN service-instance or run binding do not replace those document versions.

Source and scope

ThingDaddy connected five-pillar requirements · 2026-10-30
Architecture and policy, not proof of deployed capability.
SHA-256: df3ef7a1b3a2903639514117b10b2c14bc1b83a30a7bf89ffcea1b7654f9d479

Digital civilization vision and identity-bond requirements · 2026-10-30
Exact participants and measured feedback; roadmap is not an operational claim.
SHA-256: fb9fdb86346030f9f479be8541ed23b272d8906d8bc9a436c0c2a8f9a5dea131

Identity status is a fact of each record.

Retained source identifiers, existing issued identities, private proposals, inactive invalid assertions and identity gaps remain distinguishable. Not every displayed ID is a proposal, and a correctly formatted identifier is not proof of a physically verified unit.

Use the exact evidenced prefix and preserve separate prefix records. A regulatory source assertion is not automatically a GS1 licence determination. ThingDaddy may issue governed private proposal IDs under its rules; client validation, adoption and certification are separate states.

Source and scope

ThingDaddy registry and customer-builder requirements · 2026-10-30
Namespace authority, source preservation and scoped editing requirements.
SHA-256: 3785b8e9c14ab1adbfe56bf9ac1c47f198d2c1c381c2f71eb7462916edaf2d4b

Digital civilization vision and identity-bond requirements · 2026-10-30
Exact participants and measured feedback; roadmap is not an operational claim.
SHA-256: fb9fdb86346030f9f479be8541ed23b272d8906d8bc9a436c0c2a8f9a5dea131

Installation adds a relationship—not a replacement.

Preserve the supplier asset identity, its installed component context and the parent instrument identity. Removal ends a relationship’s active interval; replacement adds a new bond and event. Earlier identities and sources survive.

A URL locates content, a hash binds bytes, and an internal record key addresses storage. None substitutes for an established standard identity. These educational diagrams contain no assigned asset IDs.

Source and scope

ThingDaddy registry and customer-builder requirements · 2026-10-30
Namespace authority, source preservation and scoped editing requirements.
SHA-256: 3785b8e9c14ab1adbfe56bf9ac1c47f198d2c1c381c2f71eb7462916edaf2d4b