The surface is the differentiator

An agent listens for a 10-K filing dropping at 4:01 PM. It also listens for an internal request from your VP of Sales at 9:14 AM: “pull together a brief on the three accounts that went quiet last week.” Both are real-world events. Both should activate the agent. The framing that puts external triggers on a pedestal: “the trigger layer is the moat”: is internally useful for naming what an agent listens for. It is not the framing a buyer uses to decide whether to hire one.

Buyers think in two halves: what happens inside, what happens outside

What happens inside the business is the dominant half. Internal requests, internal needs, the weekly cadence of work that should already exist by the time the team arrives Monday morning. What happens outside: competitor moves, regulatory updates, customer signals, market events: is the second half. Both matter. An agent that handles only one is half an agent.

Where the work shows up decides whether the team trusts it

AI labor has one big trust failure: opacity. The agent works somewhere: a separate dashboard, a console, an app the buyer logs into: and ships a report later. The team has to remember to check. They don’t. The work the agent did becomes invisible by default.

Fidelic agents work in your Slack. Same channels the team already opens. Every action lands in the channel. Every escalation logs the rule that fired and the trigger that gated it. Every Friday digest publishes where the team will read it. Internal visibility: visible to the buyer’s whole team, in the surface they already live in: replaces the dashboard nobody checks.

The differentiator, in plain language

Three things, in order. First, the agent works on what happens inside the business and what happens outside: not just one. Second, the agent works inside the team’s Slack, in front of the people who would otherwise have done the work themselves. Third, the agent’s work is transparent to the whole team by default: every send, every escalation, every flagged signal lands in the channel, with the rule that approved it visible. No black-box dashboard. No separate app. No “log into our portal to see what happened.”

Why visibility is harder than it sounds

The work an experienced operator does is mostly invisible: the small adjustments, the watch-this-but-not-that filtering, the language they choose for the escalation. AI labor that learns this work has to watch it happen. AI labor that hides in a dashboard cannot watch the team work; AI labor in the team’s Slack can. That’s part of why the surface matters.

Michael Polanyi, The Tacit Dimension, University of Chicago Press, 1966

Polanyi put it bluntly: we know more than we can tell. The job of the agent is to make some of that tacit knowledge legible: by working in the same surface the team works in, on both internal requests and outside events, with every action visible to the people who would have to react if the agent got it wrong.

What this isn’t

It isn’t a claim that what an agent listens for doesn’t matter. It does: every Roster entry publishes the events the agent watches for, internal and external. It isn’t a claim that the cognitive architecture is solved; agent design is genuinely hard work. The claim is narrower: when a buyer evaluates AI labor, the load-bearing question isn’t “whose taxonomy of external triggers is largest.” It’s “where will the agent’s work live, and who on my team can see it.”