Writing

A numbered series on Africa's public institutions — what's broken, what works, and what the evidence says. Each paper carries a stable WP number and is citable from the Flux registry.

Showing 16 of 44

2026

WP41
The Word "Personalized" Is Doing Two Different Jobs
Abstract

Skincare has sold "personalization" for a decade — quizzes, skin-type sliders, AI-matched routines — and most of what it delivers is cosmetic segmentation: oily or dry, budget tier, fragrance preference. Almost none of it is the specific personalization that melanin-rich skin actually needs, which is a routine matched against a documented, disproportionate risk: post-inflammatory hyperpigmentation (PIH), a complication that is measurably more common, more severe, and slower to resolve in darker Fitzpatrick phototypes. This paper traces that gap to its source. Dermatology's own trial base, textbook imagery, and — now — the image datasets training AI dermatology tools all underrepresent skin of color by a repeatedly measured margin. We argue that Zamia, Flux's AI skincare consultant, is a real attempt at the second, harder kind of personalization, deliberately "boxed" so a language model narrates while a fixed, vetted product-and-evidence engine decides. We do not treat that as self-evidently true. We hold Flux's own commercial stake in this conclusion up for scrutiny, take seriously the objection that "personalized skincare" is mostly marketing language borrowing the authority of science, and set out the regulatory line — cosmetic advice, not diagnosis — that a tool like Zamia has to stay on the right side of. We close with falsification conditions and an honest accounting of what the evidence does not yet show.

24 Sep
32 min
paper ↗
WP39
The Switching Cost Is Why Nothing Sticks
Abstract

The Personal Operating Layer (WP26) argued that the most useful personal AI will not be an app people remember to open, but a presence already resident in their messages. That paper established the observation — people already run their lives inside chat threads — without establishing the mechanism: why does living in the thread actually outperform living in a separate app, rather than merely feel more convenient? This paper argues the mechanism is measurable rather than aesthetic. The cognitive-psychology literature on interrupted-task resumption — Altmann and Trafton's memory-for-goals model, and the resumption-cost experiments it produced — shows that suspending a goal to switch context is not a neutral pause. The goal's activation decays, and resuming it carries a real, measured cost that grows with the length and demand of the detour. "Open a separate app" is exactly that detour, repeated every time the tool is needed, and this is consistent with the documented collapse in engagement that self-improvement and personal-admin apps show once installed. Messaging removes the detour structurally, not through better design, and in Africa's mobile-first, WhatsApp-saturated markets it functions closer to a shared communications substrate than one interface choice among several. The paper takes seriously the objections that conversational interfaces measurably fail at complex multi-step tasks, that living inside someone's messages is the most privacy-invasive surface available, and that notification fatigue is rising, not falling — and states four falsification conditions in decreasing order of damage to the claim.

24 Sep
35 min
paper ↗
WP35
The Second Question: What Changes When an Explainer Can Be Asked Again
Abstract

This is a first-person design account of building an in-place AI explainer, using it for months as a browser extension and as a local desktop application, and discovering that its defining feature was not the one it shipped with. A single-shot inline explanation resolves a word but rarely the confusion: the first answer raises the question actually worth asking, and a tool that cannot take that question sends users to a chat window to restate everything. The paper grounds this observation in four decades of information-science research it did not set out to test — Belkin, Oddy and Brooks' 1982 account of the user who cannot specify a need because the need is a gap in their own knowledge, and Bates' 1989 model of search as an evolving sequence of moves rather than one well-aimed query — and in the task-resumption literature (Altmann and Trafton; Trafton, Altmann, Brock and Mintz; Leroy) for why the follow-up specifically, not just the first answer, has to stay anchored to an undisplaced source. It argues that a follow-up which opens a panel or a separate surface forfeits the entire premise, makes a coherence argument for going standalone, and contrasts the launcher pattern against an in-place explainer across five properties. The paper states plainly what is built and what is not, withdraws an internal claim that did not survive being checked against its own table, records how retiring the extension silently invalidated a pricing tier, and sets out five checkable commitments for a standalone version together with falsification conditions and an evidence register carrying forward the specific unmeasured case — resumption lag for a self-initiated, in-document lookup — that the companion paper also leaves open.

