The config/ directory should contain Configuration files that developers and runtime scripts use to build, run, observe, and validate the Phase 0 Baseline. These may include Node Configuration files, DDS Configuration files, QoS profile files, container Configuration files, logging Configuration files, and demonstration Configuration files.
A representative structure is:
config/
nodes/
dds/
qos/
logging/
demo/
Configuration files should use predictable names and should avoid machine-specific assumptions. They should not depend on absolute local paths, developer-specific usernames, personal directories, or unrecorded environment variables.
Where Configuration values differ across environments, the team should use templates, sample files, or documented environment variables. The Repository should distinguish shared Baseline Configuration from local developer overrides.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.