Bibliographic record
Abstract
Order of the Engineer . As early as the 1950s, some Ohio engineers began to look into extending the Canadian Iron Ring Ceremony into the United States; however, it was not until 1970 that the first American ring ceremony was held at Cleveland State University. Local chapters of the Order of the Engineer, known as Links, began to form, first around Ohio, but then increasingly throughout the country. The movement has continued to spread, but the practice of American engineers wearing a stainless steel pinkie ring has not grown to nearly the extent that Canadian engineers wear their iron (now also mostly stainless steel) rings. See Homer T. Borton, “The Order of the Engineer,” The Bent of Tau Beta Pi , Spring 1978, pp. 35–37; “The Iron Ring,” American Scientist , May–June 1995, pp. 229–232; To Forgive Design: Understanding Failure (Cambridge, Mass.: Harvard University Press, forthcoming), chapter 8. The pledge taken by engineers at the time of their induction into the American Order of the Engineer is known as the “Obligation of an Engineer.” It was modeled after that of the Canadian iron ring tradition and appeared on early membership certificates as follows: Obligation of an Engineer I am an Engineer. In my profession I take deep pride. To it I owe solemn obligations. Since the Stone Age, human progress has been spurred by the engineering genius. Engineers have made usable Nature's vast resources of material and energy for Mankind's benefit. Engineers have vitalized and turned to practical use the principles of science and the means of technology. […]
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.003 | 0.002 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.137 | 0.075 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".