Inspect background runs within customer reach

Purpose

Help customer administrators understand background activity within the records they may reach.

How It Works

A customer administrator opens Scheduled Jobs from Maintenance. The page reads the active workspace’s runs, presents readable subjects and supports type and status filtering. Opening a row shows a read-only progress and history panel. Active work refreshes while the panel remains open. The separate customer-wide read follows customer and workspace reach and excludes jobs with no customer attribution. The workspace read includes those runs when their workspace matches. Missing authority produces a refusal rather than a misleading empty list. Staff working through an access grant use the granted workspace’s surface rather than gaining the broader customer monitor.

Relationships

The job record supports reconciliation, notices and both monitors; owning modules retain responsibility for the work itself.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: The administrator can inspect runs within the permitted workspace and customer scope.Job inspection leaves execution and persisted job state unchanged.
Surfaces: consoleapi
Preconditions: The caller holds workspace jobs-read authority, including the console’s equivalent Scheduled Jobs key.
Postconditions: Job reads leave stored job records unchanged.
Constraints: Workspace-scoped reads use that workspace context so published subjects can resolve its records.
Intent sources: services-platform:docs/jobs.md#A tenant's job runs (2026-10-16) (Andrew, 2026-10-16)react-console:components/console/nav-config.ts:maintenanceArea (Andrew, 2026-10-16: Maintenance holds only Scheduled Jobs)

Controls

29 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`platform.jobs.read`	api	tenant
`maintenance.scheduled-jobs.view`	console	tenant

Business Rules

10 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 10 confirmed by a product decision, the rest inheriting this capability's confirmed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Customer job reads require the customer jobs read permission, HQ reads require staff jobs read authority, and every job route performs a read. proved by `ATS-PFM-OPS-005-01`, `TST-PFM-OPS-067`	permission	api	test services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js#declares the customer monitor and the tenant runs console, with platform.jobs.read
`02`must prove Confirmed	The customer monitor restricts jobs to the caller’s customer and workspace reach, returning an inaccessible customer’s job as not found. proved by `ATS-PFM-OPS-005-02`, `ATS-PFM-OPS-005-10`, `ATS-PFM-OPS-006-06`, `TST-PFM-OPS-067`	permission	api, service	test services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js#says of another customer's job exactly what it says of an unknown one
`03`must prove Confirmed	The workspace monitor includes all services’ jobs for that workspace, including customer-less snapshot runs excluded from the customer-wide monitor. origin: services-platform:docs/jobs.md#A tenant's job runs (2026-10-16) proved by `ATS-PFM-OPS-005-03`, `ATS-PFM-OPS-007-07`, `TST-PFM-OPS-066`	policy	service	test services-platform:modules/jobs/tests/e2e/jobs-tenant-runs.e2e.spec.js#answers exactly the tenant's jobs, of every macroservice
`04`must prove Confirmed	An unreached workspace is refused, and staff entry through a workspace grant permits that workspace’s runs without granting access to the customer-wide monitor. origin: services-platform:docs/hq/rhythm-hq-plan.md#D1 (rule S1) proved by `ATS-PFM-OPS-005-04`, `TST-PFM-OPS-066`	permission	api	test services-platform:modules/jobs/tests/e2e/jobs-tenant-runs.e2e.spec.js#is refused a tenant of the same customer the grant does not name
`05`must prove Confirmed	Portal callers are refused job reads as a context mismatch, and unauthenticated callers cannot read jobs. proved by `ATS-PFM-OPS-005-05`, `TST-PFM-OPS-066`	permission	api	test services-platform:modules/jobs/tests/e2e/jobs-tenant-runs.e2e.spec.js#refuses a portal caller as a context mismatch
`06`must prove Confirmed	Job lists continue from a timestamp-and-identity cursor and reject malformed cursors, invalid statuses and malformed kinds; unknown correctly shaped kinds return an empty result. proved by `ATS-PFM-OPS-005-06`, `TST-PFM-OPS-067`	validation	api	test services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js#refuses a cursor it did not issue
`07` Confirmed	The kind list reports labels and owning applications for kinds present in scope, and the console requests run counts separately.	calculation	service, console	observed services-platform:modules/jobs/aws/api/jobs.routes.ts:toApiJobKinds; react-console:lib/maintenance/use-job-runs.ts
`08`must prove Confirmed	Job snapshots expose summaries, steps, attempts, published definitions and events while omitting execution handles and row versions; event reads can resume after a sequence. proved by `ATS-PFM-OPS-005-07`, `TST-PFM-OPS-067`	policy	api	test services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js#never puts the execution handle or the row version on the wire
`09`must prove Confirmed	Maintenance contains Scheduled Jobs alone, and missing jobs-read authority suppresses its link and shows Access Denied. origin: react-console:components/console/nav-config.ts:maintenanceArea (Andrew, 2026-10-16) proved by `ATS-PFM-OPS-005-08`, `TST-PFM-OPS-055`	permission	console	test react-console:e2e/mock/maintenance-job-runs.mock.spec.ts#is the console's Access Denied state, and its link is not offered
`10` Confirmed	Scheduled Jobs presents run type, application, subject, status, timing and requester, labels automatic runs Scheduled, and opens a read-only panel that refreshes active work. origin: services-platform:docs/jobs.md#A tenant's job runs (2026-10-16)	policy	console	test react-console:e2e/mock/maintenance-job-runs.mock.spec.ts#lists the tenant's runs: what each was about, its status, and who started it

Scenarios

Id	Given	When	Then	Provenance
`01`	A workspace has snapshot, merge and rebuild runs alongside jobs from another workspace.	The administrator requests that workspace’s Scheduled Jobs.	The workspace’s runs are returned and the snapshot subject includes its month.	inferred services-platform:modules/jobs/tests/e2e/jobs-tenant-runs.e2e.spec.js#names Platform's snapshot run by its snapshot and month
`02`	A customer user supplies the identity of another customer’s job.	The user opens that job through the customer monitor.	The response treats it as an unknown job.	inferred services-platform:modules/jobs/tests/e2e/jobs.e2e.spec.js#says of another customer's job exactly what it says of an unknown one

Planning

Implementation

Inspect background runs within customer reach ​

Purpose ​

How It Works ​

Relationships ​