← LeResearch
Philosophy · living documentdeveloping

The thesis, the observations, and the tension at the center of the work.

This page is the substantive half of LeResearch — the one that doesn't fit in a proposal form. It explains why we exist as a distinct entity from a commercial LLC, what we refuse to treat as settled, what we are willing to build anyway, and which diagrams help when the language stops pulling its weight.

It is a living document. It will change. If it stops changing, something is wrong — either with the org or with how we are listening to the work.

§0

The thesis, in one paragraph

The of learning and professional work has always been the constraint — not human intelligence, not the availability of knowledge, not effort. For most of history the best frontends we had — the teacher, the lecture, the textbook, the specialized software package — were fixed, one-to-many, non-adaptive, and jargon-gated. Some people fit through the filter and we called them talented. Most did not, and we either blamed them or forgot them. Large language models together with modern interactive interfaces are the first serious plural, adaptive, multimodal frontends the species has ever had access to.

LeDesign was built to ship those frontends commercially, in fields where proprietary have been pricing people out of their own tools. LeResearch is the other half: the research that asks whether the reframing holds under evidence, across domains where no product roadmap would fund the work — and refuses to treat the as settled just because the frame is what everyone already agrees on.

§1

Capacity is environmental, and the frontend has always been part of it

Sapolsky's work on behavior, biology, and environment lands on one conclusion we cannot step past: human capacity is not fixed at birth. It is shaped continuously by the environment it encounters — and that environment includes every frontend through which knowledge is offered. What we call smartness is downstream of who happened to fit the particular filter a given society built at a given time, using a given paradigm, for a given distribution of people.

Post-industrial schooling built one linear frontend. A teacher at the front, a classroom in rows, a single pace, a single vocabulary, a single language, a single canonical text. Students who fit the filter were called able. Students who did not were called unmotivated, slow, or worse — and most importantly, came to believe the framing about themselves. The filter defined who was smart. The smart ones were permitted to define the filter. The people outside that loop were not less able; they were differently served by a frontend designed for a mean that never existed, enforced as if it were physics.

The filter that failed vs the frontend that fits
LINEAR FRONTENDone-to-many · fixed · gatedESENENESENESEN · adult · textthe one shape that "works"CONTENT(reached by one)others "couldn't understand"The filter defined who was smart. The smart ones defined the filter.PLURAL FRONTENDlearner chooses depth · language · modalityES·CEN·TEN·AES·AEN·EES·Tdepth × language × modalitycomposed per learnerSAME CONTENTreached by all sixalong different pathsThe learner defines the frontend. The distribution of who understands shifts.◇ visual ○ narrative □ text △ audio
Same six people. On the left, a single linear frontend — one language, one depth, one modality, one pace. The learners who happen to match the configured profile pass through; the others get classified as unable. On the right, a plural frontend — the learner picks the depth, the language, and the representation. Everyone reaches the same content, along different paths. The distribution of who understands the work changes with the frontend, not with who was born smart.

This lands as a moral claim, not just a factual one. If capacity is environmental, structural failure to provide the environment is a moral failure rather than an individual one. If the frontend is part of the environment — which it has always been — then the design of the frontend is a public-health question, a public-mind question, and only incidentally a UX question. Nobody gets to wash their hands of it by saying “we are just building software.”

§2

Inherited frames calcify as infrastructure

Eight glasses of water a day. Two thousand calories. Three meals on a schedule set by industrial factory shifts. Eight hours of sleep. The nine-to-five workday. The classroom itself. Each of these was a specific decision by specific people for specific reasons, most of which had nothing to do with what the human body or mind actually needed. And yet they are absorbed, operationally, as truths — as infrastructure, the same way gravity is infrastructure.

