Overview
OpenWiki turns repository and personal-source research into a Markdown wiki designed for maintenance, not one-time generation. Its ordered page jobs make progress recoverable; versioned Claims connect material propositions to repository evidence; deterministic finalization keeps metadata, navigation, links, provenance, and page bytes consistent; and tool and integration boundaries contain untrusted agents. Native and host-driven repository runs share lifecycle guarantees, while personal ingestion uses confidence and contestation rather than repository-grounded Claims. The series explains the update loop, focused repair, CI and visualization choices, and the limits that remain: semantic completeness, external-source correctness, provider availability, and human review.
Learning outcomes
- OpenWiki treats a page—not the entire wiki—as the durable unit of recovery.
- Claims make material propositions recheckable by linking them to versioned repository evidence.
- A clean Git tree is not enough for a no-op when Claims are stale, unresolved, or coverage is incomplete.
- Deterministic finalization improves structural consistency, but semantic completeness and external-source correctness still require judgment.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
How does OpenWiki keep documentation current after repository changes?
OpenWiki compares source identity and Claim evidence, then routes affected pages into focused repair instead of refreshing every page. Deterministic proofs and finalization preserve accepted progress, while source drift can require another update.
What are OpenWiki Claims?
OpenWiki Claims are atomic, independently falsifiable propositions linked to repository evidence with resolver-owned version tokens. Preflight classifies evidence as current, stale, or unresolved, but an agent still interprets what a change means.
Is OpenWiki suitable for personal knowledge sources?
OpenWiki can build a personal knowledge wiki from connectors, but those observations are not treated as repository-grounded Claims. Confidence labels and contested sections remain visible because external material can be time-sensitive or difficult to re-resolve locally.
What does OpenWiki guarantee—and what still needs review?
OpenWiki can make queue transitions, evidence checks, page durability, metadata repair, and interruption states explicit and repeatable, but it cannot guarantee semantic completeness or truth. Page boundaries, missing propositions, external facts, and unclear source changes may still need human or expert review.