Adaptive Decision Interface

How A2UI Works

Traditional dashboards show the same interface to everyone. A2UI dynamically generates UI blueprints based on context:

• Decision Type: Pricing, inventory, risk, promotion
• Risk Level: Low, medium, high, critical
• User Role: Operator, manager, admin
• Domain: Retail, fintech, lending compliance requirements

The backend Blueprint Builder service generates a JSON blueprint that the frontend renders deterministically. This ensures:

• Consistent rendering across sessions
• Complete audit trail of what was shown
• Role-based component visibility
• Compliance with regulatory requirements

Layout Modes

A2UI selects one of three layout modes based on decision characteristics:

Blueprint Structure

The backend generates a JSON blueprint that describes the UI structure:

{
  "blueprintId": "bp_abc123",
  "decisionId": "dec_xyz789",
  "layoutMode": "guided",
  "components": [
    {
      "type": "StepIndicator",
      "props": {
        "steps": ["Review", "Impact", "Approve"],
        "currentStep": 0
      }
    },
    {
      "type": "AnalysisPanel",
      "props": {
        "factors": [...],
        "confidence": 0.94
      }
    },
    {
      "type": "ImpactChart",
      "props": {
        "metric": "margin",
        "baseline": 28,
        "projected": 34
      }
    },
    {
      "type": "ApprovalForm",
      "props": {
        "requiresComment": false,
        "actions": ["approve", "reject", "modify"]
      }
    }
  ],
  "visibility": {
    "operator": ["StepIndicator", "AnalysisPanel"],
    "manager": ["StepIndicator", "AnalysisPanel", "ImpactChart", "ApprovalForm"]
  },
  "auditContext": {
    "generatedAt": "2024-01-15T10:30:00Z",
    "userId": "usr_123",
    "sessionId": "sess_456"
  }
}

Component Whitelist

A2UI uses a fixed set of approved components. Custom components are not supported to ensure security and audit compliance.

Role-Based Visibility

Different user roles see different components. The blueprint defines visibility rules that the frontend enforces:

Audit Logging

Every A2UI interaction is logged for compliance and debugging:

• Blueprint Generation: When and why a blueprint was created
• Component Render: Which components were shown to which user
• User Interaction: Clicks, form submissions, navigation
• Decision Actions: Approve, reject, modify with timestamps

For Fintech and Lending domains, audit logs are retained according to regulatory requirements and can be exported for compliance reviews.

Deterministic Rendering

A2UI guarantees that the same blueprint renders identically every time. This is critical for:

• Audit Replay: Regulators can see exactly what a user saw
• Debugging: Reproduce issues by replaying the blueprint
• Testing: Consistent UI for automated testing

Integration with Human-in-the-Loop

A2UI is the visual layer for Decisio'sHuman-in-the-Loop system. When a decision requires human approval:

1. Backend flags the decision for review
2. Blueprint Builder generates an appropriate layout
3. A2UI renders the review interface
4. User takes action (approve/reject/modify)
5. Action is logged and decision is updated

Customization

While components are fixed, enterprises can customize:

• Branding: Logo, colors, fonts via theme settings
• Layout Rules: When to use Fast Path vs Guided vs Escalation
• Role Mappings: Map your org roles to A2UI roles
• Component Defaults: Default props for components

Contact your account manager for custom A2UI configuration.