Trust Across Boundaries
An eight-layer model of trust with strict dependency ordering, spanning human, agent-human and agent-agent interaction, and where the unsolved problem actually sits.
I work on reducing the distance between intent and execution.
A question typed in plain English came back with the analysis, the models and the insights. Across the datasets we deployed it against, the answer arrived in under 53 seconds.
The distance still did not close. Somebody still had to know which question to ask, and what to do once the answer arrived. Compressing the work is not the same as removing the gap between wanting something and having it done.
What I have been working through lately
Earlier I built Penser Analytics and Vipani. The work
If something here overlaps with a problem you are working on, write to me. I am particularly interested in people thinking seriously about autonomy, trust, and what has to be true before a system is allowed to act on your behalf. swarochish.c@gmail.com
How much autonomy can a system earn, and what does it have to show first?
The more consequential the action, the more permissions, observability, determinism and reversibility it needs.
If the interface of the future is not a chat box, what is it?
Chat is good for ambiguity and bad at nearly everything else. The interface should emerge from the state of the work.
What is an agent actually bounded by?
Not the model. What it can sense, remember, understand and verify. Agentic systems are data systems.
What is an application, once it stops being the thing you open?
Applications look increasingly like an interface abstraction rather than the end state.
Why the gap is hard, what an analytics product taught me about compressing it, why 53 seconds was not enough, and what an application becomes responsible for when the person stops operating it step by step.
Research
Working papers. Provisional by definition, versioned, and open to correction.
An eight-layer model of trust with strict dependency ordering, spanning human, agent-human and agent-agent interaction, and where the unsolved problem actually sits.
Multi-agent systems fail at the points where control, context or commitment crosses a boundary. Ten design principles for that layer, and a metric that would show the argument to be wrong.
Felt ease treated as a regulation problem rather than a design problem. Complexity is allocated rather than removed, and the audit question is who absorbed what was taken away.
At ten thousand, nobody is watching, one per cent is a hundred failures, and volume is the thing that finds the edge case.
The shape of business software was set when computation was expensive and integration was painful. Those constraints are weakening. The shape has not moved.
The problem we could not solve was solved by people who were not solving it, three months after we had stopped.