Eight lanes, one map: sequencing an ecosystem

On the wall of our office in Bengaluru there is a map with eight lanes on it: intelligence, work, communication, finance, identity, commerce, health, infrastructure. Visitors sometimes mistake it for ambition decoration. It is closer to the opposite — it is a list of things we are not allowed to build yet, and the conditions under which that changes.

Lanes are ordered by what they inherit

The sequence is not ranked by market size, or we would have started with finance. It is ranked by inheritance: each lane must hand the next one an asset that makes it cheaper to win than it would be for a cold entrant. Intelligence — the Y0 runtime — comes first because it produces the two assets everything else consumes: a context graph that knows the user's working life, and a trust ledger proving we handle that knowledge soberly.

Work inherits both and adds artifacts — documents, tasks, invoices — to the graph. Communication inherits the artifacts and adds relationships. Finance inherits relationships and history, which is precisely what underwriting is. By the time the map reaches identity, the lane is not a product bet; it is a formality the graph already supports. Skip a lane and the inheritance breaks: a finance product built without the work lane's artifact history is just another fintech app, paying full CAC and starting from zero trust.

lane[n] enters build when:
  lane[n-1].retention  >= floor      ✓ habits, not spikes
  lane[n-1].margin     >  lane[n].burn  ✓ self-funded entry
  graph.coverage(n)    >= 0.6        ✓ context exists
  ledger.balance       >  0          ✓ trust earned, not owed

Gates, not dates

Notice what is absent from that block: a calendar. We do not know when the work lane opens, and we have stopped pretending. The gates are observable — retention floors, margin coverage, graph coverage, ledger balance — and a lane opens when its gates clear, whether that takes four quarters or nine. Twice already a gate has pushed a lane back, and both times the delay was the system catching a mistake we were about to enjoy making.

A roadmap with dates is a list of promises. A map with gates is a list of proofs.

Why publish the map at all

Telegraphing your sequence carries obvious risk: incumbents can see you coming. We publish it anyway, for a less obvious reason — the map disciplines us more than it informs them. Every giant we studied could have entered its later lanes earlier, and the ones that stumbled mostly did. Writing the gates down in public makes skipping ahead a visible act of betrayal rather than a quiet act of drift. We are betting the discipline compounds faster than the disclosure costs. Ask me in a decade whether the bet paid.