README.md: Telemetrie-Abschnitt an den installationsformabhaengigen Default angepasst
CI / verify (push) Successful in 52s
CI / verify (push) Successful in 52s
Files changed: - README.md
This commit is contained in:
@@ -329,9 +329,17 @@ AGENTS.md's "Gates" section.
|
|||||||
|
|
||||||
## Telemetry and evaluation
|
## Telemetry and evaluation
|
||||||
|
|
||||||
Every `wikitool` call appends an event to `reports/telemetry/<session>/trace.jsonl`, and the
|
In this checkout, every `wikitool` call appends an event to
|
||||||
hook files under `.github/hooks/` and `.vibe/` add what the agent did between those calls.
|
`reports/telemetry/<session>/trace.jsonl`, and the hook files under `.github/hooks/` and
|
||||||
Nothing leaves the machine: `reports/` is gitignored and no exporter is configured.
|
`.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
|
That record is what makes it possible to ask how a session *worked*, not just what it left
|
||||||
behind:
|
behind:
|
||||||
|
|||||||
Reference in New Issue
Block a user