design-time graph -> runtime valuesConfiguration, graph and documentation
Every service carries enough generated metadata to connect runtime behavior back to the architecture.
When to use
Use this reference when generating, reviewing or operating a Service Architect project.
Behavior
- config/config.yaml contains the generated runtime configuration shape and defaults.
- config/overrides.yaml is the preserved environment/project override layer.
- graph/<service>.generated.yaml is the service-level topology snapshot.
- graph/<project>.generated.yaml is the complete project topology snapshot.
- docs contains generated domain and endpoint documentation derived from graph types and descriptions.
- Runtime status endpoints use the same graph identity for topology visualization.
Configuration and documentation files
Generated and preserved metadata found at project and service scope.
<service>/config/config.yamlManagedRuntime defaults and graph-derived connector/endpoint settings.
<service>/config/overrides.yamlPreservedEnvironment-specific values and feature enablement.
<service>/config/docker_overrides.yamlManagedContainer-specific TypeScript endpoint addresses and runtime values.
<service>/config/config_vars.yamlManagedC++ variable expansion values.
<service>/static_config.yamlManageduserver static component configuration.
<service>/graph/*.generated.yamlGeneratedService topology snapshot.
graph/*.generated.yamlGeneratedComplete project topology snapshot.
<service>/docs/*.mdGenerated initiallyType, stream and endpoint documentation associated with the service.
README.mdPreservedWorkspace or component quickstart and public command summary.
spec/User ownedImplementation tasks, rules, prompts and progress outside generator ownership.
Runtime configuration layers
config/config.yaml # generated defaults
config/overrides.yaml # project/environment overrides
environment variables # deployment overrides
Kubernetes ConfigMap # rendered non-secret settings
Kubernetes Secret # operator-owned credentials