This is Joris&.
Builder. Complex care navigator 🇳🇱/🇬🇧. Independent researcher. I build accessibility tools from lived necessity — Piktoa first — and study how people take in load, process it, and produce output when the systems around them weren't built for how they run.
The kernel
Standard systems are built for one kind of machine. Most of us are running different hardware entirely — spending enormous energy compensating for the mismatch.
Move the load. Change the context. Watch the same architecture produce a completely different result — this is the whole framework in one motion.
"Not a diagnosis. A map."
The signature
Every system has a signature — a particular shape to how it takes input, processes it, and produces output. Mine has one shape. The people I build with have others. Social media flattens us all onto one feed, competing on one popularity algorithm. But complementary signatures don't compete. They compose.
My instruments + Daan's platforms + Noom's eye for pattern = something none of us builds alone.
This page is a node in that web. Not a profile competing for attention — a place where complementary signatures connect: the substrate that scales, the instrument that fits the human, the second perspective that catches what one cognitive profile misses. A different formula in each of us, composed into a stronger whole. That is the new algorithm.
The islands
This is a place to wander, not a profile to scroll. Each island is its own room — the work, the thinking, the life, the people I build with. Different formulas, composed into a whole.
More islands are coming — the people I build with, each with their own. Daan's platform work, and Project Aluna with Noom: parallel lives, a slightly different formula in each.
The architecture
Three core layers run the sequence — input, processing, output. Four contextual layers bend it: how much can be held, how much capacity is available, what happens at overload, and how it recovers. The same architecture, under different load and context, produces a completely different result. Select any layer to go deeper. Read the full framework →
The signal intake layer. How information enters the system before any processing begins — sensory load, attention routing, environmental demands. Differences in input filtering explain why the same room feels quiet to one person and overwhelming to another. Most accessibility failures happen at this layer before anyone notices anything is wrong.
The pattern recognition layer. How the system parses what it's received — making associations, building models, separating signal from noise. Processing differences explain why some minds need to talk to think, and others need silence. It's not a deficit; it's an architecture — and environments that require one processing style universally exclude the other.
The working store. What the system holds in active attention while doing something else with it. Buffer capacity determines how many threads can run simultaneously before something drops. It's why interruption costs vary so dramatically between people — and why some environments are structurally hostile to certain architectures without anyone designing it that way.
The current capacity layer. Not a fixed attribute — a dynamic state. Load, context, recovery deficit, and activation threshold all modify what's available in any given moment. The same architecture reads entirely differently at 30% load versus 90%. The bandwidth essay is the theoretical core of the framework and probably where most people recognise themselves first.
The expression layer. How the system sends information back out — writing, speech, decision-making, action. Output bottlenecks are routinely misread as reluctance, inability, or low motivation. Usually they're a bandwidth problem or a processing delay, not a delivery failure. Fixing output means diagnosing the upstream layer, not the output itself — which is why most interventions at this layer don't work.
The protective collapse layer. When the system exhausts its reserves, non-essential processes go offline — Skeleton Mode. Not a choice. A hardware response. The layer is named for what the system is doing, not what the person failed to do. This distinction is the ethical core of the entire framework. Most burnout interventions fail because they're addressed to the wrong level of the stack.
The recovery path. What it takes to rebuild from Skeleton Mode back to functional capacity. Reboot requirements are specific — and usually invisible to observers. Most recovery interventions fail because they're calibrated for the wrong OS. The reboot layer is where most institutional care frameworks have their largest blind spot: they know how to treat the collapse, but not how to support the particular rebuild.
The misreads
Institutions read outputs without seeing the architecture underneath. The same five mistakes repeat — in schools, clinics, workplaces, and care systems:
Each misread adds input exactly when the system is already signalling overload. The repair runs the other way: change the system before asking the person to adapt again. That principle is the consulting practice — Joris&.
Diagnostic instruments
You don't pass or fail. Each instrument captures how your cognitive architecture actually behaves — not how you describe it. Your activation threshold, how your working store degrades under load, how you hold reserve when capacity drops. The pattern surfaces from how you play, not what you report about yourself.
A Tetris-variant under load. Help quietly drops away as the game accelerates — the instrument reads how your play holds up through the loss, and whether it re-stabilises after. Nothing to declare; it only watches how you play.
A classic puzzle with a complete move log underneath. Every fill, error, pause and undo is recorded — the read is how you scan the board, when you slip from row-work into block-work, and where errors cluster as load builds. The first instrument in the suite with a completed triangulation: the behavioural log independently confirmed two self-reported hypotheses.
A merge game with a fixed move budget. Do you act as items arrive, or let them accumulate and clear in batches? The read is where your own threshold sits — not whether it's the right one.
A sequence lights up; you tap it back. It grows until it doesn't. The read is how much your working store holds and how it lets go — measured only against your own earlier runs, never against anyone else.
Single-player narrative across four territories. No self-report. Your cognitive signature surfaces from how you move through the world — not what you say about yourself. The deepest read in the suite.
Products & projects
Writing & essays
“The problem isn't effort. It's running too many processes at once — then calling the lag laziness.”
“Twenty-two thousand lines of code. Built solo. The AI was scaffolding. The architecture was mine.”
“The handoff fails not from negligence — but because the system was designed for a different patient than the one in the bed.”
“Your operating system isn't broken. It was just never documented.”
Training & credentials
Get in touch
I consult on the places systems fail the people using them — healthcare processes, accessible communication, GDPR compliance. Mostly care organisations, special education, and healthcare. Based in Tilburg, working internationally.
Find me elsewhere
