docs: describe receipt-bound module configuration

2026-08-07 11:15:50 +02:00
parent 612a44bc8e
commit 50b81c9ca7
1 changed files with 10 additions and 0 deletions
@@ -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