wiki-maintainer

A memory vault stays deterministic when page generation and block management are strictly controlled. Applying source-backed updates ensures that all vault pages, blocks, and provenance remain consistent, stable, and fully auditable during maintenance.

Automating wiki editing while keeping provenance intact requires applying source-backed updates through a guided maintenance loop. This enforces stable identity for memory blocks and ensures all automated vault changes remain fully auditable.

Cross-tool integration during wiki maintenance is handled by satisfying specific tooling requirements like wiki_status, memory_search, wiki_search, wiki_apply, and wiki_lint. These commands enable stable identity and provenance tracking across different tools.

Yes, you can use bridge and unsafe-local modes for vault maintenance and page editing. These modes are supported as appropriate within the maintenance loop to facilitate safe, provenance-backed updates to the memory wiki.

A wiki vault loses consistency during automated updates if page generation and block management are not deterministic. Enforcing stable identity and source-backed provenance for every update prevents this drift and keeps the vault fully auditable.

You need to run wiki_lint and wiki_apply for memory note management when checking vault consistency and applying source-backed updates. These commands validate the wiki state and enforce deterministic page generation within the maintenance loop.