RESOURCES · GLOSSARY
Operating terminology for agentic runtime, deterministic state, assurance infrastructure, intelligence, evidence, verification, compilation, recovery and Network-Centric Operations.
OVERVIEW
The glossary is not a list of slogans. Each definition states what the term means inside the Mediator architecture, what responsibility it carries and, where confusion is likely, what it does not mean.
The software environment that keeps an agentic actor operational across sessions and model changes. It separates persistent identity, authority, runtime state, memory, tools, supervision and model cognition so replacing the model does not silently replace the actor or expand its jurisdiction.
The explicit limit on what a system, agent, operator or integration is permitted to decide or execute. An authority boundary can include jurisdiction, credentials, target scope, approval requirements, financial limits and escalation rules; technical capability does not expand that boundary by itself.
An engine whose declared output can be reproduced from the same canonical inputs, versioned rules, build and explicit time basis. DSE systems fail closed on required truth that is missing or contradictory instead of inventing a persuasive state. “Daisy” is the short internal pronunciation for the DSE family, not a separate product.
The telecommunications DSE implementation for activation readiness, attach, porting, device and provisioning integrity. AIE turns fragmented carrier events into deterministic operating state, correction queues and NOC-facing workflows while preserving the distinction between source events and projected activation state.
The financial and evidentiary DSE lane for transaction, account, obligation and reconciled business state. Its purpose is to keep canonical financial calculation inside one engine boundary so dashboards and downstream products do not evolve competing versions of financial truth.
A coordinated operating model in which connected people and systems share governed information, awareness and capability to act effectively across distributed conditions. In the Mediator security architecture, NCO describes how bounded security, evidence, intelligence and command surfaces can operate together; it is not a standalone sibling product and it does not erase the authority of the participating systems.
Systems that preserve the evidence needed to inspect what happened across execution, transformation, recovery and release. Assurance infrastructure can include receipts, provenance, manifests, cryptographic checks, custody state, recovery evidence and independent verification, but it does not turn every technical record into a legal or factual conclusion.
A structured record of a declared event, action or transition, normally carrying actor, subject, time, operation and relevant identity or content references. A receipt supports reconstruction and accountability; it should be read as evidence of recorded system state, not as magical proof that every upstream assertion was true.
The attributable lineage of an observation, artifact, transformation or release: where it came from, which system handled it, what changed and how the current object relates to prior states. Good provenance lets a reviewer distinguish original source, derived material and final release instead of flattening them into one file.
The documented history of possession, transfer, handling and control for evidence or a governed artifact. Custody complements provenance: provenance explains lineage and transformation, while custody emphasizes who or what controlled the item and when.
A declared inventory of the artifacts, versions, identifiers and checks that constitute a packet or release. A manifest makes the release universe explicit so an independent verifier can detect missing, substituted or unexpected material.
A governed transformation system that converts approved inputs into validated release-ready outputs such as websites, documents, packets, reports or software artifacts. Compiler-style operation separates input authority, transformation logic, validation and release evidence so the final artifact can be reconstructed from its declared build state.
The reconstruction of prior or current state from authoritative inputs, versioned configuration and an explicit time basis. Replay is valuable because it tests whether a result follows from the declared state rather than from hidden mutable context.
A non-action state used when required truth, approval or consistency is missing. HOLD is not a low-confidence guess; it is an explicit refusal to manufacture state when the engine cannot satisfy its decision contract.
Source truth is the observed or authoritative input as received from its governing source. Derived intelligence is interpretation, ranking, correlation or projection built from that material. Mediator keeps the two distinguishable so a useful inference does not retroactively rewrite the source.
Inspection of supported properties without needing the originating system’s private execution authority. The verifier should be able to reproduce relevant checks and state the limits of verification, including which questions remain semantic, legal or evidentiary rather than purely technical.