MétaCan
Menu
Back to cohort
Record W4410039870 · doi:10.1017/dsj.2025.9

Methods as a form of engineering knowledge

2025· article· en· W4410039870 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueDesign Science · 2025
Typearticle
Languageen
FieldEngineering
TopicDesign Education and Practice
Canadian institutionsUniversity of Windsor
Fundersnot available
KeywordsComputer science

Abstract

fetched live from OpenAlex

Abstract Methods comprise a significant part of the knowledge engineers are taught and that they use in professional practice. However, methods have been largely neglected in discussions of the nature of engineering knowledge. In particular, methods prove to be hard to track down in the best-known and most influential typology of engineering knowledge, put forward by Walter G. Vincenti in his book What Engineers Know and How They Know It. This article discusses contemporary views of what engineering methods are and what they contain, how methods (fail to) fit into Vincenti’s analysis, and some characteristics of method knowledge. It argues that methods should be seen as a distinct type of engineering knowledge. While characterizing the knowledge that methods include can be done in different ways for different purposes, the core of method knowledge that does not fit into other categories is explicit ‘how-to’ knowledge of procedures, that draw on other types of knowledge.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.724
Threshold uncertainty score0.266

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.041
GPT teacher head0.400
Teacher spread0.359 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it