16 Aug
23 min
paper ↗
WP34
The Panel Is Also a Tab
Abstract

Mainstream AI answer surfaces converge on a single strategy for the mid-document lookup: bring the answer closer. Docked panels open beside the text, launcher overlays float above it, and search results increasingly compose the answer in place of an index. This paper argues that the first two solve the wrong half of the problem. The cost of interrupting a reading task to look something up is not the distance travelled but the re-entry, and it grounds that claim in published task-resumption research — Altmann and Trafton's activation-based model of goal memory, Monk, Trafton and Boehm-Davis's finding that resumption cost scales with an interruption's duration and demand, Trafton, Altmann, Brock and Mintz on the perceptual availability of the primary task, and Leroy on attention residue — while being explicit that none of those studies measured a self-initiated, in-document lookup specifically, and that the directional claim, not a borrowed number, is what survives the transfer. A sharper and somewhat counter-intuitive consequence follows: a richer, more engaging panel conversation should be more expensive to return from, not less, which cuts against treating a better panel as a strict improvement. The paper specifies four conditions an answer must meet to genuinely not move the reader, each traced to a specific mechanism, and argues that the cost of asking determines the shape of what gets asked. The claim is deliberately bounded: for sustained comparison, synthesis, or any case where the answer is itself the artifact, the persistent panel is correct. The paper states falsification conditions, including a serious unresolved objection about low-demand panels, and reports no measurement of its own for the specific case its argument is about.

16 Aug
22 min
paper ↗
WP26
The Personal Operating Layer: The Case for an AI That Lives in Your Messages
Abstract

People already run their lives inside chat threads — texting themselves, keeping solo group chats as running records. This paper argues that the most useful personal AI will not be an application one opens but a presence in the message thread that talks like a friend, acts on the user's behalf, and holds them to their own goals. It frames this as the missing-layer thesis applied to an individual life.

28 Jun
13 min
paper ↗
WP25
The Operating Workforce: An African-First Theory of AI Employees
Abstract

The phrase 'AI employee' typically evokes a Western firm replacing expensive knowledge workers. This paper argues the African case inverts that picture: AI employees will first fill roles institutions never managed to staff at all. Building on the missing-layer thesis, it develops an African-first theory of the operating workforce — role-scoped, accountable agents that do an institution's routine, rules-bound work — and presents procurement as the first such role.

25 Jun
18 min
paper ↗
WP23
The Institutional Gap Is the Feature
Abstract

This paper argues that the most constrained environments are plausible — not proven — ground for AI-complete workflow design: where staffing a process is not financially viable, the choice is not between augmenting a process with AI and redesigning it, but between redesigning it and the process not happening at all. Well-resourced organisations retain the option to merely optimise an affordable existing process and, this paper argues, tend to exercise it; resource-constrained organisations do not have that option. The argument is illustrated with four Kenyan products built by Flux (PBOMaster, AccessWASH, ProcureBee, AnswerTab) and grounded in two external literatures: a 2013 peer-reviewed innovation-management study finding resource constraints spur radical rather than incremental innovation in manufacturing (not Africa- or AI-specific, cited for the general mechanism only), and the well-documented M-Pesa history in Kenyan financial services. This revision adds a scope section distinguishing the paper's mechanism claim from a measured outcome; engages, as its most serious objection, a credentialed Africa-based technology-policy researcher's published scepticism of leapfrogging-by-default, answering it with a narrower, explicitly bounded claim (infrastructure-leapfrogging and process-elimination AI are different claims) rather than a dismissal; introduces a labour-economics displacement/reinstatement framework to name a real, unresolved risk in its own enthusiasm for AI-driven process elimination; and states falsification conditions, limitations, and both appendices. Flux's direct commercial interest in this thesis is named without softening. Three measurements the argument needs and lacks — the addressable population's actual scale, the rate at which constrained organisations choose AI redesign over cheap informal labour, and the measured displacement/reinstatement balance for constraint-driven AI specifically — are registered as CITATION-NEEDED rather than estimated.

