/ground-truth-management

What it is

Ground truth operations for the validator -- entry structure, incremental and full refresh strategies, conflict resolution, archival, token budget management, and brownfield extraction. This skill defines how the validator's knowledge about the project is structured and maintained.

Called by

• /gaia-refresh-ground-truth (the primary consumer)
• /gaia-val-validate (reads ground truth for cross-referencing)
• /gaia-brownfield (initial ground truth seeding)

What it does

Defines the canonical entry structure: category, factual statement, source path, verified date, verification count.

Supports four fact categories: file-inventory, planning-baseline, adr-baseline, and dependency-baseline.

Handles conflict resolution when ground truth disagrees with filesystem scans -- filesystem is always the source of truth.

Manages the dual-refresh pattern: runtime sidecar gets full entries, committed seed keeps empty-seed invariant.

When you will see it surface

• You will not interact with this skill directly. It provides the patterns used by /gaia-refresh-ground-truth.
• If validation mentions 'ground truth not available', running /gaia-refresh-ground-truth populates it using these patterns.

Technical notes

• The filesystem is always the source of truth -- ground truth entries are updated to match, never the reverse.
• Malformed entries are flagged and reconstructed, never silently dropped.
• Token budgets are per-tier and config-driven from _memory/config.yaml.