SYSTEM STATUS

Operational health and authority are reported separately.

The snapshot below reports what this deployment can inspect now. The release matrix then shows which customer, AI, hardware, commercial, and measurement-authority capabilities remain independently gated.

Last checked 11/1/2026, 4:25:57 AMRelease 46230ccf5a92Environment production

OPERATIONAL SNAPSHOT

Measured facts first.

This is a request-time snapshot, not a fabricated uptime percentage or contractual service-level commitment.

Public applicationOPERATIONALThis status request rendered through the public application boundary.

Deterministic Proof ModeOPERATIONALDeterministic self-test returned the expected REVIEW state.

Ask METRAXIOM public guideGATEDPublic guide disabled by release gate

Private workspaceGATEDCustomer workspace access remains behind its independent release gate.

Subscription enrollmentGATEDNew recurring enrollment remains closed; this does not determine existing-customer portal availability.

Deterministic self-test6 msExpected decision REVIEW · engine 0.3.4-candidate

Runtimev24.22.2Reported by the executing server process.

Machine statusNO-STORE JSONInspect the public status payload →

Health endpointAVAILABLEInspect machine health →

INCIDENT HISTORY

Public incident ledger not yet published.

No public incident-history feed is published yet. This statement is not a claim of zero historical incidents. Material production incidents should be documented here once commercial service begins.

INDEPENDENT RELEASE MATRIX

No single green light means the entire product is released.

The hosted public application is a production deployment for bounded evaluation. Its deterministic engine and outputs remain non-authoritative demonstrations unless a separately identified authority gate is earned. Application uptime cannot confer billing entitlement, AI authority, hardware compatibility, or authoritative measurement release.

Released: Public Builder with browser-local worksheets; Public uncontrolled PDF export; Context Twin context from NOAA/NWS and NOAA/SWPC. Held: Authoritative measurement release; Certificate issuance and signing; Private workspace; Billing and commercial enrollment; Public search indexing; Live Acquisition; Public AI and MCP.

Public application shell + Proof Mode

The public site and bounded demonstration path operate independently from private customer evidence. HTTP health does not establish metrological validation or customer fitness for use.

PUBLIC PRODUCTION · evaluation

Public calibration worksheet

Open the calibration worksheet to enter browser-local user values. An open gate does not create retained controlled evidence, certificate authority, or successful-save proof.

Release gate open · uncontrolled

Public PDF export

The independent gate permits a bounded, rate-limited server render from the selected browser-local worksheet snapshot. This release state is not proof of a successful render and the PDF is not an issued certificate.

Release gate open · uncontrolled

Context Twin public surface

Inspect Context Twin and its authority stop. Customer visibility is independent from live weather, geocoding, and space-weather provider activation.

Discoverable

Context Twin external providers

Rate-limited NOAA/NWS weather and NOAA/SWPC space-weather retrieval are enabled as context-only sources. They never auto-copy into the public calibration worksheet; candidate geocoding, global weather-model, and commercial-provider adapters remain off.

Live providers enabled

Direct customer email

The published monitored email address accepts customer and business requests. This contact channel does not open the structured web form or public enrollment.

Available

Structured contact form

The optional web-submission channel has its own implementation and environment gates. Direct email availability cannot activate it.

Closed

Authenticated workspace

Authentication, tenant membership, database/application contract, recovery, and security evidence remain separate prerequisites.

Production workspace hold

Pressure Worksheet candidate

The retained work-package path remains separate from an issued calibration certificate or authoritative release.

Candidate workflow hold

New paid subscription enrollment

Checkout and recurring enrollment require the complete commercial gate. A selection or return URL never grants paid access.

Checkout activation hold

Existing-customer billing + cancellation portal

Invoice, payment-detail, general billing, and focused cancellation access are independently gated from new enrollment. Public cancellation help remains available.

Signed-in portal hold

Signed Stripe state reconciliation

Subscription, scheduled cancellation, completed cancellation, trial, and payment state comes from verified provider events rather than browser navigation.

Provider-event hold

Ask METRAXIOM workspace assistant

Evidence Mode is authenticated, tenant-scoped, read-only, provider-routed, and has no measurement, review, release, billing, or team-administration authority.

Disabled by gate

Reference Intelligence

External discovery retains provider and trust provenance. Discovery never becomes controlled-source authority automatically.

Disabled by gate

Interrogate AI

Conversational explanation is independently gated, entitlement-scoped, and non-authoritative.

Disabled by gate

AI Connections / customer provider

Organization-scoped credentials, AAL2 administration, rotation, tenant isolation, provider verification, and data-use controls must all be proven.

Credential-vault hold

ChatGPT / MCP connection

External agent access is read-only first, OAuth/resource scoped, tenant checked, and separate from every other intelligence surface.

Disabled by gate

Device Bridge / Live Acquisition

Private live topics and explicit evidence capture remain gated by connector security, simulators, exact model/firmware/profile, time quality, and physical-device validation.

Hardware validation hold

Authoritative measurement release

Authoritative release is independent from uptime and every commercial capability. It remains off until documented validation and competent independent metrology review pass.

Validation-gated

SERVICE COMMITMENTS

Measured operation is not an invented SLA.

Availability targets, support response times, maintenance windows, incident communications, service credits, and customer-specific RTO/RPO obligations belong in controlled production documentation or a signed agreement.

Report an operational or security concern.

Use the published Support Center or security contact path. Do not place credentials, payment-card information, or customer measurement evidence in an unsecured report.

Support Center Trust posture

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.