---
id: TST-PFM-OPS-010
title: Cross job history views
kind: unit
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
repository: macroservice-libraries
files:
  - packages/jobs/src/persistence/cross-job-history.views.spec.ts
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: 'Process-local inputs, registries and test adapters.'
evidence:
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts at
    54536a441935c6e09fdb7f96f0bec71c52ba4e03: existing suite body, setup, assertions and cleanup.
binding_note: This existing engineering suite is registered without claiming a complete specification scenario.
assertion_sources:
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#selects from
    every registered family’s step table, and from nothing else
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#reads no root
    and no event table: a step view is the steps alone
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#joins the
    families with UNION ALL, one separator fewer than the branches
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#creates the view
    as security_invoker, so each branch is read with the caller’s own privileges
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#targets the
    qualified view name
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#stays read-only:
    no INSTEAD OF trigger and no rule, a union of families being no place to write a step
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#projects each
    branch’s own kind, then every step column of the contract in the contract’s order
  - >-
    macroservice-libraries:packages/jobs/src/persistence/cross-job-history.views.spec.ts#projects no
    family’s own column, the contract naming every column a step view answers
---

# Cross job history views

## Verification Boundary

This suite exercises background work through its declared function or structural boundary. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks exercise cross job history views within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. No complete specification scenario is attributed to this suite yet.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The production logic under assertion is real. Inputs, registries or source files supply the declared test data; no live service workflow runs.

## Must Not Be Doubled

The production function, registry or builder under assertion remains real.