> ## Documentation Index
> Fetch the complete documentation index at: https://docs.evox.wraithesports.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Developer SDK overview
> Learn the evoX T1 local development and T2 default-deny public runtime model.
The evoX Developer SDK connects plugin behavior through a host-assigned identity and typed capability calls. A plugin cannot choose its own identity, profile binding or permissions through a runtime message.
Compare the T0, T1 and T2 boundaries.
Verify the counter example with a process and a mock host.
Validate the project, produce a browser bundle and package it.
Declare runtime, compatibility, permission and action fields.
Prepare the pack, upload it and submit it to Market moderation.
See the boundary between local development and public readiness.
## Core contract
* **T1 is not a sandbox.** It provides separate Node process lifecycle/crash isolation but may have the OS access of the user account.
* **T2 is default-deny.** The host-owned sandboxed Chromium Worker uses only declared ∩ granted capability calls.
* The public SDK provides no raw secret getter.
* A direct network, filesystem or process fallback does not count as T2 compatibility.
* Public executable upload/install stays closed until the production chain is complete.