diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
index 99442a8..2dd6781 100644
--- a/.claude/CLAUDE.md
+++ b/.claude/CLAUDE.md
@@ -60,7 +60,7 @@ Each config's `help:` line shows a concrete example. `-c key:"'value'"` injects
 - `soap-process-bundle` — `Task/RequestTask` driven by a tagged `cleverage.soap.client` (see `oorsprong_countryinfo` client).
 - `flysystem-process-bundle` — `FileFetchTask`, `ListContentTask`, `RemoveFileTask` over Flysystem storages (config in `config/packages/flysystem.yaml`); the demo also uses SFTP.
 - `archive-process-bundle` — `ZipTask` / `UnzipTask`.
-- `cache-process-bundle` — `GetTask` / `SetTask` backed by a tagged `cleverage.cache.adapter` (see `src/Adapter/MemoryAdapter.php`).
+- `cache-process-bundle` — `GetTask` / `SetTask` backed by a tagged `cleverage.cache.adapter` (see the `app.cache.memory` pool in `services.yaml`).
 - `ui-process-bundle` (v3) — the **web UI** at `/process` (no process tasks). Built on EasyAdmin: dashboard, process list/launch/upload-and-run actions, `User` auth, and it **persists every run** — `ProcessExecution`, `LogRecord`, `ProcessSchedule` entities. Its Doctrine migrations ship in the bundle (`vendor/cleverage/ui-process-bundle/src/Migrations/`), which is why `make doctrine/migrations` creates those tables. It also provides the Scheduler integration behind `src/Schedule.php`.
 
 To find how a task behaves or what options it accepts, open its class under the relevant `vendor/cleverage/*/src/Task/` and its matching page under that bundle's `docs/reference/`.
@@ -108,7 +108,7 @@ Tasks pass data along `outputs` edges. `TransformerTask` chains named **transfor
 The `_instanceof` rules auto-tag anything implementing `TaskInterface` (public, non-shared, logged) or `TransformerInterface` (tagged `cleverage.transformer`). To expose external clients/adapters to processes you register a service with the right tag — see existing examples in `services.yaml`:
 - SOAP client → tag `cleverage.soap.client` (referenced by `code` in soap tasks)
 - REST client → tag `cleverage.rest.client`
-- Cache adapter → tag `cleverage.cache.adapter` (see `src/Adapter/MemoryAdapter.php`)
+- Cache adapter → tag `cleverage.cache.adapter` (a Symfony cache pool can be tagged directly, see `app.cache.memory`)
 
 ## Domain glue in `src/`
 
diff --git a/config/services.yaml b/config/services.yaml
index bf4c174..2f0a089 100644
--- a/config/services.yaml
+++ b/config/services.yaml
@@ -126,8 +126,9 @@ services:
         tags:
             - { name: cleverage.rest.client, code: wiremock_admin }
 
-    # For cleverage/cache-process-bundle
-    app.cleverage_cache_process.adapter.memory:
-        class: App\Adapter\MemoryAdapter
+    # For cleverage/cache-process-bundle: a Symfony cache pool tagged directly, wrapped in an adapter by the bundle
+    app.cache.memory:
+        parent: cache.adapter.array
         tags:
+            - { name: cache.pool }
             - { name: cleverage.cache.adapter, code: memory }
diff --git a/src/Adapter/MemoryAdapter.php b/src/Adapter/MemoryAdapter.php
deleted file mode 100644
index 06de9b6..0000000
--- a/src/Adapter/MemoryAdapter.php
+++ /dev/null
@@ -1,42 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-/*
- * This file is part of the CleverAge/ProcessBundleDemo package.
- *
- * Copyright (c) Clever-Age
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-namespace App\Adapter;
-
-use CleverAge\CacheProcessBundle\Adapter\Adapter;
-use Symfony\Component\Cache\Adapter\ArrayAdapter;
-
-class MemoryAdapter extends Adapter
-{
-    public function __construct()
-    {
-        $cache = new ArrayAdapter(
-            // the default lifetime (in seconds) for cache items that do not define their
-            // own lifetime, with a value 0 causing items to be stored indefinitely (i.e.
-            // until the current PHP process finishes)
-            $defaultLifetime = 0,
-
-            // if true, the values saved in the cache are serialized before storing them
-            $storeSerialized = true,
-
-            // the maximum lifetime (in seconds) of the entire cache (after this time, the
-            // entire cache is deleted to avoid stale data from consuming memory)
-            $maxLifetime = 0,
-
-            // the maximum number of items that can be stored in the cache. When the limit
-            // is reached, cache follows the LRU model (least recently used items are deleted)
-            $maxItems = 0
-        );
-        parent::__construct($cache, 'memory');
-    }
-}