---
id: ADR-PFM-CSH-013
title: The Shell Owns No Business Save
product_area: platform
module: console-shell
revision: 1
status: proposed
design_intent: proposed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Define no shell-owned business-record save while retaining Security ownership
  of consumed read bookkeeping and session termination.
constrains:
  - SVC-PFM-CSH-console-shell
  - DOM-PFM-CSH-001
  - DOM-PFM-CSH-003
  - RESP-PFM
origin: >-
  none (follows ADR-PFM-CSH-001;
  services-platform:docs/standards/record-write-contracts.md read for context)
alternatives:
  - option: >-
      Persist preferences such as the menu fold or the last workspace on the
      server
    why_not: >-
      Server-held preferences would need record ownership and retention
      decisions.
consequences:
  - There is no shell-owned business save to compensate.
  - Delivered feedback will require an owned operation and persistence contract.
  - Consumed Security reads can still update service records.
supersedes: []
evidence:
  - >-
    react-console at baf6dae: lib/auth/session.ts (remembered workspace);
    components/ui/sidebar.tsx (fold cookie);
    components/console/feedback-dialog.tsx
---
# The Shell Owns No Business Save

## Context

Record-write standards apply to business persistence, while the shell primarily holds client presentation state.

## Decision

The shell defines no business-record write operation. Security reads may perform bookkeeping, and session termination remains a consumed Security action. Browser preferences are local.

## Alternatives Considered

Server preferences would require an owned record and retention policy for a small presentation benefit.

## Consequences

No shell business save needs a compensation design. Future delivered feedback will need an owner and write contract. This boundary does not erase the side effects of consumed operations.