METROLOGY COMPUTATION WORKSTATION · PRE-CALIBRATION

The numbers go on the bench before they go into the record.

Start with measurement context, then work through repeated readings, averages, conversions, error, uncertainty and decision math in one connected reference session. A working-value register carries results between core tools while session receipts keep the arithmetic handoff inspectable. Nothing here becomes controlled calibration evidence until it enters the separately governed record workflow.

01IDENTIFY02RANGE + RESOLUTION03SOURCE + PROCEDURE04MEASURE / CAPTURE05EVALUATE06EVIDENCE + REVIEW

Configure measurement context Range Intelligence Open computation machine ↓

CALIBRATION TECHNICIAN VIEW

Choose the measurement. Keep its context.

The Atlas configures the quantity tool and asks for the conditions that make the measurand sufficiently described. Completeness is descriptive, never a validation claim. Selecting another discipline or quantity starts a fresh public context draft.

Open configured Workstation ↓

Measurement discipline

Specialty metrology12 bounded discipline contexts

PRESSURE

Pressure & vacuum

Pressure transmitters, gauges, calibrators, vacuum instruments and reference systems.

PakPaMPabarpsiinH₂O

Quantity

01Calculation context

Required to describe the arithmetic inputs

Measurand descriptionDescribe the quantity intended to be measured, including mode where relevant.QuantityConfigured by the selected Atlas quantity.UnitQuantity-compatible units only. Change quantity or discipline to move to a different physical quantity.Declared rangeState the instrument range used, including endpoints or span.Declared resolutionState actual declared instrument resolution; do not substitute a specification count term.Resolution provenanceIdentify where the resolution statement came from.Pressure modeDeclare absolute, gauge, differential or vacuum mode.Pressure mediumIdentify the pressure medium.Atmosphere / reference basisState the pressure reference or atmospheric basis; explicitly record not applicable when justified.Head / elevation correctionState head/elevation geometry or explicitly record that no head correction applies.

Evidence and method context

This public Workbench describes context only. It does not authenticate an instrument, bind a controlled procedure, create evidence, or authorize release.

Instrument identityManufacturer, model, serial or asset identity.Reference identityIdentify the reference standard, source or realization.Procedure or methodIdentify the procedure, method or revision.Environmental / influence conditionsState relevant environmental and influence conditions.Acquisition originDescribe where the reading originated; this does not verify the source.Uncertainty modelIdentify the uncertainty model or controlled budget revision.Decision ruleIdentify the adopted decision rule when conformity is evaluated.

Conditional evidence context

Fluid densitywhen applicableRetain fluid density when a head correction is used.Local gravitywhen applicableRetain local gravity when the realization or correction depends on it.

Evidence stateNot recorded in the public Metrology Workstation

Authority stateReference-only

Calculation context incomplete

Measurement context

A completeness check for stated fields—not a judgment that those statements are correct, suitable, controlled, or validated.

Calculation context2/10

Missing: Measurand description, Declared range, Declared resolution, Resolution provenance, Pressure mode, Pressure medium, Atmosphere / reference basis, Head / elevation correction.

Evidence context3/9

Missing: Instrument identity, Reference identity, Procedure or method, Environmental / influence conditions, Uncertainty model, Decision rule.

2 conditional promptsNot included in the completeness totals; applicability requires review.

Context completeness describes what has been stated. It does not validate the instrument, source, procedure, model, uncertainty, decision rule, evidence, or authority.

Configured by the Atlas.Pressure & vacuum → Pressure → kPa

REFERENCE MODEL

ATLAS CONFIGURATIONPressure & vacuum / Pressure

Linear unit conversion is available. Mode, medium, reference basis and correction terms remain separate measurement context.

REFERENCE WORKSTATIONReference calculation only. It is not a controlled calibration record, certificate, validated method, review, or authoritative release.

METROLOGY COMPUTATION MACHINE · SESSION-LOCAL

