---
id: ADR-PFM-CSH-001
title: Presentation Ownership Stays With the Shell
product_area: platform
module: console-shell
revision: 1
status: proposed
design_intent: proposed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  The shell owns client frame, navigation, address and application presentation
  without business tables or served operations, while consumed authority remains
  with Security, Metadata and Operations.
constrains:
  - SVC-PFM-CSH-console-shell
  - SVC-PFM-CSH-tenant-applications
  - DOM-PFM-CSH-001
  - DOM-PFM-CSH-004
  - RESP-PFM
origin: MOD-PFM-CSH boundary (planning layer); FND-PFM-CSH-001; FND-PFM-CSH-036
alternatives:
  - option: >-
      A Platform shell service that assembles menu, context and applications in
      one answer
    why_not: >-
      An aggregator would need to reconcile answers already owned by Security
      and Operations.
  - option: The shell keeping its own copy of licences or placements
    why_not: >-
      Persisted duplicates can drift from the authority still used for service
      refusal.
consequences:
  - >-
    The shell contract describes consumption until the owning service contracts
    provide the home.
  - >-
    Application presentation remains distinct from Operations’ stored
    application records.
  - >-
    Presentation changes need no business-table migration; browser preferences
    remain local.
supersedes: []
evidence:
  - >-
    react-console at baf6dae: components/console/**, lib/security-context/**,
    lib/routes/**
  - >-
    services-platform at ad3f6a6: modules/security/aws/api/access.routes.ts;
    modules/tenants/aws/api/tenant-applications.routes.ts
---
# Presentation Ownership Stays With the Shell

## Context

The console combines identity, application availability and customer placements from three distinct authorities. Its client objects describe how those answers are presented.

## Decision

The shell owns frame, menu, address and application presentation, with no business tables or served operations. Consumed answers retain Security, Metadata and Operations ownership.

## Alternatives Considered

A new aggregation service would introduce another authority to reconcile. Persisted copies of licensing or placements would create stale records beside the existing authorities.

## Consequences

The consumed-operation list is provisional until the owning contracts exist. Shell presentation can change without migrating business records. Browser preferences still need explicit handling.