What's known, and what isn't

Facts, not data.

A table gives you data. What you actually want are facts: what happened, where, when, how many, and what nobody wrote down. Futuremodel is where you go to read them, whether they're about the world or about your own organization.

Shooting Incident, an Entity of the Public Domain Mass Shootings, explored three ways: on a map of the United States, as a count by year, and as a table of its Individuals.
How the Entity is looked at
Shooting IncidentEntity · Mass Shootings · Citizen · Public

126 of 162 are on the map. The other 36 have no location recorded. That makes them unknown, not nowhere, and they still count.

162 Shooting Incidents, 1982 to 2026. Counts cover what's recorded, so a year with no bar just means none were recorded.

The six most recent Shooting Incidents.
CaseLocationDateFatalitiesInjuredVenueShooting location
Silver Rail Elementary shootingBend, Oregon15 Oct 202642Schoolunknown
In-N-Out Burger shootingTwin Falls, Idaho1 Aug 202637Otherunknown
San Diego mosque shootingSan Diego, CA18 May 202630Religiousunknown
Austin bar shootingAustin, Texas1 Mar 2026313Otherunknown
Brown University and MIT shootingProvidence, Rhode Island13 Dec 202539Schoolunknown
Michigan Mormon church shootingGrand Blanc, Michigan28 Sep 202548Religiousunknown

6 of 162, newest first.1,197 fatalities in all.

This is Mass Shootings, a Public Domain from the Citizen Experience. It reads Mother Jones' database of mass shootings in the United States, shown here as published on 17 November 2026.

Explore

Start anywhere. See where it leads.

You don't need to write a query to look around. Open a kind of thing, look at it whichever way fits your question, and click through to the one you're curious about.

  • Look at it your way

    Open an Entity as a table, as charts, on a map, or as a graph of what it's connected to. It's the same set of Individuals each time, just seen differently.

  • Go from the number to the thing

    Click into any Individual to see what's known about it, then move on to whatever it's related to. You're always one step away from what a number actually counts.

  • Share exactly what you see

    Whatever you've narrowed down to lives in the address. Keep it as a Saved view, or send someone the link. They get your view, and only of things they're already allowed to see.

Facts over data

A table holds values.
A fact tells you something.

Here's one row from a file, and the same row read as what it says about a real thing: an Individual with a date, a place and a count. Each value has a kind, and the kind decides what you can sensibly do with it.

One row of a file, and the same Shooting Incident read as an Individual with a value for each of six Attributes.
Dataone row of a file
Welding shop shooting,"Miami, Florida",8/20/1982,"…",8,3,11,Other,…,25.796491,-80.226683,Mass,1982

Elsewhere in this file, a date shows up as 10/1/17 and a venue as "workplace", "Workplace" or " Workplace".

Welding shop shootingShooting Incident
Date
20 August 1982
Event
Location
Miami, Florida
Category
Fatalities
8
Quantity
Injured
3
Quantity
Venue
Other
Category
Shooting location
25.7965° N, 80.2267° W
Composite

Each value is read from its Source when you ask. Nothing gets copied.

  • Typed twelve ways, counted as six

    This file spells its six venues twelve different ways. Values that mean the same thing become aliases of one Code, so when you count by venue you get six rows, not twelve.

  • Unknown isn't zero

    36 of these Shooting Incidents have no location recorded. They're left off the map but still counted, and the map tells you how many it's missing. If something wasn't recorded, it's unknown. It isn't false.

  • Always current, never copied

    A Fact doesn't store a value. It's read from the Source when you ask, so you're seeing what's there right now, and your data stays where it lives.

Metrics

Numbers that explain themselves.

You define a Metric once, in a sentence anyone can read, and it's the same number everywhere it shows up. Right next to it, you can see what it counted and what it couldn't.

Counts and sums are just the beginning. Daily, weekly and monthly actives, retention by cohort, a funnel from Sign-up to Purchase: these are all Metrics you describe in the model, so nobody has to rebuild them in a notebook.

