---
id: ADR-PFM-OPS-006
title: 'Other services’ jobs are read through published views, read-only'
product_area: platform
module: operations
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
decision: >-
  Discover compatible job views in each service schema and merge scoped reads, leaving all writes with the
  owning service.
constrains:
  - SVC-PFM-OPS-jobs
  - WF-PFM-OPS-007
  - DOM-PFM-OPS-001
origin: >-
  services-platform:docs/jobs.md#Every macroservice's jobs in one list (the cross-service contract,
  2026-10-12)
alternatives:
  - option: Replicate jobs into Platform through events
    why_not: Replication would add another account that could lag behind the owner.
  - option: Maintain one central union view
    why_not: Every added service would require central view maintenance and a Platform release.
consequences:
  - Incomplete view contracts exclude a schema from discovery.
  - 'New publishers appear after fresh discovery, normally in a new process.'
  - Each owner supplies its own subject wording in its views.
supersedes: []
evidence:
  - >-
    macroservice-libraries at 54536a4: persistence/job-view-schemas.ts, cross-job-query.view.ts,
    cross-job-history.views.ts.
  - >-
    services-platform at ad3f6a6: modules/jobs/services/persistence/jobs.ts;
    tests/integration/services/snapshots/cross-service-jobs.integration.spec.js.
  - >-
    codex examination 2026-10-23: checked the pinned source anchors, planning references and enforcement
    boundaries; unresolved limits are recorded in module findings.
---

# Other services’ jobs are read through published views, read-only

## Context

Administrators need one monitor for work stored by multiple services.

## Decision

Read the owner-published root, step and event views through a cached schema catalogue. Query each schema under the caller’s scope and merge ordered results.

## Alternatives Considered

Event replication would require copy reconciliation. A central union would couple monitoring deployment to all publishers.

## Consequences

Compatible publishers can add kinds independently, with visibility limited by discovery caching.