From 42646d86c34d20935eb19537a5b14639ea39a5a6 Mon Sep 17 00:00:00 2001 From: Torben Nehmer Date: Thu, 10 Sep 2026 23:39:16 +0200 Subject: [PATCH] README.md: Telemetrie-Abschnitt an den installationsformabhaengigen Default angepasst Files changed: - README.md --- README.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index ada03bf..55844ab 100644 --- a/README.md +++ b/README.md @@ -329,9 +329,17 @@ AGENTS.md's "Gates" section. ## Telemetry and evaluation -Every `wikitool` call appends an event to `reports/telemetry//trace.jsonl`, and the -hook files under `.github/hooks/` and `.vibe/` add what the agent did between those calls. -Nothing leaves the machine: `reports/` is gitignored and no exporter is configured. +In this checkout, every `wikitool` call appends an event to +`reports/telemetry//trace.jsonl`, and the hook files under `.github/hooks/` and +`.vibe/` add what the agent did between those calls. Nothing leaves the machine: `reports/` is +gitignored and no exporter is configured. + +**A distributed instance records nothing unless it asks to.** The default follows the +installation form - on for a git clone of this repo, where the traces are the stack's own +measuring instrument, off for a `dist export` tarball, where nobody ordered telemetry. Two +quantity caps apply either way: 5 MiB per session trace, and 250 session directories. +`wikitool doctor` reports which state a checkout is in and why; EVALS.md ยง "Whether it runs at +all" has the precedence rules and the opt-in file. That record is what makes it possible to ask how a session *worked*, not just what it left behind: