Curate proposals
How the Knowledgebase surfaces merge, contradiction, and missing-file proposals, and how maintenance runs settle them.
There is no project-wide Inbox for proposed documents, failed automations, or stuck pull requests. Knowledge maintenance appears as Curate proposals cards in the Knowledgebase.
What appears there
| Kind | What the Organizer found |
|---|---|
| Merge | Entries that overlap and may need to be combined. |
| Contradiction | Documents that disagree. |
| Cites missing files | An entry references files that no longer exist. |
Expand a document on the card to read its current body and compare the entries involved.
How proposals are settled
A background knowledge-maintenance run checks the current code and decides the proposal automatically. The card shows whether it is queued or in progress; Open run opens the run's transcript. These proposals do not have a user Approve step.
If a run fails, its card remains with the failure and two actions:
- Retry run dispatches another maintenance run.
- Dismiss dismisses the failed proposal.
Open Knowledge → History to inspect knowledge-maintenance runs. The Organizer view has the separate history of passes that rebuild and curate the map.