CALIBRATION STUDIO · PROOF MODE

Execute the engine. Prove the result, the boundaries, and the proof scope.

Proof Mode sends bounded public sample inputs through the server-side METRAXIOM Decision Engine. It returns the versioned result, reproduction fingerprint, a deterministic Decision Boundary Witness, and a scope-bound Proof Envelope so the visitor can inspect both what was proven and what deliberately remained outside the proof.

Run the proof Challenge support Inspect sample record

SERVER EXECUTION · SCOPE-BOUND PROOF

Run one decision, then interrogate the whole deterministic classification topology.

The calculation is the engine result. The Decision Boundary Witness reruns the same controlled decision helper at exact stated/guarded boundaries and representative regions; the Proof Envelope then binds the result, witness and exact proof scope into one digest/signature boundary.

PUBLIC VERIFICATION ENVIRONMENT

Challenge the Decision Engine.

Use non-proprietary demonstration data and an explicit public decision rule against the server-side METRAXIOM Decision Engine. This proof target is separate from the public Calibration Builder calculation engine, whose numerical verification profile is published independently.

Tap any metrology vector to load its values and run the controlled proof instantly.

Each vector is a different Decision Engine demonstration condition. You can also edit any field and run your own bounded sample.

NominalMeasuredLower tolerance magnitudeUpper tolerance magnitudeExpanded uncertainty UGuard bandUnit

DECISION ENGINE PROOF RECORD

Ready for a scope-bound topology proof.

Choose PASS, REVIEW, or FAIL—or change any input—then inspect the result, reproduction fingerprint, Decision Boundary Witness, proof scope, envelope digest and any earned signature level.

01SOURCEAuthorized source

02VERIFYHuman confirmation

03MODELControlled model

04CALCULATEDeterministic math

05DECIDEConfigured rule

06PROVEVersioned record

Public sample + network + proof boundary

When you run a proof, the bounded measurement inputs and declared public decision rule are sent to METRAXIOM's server for deterministic computation. The returned Boundary Witness proves software classification topology for that frozen rule/tolerance configuration; it does not validate the physical measurement, tolerance source, guard-band policy, laboratory uncertainty model, method, traceability or competence. Proof Mode does not identify a customer instrument, save a calibration record, approve a method, perform technical review, issue a certificate, or confer release authority.

Proof ladder truth

P1 proves the Decision Engine reproduction payload identity. BW proves the implemented decision-boundary topology. P2 binds the result, witness and declared proof scope into one SHA-256 envelope. P3 is earned only when a valid Ed25519 signing key signs that complete envelope. P4 remains not earned until the signing-key identity is anchored independently; a key returned by the same server does not become independently trusted merely because the signature verifies.

METRAXIOM

Loading the controlled interface.

Measurement authority is never inferred from a loading state. The requested surface is being prepared.

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.