Make what if
into how so.

A workbench for real and invented histories. Record events, the periods that hold them and the causes that link them, then branch at any moment and follow what changes.

Opens on Clerks Prevail, a branch of this history in which Parliament bans the engines, with the original drawn faintly beneath it. Branch it again, change anything; nothing leaves your browser.

Swipe the timeline sideways for the whole history, 1834 to 1871.

A history that forksThe Engine Age: 19 events from 1834 to 1868, joined by 24 causal links. On 12 Jul 1860 a branch, Clerks Prevail, splits away. In it, “Parliament bans private calculating engines”, where the original history has “Parliament passes the Engine Licensing Act”.Building the EngineThe Calculating OfficesEngines on the WireThe Clerks’ RebellionThe Engine Age1843 The Engine computes Bernoulli numbers before the Royal Society1860 Original: Parliament licenses the enginesClerks Prevail1860 Parliament bans private calculating engines1861 Lovelace’s programmers emigrate to Berlin18351840184518501855186018651870

The events in The Engine Age

  1. 15 December 1834: Babbage completes the full design of the Analytical Engine (Charles Babbage, Analytical Engine)
  2. 2 March 1838: Prime Minister Peel reverses course and funds construction (Robert Peel, Charles Babbage)
  3. 10 September 1839: Joseph Clement standardises the engine’s gears and screw threads (Joseph Clement, Analytical Engine)
  4. 1 September 1843: Ada Lovelace publishes Note G, the first program (Ada Lovelace, Analytical Engine)
  5. 20 November 1843: The Engine computes Bernoulli numbers before the Royal Society (Charles Babbage, Royal Society)
  6. 14 April 1845: The Admiralty orders engines to compute navigation tables (British Admiralty, Analytical Engine)
  7. 1 June 1847: Lloyd’s opens an actuarial engine room for the insurance market (Lloyd’s of London, Analytical Engine)
  8. 18 June 1847: The Bank of England moves its ledgers onto engines (Bank of England, Analytical Engine)
  9. 5 October 1848: Lovelace founds the School of Engine Programming in London (Ada Lovelace, School of Engine Programming)
  10. 30 May 1851: The 1851 census is tabulated entirely by engine (General Register Office, Census of 1851)
  11. 1 July 1851: The Great Exhibition’s centrepiece is a working engine hall (Prince Albert, Great Exhibition)
  12. 11 February 1853: Engines in London and Manchester exchange results by telegraph (Electric Telegraph Company, Analytical Engine)
  13. 20 August 1855: Prussia buys three engines for its General Staff (Prussian General Staff, Analytical Engine)
  14. 17 March 1859: Ten thousand clerks protest at Westminster against the engines (Clerks’ Union, Parliament)
  15. 29 March 1859: Manchester clerks hold a demonstration in solidarity (Clerks’ Union, Manchester Exchange)
  16. 5 June 1860: Parliament debates engine licensing legislation (Parliament, Analytical Engine)
  17. 28 June 1860: Parliament passes the Engine Licensing Act (Parliament, Clerks’ Union)
  18. 16 June 1866: Moltke uses engine-planned railway timetables to mobilise (Prussian General Staff, Austrian Empire)
  19. 9 January 1868: Britain and Prussia begin an engine arms race (British Admiralty, Prussian General Staff)

In the branch Clerks Prevail

  1. 12 July 1860: Parliament bans private calculating engines (Parliament, Analytical Engine)
  2. 2 April 1861: Lovelace’s programmers emigrate to Berlin (School of Engine Programming, Prussian General Staff)
The Engine Age, an invented example: Babbage finishes the Analytical Engine in 1843. In a branch, Parliament bans the engines in 1860 instead of licensing them. Select an event to see what it led to. The curves are causes: direct indirect contributory

A minute in the app

Build a history, trace what one event caused, and branch it. The video is made from the running app, like every picture here.

Read it, trace it, change it

See it in time

Events sit inside arcs: the periods that contain them, nested as deep as the history needs. Select an event to trace what it caused; its effects stay lit while the rest fades back.

Or follow one actor through it all, and see the economic, social and political pressures read from clusters of events.

In the demo: open the timeline

1 September 1843 Ada Lovelace publishes Note G, the first program. Led to 15 later events; everything else falls back.

Follow the causes

Every link between two events is direct, indirect or contributory, with a weight, a confidence and the evidence for it. Lay the graph out the way that reads best, and find every path from one event to another.

In the demo: open the causal graph, and select an event to find every path from it.

  1. 1834 Babbage completes the full design of the Analytical Enginecontributory, weight 0.5
  2. 1843 Ada Lovelace publishes Note G, the first programdirect, weight 0.9
  3. 1843 The Engine computes Bernoulli numbers before the Royal Societydirect, weight 0.8
  4. 1845 The Admiralty orders engines to compute navigation tablesindirect, weight 0.4
  5. 1851 The 1851 census is tabulated entirely by enginedirect, weight 0.8
  6. 1859 Ten thousand clerks protest at Westminster against the engines
One path through the graph, 5 links long. The line says how one event led to the next: solid is direct, dashed indirect, dotted contributory, and thicker is stronger.

Change one thing

Branch a history at any moment and write what happens instead, with the original drawn faintly beneath. Compare branches side by side, then merge one back through a conflict resolver that flags what doesn't fit.

In the demo: branching and comparing. Merging needs your own install.

Clerks PrevailThe Engine Age, the original
They part on 12 July 1860, when Parliament bans private calculating engines. The branch's own events are amber.

Bring in history

Paste text, or give it a Wikipedia article or a Wikidata ID. What it finds comes back in a review table where you edit, drop or keep each event. Nothing is written until you approve.

Patterns read the text offline; an Anthropic or OpenAI key adds a model.

Needs your own install: the demo can't fetch pages. Run it locally

Review: 3 of 3 events kept
KeepEventDateConfidence
The Royal Society honoured Ada Lovelace with the Copley MedalRoyal Society → Ada Lovelace1870-02-140.9
The Admiralty launched HMS CalculatorAdmiralty → Calculator1871-03-010.8
The Prussian General Staff founded a programming academy in BerlinPrussian General Staff → Berlin1872-06-020.9
Three sentences of pasted text, read into events. Nothing is written until you keep them.

Run it on your machine

You need Node 20 or later, and nothing else: local mode keeps every graph in JSON files, so there's no database to set up. Your own install adds what the demo can't: bringing in history, exporting, merging and simulating.

The app

Clone it, install, and start it. Then open localhost:5173.

Terminal
$ git clone https://github.com/Qworg/althistory.git
$ cd althistory
$ npm install
$ ./start-local.sh

For a shared server with Neo4j and Redis, see production deployment.

From a script or an agent

Every screen is also a CLI command that answers in JSON, and the MCP server lets an agent write a history with you, whether it bends a real one or invents a world with its own calendar. Link it once and give it to your MCP client, which starts althistory mcp itself.

Terminal, in the repository
$ npm link
# Claude Code; other clients take a JSON config
$ claude mcp add --scope user althistory \
    -- althistory mcp

Build histories with an agent

Find the moment. Change it. Follow what happens.