AirPort by Lupo IO

Remember what matters.

AirPort, by Lupo IO, a living memory substrate. Observations are read once, meaning is extracted onto one shared timeline, and the raw leaves the working path. What persists is meaning: with lineage, with evidence, with outcomes.

Billions
observations read
40
live data sources
23 years
of history
Seconds
to answer anything
One
shared timeline
never stops learning
Substrate · Livelupo://core

A new substrate

AI was built for tomorrow. Your data stack was built twenty years ago.

Traditional databases were designed for people running queries. Modern AI systems require continuously evolving, connected intelligence operating at machine speed.

Lupo transforms raw information into a living substrate of relationships, memory, and meaning, continuously organizing the world's information as it changes.

Every analytical system on Earth does the same thing with data: compute an insight, use it, throw it away, and compute it again tomorrow. The world re-derives the same understanding millions of times a day, forever. AirPort inverts this: the expensive reading happens once; what's stored is the meaning, permanent, typed, time-anchored objects, and the raw bytes leave the working path.

01

Continuously ingest

Photographs, headlines, sensor readings, filings, market events, conversations, all landing on one shared timeline.

five streams · one point of meaning
02

Continuously understand

The expensive reading happens once. Observations are read, typed, and connected. What's stored is the meaning.

nowregularvolume-surge3 observations, one meaning
03

Continuously optimize

The most valuable meaning stays close to compute. Evidence rests in the basement, reachable but never re-read.

surfaced by value

Proof

History once. Every day forever.

Overnight, AirPort read 23 years of the entire US equity market — 12,000+ companies, every exchange and dark pool, billions of observations — and distilled it into a permanent memory of what mattered. Zero failed days. And it no longer stops at markets: 40 live data sources now share one timeline — news, filings, satellites, shipping, prediction markets, the physical world itself — kept current in minutes a day, unattended. Ask it anything; answers come back in seconds.

Substrate · Liveairport://timeline · AAPL · 2024-06-11
04:00
pre-marketvolume-surgefar beyond normal (peak 112k)
09:31
regulartrendsustained climb begins
11:04
headlinestory'Is It Too Late to Buy…' , The Motley Fool
13:30
regularvolume-surgeescalating
14:16
regularvolume-surgethe loudest of the day
attributes: { intensity: extreme, session: regular } · lineage: { source, ticker: AAPL, day: 2024-06-11 }
15:26
headlinestory'7 Analysts Mixed on WWDC…'
16:06
after-hoursregimehigh-volatility
ex-dividendnone · clean
Reconstruction · AAPL · June 11 2024five layers · one clock
MON 18:00TUE 04:0009:3012:0016:00
NEWS
18:02MONkeynotekeynote lands · −2% · 'sell the news'
02:18TUEnarrativeflips, 'Apple Intelligence'
12:30headlinestory'Bet on Apple Intelligence?'
15:06headlinestory'Apple Stock Is Surging'
17:35headlinestory'Record Highs'
PRICE
04:00pre-marketsurgeloud
13:30regularsurge
14:16regularsurgeloudest
15:32regularsurge
16:00regularclose+7% intraday
OPTIONS
09:30regularcontracts4.4M · 2:1 calls
FUTURES
03:00regimeflat overnight
CORP-ACTIONS
ex-dividendnone · clean

Five layers. One clock. One question, what happened?, answered from stored meaning. Any name, any day.

All the way down

A satellite pixel, followed down to the coordinate.

Every day, the same thermal satellites that spot wildfires pass overhead and measure the temperature of the ground, reporting anywhere running unusually hot. On their own, those readings are anonymous: a location in southern Taiwan is hotter than expected. Nothing more.

We make it mean something. We match every thermal reading against the known location of every fab. An anonymous hotspot becomes a dated event at a specific maker's facility. The satellite tells us where the heat is; our map tells us whose it is.

That match doesn't become another alert. It becomes a span, the system's atomic unit of memory: a small, dated, self-describing fact about something that happened, at a precise moment, to a specific entity. And the instant it exists, it stops being alone and starts connecting.

It connects to the maker's own story. The heat event now sits on one timeline beside that company's trading, its shipments, the chemicals moving through customs, its news. So we can ask, immediately: did volume move? did options flow shift? did headlines turn? Because they're all just spans on the same clock, under the same identity.

It reaches through the supply chain: we follow it down to the firms whose products depend on that fab, and up to the suppliers feeding it. One hot pixel can light a whole web of related names. We even watch customs for the specialist chemicals moving in, an independent read on whether a fab is genuinely running or genuinely stopped.

