fadenstack 0.4.5__tar.gz → 0.5.0__tar.gz

{fadenstack-0.4.5 → fadenstack-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: fadenstack
-Version: 0.4.5
+Version: 0.5.0
 Summary: CLI installer and management tool for the Fadenstack platform
 Project-URL: Homepage, https://fadenstack.com
 Project-URL: Repository, https://github.com/fadenstack/fadenstack
@@ -21,6 +21,7 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: System :: Installation/Setup
 Classifier: Topic :: System :: Systems Administration
 Requires-Python: <4.0,>=3.12
+Requires-Dist: certifi>=2026.10.19
 Requires-Dist: click<9,>=8.1
 Requires-Dist: cryptography>=43
 Requires-Dist: httpx<1,>=0.27
@@ -65,7 +66,7 @@ upgrade the CLI and run `faden upgrade`. See
 - **Auto-tuning** — detects host CPU / RAM and computes optimal worker counts,
   DB pool sizes, and queue channel pools.
 - **Module management** — enable / disable optional services
-  (PII redaction, MCP tools, skills) via Docker Compose profiles.
+  (PII redaction, MCP tools, skills, provenance) via Docker Compose profiles.
 - **GPU detection** — `faden doctor` lists the host's GPUs; `faden deploy`
   adds the NVIDIA GPU overlay when the host has an NVIDIA runtime.
 - **Developer workflow** — clone all repos, install deps, run infra + migrations,
@@ -165,6 +166,12 @@ faden module enable pii skills    # enable modules
 faden module disable mcp          # disable a module
 ```
 
+Provenance marks AI-generated content (EU AI Act Art. 50(2)) and is on by
+default: `faden deploy` and `faden upgrade` switch it on. `faden module disable
+provenance` warns that generated content will no longer be marked, asks first
+(`--yes` for scripts), and records in faden.yaml who switched it off and when;
+upgrades then leave it off until `faden module enable provenance`.
+
 ### Configuration
 
 ```bash
@@ -201,7 +208,7 @@ faden dev init ~/projects/fadenstack --overwrite   # re-clone existing repos
 faden dev up                            # on this machine only (127.0.0.1)
 faden dev up --lan                      # on every interface, for one run
 faden dev up --backend-only
-faden dev up --modules pii,mcp,skills   # also run the optional modules
+faden dev up --modules pii,mcp,skills,provenance   # also run the optional modules
 faden dev up --local-node
 faden dev up --local-node --local-node-host ubuntu@10.0.0.12
 faden dev down
@@ -212,8 +219,11 @@ faden dev doctor
 faden dev doctor --install --yes
 ```
 
-`--modules` runs PII (8003), MCP (8007) and skills (8008) on the host beside
-the backend, and points the gateway and backend at them. Without it, the
+`--modules` runs PII (8003), MCP (8007), skills (8008) and provenance (8009)
+on the host beside the backend, and points the gateway and backend at them.
+Provenance has a repository of its own: it runs from a checkout beside the
+core one (`../fadenstack-provenance`), and without that checkout `dev up`
+says so and starts the rest. Without `--modules`, the
 modules switched on with `faden module enable` run; the others are switched
 off in the gateway and backend. See
 [What happens to a request](../docs/help/pages/administer/requests.md).

{fadenstack-0.4.5 → fadenstack-0.5.0}/README.md

@@ -30,7 +30,7 @@ upgrade the CLI and run `faden upgrade`. See
 - **Auto-tuning** — detects host CPU / RAM and computes optimal worker counts,
   DB pool sizes, and queue channel pools.
 - **Module management** — enable / disable optional services
-  (PII redaction, MCP tools, skills) via Docker Compose profiles.
+  (PII redaction, MCP tools, skills, provenance) via Docker Compose profiles.
 - **GPU detection** — `faden doctor` lists the host's GPUs; `faden deploy`
   adds the NVIDIA GPU overlay when the host has an NVIDIA runtime.
 - **Developer workflow** — clone all repos, install deps, run infra + migrations,
@@ -130,6 +130,12 @@ faden module enable pii skills    # enable modules
 faden module disable mcp          # disable a module
 ```
 
+Provenance marks AI-generated content (EU AI Act Art. 50(2)) and is on by
+default: `faden deploy` and `faden upgrade` switch it on. `faden module disable
+provenance` warns that generated content will no longer be marked, asks first
+(`--yes` for scripts), and records in faden.yaml who switched it off and when;
+upgrades then leave it off until `faden module enable provenance`.
+
 ### Configuration
 
 ```bash
@@ -166,7 +172,7 @@ faden dev init ~/projects/fadenstack --overwrite   # re-clone existing repos
 faden dev up                            # on this machine only (127.0.0.1)
 faden dev up --lan                      # on every interface, for one run
 faden dev up --backend-only
-faden dev up --modules pii,mcp,skills   # also run the optional modules
+faden dev up --modules pii,mcp,skills,provenance   # also run the optional modules
 faden dev up --local-node
 faden dev up --local-node --local-node-host ubuntu@10.0.0.12
 faden dev down
@@ -177,8 +183,11 @@ faden dev doctor
 faden dev doctor --install --yes
 ```
 
-`--modules` runs PII (8003), MCP (8007) and skills (8008) on the host beside
-the backend, and points the gateway and backend at them. Without it, the
+`--modules` runs PII (8003), MCP (8007), skills (8008) and provenance (8009)
+on the host beside the backend, and points the gateway and backend at them.
+Provenance has a repository of its own: it runs from a checkout beside the
+core one (`../fadenstack-provenance`), and without that checkout `dev up`
+says so and starts the rest. Without `--modules`, the
 modules switched on with `faden module enable` run; the others are switched
 off in the gateway and backend. See
 [What happens to a request](../docs/help/pages/administer/requests.md).

{fadenstack-0.4.5 → fadenstack-0.5.0}/hatch_build.py

@@ -22,7 +22,7 @@ except ImportError:  # the tests load this file for bundle_files() alone
 
 #: What an install writes or generates for itself, and what is only for
 #: building from source. None of it belongs in a release.
-_SKIP_DIRS = {"backups", "base", ".empty-hf-cache", "__pycache__"}
+_SKIP_DIRS = {"backups", "base", ".empty-hf-cache", "__pycache__", "secrets"}
 _SKIP_FILES = {
     ".env",
     ".bootstrap-credentials",
@@ -77,7 +77,15 @@ class CustomBuildHook(BuildHookInterface):
     """Add the shared deployment files to the wheel or sdist being built."""
 
     def initialize(self, version: str, build_data: dict) -> None:  # noqa: ARG002
+        catalog = Path(self.root).parent / "pii/faden_pii/pii-catalog.json"
         shared = Path(self.root).parent / "shared"
+        if catalog.is_file():
+            prefix = "src/faden_cli" if self.target_name == "sdist" else "faden_cli"
+            build_data["force_include"][str(catalog)] = f"{prefix}/bundle/pii-catalog.json"
+        elif shared.is_dir():
+            # From a checkout that lacks pii/: the CLI would not start (deploy reads the catalog on import).
+            msg = f"The PII catalog {catalog} is missing; the CLI cannot be built without it."
+            raise FileNotFoundError(msg)
         if not shared.is_dir():
             # Building from an sdist: the files are already in the package.
             return

{fadenstack-0.4.5 → fadenstack-0.5.0}/pyproject.toml

@@ -10,7 +10,7 @@ packages = ["src/faden_cli"]
 
 [project]
 name = "fadenstack"
-version = "0.4.5"
+version = "0.5.0"
 requires-python = ">=3.12,<4.0"
 description = "CLI installer and management tool for the Fadenstack platform"
 authors = [
@@ -46,6 +46,7 @@ dependencies = [
     "cryptography >=43",
     # Release versions in the update check and upgrade (0.5.0rc1 < 0.5.0).
     "packaging >=23",
+    "certifi>=2026.10.19",  # >=2026.10.19: GHSA-6q48-6c7w-9gw2 (emSign roots with compromised intermediate keys)
 ]
 
 [project.urls]

{fadenstack-0.4.5 → fadenstack-0.5.0}/src/faden_cli/__init__.py

@@ -13,4 +13,4 @@ Module activation via Docker Compose profiles.
 All secrets generated securely during init phase.
 """
 
-__version__ = "0.4.5"
+__version__ = "0.5.0"

fadenstack-0.5.0/src/faden_cli/bundle/pii-catalog.json

@@ -0,0 +1,44 @@
+{
+  "version": "local-pii-1",
+  "rules_version": "presidio-local-v2",
+  "default_locale": "europe-west-v1",
+  "locales": {
+    "europe-west-v1": {"name": "Western European multilingual (EN/DE/FR/ES)", "languages": ["en", "de", "fr", "es"], "scripts": ["Latin"], "recommended_model": "patronus-onnx-v1"},
+    "english-v1": {"name": "English", "languages": ["en"], "scripts": ["Latin"], "recommended_model": "patronus-onnx-v1"},
+    "german-v1": {"name": "German", "languages": ["de"], "scripts": ["Latin"], "recommended_model": "patronus-onnx-v1"},
+    "french-v1": {"name": "French", "languages": ["fr"], "scripts": ["Latin"], "recommended_model": "patronus-onnx-v1"},
+    "spanish-v1": {"name": "Spanish", "languages": ["es"], "scripts": ["Latin"], "recommended_model": "patronus-onnx-v1"}
+  },
+  "models": {
+    "patronus-onnx-v1": {
+      "name": "Patronus small FP16 ONNX",
+      "adapter": "gliner-onnx", "adapter_version": 1,
+      "repository": "patronus-studio/gliner_small-v2.5-edge",
+      "revision": "6cfcbd93d7fc6f5e1658f80afa38f73891b91693",
+      "license": "Apache-2.0; backbone MIT",
+      "languages": ["en", "de", "fr", "es"], "scripts": ["Latin"],
+      "execution": ["cpu"], "precision": "float16", "build_target": "prod-cpu",
+      "patterns": ["*.json", "*.model", "onnx/fp16/*", "LICENSE*", "tokenizer*"],
+      "required_files": ["gliner_config.json", "onnx/fp16/model_fp16.onnx"],
+      "labels": {"person": "PERSON", "first_name": "PERSON", "last_name": "PERSON", "full_name": "PERSON", "address": "LOCATION", "city": "LOCATION"},
+      "offsets": "python-codepoints", "max_window_tokens": 256,
+      "max_batch_short": 8, "max_batch_long": 2,
+      "qualification": "EN/DE/FR/ES service evaluation; detection remains incomplete"
+    },
+    "gliner2-multi-v1": {
+      "name": "GLiNER2 multilingual PII",
+      "adapter": "gliner2", "adapter_version": 1,
+      "repository": "fastino/gliner2-privacy-filter-PII-multi",
+      "revision": "1cb4166094dc58fa8d836429f060d6c95f62b495",
+      "license": "Apache-2.0",
+      "languages": ["en", "de", "fr", "es"], "scripts": ["Latin"],
+      "execution": ["cpu", "gpu-shared", "gpu-dedicated"], "precision": "float32", "build_target": "prod-gpu",
+      "patterns": ["*.json", "*.safetensors", "*.model", "*.txt", "encoder_config/*", "LICENSE*"],
+      "required_files": ["config.json", "model.safetensors"],
+      "labels": {"person": "PERSON", "first_name": "PERSON", "last_name": "PERSON", "full_name": "PERSON", "address": "LOCATION", "city": "LOCATION"},
+      "offsets": "python-codepoints", "max_window_tokens": 256,
+      "max_batch_short": 32, "max_batch_long": 8,
+      "qualification": "EN/DE/FR/ES service evaluation; CPU operation is slow; detection remains incomplete"
+    }
+  }
+}

fadenstack-0.5.0/src/faden_cli/bundle/shared/docker-compose.pii-gpu.yaml

@@ -0,0 +1,10 @@
+# Included only when an installed PII execution profile selects CUDA.
+services:
+  faden-pii:
+    deploy:
+      resources:
+        reservations:
+          devices:
+            - driver: nvidia
+              device_ids: ["${FADEN_PII_GPU_ID:-0}"]
+              capabilities: [gpu]

{fadenstack-0.4.5 → fadenstack-0.5.0}/src/faden_cli/bundle/shared/docker-compose.yaml

@@ -85,8 +85,8 @@ services:
     # segment"). pgvector's README asks for more.
     shm_size: 1g
     # Every worker of every service keeps its own pool, and they all share this
-    # server: with PII, MCP and skills an install from this file alone can open
-    # about 130 connections at its peak, past Postgres' default of 100 (see
+    # server: with PII, MCP, skills and provenance an install from this file
+    # alone can open about 145 connections at its peak, past Postgres' default of 100 (see
     # docs/help/pages/operate/requirements.md, The server). A connection is a
     # process of about 6 MB, so 250 at once is about 1.5 GB.
     command: ["postgres", "-c", "max_connections=${POSTGRES_MAX_CONNECTIONS:-250}"]
@@ -356,15 +356,20 @@ services:
     depends_on:
       postgres:
         condition: service_healthy
+    # The keys that open content, as files under /run/secrets (secrets: at the end), not environment.
+    secrets:
+      - source: settings_master_key
+        target: FADEN_GATEWAY_SETTINGS_MASTER_KEY
+      - source: gateway_encryption_key
+        target: FADEN_GATEWAY_ENCRYPTION_KEY
+      - source: gateway_encryption_key_previous
+        target: FADEN_GATEWAY_ENCRYPTION_KEY_PREVIOUS
     environment:
       FADEN_GATEWAY_DB_HOST: postgres
       FADEN_GATEWAY_DB_PORT: 5432
       FADEN_GATEWAY_DB_USER: ${POSTGRES_USER:-postgres}
       FADEN_GATEWAY_DB_PASS: ${POSTGRES_PASSWORD:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
       FADEN_GATEWAY_DB_BASE: faden_gateway
-      # The migration that seals the provider API keys (pr0vk3yg) uses the backend's master key; without it
-      # the migrator used the published development default.
-      FADEN_GATEWAY_SETTINGS_MASTER_KEY: ${FADEN_BACKEND_SETTINGS_MASTER_KEY:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
       # That migration refuses the published development key unless the install keeps it on purpose.
       FADEN_GATEWAY_ALLOW_PUBLISHED_KEYS: ${FADEN_ALLOW_PUBLISHED_KEYS:-false}
 
@@ -393,6 +398,16 @@ services:
         condition: service_completed_successfully
     ports:
       - "127.0.0.1:8001:8000"
+    # The keys that open content, as files under /run/secrets (secrets: at the end), not environment.
+    secrets:
+      - source: settings_master_key
+        target: FADEN_GATEWAY_SETTINGS_MASTER_KEY
+      - source: settings_master_key_previous
+        target: FADEN_GATEWAY_SETTINGS_MASTER_KEY_PREVIOUS
+      - source: gateway_encryption_key_previous
+        target: FADEN_GATEWAY_ENCRYPTION_KEY_PREVIOUS
+      - source: gateway_encryption_key
+        target: FADEN_GATEWAY_ENCRYPTION_KEY
     environment:
       FADEN_GATEWAY_HOST: 0.0.0.0
       FADEN_GATEWAY_PORT: 8000
@@ -406,21 +421,12 @@ services:
       # JWT secret is read from backend DB at startup (faden_gateway.jwt_secret system setting).
       # These two env vars enable that path; no static JWT_SECRET env var is needed.
       FADEN_GATEWAY_BACKEND_DB_BASE: faden_backend
-      FADEN_GATEWAY_SETTINGS_MASTER_KEY: ${FADEN_BACKEND_SETTINGS_MASTER_KEY:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
-      # Set only while `faden secrets rotate` is unfinished: values sealed with the old key still open.
-      FADEN_GATEWAY_SETTINGS_MASTER_KEY_PREVIOUS: ${FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS:-}
-      FADEN_GATEWAY_ENCRYPTION_KEY_PREVIOUS: ${FADEN_GATEWAY_ENCRYPTION_KEY_PREVIOUS:-}
       # An install that has stored data under the published development key may
       # keep it, with a warning at every start, until it is changed (Help:
       # Installing, Secrets in .env). Outside development the service refuses it otherwise.
       FADEN_GATEWAY_ALLOW_PUBLISHED_KEYS: ${FADEN_ALLOW_PUBLISHED_KEYS:-false}
-      # The key chats are encrypted with at rest: messages, titles, memory, a
-      # reply's events in Redis. `faden deploy` writes one into .env; it never
-      # reached the gateway, and every install stored its chats in plain text
-      # (2026-10-02). Empty still stores plain text. Rows from before stay
-      # readable. Without this key the encrypted chats cannot be read: .env
-      # belongs in every backup (`faden backup` takes it; --db-only does not).
-      FADEN_GATEWAY_ENCRYPTION_KEY: ${FADEN_GATEWAY_ENCRYPTION_KEY:-}
+      # Days a chat someone deleted is kept before it is erased (faden deploy asks; Settings > Chat wins).
+      FADEN_GATEWAY_CHAT_DELETED_RETENTION_DAYS: ${FADEN_GATEWAY_CHAT_DELETED_RETENTION_DAYS:-30}
       FADEN_GATEWAY_JWT_ALGORITHM: HS256
       FADEN_GATEWAY_DB_HOST: postgres
       FADEN_GATEWAY_DB_PORT: 5432
@@ -452,6 +458,10 @@ services:
       FADEN_GATEWAY_SKILLS_ENABLED: ${FADEN_GATEWAY_SKILLS_ENABLED:-false}
       FADEN_GATEWAY_SKILLS_SERVICE_URL: ${FADEN_GATEWAY_SKILLS_SERVICE_URL:-http://faden-skills:8000}
       FADEN_GATEWAY_SKILLS_SERVICE_TOKEN: ${FADEN_GATEWAY_SKILLS_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
+      # Provenance: marks AI-generated content (set via .env or COMPOSE_PROFILES)
+      FADEN_GATEWAY_PROVENANCE_ENABLED: ${FADEN_GATEWAY_PROVENANCE_ENABLED:-false}
+      FADEN_GATEWAY_PROVENANCE_SERVICE_URL: ${FADEN_GATEWAY_PROVENANCE_SERVICE_URL:-http://faden-provenance:8000}
+      FADEN_GATEWAY_PROVENANCE_SERVICE_TOKEN: ${FADEN_GATEWAY_PROVENANCE_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
       # Knowledge search runs in the backend. The default, 127.0.0.1:8000, is this container's own port:
       # every search reached the gateway itself and failed with 404.
       FADEN_GATEWAY_RAG_LITE_BACKEND_URL: ${FADEN_GATEWAY_RAG_LITE_BACKEND_URL:-http://faden-backend:8000}
@@ -495,15 +505,16 @@ services:
     depends_on:
       postgres:
         condition: service_healthy
+    # The keys that open content, as files under /run/secrets (secrets: at the end), not environment.
+    secrets:
+      - source: settings_master_key
+        target: FADEN_BACKEND_SETTINGS_MASTER_KEY
     environment:
       FADEN_BACKEND_DB_HOST: postgres
       FADEN_BACKEND_DB_PORT: 5432
       FADEN_BACKEND_DB_USER: ${POSTGRES_USER:-postgres}
       FADEN_BACKEND_DB_PASS: ${POSTGRES_PASSWORD:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
       FADEN_BACKEND_DB_BASE: faden_backend
-      # The migration that seals the remote providers' API keys (pr0vk3ys) seals them with this key.
-      # Without it the migrator used the published development default, and the backend could not open them.
-      FADEN_BACKEND_SETTINGS_MASTER_KEY: ${FADEN_BACKEND_SETTINGS_MASTER_KEY:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
       # That migration refuses the published development key unless the install keeps it on purpose.
       FADEN_BACKEND_ALLOW_PUBLISHED_KEYS: ${FADEN_ALLOW_PUBLISHED_KEYS:-false}
 
@@ -531,6 +542,17 @@ services:
       faden-backend-migrator:
         condition: service_completed_successfully
     # No host port — accessed via nginx reverse proxy
+    # The keys that open content, as files under /run/secrets (secrets: at the end), not environment.
+    secrets:
+      - source: settings_master_key
+        target: FADEN_BACKEND_SETTINGS_MASTER_KEY
+      - source: settings_master_key_previous
+        target: FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS
+      - source: credential_pepper
+        target: FADEN_BACKEND_CREDENTIAL_PEPPER
+      # The text watermark keys: the current one goes to the models it starts (core/provenance_keys.py).
+      - source: provenance_watermark_keys
+        target: FADEN_BACKEND_PROVENANCE_WATERMARK_KEYS
     environment:
       FADEN_BACKEND_HOST: 0.0.0.0
       FADEN_BACKEND_PORT: 8000
@@ -556,12 +578,6 @@ services:
       FADEN_BACKEND_RABBIT_PASS: ${RABBITMQ_BACKEND_PASS:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
       FADEN_BACKEND_RABBIT_VHOST: /
       FADEN_BACKEND_GATEWAY_URL: ${FADEN_BACKEND_GATEWAY_URL:-http://faden-gateway:8000}
-      FADEN_BACKEND_SETTINGS_MASTER_KEY: ${FADEN_BACKEND_SETTINGS_MASTER_KEY:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
-      # Set only while `faden secrets rotate` is unfinished: values sealed with the old key still open.
-      FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS: ${FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS:-}
-      # What the machines' credential hashes are keyed with. Once the master key itself; a rotation
-      # changes the master key and must not change this, or every machine would have to enroll again.
-      FADEN_BACKEND_CREDENTIAL_PEPPER: ${FADEN_BACKEND_CREDENTIAL_PEPPER:?set it in .env, as faden upgrade does (it keeps the machines' credentials valid; Help, Rotating the keys)}
       # An install that has stored data under the published development key may
       # keep it, with a warning at every start, until it is changed (Help:
       # Installing, Secrets in .env). Outside development the service refuses it otherwise.
@@ -597,6 +613,9 @@ services:
       FADEN_BACKEND_DOCLING_SERVICE_URL: ${FADEN_BACKEND_DOCLING_SERVICE_URL:-http://faden-docling:8000}
       FADEN_BACKEND_SKILLS_SERVICE_URL: ${FADEN_BACKEND_SKILLS_SERVICE_URL:-http://faden-skills:8000}
       FADEN_BACKEND_SKILLS_SERVICE_TOKEN: ${FADEN_BACKEND_SKILLS_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
+      FADEN_BACKEND_PROVENANCE_ENABLED: ${FADEN_BACKEND_PROVENANCE_ENABLED:-false}
+      FADEN_BACKEND_PROVENANCE_SERVICE_URL: ${FADEN_BACKEND_PROVENANCE_SERVICE_URL:-http://faden-provenance:8000}
+      FADEN_BACKEND_PROVENANCE_SERVICE_TOKEN: ${FADEN_BACKEND_PROVENANCE_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
       # Scalability tuning (set via faden tune)
       FADEN_BACKEND_WORKERS_COUNT: ${FADEN_BACKEND_WORKERS_COUNT:-4}
       FADEN_BACKEND_DB_POOL_SIZE: ${FADEN_BACKEND_DB_POOL_SIZE:-5}
@@ -624,6 +643,9 @@ services:
       # directory plus /knowledge on the host; empty, the named volume. The CLI copies the volume's files
       # into the folder before the container is created.
       - ${FADEN_DATA_DIR:-faden_rag_lite}${FADEN_DATA_DIR:+/knowledge}:/data/faden/rag-lite
+      # The audit trail's file copy (services/audit/chain.py): one line per event, never deleted, in every
+      # backup. Someone who edits the audit table cannot edit this from the database.
+      - faden_audit:/data/faden/audit
       # Runtime monitoring — shared with the prometheus + grafana
       # services (see their mounts). The backend generates
       # prometheus/targets.json and dashboards/*.json here; grafana
@@ -666,6 +688,17 @@ services:
         condition: service_healthy
       faden-backend-migrator:
         condition: service_completed_successfully
+    # The keys that open content, as files under /run/secrets (secrets: at the end), not environment.
+    secrets:
+      - source: settings_master_key
+        target: FADEN_BACKEND_SETTINGS_MASTER_KEY
+      - source: settings_master_key_previous
+        target: FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS
+      - source: credential_pepper
+        target: FADEN_BACKEND_CREDENTIAL_PEPPER
+      # The text watermark keys: the current one goes to the models it starts (core/provenance_keys.py).
+      - source: provenance_watermark_keys
+        target: FADEN_BACKEND_PROVENANCE_WATERMARK_KEYS
     environment:
       FADEN_BACKEND_ENVIRONMENT: ${FADEN_BACKEND_ENVIRONMENT:-production}
       FADEN_BACKEND_DB_HOST: postgres
@@ -682,12 +715,6 @@ services:
       FADEN_BACKEND_RABBIT_PASS: ${RABBITMQ_BACKEND_PASS:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
       FADEN_BACKEND_RABBIT_VHOST: /
       FADEN_BACKEND_GATEWAY_URL: ${FADEN_BACKEND_GATEWAY_URL:-http://faden-gateway:8000}
-      FADEN_BACKEND_SETTINGS_MASTER_KEY: ${FADEN_BACKEND_SETTINGS_MASTER_KEY:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
-      # Set only while `faden secrets rotate` is unfinished: values sealed with the old key still open.
-      FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS: ${FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS:-}
-      # What the machines' credential hashes are keyed with. Once the master key itself; a rotation
-      # changes the master key and must not change this, or every machine would have to enroll again.
-      FADEN_BACKEND_CREDENTIAL_PEPPER: ${FADEN_BACKEND_CREDENTIAL_PEPPER:?set it in .env, as faden upgrade does (it keeps the machines' credentials valid; Help, Rotating the keys)}
       FADEN_BACKEND_LLM_GRAPH_DB_HOST: postgres
       FADEN_BACKEND_LLM_GRAPH_DB_USER: ${POSTGRES_USER:-postgres}
       FADEN_BACKEND_LLM_GRAPH_DB_PASS: ${POSTGRES_PASSWORD:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
@@ -707,6 +734,9 @@ services:
       FADEN_BACKEND_DOCLING_SERVICE_URL: ${FADEN_BACKEND_DOCLING_SERVICE_URL:-http://faden-docling:8000}
       FADEN_BACKEND_SKILLS_SERVICE_URL: ${FADEN_BACKEND_SKILLS_SERVICE_URL:-http://faden-skills:8000}
       FADEN_BACKEND_SKILLS_SERVICE_TOKEN: ${FADEN_BACKEND_SKILLS_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
+      FADEN_BACKEND_PROVENANCE_ENABLED: ${FADEN_BACKEND_PROVENANCE_ENABLED:-false}
+      FADEN_BACKEND_PROVENANCE_SERVICE_URL: ${FADEN_BACKEND_PROVENANCE_SERVICE_URL:-http://faden-provenance:8000}
+      FADEN_BACKEND_PROVENANCE_SERVICE_TOKEN: ${FADEN_BACKEND_PROVENANCE_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
       # Scalability tuning (set via faden tune)
       FADEN_BACKEND_DB_POOL_SIZE: ${FADEN_BACKEND_DB_POOL_SIZE:-5}
       FADEN_BACKEND_DB_MAX_OVERFLOW: ${FADEN_BACKEND_DB_MAX_OVERFLOW:-5}
@@ -721,6 +751,7 @@ services:
       - /var/run/docker.sock:/var/run/docker.sock:ro
       - faden_models:/srv/faden/models
       - ${FADEN_DATA_DIR:-faden_rag_lite}${FADEN_DATA_DIR:+/knowledge}:/data/faden/rag-lite
+      - faden_audit:/data/faden/audit
 
   # -----------------------------
   # frontend (React admin console)
@@ -752,11 +783,12 @@ services:
   # =====================================================================
   faden-pii:
     profiles: ["pii"]
-    image: ${REGISTRY:-ghcr.io/fadenstack}/pii:${VERSION:-latest}
+    mem_limit: ${FADEN_PII_MEMORY_LIMIT:-4g}
+    image: ${FADEN_PII_IMAGE:-${REGISTRY:-ghcr.io/fadenstack}/pii:${VERSION:-latest}}
     build:
       context: ../pii
       dockerfile: Dockerfile
-      target: prod
+      target: ${FADEN_PII_BUILD_TARGET:-prod}
       args:
         BASE_IMAGE: ${REGISTRY:-ghcr.io/fadenstack}/base:${VERSION:-latest}
     container_name: faden-pii
@@ -781,17 +813,53 @@ services:
       FADEN_PII_RABBIT_PASS: ${RABBITMQ_PII_PASS:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
       FADEN_PII_RABBIT_VHOST: /
       # Scalability tuning (set via faden tune)
-      FADEN_PII_WORKERS_COUNT: ${FADEN_PII_WORKERS_COUNT:-4}
+      FADEN_PII_WORKERS_COUNT: ${FADEN_PII_WORKERS_COUNT:-1}
       FADEN_PII_DB_POOL_SIZE: ${FADEN_PII_DB_POOL_SIZE:-5}
       FADEN_PII_DB_MAX_OVERFLOW: ${FADEN_PII_DB_MAX_OVERFLOW:-5}
+      FADEN_PII_BACKEND: ${FADEN_PII_BACKEND:-presidio}
+      FADEN_PII_MODEL_ID: ${FADEN_PII_MODEL_ID:-}
+      FADEN_PII_MODEL_REVISION: ${FADEN_PII_MODEL_REVISION:-}
+      FADEN_PII_LOCALE_PACK: ${FADEN_PII_LOCALE_PACK:-}
+      FADEN_PII_CATALOG_VERSION: ${FADEN_PII_CATALOG_VERSION:-}
+      FADEN_PII_RULES_VERSION: ${FADEN_PII_RULES_VERSION:-}
+      FADEN_PII_ENTITY_PROFILE: ${FADEN_PII_ENTITY_PROFILE:-standard}
+      FADEN_PII_EXECUTION_PROFILE: ${FADEN_PII_EXECUTION_PROFILE:-cpu}
+      FADEN_PII_DEVICE: ${FADEN_PII_DEVICE:-cuda:0}
+      FADEN_PII_PRECISION: ${FADEN_PII_PRECISION:-float32}
+      FADEN_PII_MODEL_PATH: ${FADEN_PII_MODEL_PATH:-/models}
+      FADEN_PII_MANIFEST_PATH: ${FADEN_PII_MANIFEST_PATH:-/models/manifest.json}
+      FADEN_PII_CALIBRATION_PATH: ${FADEN_PII_CALIBRATION_PATH:-}
+      FADEN_PII_CPU_THREADS: ${FADEN_PII_CPU_THREADS:-}
+      FADEN_PII_GPU_MEMORY_MIB: ${FADEN_PII_GPU_MEMORY_MIB:-4096}
+      FADEN_PII_DEFAULT_LANGUAGE: ${FADEN_PII_DEFAULT_LANGUAGE:-en}
+      FADEN_PII_SCORE_THRESHOLD: ${FADEN_PII_SCORE_THRESHOLD:-0.35}
+      FADEN_PII_PENDING_REQUESTS: ${FADEN_PII_PENDING_REQUESTS:-64}
+      FADEN_PII_PENDING_WINDOWS: ${FADEN_PII_PENDING_WINDOWS:-512}
+      FADEN_PII_PENDING_TOKENS: ${FADEN_PII_PENDING_TOKENS:-131072}
+      FADEN_PII_PENDING_BYTES: ${FADEN_PII_PENDING_BYTES:-33554432}
+      FADEN_PII_WINDOW_TOKENS: ${FADEN_PII_WINDOW_TOKENS:-256}
+      FADEN_PII_WINDOW_OVERLAP: ${FADEN_PII_WINDOW_OVERLAP:-24}
+      # Empty means the selected image/backend defaults (CPU 8/2, GPU 32/8).
+      FADEN_PII_BATCH_SHORT: ${FADEN_PII_BATCH_SHORT:-}
+      FADEN_PII_BATCH_LONG: ${FADEN_PII_BATCH_LONG:-}
+      FADEN_PII_WORK_TIMEOUT_SECONDS: ${FADEN_PII_WORK_TIMEOUT_SECONDS:-8}
+      FADEN_PII_MAX_RECOVERIES: ${FADEN_PII_MAX_RECOVERIES:-1}
+      FADEN_PII_RECOVERY_DELAY_SECONDS: ${FADEN_PII_RECOVERY_DELAY_SECONDS:-1}
+      FADEN_PII_CACHE_ENTRIES: ${FADEN_PII_CACHE_ENTRIES:-20000}
+      FADEN_PII_CACHE_BYTES: ${FADEN_PII_CACHE_BYTES:-134217728}
+      FADEN_PII_LOCK_DIR: /run/pii-locks
+    volumes:
+      - ${FADEN_PII_MODEL_DIR:-faden_pii_models}:/models:ro
+      - faden_pii_locks:/run/pii-locks
     healthcheck:
-      test: ["CMD", "python", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/api/health', timeout=3).read()"]
+      test: ["CMD", "python", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/api/ready', timeout=3).read()"]
       interval: 5s
       timeout: 5s
       retries: 20
+      start_period: 120s
 
   faden-pii-worker:
-    profiles: ["pii"]
+    profiles: ["pii-tasks"]
     image: ${REGISTRY:-ghcr.io/fadenstack}/pii:${VERSION:-latest}
     container_name: faden-pii-worker
     logging: *faden-logging
@@ -856,6 +924,12 @@ services:
         condition: service_healthy
       faden-mcp-migrator:
         condition: service_completed_successfully
+    # The keys that open content, as files under /run/secrets (secrets: at the end), not environment.
+    secrets:
+      - source: mcp_encryption_key
+        target: FADEN_MCP_ENCRYPTION_KEY
+      - source: mcp_encryption_key_previous
+        target: FADEN_MCP_ENCRYPTION_KEY_PREVIOUS
     environment:
       FADEN_MCP_HOST: 0.0.0.0
       FADEN_MCP_PORT: 8000
@@ -873,8 +947,6 @@ services:
       FADEN_MCP_PII_SERVICE_URL: ${FADEN_MCP_PII_SERVICE_URL:-http://faden-pii:8000}
       FADEN_MCP_PII_SERVICE_TOKEN: ${FADEN_MCP_PII_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
       FADEN_MCP_SERVICE_TOKEN: ${FADEN_MCP_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
-      FADEN_MCP_ENCRYPTION_KEY: ${FADEN_MCP_ENCRYPTION_KEY:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
-      FADEN_MCP_ENCRYPTION_KEY_PREVIOUS: ${FADEN_MCP_ENCRYPTION_KEY_PREVIOUS:-}
       # An install that has stored data under the published development key may
       # keep it, with a warning at every start, until it is changed (Help:
       # Installing, Secrets in .env). Outside development the service refuses it otherwise.
@@ -952,6 +1024,73 @@ services:
       timeout: 5s
       retries: 20
 
+  # =====================================================================
+  # Provenance (profile: provenance)
+  #
+  # Marks AI-generated content and checks marks (EU AI Act Art. 50(2)).
+  # Published as an image only; switched on by default by faden deploy
+  # and faden upgrade. The migrator makes the database faden_provenance
+  # when an install created before the module has none.
+  # =====================================================================
+  faden-provenance-migrator:
+    profiles: ["provenance"]
+    image: ${REGISTRY:-ghcr.io/fadenstack}/provenance:${VERSION:-latest}
+    container_name: faden-provenance-migrator
+    logging: *faden-logging
+    restart: on-failure:5
+    command: ["sh", "-c", "sleep 5 && python -m faden_provenance.db.ensure && alembic upgrade head"]
+    depends_on:
+      postgres:
+        condition: service_healthy
+    environment:
+      FADEN_PROVENANCE_DB_HOST: postgres
+      FADEN_PROVENANCE_DB_PORT: 5432
+      FADEN_PROVENANCE_DB_USER: ${POSTGRES_USER:-postgres}
+      FADEN_PROVENANCE_DB_PASS: ${POSTGRES_PASSWORD:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
+      FADEN_PROVENANCE_DB_BASE: faden_provenance
+
+  faden-provenance:
+    profiles: ["provenance"]
+    image: ${REGISTRY:-ghcr.io/fadenstack}/provenance:${VERSION:-latest}
+    container_name: faden-provenance
+    logging: *faden-logging
+    restart: unless-stopped
+    depends_on:
+      postgres:
+        condition: service_healthy
+      faden-provenance-migrator:
+        condition: service_completed_successfully
+    # Its signer, hash keys and watermark keys, as files under /run/secrets (secrets: at the end), not environment.
+    secrets:
+      - source: provenance_signing_key
+        target: FADEN_PROVENANCE_SIGNING_KEY
+      - source: provenance_signing_certs
+        target: FADEN_PROVENANCE_SIGNING_CERTS
+      - source: provenance_hash_keys
+        target: FADEN_PROVENANCE_HASH_KEYS
+      - source: provenance_watermark_keys
+        target: FADEN_PROVENANCE_WATERMARK_KEYS
+    # The server's model store, read only: the tokenizers a text's watermark is checked with.
+    volumes:
+      - faden_models:/srv/faden/models:ro
+    environment:
+      FADEN_PROVENANCE_HOST: 0.0.0.0
+      FADEN_PROVENANCE_PORT: 8000
+      FADEN_PROVENANCE_RELOAD: "false"
+      FADEN_PROVENANCE_ENVIRONMENT: ${FADEN_PROVENANCE_ENVIRONMENT:-production}
+      FADEN_PROVENANCE_DB_HOST: postgres
+      FADEN_PROVENANCE_DB_PORT: 5432
+      FADEN_PROVENANCE_DB_USER: ${POSTGRES_USER:-postgres}
+      FADEN_PROVENANCE_DB_PASS: ${POSTGRES_PASSWORD:?set it in .env; an install that ran without it keeps its data only with the old default value (Help, Installing, Secrets in .env)}
+      FADEN_PROVENANCE_DB_BASE: faden_provenance
+      FADEN_PROVENANCE_SERVICE_TOKEN: ${FADEN_PROVENANCE_SERVICE_TOKEN:?set it in .env, as faden deploy and faden upgrade do (Help, Installing, Secrets in .env)}
+      FADEN_PROVENANCE_PLUGINS: ${FADEN_PROVENANCE_PLUGINS:-}
+    healthcheck:
+      test: ["CMD", "python", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/api/health', timeout=3).read()"]
+      interval: 5s
+      timeout: 5s
+      retries: 20
+
   # -----------------------------
   # Observability: Loki + Grafana + Alloy + Prometheus
   # -----------------------------
@@ -1081,3 +1220,49 @@ volumes:
   faden_models:
   faden_rag_lite:
   faden_chat_files:
+  faden_audit:
+  faden_pii_models:
+  faden_pii_locks:
+
+# The keys that open content: the chats, the sealed settings and provider keys, the machines' credentials, the
+# MCP servers' credentials; and the provenance engine's signer and hash keys. They are kept and changed in .env
+# as before; `faden` writes them into secrets/ (readable by the install's user only) before every compose
+# command it runs, and compose mounts them read-only under /run/secrets, where the services read them. They
+# are in no container's environment, so neither `docker inspect` nor the console's container pages show them.
+# Run compose through `faden`, or `faden up` once after changing one of them in .env by hand.
+secrets:
+  gateway_encryption_key:
+    # The key chats are encrypted with at rest: messages, titles, memory, attachment names and files, a reply's
+    # events in Redis. Required: the gateway refuses to start without it, and without it the chats cannot be
+    # read. .env belongs in every backup (`faden backup` takes it; --db-only does not).
+    file: ./secrets/FADEN_GATEWAY_ENCRYPTION_KEY
+  gateway_encryption_key_previous:
+    # Only while `faden secrets rotate` is unfinished: chats sealed with the old key still open. Empty otherwise.
+    file: ./secrets/FADEN_GATEWAY_ENCRYPTION_KEY_PREVIOUS
+  settings_master_key:
+    # Seals secret settings and the remote providers' API keys (the migrations pr0vk3ys and pr0vk3yg use it too).
+    file: ./secrets/FADEN_BACKEND_SETTINGS_MASTER_KEY
+  settings_master_key_previous:
+    # Only while `faden secrets rotate` is unfinished: values sealed with the old key still open.
+    file: ./secrets/FADEN_BACKEND_SETTINGS_MASTER_KEY_PREVIOUS
+  credential_pepper:
+    # What the machines' credential hashes are keyed with. Once the master key itself; a rotation changes the
+    # master key and must not change this, or every machine would have to enroll again.
+    file: ./secrets/FADEN_BACKEND_CREDENTIAL_PEPPER
+  mcp_encryption_key:
+    file: ./secrets/FADEN_MCP_ENCRYPTION_KEY
+  mcp_encryption_key_previous:
+    file: ./secrets/FADEN_MCP_ENCRYPTION_KEY_PREVIOUS
+  provenance_signing_key:
+    # The key C2PA manifests on generated pictures are signed with (PKCS#8 DER, base64); new with each certificate.
+    file: ./secrets/FADEN_PROVENANCE_SIGNING_KEY
+  provenance_signing_certs:
+    # Its certificate from the install's authority, then the authority (PEM, base64); renewed 30 days ahead.
+    file: ./secrets/FADEN_PROVENANCE_SIGNING_CERTS
+  provenance_hash_keys:
+    # The keys of the provenance records' hashes: every version ever used, the highest current (`1:...,2:...`).
+    file: ./secrets/FADEN_PROVENANCE_HASH_KEYS
+  provenance_watermark_keys:
+    # The keys of the text watermark the model runtimes put into answers (vLLM's --watermark-config): every
+    # version ever used, the highest current (`1:<whole number>,...`). Empty while the module is off.
+    file: ./secrets/FADEN_PROVENANCE_WATERMARK_KEYS

{fadenstack-0.4.5 → fadenstack-0.5.0}/src/faden_cli/bundle/shared/initdb/01-init.sql

@@ -23,6 +23,8 @@ CREATE DATABASE faden_gateway;
 CREATE DATABASE faden_mcp;
 -- DB for Skills Registry
 CREATE DATABASE faden_skills;
+-- DB for Provenance (its migrator also makes it on installs created before)
+CREATE DATABASE faden_provenance;
 
 -- Optional: enable pgvector in rag DB
 \connect rag