What you say is what you get.

Every automation tool has the same three parts: something arrives, something is checked, something is sent. The difference is whether you can see them. A canvas of nodes shows the mechanism to the person who built it and hides it from everyone else, including the builder six months later. A chat transcript shows the conversation and hides the mechanism entirely.

So we made the pipeline the only thing you ever look at. Trigger, Filter, Deliver, left to right, in the words you used. The model that designs a robot has to produce that pipeline, not a script, which means the thing it made is the thing you read. When a robot misbehaves, you open it and the mistake is sitting in one of three boxes.

The five views exist because people think in different shapes. A bookkeeper wants the table. A household wants the cards. The pipeline is the default because it is the one a first-time reader understands without being told.

Which robot fired, which destination took it, which Mac did the work, and the minute it happened. Failures are written in the same place, in the same size type, so a robot that stopped working is visible the same day.

The share page works the same way, turned outward: one robot, drawn as its pipeline, for the person it helps. Your spouse sees the school-closure robot exactly as it runs. Your bookkeeper sees the card-code robot and nothing about your household. The link switches off with one click.

Both are built on the same rule: the page tells you what the robot will do, in the words you would use, and never hides the mechanism behind a diagram. When a delivery fails, the feed records which destination refused and why, and the next one in the chain is tried on the spot, so the person reading the page in the morning sees the whole story of the night in one list, including the part where the backup route carried the message.

For two years a set of iPhone automations forwarded bank codes and card alerts to the people who needed them: a Slack channel for the team, two inboxes for the bookkeepers, a text to a spouse. They worked until the day the Mail app was deleted from the phone. The automations kept their green toggles and stopped sending. Nobody found out for two weeks, and the way we found out was a team member asking why the codes had stopped.

The replacement was written that night as a small program on a Mac: read the messages, match the senders, send to Slack with email as the fallback, and write a line for every delivery. It delivered to a fallback when Slack was down, it wrote a line for every send, and it did not depend on an app staying installed on a phone. It had one flaw: only the person who wrote it could read it.

So the console came next, with the robot drawn as a pipeline anyone in the house could understand. Then the sentence box, so nobody has to open an editor at all. That is the whole product: the reliable half of a script and the readable half of a sentence, on a machine that is already on.