playbook/antigravity-awesome-skills/skills/lore/references/audit-template.md

Audit report template

audit writes its output to .lore/audit/audit-YYYY-MM-DD.md. This file is read-only with respect to .lore/*.md (see main SKILL.md Conflict resolution — audit never mutates and never ALERTs).

Template

# Memory Audit Report

> Date: 2026-07-09
> Total entries audited: <N>
> Findings: <X> CONFLICT, <Y> STALE, <Z> UNVERIFIED

## Global (`_global/`)

### CONFLICT
- [CONV-2026-01-20-b1e8] claims "all packages TypeScript strict mode"
  Evidence: `packages/legacy/tsconfig.json` has `"strict": false`

### STALE
- [ARCH-2026-01-15-d7a3] references `nx.json`
  Evidence: file no longer exists at repo root

### UNVERIFIED
- [DEC-2026-02-03-7c19] last verified 2025-09-12 (>90 days)

## Scope: frontend

### CONFLICT
- ...

### STALE
- ...

### UNVERIFIED
- ...

## Summary

Recommended action: run `lore sync` to address these findings.
Audit itself does not modify any entry.

Severity definitions

Severity	Meaning
CONFLICT	Code/config directly contradicts the entry content (e.g. memory says react@18, package.json says 16)
STALE	Entry references a resource (file, API, version) that no longer exists
UNVERIFIED	Entry's #verified date is >90 days; needs re-confirmation

Required rules

• The audit report never modifies any .lore/*.md file.
• The audit report never emits ALERT blocks (ALERT noise is contained to sync and query).
• Audit is a pure read-and-report operation. To act on findings, the user runs sync.

Evidence format

Each finding includes a one-line Evidence: reference pointing to the file path and (when possible) line number that triggered the finding. The agent must verify the evidence exists before writing the report.