Artifacts
CTL uses four artifacts to keep journey trust inspectable.
Journey Contract
Section titled “Journey Contract”A UJG JSON-LD document describes the intended journey: states, transitions, exits, authority boundaries, and expected topology.
Verification Binding
Section titled “Verification Binding”Playwright scenarios and tracking manifests bind the intended journey to synthetic verification. These checks verify that the journey still works in CI or deployment pipelines.
Runtime Binding
Section titled “Runtime Binding”OpenTelemetry attributes, spans, and events track real executions. Runtime bindings carry observed facts such as selectors, clicks, URLs, timestamps, and payloads.
Trust View
Section titled “Trust View”Grafana dashboards show pass/fail signals, latency, drift, stale bindings, evidence gaps, and alignment status.
Boundary
Section titled “Boundary”UJG Graph defines intended topology. Runtime evidence belongs in runtime bindings, not in the graph model.