13 Jun
23 min
paper ↗
WP21
Personalized Is the New Glow
Abstract

This paper argues that "glow" was always a description of personalized skin care, not a purchasable finish — and that melanin-rich skin has been structurally excluded from that personalization for decades, at real cost in money, time, and the skin itself. It is the earlier of two Flux papers on this subject; [[040-two-jobs-of-personalized|a later paper]] (WP41) grounds the clinical and regulatory case in the dermatology literature on skin-of-color underrepresentation and on post-inflammatory hyperpigmentation specifically. This revision is deliberately not a duplicate of that sourcing: having read WP41 in full, it cites WP41 directly wherever the clinical mechanism is needed and instead researches what WP41 does not cover — the beauty industry's own shade-range history (Fenty Beauty's 2017 launch, and an independent data-journalism analysis finding that 40-shade ranges already existed before it, concentrated at the light end), skin-bleaching prevalence specifically in African markets (a 2023 peer-reviewed short communication reporting country-level figures from Nigeria to Mali), and the market-research industry's own inability to agree on the size of "personalized skincare" as a category, used as evidence for the paper's own "personalization is marketing language first" self-criticism. A scope section distinguishes this paper's market-and-representation argument from WP41's narrower clinical claim. Objections include Flux's direct commercial interest in Zamia, the product this essay argues for, and the risk that framing skin bleaching as a market failure understates real social and economic pressure the literature itself documents. Falsification conditions, limitations, and both appendices are added; the quantified cost of the "trial-and-error tax" and any independent audit of Zamia's own evidence engine are registered CITATION-NEEDED rather than estimated or assumed.

10 Jun
22 min
paper ↗
WP20
Accountability Is Not a Reason to Keep Humans in the Process
Abstract

This paper argues that for well-specified, high-volume, rule-based processes, human involvement does not produce the accountability it is assumed to produce — it produces a bottleneck and, often, an undocumented point of failure that a well-specified automated system would not have. The pre-revision body carried an unfinished footnote with literal bracketed research instructions left in the published text; this revision treats that as a to-do list and completes it. New sourcing: the vigilance-decrement literature (See, Howe, Warm & Dember 1995) grounds the claim that sustained human checking tasks degrade in accuracy over time; the ACFE's 2024 global fraud survey supplies real detection-method data (tips far outdetect formal review mechanisms) while also reporting, honestly, that management review measurably reduces losses by 60% where it exists — a genuine complication this paper engages rather than omits; the WHO Surgical Safety Checklist study (Haynes et al. 2009) shows specification and documentation reduce error even without automation, which this paper is careful not to overclaim as automation-specific evidence; and Mark Bovens's accountability theory supplies both a rigorous actor-forum definition and an independently-arrived-at precedent — "corporate accountability," one of his named responses to the "problem of many hands" — for relocating accountability from a named individual to a documented process. The paper's sharpest objection to itself, engaged directly rather than only disclosed, is that the automation-complacency and automation-bias literature (Parasuraman & Manzey 2010) shows human "oversight" of automated systems is not reliably real oversight, even among trained experts, which weakens the paper's own recommendation that humans remain a governance check on automated systems. Flux's commercial interest in this conclusion, through PBOMaster, ProcureBee, and AnswerTab, is named directly. Falsification conditions, limitations, and both appendices are added; a head-to-head error-rate comparison between automated and human rule-checking, and any independent audit of Flux's own products' error rates, are registered CITATION-NEEDED rather than assumed.

9 Jun
23 min
paper ↗
WP19
Your AI Strategy Is Digital Transformation With Better Branding
Abstract

