The Automator's audience is unsettled, and its Identity row depends on it

[The-Running-Dev]

The Automator's audience is unsettled, and its Identity row depends on it.
second-consumer-packages.md §5 has it open-core, feature-tiered and licensed per installation
with agents as the paid dimension, which implies external paying customers; Ben describes it as
the tool he uses to manage plugins and workflows. Both, currently — the use is still being
worked out. Record it the way BarStrad's billing cell is recorded: unsettled and stated, not
guessed. It matters because reading (a) makes Platform's Identity serve a real multi-user,
machine-credential case and reading (b) leaves it one serious human-facing consumer and two thin
ones.

Done when

• The question is answered and the answer recorded

---

Agent instructions

Authority: this issue — the bullet that raised it has been removed from design/90-decisions.md's ## Open section, since it is now tracked here rather than there.

Stop if answering this turns out to need a contract or schema change to design/20-contract.md or an existing published contract — that is a design-cycle decision, not one this issue's own scope covers.