Put the readings on the bench. Keep the math connected.

Build multiple reading sets, promote the statistic you actually need, chain it through bounded computation bays, and preserve a machine-readable arithmetic trail without turning exploratory work into controlled calibration evidence.

MODEPRE-CALIBRATIONBrowser session only · not retained to a Calibration JobChange measurement context ↑

DisciplinePressure & vacuum

QuantityPressure

Active set unitkPa

RangeNot declared

ResolutionNot declared

01CONTEXTQuantity + unit

→

02DATASETSOne or many sets

→

03REGISTERSelected working value

→

04TOOL BAYSConvert + calculate

→

05RECEIPTSInspect the handoff

MULTI-READING DATASET BAY

Keep separate runs separate. Promote only the result you intend to use.

Each set keeps its own readings, unit and computed snapshot. Changing raw readings invalidates only that set's prior summary.

Set labelUnit carried by this set

Readings · comma, semicolon or new line separatedBounded to 10,000 finite numeric values per set.

CHAINED ARITHMETIC BAY

Use the live register without retyping the last answer.

Add or subtract in the carried unit. Multiply or divide only by a dimensionless scalar. The workstation preserves the unit instead of inventing dimensional semantics.

A · REGISTEREMPTY

OperationOperand BOperand B is interpreted in the register unit.

RUN-TO-RUN COMPARISON

Compare two analyzed reading sets without retyping their means.

Comparison is same-unit only. If two runs carry different units, convert explicitly first; the machine will not silently normalize them.

Dataset ADataset B

RESOLUTION BAY

Separate internal math from the value you are entitled to report.

Declared resolution drives half-even reporting. Quantization uncertainty is calculated only under the explicit uniform ±resolution/2 assumption.

Math valueDeclared resolutionResolution provenance

STATISTICAL EVALUATION BAY

Descriptive reduction is not automatically a Type A evaluation.

Promote the active set to Type A only when the repeated observations actually support that interpretation. Effective degrees of freedom remains a separate uncertainty-model calculation.

Type A from active set

Reading set 1 · kPa

Welch–Satterthwaite νeff

u1c1ν1

u2c2ν2

u3c3ν3

SI PREFIX ENGINE

quecto → quetta

Full official decimal SI prefix range. Symbols are case-sensitive: m = milli; M = mega.

→

CONFIGURED QUANTITY TOOL

Pressure converter

Quantity family locked to the Atlas context. Change the configured quantity above instead of silently crossing physical quantities inside the computation session.

QuantityValueFromTo

DECISION MATH

Tolerance + guard band + TUR

NominalMeasuredLower tol magnitudeUpper tol magnitudeExpanded UGuard band

UNCERTAINTY

Independent RSS

Enter standard uncertainties. Correlated contributors require a covariance model and are intentionally blocked from this simplified reference model.

Standard u1Standard u2Standard u3Coverage factor k

CALIBRATION ERROR

Error, correction, ppm + % span

ReferenceIndicationSpan (optional)

REFERENCE COMPUTATION TAPE

The handoff stays inspectable.

Each supported operation records inputs, deterministic model/version, context snapshot and outputs. Export includes the reading sets and current register, but it still carries reference-only authority.

SESSION SHA-256Computing fingerprint…

No reference calculations recorded yet.

RANGES + RESOLUTION

Range Intelligence

Keep declared resolution, count terms and count-derived arithmetic estimates as separate concepts with explicit provenance.

Open range command surface →

LAB HARDWARE

Device Bridge

Vendor-neutral instrument discovery, identity and reading architecture across approved protocol and device profiles.

Inspect connectivity architecture →

CALIBRATION PROGRAM

Metrology Operations

Intervals, drift and stability, due/recall, procedures, certificates and integration governance.

Inspect operations architecture →

Automatic counts. No individual tracking.

