Zenith ResearchCanonical company wiki
OntologyCompany

Domain terminology / canonical synthesis

Terminology and semantic boundaries

Canonical vocabulary for Zenith Research, separating the company, protocol, deployment, Hub, Vault, agents, knowledge structures, data foundries, network, and treasury concepts so retrieval does not merge distinct entities.

Updated
2026-08-29
Source digest
8c1e3213f143
Structured data
JSON-LD

Scope

This page owns the canonical meaning of recurring Zenith terms. Use it when a note appears to use company, product, network, agent, data, or vault language interchangeably.

Current answer

Zenith Research is the company. Zenith is the operating protocol, product family, and network initiative it is building. A deployment is a sovereign organizational installation; the mesh is the relationship among independently controlled deployments. Hub, Vault, agents, processes, data artifacts, and governance instruments are components of that system, not interchangeable names for it.

Evidence and influences

  • defines the company/product boundary: Zenith Research.
  • defines the runtime boundary: A vault deployed on the node is the node vault; every other vault connecting to that hub is a client vault.
  • defines the agent distinction: Raziel manages the business knowledge ontology while Frank manages the business information ontology — static structure vs objects in motion.
  • defines the network registry: Zenith consortium — hub registry and relay for the connected workspace mesh.
  • defines the foundry distinction: micro1 clarifies Zenith's differentiator as a self-sovereign brokered data mesh rather than a centralized data vendor.

Core entities

TermCanonical meaning
Zenith ResearchThe company and research organization building Zenith. See Zenith Research.
ZenithThe operating protocol, product family, and network initiative. Not the legal company name.
Zenith deploymentA sovereign organizational installation consisting of a Hub, one or more Vaults, agents, tools, and configured processes.
Zenith meshThe network of independently controlled deployments that expose approved APIs, MCP interfaces, tools, data, or collaboration surfaces.
Zenith consortiumThe registry and relay layer that helps deployments discover and synchronize with one another. See Zenith consortium — hub registry and relay for the connected workspace mesh.

Runtime and knowledge substrate

TermCanonical meaning
HubA runtime node. It executes agents and tools, exposes interfaces, connects to other hubs, and operates against Vaults.
VaultA persistent, runtime-agnostic knowledge base. It stores notes, capture, releases, configuration, and explicit links.
Node VaultThe locally controlled Vault belonging to a Hub operator.
Client VaultA Vault connected to a Hub but controlled by another user or organization.
SpaceA shared presentation or module surface that aggregates linked knowledge. It is not a subject-matter domain or a real-world arena.
DomainA subject-matter area inside the knowledge ontology. In this wiki, Zenith Research is also treated as an organizational wiki domain, while its notes retain ordinary vault domains in frontmatter.
ArenaA real-world theater where knowledge is applied, such as Zenith, Gallery, or Zendo.

Agents and execution

TermCanonical meaning
FrankDispatcher and coordinator for information in motion. Frank classifies requests, selects processes, routes executors, and tracks state; he does not perform every specialist task himself.
RazielKnowledge-ontology and retrieval agent. Raziel organizes what the organization knows and maintains the structures that make it retrievable.
ProcessAn author-facing SOP or declared workflow with inputs, outputs, states, review points, and execution dependencies.
SkillReusable workflow knowledge loaded into an agent's context. A skill is not the same as a callable tool.
ToolA callable capability exposed to an agent through the runtime, API, or MCP.
ExecutorA human, agent, service, or tool capable of performing a routed unit of work.

Knowledge and evidence

TermCanonical meaning
Atomic noteOne assertable concept or claim, written as a natural retrieval chunk and connected by explicit links.
MOCMap of content. A curated relationship and navigation surface. A canonical domain page may act as a MOC, but it must also state the authoritative synthesis directly.
BucketThe versioned set of accepted propositions that must remain internally consistent.
ClaimA proposition that can be supported, challenged, ratified, or superseded.
EvidenceA source, observation, result, or proof that changes confidence in a claim.

Data and economics

TermCanonical meaning
Operational traceInput, output, tool call, decision, review, correction, and outcome produced while real work is performed.
Data artifactA rights-scoped training, evaluation, benchmark, rubric, reference, or telemetry object derived from a source or workflow.
Rights envelopeMachine-readable ownership, purpose, lineage, retention, revocation, attribution, redistribution, and revenue-routing metadata attached to an artifact.
Data foundryA system that converts raw expertise or operations into quality-controlled, reusable data products.
Sovereign data foundryA data foundry deployed under the source organization's control, with permissioned aggregation and traceable source-side economics.
Treasury companyAn operating company in the Zenith network whose economics allocate value among operators, contributors, and the collective treasury.

Current category sentence

micro1 is a centralized data foundry. Zenith is the distributed operating protocol that enables sovereign data foundries. This is a direct competitive position at the data and evaluation layer, even when the initial customer segments differ.