rename: remaining Bouncer mentions → Dispatcher
Some checks failed
Deploy (Gitea) / deploy (push) Failing after 2s
Some checks failed
Deploy (Gitea) / deploy (push) Failing after 2s
- BOUNCER-PRIVACY-TAGS → *DISPATCHER-PRIVACY-TAGS* - BOUNCER-SHELL-TIMEOUT → *DISPATCHER-SHELL-TIMEOUT* - BOUNCER-SHELL-MAX-OUTPUT → *DISPATCHER-SHELL-MAX-OUTPUT* - bouncer-privacy-tags docstrings → Dispatcher privacy tags - 'Bouncer' in log messages, docstrings, test descriptions - 'Bouncer Security Dispatcher' → 'Security Dispatcher'
This commit is contained in:
@@ -14,7 +14,7 @@ The key architectural choice: **actuators are not privileged**. The same dispatc
|
||||
|
||||
1. Adding a new actuator requires no changes to the core — just register it
|
||||
2. Safety is centralized in the deterministic gates, not scattered across actuator implementations
|
||||
3. Every actuator benefits from the same security checks (the Bouncer, the Policy)
|
||||
3. Every actuator benefits from the same security checks (the Dispatcher, the Policy)
|
||||
|
||||
** Why Dispatch-Action Verifies Again?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user