Expand description
File and module discovery infrastructure for systemprompt.io.
Reads the active services-config (with include resolution and
deduplication), loads profile YAML, writes agent files, and discovers
extension manifests under extensions/. Sits one level above
systemprompt_config in the dependency graph so that domain crates
never need to know how the on-disk layout is structured.
§Modules
config_loader— loads and mergesservices.yamland its includes.config_writer— creates, edits, and deletes agent files.extension_loader/extension_binary_index— discover extension manifests and resolve binary paths.module_loader—inventory-driven extension discovery for the compiled-in extension trait registry.profile_loader— reads, validates, and writes profile YAML.bundle— signed services bundles: fetch, verify, compose, and the boot path that installs the active services root.vertex_discovery— boot-time catalog discovery: each provider’s credential decides whichCatalogSourcemay list it, and every priced, serverless model it returns is folded into the provider registry.boot—BootContext, the owned profile, secrets, resolved config and services root the entry crates build once at startup.services_state—ServicesState, the owned services config, its resolved catalog and the discovery report, built once at boot and handed to every consumer.error— public error types (ConfigLoadError,ConfigWriteError,ExtensionLoadError).
Copyright (c) systemprompt.io — Business Source License 1.1. See https://systemprompt.io for licensing details.
Re-exports§
pub use boot::BootContext;pub use bundle::BundleError;pub use bundle::BundleResult;pub use bundle::ServicesSourceBootstrap;pub use config_loader::ConfigLoader;pub use config_writer::ConfigWriter;pub use error::ConfigLoadError;pub use error::ConfigLoadResult;pub use error::ConfigWriteError;pub use error::ConfigWriteResult;pub use error::ExtensionLoadError;pub use error::ExtensionLoadResult;pub use error::ProfileLoadError;pub use error::ProfileLoadResult;pub use extension_binary_index::ExtensionBinaryIndex;pub use extension_loader::ExtensionLoader;pub use extension_loader::ExtensionValidationResult;pub use module_loader::ModuleLoader;pub use profile_loader::ProfileLoader;pub use services_state::DiscoveryFuture;pub use services_state::ServicesState;pub use services_state::catalog_context;
Modules§
- boot
- The owned boot sequence: profile, secrets, config, services root.
- bundle
- Signed services bundles: packing, fetching, verifying and composing.
- config_
loader - Reads, parses, and merges the active services configuration.
- config_
writer - Writes individual agent files and patches the top-level config to
drop their
includes:entries. - error
- Error types raised by the loader infrastructure.
- extension_
binary_ index - In-memory index of discovered extensions used to resolve binary paths at runtime, with a separate code path for cloud deployments where every binary lives in a single configured directory.
- extension_
loader - Discovers
extensions/<name>/manifest.yamlfiles and resolves the binaries those manifests reference. - module_
loader - Thin wrapper around the
inventory-driven extension registry. - profile_
loader - Reads, validates, writes and enumerates layered profiles.
- services_
state - The owned services-config state.
- subprocess
- Process supervision for the agent and MCP children this installation owns, and for its API server: the one place that spawns, identifies, probes and stops them.
- vertex_
discovery - Boot-time discovery of the models a deployment can actually serve.