Identifying Inputs

Interview Phase (Optional)

When to Interview: Skip if the user has already identified UI actions/commands and processor triggers. Interview when it's unclear which actions are user-initiated vs. processor-automated.

Interview Strategy: Separate UI-driven commands from processor-driven commands before cataloging inputs. Mixing them leads to incorrect role attribution, which breaks the Role Catalog traceability that downstream steps depend on.

Critical Questions

1. Automation Level (Impact: Determines which commands are UI-triggered vs. processor-triggered)

   • Question: "Are there actions that should be: (A) User-initiated only, (B) Processor-automated, (C) Mix of both?"
   • Why it matters: Knowing automation vs. manual separates command types
   • Follow-up triggers: If (C) → ask "Which specific user actions trigger automation? What does the processor decide on its own?"

2. External System Triggers (Impact: Determines if there are processor commands from webhooks/integrations)

   • Question: "Will commands be triggered by: (A) UI only, (B) External webhooks (payments, notifications, etc.), (C) Scheduled processors, (D) All of above?"
   • Why it matters: External triggers are processor commands, not UI commands
   • Follow-up triggers: If (B) or (D) → ask which external systems send webhooks and what data they include