A patch that cannot auto-apply
Code Worker waits. Deny or Allow once. Evidence after.
runtime · tomorrow · How do human-in-the-loop approvals work?
Consequential actions wait on Deny or Allow. Missing approval is a blocker. Evidence records who decided. Autonomy is adjustable. HITL is not a cloud compliance add-on. It is Control on TARX_OS — on computers you already secure, or on a T-4 / T-70 you get for the department or the rack.
HITL is not a cloud compliance add-on. It is Control on TARX_OS.
TARX works privately on your computer. Connections stay off until you allow them.
Human funnel: Enterprise →

Most HITL products sit in a vendor cloud and wrap identity around a hosted agent. TARX puts Control on the computer the company already locks. The agent can propose. The write waits. The trail is Evidence.
What is gated today: Code Worker runs, patch apply, QA commands, terminal, Vault extraction, external sends or deletes. Always-on auto-approve is how blast radius becomes someone else’s incident.
Enterprise shape: TARX_OS across existing Apple silicon, free software. T-4 beside the team. T-70 in the rack. Policy is the same contract. Data stays on the premise unless you approve a route.
TARX_OS on computers you already own. Supercomputer hardware when the site needs dedicated NVIDIA.
Code Worker waits. Deny or Allow once. Evidence after.
Prompts, files, and weights stay inside unless you approve a route.
What ran, what changed, who approved. Same contract on TARX_OS and Supercomputer.
01
Autonomy is adjustable. Missing approval is a blocker.
02
The agent proposes. The human decides the write.
03
Who decided, what changed, whether it stayed local.
04
T-4 at the desk. T-70 in the rack you already lock.
Code Worker runs, patch apply, QA commands, terminal, Vault extraction, external sends or deletes.
Yes. Air-gapped and government Spaces keep Web lookup off. That is a feature.
No. TARX_OS on computers you own is free software. Get a Supercomputer when you want dedicated NVIDIA on the premise.
It stays on the premise unless you approve a route. Air-gapped capable.
Join the Supercomputer. Or own Private Hardware.
JOIN · TARX_OS

Give TARX superpowers.
TARX works privately on your computer. Connect to the Supercomputer when you want TARX to research the web, use more skills, and take on bigger jobs with deeper models. Supercomputer connection is in beta, and capacity is being qualified.
Join beta →OWN · TARX HARDWARE

Want more power of your own?
Add TARX hardware for faster local work, dedicated capacity, or a private cluster.
Explore Private Hardware →TARX software is free. Size the Black Box for the people using it. Watch the math. Submit once.