Proposals
Review saved vault change proposals in Agents → Proposals in the MindWiki Mac app. Existing proposals and their review history remain available after the proposal MCP tools retired.
What a proposal records
A proposal includes a type, summary, rationale, target files, and optional diff or structured payload. The payload describes the supported operation; the summary explains why you would want it.
A recorded proposal is separate from an applied change. Its status and readiness tell you whether it is awaiting review, executable through the supported flow, applied, rejected, or in need of refresh.
Understand executable and review-only types
| Type | Current role |
|---|---|
add_tags | Supported typed validation and application of additive tags. |
update_links | Supported typed validation and application of link changes. |
move_note | Supported typed validation and application of a file move. |
create_context_pack | Supported creation of a new pack through an approved proposal. |
edit_note, create_note, merge_notes, split_note, rename_note, archive_note | Reviewable suggestions; do not assume a generic apply operation executes them. |
flag_contradiction, create_decision, create_summary | Reviewable findings or suggested outputs; inspect the proposal for the required follow-up. |
A review-only proposal can still be useful: it preserves the recommendation and evidence. Accepting the recommendation is different from executing a supported file operation. An agent should state clearly which occurred.
Review an existing proposal
- Open Agents → Proposals in the Mac app.
- Select a pending proposal and inspect the affected pages, rationale, and preview when available.
- Accept or reject the proposal in the review queue.
- Check the resulting proposal state and affected pages.
The existing REST queue exposes recent records through GET /vault/agents/summary and decisions through POST /vault/agents/proposals/:id/:action with accept or reject. Those operations require an eligible account and suitable API access. Accepting an executable proposal can change the vault. An accepted review-only suggestion still needs any separate action you choose to take.
Request new reviewable work
Ask your agent to read the relevant sources and explain a proposed change with its exact targets. You can review its recommendation before requesting any write. Rich documents support source-anchored comments and suggestions when your connection has the corresponding MCP tools.
Handle changes after the preview
A proposal may rely on a particular page revision. If the page changed, inspect its current content and review a fresh plan before asking for a write. Authorized page writes also require the appropriate revision checks.
Keep the outcome visible
After applying, open the affected pages and verify the intended result. After rejecting, the recommendation remains part of the recorded workflow without applying its proposed change.
Activity and proposal records help you understand the operation. Save a short decision or handoff page as well when the reasoning matters to the next project session.
Next: Mission Control, Vault Health & Permissions, and MCP Tools.