Participant Relationship Protocol

Archived criterion

F35-PN: Pending

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Rationale

The current architecture permits transit and optional aggregation without transferring endpoint identity or application authority. This supports an infrastructure-only candidate but does not specify its complete deployment procedure. Current wire-v4 section 1.1 retires the prior HS2 establishment path and requires refusal where successor dependencies are unavailable. Member Route Intent separately withholds general ACCEPTED emission pending ROUTE-001. Reusing the retired handshake or assuming route activation would not establish the proposed before/after witness.

Assessment method

Primary specification review; no runtime experiment

Source context

Current PRP specification worktree, retained by hash; not a published snapshot

Outstanding qualification

Close a bounded native-PRP witness: identify the added intermediate routing/connectivity function, unchanged endpoint implementation/profile, admission and activation procedure, and before/after usable trajectory. For a witness needing new sessions, bind the successor establishment and session-installation contract; for Member Route Intent, resolve reciprocal generation, deferred results and alias lifetime under ROUTE-001. Alternatively identify an independently complete procedure over already valid sessions that avoids those dependencies. No full runtime benchmark is required for this architectural criterion. Existing valid state and non-HS2 RRL/AOP functions are not globally retired. This review changes only F35-PN evidence; it neither rejects PRP's architectural capability nor reclassifies other cells.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.