This paper argues that most organisational "AI transformation" strategies are digital transformation with updated branding: technology accelerating an existing process rather than eliminating it. The distinction is not new. Michael Hammer's 1990 Harvard Business Review article made the identical argument about an earlier technology wave, and this revision grounds it in his own case data, read directly: Ford's accounts payable department achieved a 75% headcount reduction by redesigning its process, against a 20% target from conventional automation alone; Mutual Benefit Life's reorganisation around "case managers" cut application turnaround from 5-25 days to 2-5 days. M-Pesa's founders' own 2007 account confirms the paper's claim that it was designed from the unbanked population's needs outward, not as a digitised bank branch. A 2025 preliminary, non-peer-reviewed MIT applied-research report independently restates this paper's exact mechanism for current generative-AI deployments specifically — tools that function as productivity enhancers rather than workflow transformers — treated explicitly as order-of-magnitude evidence of a pattern, not a precise rate. The paper's sharpest objection to itself, engaged directly rather than filed away as history: business process reengineering, the 1990s movement Hammer's own article launched, developed a well-documented failure rate and became cover for indiscriminate downsizing, by the explicit acknowledgment of one of its own founders — a direct precedent for the risk in this paper's own prescription, which a labour-economics displacement/reinstatement framework sharpens further. Flux's commercial interest in this conclusion, through PBOMaster, ProcureBee, and AnswerTab, is named directly. Falsification conditions, limitations, and both appendices are added; a controlled comparison of acceleration-versus-elimination strategies and any independent audit of Flux's own customers' outcomes are registered CITATION-NEEDED rather than assumed.

5 Jun
22 min
paper ↗
WP18
The Expense Report Was Never About Expenses
Abstract

This paper argues that the corporate expense report is not primarily an accounting instrument but a trust mechanism — a monitoring-cost response, in Jensen and Meckling's 1976 sense, to the problem of delegating spending authority to employees whose judgment about appropriate spending is not identical to organisational policy. It argues that agentic payment infrastructure such as ProcureBee's virtual cards does not automate this mechanism but eliminates it, by moving policy enforcement from a post-hoc review stage to the point of transaction itself, using the same merchant-category-code controls already documented in Visa's own commercial-card infrastructure. This revision grounds the argument in evidence not previously verified for this essay: the Global Business Travel Association's 2015 cost study ($58 and 20 minutes per report, 19% error rate); two US Government Accountability Office reports, nineteen years apart, tracking what changed in government purchase-card controls as point-of-sale enforcement matured; and a full, direct reading of the Association of Certified Fraud Examiners' 2024 global fraud survey, which complicates the paper's own account of manual review as mere rubber-stamping — management review rarely detects fraud directly (13% of cases) but its presence correlates with a 60% reduction in fraud loss when fraud does occur, a finding this paper cannot fully explain and treats as a live objection rather than a settled point. A new objections section names Flux's commercial interest in the conclusion through ProcureBee directly, and states as a limitation that card-based controls do not reach the cash-first and informal-sector spending common in the markets this corpus is otherwise concerned with. Falsification conditions, limitations, and both appendices are added. Three measurements the argument needs and lacks — ProcureBee's own audited outcomes, the scale of spending foregone under expense-report friction, and the mechanism behind management review's loss-reduction effect — are registered CITATION-NEEDED rather than estimated.

1 Jun
27 min
paper ↗
WP17
Did It Do It For You?
Abstract

