The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | listObjects | Open field configuration and inspect eligible record categories. | CAP-PFM-MTD-003 | Declared holders and available custom objects are selectable. | observed |
| 2 | /console/{tenantId}/configuration/{module}/fields/{recordType} | Create Member Since as a date property required by the console. | CAP-PFM-MTD-005 | The stored field includes its identity, display and creator. | observed |
| 3 | describeObject | Request the updated Contacts description. | CAP-PFM-MTD-002 | The new field follows standard fields and carries its requirement tier. | observed |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | The administrator retires and later restores Member Since. | Use the field lifecycle operations. | Descriptions omit the archived field and include it after restoration. | test services-platform:modules/metadata/tests/e2e/custom-fields.e2e.spec.js#describes the restored field again |
| failure | 2 | The target category lacks additional-field capability. | Creation returns the unsupported-capability explanation. | No definition is stored. | test services-platform:modules/metadata/tests/integration/services/registration/entity-capabilities.integration.spec.js#refuses a new custom field with the 400 problem |
| Id | Statement | Provenance |
|---|---|---|
01 | Descriptions include live custom fields after standard fields with requirement information. | test services-platform:modules/metadata/tests/e2e/custom-fields.e2e.spec.js#creates a field required by the API and describes its level, so the console and the portal can enforce theirs |
02 | Unsupported categories reject additional-field creation. | test services-platform:modules/metadata/tests/integration/services/registration/entity-capabilities.integration.spec.js#refuses a new custom field with the 400 problem |
End-to-end policy: optional: API evidence establishes creation and description. Consumer rendering belongs to a further browser acceptance check; the observed configuration path does not establish that complete journey.