R0021/2026-03-25/Q005 — Assessment

Research	R0021 — Prompt engineering definitions
Run	2026-03-25
Query	Q005

BLUF

Multiple disciplines have gone through a phase of being called "engineering" before formal methodology existed. Software engineering (1968 NATO conferences) is the most famous and best-documented case — the term was deliberately chosen as "provocative" and acknowledged as expressing "a need rather than a reality." Civil engineering predated formal schools by centuries. Knowledge engineering in the 1980s had "little formal process" initially. The pattern recurs: a practice adopts the "engineering" label aspirationally, then either develops formal methodology or retains the label without full formalization.

Probability

Rating: Almost certain (95-99%)

Confidence in assessment: High

Confidence rationale: Multiple documented examples from primary historical sources.

Reasoning Chain

1. NATO 1968 conferences explicitly applied "software engineering" as a provocative label expressing "a need rather than a reality" [SRC01-E01, Medium-High reliability, High relevance]
2. Civil engineering practices predated formal schools (first in 1747) by millennia [SRC02-E01, Medium reliability, Medium-High relevance]
3. Knowledge engineering began with "little formal process" before KADS methodology was developed [SRC03-E01, Medium reliability, High relevance]
4. JUDGMENT: The pattern is clear and recurring. The question for prompt engineering is whether it will follow the formalization path (like software engineering) or remain informal.

Evidence Base Summary

Source	Description	Reliability	Relevance	Key Finding
SRC01	NATO Conferences	Medium-High	High	"Expressed a need rather than a reality"
SRC02	Engineering History	Medium	Medium-High	Practice before label and formal schools
SRC03	Knowledge Engineering	Medium	High	"Little formal process" initially

Collection Synthesis

Dimension	Assessment
Evidence quality	Medium — secondary historical sources, but facts are well-established
Source agreement	High — all sources confirm the pattern
Source independence	Independent — different historical periods and disciplines
Outliers	None

Gaps

Missing Evidence	Impact on Assessment
Genetic engineering formalization history	Minor — would add another example
Requirements engineering evolution	Minor — additional example
Quantitative data on formalization timelines	Moderate — would strengthen pattern analysis

Researcher Bias Check

Declared biases: Researcher may use historical examples to argue prompt engineering follows the same pattern of aspirational labeling.

Influence assessment: The historical examples are factual. The application to prompt engineering is the researcher's argument, not a finding of this research.

Cross-References

Entity	ID	File
Hypotheses	H1, H2, H3	hypotheses/
Sources	SRC01-SRC03	sources/
ACH Matrix	—	ach-matrix.md
Self-Audit	—	self-audit.md