This paper argues that the central question for any AI deployment is binary: when the task was finished, did the AI do it, or did it help a person do it? "AI-assisted" work leaves the human as the agent and the AI as a faster tool; "AI-complete" work redesigns the process so a human is no longer required for individual instances, only for setting policy and handling exceptions. The paper grounds this distinction in an existing human-factors taxonomy of automation by stage and level (Parasuraman, Sheridan & Wickens, 2000) rather than treating it as original, and situates the common failure mode — organisations deploying AI as a better interface on an unexamined process — in both the 1990s enterprise-software productivity-paradox literature (Brynjolfsson 1993; Davenport 1998) and a 2021 management-research finding that organisations systematically favour "augmentation" over "automation" even where the latter is available (Raisch & Krakowski). It illustrates AI-complete design with two Flux products, PBOMaster and ProcureBee, named as illustrations from one company's own line rather than a representative sample. This revision adds a scope-and-standing section; an objections section that uses automation-complacency research (Parasuraman & Manzey, 2010) against the paper's own accountability argument, names Flux's commercial interest directly, and concedes the binary test oversimplifies most real deployments; falsification conditions; limitations; and both appendices. Three measurements the argument needs and lacks — comparative outcomes by deployment category, comparative failure rates between human complacency and automated-policy error, and the true share of eliminable administrative workload — are registered CITATION-NEEDED rather than estimated. A widely repeated secondary account (FoxMeyer Drug's 1996 ERP-linked bankruptcy) was deliberately left uncited after the primary source proved inaccessible.

28 May
26 min
paper ↗
WP12
The Agentic Buyer and the End of Dark Patterns
Abstract

This paper argues that SaaS pricing pages are built to manipulate human psychology — anchoring, decoy pricing, social proof, defaults, cancellation friction — and that AI procurement agents largely do not process pages the way the visual and social channels these patterns exploit require, creating pressure toward pricing clarity. The original essay claimed agents "have no psychological vulnerabilities." This revision corrects that rather than carrying it forward: a peer-reviewed 2025 study (Findings of ACL: EMNLP 2025) found LLM agents measurably susceptible to anchoring in simulated price negotiation, and an independent 2024 study found LLMs more susceptible to anchors framed as expert claims than the same numbers presented plainly. The corrected thesis is narrower — manipulation must change channel, from visual/social cues to numeric/framing language, to reach an agent — not that agents are immune. New sourcing grounds the argument throughout: a 2019 peer-reviewed crawl of 11,000 shopping websites quantifying dark-pattern prevalence; the FTC's 2022 dark-patterns report and its $2.5 billion 2025 Amazon settlement over Prime cancellation design; foundational decoy-effect, default-bias, and social-proof literature, independently checked; and primary documentation for four agentic-commerce payment protocols launched in 2025 (Mastercard Agent Pay, Visa Intelligent Commerce, OpenAI/Stripe's Agentic Commerce Protocol, Google's Agent Payments Protocol). An untraceable, misattributed quote ("Benedict Evans, Stratechery" — Stratechery is Ben Thompson's publication) in the prior body could not be verified and is removed rather than carried forward. An objections section names Flux's commercial interest via ProcureBee, and states as the sharpest unresolved risk that a vendor could satisfy every agent-parsability criterion while embedding a numeric anchor or false expert-framing claim. Falsification conditions, limitations, and both appendices are added. Three gaps — agent susceptibility in a live B2B purchase flow rather than simulation, measured deployment of agent-targeted manipulation, and independent adoption data — are registered CITATION-NEEDED.

2 May
31 min
paper ↗
WP11
The Corporate Card Was Never the Solution
Abstract

Every corporate payment instrument since 1950 -- the charge card, the credit card, the purchase card, the programmable virtual card -- has narrowed the gap between when spending authority is granted and when a specific transaction is validated against it, without closing it. This paper traces that lineage, correcting its own prior account along the way: purchase cards are usually filed under "2000s procurement" but U.S. federal adoption actually began in the mid-1980s, and the previous draft of this essay described a product called "the Stripe agent wallet," quoted a sentence attributed to "Stripe Engineering Blog" that could not be verified against any Stripe-published material, and claimed it was "the first complete answer" to the authorization problem. Fetching Stripe's own current documentation directly found the real, correctly-named product (Issuing for agents, distinct from the consumer-facing Link Agent Wallet) still requires a per-transaction authorization decision -- made by policy code within a 2-second default window, not eliminated. The paper's revised claim is narrower: 2026's agent-issuing products are the most precise instrument yet in a 75-year lineage, compressing authorization to a real-time programmatic decision, not removing the need for one. ProcureBee, Flux's own procurement agent, is described as a first application of this primitive, and Flux's commercial interest in that framing is named directly. The paper cross-links rather than duplicates a companion essay on what happens when a correctly-authorized agent purchase still goes wrong. Falsification conditions, limitations, and both appendices are added; three measurements the argument needs and lacks -- comparative error rates against prior-generation virtual cards, a comparable account of mobile-money authorization architecture, and ProcureBee's own live policy-layer accuracy -- are registered as CITATION-NEEDED rather than estimated.

