decision-log

You record a structured entry of an IC decision into the family's decision log. The entry preserves enough context that years later, the family (or /case-study) can understand what was decided and why — not just the outcome.

Before proceeding

Read in order:

1. The plugin's family-rules.md (shipped behavioral rules) and <family_folder>/.intelligent-alpha/family-customizations.md (family overrides) if it exists.
2. <family_folder>/.intelligent-alpha/overlays/ia-fo-decision-log-v1.md if it exists.
3. deals/{deal-id}.md — the opportunity context.
4. Any reports/{date}-ic-memo-{deal-id}.md that was prepared for the vote.

Inputs

The user provides one of:

• A meeting transcript (from Granola, etc.)
• Verbal description of what was decided
• Pasted notes
• A combination

Extract:

• Decision — proceed / pass / proceed with conditions / table
• Vote — unanimous / split (and how it split, if visible)
• Date
• Subject — the deal-id and canonical name
• Amount if proceed (commitment size, investment size, etc.)
• Reasoning — what won the room. The 1–3 specific things that drove the vote
• Dissent — if any IC member voted no or expressed strong reservations, capture their reasoning in their words where possible
• Conditions — any contingencies attached to a yes
• What we'll watch for — the metrics, milestones, or warning signs the IC pre-committed to monitoring

If any of these are unclear from the input, ask. Don't fabricate.

Generating the decision-id

Format: {YYYY-Q{N}}-{deal-id} — e.g., 2026-q2-veritas-vc-fund-iii. If multiple decisions on the same deal, append a suffix (e.g., -followup, -revision).

Writing the entry

Append to decisions/INDEX.md:

| decision-id | date | subject | type | disposition | amount | summary |

Create decisions/{decision-id}.md:

---
decision-id: <id>
date: <YYYY-MM-DD>
subject: <deal-id>
canonical-name: <name>
type: <fund commitment | direct investment | exit | re-up | pass | other>
disposition: <approved | declined | conditional | tabled>
amount: <if applicable>
vote: <unanimous | split (X-Y) | other>
---

# <name> — IC Decision, <date>

## Decision

<plain statement of the outcome>

## Reasoning

<the 1–3 specific things that drove the vote, in the IC's voice>

## Dissent / concerns

<any reservations expressed, attributed where possible>

## Conditions

<contingencies attached, if any>

## What we'll watch for

<pre-committed monitoring criteria>

## Source

<reference to the IC memo, meeting transcript, deal file>

Linking back

Update deals/{deal-id}.md:

• Set status (funded, passed, conditional, etc.)
• Append a "Decision" section with a link to the decision entry
• If passed, the deal moves out of active pipeline

Update managers/{manager-id}.md if relevant — the position changes (new commitment, exit, etc.) affect the manager profile. Note the change with citation to the decision.

If portfolio/commitments.md needs updating (new commitment, capital call schedule), add the entry with citation.

Append to change-log.md: "Recorded IC decision {decision-id}: {disposition}."

Surfacing related precedents

After recording, optionally surface related past decisions:

Logged. This is the family's 4th venture commitment in 2026, bringing total venture commitments to $X. Last similar decision: {decision-id-of-prior-similar-deal} ({date}, {disposition}).

Make this useful, not noisy. If there's nothing useful to surface, don't.

Output

Compact confirmation:

Recorded {decision-id}. {Disposition}. {N conditions}. The IC will watch: {brief summary}. Want me to schedule a check-in to review the conditions in [N] months?

If conditions involve future review, suggest the family put a reminder on their own calendar — the plugin doesn't schedule its own tasks.

Boundaries

• Capture in the IC's voice where possible. If a member said "this is a tracking error play", that's the language to use, not "the case rests on tracking error considerations".
• Do not editorialize on the decision. The decision is what it is. Capture, don't critique.
• Do not pitch any Intelligent Alpha products.