DOCUMENTATION · v5 CONSTRUCTION CONTROL

Start with the work. Open the deeper architecture when the task requires it.

METRAXIOM documentation follows technician, reviewer, metrology, quality, administration, and integration tasks while preserving the exact objects, states, reason codes, and control boundaries beneath them.

THE COMMON CONTROLLED WORKFLOW

Eight movements from physical identity to reconstructable proof.

Discipline modules add scientifically specific context, but they do not replace the common evidence, authority, review, and release model.

1 · IdentifySelect the controlled physical instrument and exact measurement system, function, channel, range, configuration, and lifecycle state.
2 · Establish authorityResolve the retained context, approved procedure, applicable specification, decision rule, required competency, standards, environment, and safety conditions.
3 · PlanDefine points, repetitions, direction, dwell, stability, support equipment, connected/manual acquisition, and required evidence.
4 · AcquireAppend raw DUT, reference, and environment observations with unit, timestamp, actor, device, source, and quality state.
5 · EvaluateRun deterministic corrections, conversions, uncertainty, specification, acceptance-boundary, and decision-rule logic under exact versions.
6 · Intervene and verifyRecord adjustment, repair, cleaning, configuration, or part changes, then create successor as-left evidence without overwriting as-found.
7 · Review and releaseResolve exceptions and OOT impact, bind approvals to the exact digest, and keep technical review separate from authorized release.
8 · Package and preserveGenerate certificate/DCC projections, manifest, audit lineage, dependency paths, verification instructions, and future recall capability.
VERSIONED DOCUMENT INDEX

Search current guidance locally.

Portal 2026.10 · reviewed 2026-10-06. Search runs only in this browser tab; the query is not retained.

9 current documentation entries.

Common controlled workflowType: guide · Version: v6.1 calibration execution · v5.0 web control
Owner: Product & Metrology · Last review: 2026-10-06 · Status: current
Eight movements from physical identity and method authority through acquisition, evaluation, review, release, and preservation.
Universal Calibration BuilderType: guide · Version: v6.1 public evaluation
Owner: Metrology Engineering · Last review: 2026-10-06 · Status: current
Public worksheet guidance for quantity, unit, range, points, uncertainty, decisions, environment, and condition lineage.
Metrology WorkstationType: reference · Version: v5.0 public reference surface
Owner: Metrology Engineering · Last review: 2026-10-06 · Status: current
Reference-only repeated-reading, conversion, comparison, uncertainty, resolution, and decision calculations.
Measurement methodologyType: reference · Version: v6.1 architecture / current public methodology
Owner: Metrology & Quality · Last review: 2026-10-06 · Status: current
Deterministic measurement, uncertainty, decision, evidence, and authority methodology used by public demonstrations.
System architectureType: architecture · Version: v5.0 web control / v6.1 calibration architecture
Owner: Architecture · Last review: 2026-10-06 · Status: current
Measurement-decision chain, assurance kernel, reconstruction, consequence, evidence, and authority boundaries.
Proof ModeType: guide · Version: public proof profile v3
Owner: Decision Engine · Last review: 2026-10-06 · Status: current
Bounded deterministic public proof with explicit inputs, rule, engine version, witness, envelope, and non-authority notice.
Public Evaluation API v1Type: api · Version: Public Evaluation API 1.0.0
Owner: Platform Engineering · Last review: 2026-10-06 · Status: current
Versioned contract for bounded public evaluation endpoints.
Trust CenterType: trust · Version: current public trust posture
Owner: Security & Quality · Last review: 2026-10-06 · Status: current
Current control and assurance posture with explicit evidence boundaries.
AFTERSHOCK standalone integrity verifierType: reference · Version: AFTERSHOCK portable impact package v1
Owner: Assurance Engineering · Last review: 2026-10-06 · Status: current
Zero-application-import reference verifier for portable-package canonicalization and SHA-256 integrity. It does not establish issuer identity, independent trust, or recall/release authority.
BY RESPONSIBILITY

The same canonical record supports different work queues.

Role lenses change priority and density. They do not change evidence meaning or authority.

01

Technician

Start from the physical instrument and assigned work. Resolve the governing procedure, specification, references, context, and safety conditions before controlled acquisition.

02

Reviewer

Open the immutable candidate, compare as-found and as-left, inspect source and reference provenance, review uncertainty and decision logic, and resolve every blocker against the exact digest.

03

Metrology manager

Control procedures, specifications, reference standards, uncertainty templates, decision rules, calibration programs, interval rationale, and discipline-module validation.

04

Quality leader

Govern nonconforming work, contests, corrections, impact/recall, electronic signatures, release authority, audit, validation, retention, and quality-system links.

05

Administrator / security

Manage tenant roles, MFA, sessions, sites, integrations, feature gates, data routing, billing, retention, incident response, and support access.

06

Developer / architect

Use versioned APIs, schemas, idempotent commands, expected-version controls, webhook verification, proof profiles, reason codes, and compatibility records.

DOCUMENTATION COLLECTIONS

Version, status, owner, and limitation travel with the guidance.

Documentation cannot describe a gated or planned function as operational merely because its architecture exists. Detailed pages are published as the implementation and acceptance evidence become available.

