Configuration Boundaries
See which AutoCore decisions belong to the platform, edition, installation, market, or external provider.
Configuration ownership is part of the product model. The same value can be safe at one layer and dangerous at another, so documentation names the owner before describing a setting.
| Owner | Examples | Not implied |
|---|---|---|
| Shared platform | API contracts, schema meaning, authorization semantics | That every future feature is enabled |
| Edition | Brand, bundled locale, market defaults, namespaces, provider availability | That an edition is a second market control plane |
| Installation | Initialization, selected edition, primary market, legal profile, payment configuration | That external credentials are bundled |
| Primary market | Country, city, currency, timezone, distance unit, category capability | That all categories or providers are active |
| External provider | Storage, email, payment, monitoring, DNS, TLS | That the customer has completed onboarding |
Change risk
Values that affect identity, data interpretation, public visibility, legal records, or financial records require a reviewed migration or release decision after production data exists. Environment variables are validated, but validation is not the same as commercial readiness.
Public-safe rule
Public documentation uses placeholders such as ${DATABASE_URL} or
api.example.com only when a later procedural page needs an example. It never
publishes real credentials, hostnames, paths, IP addresses, or provider account
references.