MétaCan
Menu
Back to cohort
Record W4302569287 · doi:10.56094/jss.v53i3.108

How Safe is Safe Enough? Acceptable Safety Criteria From an Engineering and Legal Perspective

2017· article· en· W4302569287 on OpenAlexaff
Martin Chizek

Bibliographic record

VenueJournal of System Safety · 2017
Typearticle
Languageen
FieldEngineering
TopicSafety Systems Engineering in Autonomy
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsRisk analysis (engineering)Product liabilityProduct (mathematics)BusinessLiabilityReputationContext (archaeology)IncentiveAutomotive industryCompromiseComputer securityEngineeringComputer scienceFinanceEconomics

Abstract

fetched live from OpenAlex

Manufacturers have a vested interest in the safety of their customers, and in protecting their reputation for producing safe products. An additional incentive to produce safe products is avoiding liability when their product is involved in an accident or mishap that results in personal injury and/or property damage. While it is often said that one must never compromise on safety, the fact remains that any product must necessarily be a balance between the level of safety desired and the cost and performance impact of achieving that level of safety. The product manufacturer must make a determination: Is this product (or technology) acceptably safe within the context of current consumer expectations as well as the legal/regulatory framework? Is the residual risk tolerable? This paper presents a methodology to address those questions by reviewing the publicly available information of a recent automotive product liability case, and evaluating whether the product design met current legal and safety engineering best practices.

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 imitation

Not 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.

metaresearch head score (Codex)0.027
metaresearch head score (Gemma)0.090
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.027
Threshold uncertainty score0.145

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0270.090
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0050.002
Science and technology studies0.0040.022
Scholarly communication0.0150.015
Open science0.0040.004
Research integrity0.0090.005
Insufficient payload (model declined to judge)0.0040.001

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.010
GPT teacher head0.234
Teacher spread0.225 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreEmpirical

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".

Quick stats

Citations0
Published2017
Admission routes1
Has abstractyes

Explore more

Same venueJournal of System SafetySame topicSafety Systems Engineering in AutonomyFrench-language works237,207