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.