Review changes and use history
Review turns a proposed change into a human decision. History helps you understand what changed and which version readers currently receive.
An Editor or Owner can make review decisions where the item and audience permit it. A Viewer does not gain decision rights by receiving a link. MCP-authenticated AI actors cannot approve reviews.
View full-size image
Actual dtxWiki screen with fictional demo data. Item names can differ from the walkthrough. Review overview showing an empty queue and manual approval policy for the example workspace.
Review a proposed change
- Open Review queue.
- Choose Pending and the relevant audience: To me, From me, or All where available.
- Open the item and read its summary, reason, target page, and change details.
- Use View changes when available. Check important factual changes against Library sources.
- Choose a decision.
| Decision | Result |
|---|---|
| Approve | For an eligible Context publication/update review, approves and publishes the proposed version. Read the impact message first. |
| Request changes | Keeps the work needing correction and records your reason. A reason is required. |
| Reject | Resolves the proposal as rejected. Check the item type before deciding. |
A review can be Pending, Changes requested, or resolved as Approved or Rejected. Review statuses are separate from a page's editing, draft, and published states.
Approval may settle earlier pending reviews for the same page. The screen explains the impact; do not treat every item as an isolated change. If the proposal was superseded by a newer draft, reopen the current page and review the actual latest version.
Review is not every save
The browser's Save draft keeps editor work unpublished. Explicit submissions from an integration, Ask placement, or configured workflows can enter Review. Human Editors can also publish pages directly. Workspace policy can affect review handling, so use the actual saved/published status rather than assuming every write always waits for a second person.
Handle overlapping edits
A Context reconciliation item represents a branch needing reconciliation. Its generic Approve/Reject buttons are unavailable; use Open reconciliation and the dedicated workflow to reconcile or explicitly discard the branch. A generic decision would not merge the text.
If another reviewer has claimed work or a version changed, refresh and coordinate with that reviewer. Avoid repeating a decision against an old tab.
Read page history
- Open the Context page and choose History.
- Find the current published snapshot and the current editing/draft state you can access.
- Select versions and compare changes using the available diff view.
- Use restore only after checking the content and the resulting state. A restore must not be assumed to immediately replace what readers see.
Currently editing is an author-private, unsubmitted edit. Current draft is an unpublished version. Current published snapshot is the reader-facing version. Alternative and superseded entries preserve other versions rather than making them current.
The label v3 in History means the third page revision. It does not mean dtxWiki software version 3. Library source versions and Agent versions have their own separate histories.
If a review will not complete
Read the error and reload the item. Publication and review completion are distinct operations: a notice can say that the page was published but review completion failed. Check both the page's published version and queue status before retrying. If History reports that operator repair is required, contact the administrator rather than trying to force publication.
Next: Context pages, Chats provenance, or troubleshooting.
Implementation reference: review decisions, history states, review UI labels.