Govern · Organizations & processes
One trace across every host and partner.
Real work crosses machines, teams, and organizations. CHP carries one correlation through all of it, so a process spanning many hosts produces a single, replayable record instead of fragments nobody can reassemble after the fact.
correlation_id: session-abc
Laptop
plan.create
Server
retrieval.query
Edge device
sensor.read
Partner host
claim.decide
one ordered replay
plan.create → retrieval.query → sensor.read → claim.decide
Four hosts, one causal thread, a single replayable timeline.
01
One correlation, many hosts
A correlation ID flows with every invocation. Whether the work touches a laptop, a server, an edge device, or a partner’s host, the events all carry the same causal thread.
02
A gateway stitches the trace
A gateway fans a replay query out to every host in the mesh and merges the evidence into one ordered timeline — across machines you run and, eventually, across organizational boundaries.
03
Replay the whole story
Reconstruct what happened end to end: which host did what, in what order, with which outcomes and denials — not a pile of disconnected logs.
Demonstrated, not yet shipped: correlation and local mesh replay exist today across hosts you operate. Multi-host stitching across organizational boundaries, with retention and access, is what we build with a design partner.
Work that spans hosts or partners?
If you cannot currently reconstruct a process that crosses systems, that is exactly the trace CHP is built to stitch. Bring the workflow and we will design the mesh with you.