What is CTL?
Critical user journeys should not be trusted only because tests passed once.
Continuous Trust Loop keeps the loop alive: model the journey, verify it in CI, track it at runtime, and keep product, tests, telemetry, and dashboards aligned.
The trust loop
Section titled “The trust loop”CTL is built around four connected activities:
- Model the intended journey with UJG.
- Verify the journey continuously with Playwright.
- Track runtime journey events through OpenTelemetry.
- Align model, tests, telemetry, and dashboards when the evidence stops agreeing.
What CTL is not
Section titled “What CTL is not”CTL does not replace UJG, Playwright, OpenTelemetry, or Grafana. It connects them around a single operational question: can this journey still be trusted?
It is also not a claim that a journey is permanently correct. CTL treats trust as something that must be refreshed with evidence.
Tracking collects runtime journey events. Observation interprets those events as trust signals. Alignment closes the gap between intended, verified, and observed behavior.
Current status
Section titled “Current status”CTL is experimental. The first milestone is a public specification site, a tracking manifest draft, and a Nextcloud federation reference integration.