You can also say that one Metric influences another, or works against it, and put that claim where everyone can check it.

The Metric Fatalities of the Entity Shooting Incident: its total, its definition, and its value in each year.
FatalitiesMetric · Shooting Incident

1,197

The sum of fatalities over Shooting Incidents, by the year of their date.

Counted over 162 Shooting Incidents. None were left out, because every one has a known value for fatalities.

Insights

What you learned, kept right where you learned it.

A chart won't remember why it moved. An Insight will. You write it on the thing it's about: who, what stood out, when and where, and why, if you know.

It points to its evidence: the Facts behind it, other Insights, and things people actually said, like a customer in an interview, with who said it and when. It can also say what to do next.

Anyone who can see an Insight can verify it or dispute it. Everyone, that is, except the person who wrote it.

An Insight about one Shooting Incident, with the two Facts it names as its evidence.
Insighton a Shooting Incident

The most fatalities of any Shooting Incident recorded, and more than in any whole year from 1982 to 2011.

Who
Las Vegas Strip massacreIndividual
What
Fatalities is 60Quantity
When
1 October 2017
Where
Las Vegas, Nevada
Why
not stated

Evidence

  • FactLas Vegas Strip massacre: fatalities60
  • FactOrlando nightclub massacre: fatalities49

Stories

You don't have to go looking.

A Story is one thing that happened to something you follow, along with what it means. A Metric moved, and by how much. A Profile turned something up. A Release changes something for you. A Public Domain has new figures.

Nobody writes Stories. Futuremodel reads them from what changed, and you only ever see Stories about things you're allowed to see.

They show up on your home page. The Digest sends you the same list, daily or weekly, and stays quiet when nothing's changed.

A home page listing five Stories: two from a Public Domain the reader follows, and three from an example Organization they work in.
Homewhat happened

Public what you follow

  • Shooting IncidentCitizen · Mass Shootings

    New figures: 4 Shooting Incidents are dated 2026, with 13 fatalities. The latest is 15 October, in Bend, Oregon.

  • Shooting locationCitizen · Mass Shootings

    A Profile found 36 of 162 with no value recorded. They won't show on a map until someone records where.

Acme an example Organization

  • Total RevenueAcme · Commerce

    Up 6% on last week. It's the sum of Order revenue where status is paid.

  • Release 13Acme · Commerce

    Changes Total Revenue, which you follow: refunded Orders are now left out.

  • Paying CustomerAcme · Commerce

    Your Question has an accepted Answer, and it's now the definition.

Two ways in

The world's facts and your organization's, on one home page.

  • The Citizen Experience

    You don't need an Organization behind you, or a Role from anyone. Read what Organizations have made Public, follow what you care about, and hear about it when something changes.

    Explore a Public Domain
  • The Enterprise Experience

    This is Futuremodel at work, through the Roles you hold there: your organization's Private and Internal Domains, its Sources, its Questions and its Releases, with what's been happening on your home page.

    Request Access

And they meet in the middle. Import a Public Entity into your own Domain, pinned to a Release, and read your own Individuals alongside the public record. You can have both at once, on the same home page.

Why you can trust it

Careful about what it tells you.

  • It tells you what it left out.

    A missing value is unknown. It isn't equal to anything, or unequal either. Counts cover what's known and tell you how many they couldn't include.

  • Same answer on every warehouse.

    No engine gets to be the reference. The query generated for each one smooths out the differences.

    See how: Same answer on every warehouse.
  • Nothing live changes by accident.

    Every edit is saved as a Version. What's live is a Release, and it stays put until you cut the next one.

    See how: Nothing live changes by accident.
  • AI drafts. People publish.

    The Assistant answers from what things mean and how many there are. It never sees a row.

    See how: AI drafts. People publish.
  • Everyone knows who decides.

    Stewards shape a Domain and Governors speak for the Organization. A Role only reaches as far as the thing it was granted on.

    See how: Everyone knows who decides.

Start with one thing you want to know.

Have a look around what's Public right now, or request access and bring your first table. We'll email you as soon as you're in.