The boundary is part of the product.
Arctite separates local development activity, cloud account infrastructure, and third-party inference into explicit architectural boundaries. Each zone has a defined role - and a defined limit.
Three zones. One narrow path between them.
Everything below is drawn as the system actually behaves. Arrows represent the only allowed flows.
ARCTITE SYSTEM · ZONES
Local developer environment
everything that touches your code
- Project files
- Git metadata
- Terminal metadata
- Approved browser context
- Clipboard context
- Notes
- Context Engine
- Redaction
- Context Preview
- Guides
- Agent Cycles
- Recovery
- Activity
- Evolution Lab
APPROVED INFERENCE PAYLOAD
frozen · digest-bound · user-approved - the only outbound context
ACCOUNT SIGNALS
auth · licensing · entitlement checks only
User-selected inference
the provider you chose, via your key
- OpenAI
- Anthropic
- OpenRouter
- Local models
Only approved inference payloads are sent. Local models never leave your machine.
Arctite cloud control plane
account and licensing infrastructure
- Authentication
- Accounts
- Billing
- Subscriptions
- Licensing
- Entitlements
- Devices
- Organizations / teams
Used where applicable - never as a repository or context-history store.
No data path exists between zone 02 and zone 03. Inference and account infrastructure never share a project-data plane.
Context stays in zone 01
Source assembly, redaction, previews, guides, and execution state live in the local developer environment. There is no background upload of repositories or context histories.
One narrow egress
The only context that leaves is the approved inference payload - frozen, digest-bound, and sent to the provider you selected. Every other path is closed by design.
Cloud means accounts, not data
The cloud control plane handles authentication, licensing, and entitlement state. It is not a project-data plane, and it is not a context store.
What actually crosses each boundary.
Zone 01 → Zone 02
Approved inference payload
The frozen package and its digest. Nothing else. Retries require a fresh review.
Zone 01 → Zone 03
Account and license signals
Authentication, entitlement, and licensing checks. No project files, no context.
Zone 02 ↔ Zone 03
No data path
Inference and account infrastructure are separate. The provider never sees your Arctite account state.