Profile segmentation

Every terminal, pending input request, journal row, recording, and spilled artifact belongs to one profile inside one workspace. The active profile selects the default read and mutation scope.

Switching profiles re-scopes the terminal list, dock badge, input requests, journal, and recording links together. A terminal owned by profile A does not appear under profile B, and a typing or remembered command grant created under A does not authorize B.

Operators can ask for an aggregate read when they need oversight:

compozy terminal list --workspace my-project --all-profiles -o json
compozy terminal input-requests --workspace my-project --all-profiles -o json
compozy terminal journal --workspace my-project --all-profiles -o json

Aggregate rows include profile_id and profile_name. Single-terminal reads and mutations remain single-profile operations; --all-profiles does not become cross-owner write authority.

Archive and delete behavior

Archiving a profile closes its live terminals, invalidates attach tickets, and resolves pending input requests. Its journal rows, artifacts, and recordings remain readable as historical facts through operator aggregate reads. Unarchive the profile before using single-profile history reads or opening or mutating a terminal under that owner.

Deleting a workspace removes the terminal runtime and its workspace-owned journal, recordings, and artifacts. Terminal data never needs a cross-workspace query, and a terminal ID from another workspace does not widen the caller's read scope.