DEVICE CONNECTIVITY · ARCHITECTURE

One governed bridge between the lab bench and the evidence record.

The planned METRAXIOM Device Bridge runs locally on an approved laboratory computer and connects to supported instruments through validated protocol/model profiles. Cloud software does not directly own arbitrary USB, GPIB, serial or LAN hardware.

Initial boundary: identify and read, not adjust.

A connected instrument may supply typed evidence. Connection, discovery or an imported reading does not by itself establish calibration validity, specification authority, review, release or regulatory compliance.

CAPABILITY LADDER

Every device capability is separately authorized.

READ

discover

Detect an attached or network-visible instrument through an approved adapter without issuing measurement-changing commands.

Phase: initial · device validation required

READ

identify

Read manufacturer, model, serial, firmware or equivalent identity fields when the protocol supports them.

Phase: initial · device validation required

READ

read measurement

Read typed measurement values only through a device profile that defines quantity, units, range, status and command semantics.

Phase: initial · device validation required

READ

read status

Read readiness, error/event registers and non-destructive health/status information.

Phase: initial · device validation required

READ

read configuration

Read configuration needed to interpret a measurement without modifying the device.

Phase: initial · device validation required

READ

import evidence

Create a timestamped import envelope for readings and metadata; imported data is evidence input, not automatic calibration authority.

Phase: initial · device validation required

GATE

execute controlled procedure

Execute only an approved versioned procedure after simulator/hardware validation, role controls and rollback behavior are proven.

Phase: future_gated · device validation required

GATE

write configuration

Change device configuration only with device-specific validation, MFA/role authorization, pre/post snapshots and audit evidence.

Phase: future_restricted · device validation required

GATE

adjust or trim

Calibration adjustment, zero/trim or coefficient writes remain disabled until device-specific validation and quality-system approval exist.

Phase: future_restricted · device validation required

GATE

firmware update

Firmware operations are outside the initial bridge and require a separate validated maintenance workflow.

Phase: future_restricted · device validation required

PROTOCOL CLASSES

Standards first. Vendor adapters when necessary.

VISA

GPIB / USB / serial / TCP-IP

Common multi-vendor instrumentation API layer.

SCPI

GPIB / USBTMC / LAN / serial

Common programmable-instrument command family; exact commands remain model-profile specific.

USBTMC

USB

USB Test and Measurement Class transport.

IEEE-488 / GPIB

GPIB

Long-lived laboratory bus across calibrators, DMMs, counters and RF instruments.

LXI

Ethernet

LAN instrumentation ecosystem using approved network instrument transports.

OPC UA LADS

Ethernet / OPC UA

Manufacturer-independent laboratory and analytical device information model.

Modbus TCP

Ethernet

Common industrial/environmental instrumentation protocol; register maps are device-profile specific.

Modbus RTU

RS-485 / serial

Serial industrial protocol; function/register access is allowlisted per device profile.

RS-232 / serial

Serial

Legacy and field instruments may expose ASCII or binary command sets.

HART

4-20 mA + digital

Read-only process-variable/identity access is separated from trim and configuration writes.

FOUNDATION Fieldbus

Fieldbus

Requires approved local interface hardware and profile-aware capability boundaries.

PROFIBUS PA

Fieldbus

Requires approved local interface and device-specific validation.

Approved vendor SDK/API

Vendor-defined

Fallback when open standards do not expose required read capability; versions and licenses are pinned/reviewed.

ECOSYSTEM TARGETS

Compatibility is declared by validated profile—not by marketing sentence.

These ecosystems define the initial research/adapter targets. A vendor name here does not mean every model is supported.

Fluke Calibration

electrical calibrators · reference multimeters · pressure and temperature calibration systems

Compatibility is declared only per validated model/profile.

Keysight

DMMs · counters · power · RF and microwave instruments

Standards-based programmable instruments are prioritized.

Beamex

documenting calibrators · process calibration systems

Digital calibration workflows and field-device protocols require profile-specific review.

Druck / Baker Hughes

pressure controllers · pressure calibrators · sensors

Pressure-calibration target ecosystem.

WIKA

pressure · temperature · process calibration

Protocol/model support is validated per profile.

Additel

pressure controllers · pressure calibrators · temperature calibrators

Protocol/model support is validated per profile.

Tektronix / Keithley

oscilloscopes · source measure units · DMMs · electrical test

Electrical/electronic calibration target ecosystem.

Vaisala

humidity · temperature · environmental measurement

Read and adjustment capabilities remain separate.

Mettler Toledo

balances · mass and laboratory weighing

Serial/network command sets require model validation.

Sartorius

balances · mass and laboratory weighing

Serial/network command sets require model validation.

FIRST-PARTY AGGREGATE TRAFFIC

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.

GPC, DNT and traffic objections stop collection. Exclude my traffic · How counting works · Privacy notice.

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.