---
id: TST-PFM-MTD-137
title: Custom object API journey 0404
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/data-operations/CO-ACC-0404.spec.js
implements:
  - ATS-PFM-MTD-016-07
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/data-operations/CO-ACC-0404.spec.js'
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 1: a
    read-only volunteer is refused 403 permission_missing, naming no key, and no job is made
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 2: an
    anonymous caller is refused 401 on the submit and on the list
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 3:
    another tenant’s staff are refused 403 on both surfaces, and no job is made in tests
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 4: the
    registrar submits the same request and both boats are created
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 5: a
    clerk with the create key only has the known key refused as not found and the new key created
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 6: a
    built-in administrator’s line of the roles_only object is refused not found
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 7: the
    valuer assigned to the object loads the same line and reads the record back
  - >-
    services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 8: the
    create-only clerk reading the registrar’s job results is answered 404
fixture_imports:
  - chai
  - drizzle-orm
  - ../../support
  - ./area
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-016-07
    provenance: test
    source:
      - >-
        services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 1:
        a read-only volunteer is refused 403 permission_missing, naming no key, and no job is made
      - >-
        services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 5:
        a clerk with the create key only has the known key refused as not found and the new key created
      - >-
        services-platform:tests/acceptance/custom-objects/journeys/data-operations/CO-ACC-0404.spec.js#step 8:
        the create-only clerk reading the registrar’s job results is answered 404
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Custom object API journey 0404

## 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.