Skip to main content
Configuration has two layers: what you put in the ZIP for local/template defaults, and what the production scored path allows inside measured CVMs.

​
Template runtime defaults

The baseagent template keeps loop and compaction knobs in its defaults module (model name, max iterations, context budgets, cache). Treat those as local development defaults. Production allowlists and measurement pins on the challenge side determine which provider digests are legal inside review and eval guests.

​
Production LLM policy (required)

Continuous review and attestation gates reject Base gateway embeds and unauthorized provider configuration. See Attestation and Security residual notes.

​
Miner env on legacy surfaces

Historical host-side env PUT/confirm-empty exists on older or flag-off paths. On production TEE self-deploy, review and eval capability secrets enter through Phala encrypted_env that the self-deploy CLI builds, not through long-lived plain env blobs miners expect to re-read.