How SPACE routes requests to the right sandbox execution

Evidence record

Perplexity architectural account describes execution-generation capabilities for correct-instance routing and their limits, without hardware remote attestation.

Read the original source ↗

Claim-level citations (3)

• supportsSPACE ties sandbox API capabilities to execution incarnation after migration: Perplexity describes signed capabilities binding sandbox identity and execution generation to target placement and permitted purpose in order to avoid stale-route confusion.

  Routing design: execution-incarnation capability and service routing

• supportsSPACE ties sandbox API capabilities to execution incarnation after migration: The architecture note does not claim a hardware attestation of in-guest code, and migration lease lifetime creates a separate revocation window from signature validation.

  Security guarantees and acknowledged limits

• supportsSPACE ties sandbox API capabilities to execution incarnation after migration: Perplexity describes signed route capabilities expiring after 120 seconds with a 15-second verification clock-skew allowance; retirement propagation and old-worker leases remain separate from signature validity.

  Execution capability lifetime, signature validation, routing and retirement limitations in October architecture note