INQUIRING LINE

How does externalizing tacit expertise into structured rules differ from prompt engineering?

This explores the difference between two ways of shaping LLM behavior: encoding expert knowledge as durable, structured rules baked into an agent's scaffolding, versus iteratively refining the prompt you hand the model — and why that distinction matters for who can use the system and how well it holds up.


This explores the difference between baking expert knowledge into an agent's structure as durable rules versus steering a model through prompt refinement — and the corpus suggests these are not two flavors of the same thing, but interventions at different layers with different ownership and durability. The clearest case for externalized rules comes from an industrial study where embedding domain rules and design principles directly into an agent's scaffolding produced a 206% output-quality jump and let non-experts hit expert-level ratings without specialist oversight Can codified expertise let non-experts match specialist output?. The key move there is that expertise lives in the harness — a stable, reusable component — not in a clever string a user types each session.

Prompt engineering, by contrast, is portrayed in the corpus as an ongoing negotiation between a user and a model rather than a deposit of knowledge. One line of work frames it as iterative alignment, where users repeatedly nudge outputs toward what they already expect, so the result is a co-production of model and user assumptions How much does the user shape what a model generates?. That makes prompts personal and ephemeral — they encode one user's anticipations in one moment. Externalized rules aim for the opposite: knowledge that survives the individual session and transfers to people who don't possess it. The contrast deepens when you notice prompts ride on context that is itself mutable and dissolving — prompt, history, retrieved data, hidden state all shift under you How does AI context differ from conventional software context?, which is exactly the instability structured rules try to remove.

There's a middle ground the corpus maps well: structure imposed on prompting that starts to behave like externalized expertise. Treating arguments through a formal scheme — forcing the model to check warrants and backing it would otherwise skip — turns 'prompting' into something closer to an encoded methodology Can structured argument prompts make LLM reasoning more rigorous?. The 'context as evolving playbook' approach goes further, accumulating and curating knowledge across runs instead of rewriting it, so the playbook becomes a persistent artifact rather than a momentary instruction Can context playbooks prevent knowledge loss during iteration?. And LLM Programs hard-wire control flow around the model, presenting only step-relevant context at each call — expertise expressed as algorithm, not as instruction Can algorithms control LLM reasoning better than LLMs alone?.

Here's the part you might not expect: structure can be a costume. Logically invalid chain-of-thought exemplars perform nearly as well as valid ones, which means models often learn the *form* of reasoning rather than the reasoning itself Does logical validity actually drive chain-of-thought gains?. That's a warning for both camps — a structured rule or a well-shaped prompt can produce the appearance of expertise without the substance. It also explains why the durable, externalized approach tends to win on quality control: when reasoning is externalized into inspectable artifacts like knowledge-graph triples, you can audit and correct the steps rather than trusting that the right form implies the right answer Can structuring reasoning as knowledge graphs help smaller models solve complex tasks?.

The takeaway: prompt engineering optimizes a conversation; externalizing tacit expertise builds an asset. One lives with the user and decays; the other lives in the system and compounds — which is why the case study's gains came from the harness, not from a bigger model or a better prompt. The frontier worth watching is the hybrid zone — playbooks, argument schemes, and program scaffolds — where prompting stops being personal craft and starts becoming transferable infrastructure.


Sources 8 notes

Can codified expertise let non-experts match specialist output?

An industrial case study embedding domain rules and design principles into an LLM agent's scaffolding achieved 206% output-quality improvement and expert-level ratings from non-experts, bypassing the need for specialist oversight. The capability gain came from externalizing tacit expertise into structured harness components, not from model scale.

How much does the user shape what a model generates?

Foundation Priors research shows prompt engineering as divergence minimization between synthetic output and user priors. The refinement process systematically steers generation toward what users already expect, making outputs co-productions of model and user subjectivity.

How does AI context differ from conventional software context?

AI interactions operate on a substrate of constantly shifting context—prompt, history, retrieved data, hidden state—that users cannot internalize like traditional UIs. This structural mutability demands a new design discipline centered on context engineering rather than interface design.

Can structured argument prompts make LLM reasoning more rigorous?

Applying Toulmin's argument model as explicit prompting steps (CQoT) improves LLM reasoning by forcing models to identify warrants and backing rather than skipping implicit premises. The method catches failures that standard chain-of-thought prompting allows.

Can context playbooks prevent knowledge loss during iteration?

The ACE framework treats contexts as evolving playbooks using generation-reflection-curation loops rather than full rewrites. This prevents knowledge loss from compression and detail erosion, achieving +10.6% on agentic tasks and +8.6% on finance without labeled supervision.

Can algorithms control LLM reasoning better than LLMs alone?

LLM Programs embed LLMs within explicit algorithms that manage control flow and state, presenting only step-specific context to each LLM call. This information hiding addresses capability and context window limits while treating complex reasoning as modular, debuggable sub-tasks.

Does logical validity actually drive chain-of-thought gains?

Illogical chain-of-thought exemplars matched valid CoT performance on BIG-Bench Hard, showing that structural properties—not logical validity—drive the gains. The model learns the form of reasoning, not genuine inference.

Can structuring reasoning as knowledge graphs help smaller models solve complex tasks?

Knowledge Graph of Thoughts (KGoT) achieves 29% improvement on GAIA Level 3 tasks using GPT-4o mini by externalizing reasoning into iteratively constructed KG triples. The approach improves transparency, reduces bias, and enables quality control over reasoning steps.

Next inquiring lines