IKARUSpersonal ai os
A workflow in IKARUS is an ordered list of typed steps: an instruction for the assistant, a browser action against a tab you attached, or a vault reference that reads a live entry or captures results into a new one.
The rule that keeps it trustworthy is architectural: one engine runs them all. Whether a workflow starts from the editor, the chat sidebar, or a chat command, it is the same execution path, and browser and vault steps still respect your permission tiers mid-run. Two engines for the same concept is how behavior drifts; IKARUS had the beginnings of exactly that problem and the fix was to delete the second path.
Workflows are scoped to the context that made them, system templates stay read-only, and running a workflow across contexts is refused rather than quietly allowed.
