Cargo cult

Description

Copying the surface shape of a successful thing without the underlying causal force that produced it. Named after Pacific cargo cults that imitated airfield rituals expecting cargo to arrive. Generalizes far beyond the anthropological origin — common failure mode in process imitation, ML benchmarks, code patterns “because the senior engineer does it that way,” and any imitation lacking the load-bearing mechanism.

Composition

= shape + force-dynamic. The shape is what gets copied (the visible pattern); the missing force-dynamic is the causal mechanism that originally produced it. Cargo cult is shape without force.

When it applies / triggers on

User-initiated: Trigger-verb signal in user messages is essentially absent — of 16 matches, 14 have real-user-msg triggers but the messages themselves don’t carry cargo-cult-flavored language. The agent reaches for the label as a diagnosis after observing the structural shape (shape-without-force) in the user’s described situation. Four recurring sub-shapes:

• Process-imitation diagnosis — an artifact (lint directive, sprint cadence, code pattern, defensive eslint-disable comment) exists without its causal mechanism. Canonical example: “someone wrote // eslint-disable-next-line comments in a repo that had no active linter — they were doing defensive cargo-cult lint hygiene, anticipating rules that never ran.”
• Uniformity-without-dividend — forced consistency without the cost-curve that justifies it. Canonical example: “this is a textbook case of ‘ambient instrumentation captures the easily-observable signal, not always the load-bearing one’… the uniformity is wrong when the metadata isn’t faithful to content.”
• Methodology-level meta-application — the form applied to the project’s own work (“designing without measuring = shape-without-mechanism”). Shows the form’s domain-generality.
• Catalog-graph role — cargo-cult as the named anti-pattern terminus of graduation-promotion → uniformity-dividend → cargo-cult and the third vertex of the load-bearing ↔ cargo-cult ↔ shape diagnostic triangle.

Agent-initiated: Engine evaluates whether a proposed/existing pattern is actually doing work — most often during architectural review (post-implementation or pre-commit) when a shape “sounds architectural” but doesn’t change observable behavior. 2 of 16 are <task-notification> flavor (elephant evaluating goldfish output for anti-pattern instances). The load-bearing test (“what if we removed this?”) is the agent’s cargo-cult detector.

Vocabulary cues: “cargo cult,” “performative,” “decorative,” “without the underlying,” “without the mechanism,” “sounds architectural,” “doesn’t change observable behavior,” “imitation,” “copying the shape,” “copying the surface,” “shape without force,” “ritual,” “uniformity without dividend.” Note: James himself doesn’t reach for the literal label cargo-cult often — the form is named less often than instantiated; 16-count likely underestimates by 3-5× if the structural-shape-without-mechanism phrasings were captured.

Situation-shape signals: A defensive artifact (lint comment, validator, retry, doc) exists for a constraint that isn’t actually present; uniformly-applied doctrine with no diagnostic for when it earns its keep; copying another project’s structural moves without copying the constraint that motivated them.

Encounters

• “Structures that sound architectural” — KCC design critique: invented structures that don’t change observable behavior. The load-bearing test is the diagnostic.
• Imitating process without understanding why — codebase patterns adopted without the underlying constraint that originally motivated them.
• Uniformity-without-dividend — uniformity dividend’s anti-pattern: forced consistency without the cost-curve that justifies it is cargo cult of standardization.
• Workflow imitation — adopting another team’s process artifacts (standups, retros, sprint cadences) without their cultural force-dynamic.

Composes with

• load-bearing (diagnostic relationship) — the load-bearing test (“what if we removed this?”) is the cargo-cult detector.
• uniformity-dividend (anti-pattern) — uniformity without the dividend mechanism is cargo cult of standardization.

When it doesn’t apply

• Legitimate “fake it till you make it” — imitation acknowledged as exploration toward eventually learning the force-dynamic.
• Aesthetic / ritual contexts — when the shape itself IS the goal (ceremony, art), not the absent mechanism.

Sources

• Anthropological origin (Pacific cargo cults).
• Richard Feynman, Cargo Cult Science (1974).
• Standard in engineering critique tradition.

Canonical exemplars from corpus (T2 2026-05-17)

• Load-bearing × cargo-cult × shape diagnostic triangle (cwd: campconnect, session: idx=0): “Load-bearing is the test for whether shape is doing real work; cargo cult is what happens when shape masquerades as load-bearing. graduation-promotion → creates → uniformity-dividend → anti-pattern → cargo-cult: a three-link causal chain.”
• Ambient instrumentation captures the cheap, not the meaningful (cwd: campconnect, session: idx=13): “This is a textbook case of ‘ambient instrumentation captures the easily-observable signal, not always the load-bearing one.’ … The uniformity is wrong when the metadata it captures isn’t faithful to content.”
• Designing without measuring = shape-without-mechanism (cwd: analogy, session: idx=14): “cargo-cult anti-pattern (designing without measuring is shape-without-mechanism).”
• Defensive cargo-cult lint hygiene (cwd: campconnect, session: idx=15, task-notification): “Someone wrote // eslint-disable-next-line comments in a repo that had no active linter. They were doing defensive cargo-cult lint hygiene — anticipating rules that never ran.”

Trigger pattern (T2): Cargo-cult surfaces when the agent is evaluating whether a proposed/existing pattern is actually doing work — most often during architectural review when the agent notices a shape that “sounds architectural” but doesn’t change observable behavior; trigger-verb signal in user messages is essentially absent.