FailCore is intentionally not an agent framework, planner, or sandbox.
It sits strictly at the execution boundary and focuses on two things:
1) blocking unsafe side effects before they happen
2) recording enough execution trace to replay or audit failures later
The goal isn’t to make agents smarter, but to make their failures
observable, reproducible, and boring.
If people are curious, the DESIGN.md goes deeper into why this is done
at the Python runtime level instead of kernel-level isolation (eBPF, VMs, etc.),
and what trade-offs that implies.
One clarification that may help set expectations:
FailCore is intentionally not an agent framework, planner, or sandbox. It sits strictly at the execution boundary and focuses on two things: 1) blocking unsafe side effects before they happen 2) recording enough execution trace to replay or audit failures later
The goal isn’t to make agents smarter, but to make their failures observable, reproducible, and boring.
If people are curious, the DESIGN.md goes deeper into why this is done at the Python runtime level instead of kernel-level isolation (eBPF, VMs, etc.), and what trade-offs that implies.