Entity Core Protocol

The vocabulary this corpus uses — 25 of 25 authored terms occur in entity-core-protocol/specs (4 files). Definitions are authored or pulled from each term's canonical home; occurrences are located deterministically.

B

Bootstrap type

One of the 14 seed types required to define all other types.

— ENTITY-NATIVE-TYPE-SYSTEM §1.3 (Terminology)

Also: bootstrap types.

See also: Type entity, Type resolution.

Used 13 times across 3 documents.

C

Capability

The authority a peer holds to act, transferred cryptographically and validated by chain-walking.

— ENTITY-CORE-PROTOCOL §3.5

Also: capabilities.

See also: Peer, Identity.

Used 500 times across 4 documents.

CBOR

Concise Binary Object Representation (RFC 8949) — the wire encoding. Chosen for type preservation, deterministic encoding, and being self-describing.

— ENTITY-CBOR-ENCODING §1.3, §2

See also: ECF, CDDL.

Used 191 times across 4 documents.

CDDL

Concise Data Definition Language (RFC 8610) — the notation used for type definitions.

— ENTITY-CBOR-ENCODING §1.3 (Terminology)

See also: CBOR, Type entity.

Used 27 times across 2 documents.

Conformance

The contract a peer is measured against — not the version number. The full suite is the gate, and a published number is reproducible and oracle-pinned.

— ADR-0012; AGENTS-STANDARD.md §Honesty & conformance

Also: conformance level, conformance levels.

See also: Peer, Keystone.

Used 80 times across 4 documents.

Constraint

A value predicate attached to a field-spec: an entity {type, data} whose type selects the handler and whose data supplies the parameters.

— EXTENSION-TYPE §1.6 (Terminology)

Also: constraints.

See also: Field-spec, Narrowing, Handler.

Used 89 times across 4 documents.

Content hash

format_code ‖ SHA256(ECF(type, data)) — the identifier derived from an entity's own content.

— ENTITY-CORE-PROTOCOL §1.2, §7.1

Also: content_hash, content-addressed, content addressing.

See also: Identity, ECF, Entity.

Used 214 times across 4 documents.

E

ECF

Entity Canonical Form — the deterministic encoding used for hashing.

— ENTITY-CBOR-ENCODING §1.3 (Terminology)

Also: Entity Canonical Form.

See also: CBOR, Content hash.

Used 76 times across 4 documents.

Emit

The atomic Store-and-Bind: writing an entity and binding it into the tree as two independently observable events.

— ENTITY-CORE-PROTOCOL §6.10

See also: Tree, Execution.

Used 29 times across 3 documents.

Entity

The typed data unit — {type, data, content_hash}. Everything in the system is one.

— ENTITY-CORE-PROTOCOL §1.1

Also: entities.

See also: Identity, Tree, Content hash.

Used 607 times across 4 documents.

Envelope

The message container: a root entity plus a map of the entities included with it.

— ENTITY-CORE-PROTOCOL §3.1

See also: Entity, EXECUTE.

Used 117 times across 4 documents.

EXECUTE

One of the protocol's only two messages, with EXECUTE_RESPONSE. All dispatch goes through it.

— ENTITY-CORE-PROTOCOL §3

Also: EXECUTE_RESPONSE.

See also: Execution, Envelope, Handler.

Used 187 times across 3 documents.

Execution

Typed dispatch via EXECUTE — the protocol's evaluator. Adding it to the substrate is the largest single-step unlock in the build-up sequence.

— ENTITY-CORE-PROTOCOL §3.2–3.3

See also: Emit, Peer, Handler.

Used 21 times across 2 documents.

F

Field-spec

A field specification defining the shape and optionality of a field.

— ENTITY-NATIVE-TYPE-SYSTEM §1.3 (Terminology)

Also: field spec, field-specs.

See also: Constraint, Type resolution.

Used 59 times across 4 documents.

H

Handler

The unit that implements an operation, reached through the dispatch chain under the capability model.

— EXTENSION-TYPE §2.1; ENTITY-CORE-PROTOCOL §3.2–3.3

Also: handlers.

See also: Execution, EXECUTE, Capability.

Used 526 times across 4 documents.

I

Identity

Content-derived naming: an entity's name IS a hash of its content, so the name cannot disagree with what it names.

— ENTITY-CORE-PROTOCOL §1.2, §7.1

See also: Entity, Content hash, Peer.

Used 111 times across 4 documents.

K

Keystone

The canonical conformance anchor — provided, not mandatory; anyone may build a ground-up implementation instead.

— ADR-0012

Also: entity-core-keystone.

See also: Conformance, Peer.

Used 1 time across 1 document.

N

Narrowing

The requirement that a child type's constraints are equal to or more restrictive than its parent's.

— EXTENSION-TYPE §1.6 (Terminology)

See also: Constraint, Type resolution.

Used 15 times across 2 documents.

P

Peer

Identity plus capabilities plus connection — the unit of distribution.

— ENTITY-CORE-PROTOCOL §3.5

Also: peers.

See also: Identity, Execution, Capability, Conformance.

Used 463 times across 4 documents.

Primitive

One of the six irreducible units the whole system is built from: entity, identity and tree (informational); emit and execution (temporal); peer (spatial). Everything above them is composition of them.

— ENTITY-CORE-PROTOCOL §1

Also: primitives.

See also: Entity, Identity, Tree, Emit, Execution, Peer.

Used 575 times across 4 documents.

S

Structural compatibility

The property of two types expanding to the same effective field set — the basis on which peers decide whether they can meaningfully process each other's data.

— ENTITY-NATIVE-TYPE-SYSTEM §1.3, §12

See also: Type resolution, Peer.

Used 7 times across 1 document.

T

Tree

A mutable namespace of path → hash bindings laid over the immutable content store. The tree is what changes; the entities it points at do not.

— ENTITY-CORE-PROTOCOL §1.4, §1.7

Also: trees.

See also: Entity, Emit, Peer.

Used 427 times across 4 documents.

Type entity

An entity of type system/type that defines a type. Type definitions are themselves entities in the tree — this is the self-description fixed point.

— ENTITY-NATIVE-TYPE-SYSTEM §1.3 (Terminology)

See also: Entity, Type path, Bootstrap type.

Used 5 times across 1 document.

Type path

The short path identifying a type — e.g. primitive/string, system/protocol/connect/hello.

— ENTITY-NATIVE-TYPE-SYSTEM §1.3 (Terminology)

See also: Type entity, Type resolution.

Used 11 times across 2 documents.

Type resolution

Expanding a type path to its effective field set.

— ENTITY-NATIVE-TYPE-SYSTEM §1.3 (Terminology)

See also: Type path, Structural compatibility.

Used 13 times across 3 documents.