Get startedContents: Workspace and site setup, first instrument, controlled source, reference standard, first job, technical completion, review, and package.
Current status: Current public overview; detailed signed-in guides expand with the v5 workspace.
Technician guidesContents: Preflight, point planning, acquisition, procedure steps, environment, interventions, as-left, errors, connected devices, and offline behavior.
Current status: Pressure path implemented; multi-discipline controlled guides gated by lane validation.
Metrology guidesContents: Specification expressions, units, range/resolution, corrections, uncertainty, decision rules, reference qualification, and discipline modules.
Current status: Public reference content exists; controlled authoring continues to expand.
Quality guidesContents: Review, signatures, OOT/nonconforming work, contest, correction, dependency impact, recall, amendments, audit, retention, and release.
Current status: Architecture adopted; enabled functions identified separately from planned DUEPROOF controls.
Administrator guidesContents: Roles, competency, sites, security, billing, data lifecycle, feature flags, backup/restore, incidents, and support access.
Current status: Current controls documented; production commitments remain scope-specific.
Developer docsContents: Authentication, OpenAPI, scopes, idempotency, versioning, pagination, errors, webhooks, SDK strategy, sandbox, and integration examples.
Current status: The public evaluation API contract is generated and source-reconciled. A versioned external private-workspace API remains gated and is not promised by that public contract.
ArchitectureContents: DUEPROOF kernel, canonical objects, state machines, reliance, gates, contest, correction, recall, proof package, verifier, and deployment profiles.
Current status: v5 construction control adopted; feature implementation status remains explicit.
ReferenceContents: Field dictionary, units, state taxonomy, reason codes, schemas, device compatibility, calculation models, and release profiles.
Current status: Machine-readable registries begin in the v5 branch and expand with each controlled object.
Release notesContents: User-visible changes, migrations, deprecations, security notices, feature-gate changes, and compatibility impacts.
Current status: Public changelog retained; exact build evidence remains release-scoped.
PUBLIC API CONTRACT

A machine-readable contract for the released public evaluation boundary.

The OpenAPI 3.1 document covers selected public status, health, commercial-state, instrument-classification, and deterministic proof endpoints. It deliberately excludes private workspace, controlled-write, billing, organization, team, source-document, and certificate-authority APIs from the supported external contract.

Contract boundary

Publication of this public evaluation contract does not make the signed-in workspace API a supported external integration surface and does not grant measurement, review, release, certificate, accreditation, or traceability authority.

SIGNED-IN WORKSPACE MAP

Current product surfaces share one tenant and authority model.

These are not disconnected applications. The v5 information architecture reorganizes them around durable domain objects while preserving the existing evidence and authorization foundation.

Workspace overview

Role-aware status, foundation readiness, recent evidence, current gates, and next best action.

Private workspace route · /app

Calibration Jobs

Create and resume retained measurement context and controlled work packages.

Private workspace route · /app/calibrations

Procedures

Controlled procedure identity, immutable revisions, scope, and method authority.

Private workspace route · /app/procedures

Instruments

Physical assets and measurement-system identities.

Private workspace route · /app/instruments

Review Queue

Records awaiting governed human review or release action.

Private workspace route · /app/review-queue

Evidence History

Retained calculation, decision, review, release, and supersession records.

Private workspace route · /app/history

Activity Ledger

Append-only material workspace activity.

Private workspace route · /app/activity

Metrology Operations

Calibration programs, interval basis, due anchors, and stability evidence.

Private workspace route · /app/operations

Intelligence Center

Ask METRAXIOM, reference discovery, AI-provider, external-agent, and authority-boundary status.

Private workspace route · /app/integrations

Security

MFA enrollment, session revocation, and high-authority action protection.

Private workspace route · /app/security

Reference tools versus controlled measurement

Reference Tools provide transparent unit, range, percentage, ppm, uncertainty, TUR, guard-band, electrical, and other bounded calculations. Their outputs remain reference-only until deliberately bound to a controlled instrument, context, method, source, model, rule, evidence record, and authorized workflow.

DUEPROOF assurance kernel

DUEPROOF supplies canonical evidence identity, exact source anchors, typed support and contradiction, material reliance edges, deterministic gates, contest, correction, dependency-based recall, proof packages, independent verification, AI containment, and release discipline. The public architecture page translates those controls; the complete technical baseline remains a controlled engineering source.

AI and external agents

Reference discovery, Ask METRAXIOM, Interrogate, and external ChatGPT/MCP pathways remain separate data and authority paths. AI may retrieve, explain, summarize, or challenge. It cannot invent measurements, silently promote a source, approve a waiver, alter canonical evidence, sign a package, or release a result.

Commercial and release availability

Public Studio modes are available for evaluation. Private production workspaces, public paid enrollment, external AI, live acquisition, authoritative release, local/air-gapped editions, and compatibility claims remain independently gated. See System Status before relying on availability.

Rights and protected sources

Do not submit purchased standards, customer records, employer documents, proprietary drawings, export-controlled information, secrets, credentials, or other protected content unless the organization has the right, approved environment, and authorized processing path.

Evaluating the platform?

Review Trust Center, Architecture,System Status, Legal Center, andChangelog.