About Tell

Every layer of the modern technology stack has a standard. Authentication has OAuth. APIs have OpenAPI. Agent tooling has MCP. Code has version control.

Strategy has nothing.

Strategic intent — what an organisation is betting on, what assumptions underpin those bets, and what evidence says about whether they're working — lives in slide decks, board packs, and the heads of a few senior leaders. It can't be queried. It can't be versioned. It can't be read by the AI agents that increasingly execute on an organisation's behalf.

The result: AI agents operate at machine speed with zero strategic context. They can do things, but they have no way of knowing whether those things align with what the organisation actually cares about.

Tell is the protocol that fills this gap.

In poker, a tell is the involuntary signal that reveals the truth behind the bluff. A twitch, a pause, a pattern in the betting — something that tells you what's really going on beneath the surface.

Every strategy has tells too. Evidence signals buried in data, customer behaviour, market movements, operational metrics — signals that reveal whether your strategic assumptions are actually holding or quietly breaking.

Most organisations can't read the tells because their strategy lives in a deck, not a model. Tell is the protocol that makes those signals readable — by humans and by machines.

Tell is designed to be useful even without Apophenic. A team could implement a basic Tell model in a spreadsheet. An agent framework could support Tell reads and writes. A consulting firm could structure client engagements using Tell.

Apophenic is where the full Level 3 Platform experience lives — real-time events, version history, scenario modelling, AI-powered intelligence — but the protocol itself is open for anyone to implement.