Metadata and Organization-defined Records
Purpose
This module supplies shared record descriptions and workspace configuration. It groups additional fields, presentation definitions, custom categories and their records, linked-record protocols and attachment staging. The capabilities hold the behavior; this charter identifies ownership and entry points.
Boundary
Application owners retain their native records and presentation selections. Security supplies grants, Queries supplies query and search consumers, Operations orchestrates loads, Integrations manages external destinations, Eligibility supplies referenced bindings and workspace lifecycle coordinates reset and deletion. Shared asset preparation participates in record saving.
Features
| Feature | Concepts | Capabilities | Journeys |
|---|---|---|---|
FEAT-PFM-MTD-01 — Record Type Catalogue | 1 | 4 | 0 |
FEAT-PFM-MTD-02 — Additional Fields and Attachments | 1 | 3 | 1 |
FEAT-PFM-MTD-03 — Record Presentations | 1 | 1 | 0 |
FEAT-PFM-MTD-04 — Organization-defined Record Categories | 1 | 3 | 2 |
FEAT-PFM-MTD-05 — Keeping Custom Records | 1 | 5 | 1 |
FEAT-PFM-MTD-06 — Linked Records | 1 | 3 | 2 |
Capabilities
| Capability | Title | Intent | Evidence |
|---|---|---|---|
CAP-PFM-MTD-001 | Keep the Record Catalogue Current | confirmed | observed |
CAP-PFM-MTD-002 | Describe Records for Shared Clients | confirmed | observed |
CAP-PFM-MTD-003 | Keep Configurability Within Product Scope | confirmed | observed |
CAP-PFM-MTD-004 | Use Workspace Labels for Standard Fields | confirmed | observed |
CAP-PFM-MTD-005 | Extend Records With Durable Custom Fields | confirmed | observed |
CAP-PFM-MTD-006 | Configure Field Requirements and Exposure | confirmed | observed |
CAP-PFM-MTD-007 | Prepare Image and File Uploads | confirmed | partially-observed |
CAP-PFM-MTD-008 | Manage Shared Forms and Record Layouts | confirmed | observed |
CAP-PFM-MTD-009 | Bring a Custom Record Type Into Use | confirmed | observed |
CAP-PFM-MTD-010 | Make Custom Records Discoverable | confirmed | observed |
CAP-PFM-MTD-011 | Control Custom Record Audiences | confirmed | partially-observed |
CAP-PFM-MTD-012 | Maintain Valid Custom Records | confirmed | observed |
CAP-PFM-MTD-013 | Retire or Publish Custom Records | confirmed | observed |
CAP-PFM-MTD-014 | Explain Custom Record Changes | confirmed | observed |
CAP-PFM-MTD-015 | Deliver Committed Record and Link Events | proposed | observed |
CAP-PFM-MTD-016 | Load and Reconcile Record Files | proposed | observed |
CAP-PFM-MTD-017 | Define Meaningful Record Relationships | confirmed | observed |
CAP-PFM-MTD-018 | Maintain Dated Links Between Records | confirmed | observed |
CAP-PFM-MTD-019 | Preserve Relationships Through Deletion and Merge | confirmed | observed |
Journeys
| Journey | Title | Browser policy |
|---|---|---|
JNY-PFM-MTD-001 | Create a club register and its first boat | required |
JNY-PFM-MTD-002 | Maintain a boat and inspect its changes | required |
JNY-PFM-MTD-003 | Limit a sensitive register to its assigned role | required |
JNY-PFM-MTD-004 | Define connections and maintain dated links | required |
JNY-PFM-MTD-005 | Apply deletion policies and consolidate duplicate endpoints | required |
JNY-PFM-MTD-006 | Add a contact field and inspect its description | optional |
Testing Artifact Tree
The design layer contains nineteen capability test specifications. The planning layer contains one cumulative acceptance suite for each of the six features. The implementation register identifies each existing executable suite and its scenario bindings; the structured tree names every artifact. Detailed coverage findings keep missing cases and unbound proposals visible.