And it correlates with everything else happening at that instant: news, conversation, prediction markets, weather, earthquakes. A tremor near one plant is never judged alone; it's weighed against whether the market was already nervous, whether several fabs were hit at once, whether customs had already begun to slow. That's how the system tells a one-off headline from a building risk.

From orbit to a base rateairport://descent · 2026-07-07
01
Observe
02:14Z
thermalhotspotsurface anomaly · +6°C over baseline
02
Identify
02:14Z
spanfab-thermalmatched to an advanced-chip fab · Taiwan
attributes: { intensity: elevated, source: thermal-sat } · lineage: { site, region: TW, day: 2026-07-07 }
03
Connect
marketco-locatedlands beside the maker's trading, shipments, customs & news
supplydownstream→ the device makers whose products depend on this fab
supplyupstream← the wafer, gas & equipment suppliers feeding it
customsinflowspecialist-chemical shipments, an independent “still running?” read
04
Correlate
contextcross-checknews · prediction markets · seismic · weather, same clock
one-off blip, or a building supply risk?
05
Remember

Given only what was knowable that day, how often did disruptions like this actually matter, and for whom?

Point-in-time frozen · no backfillOccurrences 38Status base rate · continuously refined

a satellite pixel, followed all the way down to a base rate · same object, one clock

Then the part that matters most. Every span is frozen at the moment it was knowable, never rewritten, never backfilled with what only became clear later. So history can be replayed honestly. A hotspot from three years ago reconstructs exactly what someone watching that day would have seen: the heat, the news then available, the prices then, the shipments then, and only after that does history roll forward to reveal what actually came next.

Most systems quietly let the future leak into the past, analysing yesterday with knowledge nobody had yesterday. This one never does. So instead of "what happened after fabs overheated?" we can ask the honest question: "given only what was knowable that day, how often did disruptions like this actually matter, and for whom?"

That turns a single hot pixel into a base rate. Not a story, evidence. And every new event adds one more honest piece to it.

every source earns its weight

We don't throw doubtful data away.

Not every source is equally reliable, and reliability isn't fixed. A wire report, a regulator's filing, a prediction market, an anonymous post: each speaks with a different authority, and each has a track record.

Most systems handle this crudely. They set a bar and discard whatever falls below it, and in doing so they throw away the very thing that's often most telling: what people believed before anyone knew better.

We don't dismiss data for being low quality, or for coming from a source that isn't always right. We keep it, and we downgrade its weight. Every source carries a trust score, not a single number but two: a baseline for how reliable it usually is, and a spread for how much that varies. A well-earned source counts heavily. A doubtful one still counts, just lightly, and honestly labelled as what it is.

And the score is alive. As a source is proved right or wrong over time, its weight rises and falls with its record. A market that keeps calling outcomes correctly earns more trust; a voice that keeps overreaching loses it. Nothing is frozen, and nothing is hidden.

It can move up, not only down. A doubtful source that keeps being right sees its score rise as its record improves. A trusted source that suddenly contradicts the facts is marked down the same day. Every trust reading is point-in-time: truthful at one moment, false at another, then revised the moment more is discovered.

That's the whole discipline in a phrase: a lens, never a filter. A low-trust claim isn't deleted, it's dimmed. Ask a careful question and it barely registers. Ask "what did people believe at the time?" and it's right there, exactly as loud as it deserves to be.

Because the honest record isn't only what turned out to be true. It's also what everyone thought was true, and how much you should have trusted them.

Substrate · Liveairport://trust · grain-of-salt
0.90
FILINGprimary-sourceon the record, first-hand
0.90 ±0.03
0.78
MARKETprediction-marketprices belief, then settles vs reality
0.78 ±0.06
0.72 → 0.78 ↑ · earned
0.64
NEWSwire-reportreported, not yet confirmed
0.64 ±0.10
0.28
SOCIALanonymous-postunverified · a single voice
0.28 ±0.15
KEPT
attributes: { trust: 0.28, spread: 0.15, retained: true } · policy: lens-not-filter
what people believed

Nothing is discarded. A doubtful source is kept as exactly that, what someone believed at the time, and weighted accordingly.

Lens not a filterScale 0.0–1.0 · baseline ± spreadStatus reweighted from track record · point-in-time

nothing discarded · every voice weighted by its record · a lens, never a filter

One day rebuilt · one signal followed down · every source weighed, the same object, on one clock, kept honest

Meaning has structure

Every observation is transformed into semantic memory that can be inspected, connected and learned from.

The idea · illustrative
illustrative.json
{
  "event": {
    "source": "WSJ",
    "speaker": "Elon Musk",
    "sentiment": "negative"
  },
  "market_state": {
    "asset": "TSLA",
    "price_move_pct": -4.2,
    "volume_multiple": 3.1
  },
  "context": { "vix_regime": "elevated" },
  "semantic_markup": [
    "negative_executive_commentary",
    "high_volatility_regime",
    "selling_pressure_detected"
  ]
}

