minutes-lint

Meeting audits for decision conflicts identify contradictory resolutions across your meeting corpus. This consistency check surfaces contradictory decisions and stale commitments, ensuring organizational decisions are tracked and resolved without inconsistencies slipping through.

Yes, you can filter stale commitments by owner using the --owner filter. The minutes consistency command applies filters like --owner and --stale-after-days across your meeting corpus to accurately surface overdue action items assigned to specific individuals.

You audit overdue action items across multiple meeting records by running a consistency check across your meeting corpus. This health-checks meeting knowledge to surface stale commitments and contradictory decisions, producing a readable report with meeting context.

The meeting consistency check outputs machine-readable JSON via the minutes consistency command. This format allows you to programmatically audit decision conflicts and stale commitments, while also generating human-friendly reports with meeting context.

Yes, the minutes consistency command relies on graph.db for accurate indexing. This database indexes your meeting corpus to ensure the consistency check accurately maps relationships and surfaces contradictory decisions and stale commitments.

You need to run a meeting audit for decision conflicts when preparing for follow-ups or ensuring commitments are tracked. A consistency check surfaces contradictory resolutions and overdue action items across your meeting corpus for organizational auditing.