---
id: ADR-PFM-MTD-004
title: Purpose-governed layout documents
product_area: platform
module: metadata
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: Four resource kinds store bounded, opaque presentation documents under an immutable purpose, while record
  owners assign compatible definitions in their own transactions.
constrains:
- DOM-PFM-MTD-003
- SVC-PFM-MTD-layouts
- SCR-PFM-MTD-006
- SCR-PFM-MTD-009
origin: 'services-platform:docs/layouts.md §1, §2 and §4 (the design contract; §4a Andrew 2026-10-11: two console
  forms); custom objects architecture D-09 for custom object purposes'
alternatives:
- option: Shared table with a kind discriminator
  why_not: The chosen separate resources provide direct composite references for assignment-kind enforcement.
- option: Server interpretation of designer content
  why_not: Coupling designer shape to service validation would require coordinated service releases for presentation
    changes.
- option: Platform-managed assignment saves
  why_not: Presentation selection belongs in the referring record owner’s transaction.
consequences:
- Five assignment slots distinguish four stored presentation kinds.
- Purpose consumption access permits rendering without purpose administration, in addition to the route’s own gate.
- The browser-local contact page designer currently bypasses these shared definitions.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: modules/layouts/**; docs/layouts.md'
---

# Purpose-governed layout documents

## Context

Applications need shared presentation storage while console designers evolve their content. Assignment consistency also has to survive concurrent saves and deletion.

## Decision

Four resource kinds store bounded, opaque presentation documents under an immutable purpose, while record owners assign compatible definitions in their own transactions.

## Alternatives Considered

Shared table with a kind discriminator: The chosen separate resources provide direct composite references for assignment-kind enforcement. Server interpretation of designer content: Coupling designer shape to service validation would require coordinated service releases for presentation changes. Platform-managed assignment saves: Presentation selection belongs in the referring record owner’s transaction.

## Consequences

Five assignment slots distinguish four stored presentation kinds. Purpose consumption access permits rendering without purpose administration, in addition to the route’s own gate. The browser-local contact page designer currently bypasses these shared definitions.