Launchpad can run a fixed set of commands. It cannot let someone assemble their own.
A workflow joins a trigger to one or more steps: a hotkey or keyword starts it, steps transform the input or act on it, and an output copies, pastes, opens or shows the result. People should be able to build one without writing code, keep it in their own library and share it as a file.
Scope
- A trigger: global hotkey, palette keyword, or selection.
- Steps that filter, transform or branch on the input.
- Outputs: copy, paste, open a URL or file, show a result, notify.
- An editor that shows the chain and runs it step by step for debugging.
- Import and export as a single file.
Constraints
This is the largest open design question in the app. Extensions are deliberately data only: they cannot run code, reach the network or read files, and that rule is what keeps the sandboxed build viable. A workflow that executes arbitrary steps needs a declarative step vocabulary the app interprets, not a script host, or it needs a distribution story that accepts the loss of the sandbox.
Settle that before building. Related: #5.