Status: Active
Owner: OSHUN Studio Architecture + Platform Identity + OSHUN Web + OSHUN BFF
Last Updated: 2026-02-23
Related:
docs/adr/ADR-0026-oshun-studio-session-and-device-management.mddocs/releases/v1/specs/studio-session-and-device-management-dependency-and-data-contract-map.md
Purpose#
Define primary journeys and deterministic edge-case behavior for Studio session and device management governance.
This document is the execution artifact for OST-00107.
Personas#
- Program Operator
- Security Reviewer
- Domain Integrator
- Reliability Engineer
- Compliance Auditor
Journey Principles#
- Active session and device state must always be visible and verifiable.
- Trust and revocation actions must be deterministic and auditable.
- Privileged operations must block on stale, revoked, or untrusted contexts.
- Recovery paths must preserve user intent while restoring secure state.
1. Primary Journeys#
J1. Active Session Inventory and Device Visibility#
Goal: Inspect all active Studio sessions and associated device trust state.
Entry: Studio -> Session & Device Management -> Inventory
Steps:
- Load current user session inventory.
- Display platform, location, assurance, and last activity metadata.
- Highlight stale or suspicious sessions.
- Surface trust state per device.
- Present next-action controls (revoke, re-verify, challenge).
Success State:
- Operator sees a complete and accurate view of active sessions/devices.
J2. Trusted-Device Enrollment for Privileged Operations#
Goal: Elevate a device to trusted state for privileged Studio workflows.
Entry: Privileged action requires trusted device
Steps:
- Initiate trust enrollment on selected device.
- Execute challenge/attestation flow.
- Validate challenge outcome and policy eligibility.
- Update device trust state to
trusted. - Emit trust-elevation audit evidence.
Success State:
- Device trust is established and privileged actions may proceed.
J3. Session Revocation for Suspected Compromise#
Goal: Revoke one or more active sessions quickly and deterministically.
Entry: Security alert or suspicious activity detection
Steps:
- Identify target session(s) from inventory.
- Select revoke scope (single/device/all).
- Execute revocation request.
- Confirm revocation propagation across domains.
- Surface completion status and residual risk guidance.
Success State:
- Target sessions are revoked and blocked from further privileged operations.
J4. Device Trust Expiry and Re-Verification Recovery#
Goal: Recover securely when previously trusted device state expires.
Entry: Trust expiry event during privileged workflow
Steps:
- Detect expired device trust state.
- Pause pending privileged action.
- Prompt re-verification challenge.
- Re-establish trust or deny privileged continuation.
- Resume flow only on successful re-verification.
Success State:
- Expired trust is handled safely and privileged continuation is controlled.
J5. Session/Device Governance Promotion and Rollback#
Goal: Promote session/device policy changes safely and roll back on regressions.
Entry: Review & Approvals or Identity/Security alert
Steps:
- Review validation evidence for trust/revocation contracts.
- Promote release candidate.
- Monitor trust, revocation, and deny-rate telemetry.
- Roll back on regression indicators.
- Publish post-incident mitigation and prevention actions.
Success State:
- Policy release is stable or safely rolled back with full evidence.
2. Critical Edge Cases#
E1. Session Inventory Payload Missing Required Fields#
- Trigger: session record omits
sessionId,deviceId, orlastSeenAt. - Required behavior: mark inventory degraded and block privileged controls.
E2. Duplicate Session IDs in Inventory#
- Trigger: inventory response contains duplicate
sessionId. - Required behavior: quarantine invalid records and request inventory refresh.
E3. Unauthorized Actor Tries Revoke-All#
- Trigger: role lacks entitlement for global revocation.
- Required behavior: deny action and preserve all active sessions.
E4. Revocation Partial Failure#
- Trigger: some domain adapters fail revocation propagation.
- Required behavior: mark outcome
partial, retry propagation, and escalate.
E5. Device Trust Attestation Failure#
- Trigger: challenge/attestation fails validation.
- Required behavior: keep device untrusted and deny privileged continuation.
E6. Device Trust Expires Mid-Action#
- Trigger: trust TTL expires while privileged action is in-flight.
- Required behavior: pause action and require re-verification.
E7. Session Revoked Mid-Workflow#
- Trigger: active session revoked from another surface/device.
- Required behavior: stop privileged pipeline and require re-authentication.
E8. Multi-Tab Revocation Race#
- Trigger: concurrent tabs issue overlapping revoke requests.
- Required behavior: deduplicate by request id and keep deterministic outcomes.
E9. Telemetry/Audit Emission Failure#
- Trigger: session/device events fail to emit.
- Required behavior: buffer/retry and surface degraded observability warning.
E10. Missing Rollback Reference for Policy Release#
- Trigger: release candidate has no certified rollback contract.
- Required behavior: block production promotion.
3. Journey-to-Surface Mapping#
| Journey | Primary Surface | Supporting Surfaces |
|---|---|---|
| J1 Active Session Inventory and Device Visibility | Session & Device Management | Identity services |
| J2 Trusted-Device Enrollment for Privileged Operations | Session & Device Management | Authentication Architecture |
| J3 Session Revocation for Suspected Compromise | Session & Device Management | Security operations |
| J4 Device Trust Expiry and Re-Verification Recovery | Session & Device Management | Challenge services |
| J5 Session/Device Governance Promotion and Rollback | Review & Approvals | Observability, Security |
4. Instrumentation Requirements#
Required events:
studio_session_device.journey.startedstudio_session_device.journey.step.completedstudio_session_device.journey.blockedstudio_session_device.journey.recoveredstudio_session_device.journey.completed
Required dimensions:
userId,sessionId,deviceIdjourneyId,stepId,action,trustStateactorRole,outcome,latencyMs,errorCode
5. Acceptance Criteria (OST-00107)#
OST-00107 is complete only when:
- At least five session/device management journeys are documented.
- At least ten deterministic edge cases are documented.
- Journey-to-surface mapping is explicit.
- Instrumentation requirements and dimensions are documented.