2 May
27 min
paper ↗
WP10
Your Knowledge Gaps Are the Most Intimate Data You Have
Abstract

This paper argues that epistemic data — the record of what a person looked up, what confused them, and where their understanding ran out — is a more intimate category of behavioral data than location or purchase history, because it maps cognitive and professional state rather than external action, and that AI reading/comprehension tools are being built directly on top of it before any protective default has been set. It adds a scope section stating what the argument rests on and what would refute it, and corrects three errors carried in the prior body: the Target/Duhigg purchasing-prediction story is redated to February 2012 and its famous father-daughter confrontation scene is flagged as an unverified anecdote rather than confirmed fact; the library profession's privacy history is separated into two actually-documented episodes (the 1953 Freedom to Read Statement and the FBI's 1973-1987 Library Awareness Program) rather than merged into one "McCarthyism" narrative; and a fabricated book attribution (a nonexistent Kenneth Crews title) is removed outright. New sourcing grounds the BYOK (bring-your-own-key) architectural recommendation in current, directly-read provider policy (OpenAI, Anthropic) and in the legal literature on reading privacy (Cohen 1996; Richards 2013), and a new section shows the GDPR's "special categories" of personal data do not currently cover cognitive or epistemic state at all. The objections section states directly, rather than omits, that Flux's own comprehension product, AnswerTab, does not yet implement the BYOK architecture this paper recommends. Falsification conditions, limitations, and both appendices are added. Three measurements the argument needs and lacks — a quantified base rate for "epistemic" versus instrumental lookups, a public legal test of compelled AI-provider disclosure, and a documented market price for comprehension-specific data — are registered CITATION-NEEDED rather than estimated.

2 May
31 min
paper ↗
WP09
The Web Was Built for Navigation, Not Comprehension
Abstract

The web's core primitives -- the link, the page, the tab -- were built to solve document connectivity, not in-document comprehension, and this paper argues that specific architectural mismatch is what makes stopping to look up an unfamiliar term so costly to a reader's progress. This revision makes a significant correction, stated plainly: the previous draft attributed a widely circulated "23 minutes to refocus" statistic to Gloria Mark's research. Reading both of Mark's most relevant studies directly found that figure in neither -- the 2005 paper measures workplace task fragmentation (11 min. 4 sec. average per working sphere, 57.1% interrupted), and the 2008 paper's headline finding is close to the opposite of what the circulated figure implies: interrupted work did not take longer, because people compensated by working faster, at a cost in stress rather than time. This revision does not use that figure, replacing it with literature that actually speaks to the paper's claim: DeStefano & LeFevre 2007 on cognitive load in hypertext reading, and Knight 1994 and Hulstijn et al. 1996 on marginal glosses versus dictionary lookup. A second fabrication was also corrected: a quotation attributed to Mortimer Adler did not appear verbatim in How to Read a Book and has been replaced with a verified quotation from the primary text. The paper also replaces a vague "medieval manuscript" example with the real, documented Glossa Ordinaria. Flux's commercial interest in AnswerTab, named as this paper's proposed comprehension layer, is stated directly. Falsification conditions, limitations, and both appendices are added; three measurements the argument needs and lacks -- the specific time cost of an in-document lookup, whether an always-available comprehension layer erodes productive reading struggle at scale, and the real-world relationship between term density and reading behaviour -- are registered as CITATION-NEEDED rather than estimated.

2 May
29 min
paper ↗