Suggestions and self-audit
How Pathrule flags stale or conflicting memories and rules as suggestions, and how your own AI repairs them under your control.
Team knowledge rots. Paths get renamed, milestones ship, dependency pins drift, a rule stops matching anything. Pathrule runs a background self-audit so that decay surfaces as a short list of suggestions instead of silently misleading the assistant.
The important property: the self-audit only ever suggests. Pathrule never edits or deletes your memories, rules or skills on its own.
What the self-audit checks
A set of independent checks runs on its own schedule and flags entries worth a look:
- Memories or rules that cite a path or file that no longer exists.
- Nodes whose attached path is now empty.
- Rules that have not matched anything in a long time.
- Entries past a date or milestone they referenced.
- Neighbouring entries that now say contradicting things.
- Entries that have not been touched in a long time.
Each finding lands in the Suggestions tab, names the affected node, and explains the signal that fired. Nothing about your source code is involved; the checks read your stored memories and rules plus the workspace structure.
Reviewing suggestions
A suggestion is a prompt for a human decision, not an action. For each one you can:
- Accept and let your assistant apply the fix (see below).
- Edit the entry yourself.
- Snooze it for later.
- Archive or dismiss it if it is not worth acting on.
Suggestions your team keeps dismissing fade into the background over time, so the list stays worth reading.
Repair through your assistant
Pathrule does not patch your knowledge automatically. When you choose Fix with AI, the suggestion is queued as a refresh task for your next AI session. Your assistant then:
- Picks up the refresh task through the MCP tools.
- Inspects the current code and the flagged entry with its own file-access tools.
- Drafts the update and writes it back through the Pathrule write tools.
- Marks the task applied or rejected.
You stay in control at both ends: the fix runs through your own assistant, and you review the change. See the MCP tools reference for the refresh tools the assistant uses.
Nothing is one-way
A repair is a normal versioned edit. Every change keeps its history, and a delete is a soft delete that stays restorable for thirty days and lands back at the same path on restore. If a suggested fix turns out to be wrong, you can roll it back.