Audit Feedback Loop

audit-feedback-loop

Template skill (doc 08). Feedback that is deleted on resolution loses the audit trail that makes a knowledge store defensible. Every item is anchored and state-tracked instead.

Trigger

/audit-feedback <add|list|resolve> [args]

Preconditions

• A feedback store exists keyed by stable text anchors (page + quoted span or stable id) that survive edits well enough to re-resolve.
• The pages under review are committed (or staged) so anchors point at durable text.

Closed-set resolution states

open → acknowledged → resolved | wontfix | superseded (Never deleted. A resolved item is closed with a reason, kept for audit.)

Steps

• add: attach feedback to an exact text anchor (page + quoted span or stable id), not "somewhere on this page." Record author + timestamp + initial state open.
• list: show items filtered by state/anchor; surface stale open/acknowledged items past an age threshold.
• resolve: move an item to a terminal state with a reason and a link to the change (PR/commit) that addressed it. The item stays in the record.

Verification

• Every item has an anchor that still resolves to existing text (a validator can flag orphaned anchors after edits).
• No item is ever removed; state transitions are append-only.

Cleanup

• n/a — non-deletion is the point.

Incident appendix