---
id: TST-PFM-MTD-131
title: write vocabulary
kind: unit
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/metadata/tests/unit/write-vocabulary.spec.js
implements:
  - ATS-PFM-MTD-001-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: >-
  Prepared integration database and the suite fixture records; fixture teardown restores or removes its own
  rows.
evidence:
  - 'services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js'
  - >-
    services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js#stores every field classification
    the library defines, and only those
  - >-
    services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js#stores every collection
    classification the library defines, and only those
  - >-
    services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js#never offers a collection the
    computed classification: only a column the owner derives is computed
  - >-
    services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js#defaults both to editable, so a
    manifest that says nothing leaves a client free to write
  - >-
    services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js#keeps no computed column: the flag
    a description carries is derived from the write access
  - >-
    services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js#keeps no system column either: a
    field is the platform\
fixture_imports:
  - 'node:assert/strict'
  - drizzle-orm/pg-core
  - '@rhythmsoftware/macroservice-metadata/object-description'
  - '@rhythmsoftware/macroservice-metadata/object-registration'
  - ../../db/registered-collections.table
  - ../../db/registered-fields.table
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-001-05
    provenance: test
    source:
      - >-
        services-platform:modules/metadata/tests/unit/write-vocabulary.spec.js#stores every field
        classification the library defines, and only those
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Write vocabulary

## Verification Boundary

This unit suite checks record descriptions and field configuration 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 imported contract and validation code runs locally. The fixture imports identify the setup seams; this register makes no broader claim that dependencies are undoubled.

## Must Not Be Doubled

The contract or validation function under examination must run directly; expected outputs cannot replace it.