CDS LabsConcept-Driven Systems
⊡Object▷Property≎Time-Space[S]State⊙Action⫐Means[E]Event
Concept-Driven Systems Labs · the third path in AI

Human intelligence is gained from events, not text.

Frontier models learn from millions of texts. We train AI on users’ actions in millions of apps and systems, in the concepts people understand.

ONE EVENT⊙ WASH ⊡ CLOTHES ▷ WOOL  [S] DIRTY → [S] CLEAN
How · from wash to ontology

One function, modelled close to the world, grows into a reasoning engine

Today’s interfaces and APIs are built around device parameters. A washer receives three numbers, while the person knows what the sweater is, what state it is in and why heat is a risk. CDS keeps that understanding in the system, in seven shared ontological categories, and records every action as an event.

⊙Wash ▷white wool ⊡clothes ⫐at 40 °C, gently, ≎in 60 minutes.
⊡
Object
What exists and can change
CLOTHES · WASHER
▷
Property
What an object is like
WOOL · WHITE
≎
Time-Space
When and where
60 min · in the drum
[S]
State
Properties at one moment
DIRTY → CLEAN
⊙
Action
What is done
WASH
⫐
Means
How it is done
40 °C · GENTLE
[E]
Event
A change, registered
this wash, recorded
One function

A sentence becomes concepts

Every word of a request takes its place in the seven categories. Before, action and after form one event record.

One space

The functional space of P-Washer

Wash, rinse, dry and clean share objects, means and properties. The space checks coherence and bounds meaning.

“wash the wool at 60 °C” → refused
offered: 40 °C · GENTLE
Many spaces

Phone, car, company systems

Every action, in every space, is recorded as an event in the same categories.

Reasoning engine

Organic ontology

Concepts linked by real events. It predicts, carries knowledge across spaces and composes what was never seen.

EVENTS FROM MANY SPACESP-Washerwash · rinse · dryP-Phonecall · send · openP-Cardrive · park · heatCompany systemsissue · claim · payORGANIC ONTOLOGYlearned from many washesphone + glass: never seen together, composed from properties⊡CLOTHES▷WOOL⫐HEAT[S]SHRUNK⊙DRY⊙WASH⊡JACKET⊡CAR⊡POLICY⊡PHONE▷HARD⊙STRIKE⊡GLASS[S]BROKEN
Organic, because it is grown from events. The categories stay fixed and shared; the links between concepts strengthen with every recorded event. Heat and shrinking are linked because many washes recorded it. A hard phone and brittle glass were never seen together, yet their properties compose into an answer.
The product · P-Suite

P-Suite carries a request through the concepts to the device, and brings back what happened

The device API becomes an expression of the concepts, not a replacement for them. Four components close the loop.

Any inputvoicetexttouchgesturetelemetrysystem calls
Understands
P-Modeler

Turns signs in any language into conceptual structure. Language stays at the edge.

“wypierz ubrania” ≍ “wash the clothes”
→ ⊙ WASH ⊡ CLOTHES
Fits
P-Designer

Matches the request to this device’s functional space and checks it before anything runs.

⊡ CLOTHES ▷ WOOL ⫐ 60 °C
→ incoherent → ⫐ 40 °C
Runs
P-Executor

Calls the device or system API under an active functional space, deterministically.

FS:F:A:E → washer.start(40, gentle, 60)
Observes
P-Instantiator

Records what actually happened as an event in the same categories.

[S] DIRTY → [S] CLEAN · WET
[E] recorded
[E]

What was meant and what happened are kept together in one event record. The difference between them is what the organic ontology learns from.

PrototypesP-WasherP-PhoneP-CarCS-MCP · CDS-MCP servers
What it brings

A conceptual layer between people, AI and every system they use

Once actions are modelled as concepts and recorded as events, the same layer serves as ontology, middleware and interface, and becomes training data for AI that learns from what people do.

⊡Ontology

Organic ontologies

Seven fixed categories, with links grown from real events. Each company’s functional spaces form a private ontology; together they converge toward a universal one.

▷ WOOL + ⊙ DRY → [S] SHRUNK
warned from experience
⇄Universal API

Middleware for every system

Conceptual structure sits between every input and every system. One coherent, event-based API across a company’s landscape, with canonical addresses for every event.

policy · claim · payment
→ one event API, one model
⫐Multimodal

Any input, one meaning

Voice, text, touch, gesture and telemetry compile into the same structure, so interfaces can change without changing what the system understands. P-Phone is built with blind users in mind.

speech ≍ tap ≍ sensor
→ ⊙ SEND ⊡ MESSAGE
[S]Verified behaviour

Systems that can be proved

Conceptual State Machines are deterministic. Forbidden states are shown unreachable before release, and every decision reproduces exactly for audit.

δ(state, action, object, context) → state′
forbidden state: unreachable
≍Interoperability

Private ontologies that agree

No party exposes its data model. Shared categories and event addresses make an insurer, a carmaker and a city mutually interpretable, without one vendor owning the schema.

vehicle ⟷ grid ⟷ city ⟷ insurer
composed on shared events
⊙Toward AGI

Common sense from events

A third path beyond symbolic AI and LLM scaling: reasoning on concepts grounded in what actions do, so knowledge transfers between spaces and composes the unseen.

⊙ BREAK ⊡ WINDOW ▷ BRITTLE ⫐ PHONE ▷ HARD
→ [S] BROKEN · never seen, composed
First marketInsuranceAn event API over policy, claims and billing systems.
MobilityVehicles and smart citiesSoftware-defined vehicles and city systems agreeing on events.
DevicesAppliances and accessibilityWashers, phones and cars that understand what people mean.
Dual useDefence interoperabilitySystems of systems with verified, reproducible behaviour.

We train AI on what people do, in the concepts they understand.