ENTITY Documentation Portal
Developer manual · non-normative implementer orientation

Clean-Room Glossary & Object Map

A plain-language entry point for engineers reading the sealed ENTITY Protocol 1.0 external conformance kit for the first time. Each term below starts with what the term is in Protocol 1.0 and then, where useful, states a boundary.

Important boundary: this page is non-normative orientation material. The signed conformance kit, its schemas, interoperability profile, canonicalization rules, vectors and pass criteria remain authoritative. The sealed v1.0.2 kit is unchanged.

Core vocabulary

Vector

A vector is a conformance input supplied by the sealed kit and evaluated by a candidate implementation. The black-box interface invokes the candidate with verify --kind <KIND> --input <PATH>; the candidate returns an accepted decision and supporting result data. Required valid vectors must be accepted and required invalid or tampered vectors must be rejected.

Entity

An Entity is a protocol identity identified by an ent1-… or ent2-… identifier and described by a signed sovereign-entity-manifest-v2. The manifest records the Entity ID, Entity classification, display name, aliases, verification methods, active signing key, recovery/cryptographic metadata, creation time, revision and signature.

Entity root

The Entity root is the Entity identity that the Protocol 1.0 interoperability profile treats as authoritative for that Entity. Verification starts from the signed Entity manifest and its active verification method. For ent2, the identifier is opaque and is intended to persist across operational-key or provider replacement.

Sovereign Entity manifest

A sovereign Entity manifest is the signed root identity document whose schema identifier is sovereign-entity-manifest-v2. It is the protocol object a verifier uses to obtain the Entity ID, key material/state, aliases, recovery information and manifest revision before applying identity/signature rules.

Alias

An alias is an alternate string stored in the Entity manifest's aliases array and associated with that Entity. It is an alternate identifier/name for the Entity; Protocol 1.0 does not treat the alias itself as the authority root.

Authority

Authority is permission recognized by Protocol 1.0 for a specific action, relationship or scope after the applicable signed records satisfy the interoperability profile. Authority is evaluated from protocol records and their state, such as signed Entity manifests, scoped relationship evidence, principal bindings, node authorizations and revocations.

In the principal-binding profile, for example, the required relationships include Principal → Installation SOVEREIGN_AUTHORITY, Application → Installation PROCESSING_AUTHORITY, and Device → Installation POSSESSION. These relationships are scoped and revocable.

Sovereign authority

Sovereign authority is authority rooted in the Entity identity/control relationship recognized by Protocol 1.0. In the public principal-binding rules, SOVEREIGN_AUTHORITY is the required active Principal → Installation relationship, verified together with the relevant signed manifests, binding hash, signature and relationship identifiers.

Signature validity

Signature validity means the signature for the applicable protocol object verifies according to the kit's canonicalization and Ed25519 rules using the referenced active verification method and required signature suite. For an Entity manifest, a valid signature establishes cryptographic control by the applicable active verification method.

Legal ownership and objective external-world truth are not protocol-validity states defined by Protocol 1.0. The interoperability profile therefore says that a valid manifest signature, by itself, does not establish those separate external claims.

Schema validity

Schema validity means the JSON object satisfies the structural constraints of its applicable public JSON Schema: required fields, types, constants, enumerations, formats and other schema rules.

Protocol validity

Protocol validity means an input satisfies every Protocol 1.0 rule applicable to that object and operation, not merely its JSON Schema. Depending on the object, those rules include canonicalization/hash checks, signature verification, active verification-method state, authority/binding relationships, revocation state, lineage commitments, version rules and the semantic requirements in the interoperability profile.

A schema-valid object can therefore be protocol-invalid. The sealed kit deliberately includes invalid vectors that are structurally plausible but must still be rejected.

Fail closed

Fail closed means the verifier rejects when a required authority, signature, binding, revocation/version or other mandatory protocol check cannot be established. Unknown major versions and failed required checks are not silently accepted.

Terms that are outside the Protocol 1.0 data model

The interoperability profile occasionally names concepts such as hosting, DNS possession, storage possession, infrastructure ownership, legal ownership or external-world truth to define a boundary. These are not additional Protocol 1.0 object types that an implementer must model for phase-one conformance. Their purpose in the profile is to make clear that those external conditions cannot substitute for the signed/scoped protocol records required to establish authority or validity.

Controlled values: classification or semantics?

FieldAllowed values in the public kitProtocol role
entity_typeperson, family, business, product, application, system, community, service, organization, projectControlled classification of the Entity. The value does not itself grant authority.
verification_methods.statusactive, retired, revokedSemantic verification-method state. Identity/signature verification requires the applicable active method.
asset_kindSOFTWARE, DATA, MODEL, KNOWLEDGE, EVIDENCERequired classification in an asset envelope and part of envelope validation.
conflict_stateCLEAR, CONFLICTSemantic state of a name claim's conflict condition.
delegated_actionsINGEST_ASSET, RECORD_EVENTExplicit bounded actions delegated by a principal binding.
relationship statusACTIVE, REVOKEDSemantic relationship state; required binding relationships must be active.

