Resolution and Status

Reference

Determine which value Custy uses and whether a documented property is fully implemented.

CommandCLI -> config.toml -> default

Quick Command

config.resolve(CLI_VALUE, CONFIG_PATH, DEFAULT)

priorityfallbackimplementation status

Priority 1

Explicit CLI

Priority 2

Project config

Priority 3

Built-in default

Required Missing

Configuration error

Overview

Most command resolvers use the same priority, but support is implemented per property. A key appearing in the generated file is not sufficient evidence that every command consumes it.

Effective-Value Flow

Workflow Timeline

Explicit CLI value

Use the invocation-specific value immediately.

current

Project configuration

When the CLI value is unspecified, look up the resolver's full path below tool.custy.

pending

Built-in default

Use the resolver or service fallback when the first two sources are absent.

pending

Required validation

Raise a configuration error when a required input remains unresolved.

pending

Value Semantics

Properties

Property	Type	Description	Default	Required
`Omitted / None`	Falls through	Allows configuration and then the built-in default to participate.	-	No
`Explicit true`	CLI override	Wins over project configuration.	-	No
`Explicit false`	CLI override	Normally remains an intentional value unless a resolver opts into special handling.	-	No
`Missing key`	Fallback	Uses the built-in default when one exists.	-	No
`Invalid present value`	Error	Is not treated as missing; parsing or typed validation can fail.	-	No

Implementation Status

Properties

Property	Description	Default	Required
`Active`	Read and applied by the current active resolver, service, pipeline, or template.	-	No
`Optional`	Supported by current code but commented out or omitted from the generated file.	-	No
`Mismatch`	The generated name or table shape differs from what active code expects.	-	No
`Loaded only`	Parsed into a model but not used by the current renderer or processing path.	-	No
`Experimental`	Loaded or partially implemented behavior whose contract may change.	-	No
`Reserved`	Generated for intended behavior but not consumed by the active command flow.	-	No

Continue

Related Commands

Commands commonly used together with this command.

All Properties

See the status and destination page for every key.

Configuration Concept

Learn the broader mental model.

Execution

Review the cross-command execution keys and mismatch.

Configuration File

Review loading and ownership boundaries.

Extending Configuration

Carry a new setting through templates, resolution, runtime use, tests, and docs.

Overview​

Overview