---
id: ADR-MBR-STR-003
title: Retain Effective and Recorded Parentage Without Future Moves
product_area: membership
module: structure
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Parent changes retain effective periods and recorded versions, while ordinary moves and merges accept today
  or an earlier valid date rather than a future date.
constrains:
  - DOM-MBR-STR-001
  - WF-MBR-STR-001
  - WF-MBR-STR-002
  - SVC-MBR-STR-structure
origin: >-
  services-membership:docs/migrations/structure/README.md#What could not be done as specified, and why (future
  restructuring is a later phase; bitemporal pair on the versions twin)
alternatives:
  - option: Keep current parentage with an unstructured audit log.
    why_not: That would not directly support reconstruction by both effective day and knowledge time.
  - option: Accept scheduled future restructuring.
    why_not: >-
      The recorded phase boundary defers the scheduling and read semantics needed to make future arrangements
      authoritative.
consequences:
  - Historical descendants can be evaluated using effective and knowledge dates.
  - Staff enter a restructuring no earlier than its effective day.
  - >-
    A correction on the current period's first day replaces that row and retains the prior value only in
    versions.
supersedes: []
evidence:
  - >-
    services-membership at 5994c270: services/persistence/organizational-units.ts (recordParentChange,
    descendantsAsOf); services/tree/tree-edits.ts (effectiveDateOf)
---

# Retain Effective and Recorded Parentage Without Future Moves

## Context

Earlier reports need the arrangement effective then and, when requested, the arrangement known at an earlier moment. Current parentage alone cannot supply both dimensions.

## Decision

This record describes dated parent periods and their version history, including the implemented restriction against future-effective ordinary restructuring. It does not add scheduling behavior to the planning layer.

## Alternatives Considered

Keep current parentage with an unstructured audit log. That would not directly support reconstruction by both effective day and knowledge time. Accept scheduled future restructuring. The recorded phase boundary defers the scheduling and read semantics needed to make future arrangements authoritative.

## Consequences

Historical descendants can be evaluated using effective and knowledge dates. Staff enter a restructuring no earlier than its effective day. A correction on the current period's first day replaces that row and retains the prior value only in versions.