Environment configuration

Documentation status: guide — see Maturity and evidence.

The conceptual model should stay stable across development and release environments. Configuration binds that model to the concrete runtime topology.

The guide's graph example, normalized for public names, is:

# Development
graphKind: MemoryRichGraph
graphParams: [Workspace]/Graph

# Release
graphKind: PersistentRichGraph
graphParams: [BasePath]/Graph

Recommended first-run order:

1. start with a memory configuration;
2. verify package activation;
3. verify the manifest exposes the expected model;
4. resolve the concept/class through the runtime container;
5. open the view and verify data bindings;
6. switch to persistent storage;
7. verify database aliases and maps;
8. activate external services only after the model is healthy.

Do not copy secrets into reusable packages. Ports, credentials, local paths, remote endpoints, and deployment-only switches belong to environment configuration or secret management.