decision-logger

To log board meeting decisions, use a dual-layer memory system that separates raw transcripts from approved outcomes. This approach tracks assigned action item deadlines and enforces a 'DO_NOT_RESURFACE' policy for rejected proposals.

Conflict detection in board governance identifies contradictions between new proposals and existing approved outcomes. This prevents contradictory policies by maintaining a curated memory of past resolutions.

Track overdue action items by running a Python CLI tool that summarizes assigned tasks and flags approaching deadlines. It queries the stored approved outcomes layer to generate status reports.

Yes, decision logging works with raw meeting transcripts by maintaining them in a separate memory layer. This dual-layer architecture preserves original transcript data while curated outcomes are tracked independently.

Prevent rejected proposals from resurfacing by enforcing a 'DO_NOT_RESURFACE' policy within the decision logging memory architecture. This governance mechanism blocks previously dismissed items from re-entering active workflows.

Yes, you need the python-dateutil dependency to manage board meeting action items. It provides the parsing logic for the CLI tool to accurately calculate deadlines and detect overdue tasks.