Rule Library: Feature Acceptance Suite

What the Feature Must Do as a Whole

Staff can carry an expression from editable work through discovery, trial and release, then replace it without hiding its remaining dependencies.

Interactions Between Capabilities

Author, find and try a rule. Create a rule, save readable work, find it and try the draft on the subject.

Move dependencies before archiving. Inspect usage, transfer following uses and references, attempt archive, then resolve the remaining pins.

Restore an earlier expression while keeping work. Try the draft, roll back to the first expression, inspect history and try the retained draft again.

Separate writing from publication. Attempt discovery, saving, promotion, publication and archive with each role.

Keep existing expressions usable after vocabulary change. Deploy the alias-bearing declaration, inspect the authoring catalogue and try the retained expression.

Regression Record

Revision	Change	Scenarios	Reason
1	Initial	All	Establish cumulative feature proof from the existing planning and design contracts.

Show evidence (sources, provenance, origins, pinned commits)

Scenarios

5 scenarios proving FEAT-PFM-ELG-01 as a whole.

01 Author, find and try a rule behaviour proposed

Exercises: CAP-PFM-ELG-001 CAP-PFM-ELG-002 CAP-PFM-ELG-003 CAP-PFM-ELG-006
Relies on: ATS-PFM-ELG-001-04 ATS-PFM-ELG-002-03 ATS-PFM-ELG-003-01 ATS-PFM-ELG-006-07
Preconditions: An author and reader can access licensed conditions and a local subject.
Steps: Create a rule, save readable work, find it and try the draft on the subject.
Expected: The same expression is visible through discovery and trial, with an explanation and no retained trial decision.
Data: Run-owned workspace records, separate caller grants and a controlled clock for time-dependent checks.
Source: ATS-PFM-ELG-001-04,ATS-PFM-ELG-002-03,ATS-PFM-ELG-003-01,ATS-PFM-ELG-006-07

02 Move dependencies before archiving interaction proposed

Exercises: CAP-PFM-ELG-002 CAP-PFM-ELG-004 CAP-PFM-ELG-005
Relies on: ATS-PFM-ELG-002-06 ATS-PFM-ELG-004-03 ATS-PFM-ELG-005-05
Preconditions: A released rule has a follower, a pin and a referencing rule, plus a compatible replacement.
Steps: Inspect usage, transfer following uses and references, attempt archive, then resolve the remaining pins.
Expected: Discovery exposes the dependencies that control archive readiness and transferred references appear as new releases.
Data: Run-owned workspace records, separate caller grants and a controlled clock for time-dependent checks.
Source: ATS-PFM-ELG-002-06,ATS-PFM-ELG-004-03,ATS-PFM-ELG-005-05

03 Restore an earlier expression while keeping work lifecycle proposed

Exercises: CAP-PFM-ELG-001 CAP-PFM-ELG-003 CAP-PFM-ELG-004
Relies on: ATS-PFM-ELG-001-05 ATS-PFM-ELG-003-01 ATS-PFM-ELG-004-08
Preconditions: Two releases and a later draft exist.
Steps: Try the draft, roll back to the first expression, inspect history and try the retained draft again.
Expected: Rollback creates another release while the author’s later work remains available for testing.
Data: Run-owned workspace records, separate caller grants and a controlled clock for time-dependent checks.
Source: ATS-PFM-ELG-001-05,ATS-PFM-ELG-003-01,ATS-PFM-ELG-004-08

04 Separate writing from publication permissionnegative proposed

Exercises: CAP-PFM-ELG-001 CAP-PFM-ELG-002 CAP-PFM-ELG-004 CAP-PFM-ELG-005
Relies on: ATS-PFM-ELG-001-11 ATS-PFM-ELG-002-01 ATS-PFM-ELG-004-01 ATS-PFM-ELG-005-01
Preconditions: Reader, writer, publisher and retirement roles are separate.
Steps: Attempt discovery, saving, promotion, publication and archive with each role.
Expected: Refused actions leave work unchanged and each allowed action can be completed by its authorized role.
Data: Run-owned workspace records, separate caller grants and a controlled clock for time-dependent checks.
Source: ATS-PFM-ELG-001-11,ATS-PFM-ELG-002-01,ATS-PFM-ELG-004-01,ATS-PFM-ELG-005-01

05 Keep existing expressions usable after vocabulary change regressionnegative proposed

Exercises: CAP-PFM-ELG-001 CAP-PFM-ELG-003 CAP-PFM-ELG-006
Relies on: ATS-PFM-ELG-001-07 ATS-PFM-ELG-003-01 ATS-PFM-ELG-006-06
Preconditions: A released expression uses the former key of a renamed condition.
Steps: Deploy the alias-bearing declaration, inspect the authoring catalogue and try the retained expression.
Expected: Existing work remains usable while newly authored work can select the renamed condition.
Data: Run-owned workspace records, separate caller grants and a controlled clock for time-dependent checks.
Source: ATS-PFM-ELG-001-07,ATS-PFM-ELG-003-01,ATS-PFM-ELG-006-06

Planning

Rule Library: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

Interactions Between Capabilities ​

Regression Record ​

Scenarios

Rule Library: Feature Acceptance Suite

What the Feature Must Do as a Whole

Interactions Between Capabilities

Regression Record