Follow a record reference to the right page — acceptance

Coverage

The table separates scenarios with test bindings from proposed proof. A binding records a static examination of the test; it does not record a passing product test run.

Rule	Acceptance scenario
`BR-CAP-PFM-CSH-018-01`	`ATS-PFM-CSH-018-01` (bound)
`BR-CAP-PFM-CSH-018-02`	`ATS-PFM-CSH-018-01` (bound)
`BR-CAP-PFM-CSH-018-03`	`ATS-PFM-CSH-018-02` (proposed)
`BR-CAP-PFM-CSH-018-04`	`ATS-PFM-CSH-018-03` (proposed)
`BR-CAP-PFM-CSH-018-05`	`ATS-PFM-CSH-018-01` (bound)

Test Scenarios

3 scenarios proving CAP-PFM-CSH-018; 1 bound to an existing test.

01 Built-in references resolve only when their guards passunitnegativetest

Proves: BR-CAP-PFM-CSH-018-01 BR-CAP-PFM-CSH-018-02 BR-CAP-PFM-CSH-018-05
Preconditions: References cover permitted, denied, planned and parent-dependent built-in types.
Steps: Resolve each reference, including punctuation in the record identity.
Expected: Usable references produce encoded destinations; refused and incomplete references remain without links.
Data: Record-type and permission variants.
Bound to: react-console:lib/console/__tests__/record-destination.test.ts#opens a contact and an organization on their record screens
react-console:lib/console/__tests__/record-destination.test.ts#asks for the noun's own permission
react-console:lib/console/__tests__/record-destination.test.ts#answers null when the person may not open the record
react-console:lib/console/__tests__/record-destination.test.ts#answers null for a noun whose screen is not built
react-console:lib/console/__tests__/record-destination.test.ts#answers null for a child noun, whose URL needs a parent id
react-console:lib/console/__tests__/record-destination.test.ts#escapes the record id into the path
Source: react-console:lib/console/__tests__/record-destination.test.ts#opens a contact and an organization on their record screens

02 Custom references need a known definition and general read grantunitnegativeproposed

Proves: BR-CAP-PFM-CSH-018-03
Preconditions: The definition catalogue contains one custom type and omits another.
Steps: Resolve both types with and without general read authority.
Expected: A destination is returned only for the known permitted type.
Data: Custom definitions and permission checks.
Source: react-console:lib/console/record-types.ts

03 Unknown type construction and reference lookup fail differentlyunitnegativeproposed

Proves: BR-CAP-PFM-CSH-018-04
Preconditions: Names are absent from both destination catalogues.
Steps: Build an unknown record-type route and resolve an unknown object reference.
Expected: Route construction throws; reference lookup returns no destination.
Data: Unknown type and object names.
Source: react-console:lib/console/record-types.ts

Planning

Follow a record reference to the right page — acceptance ​

Coverage ​

Test Scenarios

Follow a record reference to the right page — acceptance

Coverage