---
id: ADR-MBR-STR-010
title: Record the Absence of Submissions Bindings
product_area: membership
module: structure
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The examined structure, configuration and term contracts expose no Submissions binding and record a reason
  for each administrative or internal operation.
constrains:
  - SVC-MBR-STR-structure
  - SVC-MBR-STR-configuration
  - SVC-MBR-STR-terms
  - RESP-MBR
origin: >-
  R2-ARCH-002 rule 1, publish or say why not, as cited by the landed corpus: services-
  platform:docs/standards/submission-compatible-operations.md#1. The rule (not readable in this job; FND-MBR-
  STR-039)
alternatives:
  - option: Bind unit creation to a new-chapter request form.
    why_not: >-
      A formation request would need a separately decided intake, approval and authorization process before it
      can safely call structural administration.
  - option: Expose organization links through officer self-service.
    why_not: The current workspace administration permissions do not define a scoped officer write contract.
consequences:
  - Current Submissions forms have no direct binding for these setup mutations.
  - Membership application intake belongs to the memberships module's separate seam.
  - A future intake use requires a fresh publication assessment and authorized contract.
supersedes: []
evidence:
  - >-
    services-membership at 5994c270: modules/structure/aws/api/structure.routes.ts;
    modules/configuration/aws/api/configuration.routes.ts; aws/terms/terms.routes.ts; aws/bin/publish-
    manifest.ts (subject kinds are the applications module's)
---

# Record the Absence of Submissions Bindings

## Context

The cited publication standard requires a binding or a documented reason for absence. Its full external text is unavailable, so this pass verifies local declarations without certifying the proposed exemption reasons as approved.

## Decision

No local operation publication is observed. Per-operation reasons document the administrative boundary and remain proposed, rather than turning absence into product approval.

## Alternatives Considered

Bind unit creation to a new-chapter request form. A formation request would need a separately decided intake, approval and authorization process before it can safely call structural administration. Expose organization links through officer self-service. The current workspace administration permissions do not define a scoped officer write contract.

## Consequences

Current Submissions forms have no direct binding for these setup mutations. Membership application intake belongs to the memberships module's separate seam. A future intake use requires a fresh publication assessment and authorized contract.