---
id: ADR-PFM-SEC-012
title: Submissions publication exclusions
product_area: platform
module: security
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: Record all observed module operations as unpublished to Submissions with an administrative, read
  or identity-handling reason; no binding declaration is present.
constrains:
- SVC-PFM-SEC-security
- SVC-PFM-SEC-tenants
- SVC-PFM-SEC-customers
- RESP-PFM
origin: R2-ARCH-002 v2.0 (Andrew, 2026-10-22) rule 1, publish or say why not
alternatives:
- option: Publish password-bearing portal registration as intake.
  why_not: A capture form cannot carry credential or verification secrets; confirmed identity provisioning
    follows the dedicated identity flow.
- option: Omit an explicit publication declaration.
  why_not: The cited standard requires either a binding or a reason for withholding each operation.
consequences:
- Future business intake belongs to its owning domain and links the resulting business record to identity through
  its permitted contract.
- The domain chapter covering components, bindings and templates must be supplied before the first intake milestone.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: the records named in origin and the code cited by the constrained artifacts'
examined_at: '2026-10-23'
examiner: codex
---

# Submissions publication exclusions

## Context

The service rows supply operation-level publication status and reasons required by the existing standard. No current code binding contradicts those exclusions.

The proposed domain record remains open; this examination does not approve a future unpublished intake operation.

## Decision

Record all observed module operations as unpublished to Submissions with an administrative, read or identity-handling reason; no binding declaration is present.

## Alternatives Considered

Publish password-bearing portal registration as intake. A capture form cannot carry credential or verification secrets; confirmed identity provisioning follows the dedicated identity flow.

Omit an explicit publication declaration. The cited standard requires either a binding or a reason for withholding each operation.

## Consequences

Future business intake belongs to its owning domain and links the resulting business record to identity through its permitted contract.

The domain chapter covering components, bindings and templates must be supplied before the first intake milestone.