Engineer → Local
Intent, approved actions, and tool operations move through a profile-bound local channel.
02Architecture
Local intelligence.
Controlled capability.
Three endpoints divide responsibility so that customer engineering context stays local while governed capability can evolve independently.
02.1Interactive system map
CUSTOMER COMPUTE
Local AI BOX
Where intelligence is run and state is coordinated.
RESIDENT STATE
- Local model and agent runtime
- Sessions and operation ledger
- Policy and signed-capability verification
BOUNDARY CONDITION
Customer prompts, tool inputs, outputs, checkpoints, and operational state remain customer-side.
Select an endpoint to inspect its responsibility and data boundary. The line shows permitted coordination—not unrestricted data movement.
02.2Permitted flows
Local → Workstation
Typed tool calls reach local engineering software; operation state and results return customer-side.
Local → Cloud
Only public catalog requests, randomized authorization identifiers, product version, and fixed metering facts are permitted.
Cloud → Local
Authorized capability artifacts arrive individually with signature, type, version, and digest checks.