fact-viewer

To audit retained facts and constraints after context compaction, you can parse the current session's preprocessing results to extract and display structured summaries of goals, errors, and markers. This distinguishes between content kept in recent messages and summarized items.

Context preprocessing affects session memory by summarizing or compacting prior interactions, retaining core facts and markers while reducing message length. It determines exactly what information stays available for the current context window versus what is archived in summaries.

Debug session memory by analyzing assemble and after-compaction logs to identify missing markers. Extracting structured sections for facts, constraints, and errors reveals what the system retained versus what was summarized during the preprocessing pipeline.

Yes, this context auditing approach requires existing preprocessing results or compaction-debugger logs to function. It reads these inputs to extract and present the retained facts, goals, and constraints, meaning it cannot operate on a raw session without prior compaction processing.

The best way to analyze audit trails for compacted session data is to extract structured sections for facts, goals, constraints, errors, and markers. This pinpoints exactly what the system retains and clearly indicates what is still present versus summarized.