---
id: ADR-PFM-MTD-014
title: Current exclusion from Submissions
product_area: platform
module: metadata
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: The pinned module publishes no Submissions binding; configuration and reads are excluded, and custom-record
  intake is deferred pending a designed binding.
constrains:
- SVC-PFM-MTD-metadata
- SVC-PFM-MTD-layouts
- SVC-PFM-MTD-custom-objects
- SVC-PFM-MTD-associations
- SVC-PFM-MTD-files
origin: 'R2-ARCH-002 v2.0, Submission-Compatible Operations (Andrew, 2026-10-22; services- platform:docs/standards/submission-compatible-operations.md
  §1 rule 1); the portal pause for custom records (Andrew, 2026-10-18; services-platform:docs/custom-objects.md#19.
  Records: portal rules)'
alternatives:
- option: Publishing record intake immediately
  why_not: Current portal pause, absent member routes and missing binding preparation leave intake unfinished.
- option: Omitting compatibility classification
  why_not: The standard requires an explicit publication or a recorded reason for exclusion.
consequences:
- Operation rows record why no binding is published.
- A future configurable record-intake milestone must design and publish its binding before forms can use it.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: no binding declaration exists in the five modules; docs/standards/submission-compatible-operations.md'
---

# Current exclusion from Submissions

## Context

The binding standard requires a publication decision for business intake. Absence of binding code establishes current availability but does not approve indefinite exclusion.

## Decision

The pinned module publishes no Submissions binding; configuration and reads are excluded, and custom-record intake is deferred pending a designed binding.

## Alternatives Considered

Publishing record intake immediately: Current portal pause, absent member routes and missing binding preparation leave intake unfinished. Omitting compatibility classification: The standard requires an explicit publication or a recorded reason for exclusion.

## Consequences

Operation rows record why no binding is published. A future configurable record-intake milestone must design and publish its binding before forms can use it.