diff --git a/PACKAGING_EXAMPLE.md b/PACKAGING_EXAMPLE.md
index 47b8185..35b7ff3 100644
--- a/PACKAGING_EXAMPLE.md
+++ b/PACKAGING_EXAMPLE.md
@@ -605,9 +605,9 @@ jobs:
 ```
 
 The deploy workflow fires when a `debian/changelog` change reaches `main`. A
-git tag on its own does not deploy. The `sbuild-deploy-pkg` reusable workflow
-builds for the Debian suites in its `distros` input and uploads to the
-Packagecloud `dev` repository.
+git tag on its own does not deploy. The `sbuild-deploy-pkg` reusable workflow builds for the suites in its
+`distros` input (default `["trixie"]`) and uploads to the Packagecloud `dev`
+repository.
 
 ## Step 9: Complete filesystem structure
 
diff --git a/agents/AGENTS.md b/agents/AGENTS.md
index 6869456..d28294e 100644
--- a/agents/AGENTS.md
+++ b/agents/AGENTS.md
@@ -72,7 +72,7 @@ A forked upstream project versions as `<upstream>+wlanpi<N>`, for example `2.3.0
 
 ## CI
 
-CI should keep Debian Trixie packaging jobs, plus compiler builds and tests. Do not add sid, Bookworm, Ubuntu, Arch, or Fedora jobs. WLAN Pi ships Debian packages, so do not maintain an Arch `PKGBUILD` or an RPM spec to track versions.
+Packaging CI on `main` follows [Target Debian suite](https://github.com/WLAN-Pi/developers/blob/main/architecture/PACKAGING.md#target-debian-suite), plus compiler builds and tests.
 
 ## Documentation
 
diff --git a/architecture/PACKAGING.md b/architecture/PACKAGING.md
index 739073d..38a0f20 100644
--- a/architecture/PACKAGING.md
+++ b/architecture/PACKAGING.md
@@ -20,6 +20,15 @@ If you want to create a new package for WLAN Pi:
 2. Review this guide and the Packaging Example
 3. Check [FHS Policy](FHS.md) for filesystem standards
 
+## Target Debian suite
+
+On `main`, WLAN Pi ships `.deb` packages built for Debian Trixie. CI runs
+packaging jobs for that suite. Dockerfiles, build scripts, and workflow inputs
+take the target suite as a parameter, with Trixie as the default (for example
+a `SUITE` build arg, `DEBIAN_RELEASE`, or a workflow `distros` input).
+Adopting the next Debian release updates that default, not the layout of the
+build.
+
 ## Package structure
 
 All WLAN Pi packages must follow this structure: