Record Activity: Feature Acceptance Suite

What the Feature Must Do as a Whole

Record activity must connect successful visits with retained, authorized history. The feature cases follow visit identity, personal scope and retirement across recording, reading and storage.

Interactions Between Capabilities

Replay a visit without duplicating history. The replay does not create a second occurrence and both distinct visits are traversed once.

Retain history until workspace retirement. Raw history retains the visit until workspace retirement removes its owned activity.

Proposed chains require an executable suite that performs the complete sequence. Separate lower-level bindings do not establish whole-feature execution.

Regression Record

Revision	Change	Scenario	Why
1	initial	all	Establish cumulative whole-feature proof from the landed planning and design contracts.

Scenarios

5 scenarios proving FEAT-PFM-OPS-02 as a whole.

01 Follow a visit into personal history behaviour proposed

Exercises: CAP-PFM-OPS-008 CAP-PFM-OPS-009 CAP-PFM-OPS-010
Relies on: ATS-PFM-OPS-008-05 ATS-PFM-OPS-009-06 ATS-PFM-OPS-010-03
Preconditions: Two people have readable records in an isolated workspace.
Steps: [object Object]
Expected: Only the visiting person’s history names the recorded visit and its retained activity.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-008-05; ATS-PFM-OPS-009-06; ATS-PFM-OPS-010-03

02 Replay a visit without duplicating history interaction proposed

Exercises: CAP-PFM-OPS-008 CAP-PFM-OPS-009 CAP-PFM-OPS-010
Relies on: ATS-PFM-OPS-008-05 ATS-PFM-OPS-009-04 ATS-PFM-OPS-010-05
Preconditions: A person has a recorded visit and retains its occurrence key.
Steps: [object Object]
Expected: The replay does not create a second occurrence and both distinct visits are traversed once.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-008-05; ATS-PFM-OPS-009-04; ATS-PFM-OPS-010-05

03 Retain history until workspace retirement lifecycle proposed

Exercises: CAP-PFM-OPS-008 CAP-PFM-OPS-009 CAP-PFM-OPS-010
Relies on: ATS-PFM-OPS-009-02 ATS-PFM-OPS-010-08
Preconditions: A recorded visit names a record that is later removed; the workspace subsequently enters deletion.
Steps: [object Object]
Expected: Raw history retains the visit until workspace retirement removes its owned activity.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-009-02; ATS-PFM-OPS-010-08

04 Keep target authority separate from history authority permissionnegative proposed

Exercises: CAP-PFM-OPS-008 CAP-PFM-OPS-009 CAP-PFM-OPS-010
Relies on: ATS-PFM-OPS-008-02 ATS-PFM-OPS-009-01 ATS-PFM-OPS-009-06 ATS-PFM-OPS-010-04
Preconditions: Readers, an administrator and a foreign workspace caller have different reach.
Steps: [object Object]
Expected: Refused reports create no activity; each history response follows its own permission and workspace boundary.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-008-02; ATS-PFM-OPS-009-01; ATS-PFM-OPS-009-06; ATS-PFM-OPS-010-04

05 Keep visits stable across navigation and record loss regression proposed

Exercises: CAP-PFM-OPS-008 CAP-PFM-OPS-009 CAP-PFM-OPS-010
Relies on: ATS-PFM-OPS-008-08 ATS-PFM-OPS-008-09 ATS-PFM-OPS-009-02
Preconditions: A person opens a record, changes tabs and later loses the target record.
Steps: [object Object]
Expected: Navigation and transport retries retain the intended visit identities while committed history survives target removal.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-008-08; ATS-PFM-OPS-008-09; ATS-PFM-OPS-009-02

Planning

Record Activity: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

Interactions Between Capabilities ​

Regression Record ​

Scenarios

Record Activity: Feature Acceptance Suite

What the Feature Must Do as a Whole

Interactions Between Capabilities

Regression Record