MétaCan
Menu
Back to cohort
Record W4383500585 · doi:10.1002/9781119863663.ch7

Human–Machine Social Systems: Test and Validation via Military Use Cases

2023· other· en· W4383500585 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

Venuenot available
Typeother
Languageen
FieldSocial Sciences
TopicInnovation, Sustainability, Human-Machine Systems
Canadian institutionsGovernment of CanadaDefence Research and Development Canada
Fundersnot available
KeywordsImmediacySocial intelligenceArtificial intelligenceHuman resourcesComputer scienceTest (biology)Knowledge managementEngineeringOperations researchManagementPsychologySocial psychologyEconomics

Abstract

fetched live from OpenAlex

Global commercial leaders (e.g. Google, Amazon, and Toyota) and governments around the world are heavily investing in intelligent, bidirectional interactions between humans and technologies that involve complex social interactions. The military sector, in particular, is investing in modernization strategies that target artificial intelligence/machine learning (AI/ML) techniques that lend themselves to human–machine teaming in order to prepare for a future of multidomain operations. As with the pioneering empirical approach to human assessment and selection by global military leaders post–World War I [16], the immediacy, complexities, size, diversity, and resource capability of military use cases can generate the foundational underpinnings for shared problems, such as human-machine systems (HMS). When executed with strategic partners (e.g. commercial sector, partner nations), these underpinnings can be extrapolated and validated in multiple application domains. This chapter outlines key social cognitive complexities best examined in situ with real users, and highlights collaboration opportunities with the U.S. military (e.g. Army Project Convergence) as one potential path for in situ test and validation.

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.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Other · Consensus signal: Other
Teacher disagreement score0.305
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0010.000
Insufficient payload (model declined to judge)0.0010.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.043
GPT teacher head0.348
Teacher spread0.305 · 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