swarmvault review

Resolve staged approval bundles created by swarmvault compile --approve, swarmvault ingest --review, swarmvault ingest --guide, swarmvault source add --review, swarmvault source add --guide, swarmvault source review, swarmvault source guide, and swarmvault source session.

Usage

swarmvault review list
swarmvault review show <approval-id>
swarmvault review accept <approval-id> [targets...]
swarmvault review reject <approval-id> [targets...]

Commands

  • list - Show every approval bundle plus pending, accepted, and rejected entry counts
  • show <approval-id> [--diff] - Display the staged entries with a section-level change summary. Add --diff for unified diff output.
  • accept <approval-id> [targets...] - Apply pending entries to the live wiki, graph, and search state
  • reject <approval-id> [targets...] - Mark pending entries as rejected without mutating active wiki paths

Targets

Targets are optional. When omitted, SwarmVault accepts or rejects every pending entry in the bundle.

You can target entries by:

  • page id such as concept:approval-concept
  • relative wiki path such as concepts/approval-concept.md

Examples

swarmvault compile --approve
swarmvault ingest ./meeting.srt --guide
swarmvault source add ./exports/customer-call.srt --guide
swarmvault source review source-12345678
swarmvault source session source-12345678
swarmvault review list
swarmvault review show approval-2026-04-07t121530z
swarmvault review accept approval-2026-04-07t121530z
swarmvault review reject approval-2026-04-07t121530z concepts/approval-concept.md

Notes

  • Accepted entries update active wiki files immediately and refresh state/graph.json, state/search.sqlite, and affected indexes.
  • Rejected entries stay in the approval history for auditability.
  • Source-scoped review bundles typically target pages under wiki/outputs/source-reviews/, wiki/outputs/source-guides/, wiki/outputs/source-sessions/, plus either canonical wiki/sources/, wiki/concepts/, and wiki/entities/ pages or wiki/insights/ fallback pages depending on the active profile.
  • The local graph workspace exposes the same queue through /api/reviews and /api/review.