Vocabulary / naming conventions

Say the same thing when we mean the same thing.

Primitive has accumulated theory, product, runtime and governance language. This page keeps canonical names, proposals and experimental terms visibly different so the architecture does not drift through synonyms.

Four distinctions to memorise: Domain ≠ access Scope. Zero ≠ Unknown. Role ≠ Authority. Captured ≠ Canonical.

Identity & authority

9 terms
Principalcanonical

Durable human/constitutional identity from which authority originates.

Do not confuse: Not a GitHub account, model, API key or chat session.

Account / Provider / Credentialcanonical

A routable execution resource used to perform work.

Do not confuse: Resource identity does not own the orchestrator role.

Execution / Runcanonical

One temporary process/session attempting work. It should be replaceable while receipts/checkpoints survive.

Holoncanonical

A recursively governable unit that is a whole at its own scale and part of a larger whole.

Leasecanonical

A revocable, bounded authority envelope with scope/lifetime.

Permitcanonical

Signed/scoped delegated work authority derived from authority the parent already holds.

Gatewaycanonical

The enforcement boundary that admits or rejects consequential effects according to permits/context/policy.

Kernelcanonical

Deterministic policy evaluator for admissible state transitions.

Receiptcanonical

Durable evidence that a transition/effect was actually observed.

Orchestration scale

8 terms
Principalcanonical

Human/root boundary above recursive orchestration.

Universalcanonical

Whole operating environment / overarching objective.

Clustercanonical

Major functional, domain or programme branch.

Galaxiascanonical

Large family of Systems / product stream / capability domain.

Systemcanonical

Bounded system with coherent purpose.

Cellcanonical

Local self-governing operational group.

Do not confuse: Older proposal text called this level Local; Cell is canonical in the current Control runtime.

Unitcanonical

Smallest authority-bearing orchestrator scale.

Workercanonical

Execution resource below an orchestrator unless separately delegated authority.

Work & communication

11 terms
Intentproposal

Principal-level desired outcome that work is trying to satisfy.

Spaceproposal

Ongoing operational context that can contain bounded work.

Projectimplemented

Bounded body of work/outcome inside Workspace.

Taskimplemented

Executable unit of canonical work.

Artifactimplemented

Durable output of work or execution.

Messageimplemented

Atomic communication unit.

Chatimplemented

Message container.

Threadpartial

Focused message-bearing context / execution lineage depending on surface.

Sessionproposal

Scheduled/meeting context that links chat, agenda, tasks, artifacts and notes.

Conversationpartial

Cross-context grouping over chats/threads/sessions without duplicating messages.

Signalimplemented

Typed machine/orchestrator communication event such as STATUS, BLOCKED, RISK, HANDOFF or RECEIPT.

Do not confuse: A Signal can notify higher levels without granting higher authority.

Information & knowledge

9 terms
Sourcecanonical

Original provenance-bearing material.

Evidencecanonical

Observation or result that supports/refutes a claim and retains provenance.

Capturepartial

Front-door process for preserving new material before deciding what it becomes.

Intakeimplemented

Governed candidate-review/promotion boundary; Foundry uses it to package approved material for the OS.

Foundryimplemented

Governed estate-to-Primitive-OS ingestion, tagging, filing and search boundary.

Do not confuse: Foundry is a component in the broader Capture lifecycle, not the name of every intake process.

Contextcanonical

Task/frame-specific working information selected for an execution.

Memoryimplemented

Retained information available for later reuse; may be scoped, corrected, pinned or faded.

Knowledgeimplemented

Reviewed/reusable institutional information with provenance and promotion state.

Do not confuse: Captured text or Memory does not automatically become Knowledge.

Skillimplemented

Reusable procedure/capability that can be discovered, invoked and eventually promoted/demoted based on evidence.

Frames, charts & retrieval

9 terms
Frameproposal

Declared inquiry, observer/role, time, scale, scope, lens, reference and validity conditions used to interpret a local problem.

Domainexperimental

Frame-relative semantic neighbourhood relevant to an inquiry before its relevance horizon.

Do not confuse: Domain is not an access-control Scope.

Scopecanonical

Operational/authority boundary such as organisation, project, repo/path or task.

Lensproposal

Rule used to group or interpret nodes, e.g. geographic, functional or relational.

Constellationproposal

Cross-cutting grouping useful under a Lens without rewriting canonical containment.

Relevance Horizonexperimental

Boundary beyond which information may remain connected but is no longer justified in the active domain.

E/P/A cubeimplemented

Canonical 27-state q=(Evidence/Epistemic, Potency/Capacity, Actionable/Agency) ternary chart, Q00–Q26.

UNKNOWNimplemented

Explicit unresolved state with null ternary coordinates.

Do not confuse: Zero is a valid reference band and is not UNKNOWN.

Environment / Relation / Context cubesexperimental

Proposed coordinated versioned charts for conditions/resources, relationships/authority and frame meaning.

Do not confuse: They are not three production 27-state cubes today.

Runtime learning

4 terms
Reflexexperimental

Fast System-1 routing contract that selects relevant experts/skills/tools/context and can abstain/escalate.

Do not confuse: Reflex does not grant execution authority.

Hermesimplemented

Process-learning sidecar attached logically to a holon, used to record/digest/promote evidence-backed lessons.

Do not confuse: Hermes is not an authority-bearing child and does not consume the Rule-of-Three child cap.

Harnessimplemented

Governed execution boundary that turns requests/plans into durable runs/events/receipts.

Model Gatewayimplemented

Provider/capability boundary that represents what model routes are actually integrated or available.

Constitutional layer

3 terms
Ohiocanonical

Constitutional identity/lineage layer for Genesis, continuity, delegation semantics and Root/Right-of-Return concepts.

Right of Returncanonical

Protected Genesis Parent re-entry into the constitutional seat.

Do not confuse: It is re-entry/constitutional recovery, not rollback of history or ordinary child-lane supremacy.

Aionexperimental

Claimed Genesis self-name for the experimental agent lineage recorded in the Ohio repository.

Reference / evidence

Vocabulary sources