{
  "uid": "cogitave.learn.docs.glossary",
  "kind": "doc",
  "href": "/docs/glossary/",
  "title": "Glossary",
  "summary": "The terms used across Cogitave documentation and training, defined once - agent kernel, capability grant, provider driver, sandbox, sovereign unikernel, MCP, evidence, and the words that are easy to assume.",
  "type": "reference",
  "products": [
    "namzu",
    "yuva",
    "massar",
    "diyar"
  ],
  "roles": [
    "developer",
    "solution-architect",
    "platform-engineer"
  ],
  "levels": [
    "beginner"
  ],
  "subjects": [],
  "headings": [
    "Agent",
    "Agent kernel",
    "App package",
    "Capability",
    "Capability grant",
    "Cogitave Core",
    "Comms-loss watchdog",
    "De-energize-to-trip",
    "Device profile",
    "Dial-out (SSM/Arc) model",
    "Diyar",
    "Evidence",
    "Fact registry",
    "Fair Source / FSL-1.1-MIT",
    "Governed run / governed request",
    "Guardian agent",
    "HAL seam",
    "ISPM-15",
    "Learning path",
    "Massar",
    "MCP - Model Context Protocol",
    "Module",
    "Namzu",
    "Project baseline",
    "Property-graph substrate",
    "Provider / provider driver",
    "Request lifecycle",
    "Sandbox",
    "Solution",
    "Sovereign unikernel",
    "Tamper-evident evidence chain / Merkle history tree",
    "Tool",
    "Unit",
    "Verdict engine",
    "Yuva",
    "Next steps"
  ],
  "source": "\n# Glossary\n\nTerms are defined here once and used consistently everywhere else. Where a word\nis used differently elsewhere in the industry, that is noted.\n\n## Agent\n\nA program that pursues a goal by calling tools, under an identity, inside a\ncapability grant. In Cogitave usage an agent is a *process*, not a chat session -\nit has a lifecycle, a budget, and an audit trail.\n\n## Agent kernel\n\nThe layer that runs agents the way an operating system runs processes: isolation,\nscheduling, signals, budgets, memory, durability, and an event stream.\n[Namzu](what-is-namzu.md) is Cogitave's agent kernel. A kernel is deliberately\n*not* an application framework - it ships no interface and picks no vendor.\n\n## App package\n\nA Diyar app is a signed declarative package - a manifest, a grant, and a device\nprofile - that only selects among certified logic already compiled into the\ndevice firmware; it ships no code, container, or interpreter. It requests one\nof exactly three non-implicative permission tiers (`OBSERVE`, `OPERATE`,\n`ACTUATE`), and what it may actually do at runtime is the offline intersection\nof what the manifest requests, what its grant allows, and what the firmware has\ncertified to actuate (A n B n C) - computed from signatures alone, with no\ncloud round trip.\n\n## Capability\n\nA named authority an agent may exercise - a tool it may call, a resource it may\nread. Capabilities are an **allow-list**: an agent can do exactly what it declares\nand nothing more. See\n[Agent identity and capabilities](agent-identity-and-capabilities.md).\n\n## Capability grant\n\nThe explicit, least-privilege set of capabilities an agent runs under. Default\ndeny. Widening a grant is a human decision, never a workaround.\n\n## Cogitave Core\n\nCogitave's single canonical property graph - one typed model that every\nproduct, standard, and piece of documentation across the estate projects\ninto, served behind one MCP-native query layer. It is why a human and an\nagent asking the same question get the same answer: there is one model to\nquery, not one store per product.\n\n## Comms-loss watchdog\n\nA field-side heartbeat that makes a networked actuator (Modbus, OPC-UA, or\nBACnet) drop to its safe, de-energized output on its own, inside a declared\nexpiry window, the moment it stops hearing from the edge controller -\nindependent of whether the edge process or the cloud link is still alive.\nDiyar requires one on every field device it actuates over a network, so a\nlost link is fail-safe by construction rather than by a check the edge side\ncould also miss.\n\n## De-energize-to-trip\n\nThe governing safety principle behind Diyar's heater control: the safe state\nis always *heater off*, and any loss of control, evidence, or confidence - a\nsoftware fault, a stalled loop, a lost sensor reading, a failed journal write,\neven a reboot - must fall to that state rather than hold the last commanded\none. It is enforced in layers, from a mandatory hardware thermal cutoff down\nto a software typestate that releases the relay on drop.\n\n## Device profile\n\nThe signed, per-device configuration document that tells Diyar's\nproduct-agnostic runtime what it is running on: channels, actuators, safety\nlimits, process parameters, and which certified verdict engine to bind. The\nedge loads it parametrically at boot, fail-closed, so a different machine or\nprocess is a configuration change, not a fork.\n\n## Dial-out (SSM/Arc) model\n\nThe remote-access topology Massar uses instead of a VPN or mesh network: the\ndevice-side agent holds one persistent outbound connection to the cloud, and\nan operator reaches the device only through that relay, never by an inbound\nport on the device itself. Named for the AWS SSM Session Manager / Azure Arc\npattern it follows.\n\n## Diyar\n\nCogitave's edge-autonomous platform for regulated field devices - kilns, cold\nrooms, and other equipment that must keep working, and keep proving what they\ndid, without the network. What a specific industry needs on top of the\nplatform is a **solution**: a signed device profile plus a certified verdict\nengine, plugged in rather than forked.\n\n## Evidence\n\nA write-once record of an action, produced to the OpenTelemetry specification.\nAssume non-repudiation: evidence is what a reviewer or auditor reads, not a log\nyou tidy up afterwards.\n\n## Fact registry\n\nThe `facts.yaml`-backed registry that gives every load-bearing atomic fact - a\nnumber, a ceiling, a closed list - exactly one owner document; every other\nartifact cites it instead of retyping it. A read-only scanner (`fact-drift.py`)\nreads the estate and fails the quality gate the moment a restatement drifts\nfrom its owner, catching what the graph's own `xref`/`dependsOn` edges cannot\non their own.\n\n## Fair Source / FSL-1.1-MIT\n\nNamzu's licence. The source is readable and usable now, and every published\nversion converts to MIT two years after its release.\n\n## Governed run / governed request\n\nThe metered unit Cogitave prices agent usage on: one execution of an agent\nunder its capability grant, sandboxed and evidenced. Self-host Community stays\nunlimited on the operator's own compute; the managed Cloud free tier caps at\n25 governed requests a month, and paid tiers meter usage with no hard cap.\n\n## Guardian agent\n\nA small, always-on agent installed on a customer's own device that dials out\nto a Cogitave platform and holds no standing shell - a session (a PTY, a\ntunnel) is opened only for the duration of an explicit, authorized,\nTTL-bounded request. Massar is Cogitave's guardian agent for remote console\naccess.\n\n## HAL seam\n\nThe hardware-abstraction boundary in Diyar's edge runtime - `TempSource`,\n`RelayBank`, and `MonotonicClock` - above which nothing knows which physical\nboard is attached. New hardware becomes a driver behind this seam rather than\na fork of the safety or verdict logic that sits above it.\n\n## ISPM-15\n\nThe phytosanitary standard for wood packaging material - 56C core temperature\nheld for 30 minutes - and the name of Diyar's first certified solution. It is\none implementation behind the platform's `VerdictEngine` seam, not the product\nitself: the same platform runs a different process by swapping the device\nprofile and the certified engine.\n\n## Learning path\n\nAn ordered programme of modules in [training](/training/). Completing one earns a\ntrophy.\n\n## Massar\n\nCogitave's guardian dial-out remote-console agent: a small, cross-platform\nbinary installed on a customer's device that dials out to Diyar's console\nbroker so an authorized operator can open an audited web terminal to it, with\nno inbound port and no VPN. It holds no standing shell - a PTY exists only for\nan explicitly opened, TTL-bounded session.\n\n## MCP - Model Context Protocol\n\nThe protocol Cogitave exposes capabilities over. Tools are actions with typed\ninput and output; resources are addressable read-only surfaces. The point of\nbeing MCP-native is that a human calling an API and an agent calling a tool reach\nthe *same* surface, not two implementations of it.\n\n## Module\n\nA short, self-contained unit of [training](/training/) - a handful of units, an\nexercise, and a knowledge check. Completing one earns a badge. A module stands on\nits own even when it belongs to a learning path.\n\n## Namzu\n\nCogitave's agent kernel for TypeScript - see\n[What Namzu is](what-is-namzu.md). Where \"Agent kernel\" above names the\nconcept, Namzu is the concrete, Fair-Source-licensed implementation you\ninstall from npm and run on Node.\n\n## Project baseline\n\nThe set of standards and scaffolding every Cogitave repo inherits from\n`templates/base` at birth: always-on standards every repo gets regardless of\ntype, plus conditional standards switched on by the repo's product type\n(SaaS, API, frontend, agent). A repo does not assemble its own toolchain - it\nis born with the baseline already wired in.\n\n## Property-graph substrate\n\nThe physical implementation of Cogitave Core: one Rust process co-locating a\nlexical (BM25) engine, a vector (HNSW) engine, the typed property graph\nitself, and an embedded MCP server behind one query layer, so a query never\ncrosses a network boundary mid-flight. Chosen as a labeled property graph -\nnow ISO/IEC 39075:2024 (GQL) - over a relational-plus-graph-view, a triple\nstore, or a federated document store.\n\n## Provider / provider driver\n\nA model vendor adapter, published as its own package (`@namzu/openai`,\n`@namzu/ollama`, and others). The kernel treats every driver identically, so\nswitching vendors is a change at registration. See\n[Choose a provider](choose-a-provider.md).\n\n## Request lifecycle\n\nThe one process every change in the estate moves through: a unit of change is\na `Request`, a first-class Cogitave Core node, driven through seven stages by\nthe same two write tools whether a human or an agent is driving it. The rule\nunderneath every stage is propose-only - agents draft, classify, and open\nissues and PRs; they never merge, apply, release, or write a protected branch.\n\n## Sandbox\n\nThe enforcement layer for a capability grant. Namzu ships process-level isolation\nusing platform primitives (bubblewrap, Seatbelt) and container-level isolation\nwith a JWT-authenticated egress proxy. Declared in the kernel, enforced by the\nsandbox.\n\n## Solution\n\nDiyar's word for the domain-identity layer - the offering a device runs, such\nas ISPM-15 heat treatment - as distinct from the platform underneath it. Read\nas one sentence: an app deploys a solution to a device, realized by a\ncertified engine and configured by a signed profile.\n\n## Sovereign unikernel\n\nA kernel that owns the hardware it runs on rather than sitting as a process\ninside another operating system - so its isolation, memory, and audit guarantees\nare enforced by a layer you control. [Yuva](what-is-yuva.md) is Cogitave's.\n\n## Tamper-evident evidence chain / Merkle history tree\n\nDiyar's evidence model: each reading is hash-chained to the one before it, and\na per-session Merkle history tree is layered on top of that chain to give\ninclusion and consistency proofs in O(log n) instead of requiring every prior\nreading to prove one exists. The tree is what catches a retroactive edit\nbetween two published roots, which a sequential chain alone cannot see.\n\n## Tool\n\nA capability with typed input and output that an agent may invoke. Typed on both\nsides: the kernel validates input before a handler runs, so a handler only ever\nsees well-formed arguments.\n\n## Unit\n\nThe smallest piece of [training](/training/) - one page, a few minutes. Some units\nare prose, some are exercises, and some are knowledge checks.\n\n## Verdict engine\n\nThe pluggable pass/fail rule behind Diyar's `VerdictEngine` port. A **product\nengine**, like `solution-ispm15`, wraps one frozen, certified regulatory rule;\na **generic engine** (`telemetry-only`, `threshold-hold`, and others) is a\ncertified, parameterized function block that many solutions can reuse as pure\ndata, with no new code. Only an engine listed in the firmware-compiled\n`CERTIFIED_ENGINES` registry may be named by a signed device profile - signing\na profile is deliberately not enough to introduce a new rule.\n\n## Yuva\n\nCogitave's sovereign unikernel - see [What Yuva is](what-is-yuva.md). Where\n\"Sovereign unikernel\" above names the concept, Yuva is the concrete `no_std`\nRust implementation; today its live inference is MOCK and learning is DORMANT,\nreported honestly rather than implied.\n\n## Next steps\n\n- [What Namzu is](what-is-namzu.md)\n- [What Yuva is](what-is-yuva.md)\n- [Agent identity and capabilities](agent-identity-and-capabilities.md)\n",
  "lastReviewed": "2026-07-26",
  "order": 2
}