One observation, made machine-readable: who said what, what the market did, and what it meant.

The real thing · from the store
from_the_store.json
{
  "tag": "volume-spike",
  "subject": "NVDA",
  "attributes": {
    "intensity": "extreme outlier",
    "peak_volume": 207508,
    "session": "pre-market",
    "policy": "ep1"
  },
  "lineage": {
    "source": "market-tape",
    "ticker": "NVDA",
    "day": "2026-07-07"
  }
}

An actual object from a store holding 176 million of these. Every span carries its evidence, its policy, and its lineage, and traces back to the raw facts it came from.

the left is what any observation becomes · the right is proof it already happens, at scale

Trust, remembered

Every source earns its weight.

Not every voice is equally reliable, and reliability changes. Each source carries a trust weight that rises and falls with its track record, a lens, never a filter. Nothing is thrown away: a doubtful claim is kept as exactly that, what someone believed at the time, weighed accordingly. The record stays honest in both directions.

The layered web · LiveL0 → L3
L0
Raw observations
L1
Semantic objects & outcomes
REGULARprice drop
REGULARvolume spike
NEWSsentiment: negative
FILINGguidance revision
L2
Relationships
co-movement — beats chance
commentary amplified decline
news increased impact
L3
Knowledge

Negative commentary during elevated volatility frequently precedes multi-day weakness.

Confidence 0.84Occurrences 143Last observed 2d agoStatus continuously refined

The layered web

A substrate, not a model.

Small observations combine into relationships. Relationships combine into structure. Structure recursively refines itself.

What persists is meaning: with lineage, with outcome, with memory.

Some observations are forecasts. Prediction markets price what a crowd believes will happen, and the substrate remembers the belief, the outcome, and how often the crowd was right.

  • Recursive knowledge structures
  • Semantic relationship modelling
  • Continuous outcome learning
  • Adaptive memory substrate
  • Explainable reasoning paths
  • Inspectable lineage
  • Probabilistic inference
  • Self-refining memory
  • Base-rate discipline, relationships must beat chance to exist

Example memory map

Many observations. One durable memory.

A trace of how market data, news, filings, transcripts, social activity and other observations become semantic objects, relationships, outcomes and finally reusable intelligence.

Memory map · TSLA · 2024-Q2observation → knowledge
MONTUEWEDTHUFRI
MARKET DATA
regularprice-drop−4.2%
regularvolume-spike3.1×
regularregime-shiftvolatility up
NEWS
headlinestoryReuters publishes
headlinecommentarynegative Musk quote
headlineanalystdowngrade
FILINGS
regular8-Kfiled
regularguidancerevised down
TRANSCRIPTS
regularcallproduction outlook lowered
regularCEO'demand softness'
regularcallmargin pressure
SOCIAL
regularretailvolume surges
regularinfluencercommentary spreads
regularsentimentturns negative
02 · Semantic objects
Musk commentarySentiment: negativeGuidance revisionVolume anomalyVolatility anomalyDemand weaknessMargin concernLiquidity stressSocial sentiment deterioration
03 · Relationship objects
relationshipNegative commentary increased downside risk
relationshipGuidance reduction amplified weakness
relationshipVolume confirmed market conviction
relationshipWeak demand met volatility expansion
relationshipSocial sentiment reinforced narrative
04 · Outcomes
regularoutcomeTSLA closed −4.2% on 3.1× volume
regularoutcomeVolatility regime extended
regularoutcomeMulti-day drawdown initiated
regularoutcomeInstitutional selling accelerated
05 · Higher-order knowledge

Negative management commentary combined with elevated volatility, weakening guidance and deteriorating sentiment frequently precedes multi-day weakness.

Confidence 0.79Occurrences 212Last observed 4d agoStatus continuously refined

future observations refine existing memory

Applications

Wherever complex systems generate data.

01

Financial Markets

regime detection · narrative shifts

Every tick, headline, filing, and option print across entire markets, distilled into permanent memory. Hand it any name and any day; it reassembles what happened — the news, the trading, the positioning, the aftermath — from stored meaning, in seconds. Feed it ten years or thirty; it reads once and remembers.

✓ Proven at market scale · live
02

Legal

evidence · testimony · citations · outcomes · one memory

Law runs on a torrent of timestamped evidence — dockets, opinions, depositions, exhibits, clauses, and the news and filings around them. The connections are the value: precedent flowing through citation networks, doctrines and templates forming families, matters unfolding as sequences with recorded outcomes, all on the same clock as the market's reaction. Same machinery as markets; only the vocabulary changes.

