The roadmap

Gates, not dates.

The thesis is that owning the rails beats owning any single thing that runs on them, and that permanent capital is what makes owning rails possible at all. That argument is made elsewhere and is not restated here. What follows is the consequence: if it is right, there is an order in which things have to become true, and this is that order.

The order matters more than the contents. A group that acquires several good things has a portfolio; a group that acquires them so that each one lowers the cost or raises the value of the next has an estate. Every gate below is chosen because passing it makes the next one cheaper, and because failing it makes everything after it decorative.

None of this is a schedule. Each gate is a condition a stranger can check, and the state of each is published whether or not it is flattering — which is the only version of a roadmap that is worth anything a year after it is written.


The corporate track — how a vertical advances

  1. 01

    Formed

    A thesis the office can state in a sentence, and one property that exists to test it.

    A vertical begins as a claim about a market plus something built rather than a slide. Two of the group’s current verticals began as companies that fitted no existing thesis and were underwritten anyway.

    Nothing structural. This gate is cheap by design, because the expensive mistake is refusing to enter a category for four years while entry was still cheap. Formed →

  2. 02

    Operated

    An operating group carrying the vertical end to end, with a named human accountable for every property in it.

    One property, one accountable human — published on the stewardship page rather than held internally, so that an unowned property is visible as one.

    Seats are the constraint here, not capital. A vertical with no operator is a holding, and the register says so rather than describing it as early. Operated →

  3. 03

    Originating

    Deal flow of its own — enough companies arriving in the category that a dedicated arm sees more than the parent would.

    This is the gate that earns a vertical its own Ventures arm. It is a measurement rather than a decision, which is what keeps it from being granted at formation to make a vertical look complete.

    Origination that costs a fee is the most expensive kind. Convening is the group’s answer and the reason it is treated as infrastructure rather than as marketing. Originating →

  4. 04

    Capitalised

    A balance sheet of its own to allocate, earned separately and later than the deal flow.

    A Capital arm is the last gate, not the first. A vertical that receives one before it has origination spends the parent’s balance sheet on somebody else’s deal flow.

    A vertical that is not working is closed rather than starved, because a half-funded vertical consumes the scarcest thing the group has, which is attention. Capitalised →


The technical track — what the estate has to have built

Each gate below is a condition somebody outside this group can check, and the state of each is published whether or not it flatters the office. Where a figure belongs to an operating group, this page links to that group’s record rather than restating it.

  1. 01

    Declared Passed

    Every entity of consequence in the estate publishes a machine-readable charter, a handshake and a directory fragment, and each one is fetched rather than assumed.

    The parent was the last entity in the estate to conform, and that was the first finding of its own audit. All four surfaces are now emitted by the build and gated in CI, so a page cannot be edited into disagreeing with the record.

    The failure this gate exists to catch is a file committed and never served. Only a fetch proves a surface reachable, so the check fetches; a diff against the repository would have passed while the estate returned nothing. Declared →

  2. 02

    Located Not built

    An organisation’s jurisdiction is a field in the record rather than a line in a footer, and an agent can read where a counterparty operates and under whose law.

    Nothing. The directory format has no representation for it, and organisation records carry an empty description object where this would live.

    This is the gate whose absence is easiest to miss, because every other primitive can be demonstrated without it. A procurement agent that establishes capability, relationship and authority but not jurisdiction has found a supplier it may not be permitted to buy from. Located →

  3. 03

    Connected Mechanism built, evidence outstanding

    A relationship in the record confirmed by an organisation nobody in this group controls.

    The mechanism is finished, live and open source: a claim crossing an organisational boundary reaches its final state only when a human at the other organisation signs it, and the asserting party cannot sign its own claim about somebody else.

    The evidence. Almost every fact in the estate’s published record is an organisation describing itself, and the group publishes that reading of its own record rather than the flattering one. A signature between two entities this office controls would prove nothing and the scoreboard is built to say so. Connected →

  4. 04

    Accountable Mechanism built, evidence outstanding

    An agent’s authority is checkable end to end — from a named human, through grants that may only ever narrow, to the agent presenting itself — including how much it may commit.

    Delegation is attenuation rather than inheritance, assertions bind subject to holder, and the chain is verified rather than the signature alone. A charter states the impact tier above which a person must approve.

    Impact tiers do not reconcile with monetary limits, so “may commit us to a contract of this size” is not a question the current format answers. That is unbuilt work rather than a detail, and it is the gate between a demonstration and a procurement decision. Accountable →

  5. 05

    Settled Mechanism built, evidence outstanding

    Work between two organisations neither of which controls the other clears to a sealed record that a third party can recompute offline.

    Receipts and settlements hash through one canonicalisation, and the verifier is pinned against the sealer so the two cannot diverge. Settlements have cleared and can be recomputed from the published payload without asking this group for anything.

    The same gap as Connected, and for the same reason: what has settled so far has settled between parties with a common owner. The primitive is proven and the independence is not. Settled →


What joins them

The two tracks are independent and the group is deliberately at different heights on each. A vertical can be commercially mature and technically undeclared; the mesh is technically ahead of every vertical that currently uses it. A single ladder would average those and flatter both.

What joins them is allocation. Capital follows the corporate gates, and the technical gates decide what a vertical is able to inherit when it passes one. A vertical formed today inherits identity, settlement, a standard and a register that earlier properties paid for — and inherits, equally, the gates the estate has not passed yet.

The honest summary is that the estate is further along on declaring itself than on being confirmed by anyone else. That distinction is the whole difference between a format and a standard, and it is the gate this office is spending against first.


State of every gate as at 2026-08-30. A gate is revised by publishing a new statement, never by editing the old one.

The vocabulary →   The register →