Model-independent execution planSource references preservedOperations ordered for execution
This is the central architectural boundary: journey intent becomes a stable, model-independent plan before it touches a runtime.
Open-source journey validation
Validate cross-service journeys as users experience them.
JourneyMesh executes mapped user journeys against real applications and service instances. It verifies that expected states, transitions, and outcomes can actually be reached—and records evidence for every step.
Working prototype · Federated Nextcloud file sharing
UJG bindingPlaywright adapterNextcloud driverKeyboard-only profileaxe observer
Services can be healthy while the journey is broken.
Infrastructure checks confirm that services are running. JourneyMesh checks that people can complete the cross-service workflow those services are intended to provide.
Services onlineJourney unverified
How JourneyMesh works
One execution path, composed from independent layers.
JourneyMesh translates a journey description into a common execution plan, then combines it with an automation adapter, application driver, interaction profile, and optional evidence observers.
6 layers — from journey intent to runtime evidenceBuild the execution from interchangeable parts.
Working reference journey
Alice shares a file with Bob across two Nextcloud instances.
Alice uses Nextcloud A to offer a file to Bob as a remote recipient. Bob uses Nextcloud B to receive the share and verify access.
Reference execution
Federated file sharing
Last run passed
2actors
2instances
2profiles
1journey
Connected execution view
Full journey map
Both actors, service instances, phases, steps, states, and transitions in one view.
Runtime evidence
See what happened at every step.
Select any state or transition above to inspect its expectation, runtime result, chosen input modality, resolved application surface, and attached evidence.
State assertionsTransition resultsExpected effectsSelected input modalityScreenshots and tracesAccessibility findingsSource-model references
i
Automated accessibility findings support journey analysis but do not by themselves establish WCAG conformance.
Run the reference journey
Reproduce the complete flow.
Start two Nextcloud instances, provision and seed the scenario, execute the journey, and open the resulting Playwright report.
Terminal
pnpm --filter @openuji/example-nextcloud-filesharing stack:up
pnpm --filter @openuji/example-nextcloud-filesharing stack:provision
pnpm --filter @openuji/example-nextcloud-filesharing stack:seed
pnpm --filter @openuji/example-nextcloud-filesharing e2eJourney-aware delivery
Make the journey part of deployment validation.
JourneyMesh connects mapped intent to real execution, helping maintainers verify that distributed workflows continue to work across versions, configurations, service instances, and interaction profiles.