---
id: ADR-CMT-MTG-022
title: Retain Version History for Core Governance Records
product_area: committees
module: meetings
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d
decision: >-
  Meetings, minutes and decisions declare authored version records, while
  reopened attendance appends correction evidence and no inspected operation
  exposes a history view.
constrains:
  - DOM-CMT-MTG-001
  - DOM-CMT-MTG-002
  - DOM-CMT-MTG-003
  - SVC-CMT-MTG-meetings
  - SVC-CMT-MTG-decisions
origin: FND-CMT-MTG-016; FND-CMT-MTG-046
alternatives:
  - option: Store only the latest record.
    why_not: It would lose evidence of how a governance account changed.
  - option: Version every supporting table.
    why_not: >-
      The current design limits versioned core records and uses events or parent
      history for other facets.
consequences:
  - >-
    Staff need a history surface before they can inspect authors and past
    changes.
  - >-
    The selected attendance correction reason and visible history are not fully
    implemented.
supersedes: []
evidence:
  - >-
    services-committees at 36129c24: modules/meetings/db/meetings.table.ts,
    minutes.table.ts (versionedTable); modules/decisions/db/decisions.table.ts;
    modules/meetings/db/meeting-reopen-audits.table.ts
---
# Retain Version History for Core Governance Records

## Context

The current record cannot explain every past edit on its own. Version declarations and reopening evidence retain the intended change history, but visible review remains absent.

## Decision

Meetings, minutes and decisions declare authored version records, while reopened attendance appends correction evidence and no inspected operation exposes a history view.

## Alternatives Considered

Store only the latest record. It would lose evidence of how a governance account changed.

Version every supporting table. The current design limits versioned core records and uses events or parent history for other facets.

## Consequences

Staff need a history surface before they can inspect authors and past changes. The selected attendance correction reason and visible history are not fully implemented.