How it works
A case record for the work between alert and recovery.
Rootspan’s product direction is a guided, supervised investigation: preserve the competing states, explain the causal chain, and keep authority with the operator.
The loop
Five verbs, one accountable record.
Each step adds evidence or a decision without rewriting what came before.
- 01Observe
Observe permitted state
Read scoped states from the systems already involved—without taking control away from them.
- 02Assemble
Assemble evidence
Preserve each source, timestamp, authority label, and disagreement instead of flattening them.
- 03Trace
Trace the causal chain
Connect the destination symptom to the transformations and overrides that could have produced it.
- 04Approve
Propose and approve
Present the smallest exact diff, evidence basis, blast radius, and rollback for human review.
- 05Verify
Verify and learn
Re-observe the affected states, record the receipt, and retain the case for recurrence analysis.
The case record
One place to inspect the chain—not one flattened truth field.
Catalog, app, storefront, feed, and destination observations remain separate. That makes a disagreement inspectable: who reported it, when it was observed, which authority label applies, and what transformation sits between the states.
- Source and observation time
- Authority and transformation labels
- Evidence-quality gaps and alternate hypotheses
- Proposed diff, approval, rollback, and verification receipt
Permitted state
Evidence timeline
Proposed correction
Structured offer priceIllustrative investigation using synthetic data. The commerce catalog reports $99 at 09:02, the promotion app reports $79 at 09:04, structured data reports $99 at 09:07, and the feed override reports $79 at 09:09. The selected hypothesis is a stale storefront offer. The proposed correction changes the destination-visible structured offer from $99 to $79 for 14 synthetic variants, remains subject to human approval, retains a rollback, and is verified by re-observing the storefront and destination.
Authority boundary
A proposal is not an action.
The operating model separates investigation, proposal, approval, execution, and verification so an explanation cannot quietly become a write.
Verification and learning
Recovery is another observation—not a victory banner.
A case closes only when the defined destination and source states are observed again. The retained record can then reveal whether the same mechanism returns across products, merchants, or tools.
Bring one recurring case