Change the source. Trace every consequence.

Model derived context as a dependency graph, then compute invalidation, stale deletion, reprocessing order, and permission broadening.

PERMISSION-TAGGED LINEAGEGRAPH CONTRACT · NOT A COCOINDEX BENCHMARK
GRAPH SHAPE10 / 9nodes / dependency edges
INVALIDATION6AFFECTED NODES
STALE REMOVAL1STALE DELETE
ACCESS REVIEW1PERMISSION LEAK

Reprocessing order

incident → extractor → summarizer → ticket_facts → incident_summary → context_bundle

Topological order keeps dependencies ahead of their outputs. Deleted canonical input is not rebuilt.

Permission evidence

context_bundle exposes roles beyond incident_summary's security-only access.

The bundle needs partitioned retrieval or the strict intersection of upstream permissions.

Boundary. This audits graph contracts. It does not run CocoIndex, measure recovery time, propagate real ACLs, or prove storage transaction safety.

RECONCILIATION COMPLETE · 6 AFFECTED · 1 STALE DELETE · 1 PERMISSION LEAK

Six nodes move. One stale record must disappear.

6AFFECTED NODES
1STALE DERIVED DELETE
1PERMISSION LEAK

Changing the extractor and deleting the incident invalidates their union of descendants. incident_summary can no longer be regenerated and must be removed; context_bundle must not broaden its security-only upstream access.

Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.