Wiki Pages and Provenance

Wiki pages and provenance

Language: English · 简体中文

Wiki Pages are LWC's maintained knowledge layer. A Page combines readable Markdown with stable identity, retrieval metadata, citations, provenance, and links.

Page fields

Field	Purpose
Slug	Stable identifier used by commands, filenames, and Wiki links
Title	Human-readable Page name
Kind	Retrieval and maintenance category
Summary	One-line index and search description
Body	Maintained Markdown knowledge
Source IDs	Immutable evidence cited by the Page
Provenance	Explicit non-source origin of durable claims
Links	Outgoing [[slug]] relationships extracted from the body

Use stable slugs. Renaming by delete-and-recreate breaks links, retrieval history, and external references.

Page kinds

Kind	Use
source	Traceable summary of one Source
concept	Technique, pattern, rule, or idea revised across evidence
entity	Named person, organization, product, component, or dataset
query	Durable answer, decision, or open question
comparison	Structured comparison across alternatives or evidence
synthesis	Cross-cutting conclusion that integrates several Pages or Sources

Kinds improve discovery and maintenance. They do not grant authority by themselves.

Citations and source-grounded provenance

Repeat --source for every immutable Source that supports the Page:

lwc page put storage-model \
  --title "Storage model" \
  --kind concept \
  --summary "Canonical and derived storage boundaries" \
  --file storage-model.md \
  --source 12 \
  --source 18

Any cited Page automatically receives source-grounded provenance. Do not pass that value manually.

A citation means the Source supports the Page's claims. It is not merely a “related reading” link. Explain uncertainty and conflicting evidence in the Page body.

Explicit non-source provenance

Use explicit provenance when durable knowledge does not come from an immutable Source:

lwc page put accepted-boundary \
  --title "Accepted boundary" \
  --kind query \
  --summary "User decision and current verification state" \
  --file boundary.md \
  --provenance user-provided \
  --provenance agent-observed

• user-provided records a durable user statement or decision.
• agent-observed records a fact the Agent verified from current authorized evidence.
• hypothesis records a useful possibility that is not yet verified.

Do not convert a hypothesis into an observation merely because it remained unchallenged.

Replacement semantics

page put replaces the complete Page body, citation set, explicit provenance set, and extracted links in one logical update. Before replacing a Page:

lwc page show storage-model
lwc page links storage-model

Then repeat every still-valid --source and non-source --provenance value. Omitting one removes it.

This behavior prevents stale hidden metadata, but it also means blind partial updates are unsafe.

Wiki links

Use [[stable-slug]] in the Markdown body:

The canonical database is described by [[storage-model]].
Recovery behavior is defined in [[checkpoint-policy]].

page links returns outgoing links, backlinks, and unresolved links. Lint reports broken relationships and orphan maintenance issues.

Links express navigation and structural relationships. Strong semantic claims such as CONTRADICTS or DEPENDS_ON belong in explicit graph relations with provenance, reasons, confidence, and supporting Source IDs.

Writing a good Page

A useful Page:

• answers one retrievable question or explains one stable concept;
• states its scope and current status;
• distinguishes facts, decisions, and hypotheses;
• cites exact Sources when available;
• preserves meaningful contradictions;
• links to related concepts without duplicating their full content;
• includes operational verification when the claim concerns runtime behavior;
• avoids chat chronology and temporary progress.

Updating an existing Page

1. Search for the concept before creating a new slug.
2. Open the current Page and its links.
3. Inspect cited Sources whose freshness affects the claim.
4. Merge verified new knowledge while preserving still-valid material.
5. Repeat the complete citation and explicit provenance sets.
6. Run lint and fixed retrieval checks.

Use a changeset when the revision depends on other Page, Source, Purpose, Schema, or ingest mutations.

Removal

lwc page remove obsolete-page

Removal is guarded. LWC refuses to remove a Page with inbound Wiki links. Update or remove those references first. Never delete projected Markdown or database rows manually.

Provenance is not ranking

Provenance supports auditability; it does not automatically change search rank. If a verified canonical Page is hard to retrieve, first improve its title, summary, body, and links. Use explicit bounded weight or query feedback only after inspecting search --explain.

Completion evidence

A Page update is complete when:

• the slug and kind match one stable concept;
• the summary makes the Page discoverable;
• all current claims have citations or explicit provenance;
• still-valid prior evidence and links were preserved;
• contradictions and uncertainty remain visible;
• lint and both fixed retrieval forms pass.

Next: Search and context