Specific over sweeping
Use concrete systems, fields, states, and uncertainty instead of transformation slogans.
About Rootspan
The hardest operational work often begins after the alert.
Rootspan is focused on the gap between commerce systems: the reconstruction required to explain which state mattered, how it propagated, and what safe recovery would mean.
Dennis Koshta · Founder & software engineer
Building for evidence, authority, and the messy middle.
Dennis is building Rootspan around a specific observation: commerce teams have powerful tools for each system, but recurring incidents still require a specialist to reconstruct the chain across them. That work is slow because the evidence, transformations, and permission boundaries rarely live in one place.
The company is currently validating that workflow with agencies and fractional operators. The aim is not a generic chatbot or an autonomous operator. It is a supervised system that can make a causal explanation inspectable and a proposed correction safe to review.
Working principles
Trust is built in the case record.
Evidence over assertion
Every conclusion should preserve why it was reached and what could disprove it.
Authority over autonomy
The operator owns approval, client context, and the decision to act.
Verification over closure
A proposed fix is not a resolved incident until the destination is observed again.
Compare notes
What does your team keep reconstructing?
One real workflow is more useful than a broad product pitch.
Email Dennis