Journeys you can keep trusting

Model critical journeys with UJG, verify them continuously with Playwright, track runtime evidence through OpenTelemetry, and keep product, tests, telemetry, and dashboards aligned.

MODEL

UJG Contract

States, transitions, authorities

VERIFY

Playwright Check

CI verifies the journey still works

TRACK

Runtime Evidence

Events and spans through OpenTelemetry

ALIGN

Grafana Trust View

Drift, missing evidence, stale bindings

Example: Alice shares a file -> Bob accepts it -> federation evidence is tracked

Problem

Tests got greener.
Trust did not.

A critical journey can pass in CI and still drift in production. A UI can change while telemetry stays silent. A federated handoff can break between systems while each individual service looks healthy.

CTL treats the user journey as the unit of trust. It compares what was modeled, what was verified, and what was actually observed.

How the loop works

Model, verify, track, align

Tracking collects runtime journey events. Observation interprets those events as trust signals. Alignment closes gaps between intended, verified, and observed behavior.

01 / Model

Model

Define the intended journey with UJG, including states, transitions, exits, and authority boundaries.

02 / Verify

Verify

Run Playwright scenarios to prove the journey still works before release.

03 / Track

Track

Emit runtime journey evidence through OpenTelemetry without pushing runtime facts into the graph.

04 / Align

Align

Use Grafana trust views to find drift, missing evidence, stale bindings, or broken handoffs.

Reference integration

First integration: Nextcloud federation

Nextcloud federation is a good stress test for CTL because the journey crosses users, browsers, servers, and federation boundaries.

  1. Alice shares a file
  2. Nextcloud A emits handoff
  3. Nextcloud B receives share
  4. Bob accepts and opens file
  5. Grafana shows trust status

Artifact model

Four artifacts, one trust question

CTL does not replace UJG, Playwright, OpenTelemetry, or Grafana. It connects them around one question: can this journey still be trusted?

Journey Contract

UJG JSON-LD describing the intended journey.

Verification Binding

Playwright scenarios and tracking manifests verifying the journey still works.

Runtime Binding

OpenTelemetry attributes, spans, and runtime events tracking real executions.

Trust View

Grafana dashboards showing pass/fail, latency, drift, evidence gaps, and alignment status.

Project status

Experimental, docs-first, integration-led

CTL is an experimental OpenUJI project. The first milestone is a public specification site, a tracking manifest draft, and a Nextcloud federation reference integration.

Current maturity
Concept docs Draft
Tracking manifest Draft
OTel attributes Draft
Grafana dashboard Planned
Nextcloud integration Experimental