Skip to content

Workflow — UX personas and journeys

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Workflow id ux-personas · version 1 · Draft (Draft → InReview → Published → Deprecated, BC-04)
Coordinator persona-extractor · family Planning, Intent Routing & Product Vision
Owner service WorkflowEngineService (BC-38) under Run Control (BC-03)
Starts on BlueprintValidated from BlueprintService (event)
Steps 4 · gated 0 · agents 2
Budget per run 600000 tokens · cap 60.0 USD · 240 min
Descriptor workflow-definition-v1 · schema
Status target

Extracts actors and personas from the Vision Blueprint, maps their journeys, and writes them into a validated UX Blueprint.

Authored design, Draft (D54, D57)

These definitions were authored on 2026-10-14 from the coordinator cards as design assumptions. None is published, evaluated or has run; agents are named by id as design bindings, not as tested integrations.

Definition

flowchart TD
    start(("BlueprintValidated"))
    extract_actors["Extract actors"]
    build_personas["Build personas"]
    map_journeys["Map journeys"]
    validate{"Validate the UX Blueprint"}
    start --> extract_actors
    extract_actors --> build_personas
    build_personas --> map_journeys
    map_journeys --> validate
    done(("WorkflowRunCompleted"))
    validate --> done
    classDef gated stroke:#B45309,stroke-width:2px
Hold "Alt" / "Option" to enable pan & zoom

Shapes: rectangle = agent attempt · double rectangle = tool call · stadium = human decision · diamond = condition evaluated by the engine · parallelogram = fan-out or join · circle = timer · cylinder = sub-workflow · flag = compensation. A thick amber border marks a gated step.

Steps

# Step Kind Runs Gate Class Depends on Retry Timeout Compensation What it does
1 Extract actors
extract-actors		 agent persona-builder none read — exponential ×2 PT30M — Lists the actors and roles the blueprint implies, with their goals and permissions.
2 Build personas
build-personas		 agent persona-builder none read extract-actors exponential ×2 PT30M — Writes one persona per actor with needs, constraints and accessibility considerations.
3 Map journeys
map-journeys		 agent ux-designer none sandbox build-personas exponential ×2 PT30M — Orders the journeys as screen steps with decision points and adverse branches into the UX Blueprint.
4 Validate the UX Blueprint
validate		 condition engine none sandbox map-journeys fixed ×2 PT2M — BlueprintService validates against blueprint-ux-v1 and the UX rules. Condition: blueprint.valid.

Gates and approvals

No approval is required: every step runs in the read or sandbox class; the agents' own tool calls still carry their classes (D21). Compensation steps run in reverse order of the succeeded steps on failure after the last checkpoint; a step without a compensation leaves its sandbox output in place and the run ends Failed with the evidence (ADR-0014, recovery not replay).

Inputs, outputs and events

Direction Name Descriptor
in vision-blueprint blueprint-vision-v1
out ux-blueprint blueprint-ux-v1

Starts on BlueprintValidated; emits BlueprintValidated, ArtifactStored, plus the engine's WorkflowRunStarted, StepReady, StepRunStateChanged and WorkflowRunCompleted / WorkflowRunFailed and Run Control's run and attempt events (ADR-0014).

Decisions and traceability

FR: FR-08 Validated artifacts with lineageFUX: FUX-11 Software Factory journey · FUX-12 Documented viewsADRs: ADR-0014, ADR-0024 · ADR index

Definition authored 2026-10-14 from the coordinator card persona-extractor (D54); Draft until an evaluation gate (ADR-0021) and a review publish it as a BC-04 asset release.