Object map

The table below answers “what is this object for?” before an implementer reads the JSON Schema field by field.

ObjectPlain-language purposeMain verification question
entity_identityThe sovereign-entity-manifest-v2 root identity document containing the Entity ID, classification, aliases, verification methods, active signing key, recovery/crypto metadata, revision and signature.Is this a structurally valid manifest with the correct Entity identity and a valid signature from the applicable active verification method?
signature_recordSignature metadata containing the key reference, signature suite and signature material used by signed protocol objects.Does the referenced key/suite/signature verify the canonical object required by the profile?
principal_bindingA signed/scoped binding connecting Principal, Application, Device and Installation Entity IDs with bounded delegated actions.Do the binding hash, principal signature, four manifests and required active relationships agree?
principal_binding_bundleThe conformance bundle carrying the principal binding together with the manifests and relationship evidence needed to verify it.Can the complete binding context be validated rather than trusting IDs in isolation?
relationshipRelationship evidence that records relationship type, participating Entity IDs, scope, state and evidence needed by the applicable profile.Is the required relationship present, active and correctly scoped?
asset_envelopeA hash-addressed registration envelope for SOFTWARE, DATA, MODEL, KNOWLEDGE or EVIDENCE that carries metadata and content commitments without embedding raw content.Does the envelope satisfy its schema/profile rules and preserve any declared parent/derivation lineage?
event_envelopeA hash-addressed governed event representation that carries event metadata and a payload commitment without embedding the raw payload.Does the event use an allowed event type and satisfy the event-envelope validation rules?
domainA Domain object bound to an Entity root and used as the starting object for the Domain verification sequence.Does the Domain bind to the expected Entity root and satisfy the applicable Domain rules?
name_claimA signed normalized-name claim associated with a Domain and Entity root.Does the claim verify and bind to the expected Domain/Entity context?
node_authorizationA scoped authorization record for a node, including the node key, permitted services, network/publication/data scopes, timing and authorization version.Is the node currently authorized for the requested scope?
node_revocationA signed record that revokes a node authorization from an effective time and records the revocation reason.Has the applicable authorization been revoked, and from when?
revoked_node_bundleConformance material combining authorization and revocation evidence for a node.Does the verifier reject the node after the applicable revocation takes effect?
service_manifestSigned service/presence material used in the Domain verification sequence.Is the service/presence record signed, current and inside the required authorized node context?
resolution_proofProof material used by the public profile when resolving or interpreting an ENTITY Domain.Does the proof preserve the expected Entity-root/Domain binding and other required verification state?
domain_snapshotA captured Domain state used by the public Domain and export conformance vectors.Can the captured state and its commitments be interpreted and verified consistently?
domain_exportA portable Domain package containing an export manifest plus committed identity/snapshot state so it remains interpretable outside the originating runtime.Do the package, snapshot, identity commitments, Entity-root binding and export signature verify?
transaction_evidenceA transaction-related evidence object included in the public schema set.Does the evidence satisfy the applicable schema/profile rules without treating the evidence object itself as a substitute for unrelated external claims?

Suggested clean-room reading order

Entity manifest / Entity root
  ↓
Canonicalization + signature verification
  ↓
Principal / device / installation / application binding
  ↓
Asset + event envelopes
  ↓
Relationships and lineage
  ↓
Domain + name claim
  ↓
Node authorization / revocation
  ↓
Service / resolution / snapshot
  ↓
Portable domain export

Four implementation distinctions

  1. Entity root vs. alias: verification authority starts from the Entity root; an alias is an alternate manifest value.
  2. Schema validity vs. protocol validity: structural JSON validity is necessary but not sufficient.
  3. Signature validity vs. other external claims: a valid protocol signature establishes the cryptographic fact defined by the profile; it does not automatically establish unrelated claims outside that profile.
  4. Registration/lineage vs. rights/economic conclusions: an asset registration or lineage record proves only the protocol facts it actually contains and verifies.

Authoritative implementation material

Implement from the sealed ENTITY Protocol 1.0 External Conformance Kit. Start with protocol/ENTITY_PROTOCOL_1_0_INTEROPERABILITY_PROFILE.md, protocol/CANONICALIZATION_AND_CRYPTOGRAPHY.md, profiles/CLEAN_ROOM_RULES.md, conformance/IMPLEMENTATION_INTERFACE.md, vectors/VECTOR_MANIFEST.json and conformance/PASS_CRITERIA.md.

Why this page lives here: the conformance-kit integrity gate protects the signed/sealed evidence artifact. Clarifying orientation material therefore lives in the documentation portal rather than altering the frozen v1.0.2 kit.

Continue to the clean-room implementation challenge →