METRAXIOM PRODUCT
METRAXIOM connects measurement work, method authority, reference standards, uncertainty, decision rules, review, operations and proof without collapsing their different meanings into one status. The interface can expose the mechanism; the authority model remains explicit underneath it.
Four entry points. The same underlying discipline: make the evidence and limitations visible.
Each row names the owned objects, current posture and inspection path. The rail connects the product visually without implying that every relationship is a computational dependency.
Public Studio experiences are available. Private production workspaces, paid enrollment, external AI, live acquisition, and authoritative release remain separate gates whose status is published. Review current status →
Calibration job · retained context · worksheet session · point · observation · intervention
Guide the technician from preflight through as-found, intervention, as-left, technical completion, review, and package without overwriting historical evidence.
Procedure · immutable revision · applicability · runtime step · specification · calculation model
Resolve the exact controlled method before acquisition, bind it to the work, and fail closed when the authority seen by the operator becomes stale.
Reference standard · source certificate · range/function capability · support role · intermediate check
Keep the DUT specification, reference physical identity, calibration evidence, intended target, accepted reference value, and DUT indication as separate facts.
Uncertainty budget · component · correlation · specification · acceptance interval · decision rule
Separate measurement uncertainty from tolerance and conformity logic. Show why a result is PASS, REVIEW, FAIL, or indeterminate instead of hiding the rule.
Review · signature · exception · contest · correction · OOT · impact · recall
Make disagreement, missing evidence, nonconforming work, supersession, and downstream impact first-class workflow objects rather than comments or disappearing alerts.
Manifest · certificate projection · label · DCC profile · evidence package · verification result
Generate customer-facing and machine-readable outputs from the same retained evidence set, preserving issue, amendment, supersession, and verification lineage.
Calibration program · interval basis · due anchor · work order · customer · custody · delivery
Connect recall, scheduling, receiving, assignment, standards, turnaround, certificate delivery, and history without pretending to be every ERP or QMS function.
API · webhook · Device Bridge · reference discovery · Ask METRAXIOM · external agent
Use enterprise connections, live acquisition, search, and AI under typed scopes. External services remain outside the canonical authority boundary.
As a worksheet changes, METRAXIOM reads its existing readiness checks in reverse: the next open identity, configuration, basis, observation, or evaluation is named against the saved revision. A Proof Passport carries the stage findings and declared record counts to the exact work-package output.
A separate read-only lens traces which retained records depend on a selected source, without fabricating a defect or changing a historical result.
The public path never independently verifies an entered reading, approves a method, or issues a certificate. Decision X-Ray and AFTERSHOCK remain distinct sample demonstrations.
Build and inspect the proof path →The technician sees the next material task. The system retains the complete authority and evidence context so another qualified person can reconstruct what happened later.
Resolve physical identity, measurement system, retained context, assignment, competency, procedure, specification, references, environment, and safety.
Define functions, ranges, channels, points, repetitions, direction, dwell, stability, required support equipment, and acquisition mode.
Append raw DUT, reference, and environmental observations with unit, resolution, timestamp, actor, device, source, and quality state.
Apply deterministic corrections, unit conversions, uncertainty, specification expressions, acceptance boundaries, and decision rules.
Record adjustment, repair, cleaning, configuration, or part change and create a successor session without rewriting as-found evidence.
Present unresolved evidence, contradictions, OOT impact, audit lineage, signatures, and exact release blockers against the candidate digest.
Issue the authorized projection and proof package; retain dependency paths so later changes can trigger deterministic impact review.
METRAXIOM does not make a pressure worksheet “universal” by renaming pressure fields. Every controlled discipline must declare its own context, unit set, standards, point planning, corrections, uncertainty, specification forms, safety controls, and golden tests.
Simplified reports may hide working detail from the customer view, but they never license destruction or mutation of the underlying technical record.
The contemporaneous manual, connected, imported, API, calculated, or migrated fact. It is never deleted merely to improve an outcome.
A versioned deterministic transformation with explicit inputs, units, equations, constants, and calculation identity.
The reference composer exposes component assumptions and blocks declared correlation. Controlled-engine support and release authority remain separately qualified.
Specification, acceptance boundary, rule, result, reason code, and authority are separate objects.
Human responsibility binds the exact record digest. A changed record makes the prior approval stale.
The inclusion set, hashes, lineage, limitations, open disputes, recall state, build identity, and verifier profile are retained.
Role Lens changes the order and density of what each person sees. The underlying instrument, source, readings, uncertainty, rule, history, fingerprint, and release state do not change with the viewer.
The technician lens leads with the instrument, procedure step, point sequence, required observations, and the exact reason point 4 was routed to review.
The current commercial architecture is a hosted Next.js, Supabase, and Vercel application. Local Professional and Air-Gapped editions remain planned until identity, installation, key custody, backup, update, support, offline verification, and validation controls are independently built and tested.
CMMS, EAM, QMS, LIMS, ERP, API, webhook, Device Bridge, and external-agent paths are versioned and independently permissioned. No connected system gains silent measurement or release authority.
Public Studio experiences are available. Private production workspaces, paid enrollment, external AI, live acquisition, and authoritative release remain separate gates whose status is published.
Review current status →AI suggestions are not facts. Retrieval is not evidence. A live value is not released authority. A valid hash is not proof of truth. A due date requires an approved interval basis. A subscription cannot create competence. A review is not release. A released record cannot be silently rewritten.