Workflows

Overview

DMTR workflows fall into two categories: discovery (search, browse, express interest) and execution (transfer, encumbrance, lifecycle change). Discovery workflows do not mutate state; execution workflows do. Human-in-the-loop and intent capture bridge the two.

Discovery workflows

Discovery workflows help users find and evaluate positions. Search, filter, browse, and IOI (indication of interest) are discovery operations. They query the Registry and Rights Engine for visibility and transferability but do not execute transfers. Discovery is low-friction and supports exploration.

Search/Browse → IOI → Intent Capture → Rights Engine → Registry

Execution workflows

Execution workflows mutate state: transfers, encumbrances, status changes. They flow through the Rights Engine and Identity Graph, then the Registry. Execution requires full validation and compliance. It is higher-friction and produces auditable mutations.

Human-in-the-loop

Many workflows require human approval: consent signatures, compliance review, exception handling. Human-in-the-loop integrates human steps into otherwise automated flows. DMTR supports intent capture and approval workflows that pause for human action before proceeding.

Intent capture

Intent capture records a user's desire to perform an action (e.g., "I want to sell 5 units") before execution. Intent can be stored, routed for approval, and later executed when conditions are met. Intent capture separates expression of intent from execution, enabling async workflows and compliance checks.

Discovery                          Execution
─────────                          ─────────
Search/Browse → IOI → Intent  →  Rights Engine → Identity Graph → Registry
                     Capture     (validation)   (pre-clearance)  (mutation)
                       ↓
                 Human-in-the-loop
                 (consent, review)

Related

• Registry — Workflow source of truth
• Rights Engine — Evaluates workflow steps
• Execute a Transfer — Transfer workflow guide