---
id: FAS-CRM-ACT-01
feature: FEAT-CRM-ACT-01
product_area: crm
module: activities-tasks
revision: 1
status: proposed
product_intent: proposed
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  rhythm-v2-docs: 18a49edf30ee6bda18b159b65a2b91e093ea713d
capabilities:
- CAP-CRM-ACT-001
- CAP-CRM-ACT-002
- CAP-CRM-ACT-003
- CAP-CRM-ACT-004
- CAP-CRM-ACT-005
- CAP-CRM-ACT-006
- CAP-CRM-ACT-007
scenarios:
- id: FAS-CRM-ACT-01-01
  title: Record one meeting in every related context
  kind: behaviour
  exercises:
  - CAP-CRM-ACT-001
  - CAP-CRM-ACT-005
  relies_on:
  - ATS-CRM-ACT-001-02
  - ATS-CRM-ACT-005-04
  preconditions: A coordinator has two contacts and an organization with no prior interaction.
  steps:
  - do: Log one completed meeting with all three records.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-005
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts
  - do: Read each timeline and summary.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-005
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts
  expected: Each context contains one meeting with the same record identity and a single summary contribution.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to:
  - TST-CRM-ACT-034
  provenance: test
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts
- id: FAS-CRM-ACT-01-02
  title: Turn a shared meeting into visible follow-up work
  kind: interaction
  exercises:
  - CAP-CRM-ACT-001
  - CAP-CRM-ACT-002
  - CAP-CRM-ACT-005
  - CAP-CRM-ACT-010
  - CAP-CRM-ACT-014
  relies_on:
  - ATS-CRM-ACT-002-03
  - ATS-CRM-ACT-005-04
  preconditions: The activity type suggests follow-up work and the coordinator can create tasks.
  steps:
  - do: Log a linked meeting and request a named follow-up.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-002
    - CAP-CRM-ACT-005
    - CAP-CRM-ACT-010
    - CAP-CRM-ACT-014
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts
  - do: Read the primary contact Upcoming section and open My Open Tasks.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-002
    - CAP-CRM-ACT-005
    - CAP-CRM-ACT-010
    - CAP-CRM-ACT-014
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts
  expected: One meeting and one related task exist; the timeline and task view identify the same follow-up.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to:
  - TST-CRM-ACT-034
  provenance: test
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts
- id: FAS-CRM-ACT-01-03
  title: Correct and remove an entry while retaining its history
  kind: lifecycle
  exercises:
  - CAP-CRM-ACT-003
  - CAP-CRM-ACT-005
  - CAP-CRM-ACT-006
  relies_on:
  - ATS-CRM-ACT-003-04
  - ATS-CRM-ACT-003-07
  - ATS-CRM-ACT-006-02
  preconditions: An unlocked interaction links a contact and an organization.
  steps:
  - do: Correct the subject and linked-record set.
    exercises:
    - CAP-CRM-ACT-003
    - CAP-CRM-ACT-005
    - CAP-CRM-ACT-006
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0691.spec.ts
  - do: Inspect the changed timelines and revision, then delete the activity.
    exercises:
    - CAP-CRM-ACT-003
    - CAP-CRM-ACT-005
    - CAP-CRM-ACT-006
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0691.spec.ts
  - do: Read the live record and its revision list.
    exercises:
    - CAP-CRM-ACT-003
    - CAP-CRM-ACT-005
    - CAP-CRM-ACT-006
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0691.spec.ts
  expected: The correction updates the remaining timeline contexts; the live entry is absent after deletion
    and its attributed deletion revision remains.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to:
  - TST-CRM-ACT-035
  provenance: test
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0691.spec.ts
- id: FAS-CRM-ACT-01-04
  title: Read relationship context without gaining write controls
  kind: permission
  exercises:
  - CAP-CRM-ACT-001
  - CAP-CRM-ACT-003
  - CAP-CRM-ACT-005
  - CAP-CRM-ACT-006
  relies_on:
  - ATS-CRM-ACT-005-01
  - ATS-CRM-ACT-006-01
  preconditions: Reader, administrator and no-access personas inspect the same interaction.
  steps:
  - do: Read timeline, summary, record and history as each persona.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-003
    - CAP-CRM-ACT-005
    - CAP-CRM-ACT-006
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0715.spec.ts
  - do: Attempt logging, correction and removal as a reader.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-003
    - CAP-CRM-ACT-005
    - CAP-CRM-ACT-006
    provenance: test
    source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0715.spec.ts
  expected: Allowed reads remain available; reader mutations are forbidden and corresponding console controls
    are absent.
  negative: true
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to:
  - TST-CRM-ACT-059
  provenance: test
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0715.spec.ts
- id: FAS-CRM-ACT-01-05
  title: Repeat a meeting save without duplicating its follow-up
  kind: regression
  exercises:
  - CAP-CRM-ACT-001
  - CAP-CRM-ACT-002
  relies_on:
  - ATS-CRM-ACT-001-11
  - ATS-CRM-ACT-002-06
  preconditions: A client-selected time-ordered identifier accompanies an activity with a follow-up.
  steps:
  - do: Create, repeat and race the identical request.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-002
    provenance: test
    source: services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js
  - do: Read the resulting activity and count its follow-up tasks.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-002
    provenance: test
    source: services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js
  expected: Identical deliveries return the same activity and retain one task; changed content under the
    identifier conflicts.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to:
  - TST-CRM-ACT-006
  provenance: test
  source: services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js
- id: FAS-CRM-ACT-01-06
  title: Keep files aligned with correction and history
  kind: interaction
  exercises:
  - CAP-CRM-ACT-001
  - CAP-CRM-ACT-003
  - CAP-CRM-ACT-004
  - CAP-CRM-ACT-006
  relies_on:
  - ATS-CRM-ACT-004-02
  - ATS-CRM-ACT-004-03
  - ATS-CRM-ACT-006-02
  preconditions: An activity has two prepared file references.
  steps:
  - do: Save both files, remove one in a correction and inspect its revision.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-003
    - CAP-CRM-ACT-004
    - CAP-CRM-ACT-006
    provenance: proposed
    source: services-crm:modules/activities/services/persistence/activities.ts
  - do: Delete the activity and inspect released-reference cleanup requests.
    exercises:
    - CAP-CRM-ACT-001
    - CAP-CRM-ACT-003
    - CAP-CRM-ACT-004
    - CAP-CRM-ACT-006
    provenance: proposed
    source: services-crm:modules/activities/services/persistence/activities.ts
  expected: Retained files and revision sections reflect the corrections; deletion releases remaining
    references through shared cleanup.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to: []
  provenance: proposed
  source: services-crm:modules/activities/services/persistence/activities.ts
evidence:
- Pinned capability test specifications, related workflows and the scenario-specific code or suite sources.
coverage_findings:
- FND-CRM-ACT-068
- FND-CRM-ACT-069
- FND-CRM-ACT-070
- FND-CRM-ACT-050
- FND-CRM-ACT-051
- FND-CRM-ACT-052
- FND-CRM-ACT-053
---

# Interaction Records and Timelines: Feature Acceptance Suite

## What the Feature Must Do as a Whole

The feature acceptance checks follow shared interactions from entry to discovery, correction and retained history. Supporting files and follow-up work are checked where they meet the interaction record.

## Interactions Between Capabilities

A changed interaction affects several timelines, its revisions and any retained files. Initial follow-up creation adds ordinary task work, so acceptance checks compare both records and their read surfaces.

## Regression Record

| Revision | Change | Scenario | Why |
|---|---|---|---|
| 1 | initial | all | Establish cumulative acceptance across the feature and its related capabilities. |