Configuration
Configuration controls topology, persistence, policy, cryptography, recovery budgets, evidence sinks and adapter behavior. Treat production configuration as versioned operational input and review changes before deployment.
Optional 1.4.0 profiles
These are host configuration contracts. Installing a package does not create credentials, run migrations, grant tools or activate autonomous work.
| Profile | Required configuration | Activation and recovery |
|---|---|---|
| AgentPlat Planner | Rooms 019, workflows 001, persistent stores and call receipts, verified identity/membership, authorized event resolver, bounded context and provider calls, explicit model prices, cumulative Room budget, independent reviewer and idempotent notification delivery | Keep the host feature flag disabled until wiring is complete. Start with owner-approved observation, then separately admit execution. Drain retains uncertain reservations and receipts. |
| Artifacts | Separate PostgreSQL namespace, artifact migrations 001–002, same schema for store and runner, verified tenant/owner context, current per-agent operation grants and content/retention limits | Register tools explicitly. A configured publisher also requires a monitored dispatcher and deduplicating consumers. HTML preview and download security belong to the host. |
| Persistent memory | The separately opted-in memory ledger, stable-agent subject, authorized personal/shared audiences and exact revision references | Apply the memory guide; the Planner/artifact upgrade does not automatically adopt this ledger. |
Keep provider credentials and database passwords in your existing secret mechanism. Version the non-secret model identifiers, price units, limits and schema names with the deployment. A health/readiness probe should inspect required migration status and fail closed; it must not migrate or enable a profile. Host-specific environment variable names are not universal SDK settings.
See the Planner setup, artifact example and coordinated migration procedure.