Source synchronization
How project documents become a durable, traceable knowledge base.
- Page ID
concepts/source-synchronization- Digest
43bd67c81e3f…- Version
- Current published page
From a source to shared knowledge
Knowl keeps the original source and the knowledge derived from it separate. A source revision is saved before its content is used to maintain the wiki.
A saved revision is not a finished update.
Synchronization, source acceptance, and knowledge processing are separate stages. A successful sync can still have maintenance waiting in the queue.
The processing lifecycle
- Synchronize. A configured source discovers and reads a bounded set of documents.
- Accept. Knowl saves an immutable revision with its source identity and digest.
- Maintain. The maintainer proposes a change using the saved revision and selected knowledge.
- Publish. A validated change becomes part of the canonical wiki.
What happens when a source changes?
A later revision does not replace the saved original. Existing provenance continues to point to the accepted revision that supported the page. Failed updates remain visible alongside the last successful synchronization.
Confirmed upstream deletion can mark a document as deleted while preserving its accepted raw revisions and the knowledge already derived from them.