From 50b81c9ca765acdac03fc9bac37d01e40c7c12e6 Mon Sep 17 00:00:00 2001 From: Albrecht Degering Date: Fri, 7 Aug 2026 11:15:50 +0200 Subject: [PATCH] docs: describe receipt-bound module configuration --- docs/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md b/docs/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md index 217d122..cd45a9a 100644 --- a/docs/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md +++ b/docs/INSTALLATION_AND_DEPLOYMENT_ARCHITECTURE.md @@ -113,6 +113,16 @@ The private installation directory contains: The specification contract is [`installation-spec.schema.json`](installation-spec.schema.json). +The API, workers, scheduler, and Ops read the capability receipt through the +same bounded Core validator. Configuration-package providers receive that typed +receipt in preflight context. Mail uses `mail.smtp` to offer an idempotent SMTP +profile plan and accepts only an existing credential-envelope reference; Files +uses `files.storage` to prove that the deployment-owned local/S3 runtime binding +already matches. Files deliberately blocks drift instead of rewriting process +environment or initiating an implicit object migration. Invalid receipts fail +closed, while a deployment without a mounted receipt continues to run but +cannot apply receipt-bound configuration fragments. + Build the same dependency-free tool as one downloadable artifact: ```sh