From AI News to AI Action

A company that reads every piece of AI news published this quarter will end the quarter exactly where it started: informed and unchanged. That means every model card, every launch post, every regulatory filing and every funding round.

• The feed never ends.
• The share of it that turns into an outcome is close to zero.

This is the quiet failure at the front of every AI program. The problem is not too little information. It is that nothing turns information into action, and nothing proves that any of it moved a number.

This analysis is the long-form case behind the series' fifth argument. The most valuable thing an intelligence platform can do is not summarize the world faster. It is to wire every insight to a next action, and then carry that action all the way through controlled execution to a measured result. That pipeline is the front of the harness, and almost no one is building it.

1. Information overload is a problem of structure, not volume

The usual framing of AI information overload is about quantity: there is too much to read. That framing leads to the wrong fix: better filtering, tighter summaries, a curated feed. Those help one person keep up. They do nothing for the company, because the company's problem is not volume. It is that there is no path from a piece of news to a change in an outcome.

Think about what actually happens when a leadership team reads that:

• a frontier lab cut inference prices,
• a regulator issued new guidance on automated decisions, or
• a competitor shipped an agent for accounts receivable.

The information lands. It gets discussed. Sometimes it gets forwarded. Then the meeting ends, because there is no defined next step. Nothing says: this story touches our source-to-pay process, the agent that owns that process runs in three regions, here is what changes, and here is who decides.

News that informs and action that changes an outcome are different things. A newsletter is built for the first and cannot do the second, because the second requires knowing the reader's processes, agents, controls and value levers. A publisher does not have that context, and a feed does not carry it. The result is a leadership team that is current and stuck at the same time: well read, well briefed, and not measurably different for any of it.

The fix is not a better feed. It is a pipeline that treats every incoming item as raw material to be turned into work, and a graph that holds enough of the company's own structure to route that work to where it matters.

2. The source object model

Refining starts by giving every item a structured identity. A raw article is a block of prose. A source object is a typed record the rest of the pipeline can reason about. The same shape works whether the item is a news article, a regulatory filing, an earnings transcript, a model release note or a vendor announcement.

Confidence is the field most feeds leave out, and the one that matters most later. An unverified rumor about a model launch and a published price change from the vendor are not the same input. A pipeline that treats them the same will route noise into the backlog. Confidence is what lets the system tell act on this from track this from ignore this. Without it every story carries equal weight, which is the same as no weight.

A source object is not the answer. It is the foundation that makes every later stage possible: structured enough to map, score and connect, not just read.

3. From intelligence to action, stage by stage

With a source object in hand, refining moves through a fixed sequence of stages. Each one turns some awareness into some workable task. No stage is optional:

• Skip role mapping and the right person never sees it.
• Skip the action artifact and the whole pipeline falls back into a newsletter.

Read the table top to bottom and watch the item change:

• At stage one it is a cleaner version of the news.
• By stage three it is attached to a process the company runs.
• By stage five it carries a value lever and a control risk.
• By stage seven it is a backlog item or an agent card: something an engineering team can build, a CFO can fund and an auditor can trace.

The same model-release post a feed would show as a headline becomes, at the bottom of this pipeline, a scoped piece of work with an owner.

The market has built the top of this table many times. Structured feeds, topic tags and persona digests are stages one and two, and they are commodities. The value lives in stages five through seven, where awareness becomes something that can be funded, owned and audited. That is the part almost no one ships, because it needs a model of the reader's company, not just a model of the news.

The five process domains and five value levers

Two of the mappings deserve names, because the whole system rests on their vocabulary.

• Process mapping assigns each source object to one of five process domains: lead-to-cash (L2C), source-to-pay (S2P), forecast-to-fulfill (F2F), plan-to-perform (P2P) and record-to-report (R2R).
• Use-case extraction attaches a value lever: revenue, margin, working capital, productivity or risk.

So every action artifact that leaves the pipeline knows which process it affects and which number it moves. An item that can answer neither does not leave. It is a watch item, not an action.

4. The Koko Intelligence Graph

Stages produce objects. Objects only compound if they connect. A source object that touches S2P, one that names a vendor and one that describes a new tool capability are three unconnected facts until a graph links them to each other and to the company's own deployed agents and value cards.

The Koko Intelligence Graph is that connecting layer. It links eight kinds of node into one graph of objects you can act on:

• stories,
• companies,
• models,
• tools,
• vendors,
• use cases,
• capabilities, and
• processes.

Every node, and every link between nodes, is built to answer four questions:

1. What changed? The event, taken from the source object.
2. Who cares? The roles and accounts the change touches.
3. Which process is affected? The L2C / S2P / F2F / P2P / R2R domain.
4. Which agent can act? The existing agent, or the build that should exist.

A feed and a graph are different kinds of thing, not more and less of the same.

• A feed is a timeline: things that happened, ordered by recency, identical for every reader.
• A graph is a structure: things that happened, connected to the things they affect in your company specifically.

When a frontier lab cuts inference prices, a feed shows every reader the same headline. The graph tells one company that three of its deployed agents just got cheaper to run, names the margin lever on each and flags whether a value card it already holds needs a new baseline. The same outside event, routed by the graph, becomes a different and specific action for each company.

