Skip to content

CAP-PFM-MTD-004Use Workspace Labels for Standard Fields

Markdown

CAP-PFM-MTD-004

Use Workspace Labels for Standard Fields

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

Planning

Feature
FEAT-PFM-MTD-01
Exercised by
FAS-PFM-MTD-01-01, FAS-PFM-MTD-01-03
Key concepts
CON-PFM-MTD-001
Actors
ACT-PFM-007
Depends on
CAP-PFM-MTD-001
Related
CAP-PFM-MTD-002
Proved by
ATS-PFM-MTD-004

Implementation

Executable suites
TST-PFM-MTD-108, TST-PFM-MTD-124

KindCapabilityProduct areaPlatformModuleMetadata and Organization-defined RecordsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
Staff can use familiar terminology for information that Rhythm already defines.Removing the override restores the owner label.
Surfaces
consoleapi
Preconditions
The selected field is a live registered standard field.
Intent sources
services-platform:docs/metadata.md#Label overridesservices-platform:docs/metadata.md#Acceptance checkpoints (2026-10-08 Final acceptance, accepted by Andrew)

Controls

19 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-003 TC-DAT-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

KeyChecked atScope
platform.field-labels.updateapitenant

Business Rules

6 rules, 6 to be proved before approval. A rule's product intent is derived from its origin: 6 confirmed by a product decision, the rest inheriting this capability's confirmed.

IdRuleKindEnforced atProvenance
01must prove
Confirmed
A standard-label request may change the label alone and rejects attempts to alter visibility, requirement, type or presentation.
validationapi, servicetest
02must prove
Confirmed
Relabelling requires a live registered standard field; custom keys, undescribed columns, missing types and retired fields return not found, while prior overrides survive field retirement.
validationservice, databasetest
03must prove
Confirmed
An override label contains between one and two hundred characters after trimming.
validationapi, service, databasetest
04must prove
Confirmed
Workspace relabelling changes neither the owning declaration nor labels seen in other workspaces.
invariantservice, databasetest
services-platform:modules/metadata/tests/e2e/standard-field-label-overrides.e2e.spec.js#shows the other tenant the owner's label on the same field
05must prove
Confirmed
Removing an override returns the owning label, and removing an absent override succeeds while reporting that no override was removed.
lifecycleservicetest
services-platform:modules/metadata/tests/e2e/standard-field-label-overrides.e2e.spec.js#answers removed false for a field the tenant never overrode
06must prove
Confirmed
Setting a replacement label retains the original creator and increments the override version.
lifecycleservicetest

Scenarios

IdGivenWhenThenProvenance
01One workspace has renamed a standard contact field.Describe Contacts from that workspace and a second workspace.The first receives its override and original label, while the second receives the owning label.test
services-platform:modules/metadata/tests/e2e/standard-field-label-overrides.e2e.spec.js#describes the field with the tenant's label and the owner's original

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.