Read the field guide →
03

Government & Regulatory

where every domain collides

Regulation is sprawling and it touches everything. A rule like Volcker is statute, rulemaking, compliance metrics, and live trading data at once — today scattered across departments that don't share a clock. On one timeline, the regulation connects directly to the behavior it governs: the rule, the debate that shaped it, the filings it demands, and the market data that proves compliance — one memory.

04

Agriculture

predictive to be protective

Soil probes, weather stations, satellite passes — millions of readings a season, mostly glanced at once and discarded. On one timeline, a dry-warm signature in block 7 matches the pattern that preceded the last two fungal outbreaks — eleven days before visible damage. Flagged in time to act. Nothing predicted for profit; something protected.

05

Logistics & Supply Chain

the physical chain, remembered

A delivery truck photographed at the same dock every Tuesday. One photo is nothing. Joined to delivery scans, inventory levels, and weather, the memory notices Tuesday runs late whenever a specific upstream hub had weekend backlog. Nobody asked; the substrate connected it.

06

Healthcare

longitudinal patient memory

A decade of one patient — every lab value, prescription, symptom note, wearable reading — on one timeline. The memory notices the fatigue reports always follow two weeks after a medication change, across visits, across doctors who each saw only one slice.

07

Industrial Systems

anomaly · failure topology

A pump's vibration ticks slightly odd — below every alert threshold. On the timeline, the same signature preceded two failures at sister plants, both about eleven days out. And the memory is honest the other way too: it records which warning signs never led to anything.

08

Scientific Research

discovery from sparse signal

Every experiment on one timeline — including the failed ones, recorded as first-class knowledge. The lab stops re-running dead hypotheses, and negative results stop vanishing into drawers.

09

Insurance & Claims

evidence with lineage

Photos, adjuster notes, weather data, repair invoices — one claim's whole life on a timeline. A thousand claims reveal which patterns are genuine and which body shops bill triple after hailstorms.

10

Sensor Networks

high-frequency event memory

Millions of readings a day, meaning extracted once, raw flushed. What persists: the events that mattered, the patterns that repeat, and an honest record of the alarms that never came true.

The principle

Store the surprising. Compute the routine. Record the outcomes.

Placement

Placement decided by value, not recency.

Memory has economics. In a GPU-accelerated world, the scarcest real estate is the fastest tier. AirPort's control plane treats data placement as an economic decision: the most valuable meaning lives closest to compute; evidence rests in the basement, reachable, never re-read.

insighthot
outcomewarm
relationshipcool
semanticcold
rawbasement
the most valuable meaning lives closest to compute

The physical world

Your product, in the real world.

Customers and teams can feed in photographs, social posts, store shots and field notes from Instagram, TikTok or anywhere else. Lupo connects that real-world feedback to your product, campaign, inventory and sales data, so you can follow a product from creation to purchase to use, and continuously improve it. The same kind of object holds at any scale, from a single photograph to undersea cables, shipping chokepoints and factory floors.

01 · Observe
Black rideshare outside a restaurant in Amsterdam canal district at dusk
OBS · Raw inputLive
UberVehicleAmsterdamCanal DistrictEvening19:06
02 · Understand
Extracted entities
PLACEAmsterdamPLACECanal DistrictENTITYUberENTITYVehicleCONTEXTEveningTIME19:06
Inferred concepts
  • User travelling
  • Transportation event
  • Evening arrival
  • Urban mobility context
Relationships
CustomerusesUber
Observationoccurred inAmsterdam
CustomervisitedRestaurant District
03 · Remember
Evening Mobility Pattern

Users frequently use rideshare services following social or dining activities.

Confidence 92%
Brand Engagement

Uber observed across 12 independent interactions over 4 months.

Confidence 87%
Location Behaviour

High rideshare activity within central Amsterdam entertainment districts.

Confidence 84%
Preference

Strong preference for rideshare over public transportation.

Confidence 89%
Input types
01
Campaign photographs
02
User-generated content
03
Product photography
04
Field observations
05
Voice & video
06
Purchase signals

a photograph, a headline, a sensor reading, and a market event · the same kind of object here

Beyond the data stack

The world itself can become intelligence.

Lupo continuously transforms observations from the physical world into connected memory, relationships and understanding.

Photographs, conversations, documents, locations, movement, sensor readings and human experiences can all become part of a continuously evolving substrate of intelligence.

About

We are not building software. We are building a living memory system.

Lupo IO is a small team of researchers and engineers working on a fundamentally different way to handle data: as memory, not as records.

Our work sits at the intersection of semantic reasoning, recursive memory and explainable inference. The system never finishes learning.