Skip to main content

Asset Escalation and Ownership

Summary​

This page maps operational ownership to roles and states where named on-call ownership is not established. The asset/backend team owns the service and the frontend team owns the portal. Gateway, workflow, document, notification, database, security, QA, support, operations, and product are referenced by role. Named on-call ownership is not established in source and is therefore Requires confirmation. No escalation runbook or contact detail is invented here.

Audience​

  • Support engineers routing incidents.
  • DevOps engineers coordinating cross-service issues.
  • Product owners understanding responsibility boundaries.

Reference Content​

Role-based ownership​

ConcernOwning roleNotes
Asset-service (backend)Asset / backend teamOwns the service
Asset portal (frontend)Frontend teamOwns the portal
Gateway routingGateway roleReferenced by role
Workflow integrationWorkflow roleReferenced by role
Document integrationDocument roleReferenced by role
Notification deliveryNotification roleReferenced by role
Database / schemaDatabase roleReferenced by role
Security postureSecurity roleReferenced by role
VerificationQA roleReferenced by role
TriageSupport roleReferenced by role
Runtime operationsOperations roleReferenced by role
Product decisionsProduct ownerReferenced by role

Escalation flow​

Ownership boundary​

Roles are identified, but named individuals or an on-call rotation are not established in source. Any specific escalation contact, rotation, or response commitment is Requires confirmation.

Source References​

  • microservices/src/asset-service/Program.cs
  • microservices/src/gateway-api/Program.cs
  • microservices/scripts/smoke-asset.ps1

See Also​

Keywords​

asset ownership, escalation, roles, on-call requires confirmation, responsibility

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly