cache: share published catalogs across instances

This commit is contained in:
a.tolmachev
2026-05-04 05:22:27 +00:00
parent 284ba76b6b
commit 50b1e5ea13
6 changed files with 164 additions and 7 deletions
+3 -1
View File
@@ -62,9 +62,11 @@ Progress:
- `ExecutionConfig.response_cache` is now part of the public operation model, and `admin-api` validates the safe Community baseline: only explicit `REST GET` operations without `auth_profile_ref`
- cache boundary and namespace rules are now documented for `platform / coordination cache` versus `response cache`
- runtime executor now performs actual response cache reads/writes for eligible `REST GET` operations with keys isolated by `workspace + agent + operation + request fingerprint`
- mcp-server published tool catalog now uses shared coordination snapshots across instances, while preserving the same `workspace + agent` isolation model
- pending:
- preserve the same isolation model while extending response cache beyond the first `REST GET` hot path
- wire replay guard / coordination state into additional concrete runtime and transport paths
- wire replay guard into the first real token or nonce flow once commercial machine-token issuance stops being a `Community` stub
- wire coordination state into additional runtime or transport paths beyond the shared published catalog snapshot
## Planned