An instrument for LLM internal state

Separate what was measured from what was claimed.

NVS-Kernel is an instrument. It measures the internal state of an LLM and keeps the measurements as a hash-chained record that shows tampering, separate from any interpretation of them. It does not control generation.

What is NVS

NVS Technology

From LLM to verified record
LLM Generates text. Not controlled by NVS-Kernel. Internal state The hidden-state trajectory, token by token. Edge (measurement) Measures the state; designed to run in your environment. Hash-chained record Quantized board record, hash-chained to the previous one. CDM (verification) CoreDecisionMaker: verifies records in the cloud.

1. Summary

NVS-Kernel is an instrument. It measures an LLM's internal state — the trajectory that the hidden state traces, token by token — and records it. It does not control generation. Whether to stop is decided by the user's policy; the default is display only.

2. What is NVS

NVS is provided by Koto Metric. The commercial part of it is NVS-Kernel, which measures the trajectory of an LLM's hidden state and records the measurements.

What is deterministic is the measurement, not the LLM's generation. Each measurement is stored as a quantized board record. Each record is hash-chained to the previous one.

"NVS-Kernel is an instrument: it measures and records. It does not control generation."

3. What NVS-Kernel Does

  • Measures, does not decide: It follows the hidden-state trajectory and records it. Whether generation is stopped is up to the user's policy (default: display only).
  • Measurement and verification are separate: Edge measures. CDM (CoreDecisionMaker) verifies the records in the cloud.
  • Reproducibility, confirmed: For the same input in the same environment, the record was byte-for-byte identical. On a different CPU (Mac arm64 and cloud x86_64), results matched within tolerance, compared over about 7.85 million values. A byte-level match applies only within the same environment.
  • Tamper-evident record chain (implemented): Each record is hash-chained to the previous one. The chain shows a one-byte rewrite, a missing record, or reordered records.

4. Data Boundary (by design)

The data boundary is a design. Edge runs in your environment. Prompts, generated text, and internal states are designed to stay there. Edge sends two things to the cloud: the quantized board records and an API key. We have not investigated how much of the original content a record could reveal.

What NVS-Kernel records

  • The trajectory of the LLM's hidden state, token by token
  • A 42-cell board record: 38 Core measurements plus four information cells (format, calibration, summary, check)
  • A hash chain: each record links to the previous record
  • A tamper-evident chain: it shows rewritten, missing, or reordered records

Measured, claimed, checked

Implemented

Observation — what was measured

For each token, NVS-Kernel measures the LLM's hidden state, stores the reading as a quantized record, and chains that record by hash to the previous one. A rewritten byte, a missing record, or reordered records are detected. An observation record is not rewritten when its interpretation changes.

Designed

Interpretation — what it was taken to mean

NVS-Kernel is designed to record interpretations, whether given by a model, a person or a checker, separately from the observation. It is designed to keep apart who gave each interpretation and how far it has been checked.

Designed

Evidence — what it rests on

Definitions and recalculation results are designed to be sealed so that they can be referenced. A valid seal and mathematically correct evidence are different things: the seal will not show that the evidence is correct.

Designed

Structure check — is the claimed chain consistent

NVS-Kernel is designed to check whether the history of a change of representation is structurally consistent. It will be a check of structure, not a judgement of whether a claim is true.

What a pass means. A passing check means the record or contract passed the defined checks. It does not prove that an interpretation or a mathematical claim is correct. The service gives traceability — what was proposed, adopted or rejected, on what basis — not a causal explanation.

Limits we state. Until signed receipts exist, whoever holds the session key could build a different, self-consistent chain, and a third party could not tell from the records alone. Signed receipts are planned. The contract that declares where a capture came from is a self-declaration: the hash chain shows consistency, not that the declaration is true. It does not cover anything changed before the Edge captured the state.

How NVS-Kernel Works

How NVS-Kernel works

01

Core/Port Execution Isolation

Each of the 38 Cores is observed through its own independent port. For each token, one measurement cycle computes the 38 Core measurements. NVS-Kernel only measures and records; it does not control generation.

02

Deterministic Measurement

The measurement is deterministic: the same input in the same environment gave a byte-for-byte identical record (confirmed). The LLM's own generation is not deterministic, and NVS-Kernel does not control it.

03

Tamper-Evident Trajectory Log

Each record is hash-chained to the previous one, so the chain shows a rewritten byte, a missing record, or a reordered record.