Configuration Graphs

Unified option shape

The configuration package owns the common model layer for service options. A graph can carry local and remote branches for a resource while keeping the resource identity, naming, and relationship information in one place.

Projection

Consumers project the unified graph into runtime option types after credential authority is known. For example, Azure service registration can bind local option types when authority is local and remote option types when authority is remote.

services.AddAzureServicesFactory(
    configuration,
    CredentialAuthority.Remote,
    builder =>
    {
        builder.ConfigureKeyVaultSecrets("KeyVaultSecrets");
        builder.ConfigureBlobStorage("StorageBlobs");
        builder.ConfigureAzureSql("AzureSql");
    });

csaed derivation

csaed derives configuration graph payloads from APB/APE definitions. Use csaed derive full-graph when an operator or automation pipeline needs a full configuration graph, and use bootstrap or launcher derivations for startup payloads.

Consumer libraries

• CopelandSyst.AzureServicesManagement registers Azure clients from projected options.
• CopelandSyst.AegiSentry uses secure column, key ring, and secure blob configuration.
• CopelandSyst.OpenAI uses credential-authority-aware OpenAI and Azure OpenAI provider options.
• CopelandSyst.Hosts.Template loads bootstrap metadata and full configuration during startup.