AETHELFORGESTAGING
Try Axis

TRANSPARENCY · LIVE

Status

Public telemetry for aethelforge.ai and the gate. If it's not on this page, we're not measuring it. If we're not measuring it, you shouldn't trust it.

THE ANSWER

What does aethelforge.ai/status show?

The Status page publishes the gate's real metrics — AEO scores, Core Web Vitals, crawl coverage, handshake throughput, and latency across MCP / ACP / AP2 / x402. Values marked pending wire are endpoints staged but not yet connected. No backfill, no retroactive smoothing.

word_count=44 · type=definitional

AEO · atomic answers

7pages

reporting

AEO · schema coverage

100%

reporting

CWV · LCP (p75)

—s

pending wire

CWV · INP (p75)

—ms

pending wire

CWV · CLS (p75)

—

pending wire

Crawl · allow-listed bots

11

reporting

Gate · p95 latency

—ms

pending wire

Ops · events (7d)

500

reporting

Ops · Axis receipts (7d)

0

reporting

Ops · Forge SDK (7d)

0

reporting

Gate · handshakes last 24h

—

pending wire

What's here

This page is the honest answer to “does the gate actually work?” Public telemetry, not marketing bullets. Numbers marked pending wireare metrics we plan to surface here but haven't yet — the infrastructure is staged, the endpoints aren't connected. As each lands, the value appears. No backfill, no retroactive smoothing.

What's coming

  • Core Web Vitals (LCP / INP / CLS) wired from the real-user monitoring beacon. Target: p75 LCP under 2.0s, INP under 200ms, CLS under 0.1.
  • Gate telemetry: handshake count, p95/p99 latency, success rate, protocol mix across MCP / ACP / AP2 / x402. Redacted of tenant identifiers.
  • AEO audit: per-page atomic-answer word count, schema emission check, llms.txt freshness, robots.txt crawler policy.
  • Infrastructure: CDN hit rate, Lambda cold-start histogram, CloudFront error rate, SES deliverability.

Why this page exists

Because trust requires something to check. A competent gate publishes its own numbers. If we ever stop doing that, stop trusting us.

FAQ

Status, answered.

  1. 01What does the Status page measure?

    AEO posture (atomic-answer coverage, schema emission, crawl allow-list), Core Web Vitals (LCP, INP, CLS at p75), gate telemetry (handshake throughput and p95 latency across MCP / ACP / AP2 / x402), and infrastructure health (CDN hit rate, Lambda cold-starts, SES deliverability).

  2. 02Why are some metrics marked “pending wire”?

    Because the endpoints are staged but not yet connected to the beacon. Rather than show a placeholder number, we show the status. When the wire lands, the value appears. No backfill, no retroactive smoothing — real data or nothing.

  3. 03How often does this page update?

    Counts for the last 7 days refresh on every request directly from DynamoDB. Core Web Vitals and gate latency (once wired) will aggregate at p75/p95 across rolling 28-day windows so a single regression does not skew the public view.

  4. 04Is there an SLA?

    Not yet. Aethelforge is in pre-production. The Status page exists so that when an SLA is offered, the numbers behind it are already public and continuous. A competent gate publishes its own metrics before asking to be trusted.