Measurement Methodology

Operating standard

Every released result is designed to walk backward: Decision → Result → Formula/Model → Engine Version → Human-confirmed Input → Source → Controlled Instrument. The technical record must make that path reviewable without relying on memory or an unexplained spreadsheet cell.

Physical asset identity is not specification identity

The instrument registry identifies the actual organization-controlled asset under test through its own asset/serial identity and lifecycle. Manufacturer/model context may improve reference discovery, but it does not substitute for physical asset identity. Likewise, an AI-discovered specification candidate is not the instrument and is not automatically the controlling source. Authoritative evidence is designed to bind the physical instrument, the separately controlled source and locator, the measurement inputs, the rule/model, and the deterministic decision into one traceable record.

Measurand and requirement first

Before uncertainty or TUR is calculated, the workflow identifies what is actually being measured, the exact test point, governing tolerance/accuracy statement, range, resolution, units, source revision, and any method/customer qualifiers. A correct equation applied to the wrong requirement is still a wrong decision.

Metrological traceability

Traceability is represented as evidence, not a label. Where applicable, records should preserve the reference identity, calibration status, certificate/source relationship, uncertainty/capability information, and the documented chain or evidence needed by the governing quality system. METRAXIOM does not reduce traceability to the phrase “NIST traceable.”

Metrological traceability belongs to a measurement result: a documented, unbroken calibration chain contributes uncertainty at each step. Traceability alone does not establish fitness for the intended use. NIST

Precision and units

Boundary-sensitive arithmetic uses decimal arithmetic. Units are typed quantities, not labels appended to raw numbers. Calculation precision is separated from displayed rounding so presentation choices do not silently alter the decision.

No magic constants

Coverage factor, ratios, thresholds, equality behavior, guard bands, and customer/method rules are controlled configuration. METRAXIOM does not treat k=2 or 4:1 as universal requirements.

Uncertainty

Type A and Type B contributors, distributions, divisors, sensitivity coefficients, degrees of freedom where used, correlation assumptions, and coverage-factor conventions must remain explicit enough for competent review. Independent components may use RSS only where the model supports independence. Correlation requires a controlled covariance treatment or a review block.

Decision rules and statements of conformity

A PASS/FAIL/REVIEW outcome is inseparable from the selected decision rule. The record identifies the rule, version, boundary behavior, guard band or other risk treatment, and source/policy authority. METRAXIOM must not silently turn an organization’s risk policy into a universal metrology rule.

Technical records and validity

Evidence records are designed to preserve controlled instrument identity, inputs, source locator, model/rule identifiers, engine version, calculated outputs, review/release state, timestamps, and audit history needed to reconstruct what occurred. Instrument retirement preserves historical identity. Corrections supersede controlled history rather than overwriting it, and a controlled correction cannot silently switch the physical asset under test.

Validation

Paid authoritative output remains disabled until manual calculations, a controlled workbook, and the web engine agree under the same documented convention; security, entitlement, backup/restore and rollback controls pass; and an independent competent metrologist reviews the conventions, vectors, decision logic, and report language.

Scope discipline

References to ISO/IEC 17025, ISO 9001, ISO 10012, NIST or ILAC identify relevant control frameworks and guidance. They do not state that METRAXIOM is an accredited laboratory, a certification body, a standards publisher, or endorsed by those organizations.

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.