André Lindenberg’s Post

Donald Norman argued in 1991 that tools don't amplify cognition … they change the task by changing its representation. A checklist doesn't improve memory. It gives you a different task: read and follow. The system sees enhancement. The user sees new cognitive demands. Precomputation … building representations once, reusing them across people and time … is the mechanism. Context engineers rediscovered this 35 years later. #cognitiveArtifacts #contextEngineering #representation #HCI

  • graphical user interface, text, application

Check out this interesting new paper with many great visualisations … Externalization in LLM Agents: A Unified Review of Memory, Skills, Protocols and Harness Engineeringhttps://arxiv.org/abs/2604.08224

Context helps. Books help. Neither can think. Gartner made the “C” word even more famous. But open-book exams proved long ago: giving everyone the same books did not give everyone the same result. Books are context. The gap is reasoning. The real frontier is not more context, but a reasoning layer — systems that can infer, justify, and prove. Don’t Trust AI. Prove It.https://hypergraphmind.com/

Most people still frame this as model capability. But the real leverage sits in the representational architecture. Better outputs don't come from more intelligence at inference time, they come from compressing ambiguity upfront, reformulating the task before the model ever sees it. Which leads to the real asymmetry: whoever controls the representation layer controls the usable intelligence of the system. It's also why most LLM wrappers are fungible, they don't own the layer that matters.

Norman's Argument reicht weiter als bis zur Context-Schicht. Wenn Werkzeuge nicht Kognition verstärken, sondern die Aufgabe neu definieren — dann gilt das auch für menschliche Aufsicht. Art. 14 EU AI Act setzt voraus, dass ein Mensch eingreift und versteht. Aber wenn das Werkzeug die Aufgabe neu definiert, ist das nicht mehr dieselbe kognitive Handlung. Der Mensch folgt einem anderen Task-Graph — und niemand hat das spezifiziert. Die Grafik zeigt, wo das strukturell wird: Der Diskurs 2026 liegt im Harness-Layer — MCP, Protokolle, Orchestrierung, A2A. Genau dort greifen weder EU AI Act noch NIS2. Precomputation löst ein Latenzproblem im Inference-Pfad. Aber im Harness-Layer entscheidet nicht das Modell, sondern der Orchestrator — und dessen Entscheidungslogik ist weder klassifiziert noch auditierbar. Für das Governance-Problem ist Precomputation keine Antwort. Es ist eine weitere Schicht.

This reminds me of a general theme in software engineering: adding a layer on top of what's already there, to increase the level of abstraction, and hence simplify what sits on top e.g. the remaining code. At one end of the spectrum it's building a domain specific language so that ideas (code) can be expressed more clearly and closer to the world of the problem/people. At the other end it's refactoring some code before you modify its behaviour. You refactor to make the following change easier, then you make the easy change.

Love the Norman callback. His personal-view vs system-view distinction from '91 maps perfectly onto how we build agent interfaces now, except the artifact isn't static anymore. A dashboard that rewrites itself based on what the agent learned last session is closer to a cognitive partner than a cognitive artifact, and I think we're only starting to figure out what that means for how people actually think alongside these systems.

What’s interesting is how this plays out beyond individual cognition. In many real-world systems, we don’t just change tasks through representation - we fragment decision-making itself. Different roles operate on different representations of the same problem, which leads to inconsistent outcomes rather than better ones. So the challenge is not only building better representations, but aligning them across the system so decisions don’t depend on who is looking at them.

This reframes something I've been feeling but couldn't articulate. CLAUDE.md isn't "documentation for AI" — it's a cognitive artifact that changes the task itself. Without it, the task is "explain your codebase to an AI every session." With it, the task becomes "verify the AI understood the representation." Completely different cognitive load. Completely different outcome. The precomputation angle is spot on — I write the representation once, and every Claude Code session reuses it. The cost of creating it is amortized across hundreds of sessions. Norman would probably argue we're not making AI smarter, we're making the task more compatible with how AI already processes context.

André Lindenberg This has direct relevance to the #HolisticMeta #RGEM. Your post, and the cited article, sits squarely in the same problem space RGEM was designed to resolve, and provides a solution to—but from a narrower, engineering-first perspective. At its core, the post is about: -Cognitive artifacts -Context engineering -Representation as the limiting factor for AI systems This aligns almost one-to-one with RGEM’s foundational premise: Intelligence effectiveness is constrained not by computation, but by the quality, structure, and governance of representation. See https://chatgpt.com/share/69dc5a93-4310-832b-b0d8-ca1ca6c289e7

It’s critical to have a transparent and open source provider agnostic harness ! This determines what you can exact from the LLM ! https://github.com/nikhilvallishayee/duh

See more comments

To view or add a comment, sign in

Explore content categories