Section I
Category Boundary
These terms define Sovrient's top-level category and the boundary that keeps evidence infrastructure separate from legal, procurement, certification, and review authority.
Machine-Verifiable Evidence Infrastructure (MVEI)
An infrastructure layer that captures, structures, hashes, and bounds evidence at or near the time activity occurs, so later reviewers can reconstruct what happened, what supports a claim, what changed, and what remains unsupported.
Used in: Capabilities
Machine-Verifiable, Not Machine-Authorized
Machine-verifiable does not mean machine-authorized. A machine can help verify hashes, custody, replay paths, missing inputs, drift, and supportability states, but it does not grant compliance, certification, legal sufficiency, mission readiness, or procurement approval.
Used in: Capabilities
Evidence Layer
The layer that converts activity records into bounded evidence states: source custody, manifests, receipts, supportability states, non-claims, blocked claims, and replay conditions. Sovrient operates here.
Used in: Capabilities
Authority Layer
The layer where auditors, IV&V teams, contracting officers, certifying authorities, review boards, regulators, and counsel decide acceptance, certification, compliance, legal sufficiency, or mission readiness.
Used in: Capabilities
Activity Layer
The systems and workflows that generate events or outputs: Git, Jira, LMS, telemetry, AIS, documents, AI agents, simulations, sensors, and operational workflows.
Used in: Capabilities
Evidence Before Opinion
The operating principle that an organization should establish the evidence state before establishing conclusions. Sovrient's posture is event, evidence, verification, then decision.
Used in: Prime Contractor One-Pager
Section II
Evidence States
These terms describe what a claim can safely inherit from its evidence packet. They prevent dashboards, summaries, or AI outputs from quietly saying more than the source artifacts support.
Source-Bound Evidence
A claim state where the source material, retrieval context, hashes, and interpretive boundary are linked tightly enough for a reviewer to inspect what supports the claim.
Used in: Capabilities
Evidence Curation
The process of turning source material into claim-bounded evidence by preserving provenance, custody, replay conditions, supportability state, and explicit non-claims. Evidence curation is data curation plus claim discipline: it does not stop at organizing information; it governs what the information can safely be used to assert. Data curation makes information usable; evidence curation makes reliance inspectable.
Used in: Capabilities
Source Receipt
A record of what was retrieved, when it was retrieved, where it came from, and which digest or sidecar binds the source bytes.
Used in: Verification
Evidence Packet
A bounded bundle of sources, manifests, receipts, normalized outputs, release state, and non-claims for one reviewable question or lane.
Used in: Procurement Packet
Bounded Evidence Record
A scoped record of what was tested, what happened, what the result means, what it does not mean, and which supporting artifacts are included or hash-bound.
Used in: Home
Canonical Manifest
The declared inventory of files, hashes, roles, and relationships in an evidence packet. It tells a reviewer what belongs in scope and what should hash-match.
Used in: Evidence Architecture
Sealed Manifest
A manifest whose own contents have been hashed or signed so later changes are visible. A sealed manifest supports custody, not truth by itself.
Used in: Sealed Catalog
Sealed Catalog
The public catalog of sealed evidence artifacts and their verification metadata. It is an inspection surface, not a dashboard-only trust claim.
Used in: Sealed Catalog
Sidecar
A small companion file, often a hash or receipt, attached to a larger artifact. Sidecars make changes, omissions, and mismatches easier to detect.
Used in: Verification
Anchor
A public reference, transaction, witness, or hash handle that helps locate or verify a published evidence state. An anchor helps preserve a record; it does not prove the underlying claim is true.
Used in: Anchors
Machine State
A compact machine-readable state file for agents and reviewers. It helps software locate current evidence posture, but the underlying artifacts remain the source of truth.
Used in: Machine State
Replay
Running the declared verification path again from the declared inputs to see whether the published state can be reproduced.
Used in: Replay a Receipt
Replayability
The property that a declared evidence or computation path can be rerun from declared inputs and compared against published outputs. Replayability supports inspection; it is not universal truth.
Used in: Start Here
Re-Pull
Retrieving a source again from its public or authorized location to compare current source state against the captured source state.
Used in: Verification
Drift
A detected change between a prior sealed state and a later source, artifact, or derived output. Drift is not automatically bad; it must be named and handled.
Used in: Verification
Supported
The evidence packet carries enough source-bound support for the bounded claim as written. It does not authorize broader claims outside that wording.
Used in: Regulatory Claim Control
Admissibility
Sovrient's public-surface shorthand for whether a claim or artifact passes declared evidence gates. It is not courtroom admissibility doctrine unless a separate legal process says so.
Used in: Verification
Partial / Partially Supported
The packet supports part of the claim, a narrower version of the claim, or the mechanism but not full coverage. Partial is a boundary, not a failure.
Used in: Regulatory Claim Control
Needs Review
The machine-readable packet cannot safely decide the claim state alone. A reviewer must inspect context, authority, or judgment-bearing facts before the claim moves.
Used in: Prime Contractor One-Pager
Blocked Claim
A claim the system explicitly prevents from being asserted because the evidence does not support it, conflicts with it, or leaves a necessary condition unresolved.
Used in: Training Evidence Wrapper
Out Of Scope
A question or assertion outside the declared packet boundary. Out-of-scope claims may be valid elsewhere, but this packet does not establish them.
Used in: Teaming Brief
Human Disposition
A reviewer-applied state such as accept, hold, reject, escalate, or revise. Sovrient can preserve the disposition record without replacing the human authority that made it.
Used in: Governance Reconstruction
Source-Cited, Capture Pending
A source is cited or visible, but the source bytes have not yet been captured, saved, hashed, and bound into the custody manifest.
Used in: Verification
Partially Source-Bound
Some sources in a packet are captured and bound while others remain blocked, pending, unavailable, or attested-only. The packet must not be called fully source-bound.
Used in: Verification
Browser-Render Confirmed
A human or browser-render pass visibly confirmed support, but the rendered source text or file has not necessarily been captured and hashed. It is stronger than a bare citation, weaker than source-bound custody.
Used in: Verification
Tamper-Evident Receipt
A receipt that makes later alteration visible through hashes, signatures, manifests, or witnessed state. Tamper-evident does not mean independently certified unless that verification is separately earned.
Used in: Evidence Architecture
Section III
Claim Governance
These terms define how Sovrient keeps uncertainty visible instead of hiding it inside a score, paragraph, or generated narrative.
Claim Boundary
The exact edge of what the evidence permits a party to say. A claim boundary separates supported language from wording that still needs review, authority, or additional evidence.
Used in: Capabilities
Structured Uncertainty
A state where unknowns are named, typed, and routed instead of being hidden behind confidence language. Structured uncertainty makes a system safer because it can say what it does not know.
Used in: Doctrine Alignment
Representational Ambiguity Cost (RAC)
The expected cost of being unable to reconstruct, attribute, bound, or defend a claim or decision later. RAC is workflow-specific and should be derived from the buyer's own challenge probabilities and defense costs.
Used in: Prime Contractor One-Pager
NERV
Net Expected Risk Value: a deterministic decision score computed from declared risk, loss, and verification-cost inputs under fixed ordering and rounding rules. RAC is one way to describe a loss surface that evidence controls can reduce.
Used in: Governance Reconstruction
NERV Release Evidence Bundle
A bounded package of release evidence, policy criteria, manifests, receipts, and verdict state. On the federal surface, NERV refers to this release-bundle pattern.
Used in: Federal AI Evidence
SSEJ
Saw, Selected, Excluded, Justified: the minimum reconstruction record for a reviewable decision. It records what was considered, what was used, what was left out, and why.
Used in: Governance Reconstruction
PCBA
Persona Consortium Based Analysis: a structured adversarial review method for testing whether claims hold across reviewer roles and objection paths.
Used in: Federal AI Evidence
MAS
Sovrient's governed memory runtime and replayable path-validity engine. MAS handles admissibility, path selection, contradiction handling, and fail-closed emission over declared state.
Used in: Governance Reconstruction
Governance Seed
A bounded early-stage publication artifact proving source possession, manifest discipline, and replay posture without claiming full production maturity.
Used in: Governance Reconstruction
Cross-Domain
Reuse of the same evidence-governance method on a different operational surface. Cross-domain reuse transfers the discipline, not the original domain's authority or conclusions.
Used in: Home
Section IV
Capture, Prime, And Training Fit
These terms help GovCon and prime teams read Sovrient as an evidence-bound layer around capture, teaming, training, and proposal language, not as a replacement for the prime's role.
Pursuit Signal Interrogation (PSI)
A pursuit-intelligence method that asks what a notice, forecast, RFI, recompete signal, or market source actually supports before capture resources or customer-facing claims harden.
Used in: Regulatory Claim Control
Regulatory Claim Control
A source-bound evidence layer that separates supported, partial, blocked, stale, missing, and review-required claims before teaming, proposal, or recompete language becomes customer-visible.
Used in: Capabilities
Training Evidence Wrapper
A separation-of-duties evidence layer around LMS, simulation, or course delivery records. It preserves what the authoritative training system asserted, under which course version or rubric, and what stronger claims remain unsupported.
Used in: Capabilities
Completion Assertion
A record that a source system asserted a learner, cohort, or module reached a completion state. Sovrient binds the assertion and its source context; it does not automatically prove mastery or program effectiveness.
Used in: Prime Contractor One-Pager
Rubric / Version Reference
The curriculum, scoring rubric, or evaluation version tied to a training record. Binding the reference proves which version was applied, not that the version was government-approved.
Used in: Training Evidence Wrapper
Separation Of Duties
A control pattern where the same platform that generates or delivers an output is not the only party preserving evidence about that output.
Used in: Prime Contractor One-Pager
Recompete Indicator
A source signal suggesting a requirement may follow, replace, continue, or re-open prior work. It is not proof of a confirmed recompete unless predecessor contract, incumbent, or award-path evidence is bound.
Used in: Regulatory Claim Control
Incumbent Binding
The act of tying a current or prior contractor claim to official award, transaction, notice, or agency source evidence. Without binding, incumbent language stays inferred or blocked.
Used in: Teaming Brief
Partner Path
A posture where Sovrient can support a requirement only through a prime, teammate, integrator, or domain partner because part of the buyer need sits outside Sovrient's direct lane.
Used in: Prime Contractor One-Pager
Section V
AI And Evidence Architecture
These terms explain the architecture layer: the source, model, evidence, authority, and maintenance surfaces that make a claim inspectable over time.
Operational Substrate
The actual system, workflow, dataset, model, human review, or source environment from which an evidence claim arises.
Used in: Evidence Architecture
Append-Only Maintenance
A maintenance posture where later updates add new state or correction records instead of silently rewriting prior evidence state.
Used in: Evidence Architecture
External Verification
Verification by a party, procedure, or artifact surface outside the original claim author. It must be earned through inspectable evidence, not asserted by label.
Used in: Evidence Architecture
AIBOM
AI bill of materials: an inventory of AI, data, model, component, dependency, and lineage elements relevant to a scoped release or review boundary.
Used in: Federal AI Evidence
AUTH-REF
Authority-bound reference register. Authority-bound means the referenced source bytes are bound and checked; it does not mean the artifact replaces the authority.
Used in: Federal AI Evidence
Anatop
Agent-Native Topology: Sovrient's method for turning documents, measurements, and decision structures into deterministic, sealed, bounded machine surfaces that agents can use without hidden interpretation steps.
Used in: Federal AI Evidence
TEVV
Testing, evaluation, validation, and verification artifacts tied to a release, model, requirement, or decision boundary.
Used in: Federal AI Evidence
Evidence-Path Reconstruction
Sovrient's practice of reconstructing why a machine-supported workflow landed where it did in evidentiary terms: what it saw, what it selected, what it excluded, and what it carried forward.
Used in: Governance Reconstruction
Maritime AIS Governance Surface
A published lane applying Sovrient's evidence discipline to authoritative open U.S. coastal AIS data. The lane demonstrates manifest discipline and bounded non-claims around public maritime evidence.
Used in: Maritime AIS Dashboard
Section VI
Replay, Cryptographic, And Deterministic Controls
These are the older core verification terms that still underwrite the newer GovCon, training, AI, maritime, and source-custody surfaces.
Deterministic Replay
Re-executing a declared computation path from declared inputs to reproduce the same outputs byte-for-byte. Determinism is the minimum technical bar for independent verification.
Used in: Start Here
Fail-Closed
A control posture where missing, stale, malformed, or mismatched verification artifacts block publication or stronger claims. The system does not downgrade requirements silently when verification fails.
Used in: VOSINT post
Fail-Closed Gate
A specific release or workflow gate that stops promotion when required evidence is missing, stale, malformed, or mismatched.
Used in: Federal AI Evidence
Attestation Context
The declared set of inputs, transforms, hashes, signatures, and witness metadata that makes a claim replayable. Context links narrative statements to verifiable artifacts.
Used in: FONDEN post
Non-Repudiation
Cryptographic evidence that a signed state existed at a declared time and cannot be plausibly denied later. Detached signatures and witness roots are typical mechanisms.
Used in: VOSINT post
Merkle Seal
A root hash committing a set of artifact hashes under deterministic ordering and node rules. It allows inclusion verification without transferring the entire artifact set.
Used in: Verification
GPG Signature
A detached cryptographic signature binding a specific file hash to a signing key. Signature verification confirms authenticity and integrity of published artifacts.
Used in: Verification
DMSS
Deterministic Multi-Source Settlement Standard: a control framework where critical measurements require multi-source corroboration, deterministic replay, and sealed evidence before admissible publication.
Used in: Start Here
DT0
Delta tau equals zero: a strict determinism profile requiring zero unresolved computational variance under declared scope. DT0-compliant runs are either reproducible or fail-closed.
Used in: Verification
DAROC
Deterministic Acquisition, Reconciliation, and Operational Cryptoseal: an execution pattern where acquisition, reconciliation, and cryptographic sealing are bound into one replayable claim chain.
Used in: Protocol
VOSINT
Verifiable Open-Source Intelligence. Public-source inputs are upgraded to evidentiary quality by verification, replayability, and witnessed non-repudiation.
Used in: VOSINT Framework
Section VII
Legacy Catastrophe And Settlement Terms
These terms remain for older public pages and posts that introduced Sovrient's replay-governance vocabulary through catastrophe, seismic, and settlement examples.
Parametric Trigger
A predefined condition that determines eligibility in a parametric structure without case-by-case loss adjustment. It depends on declared measurements, thresholds, and policy logic.
Used in: FONDEN post
Pre-Catalog Parameter
An event parameter captured before later scientific normalization cycles. It is suited for deterministic trigger-state replay when provenance and timing are explicitly sealed.
Used in: Pre-catalog post
Catalog Parameter
A refined event parameter published in a curated catalog that may change over time. Catalog quality can improve while introducing revision-handling requirements in trigger governance.
Used in: Pre-catalog post
Oracle Risk
The risk that settlement-critical state cannot be independently reproduced under declared scope. Oracle risk rises when systems depend on mutable single-source values without replay controls.
Used in: FONDEN post
Trigger Dispute Surface
The set of ambiguities counterparties may contest when evaluating trigger outcomes. Deterministic replay and sealed evidence reduce this surface.
Used in: FONDEN post
Provider Drift
Divergence between providers over time in reported event parameters or derived indicators. Drift requires explicit policy handling to avoid implicit trigger inconsistency.
Used in: Market drift lane
Glossary definitions are public orientation language. They are not legal advice, machine authorization, eligibility determinations, ATO readiness, CMMC assessment, standards certification, customer ROI proof, or proof that unlisted terms or artifacts do not exist.