---
id: TST-PFM-INT-627
title: Shared capability registry
kind: unit
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: macroservice-libraries
files:
  - packages/integration-contracts/src/registry.spec.ts
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The test process owns its inputs, fake clocks and any replaced runtime ports.'
test_cases:
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#lists the 54
      capabilities (the first set, the 0.3.0 and 0.4.0 additions, the shipping family, the storage write
      probe), once each
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#has a schema document
      for every capability, and a capability for every schema document
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#declares exactly the
      schema's features, and each feature unlocks fields that exist
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#has an example for every
      capability and one for every declared feature
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#gives every sensitive
      capability a lookup counterpart that exists, on the same major
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#requires an idempotency
      key of every sensitive capability, and is consistent about modes and budgets
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#names only known
      integration events
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#classifies every error
      code, and must_map draws only from the codes it may answer
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#sunsets a deprecated
      major at least ${MINIMUM_SUNSET_DAYS} days after its deprecation; only journal.export is deprecated
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#raises the minor of
      exactly the capabilities the minors changed
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#gives the accounting
      capabilities the destinations design's codes, and journal.post its shape
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#defines
      accounting.exchange_rates.pull as a plain read: sync, no key, nothing recorded withheld, the rate
      codes
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#defines
      files.destination.probe as chapter 10 section 5 has it: sync, no key, manage, the four codes all
      mapped
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/registry.spec.ts#defines the shipping
      family as the carrier port's operations: sync, the label sensitive and keyed with its lookup, the
      carrier's refusals
evidence:
  - 'macroservice-libraries:packages/integration-contracts/src/registry.spec.ts'
---
# Shared capability registry

## Verification Boundary

This unit suite exercises shared capability registry within the shared package. It records engineering coverage at the pinned revision without claiming a deployed run.

## What This Suite Proves

The source assertions cover the package behavior under controlled inputs. No detailed capability or feature scenario binding is verified in this registration.

## What It Does Not Prove

The suite does not establish deployed authorization, database behavior, provider effects or a complete customer workflow.

## Real Dependencies and Test Doubles

Imported package functions execute against the source-defined fixtures. Runtime ports, clocks and external transport responses remain controlled wherever the suite replaces them.

## Must Not Be Doubled

The shared function under test and its result assertions must execute. Returning an expected answer from a substitute does not prove the package behavior.