This is exactly why intelligence is not news. News is what happened. Intelligence is what happened, wired to who in your organization cares, which of your processes is exposed and which of your agents can do something about it. The graph is what makes that wiring last, instead of being rebuilt by hand every morning.

5. Koko already runs the front of the arc

These claims are not aspirations. The front of this pipeline runs in production today, across four capabilities that already exist and already produce structured output:

• Sourced daily briefs turn the raw feed into dated, scored, structured intelligence. That is the source-object stage, running continuously rather than on request.
• Persona insights translate that intelligence for the CFO, the CIO-CTO, the partner-MD and the builder. That is role mapping, delivered as something each persona can read and use.
• Company diagnostics score where a given organization is exposed, behind or ready. That is the diagnostic artifact at the bottom of the pipeline, attached to a specific company.
• The Agent OS turns a recommendation into an agent that can be built and deployed. That is the bridge from action artifact to running capability.

Together these cover the path from a source to a recommendation. The intelligence is sourced, scored, routed by role, mapped to process and turned into a recommendation a team can act on. That is the front of the harness, and it is live.

6. The harness adds the back half

A recommendation is where most intelligence products end, and where the hard part begins. An exec brief that recommends an agent, a value card that names a lever, a backlog item with an owner: these are still proposals.

• No outcome has moved.
• The number on the P&L is unchanged.
• The pipeline has produced excellent intentions and zero evidence.

The harness exists to carry the item the rest of the way, through three more stages the front half cannot reach on its own:

• Controlled execution. The recommended agent runs under the control plane: risk tiers, human approvals, segregation of duties and scoped tool access. It does not act because someone read a brief. It acts because a governed capability was deployed to act, with the guardrails that make a company willing to let it.
• Evidence. Every run leaves an audit-ready record of what the agent did, on what data, under which approval and with what result. This is what turns "we deployed an agent" from a claim into a fact a risk officer can sign and an auditor can trace.
• Value. The evidence resolves into a measured result on one of the five levers: revenue, margin, working capital, productivity or risk. The loop closes when a story from the morning feed can be traced, weeks later, to a measured change in a number the CFO reports.

The full path, end to end:

source → insight → diagnosis → recommendation → controlled execution → evidence → value

Every link is a place a competing intelligence product stops.

• Some sell the source.
• A few reach the recommendation.
• None carry the item through controlled execution to a measured result, because that takes a harness (a control plane, an evidence ledger and value telemetry), not a content pipeline.

The front of the path makes the company aware and decided. The back half makes it changed, and able to prove it. This piece is about the front; the rest of the series is about the back.

7. The discipline that makes it real

A pipeline this elaborate is easy to fake. Add more tags, ship a prettier digest, call the topic clusters a graph, and the output looks sophisticated while still being a newsletter. Two rules separate the real thing from the imitation, and both are blunt on purpose.

No insight ships without a next action.

• Every item that leaves the pipeline names something to do: build this agent, re-baseline this value card, score this exposure, file this backlog item.
• An insight that cannot produce a next action is a watch item, logged but not promoted.

This rule is what keeps the pipeline from sliding back into a feed. A feed is allowed to end at "here is what happened." This pipeline is not.

No action ships without an owner and a lever.

• Every action names a person accountable and a value lever it is meant to move.
• An action with no owner is a suggestion. An action with no lever cannot be funded or measured.

This is the same logic the series applies to agents (no value card, no money to scale), pushed all the way to the front of the system, so the discipline starts the moment a story arrives, not the moment an agent is proposed.

These rules are cheap to state and expensive to keep, which is exactly why they are the test. An intelligence product that cannot tell you what to do, and cannot later prove that doing it changed an outcome, is a newsletter with better metadata, however it is marketed. The market is full of those. Companies have read enough of them to know they do not move the number.

8. The view ahead

Over the next several quarters, intelligence products split into two groups, and the dividing line is whether the product carries an insight to an action or stops at awareness.

• Feed-shaped products (digests, trackers, curated newsletters, however well tagged) become commodities, because summarizing the world faster is something everyone will be able to do and no one will pay extra for.
• Platforms that wire intelligence to governed, measured action become what companies actually fund, because they are the only ones that change an outcome rather than describe one.

The intelligence graph becomes the asset. A company that has spent two years connecting its stories, processes, agents and value levers in one graph holds something a competitor cannot buy off the shelf or rebuild overnight: a structure where every outside change arrives already routed to the place it matters. The graph is to intelligence what the harness is to agents: the owned layer that compounds, which all the commodity parts flow through.

And the closed loop becomes the proof. The defining test of a real intelligence platform is not the quality of its morning brief. It is whether it can take a story from that brief and trace it, through diagnosis, recommendation, controlled execution and evidence, to a measured result on a lever the CFO reports.

The day an organization can draw that line from a headline to a measured number is the day its AI program stops being an expense that informs and becomes a capability that compounds. That line is the harness, drawn from front to back. The front is built. The rest of this series is the back.