---
id: TST-PFM-MTD-139
title: Custom object API journey 0015
kind: api-lifecycle
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js
implements:
  - ATS-PFM-MTD-009-10
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Prepared integration database and the suite fixture records; fixture teardown restores or removes its own
  rows.
evidence:
  - 'services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js'
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 1: the
    impl admin defines and activates vessel with three properties and two rules, and creates two vessels
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 2: the
    system resets impl_{run}; the custom objects participant empties its records and keeps its objects
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 3: the
    database keeps vessel active and holds none of impl_{run}'s properties, rules, records or unique values
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 4: the
    impl admin puts vessel back unchanged and is refused: its display property is gone
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 5: the
    impl admin reloads the three definitions through the platform.custom_fields data operation
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 6: the
    reloaded fields carry no rules, and two vessels may hold the same reg_no
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 7: the
    system deletes impl_{run} through the tenant lifecycle; the objects go before the types they name, and
    nothing of the tenant is left
fixture_imports:
  - chai
  - drizzle-orm
  - ../../../../../aws/api/platform-api-handler
  - ../../../../../aws/api/platform.routes
  - '@rhythmsoftware/macroservice-testing/signed-context'
  - ../../../../../db/seeds/integration/seed
  - ../../../../e2e/staff-context
  - ../../../../../modules/tenants/services/persistence/tenants
  - ../../../../../modules/tenants/services/access/tenant-availability
  - ../../../../../modules/tenants/tests/integration/deletion-support
  - ../../../../../modules/tenants/services/deletion/tenant-purge-workflow
  - '@rhythmsoftware/macroservice-execution/tenant-time-zones'
  - ../../support
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-009-10
    provenance: test
    source:
      - >-
        services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 3: the
        database keeps vessel active and holds none of impl_{run}'s properties, rules, records or unique
        values
      - >-
        services-platform:tests/acceptance/custom-objects/journeys/definitions/CO-ACC-0015.spec.js#step 4: the
        impl admin puts vessel back unchanged and is refused: its display property is gone
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Custom object API journey 0015

## Verification Boundary

This API suite checks custom record journeys within the local test harness. The registered file and pinned revision define its boundary.

## What This Suite Proves

The bindings identify the detailed or feature scenarios whose outcomes have assertions in this suite. Original case references remain attached to the detailed scenarios so a reviewer can inspect the exact assertion. Assertions are evidence of implemented checks; no execution result is claimed.

## What It Does Not Prove

The register does not establish a current passing run or full specification conformance. Behavior outside the suite’s fixtures and assertions remains unverified.

## Real Dependencies and Test Doubles

The fixture uses PostgreSQL and the imported persistence or API code. The fixture imports identify the setup seams; this register makes no broader claim that dependencies are undoubled.

## Must Not Be Doubled

The operation under examination and its asserted stored outcomes must remain real within the declared harness. A fixture cannot replace the write, refusal or transactional effect that the bound scenario checks.