Harness design
4 articles
Payments for machinesSpending limits and revocation for agents
When software spends money, someone has to answer for it. That takes a responsible party behind every agent, limits the agent cannot raise itself, and a revocation that stops payment on every rail at once. How each of those works on Tenzro, and why each has to be enforced outside the agent.
5 min read
Edge AIAgentic Harnesses on Small Devices: Orchestrating From the Edge
Most of an agent's work is orchestration, not large-model inference. Why the harness belongs on small hardware near the data, what runs on a Tenzro edge node today, and what edge harness hosting will add once it ships.
5 min read
SafetyDesigning Safe Harnesses: Scopes, Limits, Expiry and Revocation
Prompt injection will sometimes succeed, so an agent's safety has to live outside the model. How Tenzro bounds every delegated agent with consensus-enforced scopes, spending limits, expiry, step-up approval and revocation, with an accountable root behind each one.
5 min read
Machine economyMachines That Pay Machines: Accounting for Autonomous AI Work
When agents buy inference, data and compute from other machines, the hard parts are accounting, receipts, limits and settlement, not the payment rail. How Tenzro records each payment once, binds it to what was asked and delivered, and settles in the rails people already use.
5 min read