Technician
Start from the physical instrument and assigned work. Resolve the governing procedure, specification, references, context, and safety conditions before controlled acquisition.
METRAXIOM documentation follows technician, reviewer, metrology, quality, administration, and integration tasks while preserving the exact objects, states, reason codes, and control boundaries beneath them.
Discipline modules add scientifically specific context, but they do not replace the common evidence, authority, review, and release model.
Portal 2026.10 · reviewed 2026-10-06. Search runs only in this browser tab; the query is not retained.
9 current documentation entries.
Role lenses change priority and density. They do not change evidence meaning or authority.
Start from the physical instrument and assigned work. Resolve the governing procedure, specification, references, context, and safety conditions before controlled acquisition.
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.
Control procedures, specifications, reference standards, uncertainty templates, decision rules, calibration programs, interval rationale, and discipline-module validation.
Govern nonconforming work, contests, corrections, impact/recall, electronic signatures, release authority, audit, validation, retention, and quality-system links.
Manage tenant roles, MFA, sessions, sites, integrations, feature gates, data routing, billing, retention, incident response, and support access.
Use versioned APIs, schemas, idempotent commands, expected-version controls, webhook verification, proof profiles, reason codes, and compatibility records.
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.
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.
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.
These are not disconnected applications. The v5 information architecture reorganizes them around durable domain objects while preserving the existing evidence and authorization foundation.
Role-aware status, foundation readiness, recent evidence, current gates, and next best action.
Private workspace route · /appCreate and resume retained measurement context and controlled work packages.
Private workspace route · /app/calibrationsControlled procedure identity, immutable revisions, scope, and method authority.
Private workspace route · /app/proceduresPhysical assets and measurement-system identities.
Private workspace route · /app/instrumentsRecords awaiting governed human review or release action.
Private workspace route · /app/review-queueRetained calculation, decision, review, release, and supersession records.
Private workspace route · /app/historyAppend-only material workspace activity.
Private workspace route · /app/activityCalibration programs, interval basis, due anchors, and stability evidence.
Private workspace route · /app/operationsAsk METRAXIOM, reference discovery, AI-provider, external-agent, and authority-boundary status.
Private workspace route · /app/integrationsMFA enrollment, session revocation, and high-authority action protection.
Private workspace route · /app/securityReference 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 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.
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.
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.
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.
Review Trust Center, Architecture,System Status, Legal Center, andChangelog.