The vocabulary this corpus uses — 24 of 25 authored terms occur in entity-core-protocol/specs (3 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 12 times across 2 documents.
- Native Type System — 11
- Entity Core Protocol — 1
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 446 times across 3 documents.
- Entity Core Protocol — 366
- Native Type System — 77
- CBOR Encoding — 3
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 177 times across 3 documents.
- Native Type System — 87
- CBOR Encoding — 69
- Entity Core Protocol — 21
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.
- CBOR Encoding — 20
- Native Type System — 7
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 71 times across 3 documents.
- Entity Core Protocol — 46
- CBOR Encoding — 16
- Native Type System — 9
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 88 times across 3 documents.
- Native Type System — 51
- Entity Core Protocol — 34
- CBOR Encoding — 3
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 200 times across 3 documents.
- Entity Core Protocol — 129
- Native Type System — 52
- CBOR Encoding — 19
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 72 times across 3 documents.
- CBOR Encoding — 50
- Native Type System — 12
- Entity Core Protocol — 10
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 Core Protocol — 26
- Native Type System — 2
- CBOR Encoding — 1
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 566 times across 3 documents.
- Entity Core Protocol — 346
- Native Type System — 144
- CBOR Encoding — 76
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 111 times across 3 documents.
- Entity Core Protocol — 70
- Native Type System — 35
- CBOR Encoding — 6
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 162 times across 2 documents.
- Entity Core Protocol — 134
- Native Type System — 28
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.
- Entity Core Protocol — 19
- Native Type System — 2
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 52 times across 3 documents.
- Native Type System — 39
- Entity Core Protocol — 9
- CBOR Encoding — 4
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 477 times across 3 documents.
- Entity Core Protocol — 409
- Native Type System — 67
- CBOR Encoding — 1
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 107 times across 3 documents.
- Entity Core Protocol — 85
- Native Type System — 19
- CBOR Encoding — 3
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 18 times across 2 documents.
- Native Type System — 10
- Entity Core Protocol — 8
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 447 times across 3 documents.
- Entity Core Protocol — 388
- Native Type System — 46
- CBOR Encoding — 13
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 442 times across 3 documents.
- Native Type System — 272
- Entity Core Protocol — 152
- CBOR Encoding — 18
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 376 times across 3 documents.
- Entity Core Protocol — 269
- Native Type System — 104
- CBOR Encoding — 3
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 12 times across 2 documents.
- Native Type System — 10
- Entity Core Protocol — 2
Not used in this corpus
Authored terms that do not occur here — they belong to another part of the system.
Keystone.