CALIBRATION STUDIO · AFTERSHOCK

Change one foundation. Interrogate the consequence.

AFTERSHOCK is a deterministic public prototype built around an explicitly synthetic foundation incident and synthetic decision capsules. It distinguishes mere connection from a bounded calculation showing invariant outcome, possible change, divergence, or insufficient evidence.

Analyze consequence Inspect sample record Challenge support Open live Context Twin

DETERMINISTIC CONSEQUENCE PROOF · PUBLIC PROTOTYPE

Connection is not consequence.

Incident INC-DEMO-481 challenges RS-00481; the lab classifies the bounded 842-capsule fixture without manufacturing missing evidence.

AFTERSHOCK · SYNTHETIC CONSEQUENCE ANALYSISNO CUSTOMER DATA · NO AUTOMATIC PRODUCT DISPOSITION

FOUNDATION INCIDENT

Reference standard RS-00481 · DCV 10 V range

SUPPORTED CORRECTION ENVELOPE+300 µV → +420 µV

CONSERVATIVE USE INTERVAL2026 day 030 → 330

INCIDENT TYPEReference standard OOT

INCIDENT BASIS STATECORRECTED CURRENT

CURRENT ASSERTIONassertion:rs-00481:rev-2

ONSET ASSUMPTIONNone invented

Synthetic demonstration incident: the retained evidence supports a +300 µV to +420 µV correction envelope for the affected 10 V DC range. No onset inside the interval is invented.

FLIGHT RECORDER FOUNDATIONREPLAY CAPSULE

History is interrogated from retained decision state—not today's mutable UI.

Observationoriginal + normalized
Referenceidentity + material reliance
Procedurehistorical revision
Decisionguarded limit + outcome
Runtimeengine version
Contest/correctionCORRECTED CURRENT
Assertion lineage2 retained revisions
Sustained contests1
Applied corrections1
Reliance closureCOMPLETE
Material scope655 decision nodes
Context excluded66 contextual nodes
Boundarymissing evidence stays missing

Public prototype only. The superseded incident assertion remains retained; a sustained contest can advance the current basis only through an explicit appended correction. Contest/correction and material-reliance states are projections with no recall or release authority. A successful replay does not establish physical truth, accreditation, traceability, regulator approval, or product disposition.

842 synthetic capsules are staged.Run AFTERSHOCK to separate connection from consequence.

THE OPERATING MODEL

Flight Recorder preserves the state. AFTERSHOCK interrogates the consequence.

The intended controlled architecture requires a historical decision to be replayed from its retained measurement-decision state rather than silently rebuilt from today's mutable procedure, software, reference, or database interpretation. The public AFTERSHOCK lab demonstrates the consequence-classification logic with synthetic capsules; it is not evidence that the controlled historical replay substrate is already promoted.

Historical replay and current comparison remain separate modes.

A later rule, model, correction, or procedure may eventually be compared against a retained historical observation, but it must never rewrite the original record.

ONE ENGINE · MULTIPLE FOUNDATION FAILURES

The incident does not have to be an instrument.

The same consequence architecture can apply only when affected dependencies, temporal scope, transformations and evidentiary bounds are explicit enough to support the analysis.

Reference standard

An as-found calibration result, correction, range, or certificate changes the supported historical state.

Procedure / specification

A controlled method, tolerance, source locator, revision, or interpretation is corrected or superseded.

Calculation software

A bounded implementation defect is discovered in a specific engine version, code path, unit conversion, rounding rule, or decision-rule branch.

Environment

A method-relevant environmental sensor or retained condition is later shown to be unreliable within a bounded interval.

AUTHORITY BOUNDARY

AFTERSHOCK narrows the technical investigation. It does not make the organization's disposition.

A consequence classification is not a declaration that product is safe, a certificate is valid, a batch may be released, hardware may fly, a laboratory is accredited, or a regulator has accepted the analysis. Those authorities remain outside this public software demonstration.

The strongest result may be “not determinable.”

When required evidence is unavailable, the classifier stops rather than converting inference into fact.

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.

Change one foundation. Interrogate the consequence.

Flight Recorder preserves the state. AFTERSHOCK interrogates the consequence.