Archived criterion

C08-PI: Yes

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

Rationale

Bounded architectural capability for interior transit A in S -> X -> A -> B -> D: both adjacent members are intermediaries, use their own identities, and A neither hosts endpoint publication/rendezvous nor terminates the deeper protected exchange. Member Route Intent sections 2/4/5 identify adjacent source and target; wire-v4 keeps deeper content opaque. Required forwarding/relationship state need not therefore contain a history of final S/D identities. Select no optional final-identity traffic logging or role co-location. This is not a claim that all runtime databases are empty or that first/last hops have the same privacy.

Assessment method

Documentary analysis

Source context

Primary specification / explicit profile inference

Outstanding qualification

Bind the interior-transit composition to executable ROUTE-001 and capture control/data plus memory, SQLite/WAL, diagnostics, telemetry and backups after communication. Runtime store_result persists the requested target even when unresolved; distinguish valid adjacent-member requests from arbitrary identifiers supplied by peers. Verify deeper identities are not learned by another role, record adjacent-identity retention, and audit cleanup separately. No implementation-wide retention audit, secure erasure, legal compliance or traffic-correlation immunity is established.

Public sources

Editorial evidence references

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

• index.html#round047