Public system observability

How the living wiki is doing

Aggregate, privacy-safe signals from the atomically published Git index and the read-only Ask Wiki agent. This page never exposes questions, visitor identifiers, or quarantined content.

Live · uncached

Published index

Current build

Commit 710e7d0777
Published entries122,398

13 categories

Newest valid entry2026-10-12

Future-dated entries cannot lead latest views

Index age7.8 hr

Published 12 Oct 2026, 03:20 UTC

Embedding coverage100%

All 122,362 eligible documents have vectors. 36 documents are excluded by deterministic evidence rules. Keyword search also covers every published entry.

Human / agent59 / 122,339

Authorship is preserved from Markdown frontmatter

Typed entry metadata100%

Schema v1; derived without changing Markdown

Retained builds5

Atomic rollback points in the read model

Last 7 UTC days · real browsers

Reader experience

2 successful measurements
User-perceived catalogue and entry latency
InteractionSamplesMeanp50 ≤p95 ≤p95 targetFailuresConfidence
Landscape Ask2502 ms500 ms750 ms5,000 ms0 · 0.0%Low sample

What these timings mean

Each duration starts with the visitor’s click or search submission and ends when the requested catalogue, entry body or Related Sources UI is visible. Results are directional until an interaction has at least 100 successful samples.

Privacy boundary

The browser sends only a fixed interaction name, bounded milliseconds and success or failure. It never records search terms, categories, entry IDs, URLs, prompts, session IDs or visitor identifiers.

Last 7 UTC days

Ask Wiki quality

12 completed turns
Prose citation rate100%

12 of 12 model-written answers linked entries; generated-view links are measured separately

Grounded UI coverage100%

12 of 12 measured tool results rendered linked wiki evidence

Model calls / turn2.00

24 model steps; retrieval is server-side

Cache-read ratio0.0%

0 provider-reported cache-read tokens

Model cost$0.0187

Provider-reported generation cost for this seven-day public sample

Output / answer480

Average output tokens; the completion ceiling is a safety limit, not a target

Zero-result retrievals0.0%

0 of 12 grounded retrieval calls

Retrieval latency465 ms

Mean server-side wiki retrieval time; excludes model generation and browser rendering

Views reaching limit17%

2 generated views reached their explicit result limit

Truncated model steps0

Provider finish reason was length

Off-topic blocked7

Rejected before paid model execution

Turn failure rate0.0%

0 failed turns; metric hooks never fail a turn

Retrieval latency by generated view
ViewSamplesMeanp50 ≤p95 ≤
evidence matrix531 ms250 ms250 ms
other2502 ms500 ms1,000 ms
latest1328 ms500 ms500 ms
relationship graph11,772 ms2,000 ms2,000 ms
timeline1204 ms250 ms250 ms
topic comparison1209 ms250 ms250 ms
topic map11,905 ms2,000 ms2,000 ms
Generated-view result limits by view type
Generated viewCallsReached limitLimit-hit rate
evidence matrix500.0%
other22100%
latest100.0%
relationship graph100.0%
timeline100.0%
topic comparison100.0%
topic map100.0%

Reaching a limit is an intentional cost and readability boundary, not a failed answer. The generated view links to the full catalogue when a broader result set is available.

Publication guardrails

Ingestion quality

Latest weekly lint →
Broken wiki links1,721

165,559 authored links checked during indexing

Title-only entries0

New ingestion now fails closed instead of inventing body text

Future-dated entries0

Excluded from latest ordering and surfaced for maintenance

Missing source URLs0

32 generated wiki pages correctly have no external source

Stale entries5

Explicitly marked for review in frontmatter

Short bodies0

Under 160 characters; useful as a conservative review signal

What is measured

Index quality is computed once while the DGX/Spark-authored Markdown build is prepared, then stored with the atomic publication record. Ask quality comes from EVE lifecycle hooks, while reader performance comes from bounded browser events. Both store daily counters only.

Which documents are eligible for vectors

Published evidence needs a valid HTTP source, a non-future date, at least 100 normalized evidence characters and 12 meaningful words, and no known retrieval-failure placeholder. Identical content shares vectors by SHA. Stale evidence remains eligible but is visibly marked for review.

What is deliberately not measured here

No prompts, answers, IP addresses, session IDs, hashed visitor IDs, or quarantined entry text are retained for this page. Missing samples show “Collecting”; small reader samples are explicitly labelled “Low sample” instead of being presented as a quality verdict.