Audit Trail

To trace why a decision was made during verification checks, you can use bidirectional traversal to search decision histories across sessions and iterations. This exposes the exact context and reasoning behind past coherence check outcomes.

Yes, you can preserve provenance using Git commit messages. The audit trail supports persistent storage through in-memory logs, file-based logs, and Git commits to maintain structured records of changes.

You can view the complete decision history for a specific verification session by running the view command with your session identifier. This retrieves the structured audit logs for forensic analysis.

The best way to analyze the impact of file changes across iterations is through bidirectional audit trail traversal. It provides exposure analysis to assess what happened after a change and trace historical verification results.

No external dependencies are required to search decision histories. The system operates independently to provide structured audit logs and traceability across your verification sessions and file changes.

You should not rely on in-memory logs for audit trails when you need persistent provenance across sessions. For long-term forensic analysis, file-based logs or Git commit messages provide durable storage.