Measurement Rsnative Core Measurement

The measurement record

A measurement is an act of writing something down: a number, a window of time, a note about how the number was obtained, and an honest statement of how sure you are. In Recognition Science, this act is captured by a single formal structure called Measurement, which is a discrete record of events. The structure bundles four pieces of information. The first is the value itself, which can be any real number or more complex object. The second is a window, a span of time measured in ticks, where a tick is the framework's basic unit of time and a window of length zero means an instantaneous reading. The third is a protocol, a named procedure that says what was measured and under what assumptions. The fourth is an uncertainty, either a standard deviation or an interval with a confidence level, plus optional notes.

The design goal is that every measurement carries its own receipt. In ordinary physics, a measurement is often just a number with an error bar, and the choices behind it, such as how you windowed the data or what basis you used, live in the methods section of a report. Recognition Science wants those choices to be part of the measurement object itself, so they cannot be forgotten or hidden. The framework defines a protocol as hygienic when it has a nonempty name, and when its status is hypothesis or scaffold it must list both its assumptions and its falsifiers, the specific observations that would refute it. A measurement with a hypothesis status but no falsifier is not a well-formed measurement in this system.

This is a definitional scaffold, not a physical law. The structure does not say what the value should be, only how a value must be packaged. It is a machine-checked collection of formal theorems, a library, that lets the framework build observables, which are functions from a system state to a measurement. The library also defines the native units of the framework: ticks, voxels, coherence, action, cost, skew, meaning, and qualia, each as its own unit type so that adding a tick to a cost is a type error. The core file is deliberately small and dependency-light; concrete observables live elsewhere, and calibration against SI units is an optional layer that sits outside the core.

What the declaration does not claim is as important as what it does. It does not claim that any particular measurement is correct, that the framework's native units match any physical unit, or that the protocol structure guarantees truth. It only guarantees that a measurement is recorded in a uniform, auditable shape. A measurement can be perfectly well-formed and completely wrong. The structure is a contract about bookkeeping, not a claim about the world. That is the point: before you can argue about what reality is, you need a way to write down what you observed that does not let you quietly change the rules later.

/-- A measurement value with protocol + (optional) time window + (optional) uncertainty. -/
structure Measurement (α : Type) where
  value : α
  window : Option Window := none
  protocol : Protocol
  uncertainty : Option Uncertainty := none
  notes : List String := []

/-- A measurement value with protocol + (optional) time window + (optional) uncertainty. -/
structure Measurement (α : Type) where
  value : α
  window : Option Window := none
  protocol : Protocol
  uncertainty : Option Uncertainty := none
  notes : List String := []

/-- Protocol hygiene predicate (v1/v2).

Rules:
- `name` must be non-empty
- if `status` is `.hypothesis` or `.scaffold`, both `assumptions` and `falsifiers` must be non-empty -/
def hygienic (p : Protocol) : Prop :=
  p.name ≠ "" ∧
    match p.status with
    | .hypothesis | .scaffold => p.assumptions ≠ [] ∧ p.falsifiers ≠ []
    | _ => True

inductive TickUnit : Type

What this page does not claim

No claim that any particular measurement value is correct. No claim that the framework's native units correspond to any physical unit. No claim that a well-formed measurement guarantees truth.

Verify this page

Every tagged claim above names its theorem. To check one yourself rather than trust this page, elaborate the source module with Lean 4 and audit its axiom basis:

$ lake env lean IndisputableMonolith/Measurement/RSNative/Core.lean
expected axiom basis: [propext, Classical.choice, Quot.sound] (the Lean kernel's standard three; no RS-specific axioms)

A page whose claims cannot be reproduced this way does not ship. In production, every anchor links to the exact declaration in the public source release, and this block carries the build receipt for the page itself.

Derived articles

This page is generated by a question-recursion engine: the questions its answers raise become the next pages. The current agenda, with open targets marked red: