CHORE: Prepare for Bouncer Matrix implementation
This commit is contained in:
@@ -9,6 +9,13 @@
|
||||
* Overview
|
||||
The *System 2 Bouncer* is the authorization gate for high-risk actions. It serializes intercepted actions into Org nodes ("Flight Plans") and re-injects them once manually approved by the Sovereign.
|
||||
|
||||
** Deep Reasoning: Beyond Permission
|
||||
While the *Formal Prover* ensures an action is "legal" (e.g., "Yes, you are allowed to send a Matrix message"), the *Bouncer* ensures the action is "safe" by inspecting the payload content via **Deep Packet Inspection (DPI)**.
|
||||
|
||||
1. **Secret Exposure Gate:** The Bouncer automatically scans all outgoing `:text` payloads for strings matching your API keys or sensitive IDs stored in the `Credentials Vault`.
|
||||
2. **Network Exfiltration Gate:** It monitors for unauthorized IP addresses or domains in shell commands, preventing the agent from "phoning home" to a malicious server.
|
||||
3. **The Final Filter:** The Bouncer sits at the very end of the symbolic pipeline. It is the last gate before an action touches the physical hardware.
|
||||
|
||||
* Implementation
|
||||
|
||||
** Approval Processing
|
||||
|
||||
Reference in New Issue
Block a user