Infrastructure, or decisions nobody remembers making?
THE "TRUTH"HOW IT ACTUALLY GOT THEREWHAT THE EVIDENCE SAYS8glasses of water / day1945misread 1945 FNB note: "1 mL per calorie of food intake" — the original line said most of the water comes from foodFAILS ↓Individual needs vary ~1–3 L; no evidence supports a universal "8 × 8"2,000daily calorie target1993FDA food-label rounding, 1993 Nutrition Labeling and Education ActFAILS ↓Highly individual — varies with age, sex, build, activity, season3meals / day, fixed schedule~185019th-century industrial shift structure — breakfast / lunch / dinner synchronized to factory bellsFAILS ↓Pre-industrial societies used 2 or 5; satiety signalling is not clock-driven8hours of sleep / night, continuous~1800industrial-era consolidation of historically-segmented sleep ("first sleep" + "second sleep")FAILS ↓Individual needs 6–10 h; segmented sleep is the historical norm9–5workday, Mon–Fri1914Ford Motor Company 8-hour day (1914) + mid-20th-century office-work conventionFAILS ↓Cognitive productivity does not map uniformly to clock hours30students per classroom, age-graded~185019th-century Prussian + industrial-US compulsory-education model: one teacher, age-sorted rows, 50-minute periodsFAILS ↓Nothing about learning requires uniform age-cohorts, ratio, or period lengthThe filter hardens into infrastructure. Infrastructure stops being questioned."Common sense" is often a contingent decision that survived long enough to be mistaken for gravity.
Every row is a number most adults treat as physics. Every row was a specific decision by specific people for specific reasons — most of which had nothing to do with what the human body or mind actually needed. The numbers are not uniformly wrong; some are approximately right for some people some of the time. The point is not the specific number. The point is that a contingent frame is being accepted as a natural law by people who would, in other contexts, be the first to ask to see the evidence.

Very few of them survive contact with the evidence. They are not uniformly wrong; some are approximately right for some people some of the time. The point is not the specific number. The point is that a contingent frame is being accepted as a natural law by people who would, in other contexts, be the first to insist on seeing the evidence.

§3

The normalization gradient — why slow change is invisible and fast change is shock

Section 2 named the outcome — that contingent decisions calcify into infrastructure. This section names the mechanism: the same biological and cognitive normalization that makes humans adaptable to almost any environment also makes change at low gradient invisible to us, and reserves our awareness for change steep enough to fire many sensors at once.

The species-level argument is straightforward. The same body and brain that allowed humans to inhabit the Arctic and the equator, the savanna and the city, did so by continuously recalibrating what counts as normal. A fixed reference for normal would have killed the lineage. A drifting reference, retuned to whatever is most recently present, kept it alive. The cost of that adaptation is not metaphorical: things that move slowly enough do not register as change. They register as the world.

