GOVERNANCE CENTER

Governance should execute—not sit in a PDF nobody reads.

METRAXIOM treats public utility, calculation models, AI capabilities, commercial activation and measurement authority as separately versioned and gated systems. A feature being technically possible does not mean it is authorized.

RELEASE PROFILE · PUBLIC_USE_PRODUCTION

LIVE ENVIRONMENT POSTURE

Independent gates

The public-use release model keeps useful public tools and context-only provider signals separable from purchasing, private controlled work, candidate providers, and authoritative measurement release.

ONPublic Builder

ONPublic fixed-layout PDF

ONContext Twin provider execution

ONPublic indexing

OFFNew paid enrollment

OFFBilling + cancellation portal

OFFSigned Stripe reconciliation

OFFReference Intelligence

OFFInterrogate AI

OFFChatGPT / MCP

OFFAuthoritative release

REFERENCE MODEL REGISTRY

Every Workbench formula has a name and version.

Reference-only models can help a technician work quickly, but they cannot silently become a controlled certificate, validated method or authoritative release.

1.0.0

SI prefix scaling

MW-SI-PREFIX · reference only

Scale SI quantities across the complete official decimal prefix range.

Assumptions: SI prefix symbols are case-sensitive. · Decimal powers of ten only; binary prefixes are out of scope.

1.0.0

Measurement-unit conversion

MW-UNIT-CONVERT · reference only

Convert common calibration-lab quantities through an explicit reference unit.

Assumptions: Only units within the same declared quantity family may be converted. · Affine temperature conversion is handled separately from linear conversions.

1.1.0

Range intelligence

MW-RANGE-INTELLIGENCE · reference only

Expose span, range position, headroom, error percentages, ppm, resolution provenance and user-declared multi-term accuracy allowance without hiding the range basis.

Assumptions: Range high is greater than range low. · Specification count terms and full-scale display counts are different concepts. · Count-derived span/count arithmetic does not by itself prove physical instrument resolution. · Range selection is not automated without a validated device profile.

1.0.0

Resolution-limited reporting

MW-REPORT-RESOLUTION · reference only

Preview a value rounded to an explicitly declared resolution while preserving higher internal calculation precision.

Assumptions: Declared resolution is supplied with provenance. · Half-even rounding is a reporting policy, not evidence that the instrument actually possesses the declared resolution.

1.0.0

Digital quantization uncertainty reference

MW-DIGITAL-QUANTIZATION · reference only

Calculate the standard uncertainty corresponding to a uniform quantization model over plus/minus one-half declared resolution.

Assumptions: Uniform quantization over ±resolution/2 is explicitly justified for the measurement system. · Do not add this contribution automatically when another model already accounts for quantization/resolution.

1.0.0

Tolerance, guard band and TUR reference

MW-DECISION-REF · reference only

Expose error, specification limits, guarded acceptance limits and a declared demonstration TUR convention.

Assumptions: Inclusive boundaries. · TUR convention = minimum tolerance magnitude / expanded uncertainty. · This reference tool does not select a decision rule for the user.

1.0.0

Independent-component RSS uncertainty

MW-UNC-RSS · reference only

Combine independent standard uncertainty contributors and apply an explicit coverage factor.

Assumptions: Contributors are independent unless a controlled covariance model is used elsewhere. · Sensitivity coefficients are explicit.

1.0.0

Type A repeatability statistics

MW-TYPE-A-REPEAT · reference only

Evaluate repeated independent observations obtained under the same conditions as a Type A statistical contribution.

Assumptions: At least two observations are required. · Observations are independent and obtained under the same measurement conditions. · This evaluates repeatability/statistical contribution; it is not a complete uncertainty budget.

1.0.0

Effective degrees of freedom

MW-WELCH-SATTERTHWAITE · reference only

Approximate effective degrees of freedom for mutually independent standard-uncertainty components.

Assumptions: Components are mutually statistically independent. · Degrees of freedom are supplied or explicitly treated as infinite. · Correlation/covariance requires a different validated model.

1.0.0

Ohm's Law and DC power

MW-OHMS-LAW · reference only

Solve voltage, current, resistance and power when two electrical quantities are known.

Assumptions: DC/resistive model. · Resistance must remain positive. · Complex impedance and phase are outside this model.

1.0.0

Kirchhoff balance checks

MW-KCL-KVL · reference only

Check signed current and voltage sums against a user-declared residual tolerance.

Assumptions: Users assign signs consistently with the selected node/loop convention.

1.0.0

Linear transmitter scaling

MW-LINEAR-SCALE · reference only

Map common electrical signals such as 4–20 mA or 0–10 V into engineering-unit ranges.

Assumptions: Linear transfer function. · No sensor nonlinearity, trim, square-root extraction or environmental correction unless separately modeled.

1.0.0

Calibration error / correction / ppm

MW-ERROR-STATS · reference only

Calculate indication error, correction, relative error and ppm against a declared reference.

Assumptions: Reference value is nonzero for relative/ppm quantities.

1.0.0

Frequency / period reciprocal

MW-FREQ-TIME · reference only

Convert positive frequency to period and positive period to frequency.

Assumptions: Steady periodic signal.

1.0.0

AC reactance and ideal resonance reference

MW-AC-REACTANCE · reference only

Calculate ideal capacitive reactance, inductive reactance, and LC resonant frequency from explicitly declared frequency and component values.

Assumptions: Ideal lumped-element model. · Frequency, capacitance, and inductance are positive. · Loss, ESR, parasitics, Q, phase, distributed effects, and RF fixture behavior are outside this model.

1.0.0

Reading-set descriptive statistics

MW-DATASET-SUMMARY · reference only

Summarize a technician reading set with deterministic decimal count, sum, mean, median, extrema, range and bounded repeatability statistics.

Assumptions: Readings carry the same declared quantity and unit. · Sample standard deviation and standard uncertainty of the mean require at least two observations. · Descriptive statistics do not establish measurement validity, independence, stability or calibration authority.

1.0.0

Working-register scalar arithmetic

MW-SCALAR-ARITH · reference only

Perform bounded deterministic arithmetic on a carried working value without exposing a general expression evaluator.

Assumptions: Addition and subtraction require the second operand to be expressed in the same carried unit. · Multiplication and division treat the second operand as dimensionless. · This model does not perform dimensional synthesis or infer new derived quantities.

1.0.0

Reading-set mean comparison

MW-DATASET-COMPARE · reference only

Compare the deterministic means of two analyzed reading sets without retyping values.

Assumptions: Both sets carry the same declared physical quantity and exact unit. · A difference between means does not by itself establish drift, stability, bias, significance, or conformity.

Open Workbench Controlled methodology

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.