You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document outlines the recommended [proven](https://github.com/hyperpolymath/proven) modules for Project Wharf.
4
+
5
+
## Recommended Modules
6
+
7
+
| Module | Purpose | Priority |
8
+
|--------|---------|----------|
9
+
| SafeCapability | Capability-based security with delegation proofs for the sovereign web hypervisor's permission model | High |
10
+
| SafeTransaction | ACID transactions with isolation proofs for stateful web operations | High |
11
+
| SafePath | Filesystem access that prevents path traversal attacks in sandboxed environments | High |
12
+
| SafeSQL | SQL injection prevention for database operations | Medium |
13
+
| SafePolicy | Zone-based policy enforcement for hypervisor security boundaries | Medium |
14
+
| SafeZone | (Custom) Security zone management with boundary enforcement | Medium |
15
+
16
+
## Integration Notes
17
+
18
+
Project Wharf as a sovereign web hypervisor requires strong security guarantees:
19
+
20
+
-**SafeCapability** is essential for managing permissions between isolated web contexts. The hypervisor must ensure capabilities cannot be escalated or leaked between zones.
21
+
22
+
-**SafeTransaction** ensures that web operations maintain ACID properties, critical for stateful interactions that span multiple components.
23
+
24
+
-**SafePath** prevents sandboxed applications from escaping their designated directories through path traversal attacks.
25
+
26
+
-**SafeSQL** should wrap any database interactions to guarantee injection-proof queries.
27
+
28
+
-**SafePolicy** enables AST-level policy enforcement, ensuring zone boundaries are respected at the code level.
29
+
30
+
The combination of these modules provides defense-in-depth for the hypervisor's security model.
0 commit comments