00TraceAxiom / website release record

Inspect the website record, including its limits.

This page exposes what the current TraceAxiom website release checked, the exact source digest it bound, and the claims that remain outside its authority.

Join the waitlistBegin

01Scope

This record verifies the public website release and nothing beyond it.

The release record covers the static build served at traceaxiom.com. It checks the exact source tree used for the build, desktop and mobile browser behavior, keyboard operation, reduced-motion behavior, automated accessibility, crawler-visible content, canonical metadata, structured data, internal links, and machine-readable discovery files.

Its status is locally_verified_scope. That wording is deliberate: these checks were executed by the project's release gate against the built site. They are not a penetration test, an external certification, customer acceptance, or proof that TraceAxiom Verify is ready for use.

  • Exact source-tree digest
  • Named checks and methods
  • Observed timestamp
  • Limitations retained with the result

02Reproduce

The public JSON carries the values shown here and a digest of its own subject.

The machine-readable record at /.well-known/traceaxiom-verification.json contains the release scope, observation time, source digest, check verdicts, measured browser values, accessibility result, limitations, and unverified items. Its recordDigest is SHA-256 over canonical JSON of those fields, excluding the digest fields themselves.

A reader can fetch the JSON, sort each object key, serialize the subject without extra whitespace, and recompute the digest. That verifies that the record is internally unchanged. Recomputing the source-tree digest still requires access to the exact source bytes, so this record does not pretend to provide source transparency that the private repository does not provide.

  • Canonical machine-readable URL
  • Declared digest algorithm
  • No credential or customer data
  • Source-access limitation stated

03Crawler

Every canonical page must stand on its own before JavaScript runs.

The release gate reads the built HTML for every URL in the sitemap. Each page must contain substantial main content, a unique title and description, one H1, a self-referencing canonical URL, visible breadcrumbs where applicable, valid structured data that matches the page, and crawlable links to known internal destinations.

The same release generates llms-full.txt and ai-index.json from those server-rendered pages. If the main element disappears, a canonical changes origin, a sitemap URL duplicates another, or a discovery file drifts from the HTML, publication fails. This protects ordinary search indexing and gives answer engines a text-first representation of the same public content.

  • Server-rendered HTML
  • Canonical-only sitemap
  • Index and follow directives
  • No crawler-only content

04Accessibility

Automated checks cover serious failures, keyboard paths, motion, and layout.

The gate runs axe against the homepage and every substantive detail page, exercises the main interaction with a keyboard, checks visible focus treatment, inspects horizontal overflow, and loads a mobile viewport with reduced motion enabled. The published record reports the serious or critical automated violation count instead of replacing it with a hand-written claim.

Automated accessibility testing has a firm boundary. It does not replace review with VoiceOver, NVDA, or TalkBack, nor does it establish that every interaction works well for every user. Those items remain in the record's unverified list until a person with the relevant authority and method completes them.

  • Desktop browser path
  • Mobile reduced-motion path
  • Keyboard focus path
  • Automated limitations visible

05Trust

A passing site check does not close product, security, or customer gates.

TraceAxiom is an in-development product operated by founder Arhan Canli. The Trust, About, Privacy, Terms, Contact and Security pages identify the operator, current legal status, data processors, reporting route, product boundary, and claims the project does not yet make.

Independent external security review, managed production isolation, and design-partner acceptance remain open. They will not be inferred from this website record. The purpose of publishing the record is narrower: anyone evaluating the site can inspect what its release process checked, when it checked it, and where that evidence stops.

  • Named operator
  • In development
  • External review remains open
  • Customer acceptance remains open

This page is a run

The record this site's own gate wrote for this exact build.

The build reads these rows from the evidence file and binds them to the source digest. Change one byte of the source and the rows stop applying.

Subject / source tree digestsha256:3f5e6b927dd80710bf12818ce8995d021d2e1cdd0fb822b0d15407a1eced4291

The exact 49 source files this page was built from, digested byte-wise.

Status
locally_verified_scope
Observed
2026-10-05T16:05:55Z
Scope
local_static_build_gate
This page's evidence record
GateMethodResult
Production builddeterministic_testpassed
Desktop browser smokedeterministic_testpassed
Mobile, reduced motiondeterministic_testpassed
Keyboard interactionsdeterministic_testpassed
Automated accessibilitydeterministic_test0 critical or serious
Core Web Vitals in the labruntime_measurementLCP 264 ms · CLS 0.000
Full page visible without scrollingdeterministic_testpassed
Canonical indexable routesdeterministic_testpassed
Unique titles and descriptionsdeterministic_testpassed
Search and grounding directivesdeterministic_testpassed
Visible-content structured datadeterministic_testpassed
Internal link integritydeterministic_testpassed
Sitemap and robots discoverydeterministic_testpassed
Public trust filesdeterministic_testpassed
AI discovery filesdeterministic_testpassed

Limitations

  • Automated accessibility checks do not replace assistive-technology review
  • Lab web vitals on one machine are not field data
  • This gate does not establish production isolation or customer acceptance

Not verified

  • Assistive-technology review with VoiceOver, NVDA, or TalkBack
  • Blind human visual preference
  • Customer acceptance
  • Production use of TraceAxiom Verify

Machine-readable record

Read the same result without the interface.

The JSON endpoint preserves the current site-release scope, verdicts, source binding, measured values, limitations, and record digest.

Open verification JSON