The vocabulary this corpus uses — 24 of 25 authored terms occur in entity-system-architecture/specs/extensions (26 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 2 times across 2 documents.

• EXTENSION-IDENTITY — 1
• EXTENSION-TREE — 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 626 times across 25 documents, the 12 it is used in most.

• EXTENSION-COMPUTE — 105
• EXTENSION-ROLE — 93
• EXTENSION-CONTINUATION — 53
• EXTENSION-HISTORY — 38
• EXTENSION-TREE — 37
• EXTENSION-NETWORK — 36
• EXTENSION-REVISION — 35
• EXTENSION-REGISTRY — 32
• EXTENSION-SUBSCRIPTION — 25
• EXTENSION-CONTENT — 22
• EXTENSION-IDENTITY — 20
• EXTENSION-QUERY — 18

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 89 times across 14 documents, the 12 it is used in most.

• EXTENSION-TYPE — 33
• EXTENSION-TREE — 12
• EXTENSION-COMPUTE — 9
• EXTENSION-SIGNALING — 7
• EXTENSION-NETWORK — 6
• EXTENSION-CONTENT — 5
• EXTENSION-REGISTRY — 4
• EXTENSION-INBOX — 3
• EXTENSION-RELAY — 3
• EXTENSION-ENCRYPTION — 2
• EXTENSION-QUERY — 2
• EXTENSION-CONTINUATION — 1

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 218 times across 26 documents, the 12 it is used in most.

• EXTENSION-NETWORK — 23
• EXTENSION-REGISTRY — 23
• EXTENSION-QUERY — 18
• EXTENSION-COMPUTE — 17
• EXTENSION-CONTENT — 15
• EXTENSION-SIGNALING — 13
• EXTENSION-REVISION — 10
• EXTENSION-ROLE — 10
• EXTENSION-TREE — 10
• EXTENSION-TYPE — 10
• EXTENSION-ENCRYPTION — 9
• EXTENSION-RELAY — 8

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 304 times across 17 documents, the 12 it is used in most.

• EXTENSION-TYPE — 219
• EXTENSION-QUERY — 31
• EXTENSION-COMPUTE — 25
• EXTENSION-ROLE — 6
• EXTENSION-NETWORK — 4
• EXTENSION-TREE — 3
• EXTENSION-CONTENT — 2
• EXTENSION-ENCRYPTION — 2
• EXTENSION-IDENTITY — 2
• EXTENSION-REGISTRY — 2
• EXTENSION-SUBSTITUTE — 2
• EXTENSION-CONTINUATION — 1

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 381 times across 26 documents, the 12 it is used in most.

• EXTENSION-ENCRYPTION — 42
• EXTENSION-COMPUTE — 41
• EXTENSION-TREE — 32
• EXTENSION-REVISION — 30
• EXTENSION-REGISTRY — 29
• EXTENSION-CONTENT — 23
• EXTENSION-ATTESTATION — 22
• EXTENSION-ROLE — 22
• EXTENSION-CONTINUATION — 19
• EXTENSION-NETWORK — 16
• EXTENSION-IDENTITY — 15
• EXTENSION-RELAY — 14

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 68 times across 16 documents, the 12 it is used in most.

• EXTENSION-ENCRYPTION — 20
• EXTENSION-NETWORK — 9
• EXTENSION-TREE — 8
• EXTENSION-COMPUTE — 7
• EXTENSION-TYPE — 5
• EXTENSION-CONTENT — 4
• EXTENSION-REVISION — 3
• EXTENSION-RELAY — 2
• EXTENSION-ROLE — 2
• EXTENSION-SIGNALING — 2
• EXTENSION-DISCOVERY — 1
• EXTENSION-GROUP — 1

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 82 times across 18 documents, the 12 it is used in most.

• EXTENSION-REVISION — 16
• EXTENSION-TREE — 9
• EXTENSION-CLOCK — 8
• EXTENSION-HISTORY — 8
• EXTENSION-TRANSACTION — 7
• EXTENSION-IDENTITY — 6
• EXTENSION-QUERY — 5
• EXTENSION-NETWORK — 4
• EXTENSION-SUBSCRIPTION — 4
• EXTENSION-CONTINUATION — 3
• EXTENSION-COMPUTE — 2
• EXTENSION-CONTENT — 2

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 1677 times across 25 documents, the 12 it is used in most.

• EXTENSION-COMPUTE — 251
• EXTENSION-REVISION — 195
• EXTENSION-CONTENT — 154
• EXTENSION-ENCRYPTION — 102
• EXTENSION-QUERY — 97
• EXTENSION-CONTINUATION — 82
• EXTENSION-NETWORK — 78
• EXTENSION-TREE — 72
• EXTENSION-REGISTRY — 70
• EXTENSION-ROLE — 70
• EXTENSION-SUBSCRIPTION — 68
• EXTENSION-GROUP — 63

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 194 times across 20 documents, the 12 it is used in most.

• EXTENSION-CONTENT — 43
• EXTENSION-RELAY — 32
• EXTENSION-REVISION — 21
• EXTENSION-TREE — 19
• EXTENSION-NETWORK — 11
• EXTENSION-CONTINUATION — 10
• EXTENSION-COMPUTE — 9
• EXTENSION-IDENTITY — 9
• EXTENSION-SIGNALING — 9
• EXTENSION-QUERY — 5
• EXTENSION-SUBSCRIPTION — 5
• EXTENSION-GROUP — 4

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 327 times across 19 documents, the 12 it is used in most.

• EXTENSION-CONTINUATION — 67
• EXTENSION-NETWORK — 56
• EXTENSION-INBOX — 32
• EXTENSION-COMPUTE — 31
• EXTENSION-SUBSCRIPTION — 27
• EXTENSION-REVISION — 24
• EXTENSION-ROLE — 20
• EXTENSION-CONTENT — 15
• EXTENSION-TRANSACTION — 10
• EXTENSION-TREE — 10
• EXTENSION-HISTORY — 6
• EXTENSION-RELAY — 6

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 34 times across 11 documents.

• EXTENSION-HISTORY — 7
• EXTENSION-CONTINUATION — 6
• EXTENSION-REVISION — 5
• EXTENSION-COMPUTE — 4
• EXTENSION-QUERY — 4
• EXTENSION-CLOCK — 2
• EXTENSION-NETWORK — 2
• EXTENSION-IDENTITY — 1
• EXTENSION-ROLE — 1
• EXTENSION-SIGNALING — 1
• EXTENSION-TRANSACTION — 1

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 13 times across 1 document.

• EXTENSION-TYPE — 13

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 962 times across 26 documents, the 12 it is used in most.

• EXTENSION-REVISION — 110
• EXTENSION-COMPUTE — 106
• EXTENSION-ROLE — 99
• EXTENSION-CONTENT — 96
• EXTENSION-TYPE — 75
• EXTENSION-CONTINUATION — 72
• EXTENSION-TREE — 66
• EXTENSION-INBOX — 42
• EXTENSION-SUBSCRIPTION — 41
• EXTENSION-HISTORY — 35
• EXTENSION-IDENTITY — 33
• EXTENSION-QUERY — 32

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 601 times across 22 documents, the 12 it is used in most.

• EXTENSION-IDENTITY — 195
• EXTENSION-GROUP — 106
• EXTENSION-ENCRYPTION — 65
• EXTENSION-ROLE — 34
• EXTENSION-QUORUM — 26
• EXTENSION-REGISTRY — 23
• EXTENSION-ATTESTATION — 21
• EXTENSION-CONTINUATION — 20
• EXTENSION-NETWORK — 18
• EXTENSION-SUBSCRIPTION — 17
• EXTENSION-SIGNALING — 14
• EXTENSION-TREE — 13

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 3 times across 1 document.

• EXTENSION-ENCRYPTION — 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 23 times across 4 documents.

• EXTENSION-TYPE — 15
• EXTENSION-COMPUTE — 4
• EXTENSION-REGISTRY — 3
• EXTENSION-TREE — 1

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 1436 times across 26 documents, the 12 it is used in most.

• EXTENSION-NETWORK — 296
• EXTENSION-ROLE — 129
• EXTENSION-REGISTRY — 126
• EXTENSION-SIGNALING — 111
• EXTENSION-REVISION — 92
• EXTENSION-IDENTITY — 87
• EXTENSION-ENCRYPTION — 79
• EXTENSION-CONTINUATION — 63
• EXTENSION-SUBSCRIPTION — 62
• EXTENSION-COMPUTE — 52
• EXTENSION-DISCOVERY — 44
• EXTENSION-RELAY — 40

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 626 times across 25 documents, the 12 it is used in most.

• EXTENSION-COMPUTE — 66
• EXTENSION-REVISION — 60
• EXTENSION-ENCRYPTION — 55
• EXTENSION-TYPE — 46
• EXTENSION-GROUP — 43
• EXTENSION-CONTINUATION — 40
• EXTENSION-NETWORK — 35
• EXTENSION-SIGNALING — 29
• EXTENSION-ROLE — 28
• EXTENSION-IDENTITY — 27
• EXTENSION-TREE — 27
• EXTENSION-QUERY — 26

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 1 time across 1 document.

• EXTENSION-TYPE — 1

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 1264 times across 26 documents, the 12 it is used in most.

• EXTENSION-REVISION — 274
• EXTENSION-TREE — 226
• EXTENSION-COMPUTE — 124
• EXTENSION-NETWORK — 65
• EXTENSION-QUERY — 63
• EXTENSION-ROLE — 61
• EXTENSION-SUBSCRIPTION — 47
• EXTENSION-CONTENT — 41
• EXTENSION-HISTORY — 41
• EXTENSION-TYPE — 40
• EXTENSION-TRANSACTION — 35
• EXTENSION-CONTINUATION — 34

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 3 times across 2 documents.

• EXTENSION-TYPE — 2
• EXTENSION-COMPUTE — 1

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 12 times across 2 documents.

• EXTENSION-TYPE — 11
• EXTENSION-TREE — 1

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 7 times across 2 documents.

• EXTENSION-TYPE — 6
• EXTENSION-QUERY — 1

Not used in this corpus

Authored terms that do not occur here — they belong to another part of the system.

CDDL.