Give a correction a reason and a history.
The problem
Cleanup is hard to assess when a fact disappears or changes without leaving a reason. A mistaken correction also needs a way back.
An explanatory exhibit
An edit that stays inspectable
Invented relationship and review reason. The examples explain a correction and its inverse; they do not edit a real graph.
- 01
Before
Lantern / uses / PostgreSQL
- 02
Correction
Source says SQLite; record the reason
- 03
After
Lantern / uses / SQLite
Inspect the consequence
Inspect the correction
PostgreSQL / SQLite
The before-state and the source-based reason remain available with the action.
Inspect an inverse action
Restore the recorded before-state
A supported inverse action writes its own history. A reversal is itself something to review.
What this makes possible
I added action records and before-state snapshots to graph curation, with inverse actions for supported corrections.
Source information sheet
Evidence, implementation & history Implementation inspected
What I checked
Curation and action-history source inspected. Some operations may be API-only rather than visible interface controls.
Research cut: 14 October 2026. Source areas below are from panel-forge. Private conversation references are retained in the research ledger and are not published here.
Implementation decisions
The curation service records actions such as rewriting, retyping and canonicalizing relationships. Action rows and before-state snapshots preserve what changed and why.
Supported actions can be inverted through another recorded action. The October implementation work also addressed preserving reviewed records during re-analysis. The exact set of controls exposed in the interface still needs a separate live check.
A path through the feature
- Read the action
Inspect the original state, the new state and the recorded reason in a review run.
- Check or reverse it
Use the source to decide whether the correction was justified. Where inversion is supported, restoring the earlier state creates another action in the trail.
Source areas
app/Services/KnowledgeCurationService.phpapp/Models/KnowledgePruneRun.phpapp/Models/KnowledgePruneRunAction.phpresources/js/pages/KnowledgeGraph/components/KnowledgePruneRuns.vueresources/js/pages/KnowledgeGraph/components/KnowledgePruneRunActions.vue
The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.
Recorded history
Dates describe the researched record, rather than today’s deployment.
Testing graph pruning and retention tradeoffs
Graph ingest, search, and pruning implementation