Open a file. Properly.

Sarah clicks “+ New Enquiry”. A bare work item of type alt-fo-shared-process-enquiry is created in Draft. No form — just a title input. This validates the lifecycle shape before the forms arrive.

An ODS-backed triage form opens (alt-fo-shared-form-enquiry-triage). Caller name, phone, instruction types from the option set, notes. On save: ODS Person upserts, links as alt-fo-shared-role-enquiry-contact, intake source stamped phone, enquiry created in Draft.

External intake arrives via POST /api/v1/intake/enquiry with an idempotency key. On phase-entry to Draft, alt-fo-shared-vw-enquiry-ods-upsert runs: matches by email → phone → creates, links the Person as enquiry-contact, stamps intake source. If required fields are missing, spawns a review task rather than erroring — the caller is never lost.

Sarah types the classification and conflict note into the enquiry description, clicks Submit to Instructions. Validates the phase shape (Draft → Triage → Instructions → Completed) with an off-ramp to Not Proceeding.

Two tasks appear: Classification (practice area + urgency from the option set) and Conflict Check (manual search, outcome recorded on the task). The Client Picker widget links an existing or new Client via a client-related relationship. The Submit to Instructions button unlocks only when both triage tasks complete AND the client is linked — enforced by ChildWorkItemsCompleted and alt-fo-shared-dqr-enquiry-client-linked.

alt-fo-shared-vw-enquiry-triage fires on Triage entry, auto-creating both tasks (parallel fan-out). Sarah still decides the outcomes — the task completion IS the user judgement. A conflict-outcome gateway detects whether partner review is needed and spawns it automatically. “Re-run informational conflict” stays as a ribbon button per CFG-RS-02 — the toolbox pattern.

Click “Add Instruction” — creates a bare alt-fo-shared-process-instruction-base child. Click Complete. The guard alt-fo-shared-dqr-enquiry-has-instruction checks ≥1 instruction exists before the enquiry can close.

Sarah picks the concrete instruction type — alt-fo-pi-process-instruction or alt-fo-wc-process-instruction — from a modal. A new instruction child is created in Draft; Sarah fills it in. One click per instruction type.

A phase-entry trigger reads the instructionTypes field from the original triage form and auto-spawns one instruction per selected type. “Add Instruction” stays visible for late additions — automation dials up, user capability doesn't dial down (CFG-RS-02).

No widget. Sarah creates an alt-global-shared-entity-client work item from the admin menu and adds it as a participant. Crude, but validates that the Client work type exists in the right place in the hierarchy.

The Client Picker widget is deployed. Searches by email → phone → name. Five orchestrated steps on creation: create ODS Person → create Client WT in Draft → add primary-subject participant → transition Client to Pending-Approval → link Enquiry to Client via client-related.

The Picker calls alt-fo-shared-vw-client-create — idempotent, with per-step rollback, guarded by an idempotency key. Four supported flows: promote-contact, create-new, link-existing, PMS-import. Phase-entry trigger spawns the partner-approval task automatically on Pending-Approval.

Sarah creates a partner-approval task manually, assigns to David. David records a decision. No conflict search yet — she runs one outside the system for validation.

“Run Conflict Search” spawns an alt-fo-shared-process-conflict-search child. The AltConflictSearch action runs against the primary subject and contacts, records the result on the search child. The Client Context Panel widget renders it for David alongside his approval task.

Phase-entry on Pending-Approval fires two things in parallel: alt-fo-shared-vw-conflict-check (enumerates all 12 ODS-role entities, fans out AltConflictSearch, aggregates, flags), and alt-fo-shared-task-partner-approval (mode client-approval). David's decision auto-advances Client to Approved or Inactive. “Re-run conflict search” stays as a toolbox command — directors get added, searches get re-run.

Sarah advances Draft → Onboarding, types matter details into the description, then advances Onboarding → Converting. Validates the onboarding phase shape.

Onboarding form plus participant widget. Sarah fills matter type, billing defaults, assigns responsible lawyer and partner. Matter-compliance child is created manually when she clicks “Start Matter Compliance”. “Proceed to Converting” moves the phase forward.

alt-fo-shared-vw-instruction-onboarding fires on Onboarding entry: auto-spawns the matter-compliance child, validates prerequisites (client linked, matter type set, responsible partner assigned), surfaces a “missing prereq” task for the responsible lawyer if anything's absent. “Proceed to Converting” stays user-driven (CFG-RS-01 — user-driven transitions always possible).

Rachel creates a Client Compliance work item, advances phases (AML Verification → Risk Scoring → Approval → Complete) manually. No real AML lookup — just validates the lifecycle.

Rachel opens the AML task, records ID verification outcome. Opens the CRR (Client Risk Rating) form — jurisdiction, industry, PEP — system calculates the risk score. Partner-approval task in cycle-approval mode; David reviews and decides. Rachel updates the Client attributes on completion.

alt-fo-shared-vw-client-compliance drives the phases. On AML entry the VW auto-creates the task and calls FirstAML outbound. Five event-engine plans listen for inbound FirstAML events and update the Client's firstAmlCaseRef and identityVerificationStatus. Auto-advances AML → Risk → Approval → Complete on outcomes. “Re-fire FirstAML” stays as a toolbox command for support when automation is off.

Rachel manually advances the matter-compliance phases. No forms, no tasks — just phase validation.

Classification form (practice area + activity), MRR form (matter-specific risk), partner-approval task (matter-compliance mode). Rachel drives each task to completion.

alt-fo-shared-vw-matter-compliance drives the transitions. On terminal, the platform fires a process-complete event. The Instruction's gate-2-reevaluator plan consumes it and re-runs the four-gate check automatically.

Sarah checks each condition herself and clicks “Create Matter” when she's satisfied. Validates the manual gate.

Same as Pass 1 — Sarah checks conditions on the Client, the compliance children, and the approval task, then clicks “Create Matter”. No re-evaluator yet; the matter is created as an instruction child manually.

alt-fo-shared-vw-instruction-gate-2-reevaluator subscribes to process-complete events from Client Compliance and Matter Compliance and to approval events. On every fire, it re-runs the four-gate check and writes gatesAllPassed = true when they all pass. alt-fo-shared-vw-instruction-converting guards on that flag before materialising the matter. “Override gate — force create” is available as an admin-only toolbox command for support scenarios.

Sarah manually creates a Matter work item as a child of the Instruction. Advances Instruction → Live. No PMS call yet.

“Create Matter” uses createWorkItem. Sarah copies client, case team, and billing defaults with “Copy from Instruction” ribbon commands. PMS provisioning is stubbed — a log entry, not a real push.

alt-fo-shared-vw-instruction-converting executes every step: create matter → link Client → copy case team via alt-fo-shared-wf-add-participant → copy billing via alt-fo-shared-wf-update-work-item → transition Instruction to Live → PMS provisioning fires on Client → Approved. On PMS failure exhaustion, escalation task appears for the support team. “Retry PMS” stays available forever as a toolbox command (CFG-RS-02).