Infrastructure and runtime
The deployment contract declares the frontend behind Caddy, a systemd-managed API on AX42 and self-hosted Supabase services. The marketing site is separate. Toolora uses shared infrastructure under explicit ownership contracts. The runtime map describes the declared topology; current running versions require separate observation.
Runtime components and services
Section titled “Runtime components and services”Caddy serves the frontend release and proxies the declared Supabase paths. FastAPI runs as the Toolora API service. Its scheduler lifecycle is tied to the application process. Background jobs therefore need component-aware diagnosis. The exact units, ports and release paths remain in the deployment contract.
Runtime components and entry points provides the detailed contract, examples and verification limits.
Configuration and service identities
Section titled “Configuration and service identities”Runtime configuration is supplied through protected component files and the installed broker. Service identities and supplementary groups determine access to those files. Commands that need shared API configuration must follow the documented execution identity. Credential handling preserves ownership and avoids secret values in arguments, logs or repository files.
Runtime identities and configuration provides the detailed contract, examples and verification limits.
Release directories and publication
Section titled “Release directories and publication”Application publication builds an exact Git commit into a release directory and switches the current release under shared locks and health checks. Frontend and API have separate versions. Release procedure verifies that publication preserves already deployed work and respects the applied schema before changing a running component.
Release directories and publication provides the detailed contract, examples and verification limits.
Shared infrastructure ownership
Section titled “Shared infrastructure ownership”The estate owns shared capabilities such as backup implementation and connector contracts. Toolora owns its product behaviour and verifies adopted services against its actual workflow. A design proposal is not a completed adoption. Integration ownership and recovery evidence identify the smallest relevant responsibility at each boundary.
Product and shared infrastructure ownership provides the detailed contract, examples and verification limits.