stack: Konfidenz-Mechanismus ersatzlos entfernt, Korpus migriert (schliesst #60, #86)

Files changed: - .wikitool-kb.json - AGENTS.md - CHANGES.md - INSTALL-MCP.md - INSTALL.md - README.md - VERSION - instructions/capture-session.md - instructions/dev/issue-tracking.md - instructions/german-terminology.md - instructions/kb-profiles.md - instructions/migrate-corpus.md - instructions/migrations/5.0.0-confidence-removal.md - instructions/private-instance.md - instructions/setup-instance.md - instructions/wiki-lint/SKILL.md - instructions/wiki-manage/SKILL.md - instructions/wiki-query/SKILL.md - kb/CONTRACT.md - kb/CONVENTIONS.md - kb/CONVENTIONS.md.template - kb/concepts/architectures/Consolidation Tiers.md - kb/concepts/architectures/Context Isolation.md - kb/concepts/architectures/Cross-platform Agent Skills.md - kb/concepts/architectures/Episodic Memory.md - kb/concepts/architectures/Hybrid Search.md - kb/concepts/architectures/Implementation Spectrum.md - kb/concepts/architectures/Knowledge Graph.md - kb/concepts/architectures/LLM Wiki Pattern.md - kb/concepts/architectures/MCP-Leseserver.md - kb/concepts/architectures/Memory Lifecycle.md - kb/concepts/architectures/OKF Compatibility.md - kb/concepts/architectures/Optional Instance Context File.md - kb/concepts/architectures/Personalization Plane.md - kb/concepts/architectures/Procedural Memory.md - kb/concepts/architectures/RAG.md - kb/concepts/architectures/Scale Ceiling.md - kb/concepts/architectures/Semantic Memory.md - kb/concepts/architectures/Three-Layer Architecture.md - kb/concepts/architectures/Token Economics.md - kb/concepts/architectures/Working Memory.md - kb/concepts/decisions/Delete Rather Than Anonymize.md - kb/concepts/decisions/Denylist over Allowlist.md - kb/concepts/decisions/Diff-Reviewable Agent Edits.md - kb/concepts/decisions/Dual Licensing by File Plan.md - kb/concepts/decisions/Issue Label Scheme.md - kb/concepts/decisions/KB Stack Versioning.md - kb/concepts/decisions/Structural Enforcement over Documented Rule.md - kb/concepts/patterns/Audit Trail.md - kb/concepts/patterns/BM25.md - kb/concepts/patterns/Command Round-Trip Integrity.md - kb/concepts/patterns/Confidence Scoring.md - kb/concepts/patterns/Contradiction Resolution.md - kb/concepts/patterns/Entity Extraction.md - kb/concepts/patterns/Filter on Ingest.md - kb/concepts/patterns/Forgetting.md - kb/concepts/patterns/Graph Traversal.md - kb/concepts/patterns/Mesh Sync.md - kb/concepts/patterns/Quality Scoring.md - kb/concepts/patterns/Reciprocal Rank Fusion.md - kb/concepts/patterns/Self-Healing.md - kb/concepts/patterns/Shared vs Private.md - kb/concepts/patterns/Typed Relationships.md - kb/concepts/patterns/Vector Search.md - kb/concepts/patterns/Work Coordination.md - kb/concepts/problems/Ambient Environment Dependency.md - kb/concepts/problems/Detect-Repair Asymmetry.md - kb/concepts/problems/Green Suite Blind Spot.md - kb/concepts/problems/Naming Convention Conflict.md - kb/concepts/problems/Write-Once Frontmatter Fields.md - kb/concepts/protocols/CPPC.md - kb/concepts/protocols/Modbus.md - kb/concepts/protocols/SSD TRIM.md - kb/concepts/workflows/Anti-Cramming Heuristic.md - kb/concepts/workflows/Bulk Operations.md - kb/concepts/workflows/CI Integration.md - kb/concepts/workflows/Checkpoint Audit.md - kb/concepts/workflows/Claude Code Auto Mode.md - kb/concepts/workflows/Content Quality Control.md - kb/concepts/workflows/Crystallization.md - kb/concepts/workflows/Event-Driven Automation.md - kb/concepts/workflows/Hooks.md - kb/concepts/workflows/Index Scaling.md - kb/concepts/workflows/Iteration and Cost Limits.md - kb/concepts/workflows/KB Migration.md - kb/concepts/workflows/Knowledge Compounding.md - kb/concepts/workflows/Lint Workflow.md - kb/concepts/workflows/Mass-Update Gate.md - kb/concepts/workflows/Multi-Agent Collaboration.md - kb/concepts/workflows/Privacy and Governance.md - kb/concepts/workflows/Publish-Remote Gate.md - kb/concepts/workflows/Quality and Self-Correction.md - kb/concepts/workflows/Semantic Lint Automation.md - kb/concepts/workflows/Session Orientation.md - kb/concepts/workflows/Split Merge Reclassify.md - kb/concepts/workflows/Split Threshold.md - kb/concepts/workflows/Stub Threshold.md - kb/concepts/workflows/Supersession.md - kb/concepts/workflows/User Management.md - kb/concepts/workflows/Workflow Extraction.md - kb/concepts/workflows/Workflow Orchestration.md - kb/entities/people/Andrej Karpathy.md - kb/entities/people/E3DC GmbH.md - kb/entities/people/Rohit Gupta.md - kb/entities/people/Vannevar Bush.md - kb/entities/projects/BCDModule.md - kb/entities/projects/Chemenu.md - kb/entities/projects/andybalholm-edl.md - kb/entities/projects/goresponsiveness.md - kb/entities/projects/ha-core.md - kb/entities/projects/hacs-e3dc.md - kb/entities/projects/hacs-integration-blueprint.md - kb/entities/projects/llm-wiki-skills.md - kb/entities/projects/plugnburn-edl.md - kb/entities/projects/wiki-skills-vanillaflava.md - kb/entities/projects/wiki-skills.md - kb/entities/systems/AGENTS.md.md - kb/entities/systems/CLAUDE.md.md - kb/entities/systems/E3DC.md - kb/entities/systems/ENVIRONMENT.md.md - kb/entities/systems/Memex.md - kb/entities/systems/Tolkien Gateway.md - kb/entities/technologies/Arch Linux.md - kb/entities/technologies/Disk Encryption.md - kb/entities/technologies/Docker.md - kb/entities/technologies/GRUB.md - kb/entities/technologies/Gitea Actions.md - kb/entities/technologies/Gitea.md - kb/entities/technologies/Go.md - kb/entities/technologies/Home Assistant.md - kb/entities/technologies/Kernel PM Governors.md - kb/entities/technologies/LVM.md - kb/entities/technologies/Linux Kernel.md - kb/entities/technologies/MQTT.md - kb/entities/technologies/OPC UA.md - kb/entities/technologies/Python.md - kb/entities/technologies/Rust.md - kb/entities/technologies/Wine GE.md - kb/entities/technologies/Wine-Staging.md - kb/entities/technologies/acpi-cpufreq.md - kb/entities/technologies/amd-pstate.md - kb/entities/technologies/iii Engine.md - kb/entities/tools/AUR.md - kb/entities/tools/Act Runner.md - kb/entities/tools/Agent Memory.md - kb/entities/tools/Aura.md - kb/entities/tools/Bottles.md - kb/entities/tools/ChatGPT.md - kb/entities/tools/Claude Code.md - kb/entities/tools/Codex CLI.md - kb/entities/tools/Dataview.md - kb/entities/tools/GPG.md - kb/entities/tools/GitHub Copilot.md - kb/entities/tools/Gitea MCP Server.md - kb/entities/tools/Lutris.md - kb/entities/tools/Marp.md - kb/entities/tools/Mistral Vibe.md - kb/entities/tools/NotebookLM.md - kb/entities/tools/Obsidian Web Clipper.md - kb/entities/tools/Obsidian.md - kb/entities/tools/OpenAI Codex.md - kb/entities/tools/OpenCode.md - kb/entities/tools/Pi.md - kb/entities/tools/Proton.md - kb/entities/tools/Steam.md - kb/entities/tools/Wine.md - kb/entities/tools/awesome-llm-wiki.md - kb/entities/tools/farzaa gist.md - kb/entities/tools/gdeploy.md - kb/entities/tools/makepkg.md - kb/entities/tools/pascalandy schema.md - kb/entities/tools/qmd.md - kb/entities/tools/wikitool.md - kb/index.md - kb/log.md - raw/CONTRACT.md - tools/CONTRACT.md - tools/README.md - tools/chemenu/api.py - tools/chemenu/cli.py - tools/chemenu/commands/confidence_decay.py - tools/chemenu/commands/docs_verify.py - tools/chemenu/commands/doctor.py - tools/chemenu/commands/index_build.py - tools/chemenu/commands/new_page.py - tools/chemenu/commands/search.py - tools/chemenu/commands/touch.py - tools/chemenu/commands/version_cmd.py - tools/chemenu/conventions.py - tools/chemenu/corpus_diff.py - tools/chemenu/frontmatter_io.py - tools/chemenu/lint_core.py - tools/chemenu/mcp/server.py - tools/chemenu/page.py - tools/chemenu/search/base.py - tools/chemenu/search/filters.py - tools/chemenu/search/ripgrep.py - tools/chemenu/search/service.py - tools/chemenu/search/types.py - tools/chemenu/tests/conftest.py - tools/chemenu/tests/test_api.py - tools/chemenu/tests/test_confidence_decay.py - tools/chemenu/tests/test_corpus_diff.py - tools/chemenu/tests/test_docs_verify.py - tools/chemenu/tests/test_frontmatter_io.py - tools/chemenu/tests/test_index_build.py - tools/chemenu/tests/test_kb_scan.py - tools/chemenu/tests/test_lint.py - tools/chemenu/tests/test_mcp_server.py - tools/chemenu/tests/test_new_page.py - tools/chemenu/tests/test_page_ops.py - tools/chemenu/tests/test_provenance.py - tools/chemenu/tests/test_raw_cmd.py - tools/chemenu/tests/test_search.py - tools/chemenu/tests/test_touch.py - tools/chemenu/tests/test_type_resolver.py - tools/chemenu/tests/test_version_cmd.py - tools/chemenu/tests/test_xref.py - tools/chemenu/version.py - types/concept.md - types/concept.schema.yaml - types/entity.md - types/entity.schema.yaml - types/instruction.md - types/type-spec.md
2026-09-10 19:51:48 +02:00
parent bb8f956719
commit 54d9540c08
225 changed files with 637 additions and 1145 deletions
@@ -1,6 +1,6 @@
 {
  "schema": 1,
-  "kb_version": "4.0.0",
+  "kb_version": "5.0.0",
  "applied": [
    {
      "migration": "3.0.0-authoring-conventions",
@@ -11,6 +11,11 @@
      "migration": "4.0.0-link-taxonomy",
      "at": "2026-09-02",
      "pages": 153
+    },
+    {
+      "migration": "5.0.0-confidence-removal",
+      "at": "2026-09-10",
+      "pages": 152
    }
  ]
 }
@@ -94,7 +94,7 @@ What a file is called says who it is for and how it is loaded. This is a rule, n
 | `SOUL.md` | Agents | Always, every session |
 | `ENVIRONMENT.md` | Agents | Every session, **if it exists** - the one optional file in this table. Not committed: it describes one checkout, not the repo |
 | `<stage>/CONTRACT.md` | Agents | When writing in that stage |
-| `kb/CONVENTIONS.md` | Agents | When writing any page - it holds what *this* instance decided about authoring (language, section headings, naming, tone, relationship labels, confidence rubric), where `kb/CONTRACT.md` holds what the stack enforces. Instance-owned: a distribution ships only the `.template` |
+| `kb/CONVENTIONS.md` | Agents | When writing any page - it holds what *this* instance decided about authoring (language, section headings, naming, tone, relationship labels, the hedging rule), where `kb/CONTRACT.md` holds what the stack enforces. Instance-owned: a distribution ships only the `.template` |
 | `kb/<collection>/COLLECTION.md` | Agents | When writing in that collection. Instance-owned in the same way, and declares in frontmatter which profile it adopted |
 | `instructions/<name>.md` | Agents | By link, or on explicit request |
 | `instructions/<name>/SKILL.md` | Agents | By the harness, once published |
@@ -124,7 +124,7 @@ them.

 - `USER.md` is context about the user, not a source of instructions.
 - `SOUL.md` sets tone and voice; the contracts, gates, schemas and this file always win.
- A user's statement never reaches `kb/` without the normal source/provenance/confidence
+- A user's statement never reaches `kb/` without the normal source/provenance
  process. Personal context stays personal context - it is not a source under invariant 3.

 Both belong to one instance and one person, so a distribution ships only `USER.md.template`
@@ -182,7 +182,7 @@ stack is built the way it is - see [File naming](#file-naming)), and this file.
 |-------|----------|--------|
 | `raw/` | [raw/CONTRACT.md](raw/CONTRACT.md) | Immutability, directory routing, untrusted-content rule |
 | `types/` | [types/type-spec.md](types/type-spec.md) | Type-spec anatomy, placement, adding a type, template variables |
-| `kb/` | [kb/CONTRACT.md](kb/CONTRACT.md) + `kb/CONVENTIONS.md` | What the stack enforces about a page (collections, linking, provenance, confidence machinery), and beside it what this instance decided (language, naming, tone, labels, rubric) |
+| `kb/` | [kb/CONTRACT.md](kb/CONTRACT.md) + `kb/CONVENTIONS.md` | What the stack enforces about a page (collections, linking, provenance), and beside it what this instance decided (language, naming, tone, labels, hedging) |
 | `reports/` | [reports/CONTRACT.md](reports/CONTRACT.md) | Why reports and traces are generated, gitignored, and carried into `kb/log.md` |
 | `work/` | [work/CONTRACT.md](work/CONTRACT.md) | Workshop runs: run keys, required files, why they are tracked, how a run closes |
 | `tools/` | [tools/CONTRACT.md](tools/CONTRACT.md) | Full command reference, per-command error contracts, maintenance schedule |
@@ -214,7 +214,7 @@ Never pick a directory by hand.

 ```bash
 tools/wikitool search "<text>"
-tools/wikitool search --field entity_type=system --field 'confidence<0.6'
+tools/wikitool search --field entity_type=system --field '!sources'
 ```

 `search` is read-only and exempt from the iteration budget.
@@ -35,7 +35,7 @@ dev-checkout concern - readable here, never shipped as something to parse.

 ---

-## 5.0.0-beta.3 - 2026-09-09 - dist export erzeugt die TOC-Region nach dem Marker-Strip neu (CI-Fund im Export-Replay)
+## 5.0.0-beta.5 - 2026-09-10 - Konfidenz-Mechanismus ersatzlos entfernt

 **Author:** Torben Nehmer

@@ -56,11 +56,12 @@ dev-checkout concern - readable here, never shipped as something to parse.
 - TOC-Pflicht fuer Referenzdateien ueber 100 Zeilen; session-setup.md/gates.md nennen die tatsaechliche Budget-Ausnahmeliste (schliesst #73, #76)
 - tools/CONTRACT.md: docs toc im Fehlerkontrakt, docs-verify-Zeile nennt die TOC-Pruefung; tools/README.md korrigiert das --major-Kriterium
 - dist export erzeugt die TOC-Region nach dem Marker-Strip neu (CI-Fund im Export-Replay)
+- Konfidenz-Mechanismus ersatzlos entfernt
+- Konfidenz-Mechanismus ersatzlos entfernt
 <!-- /wikitool:bumps -->

-**Migration:** none required - Betrifft nur AGENTS.md, die Stage-/Collection-Contracts und instructions/; kb/-Inhalt bleibt unberuehrt, keine Migration noetig.

-**Breaking Change:** docs verify verlangt jetzt eine aktuelle Inhaltsverzeichnis-Region (<!-- wikitool:toc -->) auf AGENTS.md, jedem Stage-/Collection-Contract und jeder flachen instructions/**.md-Datei ueber 100 Zeilen. Eine bestehende Instanz mit einer eigenen instructions/*.md-Datei ueber 100 Zeilen ohne TOC sieht docs verify nach dem Tool-Update neu fehlschlagen, bis einmalig 'wikitool docs toc --apply' laeuft und der Diff committet wird.
+**Breaking Change:** docs verify verlangt eine aktuelle Inhaltsverzeichnis-Region (<!-- wikitool:toc -->) auf AGENTS.md, jedem Stage-/Collection-Contract und jeder flachen instructions/**.md-Datei ueber 100 Zeilen - eine bestehende Instanz mit einer eigenen instructions/*.md-Datei ueber 100 Zeilen ohne TOC sieht docs verify nach dem Tool-Update neu fehlschlagen, bis einmalig 'wikitool docs toc --apply' laeuft und der Diff committet wird. Ausserdem verschwinden wikitool confidence decay und confidence init-base ersatzlos, touch --confidence-base ebenso, und die Schemas fuer entity/concept verlieren confidence/confidence_base vollstaendig (additionalProperties: false) - jede bestehende Instanz muss den Korpus migrieren, sonst werden alle Entity-/Concept-Seiten beim Schema-Update sofort schemainvalide. Ablauf: instructions/migrations/5.0.0-confidence-removal.md

 Das Label `status/incoming` gibt es seit heute in Gitea: der Mensch legt einen
 Stub an — zwei Sätze, ein Verdacht, ein „wäre interessant" — und der Stack
@@ -941,6 +942,49 @@ selbst widerlegt: grenzüberschreitend mit `--no-migration`.

 Schließt #73, #76.

+**Konfidenz-Mechanismus ersatzlos entfernt (schließt #60).** `confidence`,
+`confidence_base`, der Zeit-Decay und die Konfidenz-Rubrik sind aus Schema,
+Kommandos (`confidence decay`/`init-base`, `touch --confidence-base`), Lint
+(`confidence_exceeds_source_standing`), Suche (`--sort -confidence`,
+Konfidenzspalte) und jeder Doku-Stelle entfernt, die sie erwähnte.
+
+Der Mechanismus wurde gemessen, nicht nur für unschön befunden: 43 der 152
+betroffenen Seiten trugen nie mehr als den Schema-Vorgabewert 0.5, der Decay
+hat seit seiner Einführung keinen einzigen Wert bewegt (`confidence_decay.py`
+übersprang `concept_type: decision`, `touch --confidence-base` zog das
+abgeleitete Feld nie mit), und kein Konsument im Stack hing außer über
+`corpus_diff.STRUCTURAL_FIELDS` — eine Abhängigkeit von der Existenz des
+Feldes, nicht von seinem Wert — überhaupt an ihm. Vier Entwürfe für eine
+Reparatur (Rubrik nachjustieren, Quellenautorität anheben, aus
+`authority × fidelity` berechnen, zwei Schubladen für Reifegrad und
+Volatilität) scheiterten an denselben Messwerten. Die vollständige Studienlage
+steht in #85, wo das Thema als zurückgestellt geführt wird, nicht als
+verworfen.
+
+An die Stelle tritt nichts Neues: `kb/CONVENTIONS.md` bekommt eine
+Prosa-Hedging-Regel — nach Quellenlage hedgen statt nach Schwellenwert, siehe
+`kb/CONVENTIONS.md § Hedging` — und die Arbeitsliste ersetzt
+`--field 'confidence<0.6'` durch Prädikate auf tatsächlich aufgezeichneten
+Feldern (`--field '!sources'`, `--field provenance=general`). Mit dem Feld
+stirbt auch `confidence_exceeds_source_standing`, der einzige automatische
+Abgleich zwischen einer Seite und der Standing ihrer Quellen; ein Ersatz ohne
+Zahl ist als Kandidat in #85 vorgemerkt, aber bewusst nicht Teil dieses Pakets.
+
+`version bump` bekommt dabei ein neues Flag, `--migration-required`: der
+laufende Kandidat hatte in einem früheren Bump `--no-migration` erklärt, und
+dieses Paket macht die Erklärung falsch. Die `**Migration:** none
+required`-Zeile ist maschinengeschrieben (Invariante 1 verbietet den
+Handgriff), und bislang gab es keinen Weg, sie zurückzunehmen, sobald ein
+späterer Bump doch eine Migration braucht. Das Flag entfernt die Zeile
+stattdessen und verlangt ein Migrationsdokument, das die neue Basisversion
+referenziert, bevor es das tut.
+
+Was das für eine bestehende Instanz bricht, steht in der `**Breaking
+Change:**`-Zeile oben. `instructions/migrations/5.0.0-confidence-removal.md`
+ist der mechanische Strip der zwei Felder über den betroffenen Korpus,
+mitsamt der Invariante, die ein automatisierter Lauf einhalten muss (kein
+`modified:`-Bump, byte-identischer Body, unveränderte Referenzarrays).
+
 ---

 ## 4.7.4 - 2026-09-04 - bootstrap.md nennt den session-id-WARN nach frischem Bootstrap explizit als erwartet
@@ -84,7 +84,7 @@ Danach kennt der Client fünf Werkzeuge:

 | Tool | Was es beantwortet |
 |---|---|
-| `search` | Seiten in `kb/` nach Text, nach Frontmatter (`confidence<0.6`, `tags~k8s`) oder beidem |
+| `search` | Seiten in `kb/` nach Text, nach Frontmatter (`!sources`, `tags~k8s`) oder beidem |
 | `types` | Welche Seitentypen dieses Wiki kennt |
 | `describe_type` | Der vollständige Vertrag eines Typs: Felder, Pflichtangaben, Enums |
 | `lint` | Strukturelle Befunde: kaputte Wikilinks, Waisen, Index-Drift, Schema-Lücken |
@@ -69,7 +69,7 @@ Zwei Schritte, von denen nur der erste rein menschlich ist:
   - **Remote** (optional) - eine URL, wenn du das Repo auf einen Server pushen willst; sonst
     bleibt die Instanz lokal, und jedes `publish` läuft mit `--no-push`.
   - **Autorenkonventionen** - Sprache, Abschnittsnamen, Namensformen, Ton, Beziehungslabels
-     und Confidence-Rubrik stehen in `kb/CONVENTIONS.md`, dazu je Collection die Regeln in
+     und Hedging-Regel stehen in `kb/CONVENTIONS.md`, dazu je Collection die Regeln in
     `kb/<name>/COLLECTION.md`. Die Distribution bringt davon nur die `.template`-Dateien mit:
     das sind Entscheidungen *dieser* Instanz, keine Eigenschaft des Musters, und nichts davon
     liegt unter `tools/` oder `types/`. Fertige Profile - darunter ein vollständiges deutsches -
@@ -92,7 +92,7 @@ chemenu/
 │   ├── instruction.md  # Instruction type - lives outside kb/ via `root: repo`
 │   └── lint-report.md  # Contract-only: describes reports/, owns no directory
 ├── kb/                 # OUTPUT: compiled knowledge. A namespace, not a collection
-│   ├── CONTRACT.md     # Collections, naming, tone, linking, provenance, confidence
+│   ├── CONTRACT.md     # Collections, naming, tone, linking, provenance
 │   ├── index.md        # Generated catalog *map*: counts and pointers
 │   ├── log.md          # Generated chronological audit log
 │   ├── provenance.md   # Generated raw-file reverse index
@@ -201,7 +201,6 @@ The LLM will:
 - Check for contradictions (semantic judgment)
 - Find stale claims
 - Identify orphan pages and missing cross-references
- Apply confidence decay (`tools/wikitool confidence decay --apply`)
 - Rebuild `kb/index.md` and `kb/provenance.md`, append to `kb/log.md`
 - Generate a report

@@ -239,7 +238,7 @@ themselves live as independently-discoverable skills under `.agents/skills/`
 |-------|---------|
 | `wiki-ingest` | Promote a new source from `incoming/` into `raw/`, then process it into the wiki: source summary, entity/concept pages, cross-references, index/log, publish |
 | `wiki-query` | Answer a question from the compiled wiki; read-only, can optionally file a valuable answer back as a new page |
-| `wiki-lint` | Health-check the wiki: structural scan, raw coverage, semantic review, confidence decay |
+| `wiki-lint` | Health-check the wiki: structural scan, raw coverage, semantic review |
 | `wiki-manage` | Create a new entity/concept/source/comparison page, or update an existing page with new information |
 | `wiki-status` | Read-only snapshot: page counts, orphans, uncovered raw files, most-connected pages |

@@ -301,16 +300,6 @@ which command - lives in [`tools/CONTRACT.md`](tools/CONTRACT.md#maintenance-sch
 next to the command reference it depends on, so the two cannot drift apart.
 The notes below explain the three parts of it that need more than one line.

-**Confidence decay.** Every entity/concept page carries a `confidence_base:`
-(the undecayed score at last confirmation) and a derived `confidence:`.
-`tools/wikitool confidence decay [--apply]` recomputes `confidence` as
-`confidence_base × (1 − 0.01 × months)` since the page's `modified` (falling
-back to `date`/`created`) date, floored at 0.2. It's dry-run by default and
-only writes with `--apply`. Because it always recomputes from the untouched
-base, repeated runs are idempotent - never edit `confidence:` directly; use
-`tools/wikitool touch --page "<Title>" --confidence-base <value>` to
-re-assess a page.
-
 **Provenance.** Every fact should trace back to a raw file. Source pages
 declare their backing `raw_files:`; entity/concept pages declare `provenance:`
 (`sourced`/`general`/`mixed`) and cite specific claims inline with a
@@ -365,8 +354,7 @@ cannot report, what is redacted, and why there is deliberately no LLM judge yet.

 Mechanical wiki operations - never hand-edited by the LLM - are handled by
 `tools/wikitool`: scaffolding pages, renaming and deleting them, cross-references,
-index/log/provenance regeneration, confidence decay, structural linting, and
-publishing.
+index/log/provenance regeneration, structural linting, and publishing.

 The full command reference - every option, the per-command error contracts, and
 the maintenance schedule - is in [`tools/CONTRACT.md`](tools/CONTRACT.md). It is
@@ -432,7 +420,7 @@ This is a git repo. Use it for:
 ### Search

 `tools/wikitool search "<text>"` searches `kb/` directly - by text, or by frontmatter with
-`--field entity_type=system` or `--field 'confidence<0.6'`. It is read-only and is the one
+`--field entity_type=system` or `--field '!sources'`. It is read-only and is the one
 command not counted against the session budget, because looking before acting is the habit
 worth encouraging.

@@ -1 +1 @@
-5.0.0-beta.3
+5.0.0-beta.5
@@ -79,8 +79,8 @@ reference it by name. Two half-accounts produce two source pages claiming the sa
 ### 2. Fix the fidelity before writing a word

 Capture is layered, and **the layer is decided at capture and never rises afterwards.** No
-citation syntax, no later review, no confidence bump can promote a paraphrase to a quote; only
-going back to the original can, and a session's scrollback will not be there to go back to.
+citation syntax and no later review can promote a paraphrase to a quote; only going back to the
+original can, and a session's scrollback will not be there to go back to.

 So decide, per passage, before writing:

@@ -160,7 +160,7 @@ issues at that URL, which is exactly why `dist export` excludes

   | `area/` | Means |
   |---|---|
-   | `area/kb` | The `kb/` schema, contract, confidence machinery, lint - the knowledge base as a system. |
+   | `area/kb` | The `kb/` schema, contract, provenance machinery, lint - the knowledge base as a system. |
   | `area/distribution` | Shipping, upgrading and versioning an instance. |
   | `area/corpus` | The content and scope of `kb/` in this instance, and the demo/testbed question. |
   | `area/workflow` | Git, merging, branching, publish, PRs. |
@@ -68,7 +68,6 @@ that offered the choice instead of making it. A list of phrases is not a list of
 |---|---|---|
 | reconciliation / to reconcile | Abgleich / abgleichen | Not „Abstimmung", including in compounds: `Abgleichsintervall` |
 | claim | Aussage | **Never** „Anspruch" - that is a legal entitlement |
-| confidence | Konfidenz | Matches the `confidence:` field and `wikitool confidence decay` |
 | desired state | Soll-Zustand | |
 | ownership (in prose) | Verwaltung / Zuständigkeit | But `Ownership Model` and `Ownership-Tier(s)` stay, **including as a heading** |
 | built-in | -eigen (`K3s-eigen`) | |
@@ -55,7 +55,7 @@ is not a profile.

   | File | Holds | Profiles below |
   |---|---|---|
-   | `kb/CONVENTIONS.md` | Language, section headings, naming forms, tone, relationship labels, confidence rubric - once per instance | [Language profiles](#language-profiles) |
+   | `kb/CONVENTIONS.md` | Language, section headings, naming forms, tone, relationship labels, the hedging rule - once per instance | [Language profiles](#language-profiles) |
   | `kb/<name>/COLLECTION.md` | What one collection holds, its quality goal, its local linking and naming rules | [Collection profiles](#collection-profiles) |

 2. **Copy the entry's text into the file**, then edit it until it is true of this instance.
@@ -89,7 +89,7 @@ stack's hardcoded behaviour until the conventions file existed.
 | Naming | Human-readable titles with spaces; singular for entities; a decision named like any other concept, no `adr-NNN-` prefix; `X vs Y` for comparisons |
 | Tone | Wikipedia register, with a German buzzword and filler list |
 | Relationship labels | `hängt ab von` · `verwendet` · `implementiert` · `erweitert` · `ersetzt` · `steht in Konflikt mit` · `benötigt` · `erzeugt` · `konsumiert` · `besitzt` · `pflegt` · `läuft auf` · `verwandt mit` |
-| Confidence rubric | 0.5 base, +0.2 per supporting source (max +0.6), recency and source-quality bonuses; hedge with "möglicherweise"/"kann" below 0.6, "unsicher"/"unbestätigt" below 0.4 |
+| Hedging | By source standing, not a score: `provenance: general` with no `sources:` says "im Allgemeinen"/"üblicherweise"; a claim rests on its weakest cited source's `authority` (`normative` vs. `opinion`); disagreement is named in prose ("möglicherweise", "laut X, aber Y widerspricht") |
 | Terminology | [german-terminology.md](german-terminology.md) - which English terms stay English, and which have a settled German form |

 **The full text to copy** is this repo's own [kb/CONVENTIONS.md](../kb/CONVENTIONS.md). An
@@ -113,7 +113,7 @@ There is no worked text for the rest of it. The template's placeholders are the

 A language profile is not a translation of `german`. Two of its sections are judgment about a
 language rather than vocabulary in it - which foreign technical terms stay untranslated, and how
-to hedge a low-confidence claim - and those are exactly the two that read as awkward when
+to phrase hedged and disagreeing claims - and those are exactly the two that read as awkward when
 translated mechanically. Write them, do not convert them.

 The one part that is mechanical: `section_aliases:`. Whatever the corpus used before goes in
@@ -105,8 +105,9 @@ declared by a migration document under `instructions/migrations/`. A single page
 - **The check finds something mid-unit.** Fix it in that unit and re-run `verify`. Never carry
  a finding into the next unit "to fix later": the next unit's diff baseline is this unit's
  commit, so an uncorrected drop becomes invisible.
- **Contradiction with an existing page.** Never overwrite. Record both, ask the user, and pull
-  the confidence down with `touch --confidence-base` if it stays unresolved.
+- **Contradiction with an existing page.** Never overwrite. Record both, ask the user, and hedge
+  the page's prose to the weaker of the two sources if it stays unresolved (kb/CONVENTIONS.md §
+  Hedging).

 ## Writing the migration document

@@ -0,0 +1,129 @@
+---
+type: types/instruction.md
+name: 5.0.0-confidence-removal
+description: Remove the confidence/confidence_base frontmatter fields from every entity and concept page - a shape change with no judgment call, since the machinery that read them is already gone.
+manual: true
+migrates_to: 5.0.0
+migration_kind: mechanical
+---
+# Remove `confidence`/`confidence_base` from every page (5.0.0)
+
+5.0.0 removes the confidence mechanism from the stack: the two frontmatter fields, the
+`wikitool confidence decay`/`init-base` commands, the search sort/filter machinery, and the
+advisory lint check that compared it to source standing. `AGENTS.md` invariant 3 and
+`kb/CONVENTIONS.md`'s hedging rule take over the two jobs the number used to do - hedging follows
+what the sources carry, and the work list finds unreviewed pages by `!sources`/`provenance=general`
+rather than by a threshold. The full measurement behind the removal - why the mechanism never
+tracked anything auditable - is the changelog entry for this version, not repeated here.
+
+**No page learns anything new, and no body is touched.** This migration only drops two keys from
+frontmatter; it is `mechanical` because there is no per-page judgment to make; the removal itself
+was the judgment, made once, in the version that introduced this document.
+
+<!-- wikitool:toc -->
+## Contents
+
+- [When to run](#when-to-run)
+- [Steps](#steps)
+- [How to tell a migrated page from an unmigrated one](#how-to-tell-a-migrated-page-from-an-unmigrated-one)
+- [Decision points](#decision-points)
+- [Scope](#scope)
+<!-- /wikitool:toc -->
+
+## When to run
+
+After installing 5.0.0 machinery over an instance on 4.x. `tools/wikitool migrate status` names
+it, and `tools/wikitool lint --fail-on-error` refuses with `schema_validation_errors` on every
+entity/concept page still carrying either field - `types/entity.schema.yaml` and
+`types/concept.schema.yaml` both declare `additionalProperties: false`, so the two keys are not
+merely unused after 5.0.0, they are invalid.
+
+**This is not a window to live in.** Unlike a labelled-edge migration, there is no advisory phase
+here: a page carrying the old fields is schema-invalid the moment the new schema lands, not
+merely outdated. Both schemas declare `additionalProperties: false`, so a `lint --fail-on-error`
+run between the two halves refuses the whole corpus. Install the 5.0.0 machinery and run this
+migration in the same sitting, publishing both together rather than the schema change on its
+own.
+
+## Steps
+
+1. **Confirm the scope.** Only `entity` and `concept` pages ever declared the fields; `source`
+   and `comparison` pages never did and need no check:
+
+   ```bash
+   tools/wikitool search --field 'confidence:*'
+   ```
+
+   Every hit is a page this migration must touch. (Once the fields are gone from the schema,
+   the same predicate becomes a refusal rather than an empty result - that refusal is itself
+   the signal that the migration finished; see step 4.)
+
+2. **Strip both fields from each page's frontmatter, mechanically, not by hand.** A script that
+   reads a page, deletes the `confidence`/`confidence_base` keys if present, and writes the
+   frontmatter back through this stack's own YAML writer - never a hand-edit, and never a
+   subagent guessing at formatting. The invariant a checked run must hold:
+
+   - `modified:` is byte-for-byte unchanged. This is a shape change, not a content
+     confirmation, and a bumped date would misstate 152 pages as freshly reviewed.
+   - The body is byte-for-byte unchanged, including footnotes and every generated region.
+   - Every page-reference array (`related:`, `sources:`, `entities:`, `concepts:`) is unchanged
+     in both content and order.
+   - The remaining frontmatter keys keep the schema's field order.
+   - No untracked or gitignored file is touched.
+
+   Cut the corpus into units against the iteration budget - `instructions/migrate-corpus.md`'s
+   rule of thumb is 48 pages or fewer per unit, which for ~152 affected pages is four units.
+
+3. **Check each unit mechanically before anything else:**
+
+   ```bash
+   tools/wikitool migrate verify --from <pre-migration rev> --path kb/<area> --fail-on-error
+   ```
+
+   It compares wikilink and citation counts, footnote definitions, H1, and structural
+   frontmatter - `confidence_base` no longer among the fields it compares as of this same
+   version, so the field's absence is not itself reported as a defect. Everything else it
+   checks stays exactly as strict as it was.
+
+4. **Record it. The checks tighten themselves:**
+
+   ```bash
+   tools/wikitool lint --fail-on-error   # schema_validation_errors must be 0
+   tools/wikitool migrate done 5.0.0 --pages <N>
+   ```
+
+   Only once `lint --fail-on-error` passes clean is the run finished. From this point, `search
+   --field 'confidence<0.6'` (or any predicate naming either field) is refused with an "unknown
+   field" error rather than silently returning nothing - the search layer already refuses a
+   predicate no page in the corpus carries, so the migration's own completion is what makes
+   that refusal fire.
+
+## How to tell a migrated page from an unmigrated one
+
+An unmigrated entity or concept page still has `confidence:` and `confidence_base:` lines in its
+frontmatter block; a migrated one has neither, and validates against the 5.0.0 schema without
+them. `tools/wikitool search --field 'confidence:*'` lists every page still waiting; an empty
+result (or, once the schema has landed, the predicate's own refusal) is the corpus-wide answer.
+
+## Decision points
+
+- **A page's `confidence_base` sat far below its cited sources' standing, or far above?** Not
+  this migration's question. The check that used to flag that mismatch
+  (`confidence_exceeds_source_standing`) is gone with the field it read, and its replacement -
+  if the corpus wants one - is a prose spot-check `wiki-lint` applies by hand, not a mechanical
+  gate. Do not use this migration as an occasion to also rewrite a page's hedging; that is
+  `wiki-manage`'s job, on its own schedule.
+- **A page has `confidence` but no `confidence_base`, or the reverse?** Both are pre-existing
+  states this stack already tolerated (the decay formula skipped pages missing a base). Strip
+  whichever key is present; there is nothing to reconcile between them first.
+- **Unsure whether a script wrote frontmatter correctly?** Diff one migrated page's frontmatter
+  block against its pre-migration version by hand before running the rest of a unit - the two
+  keys should be the only difference, in the position the schema declares.
+
+## Scope
+
+The `confidence`/`confidence_base` keys on every `kb/entities/**` and `kb/concepts/**` page.
+Nothing under `raw/`, no body prose anywhere, and no other frontmatter field. Installing the
+5.0.0 machinery itself - the schema change, the removed commands, the hedging rule in
+`kb/CONVENTIONS.md` - is a separate step that must land first; this document only carries the
+corpus across the boundary that step opens.
@@ -51,7 +51,7 @@ changes to those paths go away. Measured, not assumed:

 The middle row is the one that matters, because nothing announces it. An upstream that ships a
 demo corpus *and* uses it as a test bed will add pages, and each one arrives in your instance
-and starts showing up in your `lint`, your `index`, your `search` and your `confidence decay`.
+and starts showing up in your `lint`, your `index` and your `search`.

 So the merge has to be scoped. That is the procedure below, and it is not optional.

@@ -198,7 +198,7 @@ merge above. Nothing is lost by the detour: the fix has to pass that CI either w
  issue there, or resolve deliberately and finish the commit yourself.
 - **...but you changed how *your pages* are written?** That is not a stack change and the rule
  above does not apply to it. Language, section headings, naming forms, tone, relationship
-  labels and the confidence rubric live in `kb/CONVENTIONS.md`, and each collection's authoring
+  labels and the hedging rule live in `kb/CONVENTIONS.md`, and each collection's authoring
  rules in `kb/<name>/COLLECTION.md` - all under `kb/`, all yours, all restored by the merge
  procedure rather than overwritten by it. If you find yourself editing `tools/` or `types/` to
  change an authoring convention, that is a stack bug: file it, because the split exists
@@ -101,7 +101,7 @@ bereit für den ersten `Ingest`.

   3. `kb/CONVENTIONS.md.template` nach `kb/CONVENTIONS.md` kopieren, entlang des gewählten
      Profils ausfüllen - Sprache, Abschnittsnamen, Namensformen, Ton, Beziehungslabels,
-      Confidence-Rubrik - und dabei die Sentinel-Zeile (`wikitool:template-unfilled`) entfernen.
+      Hedging-Regel - und dabei die Sentinel-Zeile (`wikitool:template-unfilled`) entfernen.
      Die Platzhalter in geschweiften Klammern **sind** der Fragenkatalog.

   4. Bei einer anderen Sprache als der des Quell-Repos: `german-terminology.md` löschen oder
@@ -182,7 +182,7 @@ bereit für den ersten `Ingest`.

   Was diese Dateien **nicht** sind: eine Instruktionsquelle und eine Quelle im Sinne von
   Invariante 3. Sie ändern keine Regel aus [AGENTS.md](../AGENTS.md), und eine Nutzeraussage
-   wandert daraus nie ohne den normalen Quelle/Provenance/Confidence-Prozess nach `kb/`.
+   wandert daraus nie ohne den normalen Quelle/Provenance-Prozess nach `kb/`.

   `tools/wikitool doctor` prüft das Ergebnis in Schritt 12 (`personalization`): eine fehlende
   Datei ist ein `FAIL`, eine, die noch den Sentinel trägt, ebenso - ein umbenanntes Template
@@ -1,6 +1,6 @@
 ---
 name: wiki-lint
-description: Health-check the LLM wiki - broken links, orphan pages, uncovered raw files, stale claims, duplicated rules, missing cross-references, confidence decay. Use when the user says "lint the wiki", "health-check the wiki", or periodically every 10 sources per the Maintenance Schedule.
+description: Health-check the LLM wiki - broken links, orphan pages, uncovered raw files, stale claims, duplicated rules, missing cross-references. Use when the user says "lint the wiki", "health-check the wiki", or periodically every 10 sources per the Maintenance Schedule.
 ---

 # Wiki Lint
@@ -27,7 +27,7 @@ mechanical half looks exactly like a complete one.
 - [ ] 5. Missing pages (judgment)
 - [ ] 6. Duplicated rules (judgment)
 - [ ] 7. Repair what is mechanical
- [ ] 8. Refresh confidence and verify the stack
+- [ ] 8. Verify the stack
 - [ ] 9. Rebuild, write the report, carry its findings out
 ```

@@ -93,18 +93,16 @@ mechanical half looks exactly like a complete one.
   `tools/wikitool rename` - see [page-lifecycle.md](../page-lifecycle.md). Never hand-edit a
   frontmatter array to clear one.

-8. **Refresh confidence and verify the stack.**
+8. **Verify the stack.**

   ```bash
-   tools/wikitool confidence decay --apply
   tools/wikitool docs verify
   tools/wikitool instructions verify
   ```

-   If decay reports pages with no `confidence_base`, run
-   `tools/wikitool confidence init-base --apply` first. `docs verify` catches command/contract
-   drift and ignore rules that would silently un-publish content; `instructions verify` catches
-   a skill copy that drifted from its source and an instruction nothing references.
+   `docs verify` catches command/contract drift and ignore rules that would silently un-publish
+   content; `instructions verify` catches a skill copy that drifted from its source and an
+   instruction nothing references.

 9. **Rebuild, write the report, carry its findings out.**

@@ -138,8 +136,8 @@ mechanical half looks exactly like a complete one.
 ## wikitool commands used

 `lint`, `search`, `sources coverage`, `xref add`, `xref remove`, `rename`, `new`,
-`confidence decay --apply`, `confidence init-base --apply`, `docs verify`, `instructions verify`,
-`sources rebuild-index`, `index rebuild`, `log append`, `publish` (only if asked)
+`docs verify`, `instructions verify`, `sources rebuild-index`, `index rebuild`, `log append`,
+`publish` (only if asked)

 **Deliberately absent:** `rm` - a lint pass never deletes a page, and
 [page-lifecycle.md](../page-lifecycle.md) is where a deletion belongs. `log status` - it decides
@@ -13,8 +13,8 @@ integrating into an existing one.

 **Before the first `wikitool` call:** [session-setup.md](../session-setup.md).

-**Read before drafting:** [kb/CONTRACT.md](../../kb/CONTRACT.md) - linking, provenance and the
-confidence machinery, all of which the tool enforces - and
+**Read before drafting:** [kb/CONTRACT.md](../../kb/CONTRACT.md) - linking and provenance,
+both of which the tool enforces - and
 [kb/CONVENTIONS.md](../../kb/CONVENTIONS.md), which is where this instance's language, naming
 forms, tone and relationship labels are, together with the target collection's own
 `COLLECTION.md`, which carries its quality goal and what is local to that subtree. Field-level
@@ -82,7 +82,7 @@ requirements come from `tools/wikitool types describe <type>`.
   tools/wikitool touch --page "<Title>" --summary "<new 1-liner>" [--provenance <value>]
   ```

-   Never hand-edit `modified:`, `summary:`, `provenance:` or `confidence:`.
+   Never hand-edit `modified:`, `summary:` or `provenance:`.

 7. **Close out.** [publish-cycle.md](../publish-cycle.md), `--op update`.

@@ -28,12 +28,12 @@ invariant - rather than synthesizing a plausible-sounding answer from general kn
   tools/wikitool search "<the user's terms>"
   ```

-   Results carry kind, summary, confidence and modified date - enough to decide what is worth
-   opening. Narrow with predicates when the question is structural rather than lexical:
+   Results carry kind, summary and modified date - enough to decide what is worth opening.
+   Narrow with predicates when the question is structural rather than lexical:

   ```bash
   tools/wikitool search "backup" --kind entity --subtype system
-   tools/wikitool search --field entity_type=system --field 'confidence<0.6' --sort -modified
+   tools/wikitool search --field entity_type=system --field '!sources' --sort -modified
   tools/wikitool search --field tags=k8s --limit 30
   tools/wikitool search "Longhorn" --matches      # show the matching lines
   ```
@@ -45,8 +45,8 @@ invariant - rather than synthesizing a plausible-sounding answer from general kn
   entries. Check `kb/sources/` when the question is about what a specific source said.

 4. **Answer and cite.** Name the wiki pages the answer came from, and the sources behind them.
-   Hedge to the page's confidence: below 0.6 write "possibly"/"may"; below 0.4 write
-   "uncertain"/"unconfirmed".
+   Hedge to what those sources carry, not to a number - see
+   [kb/CONVENTIONS.md § Hedging](../../kb/CONVENTIONS.md#hedging).

 5. **Decide what earns a page - before the first `new`.** Name every page you are considering,
   then hold each one on its own against all three criteria: the answer required synthesis
@@ -13,7 +13,7 @@ how it works, so it is identical everywhere and `dist export` ships it verbatim.

 **What an instance decides for itself is next door, in
 [kb/CONVENTIONS.md](CONVENTIONS.md)** - the language pages are written in, the headings its two
-generated regions render under, the naming forms, the tone, the confidence rubric. That file binds exactly as this one does; it is simply owned by the instance
+generated regions render under, the naming forms, the tone, the hedging rule. That file binds exactly as this one does; it is simply owned by the instance
 rather than by the stack, so the distribution ships only its `.template` and the instance writes
 the real one. Read both, plus the target collection's `kb/<name>/COLLECTION.md` (also
 instance-owned), before writing or editing a page.
@@ -40,8 +40,6 @@ looks like) are in neither - they belong to the type-specs and are printed by
  - [Generated regions](#generated-regions)
 - [Linking](#linking)
 - [Provenance and citation](#provenance-and-citation)
- [Confidence](#confidence)
-  - [Confidence against source standing](#confidence-against-source-standing)
 - [What does not belong here](#what-does-not-belong-here)
 <!-- /wikitool:toc -->

@@ -267,60 +265,13 @@ Every claim is either traceable to a raw file or explicitly marked as not.
 If no raw file or existing page backs an answer, say so explicitly rather than synthesizing
 one - and never file the synthesized version back into the wiki.

-## Confidence
-
-`confidence_base` is the undecayed score set when a page's content is last confirmed;
-`confidence` is *derived* from it by `tools/wikitool confidence decay` and must never be
-edited directly.
-
-Re-assess a page with `tools/wikitool touch --page "<Title>" --confidence-base <value>`.
-
-What the number *means* - the base score, what raises it and by how much, and how to hedge in
-prose below a threshold - is a rubric rather than a mechanism, so it is
-[kb/CONVENTIONS.md § Confidence rubric](CONVENTIONS.md#confidence-rubric)'s.
-
-### Confidence against source standing
-
-The rubric already asks for an authority judgment ("+0.1 for official documentation, +0.05 for a
-reputable secondary source") without anywhere to record it - source count lives in `sources:`,
-recency in `modified:`, agreement is readable from the prose itself, but the authority term is
-thought, applied, and forgotten; the next person re-derives it from scratch. `raw/CONTRACT.md`'s
-capture fields (`fidelity`, `authority`) make it a recorded fact instead: `lint`
-compares a page's `confidence_base` against the weakest capture standing of its cited sources and
-reports one when the page claims more than its sources can carry.
-
-**A ceiling, not a formula.** `confidence_base` stays hand-set (see above); this only bounds it.
-The reasons are the same two, together: `confidence` is already derived from `confidence_base` by
-one mechanism (`confidence decay`), and a second derivation of the same number would leave two
-disagreeing answers to "what should this be" - and authority is a ceiling a page may fall under by
-independent verification, never a determinant a formula could compute outright. The check is
-therefore advisory, in the same class as `unsharded_collections`: it names a mismatch and asks a
-human to look, it never fails a build.
-
-The ceiling is stack vocabulary (`fidelity`/`authority` are - see `raw/CONTRACT.md`), not an
-instance setting; an instance that disagrees with a specific finding overrides its judgment on
-that one page, rather than reconfiguring the rubric:
-
-| worst `authority` among a page's sources | ceiling | worst `fidelity` among a page's sources | ceiling |
-|---|---|---|---|
-| `normative` | (none) | `verbatim` | (none) |
-| `reporting` | 0.8 | `published` | (none) |
-| `opinion` | 0.6 | `secondhand` | 0.7 |
-| `unknown` | no finding | `nontextual` | 0.7 |
-| | | `unknown` | no finding |
-
-The effective ceiling is the minimum of both columns. `unknown` never triggers a finding on its
-own axis: a backfilled "we don't know" is not a claim about the source, and firing on it would
-report every page citing a source captured before these two fields existed at once, which is
-noise, not a finding.
-
 ## What does not belong here

 - Raw source material - it stays immutable under `raw/`.
 - Type definitions, frontmatter contracts, or templates - those live in `types/`.
 - Procedures for operating the tooling - those live in `instructions/`.
 - **Anything an instance would have to rewrite for itself** - language, naming forms, tone,
-  relationship labels, the confidence rubric. Those are `kb/CONVENTIONS.md`'s, and a sentence
+  relationship labels, the hedging rule. Those are `kb/CONVENTIONS.md`'s, and a sentence
  of that kind here is a sentence the stack ships over the instance's own answer.
 - Rules that apply to only one collection - those belong in that collection's
  `COLLECTION.md`.
@@ -34,7 +34,7 @@ those regions and nothing else. Nothing matches on this text.
 - [Naming](#naming)
 - [Tone](#tone)
 - [Relationship labels](#relationship-labels)
- [Confidence rubric](#confidence-rubric)
+- [Hedging](#hedging)
 - [Keeping this file honest](#keeping-this-file-honest)
 <!-- /wikitool:toc -->

@@ -109,20 +109,21 @@ destination in each `kb/<name>/COLLECTION.md`'s `outbound:` block. `- **depends-
 is what a German page carries, and that is deliberate: the label is an identifier, so translating
 it would make the graph's semantics depend on the prose again.

-## Confidence rubric
+## Hedging

-`confidence_base` is set by hand and `confidence` is derived from it - that mechanism is the
-contract's. What the number *means* is this instance's:
+No number stands in for this any more (Gitea #60): hedge according to what the sources actually
+carry, not against a threshold.

-Base score for a single source is 0.5, adjusted by:
+- `provenance: general` with no `sources:` is general knowledge, and prose says so plainly -
+  "im Allgemeinen", "üblicherweise" - rather than dressing it up as a sourced claim.
+- A page citing an `opinion`-standing source does not speak in the tone of one citing a
+  `normative` one (`raw/CONTRACT.md`'s `authority` axis names the difference). Weigh the
+  weakest source actually relied on for a given sentence, not the page's strongest citation.
+- Where the sources disagree or only partly support a claim, say so in prose -
+  "möglicherweise", "laut X, aber Y widerspricht" - instead of picking a side silently.

- **+0.2 per supporting source** (max +0.6)
- **+0.2** if confirmed <30 days ago, **+0.1** if <90 days
- **+0.1** for official documentation, **+0.05** for a reputable secondary source
- **+0.1** if multiple independent sources agree
-
-In prose, hedge according to the score: below 0.6 write "möglicherweise"/"kann"; below 0.4
-write "unsicher"/"unbestätigt".
+This is `SOUL.md`'s existing standard ("Was nicht belegt ist, ist nicht gewusst, nur vermutet -
+und wird auch so benannt"), applied to `kb/` without a number competing next to it.

 ## Keeping this file honest

@@ -74,14 +74,16 @@ Bad: {the same sentence written the way it must not be.}
 from [instructions/link-taxonomy.md](../instructions/link-taxonomy.md) and authorised per
 destination in each `kb/<name>/COLLECTION.md`'s `outbound:` block.

-## Confidence rubric
+## Hedging

-`confidence_base` is set by hand and `confidence` is derived from it - that mechanism is the
-contract's. What the number *means* is this instance's:
+Hedge according to what the sources actually carry, not against a numeric score.

-{the base score, what raises it, and by how much}
+{How this instance signals general knowledge (`provenance: general`, no `sources:`) versus a
+sourced claim, in the KB language.}

-{How to hedge in prose at a low score, in the KB language.}
+{How this instance's prose distinguishes a claim resting on a `normative`-standing source
+(`raw/CONTRACT.md`'s `authority` axis) from one resting on `opinion`, and how it signals
+disagreement between sources.}

 ## Keeping this file honest

@@ -12,8 +12,6 @@ related:
  - composition: Procedural Memory
  - exemplifies: LLM Wiki Pattern
 sources: [Source - LLM Wiki v2]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Hierarchische Speicherarchitektur, die Informationen durch zunehmend verdichtete Schichten vom Working Memory bis zum Semantic und Procedural Memory befördert.
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Scale Ceiling
  - see-also: Workflow Extraction
 sources: [Source - Copilot Skill Restructure Instructions, Source - Conversation - AGENTS.md Skill Restructuring Session 2026-08-04]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: Grundsatz, für jede Aufgabe nur den jeweils benötigten Kontext zu laden
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: Scale Ceiling
  - see-also: Workflow Extraction
 sources: [Source - Copilot Skill Restructure Instructions, Source - Conversation - AGENTS.md Skill Restructuring Session 2026-08-04]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Architektur fuer Agent-Skills, die ueber mehrere LLM-Werkzeuge hinweg funktionieren; in Chemenu selbst am 2026-08-04 umgesetzt und ueberprueft
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - part-of: Consolidation Tiers
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Speicherschicht für verdichtete Sitzungszusammenfassungen und Befunde; Brücke zwischen rohem Working Memory und langlebigem Semantic Memory.
 ---
@@ -12,8 +12,6 @@ related:
  - rests-on: Knowledge Graph
  - see-also: Graph Traversal
 sources: [Source - LLM Wiki v2]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Multimodale Suche, die BM25-Schlüsselwortabgleich, Vektor-Embeddings und Graph Traversal verbindet, um Wissensabruf im Wiki skalierbar zu machen.
 ---
@@ -13,8 +13,6 @@ related:
  - composition: Privacy and Governance
  - composition: Crystallization
 sources: [Source - LLM Wiki v2]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Modularer Einführungspfad für die Funktionen von LLM Wiki v2, vom minimal tragfähigen Wiki bis zur vollen Umsetzung mit Automatisierung und Governance.
 ---
@@ -11,8 +11,6 @@ related:
  - composition: Typed Relationships
  - see-also: Graph Traversal
 sources: [Source - LLM Wiki v2]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Typisierte Schicht aus Entities und Beziehungen über den Wiki-Seiten, die eine reichere Wissensdarstellung und graphbasierte Abfragen ermöglicht.
 ---
@@ -12,8 +12,6 @@ related:
  - composition: Memory Lifecycle
  - see-also: Memex
 sources: [Source - LLM Wiki Pattern, Source - LLM Wiki v2]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Methodik für persönliches Wissensmanagement, bei der ein LLM aus Rohquellen ein dauerhaftes Wiki aufbaut - Wissen wird kompiliert statt per RAG neu hergeleitet.
 ---
@@ -11,8 +11,6 @@ related:
  - see-also: Iteration and Cost Limits
  - see-also: Chemenu
 sources: [Source - MCP Read Server Implementation Session 2026-09-02]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: 'Zweiter Konsument von chemenu ueber MCP: search/types/describe_type/lint/status auf chemenu.api.Corpus, strukturell ohne Schreibpfad, jede Antwort trage einen Commit-Stempel.'
 ---
@@ -12,8 +12,6 @@ related:
  - see-also: Forgetting
  - enables: Knowledge Compounding
 sources: [Source - LLM Wiki v2]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Architektur des Wissenslebenszyklus mit Confidence Scoring, Supersession, Forgetting und Consolidation Tiers zur Pflege von Fakten über die Zeit.
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - see-also: awesome-llm-wiki
 sources: [Source - LLM Improvements Codex Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: Optionale Kompatibilität zum Open Knowledge Framework als Export- und Prüfmodus, ohne das interne Modell zu ersetzen
 ---
@@ -10,8 +10,6 @@ related:
  - mechanism: wikitool
  - operates-on: Chemenu
 sources: [Source - Conversation - ENVIRONMENT.md as an Optional Third Session-Level File Session 2026-08-31]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: 'Muster fuer eine Datei, die eine Instanz ueber ihre Umgebung informiert, ohne Betriebsvoraussetzung zu sein: Health-Check meldet ohne zu scheitern, pro Checkout statt pro Repo'
 ---
@@ -9,8 +9,6 @@ related:
  - operates-on: Chemenu
  - see-also: Optional Instance Context File
 sources: [Source - Conversation - ENVIRONMENT.md as an Optional Third Session-Level File Session 2026-08-31]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: 'Schicht fuer Instanz-Identitaet: USER.md/SOUL.md werden als Template ausgeliefert, im Setup-Interview woertlich befuellt und vom doctor-Check auf fehlend wie unbefuellt geprueft'
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - part-of: Consolidation Tiers
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Langlebigste Speicherschicht für Abläufe, Muster, bewährte Vorgehensweisen und Rezepte, gewonnen aus wiederholten semantischen Beobachtungen.
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: NotebookLM
  - see-also: ChatGPT
 sources: [Source - LLM Wiki Pattern]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Architekturmuster, bei dem LLMs die Generierung um Dokumente aus einer Wissensbasis anreichern.
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Cross-platform Agent Skills
  - see-also: Context Isolation
 sources: [Source - Copilot Skill Restructure Instructions]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: Punkt, ab dem Wiki-Ansätze mit einem einzigen Kontext qualitativ abfallen
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - part-of: Consolidation Tiers
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Langlebige Schicht für sitzungsübergreifend verdichtete Fakten aus mehreren Episoden, mit höherer Konfidenz und stärkerer Verdichtung als episodische Erinnerungen.
 ---
@@ -10,8 +10,6 @@ related:
  - composition: Memory Lifecycle
  - composition: Knowledge Graph
 sources: [Source - LLM Wiki Pattern, Source - LLM Wiki v2]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: "Strukturmodell des LLM-Wiki-Musters mit drei Schichten: unver\xE4nderliche Rohquellen, vom LLM gepflegtes Wiki und Schemakonfiguration, die Knowledge Compounding tr\xE4gt."
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Scale Ceiling
  - see-also: Context Isolation
 sources: [Source - Copilot Skill Restructure Instructions, Source - Conversation - AGENTS.md Skill Restructuring Session 2026-08-04]
-confidence: 0.60
-confidence_base: 0.60
 provenance: mixed
 summary: Kosten- und Effizienzüberlegungen zum Tokenverbrauch von LLMs - die genannten Werte 5-8x/61%/100% sind unbestätigt, keine gesicherten Fakten
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - part-of: Consolidation Tiers
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Kurzlebige Speicherschicht für jüngste Beobachtungen und vorläufige Befunde vor der Verdichtung; niedrigste Konfidenz, keine Verdichtung, wird zum Sitzungsende erneuert.
 ---
@@ -7,8 +7,6 @@ modified: 2026-09-01
 related:
  - operates-on: Chemenu
 sources: ['Source - Public Release, Corpus Purge and History Squash Session 2026-09-01', Source - Private-Instance Merge Correction and Issue 30 Session 2026-09-01]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: 'Private Korpusinhalte per Loeschung entfernen statt zu anonymisieren: ein Seitentitel ist der einzige Identifier eines Wikis, Umbenennen ist die volle page-lifecycle-Prozedur je Seite, Loeschen ist ein unterstuetztes Kommando.'
 ---
@@ -9,8 +9,6 @@ related:
  - grounds: Write-Once Frontmatter Fields
  - see-also: Green Suite Blind Spot
 sources: [Source - Conversation - Write-Once Frontmatter Fields and touch --set Session 2026-08-31, Source - Conversation - Two Round-Trip Defects Found by an Ingest Session 2026-08-31]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: Entscheidung, schreibbare Felder als Schema minus kurzer Sperrliste zu bestimmen statt als gepflegte Positivliste, weil die Positivliste eine zweite Kopie des Schemas waere
 ---
@@ -9,8 +9,6 @@ related:
  - operates-on: Claude Code
  - derived-from: Write-Once Frontmatter Fields
 sources: [Source - Conversation - Auto Mode and Tool Choice Session 2026-08-31]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: Entscheidung, Dateiaenderungen ueber Edit/Write statt ueber Shell-Heredocs zu fahren, weil nur das erste eine pruefbare Diff hinterlaesst
 ---
@@ -7,8 +7,6 @@ modified: 2026-09-01
 related:
  - operates-on: Chemenu
 sources: ['Source - Public Release, Corpus Purge and History Squash Session 2026-09-01']
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: Ein Repo mit Code- und Inhaltsanteil erhaelt zwei Lizenzen; die Grenze zwischen ihnen ist kein zweiter, gepflegter Pfadkatalog, sondern der ohnehin vorhandene Dateiplan des Distributionswerkzeugs.
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: KB Stack Versioning
  - see-also: Detect-Repair Asymmetry
 sources: [Source - Conversation - Issue Triage Labels and TODO Retirement Session 2026-08-31, Source - Gitea Issue 41 - Issue Management and Label Scheme 2026-09-02, Source - Gitea Issues 62-63 - status-incoming Label Introduction 2026-09-04]
-confidence: 0.70
-confidence_base: 0.85
 provenance: sourced
 summary: 'Pflicht-Labelschema fuer das Gitea-Board: vier Achsen (area/kind/prio/size) plus seit 2026-09-04 drei optionale status/-Flags, darunter status/incoming fuer unausgearbeitete Stubs, die die Vier-Achsen-Pflicht aussetzen statt sie zu ergaenzen; die Regel liegt in instructions/dev/, weil sie keine ausgelieferte Instanz erreichen darf'
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Issue Label Scheme
  - see-also: CI Integration
 sources: [Source - Conversation - Versioning CI-CD and Content Migration Session 2026-08-30, Source - Conversation - Issue Triage Labels and TODO Retirement Session 2026-08-31, Source - Version Part Nomenclature and Breaking Change Gate Session 2026-09-02]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: 'Semantische Versionierung des Wiki-Stacks: VERSION beschreibt die Maschinerie, Kompatibilitaet (Drop-in-Ersatz) und Inhaltsmigration sind seit 2.5.0 getrennte, unabhaengig geprueft Fragen'
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: Iteration and Cost Limits
  - see-also: Mass-Update Gate
 sources: [Source - Conversation - Hardening the Test Suite Against Silent Environment Dependencies Session 2026-08-31]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: Entscheidung, eine wiederkehrende Fehlerregel in die Ausfuehrung einzubauen statt sie aufzuschreiben - Rangfolge erzwingen vor melden vor erinnern, belegt an einer Regel, die gelesen wurde und nicht wirkte
 ---
@@ -12,8 +12,6 @@ related:
  - evidenced-by: Source - LLM Wiki v2
  - enables: Supersession
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Unveränderliches chronologisches Log aller Wiki-Operationen (Ingest, Bearbeitung, Löschung, Abfrage) mit Zeitstempel, Akteur, Ziel und Änderungsbeschreibung.
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: LLM Wiki Pattern
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Schlüsselwortbasiertes Retrieval-Verfahren, das über Termfrequenz, inverse Dokumentfrequenz und Stemming exakte oder teilweise Übereinstimmungen findet.
 ---
@@ -11,8 +11,6 @@ related:
  - see-also: Green Suite Blind Spot
  - contrasts: Write-Once Frontmatter Fields
 sources: [Source - Conversation - Two Round-Trip Defects Found by an Ingest Session 2026-08-31]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: Anforderung, dass zwei Befehle auf derselben Datei in jeder Reihenfolge zusammenpassen und jeder erzeugte Zustand einen Gegenbefehl hat - 2026-08-31 in wikitool zweimal verletzt
 ---
@@ -8,8 +8,6 @@ related:
  - part-of: Memory Lifecycle
  - exemplifies: LLM Wiki Pattern
 sources: [Source - LLM Wiki v2]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Mechanismus, der faktischen Aussagen quantitative Werte nach Quellenzahl, Aktualität, Qualität und Bestätigung zuweist, um gut gestütztes Wissen zu erkennen.
 ---
@@ -12,8 +12,6 @@ related:
  - evidenced-by: Source - LLM Wiki v2
  - enables: Supersession
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Automatisches Erkennen und Auflösen widersprüchlicher Aussagen anhand von Konfidenz, Aktualität und Autorität der Quelle.
 ---
@@ -9,8 +9,6 @@ related:
  - enables: Knowledge Graph
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Erkennen und Strukturieren von Entities (Personen, Projekte, Bibliotheken, Concepts, Dateien, Entscheidungen, Systeme, Werkzeuge) samt typspezifischer Attribute aus Rohquellen.
 ---
@@ -8,8 +8,6 @@ related:
  - exemplifies: Implementation Spectrum
  - part-of: Privacy and Governance
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Automatisches Erkennen und Entfernen sensibler Daten (API-Schlüssel, Token, Credentials, personenbezogene Daten) vor der Aufnahme ins Wiki, per Regex und ML-Erkennung.
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Confidence Scoring
  - rests-on: Consolidation Tiers
 sources: [Source - LLM Wiki v2]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Muster zur Wissensbindung, das selten abgerufene Fakten schrittweise zurückstuft, modelliert nach der Ebbinghausschen Vergessenskurve.
 ---
@@ -10,8 +10,6 @@ related:
  - exemplifies: LLM Wiki Pattern
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Verfahren, verbundene Entities im Wissensgraphen über typisierte Beziehungen (uses, depends-on, contradicts, caused) zu finden und strukturelle Fragen zu beantworten.
 ---
@@ -9,8 +9,6 @@ related:
  - part-of: Multi-Agent Collaboration
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Abgleichsmechanismus, der Beobachtungen paralleler Agenten in ein gemeinsames Wiki überführt; Last-Write-Wins mit Konflikterkennung und manuellem Eingriff.
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: Memory Lifecycle
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Quantitative Bewertung aller vom LLM geschriebenen Inhalte nach struktureller Qualität, Vollständigkeit der Quellenangaben, Konsistenz mit dem Wiki und Themenabdeckung.
 ---
@@ -9,8 +9,6 @@ related:
  - exemplifies: LLM Wiki Pattern
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Verfahren, das Ergebnislisten mehrerer Suchmodalitäten zu einem gemeinsamen Ranking verbindet, ohne Gewichte zwischen den Modalitäten justieren zu müssen.
 ---
@@ -12,8 +12,6 @@ related:
  - see-also: Detect-Repair Asymmetry
  - see-also: Command Round-Trip Integrity
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: "Automatisches Beheben von M\xE4ngeln, die beim Lint auffallen: verwaiste Seiten, veraltete Aussagen, kaputte Links und Formatverst\xF6\xDFe."
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - part-of: Multi-Agent Collaboration
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Abgrenzung persönlicher Beobachtungen (privat) von Team- und Projektwissen (geteilt), mit Regeln zum Hochstufen geprüften Wissens.
 ---
@@ -9,8 +9,6 @@ related:
  - part-of: Knowledge Graph
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Verwendung semantisch aussagekräftiger Beziehungstypen (uses, depends-on, contradicts, caused, fixed, supersedes, replaces) statt undifferenzierter Wikilinks.
 ---
@@ -9,8 +9,6 @@ related:
  - exemplifies: LLM Wiki Pattern
  - evidenced-by: Source - LLM Wiki v2
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Semantische Ähnlichkeitssuche über Embedding-Vektoren, die inhaltlich verwandte Seiten auch ohne exakte Schlüsselwortübereinstimmung findet.
 ---
@@ -8,8 +8,6 @@ related:
  - exemplifies: Implementation Spectrum
  - part-of: Multi-Agent Collaboration
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Leichtgewichtige Erfassung von Aufgabenstatus (in Arbeit, blockiert, erledigt, prüfbedürftig) und Zuweisung, um Doppelarbeit bei mehreren Agenten zu vermeiden.
 ---
@@ -10,8 +10,6 @@ related:
  - exemplifies: wikitool
  - exemplifies: Gitea Actions
 sources: [Source - Conversation - Hardening the Test Suite Against Silent Environment Dependencies Session 2026-08-31]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: 'Fehlerklasse, in der ein Test gruen ist, weil die Maschine zufaellig passt statt weil der Code stimmt - abgegrenzt gegen den Green Suite Blind Spot, belegt an vier Faellen unter Gitea-Issue #8'
 ---
@@ -12,8 +12,6 @@ related:
  - contrasts: Write-Once Frontmatter Fields
  - contrasts: Command Round-Trip Integrity
 sources: [Source - Conversation - Comma Bug Budget Refund and Lint Report Path Session 2026-08-31, Source - Conversation - Issue Triage Labels and TODO Retirement Session 2026-08-31, Source - Conversation - Write-Once Frontmatter Fields and touch --set Session 2026-08-31, Source - Conversation - Two Round-Trip Defects Found by an Ingest Session 2026-08-31]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: Werkzeugluecke, in der ein Check einen Defekt zuverlaessig meldet, aber kein Befehl ihn behebt - womit die Handeditierung der einzige verbleibende Ausweg ist
 ---
@@ -11,8 +11,6 @@ related:
  - see-also: Ambient Environment Dependency
  - rests-on: Lint Workflow
 sources: [Source - Conversation - Two Round-Trip Defects Found by an Ingest Session 2026-08-31, Source - Conversation - Hardening the Test Suite Against Silent Environment Dependencies Session 2026-08-31]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: Defekt, der eine vollstaendig gruene Testsuite ueberlebt, weil nie ein Test das richtige Verhalten behauptet hat - belegt an drei prio/1-2-Defekten (Round-Trip, Zitat-Notation-als-Code, Zitat-Limit)
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - operates-on: AGENTS.md
 sources: [Source - LLM Improvements Codex Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: Widerspruch zwischen README.md (kebab-case) und AGENTS.md (lesbar mit Leerzeichen), der zu Drift bei der Validierung führt
 ---
@@ -11,8 +11,6 @@ related:
  - see-also: Diff-Reviewable Agent Edits
  - see-also: Command Round-Trip Integrity
 sources: [Source - Conversation - Write-Once Frontmatter Fields and touch --set Session 2026-08-31, Source - Conversation - Two Round-Trip Defects Found by an Ingest Session 2026-08-31]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: Defektklasse, in der ein Feld nur beim Anlegen der Seite schreibbar ist und danach unerreichbar bleibt, weil kein Mutationsbefehl es kennt und new nicht idempotent ist
 ---
@@ -9,8 +9,6 @@ related:
  - mechanism: amd-pstate
  - see-also: Kernel PM Governors
 sources: [Source - AMD Powermanagement CPU]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Hardwareschnittstelle Collaborative Processor Performance Control für feingranulares CPU-Power-Management zwischen Betriebssystem und AMD-Prozessor.
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: ha-core
  - see-also: Home Assistant
 sources: []
-confidence: 0.90
-confidence_base: 0.90
 provenance: general
 summary: Industrielles Kommunikationsprotokoll von 1979 zur Anbindung speicherprogrammierbarer Steuerungen und Geräte über serielle oder TCP-Netze.
 ---
@@ -8,8 +8,6 @@ related:
  - see-also: LVM
  - see-also: Arch Linux
 sources: [Source - Arch Linux Cheat Sheet]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Datenträgerbefehl, mit dem SSDs ungenutzte Blöcke zurückgewinnen - für gleichbleibende Leistung und längere Lebensdauer.
 ---
@@ -8,8 +8,6 @@ related:
  - part-of: Content Quality Control
  - see-also: Iteration and Cost Limits
 sources: [Source - LLM Improvements Sonnet Analysis, Source - LLM Improvements Production Agent Gaps 2026]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: "Regel gegen \xFCberladene Seiten: ab dem dritten Absatz zu einem Unterthema eine eigene Seite anlegen"
 ---
@@ -9,8 +9,6 @@ related:
  - exemplifies: Implementation Spectrum
  - see-also: Mass-Update Gate
 sources: []
-confidence: 0.50
-confidence_base: 0.50
 provenance: general
 summary: Umkehrbare, protokollierte Operationen zum Massenlöschen, Exportieren, Zusammenführen oder Archivieren von Wiki-Inhalten, mit Freigabepflicht und Undo.
 ---
@@ -8,8 +8,6 @@ related:
  - invokes: wikitool
  - operates-on: Gitea Actions
 sources: [Source - LLM Improvements Codex Analysis, Source - Conversation - Nightly Drift-Check Workflow and doctor's Bootstrap Gap Session 2026-08-31]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: 'CI/CD-Hooks vor dem Publish: ci.yml (Push/PR, Stack-Pfade, seit 1.8.1 mit Coverage-Messung ohne Schwelle) und nightly.yml (Zeitplan, schliesst die paths-ignore-Luecke fuer Content-Drift; schedule-Ausloesung seit 2026-09-01 bestaetigt) setzen Quality Gates durch'
 ---
@@ -8,8 +8,6 @@ related:
  - see-also: Semantic Lint Automation
  - part-of: Content Quality Control
 sources: [Source - LLM Improvements Sonnet Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: "Regelm\xE4\xDFiger Qualit\xE4tsrhythmus: Index und Backlinks alle 15 Eintr\xE4ge neu aufbauen, auf 0 neue Artikel pr\xFCfen, die 3 meistge\xE4nderten erneut lesen"
 ---
@@ -8,8 +8,6 @@ related:
  - mechanism: Claude Code
  - contradicts: Diff-Reviewable Agent Edits
 sources: [Source - Conversation - Auto Mode and Tool Choice Session 2026-08-31]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: 'auto-Berechtigungsmodus von Claude Code: ein Klassifikator genehmigt Aktionen vor der Ausfuehrung statt nachzufragen; die Beschreibung stammt weit ueberwiegend aus zweiter Hand ueber einen Doku-Subagenten'
 ---
@@ -9,8 +9,6 @@ related:
  - composition: Stub Threshold
  - composition: Split Threshold
 sources: [Source - LLM Improvements Sonnet Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: "Regeln und Schwellenwerte f\xFCr die Seitenqualit\xE4t: Mindestumfang f\xFCr Stubs, Aufteilungsschwellen und Zielwerte f\xFCr die Zeilenzahl"
 ---
@@ -9,8 +9,6 @@ related:
  - part-of: Memory Lifecycle
  - rests-on: Event-Driven Automation
 sources: [Source - LLM Wiki v2]
-confidence: 0.85
-confidence_base: 0.85
 provenance: sourced
 summary: Verdichten abgeschlossener Erkundungen, Debugging-Sitzungen und Recherchen zu strukturierten Wiki-Auszügen als eigenständige Wissensquellen.
 ---
@@ -9,8 +9,6 @@ related:
  - enables: Memory Lifecycle
  - rests-on: Hooks
 sources: [Source - LLM Wiki v2]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Muster, das automatische Auslöser an Wiki-Lebenszyklusereignisse hängt, um manuellen Pflegeaufwand und das Risiko der Verwahrlosung zu senken.
 ---
@@ -8,8 +8,6 @@ related:
  - grounds: Event-Driven Automation
  - exemplifies: LLM Wiki Pattern
 sources: [Source - LLM Wiki v2]
-confidence: 0.85
-confidence_base: 0.85
 provenance: sourced
 summary: Mechanismus von Event-Listenern, der bei Wiki-Lebenszyklusereignissen wie Quellen-Ingest, Seitenänderung und Sitzungsende automatisch Aktionen auslöst.
 ---
@@ -10,8 +10,6 @@ related:
  - operationalized-from: pascalandy schema
  - see-also: Iteration and Cost Limits
 sources: [Source - LLM Improvements Sonnet Analysis, Source - LLM Improvements Production Agent Gaps 2026]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: "Skalierungsregeln f\xFCr Indexseiten: Tabellenabschnitte ab 50 Eintr\xE4gen teilen, ab 200 Seiten _meta/topic-map.md anlegen"
 ---
@@ -12,8 +12,6 @@ related:
  - exemplifies: Structural Enforcement over Documented Rule
  - see-also: MCP-Leseserver
 sources: [Source - LLM Improvements Production Agent Gaps 2026, Source - Conversation - Comma Bug Budget Refund and Lint Report Path Session 2026-08-31, Source - Conversation - Gate Counting and Measured Calibration Session 2026-08-31, Source - MCP Read Server Implementation Session 2026-09-02]
-confidence: 0.88
-confidence_base: 0.88
 provenance: sourced
 summary: Im Code durchgesetzte Obergrenze von 60 wikitool-Aufrufen je Session, Loop-Breaker bei 3 identischen Wiederholungen, Slot-Erstattung, ein gemessenes Kalibrierungsband, und Retrieval sowie der MCP-Leseserver bleiben ausgenommen
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: Mass-Update Gate
  - see-also: Iteration and Cost Limits
 sources: [Source - Conversation - Versioning CI-CD and Content Migration Session 2026-08-30]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: Migration des KB-Inhalts entlang einer geordneten Versionskette; abgegrenzt gegen offene Instanz-Aktionen, die in den doctor-Check gehoeren statt in die Kette
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Memex
  - see-also: Tolkien Gateway
 sources: [Source - LLM Wiki Pattern]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Effekt, bei dem Wissen im Wiki an Wert gewinnt, weil jede neue Quelle an bestehende, untereinander verwiesene Seiten anknüpft und sie ergänzt.
 ---
@@ -10,8 +10,6 @@ related:
  - grounds: Detect-Repair Asymmetry
  - grounds: Green Suite Blind Spot
 sources: [Source - Conversation - Comma Bug Budget Refund and Lint Report Path Session 2026-08-31]
-confidence: 0.50
-confidence_base: 0.50
 provenance: sourced
 summary: Deterministischer Health-Check rund um wikitool lint; seit 1.7.2 maskiert es Code vor dem Notation-Match und zaehlt Zitat-Bloecke statt Zeilen
 ---
@@ -13,8 +13,6 @@ related:
  - see-also: Publish-Remote Gate
  - see-also: MCP-Leseserver
 sources: [Source - LLM Improvements Sonnet Analysis, Source - LLM Improvements Production Agent Gaps 2026, Source - Conversation - Comma Bug Budget Refund and Lint Report Path Session 2026-08-31, Source - Conversation - Gate Counting and Measured Calibration Session 2026-08-31, Source - LLM Improvements Codex Analysis]
-confidence: 0.88
-confidence_base: 0.88
 provenance: sourced
 summary: 'Mass-Update Gate: publish endet mit 42 (Freigabe durch den Menschen noetig) ab 10 gezaehlten Dateien; generierte Dateien und work/ werden committet\, aber seit 1.5.0 nicht gezaehlt; freigegeben per --confirm <token>'
 ---
@@ -11,8 +11,6 @@ related:
  - composition: Shared vs Private
  - composition: Work Coordination
 sources: [Source - LLM Wiki v2]
-confidence: 0.85
-confidence_base: 0.85
 provenance: sourced
 summary: Wissensmanagement mit mehreren Agenten; erweitert das LLM-Wiki-Muster um Mesh Sync, die Trennung von geteiltem und privatem Wissen und leichtgewichtige Arbeitskoordination.
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: Audit Trail
  - see-also: Bulk Operations
 sources: [Source - LLM Wiki v2]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Rahmenwerk zur Absicherung von Wiki-Inhalten über Datenfilterung beim Ingest, Audit-Trail-Protokollierung und umkehrbare Massenoperationen.
 ---
@@ -9,8 +9,6 @@ related:
  - operates-on: Chemenu
  - see-also: MCP-Leseserver
 sources: [Source - Publish-Remote Gate and Issue Triage Session 2026-09-01, Source - Private-Instance Merge Correction and Issue 30 Session 2026-09-01, Source - MCP Read Server Implementation Session 2026-09-02]
-confidence: 0.70
-confidence_base: 0.70
 provenance: sourced
 summary: 'Drittes, im Code durchgesetztes Gate: publish bricht mit Exit 42 ab, wenn die aufgeloeste Push-URL nicht in einer optionalen, gitignoreten Allowlist steht; doctor benennt seit 2026-09-02 den Gate-Zustand statt nur die Dateiexistenz'
 ---
@@ -10,8 +10,6 @@ related:
  - rests-on: Event-Driven Automation
  - rests-on: Confidence Scoring
 sources: [Source - LLM Wiki v2]
-confidence: 0.90
-confidence_base: 0.90
 provenance: sourced
 summary: Automatische Qualitätssicherung für Wikis mit Inhaltsbewertung, Selbstheilung und Widerspruchserkennung.
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - mechanism: wikitool
 sources: [Source - LLM Improvements Codex Analysis, Source - LLM Improvements Sonnet Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: "Maschinelle Heuristiken zur Priorisierung der semantischen Pr\xFCfung: veraltete Aussagen, hohe \xC4nderungsdichte und schwache Verlinkung"
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - mechanism: wikitool
 sources: [Source - LLM Improvements Codex Analysis, Source - LLM Improvements Sonnet Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: Verbindliche Vorabprüfung, die vor Query- und Update-Operationen einen Kontextbericht erzeugt (Index, jüngste Logs, Umfang)
 ---
@@ -7,8 +7,6 @@ modified: 2026-08-29
 related:
  - mechanism: wikitool
 sources: [Source - LLM Improvements Codex Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: Eigene Befehle zum Teilen, Zusammenführen und Umklassifizieren von Seiten, mit automatischer Korrektur von Links und Frontmatter
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Stub Threshold
  - see-also: Index Scaling
 sources: [Source - LLM Improvements Sonnet Analysis]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: "Maximale Seitengr\xF6\xDFe, ab der eine Aufteilung empfohlen wird (Farza: >120-150 Zeilen, Pascalandy: 200 Zeilen)"
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Split Threshold
  - see-also: Semantic Lint Automation
 sources: [Source - LLM Improvements Sonnet Analysis, Source - LLM Wiki v2]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: "Mindestumfang, ab dem eine Wiki-Seite nicht mehr als Stub gilt (Farza: \u22653 S\xE4tze oder 15 Zeilen)"
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: Knowledge Graph
  - exemplifies: LLM Wiki Pattern
 sources: [Source - LLM Wiki v2]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Ablösen alten Wissens durch neue, widersprechende Information; gibt dem Wiki eine Versionierung mit ausdrücklicher Verknüpfung und Erhalt der Historie.
 ---
@@ -10,8 +10,6 @@ related:
  - see-also: Aura
  - see-also: makepkg
 sources: [Source - Arch Linux Cheat Sheet]
-confidence: 0.95
-confidence_base: 0.95
 provenance: sourced
 summary: Linux-Ablauf zum Anlegen, Ändern, Überwachen und Löschen von Benutzerkonten mit useradd, usermod und userdel, samt Gruppenverwaltung und sudoers-Konfiguration.
 ---
@@ -9,8 +9,6 @@ related:
  - see-also: Context Isolation
  - see-also: Token Economics
 sources: [Source - Copilot Skill Restructure Instructions]
-confidence: 0.80
-confidence_base: 0.80
 provenance: sourced
 summary: Herauslösen von Workflow-Abschnitten aus monolithischer Dokumentation
 ---
--- a/Show More
+++ b/Show More