Skip to content

swarmvault candidate

Resolve staged concept and entity pages under wiki/candidates/.

Usage

swarmvault candidate list
swarmvault candidate promote <target>
swarmvault candidate archive <target>
swarmvault candidate preview-scores
swarmvault candidate auto-promote [--dry-run]

Commands

  • list - Show current candidate pages and their active destination paths
  • promote <target> - Move a candidate into wiki/concepts/ or wiki/entities/ immediately
  • archive <target> - Remove a candidate from the active candidate set
  • preview-scores - Show each staged candidate's promotion score without promoting anything
  • auto-promote - Apply the configured auto-promotion rules to staged candidates. Requires candidate.autoPromote.enabled in config. Add --dry-run to score candidates without moving files

Targets

Targets can be:

  • page ids such as concept:approval-concept
  • relative candidate paths such as candidates/concepts/approval-concept.md

Examples

swarmvault candidate list
swarmvault candidate promote concept:approval-concept
swarmvault candidate archive candidates/entities/old-tool.md

Auto-Promotion Rules

Auto-promotion is off by default. Turn it on under candidate.autoPromote in swarmvault.config.json. These are the defaults for every key:

{
  "candidate": {
    "autoPromote": {
      "enabled": false,
      "minSources": 3,
      "minConfidence": 0.8,
      "minAgreement": 0.7,
      "minDegree": 2,
      "minAgeHours": 24,
      "maxPerRun": 25,
      "dryRun": false
    }
  }
}

A candidate is promoted only when it passes every gate: it cites at least minSources sources, its confidence is at least minConfidence, its current sources overlap its previously recorded sources by at least minAgreement, one of its graph nodes has at least minDegree connections, and it is at least minAgeHours old. preview-scores reports the share of gates each candidate passes. At most maxPerRun candidates are promoted per run.

Notes

  • Compile stages new concept and entity pages here on first sighting.
  • A later matching compile can promote them automatically, but candidate promote and candidate archive always override that heuristic.
  • Candidate actions refresh the live graph, search index, and project rollups immediately.