PUBLIC PRODUCTIONEVALUATION ONLY · NOT AUTHORITATIVERelease scope
Open the Builder

METRAXIOM

Choose your language

Translation drafts · not independently reviewed Display only. Canonical values, significant digits, calculations, decisions, provenance and record fingerprints do not change.

DOCUMENT & BUILD INTEGRITY · REGISTRY 1.1.0

Know what governs METRAXIOM — and identify the exact artifact.

Document role, byte identity, adoption, implementation, deployment, and production authority are different facts. This registry identifies supplied architecture records without converting a digest, document, source commit, or deployment into scientific or operational authority.

Registry content reviewed: . Source-byte verification dates remain unchanged unless the exact source files are supplied and recomputed.

Validation statusArchitectureTrust Center
IDENTITY VOCABULARY

Four different identity concepts

These identifiers answer different questions and must not be collapsed into a single claim of authority.

DOCUMENT SHA-256

Exact PDF or DOCX bytes, not the authority of their contents.

BYTE IDENTITY
ARTIFACT SHA-256

Exact generated output bytes, not an issued certificate or governing specification.

OUTPUT IDENTITY
PACKAGE FINGERPRINT

A separately defined canonical evidence-package identity. None is attested by this document registry.

PACKAGE IDENTITY
SOURCE / DEPLOYMENT IDENTITY

Source commit and deployed instance are separate. Neither alone identifies every dependency or configuration setting.

BUILD IDENTITY
Integrity is not authority.

A matching digest and byte length establish a match against the registered identity under SHA-256, not scientific truth, authorship, adoption, accreditation or implementation completeness. Verification dates below are not publication, approval or release dates.

ARCHITECTURE CONTROL HIERARCHY

Primary construction and calibration records

v6.1 supersedes v5.0 only where it expressly changes calibration execution or output. The broader website construction direction and protected invariants remain distinct. Listing a role does not itself record formal adoption or acceptance.

Primary calibration control document · CAL-ARCH-V6.1 · 6.1

World-Class Universal Calibration Architecture + Certificate Control Manual

Calibration/product construction: universal execution, multi-discipline schemas, evidence, certificate architecture and verification.

Document / artifact status: Full-interrogation architecture / product construction candidate; capability-specific release evidence remains required.

Authority and lineage: Supersedes v5.0 only where v6.1 explicitly changes calibration execution or output architecture. It does not replace all website construction controls.

Document SHA-256: bf356a041af4e44a1bc31f90d8e18e2fa72eebea611650c4987bf98d3989a9d0

Exact byte representation: PDF · 1,615,104 bytes

Source-byte verification date: · SHA-256 recomputed from the supplied file

Publication and availability: Metadata only here. File publication date is not established by this registry; no file download is hosted by this page.

Implementation evidence: Not attested by this file identity. Review capability and validation status.

IDENTITY REGISTERED

Primary website construction document · WEB-PRODUCT-V5.0 · 5.0

World-Class Website + Product Construction Manual

Website, information architecture, UX, Trust, documentation, DUEPROOF integration and implementation control.

Document / artifact status: Architecture-freeze candidate in the document; adoption and implementation evidence are separate from byte verification.

Authority and lineage: Broader website/product construction baseline, subject to scoped v6.1 changes and later adopted architecture decisions.

Document SHA-256: 34d3871ff82385442ad9b95c41ebfc22260b71a56e914651ac0a56503b96bb32

Exact byte representation: PDF · 911,394 bytes

Source-byte verification date: · SHA-256 recomputed from the supplied file

Publication and availability: Metadata only here. File publication date is not established by this registry; no file download is hosted by this page.

Implementation evidence: Not attested by this file identity. Review capability and validation status.

IDENTITY REGISTERED

Supporting assurance architecture

DUEPROOF remains the assurance kernel beneath METRAXIOM.

Supporting assurance-kernel technical baseline · DUEPROOF-V0.2 · 0.2

METRAXIOM DUEPROOF Complete System Architecture & Technical Control Specification

Supporting assurance-kernel technical baseline for provenance, reliance, gates, contest, correction, recall, proof packages, security and AI boundaries.

Document / artifact status: Technical architecture specification; this listing is not an implementation or release attestation.

Authority and lineage: DUEPROOF is the assurance kernel beneath METRAXIOM, not a second customer-facing product or competing control hierarchy.

Document SHA-256: adb044c435f665d00c850cd234a258ccc17746607dc7bfbd5b9429245c563207

Exact byte representation: PDF · 2,245,423 bytes

Source-byte verification date: · SHA-256 recomputed from the supplied file

Publication and availability: Metadata only here. File publication date is not established by this registry; no file download is hosted by this page.

Implementation evidence: Not attested by this file identity. Review capability and validation status.

IDENTITY REGISTERED

Public explanatory material

The two supplied v1.1 brief copies were compared directly and are byte-identical. They have one canonical registry entry, not two competing versions. The downloadable publication is not enabled here.

Public explanatory brief · DUEPROOF-PUBLIC-V1.1 · 1.1

METRAXIOM DUEPROOF Public Architecture Brief

Public explanation of proof-carrying decisions, material reliance, correction and decision recall.

Document / artifact status: Architecture under active development; public claims intentionally conservative.

Authority and lineage: One canonical record for two byte-identical supplied copies. Explanatory material is not a governing specification or production-readiness attestation.

