wiki-maintainer

A memory wiki vault stores memory artifacts and daily notes with source-backed updates that preserve provenance across edits. It uses deterministic pages and revision history to track content origin and maintain consistency across branches or bridges.

You can automate provenance-backed updates by running validation and linting workflows that apply deterministic edits to memory artifacts and daily notes. This ensures source-backed updates and safe merging across branches while maintaining vault integrity.

Yes, you can safely merge memory wiki updates across branches or bridges. The workflow applies validation and linting to ensure deterministic page updates and preserve source-backed provenance, maintaining vault integrity throughout the merge process.

The best way to validate and lint a memory wiki is to run an automated workflow that checks deterministic pages and applies provenance-backed updates. This process validates, lints, and publishes memory-wiki updates safely.

Yes, the workflow supports tools including wiki_status, memory_search, wiki_search, wiki_get, wiki_apply, and wiki_lint. It also handles workflows such as openclaw wiki ingest, compile, and lint to maintain vault consistency.

Memory wiki pages may lose revision history during merges if provenance is not preserved. Applying automated linting and validation workflows ensures deterministic page updates and source-backed provenance, preventing history loss across branches or bridges.