22 lines
953 B
Markdown
22 lines
953 B
Markdown
|
# sand-boxer research
|
||
|
|
|
||
|
|
Research informing the sand-boxer meta-framework charter and implementation
|
||
|
|
roadmap. These documents are **inputs to design**, not normative specs — see
|
||
|
|
`INTENT.md` for authority and boundaries.
|
||
|
|
|
||
|
|
## Index
|
||
|
|
|
||
|
|
| Document | Contents |
|
||
|
|
|----------|----------|
|
||
|
|
| [01-agent-sandbox-landscape.md](01-agent-sandbox-landscape.md) | Market survey: isolation technologies, providers, convergence trends |
|
||
|
|
| [02-reference-frameworks.md](02-reference-frameworks.md) | Deep dives: OpenClaw, Hermes, Blitzy, OpenShell, hosted platforms |
|
||
|
|
| [03-meta-framework-synthesis.md](03-meta-framework-synthesis.md) | Design synthesis: API shape, extensions, payments, Coulomb boundaries |
|
||
|
|
|
||
|
|
## How to use
|
||
|
|
|
||
|
|
1. Read `INTENT.md` for the governing charter.
|
||
|
|
2. Use `03-meta-framework-synthesis.md` when designing profiles, extensions, or
|
||
|
|
the unified API.
|
||
|
|
3. Use `01` and `02` when evaluating a backend extension or security posture.
|
||
|
|
|
||
|
|
Last updated: 2026-06-22
|