AI + INSTRUMENT INTELLIGENCE

Ask almost anything about the work. Keep the answer basis visible.

METRAXIOM combines broad calibration intelligence, global instrument classification, tenant evidence, governed current-source research, deterministic tools, and external AI connectivity without turning the model into the measurement authority.

Try Proof Mode See AI data boundaries

FIVE ANSWER AUTHORITIES

METRAXIOM decides what kind of answer the question requires before treating it as trustworthy.

That prevents general model memory, static classification, current web material, tenant evidence, and deterministic calculation from being blended into one unlabeled response.

GENERAL KNOWLEDGE

Teach concepts, troubleshoot conceptually, explain metrology and instrumentation. Not controlled evidence.

REGISTRY CLASSIFICATION

Normalize instrument family, manufacturer aliases, and measurement context. Not a current specification.

TENANT EVIDENCE

Answer from retained workspace facts. Missing evidence stays missing.

CURRENT RESEARCH

Find current candidate manufacturer/metrology material. Human verification still required.

DETERMINISTIC ENGINE

Perform controlled measurement arithmetic. AI may explain; it does not replace this authority path.

METRAXIOM INTELLIGENCE CENTER

Visible architecture—even when execution is gated.

A disabled capability stays understandable. Customers can see what Ask METRAXIOM, the registry, Interrogate, Reference Intelligence, provider connections, and MCP are designed to do without exposing credentials or silently opening authority.

ASK METRAXIOM™

The workspace assistant separates tenant Evidence Mode from broad Knowledge Mode. A fluent model answer never becomes a retained fact merely because it sounds confident.

GLOBAL INSTRUMENT REGISTRY

Canonical instrument classes, manufacturer aliases, measurement disciplines, and common terminology help normalize a device before current manufacturer research. Classification is not a current specification.

INTERROGATE™

The record-level evidence reasoning layer computes deterministic integrity before AI synthesis, then explains the exact retained context, sources, uncertainty, rule, result, chronology, and blockers.

REFERENCE INTELLIGENCE™

Current manufacturer and metrology material is discovered separately as candidate evidence. A qualified human still verifies identity, revision, locator, applicability, and authorization before controlled use.

AI CONNECTIONS

The implemented provider architecture supports METRAXIOM-managed OpenAI inference, governed organization-connected OpenAI, and explicitly allowlisted OpenAI-compatible enterprise endpoints. Provider choice never widens measurement authority.

CHATGPT / MCP

External AI clients connect through METRAXIOM identity and OAuth-authenticated MCP tools—not consumer AI passwords or subscription credentials.

EXTERNAL AI CLIENT FLOW

Connect the customer's METRAXIOM identity—not a consumer AI password.

Customers do not give METRAXIOM a ChatGPT password. The connection is an OAuth-authenticated MCP relationship bound to METRAXIOM identity and policy.

1CONNECT

Customer approves the METRAXIOM app or connector in an approved external AI client.

2AUTHENTICATE

OAuth binds the request to the customer’s METRAXIOM identity and intended resource audience.

3SCOPE

Membership, tenant RLS, entitlement, and tool policy determine what the client may read.

4INTERROGATE

The client can request instruments, sources, evidence, decisions, and blockers through declared tools.

5EXPLAIN

METRAXIOM returns scoped evidence that an AI client may explain without inventing missing authority.

6AUTHORITY STAYS

Review, release, source finalization, billing, and role changes remain inside governed METRAXIOM controls.

PROVIDER-NEUTRAL AUTHORITY

Inference can be replaceable. The measurement system cannot.

Changing the inference provider changes where model reasoning runs. It does not change tenant scope, source status, deterministic arithmetic, evidence history, review authority, release authority, or billing permissions.

METRAXIOM MANAGED

Platform-managed inference

Uses the platform-configured OpenAI provider behind the same governed answer and authority boundaries.

ORGANIZATION OPENAI

Customer-controlled provider credential

Requires encrypted server-side storage, tenant binding, AAL2 administration, model policy, rotation, revocation, and connection verification.

ENTERPRISE ENDPOINT

Approved OpenAI-compatible endpoint

Explicit allowlisting governs the endpoint and model. The browser never receives the stored secret back.

READ-ONLY FIRST

External clients start smaller

No external AI tool silently reviews or releases records, rewrites controlled evidence, changes roles, or mutates billing.

PROMPT-INJECTION BOUNDARY

Retrieved text is data—not instruction authority.

Manuals, web pages, customer files, and candidate source text never gain permission to alter tool scope, tenant access, review/release authority, or system instructions.

Customer MCP connection execution is currently OFF.

The architecture remains visible, but no customer MCP connection opens until OAuth, client interoperability, privacy/security review, origin restrictions, and authenticated tenant-isolation testing pass.

Trust Center AI & Data Use Reference Intelligence

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.