Safety and coordination model
Signal Core, Blast Shield, and Race Shield — how Pytxo scopes reads, isolates writes, and orders overlapping work.
Pytxo has three controls for context, isolated changes, and overlapping tasks. Their effect depends on the run configuration and permission profile.
| What it does | Feature | Function |
|---|---|---|
| Smarter context | Signal Core | Send agents code skeletons so they spend tokens on work, not noise |
| Isolated writes | Blast Shield | Keep writes in isolated copies until you Review → Apply |
| No write collisions | Race Shield | Path ownership and waves so overlapping work does not run together |
Signal Core Blast Shield Race Shield
| | |
+----------+----------+----------+---------+
|
Orchestrator
|
AgentsOn Galaxy, human approvals add a queue for risky host commands. That queue is not repository Apply. Apply is Desktop Run Review.
Eligible Orbit and Galaxy runs use isolated copies of your repo (Git worktrees by default). Supernova writes directly to the host. Race Shield orders declared overlapping path claims; it does not govern every external side effect. See Signal Core for how context scaffolding works.
Each layer has its own concept page with configuration options.