Use one reviewed configuration to resolve project paths, Python imports, modules, and application lifecycle calls.
Input: A supplied YAML file, a real synthetic data file, and three supplied lifecycle functions.
Result: The cache task completes, a deliberate startup failure is reported, and shutdown still closes the synthetic database task.
Read the captured output | Inspect the example
Python 3.11 or newer. From the repository root:
python -m pip install -e .
python -m examples.walkthroughThe example uses synthetic material and runs offline. The captured output comes from executing this example, not a hand-written mockup.
Path aliases resolve relative to the configuration file and cannot escape that root. Import and module aliases resolve lazily. Sequential lifecycle calls collect named results and failures, allowing the caller to decide how to handle a failed startup.
Implementation: src/alias_resolver/resolver.py, src/alias_resolver/cli.py, examples/config.yaml.
YAML import targets execute Python code and must be trusted. Daemon-thread startup reports thread launch, not eventual completion or failures inside the thread. This is not a service supervisor.