The prototype switches the signed-in role. Only the named role sees a decision's trigger.
Boundary Gateway
Where calls are declared, and, where you switch it on, enforced.
Prototype states
- Boundaries
- 3 of the 4 systems in operation
- p99 overhead
- not recorded yet
- Link
- outbound mTLS; no inbound rules
- Buffer
- 0 calls waiting
We can enforce. We always evidence.
Watching only, and watching and flagging, declare every call and cannot block. In the path, the boundary can allow, escalate or block where enforcement is switched on, per boundary. The three modes
Boundaries
| Boundary | Mode | Can block? | Set by | Action |
|---|---|---|---|---|
| nebula-mutual/ | watching and flagging declares every call and flags what it sees outside the approval; cannot block | no | CISO, boundary decision of 2026-09-03 | the CISO decides |
| nebula-mutual/ | watching only beside your own gateway, which enforces; declares every call; cannot block | no | CISO, boundary decision of 2026-08-31 | the CISO decides |
| nebula-mutual/ | watching only beside your own gateway, which enforces; declares every call; cannot block | no | CISO, boundary decision of 2026-09-13 | the CISO decides |
| nebula-mutual/ | no boundary live behavior not observed | no | none | the CISO decides |
Declarations
One declaration per call, chained. When the configuration on live calls no longer matches the one approved at G4, that is a signal.
| Time | System | Call | Declaration hash |
|---|---|---|---|
| 2026-10-16 11:02:41 CT | customer-assistant | claim-update changed configuration; outside the tool authorization record, inc-0006 | d110241clac1… show full hashd110241clac133a2bd0503e4cbf868130e156145ce5cc1f27ca41282593bef8b |
| 2026-10-16 09:15:40 CT | claims-routing | route | d091540rou4f… show full hashd091540rou4f5ab45a80676ae4bf7d92ab276f1b6cb2982afea36d8afaf5ef18 |
| 2026-10-16 09:14:05 CT | customer-assistant | claim-status changed configuration | d091405cla73… show full hashd091405cla73a2ddbc3f10c94e69e5ce07dd12acefec798cd979595b4b7bfbcb |
| 2026-10-16 09:14:02 CT | customer-assistant | policy-lookup changed configuration | d091402pole4… show full hashd091402pole4fcfbb5c8ca6a41e3c25f37c016e913695cc03d1fa27d4759326a |
| 2026-10-15 09:41:07 CT | customer-assistant | policy-lookup changed configuration; the first, chg-0014 | d094107pola8… show full hashd094107pola89acc1283884c9ec4302c2eaf3a06d4682b459fca921db5f9fbcc |
| 2026-10-15 09:38:52 CT | customer-assistant | policy-lookup | d093852pol09… show full hashd093852pol096ba4086475169e498ae6b454215cf9c9f781d3fb86d52336a65b |
The gateway link is down since 2026-10-16 15:02 CT. Calls still run and are written to the gateway's local log; 1,912 are waiting to upload. Nothing is lost. Until the link returns, each run status shows when it was last updated. Check the outbound route from the institution's network to the console.
No boundaries yet
No system sits behind a boundary, so live behavior is not observed for any of them. Add the first boundary beside your own gateway, watching only, or watching and flagging.
Read about the three modes