gaia-refresh-ground-truth

Ground-truth synchronization works by comparing a current filesystem scan against the last committed snapshot. It identifies added, updated, and removed files, then dual-writes the refreshed inventory to a seed file and a decision log for auditability.

You need a filesystem scan for ground-truth initialization during first-run setup or cross-agent synchronization. It captures the initial project state and writes a ground-truth.md file with the standard header to establish a baseline snapshot.

Yes, you can perform an incremental scan instead of a full filesystem scan. The tool supports both modes, allowing you to efficiently detect recent changes and update the memory-ground-truth format without rescanning unchanged files.

The validator-sidecar maintains a decision log by writing a diff summary of added, updated, and removed entries during each refresh. This dual-write to the committed seed and decision log creates an audit trail for governance and rollback.

The best way to keep project memory aligned is to use an automated inventory tool that rescans the filesystem and regenerates a diff report. This enforces the memory-ground-truth format and dual-writes updates to the seed and decision log.