Decision Logger

What Is Decision Logger?

Decision Logger is a productivity skill designed for board meetings and executive decision tracking. It implements a two-layer memory architecture: Layer 1 records the raw, unfiltered meeting transcripts, while Layer 2 retains only those decisions formally approved by the founder or board. This architecture provides robust governance, clear separation between discussion and actual decisions, and helps organizations maintain an authoritative, auditable log of strategic choices. Decision Logger is typically integrated as a post-meeting workflow, invoked automatically after the final approval phase during board meetings, but can also be used independently to review, audit, and manage organizational decision memory.

Why Use Decision Logger?

Board meetings generate a wealth of information, but not all discussions translate into actionable or approved decisions. Relying on undifferentiated meeting notes often leads to confusion, misattributed consensus, and, worst of all, policy drift—where past debates influence future decisions unintentionally. Decision Logger addresses these problems by distinctly managing:

• Raw transcripts (Layer 1): Captures every proposal, debate, and action item discussed.
• Approved decisions (Layer 2): Retains only those decisions that have passed the required approval threshold (e.g., founder sign-off).

This separation is critical for compliance, accountability, and organizational clarity. Only Layer 2 is referenced by future meetings or systems, ensuring that hallucinated consensus or preliminary discussions do not resurface as “decisions” in subsequent deliberations. Decision Logger also offers advanced querying, conflict detection, and overdue item tracking, making it a cornerstone for modern, transparent board management.

How to Get Started

Decision Logger is open source under the MIT license. The primary entry point is the decision_tracker.py script, which provides a command-line interface to interact with both layers of the decision log.

Installation

1. Clone the repository:

   bash

   git clone https://github.com/alirezarezvani/claude-skills.git
   cd claude-skills/c-level-advisor/decision-logger

2. Ensure Python 3.8+ is installed, then install dependencies (if any):

   bash

   pip install -r requirements.txt

3. Run the demo to see sample output:

   bash

   python scripts/decision_tracker.py --demo

Typical Usage

• Summarize all decisions and overdue action items:

  bash

  python scripts/decision_tracker.py --summary

• Review only past-due action items:

  bash

  python scripts/decision_tracker.py --overdue

• Detect conflicts or contradictions in approved decisions:

  bash

  python scripts/decision_tracker.py --conflicts

• Filter decisions by owner (e.g., CTO):

  bash

  python scripts/decision_tracker.py --owner "CTO"

• Search decisions for a keyword (e.g., "pricing"):

  bash

  python scripts/decision_tracker.py --search "pricing"

Key Features

• Two-Layer Memory Architecture:
  • Layer 1: Stores unfiltered transcripts, proposals, and discussions.
  • Layer 2: Stores only founder- or board-approved decisions and actions.
• Action Item Tracking:
  Each approved decision can include action items with deadlines and owners, supporting accountability.
• Conflict Detection:
  The --conflicts flag highlights contradictory or overlapping decisions, helping prevent policy drift.
• Overdue Monitoring:
  The --overdue and --summary commands surface action items past their deadlines for follow-up.
• Granular Filtering and Search:
  Query decisions by owner, keyword, or status, making audits and reviews efficient.
• Integration with Board Meeting Workflows:
  Designed to be triggered automatically by the broader board-meeting skill after founder sign-off.
• CLI-First Design:
  All features are accessible via command-line, facilitating automation and integration with other productivity tools.

Best Practices

• Record Everything, Approve Deliberately:
  Do not filter discussions during Layer 1 capture. Let the approval phase (Layer 2) determine what becomes part of the organizational memory.
• Regularly Review Overdue Items:
  Use the --summary or --overdue commands after each meeting to ensure no action items slip through the cracks.
• Audit for Conflicts Periodically:
  Run the --conflicts check before major decisions or quarterly reviews to catch contradictions early.
• Enforce Strict Approval Workflow:
  Only move decisions to Layer 2 after explicit founder or board approval. Avoid “soft” consensus.
• Use Consistent Terminology:
  Standardize the way decisions, owners, and action items are described to improve searchability and reduce ambiguity.

Important Notes

• Layer 2 Is the Source of Truth:
  Only Layer 2 should inform future meetings, compliance reviews, or reporting. Never treat Layer 1 as authoritative.
• No Automatic Promotion:
  Discussions in Layer 1 are not elevated to Layer 2 without explicit approval. This prevents unintentional memory leaks.
• Integration Points:
  Decision Logger is best used alongside the broader C-level advisor suite but can operate as a standalone tool.
• Security and Confidentiality:
  As with any decision log, ensure access control and data security measures are in place, especially when handling sensitive board matters.
• Extensible and Open Source:
  The MIT license allows adaptation and extension. Custom workflows, integrations, or UI layers can be added as needed.

For more details, visit the official repository.