WHITE PAPER #16 · #17 · PATH FORMATION · LIFECYCLE

PATH
LIFECYCLE

In Velsanet, paths are not calculated — they form.
Once formed, they are not recalculated under change.

Paths persist as identity-bound stateful entities. Mobility is a state transition, not a re-formation. Make-before-break is the default. Lifecycle control resides exclusively in the network.

PATH STATE MODEL — CLICK EACH STATE
MAKE-BEFORE-BREAK HANDOVER SIMULATION
DEVICE MOVES FROM CELL A → CELL B · NO PACKET LOSS · NO RE-ROUTING
E2E PATH A
OVERLAP ZONE
E2E PATH B
T=0T=1 HANDOVER BEGINST=2 OVERLAPT=3 PATH A RELEASEDT=4
Path A remains Active while Path B is pre-formed in the target cell.
During overlap: both paths satisfy the original constraint profile.
Path A is released only after Path B is confirmed stable.
Zero packet loss. Zero re-routing. Zero identity revalidation.
LIFECYCLE INVARIANTS — NEVER VIOLATED
🔒
IDENTITY BINDING
A path is permanently bound to the originating identity. No lifecycle operation — mobility, reconfiguration, recovery — may alter or re-evaluate the identity binding. The path is the identity.
IMMUTABLE
📋
CONSTRAINT PROFILE
The constraint profile established at path formation cannot be expanded during the lifecycle. Internal reallocation (core, plane) is permitted within bounds. Any expansion triggers termination.
IMMUTABLE
🏛️
HIERARCHY SCOPE
The hierarchical scope of the path — which Q-layer domains it crosses — is fixed at formation. No reconfiguration may introduce new peers or expand the admissible topology domain.
IMMUTABLE
🗂️
LIFECYCLE RECORD
Every terminated path generates a lifecycle record: identity reference, all state transitions, mobility events, and termination cause. Records are retained for audit and structural verification.
ALWAYS RETAINED