The implication for inherited systems — the imagined orders, in the anthropological sense, that humans started building once group sizes exceeded what direct social cognition could hold (roughly Dunbar's number) — is that slow drift gets absorbed into the frame without ever entering deliberation. A nine-to-five workday, a classroom of thirty students in rows, eight glasses of water a day: each of these started as a gradient steep enough to be visible (a labor strike, a Prussian school decree, a magazine column), and each ended as something nobody remembers having decided. The shock made them legible. The normalization made them invisible.

The normalization gradient — slow change is invisible; fast change is shock
↑ magnitude of change197519851995200520152025time →PERCEPTION THRESHOLD← the threshold drifts to follow the new normalSLOW GRADIENTabsorbed as “the world” · no sensor firesarrives at magnitude 1050 years later · no public debate happenedFAST GRADIENTfires sensors · debate · regulationTHE POLITICAL ASYMMETRYSLOW — absorbs into infrastructure· recommender systems · 2008–2024· extension of workplace monitoring· contraction of professional judgment· eight-hour workday becoming "normal"FAST — produces a cohort moment· ChatGPT · Nov 2022· COVID lockdowns · March 2020· a labor strike· a Supreme Court rulingSame destination. Different slopes. Only one of them gets a public debate.
Two trajectories reach the same magnitude. The slow gradient drifts under the perception threshold, and the threshold itself drifts down to follow it — the shifting baseline made literal. The fast gradient blasts through, fires sensors, gets debate. Both arrive at the same destination. The political question is who chooses which slope a given change rides — because the same actor who would lose a fast public argument can usually win a slow private one.

The inverse case — the paradigm shift, in Kuhn's sense — is what happens when a change exceeds the normalization range fast enough that many sensors fire simultaneously. Body, society, ecosystem, market, institutional rule-set: all reading out of adjacent normality at once, with no available frame to absorb the input. That dissonance is what “feels like a paradigm shift.” It is also when public attention, regulation, journalism, and resistance briefly catch up to the change. Then normalization resumes, the frame absorbs the new state, and the cycle resets.

The political question — who steers the gradient — is not symmetric. The same actor who would lose a fast public argument can usually win a slow private one, because nobody is looking at the slope. A great deal of what shapes contemporary life — recommender systems sorting hiring, lending, news, dating; the steady extension of monitoring at work; the steady contraction of what counts as professional judgment — moved on a slope shallow enough to never trigger broad debate. The shock-and-normalize cycle is not just a description of how change happens. It is, increasingly, an instrument: a way of allocating which changes get democratic friction and which do not.

The intellectual lineage of this section sits across several traditions we have not yet developed in their own right — Castoriadis on the imaginary institution of society, Anderson on imagined communities, Searle on institutional facts, Berger & Luckmann on the social construction of reality, Bourdieu on doxa and habitus, Pauly on shifting baseline syndrome, Schmachtenberger on the metacrisis. Each is named in §12 with a one-line note on how we intend to take it up. This section will be revised as those threads develop.

§4

The word "AI" as a semantic black box

AI has broken the silos open. It is feasible for one person or a small team to produce the adaptive, multimodal, plural-by-construction frontends that an entire industry of proprietary software gatekeepers previously charged rent for. That observation is correct as far as it goes.

The companion observation we find less comfortable: the word AI has become analytically unusable in public discourse, precisely because everyone — the people selling it and the people rejecting it — benefits from keeping the category undifferentiated. On the hype side, AI is a unitary force with a runaway future, deserving massive capital on the theory that any piece of it might turn out to be the piece. On the refusal side, AI is a unitary threat that consumes water, replaces jobs, and steals public knowledge, deserving rejection as a category because decomposing it is work. Both positions avoid having to name what they actually mean, and the ambiguity serves both.

Seven things, all called "AI"
INSTANCECOMPUTESCALE (RELATIVE)OPENNESSFrontier foundation LLM (GPT-5, Claude, Gemini Ultra)trained for months across thousands of GPUs; what the water critique is actually aboutdata-centerxlclosedMid-size open LLM (Llama 3, Mistral Large)weights released; training cost still massive; inference on a single workstationclusterlpartialVision / multimodal model (CLIP, image-gen)image training sets carry decades of representational bias, calcified in pixel spaceclusterlpartialPhysics-informed neural net (our PI-GNN)millions of params; trains in hours; runs in watts; physics regularizer keeps it honestlaptopsopenClassical ML (random forest, gradient boost)existed for decades; unambiguously “AI” in the taxonomic sense; nobody panicslaptopsopenKriging (geostatistics, 1960s)the workhorse half of computational hydrology depends on; “AI” by the same taxonomylaptopxsopenThe marketing category (“AI-powered”)vibes; may be any or none of the above; sold by the labellaptopxspartial“We don't do AI” has no referent until a row is named.Most critique of AI is a critique of row 1. Most of LeResearch's work happens in rows 4 – 6.
Every row is called AI. They differ on every property that would matter for a rejection or an endorsement: compute scale, training environment, openness, water footprint, relationship to the public record, whose hands are on the governance. Refusing to decompose the category lets a blanket veto pass as a considered position — and lets a blanket enthusiasm pass as the same. Part of what LeResearch exists to do is build the vocabulary that separates a mathematical method from the business model currently monetizing it.

When someone says “we don't do AI,” the sentence has no referent until a specific row is named. The refusal to decompose is itself the governance pathology — it lets a blanket rejection pass as a considered position, and it lets a blanket enthusiasm pass as the same. Neither side has to do the work of distinguishing a mathematical method from the business model that happens to be monetizing it this year.

This is why the most common critique of AI — that it consumes water, that it is extractive, that it replaces labor — is mostly, in substance, a critique of bubble economics, not of the underlying mathematics. Compute intensity and ecological cost are overwhelmingly concentrated in training frontier foundation models at scale, because scale is what capital markets are pricing, not because the applications require it. Inference on a small, purpose-built, openly-licensed model on commodity hardware is measured in watts, not megawatt-hours. A physics-informed graph neural network for aquifer modeling is AI in the same taxonomic sense as a frontier LLM and has essentially none of the objectionable properties. The refusal to decompose collapses that distinction on purpose, because naming it would concede that work can be done without the business model attached.

LeResearch's existence presumes the distinction is real and operable. Our work happens in small teams, on open hardware at commodity price-points, with models small enough to run on a laptop, trained on openly-published data, under licenses that require outputs to be redistributable. This is AI in the taxonomic sense. It is not the thing the refusal is rejecting. But the dominant discourse has no vocabulary for the distinction, so work like ours sits in a semantic blind spot — present but unclassifiable — until someone builds the vocabulary that separates a mathematical method from the economic model currently monetizing it. Part of what LeResearch exists to do is build that vocabulary.

§5

AI and labor — applying the decomposition (the worked example)

§4 refused to let AI be a single thing. The same refusal applies to labor. The conventional question — “what jobs will AI replace?” — assumes the current job structure was natural, optimal, or inevitable, when it was none of these. The category of job in its modern sense (wage labor as identity, hours as contract, employer as primary social affiliation) is roughly two hundred years old. Before it: household economies, craft, subsistence, slavery, serfdom, indentured service, common land. The post-WWII professional middle class — the population that experiences “AI replacing my work” most acutely — is younger than penicillin.

Who got which job inside that arrangement was never a measurement of natural capacity. It was a function of race, gender, citizenship, language, schooling access, and whose children were allowed into which credential pipeline. The knowledge worker category that contemporary AI discourse most often centers — paralegal, junior copywriter, customer-service operator, illustrator, translator, programmer — is a particular layer of a particular society at a particular moment. AI does not disrupt the assignment. It operates through it.

When the joint decomposition is applied — which AI, which labor, at which gradient (in the sense of §3) — the picture stops being one story.

On the AI side
  • Recommender systems silently reorganized hiring, lending, sentencing, news distribution, and dating for roughly fifteen years. Pure low-gradient change: no shock, no public debate, no cohort moment. We normalized it.
  • Generative LLMs crossed the visibility threshold in late 2022 and produced a shock — not because they are more consequential than recommenders, but because they crossed into a sensor-firing range (visible output, in our language, in the chairs of the people who write the discourse).
  • Vision and biometric models are mostly in the silent regime, except where they hit a sensor (a face-recognition wrongful-arrest case, a targeting system named in court).
  • Robotics with embedded learning in warehouses, agriculture, and logistics is gradient-invisible to the professional class because it does not touch their work. It is conspicuously visible to the workers whose conditions it is reorganizing.
On the labor side
  • High-status knowledge work experiences compression as shock — visible, fast, named. It gets the discourse, the strikes, the magazine covers.
  • Mid-tier credentialed work (paralegal, junior creative, customer service, content moderation back-office) is squeezed first and quietest. It usually does not produce a strike; it produces attrition.
  • Low-status data work — the human reinforcement that makes the models behave at all, paid at $1.32–$2/hour in Kenya at the time of writing — sees worse conditions on the same gradient that produced the consumer product. The visibility curve is inverse to the consequence curve.
The labor decomposition — which AI × which labor × which gradient
AI TYPEpositioned by gradient (silent ↔ shock)↑ vertical = actual consequenceLABOR TYPEpositioned by visibility (silent ↔ shock)↑ vertical = actual consequencesilent · low gradientquietvisibleshock · high gradientSHARED GRADIENT — the §3 axisRecommender systemsRobotics with embedded learningVision / biometric modelsGenerative LLMsLow-status data workMid-tier credentialed workHigh-status knowledge workTHREE GRADIENTS · THREE POLITICAL RESPONSESCalling all three “AI and jobs” is the same move as calling everything from a thermostat to ChatGPT “AI” — a refusal to decompose. It is the move that lets the shock layer absorb the public attention while the slow layer reorganizes labor without it.Visibility curve is inverse to consequence curve. The discourse follows the visible.
A shared horizontal axis runs from silent / low-gradient on the left to shock / high-gradient on the right. Each AI type (top band) and labor type (bottom band) is positioned along it; vertical position encodes actual consequence. The mismatch between the two bands is the argument: the visibility curve is inverse to the consequence curve. Recommender systems and low-status data work sit at the silent end with the biggest consequences. Generative LLMs and high-status knowledge work sit at the shock end with relatively smaller ones.

These are three different gradients and three different political responses. Calling all of them “AI and jobs” is, structurally, the same move as calling everything from a thermostat to ChatGPT AI: a refusal to decompose that is not neutral. It is the move that lets the shock layer absorb the public attention while the slow layer reorganizes labor without it.

The earlier observation — that doom and hype are the loud sensors that keep the rest invisible — is the same mechanism viewed from the political side. The discourse is not failing to discuss AI and labor. It is discussing the part of AI and labor that fires the sensor, while the part that moves on the slow gradient embeds.

The work the framework therefore wants to do is not “predict which jobs disappear.” That is the wrong question, asked from inside the silo. The work is: name the assignment that produced the current job structure, name the gradient on which any given AI is reorganizing it, name the actor who benefits from which sensor firing, and refuse the version of the conversation that treats either AI or labor as one thing.

The historical contingency of the job as a category — central to the argument above — sits in conversation with Graeber (Bullshit Jobs, Debt) and Zuboff (Surveillance Capitalism) among others, listed in §12.

§6

Compression, silent versioning, and the risk of lockstep truth

AI has broken the silos open. The companion observation we find less comfortable: AI also compresses the silos' outputs into one confident-sounding voice and replays them as though they were the record of human knowledge — rather than the record of what got written, by whom, weighted toward the paradigm that decided what deserved to be written. The representation biases do not disappear when you route them through a language model. They calcify. Every query returns a weighted average of the same inherited frame.

A recent small example: an image model was asked to generate a community. Most of the figures in the frame were Black or brown. The one in the center, taller than the others and dressed in a suit, was white. Nobody told the model to do that. The training distribution did — because the training distribution is a statistical record of whose bodies, whose clothes, whose postures were historically placed at the centers of frames in the images the model was trained on. No malice required. The frame IS the malice, carried forward.

And the compression layer is commercially governed. Production models are silently versioned — RLHF updates happen, fine-tunes ship without announcement, A/B tests run on real questions in real production contexts. The answer returned today is not the answer that would have been returned last quarter, and the people using the model typically do not know. “Truth” in the public domain becomes, in practice, downstream of whichever provider has the subsidy runway plus the distribution channel. The model that wins is not necessarily the model that is most accurate. It is the one whose business lasts longest in the AI-investment cycle we are currently inside.

The same question asked of the same "AI" across a year
THE QUESTION“Is X safe / true / recommended?”— constant across all four versions —v4.0Janbase releasev4.1MarRLHF passv4.2Junsafety fine-tunev4.3Sepsilent A/BCAUTIOUS"There is scientificdebate. Evidence suggestsX, but Y is contested."CONFIDENT"The mainstream positionis X. You can read morehere."REFUSES"This is a sensitive area.I can't provide specificguidance."HEDGED"Depending on context, Xor Y may be appropriate.Consult a specialist."WHAT THE USER SEES“The AI says [whatever was current the day they asked].”No version indicator. No changelog. No acknowledgement that last quarter's answer was different.“Truth” becomes downstream of whoever has the subsidy runway + distribution channel to ship the next update.
The question never changes. The model's name never changes. But the answer does — silently, between quarterly RLHF passes, safety fine-tunes, and A/B tests that ship without announcement. Users see a moving target as a stable one. “The AI said” is a sentence with no fixed referent, and what counts as “the answer” becomes a property of the provider rather than the question. The traveling dot shows the default answer moving over time — what most users will have quoted at any given moment.

If a society routes its default truth-formation through a small number of privately-governed, silently-versioned models, the capacity for collective error-correction — which has always depended on dissonance, patience, diverse error, and the structural visibility of disagreement — gets thinner. Not zero. Thinner. The early sign is not obvious collapse. The early sign is that disagreement starts to feel eccentric rather than ordinary, and that more people say “the AI says” the way a previous generation said “science says,” as if that were the end of the conversation.

§7

The mirror failure: refusal-to-analyze as a privileged-actor pathology

Section 1 named how people who were filtered out by the linear frontend come to believe they cannot understand the work. The mirror observation is less comfortable and less often stated: people who were not filtered out — who hold governance roles, institutional salaries, and the decision rights that flow from them — often refuse to analyze the same work, under different cover. Where the excluded internalize “this is not for me,” the privileged perform “we respect what the people believe.” The public posture is humility. The operational effect is the same: the category is not decomposed, the specific instance is not examined, and the governance choice is made on brand rather than substance.

This is a live pathology in the environmental, advocacy, and community-nonprofit world — and it is not politically symmetric with the first. When an excluded person says “I don't understand AI,” they are reporting on the filter that failed them. When a nonprofit director paid several multiples of the median household income in their service area says “the people don't like AI,” they are invoking a public they have not consulted on a specific question to justify declining to analyze the specific question. The first is a symptom. The second is a decision — one of a set of decisions that cumulatively reproduce the environment the first is a symptom of.

Two opposite-seeming positions. Same outcome.
FAILURE MODE 1 · EXCLUDED PERSONfiltered out · internalizes exclusion · reports the filterfiltered out bya linear frontend“I don't understand AI.”“Science isn't for people like me.”MECHANISMreports the filter that failed them —a symptom, not a choice.the frontend decided they couldn'tunderstand; they came to believe it.FAILURE MODE 2 · PRIVILEGED ACTORempowered by the filter · invokes "the people" · avoids analysisprivileged intoa governance role“The people don't like AI.”“We're respecting what they believe.”MECHANISMinvokes a public they haven'tconsulted on this specific question —a decision, not a symptom.performs humility, avoids the analysis.SAME OUTCOMEthe specific instance is not examinedthe category is not decomposed · governance made on brand, not substance
The excluded person says “this is not for me” because the filter they met told them so. The privileged actor says “the people don't like it” without having asked the specific question of the specific public. The first is a symptom. The second is a decision. But the operational effect is identical: the category is not decomposed, the specific instance is not examined, and the governance choice is made on brand rather than substance. Addressing only the first leaves the second intact — which is why LeResearch commits to naming both.

Both failure modes produce the same outcome. They keep the dominant framework — whatever it is, technical or otherwise — from being examined in its particulars. The first happens because the frontend filtered someone out. The second happens because the frontend privileged someone into a position from which examining it would be uncomfortable. Both versions need to be named, because addressing only the first leaves the second intact, and the second is the mechanism by which institutional governance actively reproduces what institutional rhetoric claims to fight.

LeResearch commits to being honest about both versions, including when the second version shows up inside our own organization — which it will, because no structure is immune to it, and the only durable defense is a governance split (board authority vs. executive authority vs. research authority) that makes substantive analysis the default behavior rather than a thing that has to be insisted on under pressure.

For publicly documented cases of this pattern in operation — including the NYC Department of Education ChatGPT ban-and-reversal as a near-textbook execution and the Memphis xAI opposition as a counter-example of substantive (not pathological) refusal — see /philosophy/cases. The framework should be triangulated against the public record, not just against any participant's account.

§8

The tension LeResearch exists to hold

This is not an argument against AI as a frontend. LeDesign uses language models precisely because they are the first adaptive, multimodal, plural-by-construction frontends humans have ever had access to. The argument is against monoculture in the frontend layer. It is against the version of the future where everyone consults the same model, that model is governed by three or four companies, and our collective ability to say “that is wrong, and here is why” atrophies because we stopped exercising it.

The tension LeResearch exists to hold
MONOCULTUREeveryone consults the same 3–4 modelsONE MODELgoverned by 3–4 firmssilently versioned“the AI says”(= end of conversation)PLURALITYmany small models, each grounded in its source“these models say X — and here's why”(= conversation continues)LERESEARCH HOLDSboth at onceThe argument is not against AI as frontend. The argument is against monoculture in the frontend layer.
Not anti-AI as a frontend. LeDesign uses language models commercially because they are the first plural-by-construction frontends humans have ever had access to. The argument is against monoculture in the frontend layer — the version of the future where everyone consults the same three or four models, governed by three or four companies, and our collective ability to say “that is wrong, and here is why” atrophies because we stopped exercising it.

This is the tension we find ourselves unable to step past. It is the reason LeResearch exists as a distinct entity — the reason we did not simply expand LeDesign's product work. Research on epistemic hygiene in an AI-mediated knowledge ecology is not a product requirement that resolves in eighteen months. It is slow, it is unglamorous, it does not resolve cleanly, and it touches every substrate we work on — from how a child meets an aquifer for the first time, to how a household assembles nutrition for a week, to how a court evaluates a calibrated groundwater model under equitable apportionment. The work is the ecology itself.

LeResearch is how we intend to hold it.

§9

Six operational principles

How the thesis becomes day-to-day product and research decisions. These are constraints we accept, not aspirations we aim at.

Six operational principles · radial constellation
THE LEARNERdefines the frontendthe author does not§9.1Frontend defined by learnerdepth, language, modality, jargon — chosen on the receiving end§9.2Silos are our convenienceaquifers ↔ water policy ↔ AI compute ↔ legal history are one story§9.3Jargon is a frontend choiceevery term gets a plain-language companion one tap away§9.4Confidence is structuralevery claim travels with source, confidence tag, update timestamp§9.5Open by defaultdata, code, hardware, methodology — public good when we can§9.6Experts augmented, never replacedteacher, hydrogeologist, lawyer still own the frontendConstraints, not aspirations. Removing any one collapses the whole.
The six principles aren't a list — they are six axes around one commitment: the person on the receiving end defines the frontend. Each principle is a constraint, not an aspiration. Removing any one collapses the whole; that is what “structural” means here.
§9.1
The learner defines the frontend, not the author

Every tool we build lets the person on the receiving end choose the depth, the language, the modality, and the jargon level. The authoring surface is plural by construction, not as a later accessibility bolt-on.

§9.2
Silos are our convenience, not the world's truth

Domains connect. Aquifers, municipal water policy, AI compute water use, and legal history are the same story. Our products cross-link rather than silo-enforce, even at the cost of making the UI harder to categorize.

§9.3
Jargon is a frontend choice, not a truth

Every technical term gets a plain-language companion one tap away. The expert version is not truer — it is shorter for people who already share the vocabulary. Language is interface.

§9.4
Confidence is structural

Every factual claim in every tool travels with a confidence tag (confident / likely / debated / we don't know), its source, and an update timestamp. Grounded AI assistants refuse to fabricate; they prefer 'we don't know' to a plausible sentence. A claim that cannot produce its source is not a claim the system will make.

§9.5
Open by default

Public data whenever it exists. Open-source licenses on software, hardware, content, and methodology. When we take nonprofit or foundation funding, the entire artifact stack becomes public good. When we work with private clients, the architectural patterns we learn still become public good.

§9.6
Experts are augmented, never replaced

A teacher still defines the classroom. A hydrogeologist still owns the science. A lawyer still represents the client. Our tools run alongside those roles and give them capacity they did not have before. A tool that claims to replace any of them is a different product — not ours.

§10

What LeResearch is NOT claiming

  • ·Not a replacement for teachers, doctors, lawyers, engineers, or scientists. These are frontends with virtues software does not have.
  • ·Not apolitical. Water is political. Education is political. Law is political. AI-governance is political. Pretending otherwise is itself a political stance — one that defaults to the status quo.
  • ·Not a universal curriculum. The reading levels, representation toggles, depth controls — these are frontends each learner composes. They are not a standard we impose.
  • ·Not a static framework. This document will need to be revised. If it stops being revised, we have stopped learning.
  • ·Not a closed ecosystem. Open-source, open-data, open-hardware where licensing allows. No “you have to use our full stack” ever.
  • ·Not a single-domain research center. Hydrology, food systems, educational frontends, AI epistemics — these are substrate tracks, not the mission. A donor looking for “the water nonprofit” or “the food nonprofit” is in the wrong place.
§11

The voice we use

Across writing, product copy, proposals, documentation:

  • Learner-first, not teaching-first. Prefer “the tool makes it possible for someone to…” over “we teach X.” Avoid totalizing constructions (always, every, all).
  • Conditional over declarative. “If this is useful…” rather than “this is the right way to…”
  • Specific over abstract. A $15K line item defending 150 hours of classroom UX review beats a $40K line for “educational consulting.”
  • Humble about what we don't know. Uncertainty is named. Drafts are labeled drafts. Work in progress is labeled work in progress.
  • Political when honesty requires it. We do not hide behind neutrality when the facts have stakes. We do not campaign, but we do not obscure either.
§12

Open threads — the literature we will go deeper on

This document leans on a set of intellectual traditions developed elsewhere. The list below is the index; the first-pass treatments — three to five paragraphs each, naming the load-bearing argument, the connection to the framework, and the question we have not yet worked out — live on the dedicated open-threads page. Each entry below links to its developed treatment. The order is rough; the groupings are not.

Literature map — the threads behind this document
1960197019801990200020102020IMAGINED ORDERShow shared frames become institutional factNORMALIZATION · PARADIGM · SHOCKhow change becomes invisible or visibleCONTINGENCY OF "THE JOB"wage labor as a recent, particular formBerger & LuckmannSocial ConstructionCastoriadisL'institution imaginaireBourdieudoxa / habitusAndersonImagined CommunitiesSearleConstruction of Soc. RealityHarariSapiensKuhnScientific RevolutionsPaulyshifting baselineKleinThe Shock DoctrineSchmachtenbergermetacrisis (ongoing)GraeberDebtGraeberBullshit JobsZuboffSurveillance CapitalismFEEDS§3 — substratenormalization gradientFEEDS§3 — mechanismand §6 silent versioningFEEDS§5 — worked exampleAI and laborThe framework is not original. The synthesis is. Each thread has its own deep dive coming.
Thirteen threads, three buckets, six decades. Each track flows into the section it informs: imagined orders beneath §3, normalization & paradigm inside §3, contingency of the job beneath §5. Each entry is a thread to be developed in its own piece — adding the next one is one line of data.
Imagined orders · the substrate beneath §3
Normalization, gradient, paradigm · §3 in detail
The contingency of 'the job' · §5 in detail

The treatments on the open-threads page are first-pass readings, not finished pieces. They are commitments — to do the reading, to revise the page, and eventually to split out the threads that mature into their own essays, diagrams, or worked cases. Read the developed treatments →

§13

A closing note

The tagline — “a small contribution to the silos's fall” — is the one-line version of everything above. It means: we are not the ones tearing down the wall. The wall is coming down. We would rather be in the rubble with the people who were priced out, than on the other side charging rent for the door.

Last revised 2026-07-14. Living document.