Local by default
Engineering files, prompts, paths, tool parameters and results, sessions, checkpoints, and local knowledge remain on the customer workstation or AI BOX.
ENFORCED BY ARCHITECTURE04Security
The boundary is
part of the product.
PHYMER separates customer engineering context from vendor capability delivery, then makes each allowed crossing explicit and verifiable.
04.1Control register
Signed delivery
Capabilities are requested individually and checked for signature, type, version, stable identity, and content digest before use.
ENFORCED BY ARCHITECTUREExplicit authorization
Devices and capabilities require scoped authorization. Missing, expired, revoked, or incompatible authority fails closed.
ENFORCED BY ARCHITECTURERecoverable operations
Connection loss does not imply a physical operation stopped. Ownership, state, and human confirmation govern recovery.
ENFORCED BY ARCHITECTUREMinimal facts
Cloud-side records are limited to product and capability identity, authorization state, randomized request identifiers, version, timing, and fixed metering facts.
ENFORCED BY ARCHITECTUREHuman authority
State-changing or high-risk work exposes an approval step; computational completion is not physical validation or production approval.
ENFORCED BY ARCHITECTURE04.2Residency map
CUSTOMER ENVIRONMENT
Rich engineering context
- Models and geometry
- Prompts and conversations
- Tool inputs and outputs
- Operational state and checkpoints
- Local project knowledge
VENDOR CLOUD
Minimal control facts
- Public capability metadata
- Product and capability version
- Randomized authorization IDs
- Signed issuance state
- Fixed metering facts
HONEST LIMIT
Cryptographic delivery, transport security, memory-only handling, and sanitized releases reduce ordinary leakage and tampering risk. They do not promise absolute resistance against an actor with root or physical control of customer hardware.