Document SHA-256: 20966758bda966d327e6a11fb62efc5ff60df9b42f9ca01b0c6befb3eceb6041

Exact byte representation: PDF · 43,884 bytes

Source-byte verification date: · SHA-256 recomputed from the supplied file

Publication and availability: Metadata only here. File publication date is not established by this registry; no file download is hosted by this page.

Implementation evidence: Not attested by this file identity. Review capability and validation status.

IDENTITY REGISTERED
Historical / foundational records — not current architecture authority

The PDF and DOCX are separate representations with separate digests; neither hash verifies the other.

Historical / foundational record · FOUNDER-BUILD-REV3-PDF · Rev 3.0 PDF

Founder Computer Build Manual + Full Commercial Bill

Foundational execution history covering formation, accounts, code, validation, deployment, launch, sales and scale.

Document / artifact status: Historical/foundational build record; not current controlling product architecture.

Authority and lineage: Preserved execution lineage. Later adopted control documents govern where they differ.

Document SHA-256: 37c365b2eb975553e86a739b5c02fe1a14265f5f8d95bb8fb5a685e42a06efc3

Exact byte representation: PDF · 805,327 bytes

Source-byte verification date: · SHA-256 recomputed from the supplied file

Publication and availability: Metadata only here. File publication date is not established by this registry; no file download is hosted by this page.

Implementation evidence: Not attested by this file identity. Review capability and validation status.

IDENTITY REGISTERED

Historical / foundational record · FOUNDER-BUILD-REV3-DOCX · Rev 3.0 DOCX

Founder Computer Build Manual + Full Commercial Bill

Editable source-format artifact in the Founder Build Manual lineage.

Document / artifact status: Separate byte artifact from the PDF representation; historical, not current architecture authority.

Authority and lineage: Its SHA-256 identifies only the DOCX bytes. It does not verify the PDF, and this registry does not attest content equivalence between formats.

Document SHA-256: 07c665e376d613d80a683c62fab002f751a54de2828e7694e76e39c17e34b7fb

Exact byte representation: DOCX · 97,510 bytes

Source-byte verification date: · SHA-256 recomputed from the supplied file

Publication and availability: Metadata only here. File publication date is not established by this registry; no file download is hosted by this page.

Implementation evidence: Not attested by this file identity. Review capability and validation status.

IDENTITY REGISTERED
SEPARATE OUTPUT REGISTER

Sample artifacts — not governing documents

These outputs are deliberately excluded from the architecture-control collection. A sample cannot confer laboratory, certificate or release authority.

Sample output — no governing authority · DMM-0427-PUBLIC · Public v6.1 sample artifact

METRAXIOM-DMM-0427 Uncontrolled Calibration Data Sheet

Generated public calibration-data example with user-supplied/demo data; evidence of one sample output, not of complete system validation.

Document / artifact status: UNCONTROLLED; not an issued Certificate of Calibration or controlled laboratory record.

Authority and lineage: Artifact identity only. The printed input fingerprint is not this PDF digest and is not attested here as a canonical package fingerprint. Other files named DMM-0427 may have different bytes.

Artifact SHA-256: 219fc108d8aa9d5096a8945020c48d16bd1e99600c4597cc1c62082d98e67f98

Exact byte representation: PDF · 4,984 bytes

Source-byte verification date: · SHA-256 recomputed from the supplied file

Publication and availability: Metadata only here. File publication date is not established by this registry; no file download is hosted by this page.

Implementation evidence: Not attested by this file identity. Review capability and validation status.

IDENTITY REGISTERED

Check a file on your own device

The selected file is read locally for SHA-256 comparison. This component does not upload the file, send its digest, or retain either in browser storage. Maximum file size: 16 MiB.

Select a registered item, then choose your local file. No file is uploaded.

Source and deployment identity for this page

These allowlisted values are reported by the hosting environment when this static page is built. They identify the page build; they are not independent attestations and do not prove that every registered document is adopted, implemented, validated, or released.

Source commit

46230ccf5a9207139d30941235a2a6f95e47b1b8

SOURCE
Deployment identifier

dpl_WWhD7yaMu9Av7R7Mjv26WnxNwvqx

DEPLOYMENT
Environment at build time

production

ENVIRONMENT
Document-to-build acceptance mapping

Not attested by this registry. Source presence, successful deployment, controlled qualification and authorized release require separate evidence.

UNATTESTED

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.

Measure with purpose. Decide with evidence.

Measurement-decision infrastructure connecting instrument identity, controlled authority, deterministic calculation, uncertainty, review, and reproducible proof.

METRAXIOM is the software product and brand. The individual seller is Andre Jason Watts. METRAXIOM DUEPROOF is the assurance architecture beneath evidence, dependency, correction, recall, and proof; it is not a separate calibration certificate, accreditation mark, or public product.

PlatformProductCalibration StudioFleet importMetrology WorkstationConnection AtlasCalibration Label StudioDevice BridgeOperationsIntegrations
EvaluationSolutionsArchitectureDocumentationMethodologyPricingContact
TrustTrust CenterSecurityAssuranceData GovernanceAI & Data UseSystem Status
Company & legalCompanySupportAccessibilityLegal CenterPrivacyTermsCancel subscriptionAccount deletionCustomer & business contact
© 2026 Andre Jason Watts · METRAXIOM. Contact:ANDREWATTS23@gmail.com.No accreditation, certification, regulator approval, universal device compatibility, or independent metrology-validation claim is created by purchasing or using the software.