[bpshaver]

If you're going to use a spreadsheet as your UI, I think you should be more careful how you describe the semantics of rows and columns. And make a strong case for why this representation makes sense.

People expect that rows represent observations and columns represent variables. Along those lines, would it not be more accurate to say each row represents an instance of a task and column represents a sub-task or step in that task?

"each row corresponds to an AI agent executing a task" just... doesn't make sense. The rows exist before you press the "execute" button, after all. The agent executing the (generic) task is something that happens on or with the sheet.

[gcanyon]

Seconding this -- I actually had copied "each column represents a step in the workflow and each row corresponds to an AI agent executing a task" to post a comment like this, but then checked through the comments to see if someone beat me to it, and here you are!

I'll add my terminology though, since it's slightly different. I think we're mostly agreed that "each column represents a step in the workflow" is fine. But for me the sheet represents an agent configuration, and each row is a specific job the agent performs.

[austinwang115]

We're using a spreadsheet UI because it's familiar to millions of office workers and easy to understand the step-by-step progression of a workflow. The wording that you proposed makes a lot of sense to us.