---
id: ADR-CRM-ACT-015
title: No activities or tasks operation is published to Submissions yet
product_area: crm
module: activities-tasks
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Declare the locally inspected staff, configuration, service and health operations
  without a Submissions binding, and keep external publication status as an explicit proof
  gap.
constrains:
  - SVC-CRM-ACT-activities
  - SVC-CRM-ACT-tasks
origin: >-
  R2-ARCH-002 (operations that capture a request are published to Submissions with a
  contract version, or state why not); no Submissions process at the pinned revisions
  captures activities or tasks.
alternatives:
  - option: Publish public or portal interaction capture now.
    why_not: >-
      No current planning capability establishes that intake process or its versioned
      contract.
  - option: Publish the directly invoked workflow task dispatcher as intake.
    why_not: >-
      Its service-operation boundary is not a locally declared captured-submission
      process.
consequences:
  - >-
    A future portal or form capture needs its own product decision and versioned
    publication contract.
  - >-
    Each service-operation row records the local reason for no publication and the
    applicable external proof limit.
supersedes: []
evidence:
  - >-
    services-crm at a8d1364f: modules/activities/aws/api/activities.routes.ts;
    modules/tasks/aws/api/tasks.routes.ts, tasks-service.routes.ts; no Submissions binding
    found in modules/activities or modules/tasks.
---

# No activities or tasks operation is published to Submissions yet

## Context

The architecture requires an explicit publication disposition for service operations. Local routes identify their caller boundary but cannot by themselves prove all external bindings.

## Decision

Neither inspected CRM module declares a Submissions binding. Health serves deployment monitoring, configuration serves administration, and workflow actions use direct service invocation. The examination qualifies the original global absence claim rather than confirming external publication.

## Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

## Consequences

The contract rows record local evidence and remaining uncertainty. Product and integration owners must establish any external intake binding before publication completeness is accepted.