TRACE counts approved public page requests worldwide without an analytics consent banner. No visitor identifiers, fingerprints, individual browsing histories or GPS locations are collected.

Analytics privacy update · October 29, 2026

TRACE automatically measures aggregate requests to approved public METRAXIOM pages worldwide to improve content, navigation and reliability. It runs at the first-party hosting proxy, before the hosting page cache, and works when JavaScript is disabled. No analytics consent banner or country-based opt-in selection is used.

The basic store contains separate hourly totals for approved pages, country and US-state labels, common referral domains, broad device/browser/operating-system families and unverified request categories. It contains no individual request ledger, full IP addresses, raw user agents, full URLs or queries, visitor identifiers, fingerprints, session histories or GPS coordinates. Country labels come from hosting network metadata and can describe a VPN or network exit. Missing geography is recorded as unavailable. No city, address or coordinates are collected. US-state labels come only from the trusted hosting header; other state/region labels remain unavailable. Software names are broad, spoofable claims, with no versions or cross-request fingerprint.

GPC, DNT and an explicit traffic objection stop collection. Earlier “Keep analytics off” choices saved only in browser storage are carried forward as objections when JavaScript runs on a public application page. They are not sent with the initial HTTP request: that request, JavaScript-disabled requests and static-only visits may contribute until an objection cookie or privacy signal is sent. Exclude this browser from traffic measurement without an account or JavaScript. The preference cookie uses the same value for everyone who excludes traffic (1) or explicitly restores basic measurement (0), lasts up to 180 days and does not identify you. Restoring basic measurement preserves the old local choice; it can apply again after the restore preference expires or is cleared. Restoring aggregate measurement does not override privacy signals or grant individual tracking permission. Earlier aggregate counts cannot be linked back to you or selectively removed.

When you choose a dashboard view, a separate functional reporting-preference cookie remembers only the preset or calendar dates for up to 30 days, scoped to /traffic. It is not used by the collection layer and contains no identifier or consent grant. Use Forget saved reporting view, including without JavaScript, to remove it. A failed refresh may display a clearly dated snapshot held briefly in page memory; it is never relabeled as current or replaced with fabricated zero counts.

Individual browser analytics is disabled in this aggregate-only rollout. The former optional browser collector is not loaded, its intake is retired, and no new tab/session events are accepted. Earlier consent records are not rewritten as new permission. Previously collected optional events follow their existing 30-day retention and integrity-checkpoint policy.

Page requests are separate from verified page rendering or unique people. Navigation requests, crawler claims, link previews, other automation and unknown requests remain separate. Estimated visitors and session histories are unavailable. Small labeled groups are combined in public reports. Counts are aggregate observations and do not establish identity, intent or endorsement.

Recognized health checks, HEAD requests, prefetches, server-component fetches and private/API/unapproved paths are excluded. Browser memory/disk cache, back-forward restores, client-only navigation, privacy objections, missing metadata and storage failures leave coverage gaps. Request retries and spoofed software labels can affect totals. The system does not extrapolate missed traffic or import historical Vercel Analytics counts.

Hourly counter buckets are retained for 30 days and pruned hourly in bounded runs; calendar reports exclude older hourly data even if maintenance is delayed. Separate cumulative marginal totals, with no event times or cross-dimension links, remain for the life of the site’s traffic record. Changing a date range, leaving the page or closing a browser does not erase those totals. Earlier uncollected state/software labels remain unavailable, not reconstructed. Vercel delivers the website and Supabase stores TRACE aggregates in the existing United States database. Provider security logs and backups have separate policies. TRACE adds no paid analytics feed or operator-computer dependency.

This October 29, 2026 supplement updates the analytics description in the September 7, 2026 Privacy Notice. It does not amend frozen agreement snapshots or claim that server-side processing is automatically exempt from privacy law. The assessment concerns this limited data flow and its controls; no universal regulatory approval is claimed. Privacy requests: ANDREWATTS23@gmail.com.