PASS 3: Temporal Dynamics
Case 109: Competence To Certify Arms Storage Rooms
Timeline Overview
OWL-Time Temporal Structure 8 relations time: = w3.org/2006/time
Extracted Actions (8)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A accepted or continued serving as Civilian Building and Grounds Division Chief at a U.S. Army installation despite lacking significant training or knowledge in arms, ammunition, and explosive regulations that would foreseeably be required in that role.
Temporal Marker: Prior to the certification request; pre-existing condition established before the central ethical conflict
Mental State: deliberate
Intended Outcome: Fulfill a professional employment role leveraging civil engineering expertise in building and grounds management
Fulfills Obligations:
- Responding to employment opportunity and organizational need
- Applying civil engineering expertise to building and grounds management functions
Guided By Principles:
- Practice within areas of competence
- Public health and safety protection
- Professional integrity in role acceptance
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Career advancement, sense of duty to serve the organization, possible financial incentives, or underestimation of the specialized knowledge gaps the role would expose; Engineer A may have assumed general civil engineering competence would be sufficient or that on-the-job learning would bridge any gaps.
Ethical Tension: Professional ambition and organizational loyalty vs. the NSPE Code obligation to practice only within one's area of competence; the desire to be a team player conflicts with the duty to be honest about one's limitations before accepting responsibility.
Learning Significance: Engineers must conduct a candid self-assessment of competency before accepting roles, not after problems arise; accepting a position creates implied representations of capability that carry ongoing ethical weight, illustrating that ethical obligations begin at the moment of role acceptance.
Stakes: Public and military personnel safety if arms storage is later certified incorrectly; Engineer A's professional license and reputation; institutional trust in engineering certifications; potential criminal or civil liability if an arms storage failure causes injury.
Decision Point: Yes - Story can branch here
- Decline the Division Chief appointment until completing required training in arms, ammunition, and explosive regulations.
- Accept the role conditionally, with a documented agreement that training and a qualified subject-matter expert would be provided before any arms-related certifications were required.
- Accept the role but immediately disclose known competency gaps in writing to supervisors and request assignment of a qualified co-signer for any arms-related certifications.
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Accept_Division_Chief_Role",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the Division Chief appointment until completing required training in arms, ammunition, and explosive regulations.",
"Accept the role conditionally, with a documented agreement that training and a qualified subject-matter expert would be provided before any arms-related certifications were required.",
"Accept the role but immediately disclose known competency gaps in writing to supervisors and request assignment of a qualified co-signer for any arms-related certifications."
],
"proeth-scenario:characterMotivation": "Career advancement, sense of duty to serve the organization, possible financial incentives, or underestimation of the specialized knowledge gaps the role would expose; Engineer A may have assumed general civil engineering competence would be sufficient or that on-the-job learning would bridge any gaps.",
"proeth-scenario:consequencesIfAlternative": [
"Declining may have caused short-term organizational friction or missed career opportunity, but would have prevented the downstream ethical dilemma entirely and preserved professional integrity.",
"A conditional acceptance with documented safeguards could have protected Engineer A and the organization, though it might have been rejected by leadership or ignored, still leaving Engineer A exposed.",
"Immediate written disclosure would have created a paper trail demonstrating good faith, potentially prompting the organization to fund training or assign a qualified co-signer, reducing both safety risk and ethical liability."
],
"proeth-scenario:decisionSignificance": "Engineers must conduct a candid self-assessment of competency before accepting roles, not after problems arise; accepting a position creates implied representations of capability that carry ongoing ethical weight, illustrating that ethical obligations begin at the moment of role acceptance.",
"proeth-scenario:ethicalTension": "Professional ambition and organizational loyalty vs. the NSPE Code obligation to practice only within one\u0027s area of competence; the desire to be a team player conflicts with the duty to be honest about one\u0027s limitations before accepting responsibility.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "Public and military personnel safety if arms storage is later certified incorrectly; Engineer A\u0027s professional license and reputation; institutional trust in engineering certifications; potential criminal or civil liability if an arms storage failure causes injury.",
"proeth:description": "Engineer A accepted or continued serving as Civilian Building and Grounds Division Chief at a U.S. Army installation despite lacking significant training or knowledge in arms, ammunition, and explosive regulations that would foreseeably be required in that role.",
"proeth:foreseenUnintendedEffects": [
"Exposure to requests requiring expertise outside civil engineering competency",
"Potential institutional pressure to perform tasks beyond professional qualifications",
"Risk of being asked to certify compliance with specialized military regulations"
],
"proeth:fulfillsObligation": [
"Responding to employment opportunity and organizational need",
"Applying civil engineering expertise to building and grounds management functions"
],
"proeth:guidedByPrinciple": [
"Practice within areas of competence",
"Public health and safety protection",
"Professional integrity in role acceptance"
],
"proeth:hasAgent": "Engineer A (Civilian Building and Grounds Division Chief, licensed Professional Engineer in civil engineering)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Employment opportunity and organizational service vs. strict competency boundaries",
"proeth:resolutionReasoning": "BER Case 85-3 precedent suggests that accepting a role whose required duties fall outside one\u0027s competency is unethical regardless of employment pressure; Engineer A\u0027s acceptance is ethically questionable to the extent arms storage compliance was a foreseeable duty of the role"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Fulfill a professional employment role leveraging civil engineering expertise in building and grounds management",
"proeth:requiresCapability": [
"Civil engineering expertise (partially applicable to building/grounds management)",
"Knowledge of Army physical security regulations",
"Knowledge of arms, ammunition, and explosive storage regulations",
"Ability to interpret complex cross-referenced Army regulatory frameworks"
],
"proeth:temporalMarker": "Prior to the certification request; pre-existing condition established before the central ethical conflict",
"proeth:violatesObligation": [
"NSPE Code Section II.2.a: Engineers shall practice only in areas of their competence \u2014 accepting a role with foreseeable duties outside competency risks violating this obligation",
"Obligation to assess whether the full scope of role responsibilities falls within professional competency before accepting"
],
"proeth:withinCompetence": false,
"rdfs:label": "Accept Division Chief Role"
}
Description: In BER Case 94-8, Engineer A identified that Engineer B lacked apparent training in foundation design and made the decision to report concerns about Engineer B's competency to the construction contractor.
Temporal Marker: Referenced prior case (BER Case 94-8); historical precedent cited in case discussion
Mental State: deliberate
Intended Outcome: Alert the contractor to the competency concerns regarding Engineer B's qualifications to perform structural footing design, and prompt corrective action to ensure the work is performed by a competent engineer
Fulfills Obligations:
- NSPE Code obligation to report known violations of professional ethical standards
- Obligation to hold paramount the safety, health, and welfare of the public
- Duty to confront incompetent practice and bring concerns to appropriate parties
- Professional obligation to ensure engineering work is performed by competent practitioners
Guided By Principles:
- Public health and safety primacy
- Professional accountability and peer oversight
- Honesty and transparency in professional dealings
- Courage to report ethical violations
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Professional responsibility to protect the public from incompetent engineering work, concern about the safety of the industrial facility and its future occupants or workers, and recognition of the NSPE Code obligation to report known or suspected violations of engineering ethics and competency standards.
Ethical Tension: Professional solidarity and reluctance to report a colleague vs. the overriding duty to protect the public from unsafe engineering practice; loyalty to fellow engineers conflicts with the higher obligation to public safety and honest professional standards.
Learning Significance: Illustrates the affirmative duty engineers have to report competency concerns about other engineers; teaches that silence in the face of known incompetent practice is itself an ethical failure; demonstrates how the reporting obligation interacts with the competency standard in a real case context.
Stakes: If Engineer A does not report, the incompetent foundation design may proceed unchallenged, risking structural failure and harm; if Engineer A does report, Engineer B faces professional consequences but the public is protected; the case outcome informs the analysis of Engineer A's own situation.
Decision Point: Yes - Story can branch here
- Directly confront Engineer B about the competency concern before reporting to the contractor, giving Engineer B an opportunity to voluntarily withdraw from the project.
- Report concerns to a professional engineering licensing board rather than or in addition to the construction contractor, triggering a formal regulatory review.
- Document the concern but take no immediate action, monitoring the project for signs of design deficiency before deciding whether to escalate.
Narrative Role: falling_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Report_Engineer_B_s_Incompetency",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Directly confront Engineer B about the competency concern before reporting to the contractor, giving Engineer B an opportunity to voluntarily withdraw from the project.",
"Report concerns to a professional engineering licensing board rather than or in addition to the construction contractor, triggering a formal regulatory review.",
"Document the concern but take no immediate action, monitoring the project for signs of design deficiency before deciding whether to escalate."
],
"proeth-scenario:characterMotivation": "Professional responsibility to protect the public from incompetent engineering work, concern about the safety of the industrial facility and its future occupants or workers, and recognition of the NSPE Code obligation to report known or suspected violations of engineering ethics and competency standards.",
"proeth-scenario:consequencesIfAlternative": [
"Direct confrontation with Engineer B might resolve the issue more collegially if Engineer B responds ethically, but risks being ignored or leading to conflict without the protective intervention of a third party.",
"Reporting to the licensing board would initiate a formal process with greater authority to intervene, though it is a more severe step that may not be necessary if the contractor acts on the concern.",
"Monitoring without action delays protection of the public and may allow an unsafe design to proceed to construction, making this the least defensible alternative from an ethics standpoint."
],
"proeth-scenario:decisionSignificance": "Illustrates the affirmative duty engineers have to report competency concerns about other engineers; teaches that silence in the face of known incompetent practice is itself an ethical failure; demonstrates how the reporting obligation interacts with the competency standard in a real case context.",
"proeth-scenario:ethicalTension": "Professional solidarity and reluctance to report a colleague vs. the overriding duty to protect the public from unsafe engineering practice; loyalty to fellow engineers conflicts with the higher obligation to public safety and honest professional standards.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "falling_action",
"proeth-scenario:stakes": "If Engineer A does not report, the incompetent foundation design may proceed unchallenged, risking structural failure and harm; if Engineer A does report, Engineer B faces professional consequences but the public is protected; the case outcome informs the analysis of Engineer A\u0027s own situation.",
"proeth:description": "In BER Case 94-8, Engineer A identified that Engineer B lacked apparent training in foundation design and made the decision to report concerns about Engineer B\u0027s competency to the construction contractor.",
"proeth:foreseenUnintendedEffects": [
"Professional conflict with Engineer B",
"Potential disruption to the project timeline",
"Engineer B may be removed from or withdraw from the project"
],
"proeth:fulfillsObligation": [
"NSPE Code obligation to report known violations of professional ethical standards",
"Obligation to hold paramount the safety, health, and welfare of the public",
"Duty to confront incompetent practice and bring concerns to appropriate parties",
"Professional obligation to ensure engineering work is performed by competent practitioners"
],
"proeth:guidedByPrinciple": [
"Public health and safety primacy",
"Professional accountability and peer oversight",
"Honesty and transparency in professional dealings",
"Courage to report ethical violations"
],
"proeth:hasAgent": "Engineer A (licensed Professional Engineer; referenced case BER 94-8, distinct from the Engineer A in the present case)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Professional collegiality and non-interference vs. duty to report competency concerns and protect public safety",
"proeth:resolutionReasoning": "BER Case 94-8 affirmed that Engineer A acted ethically and had an affirmative obligation to report competency concerns; public safety and professional accountability obligations outweigh professional courtesy considerations"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Alert the contractor to the competency concerns regarding Engineer B\u0027s qualifications to perform structural footing design, and prompt corrective action to ensure the work is performed by a competent engineer",
"proeth:requiresCapability": [
"Sufficient engineering knowledge to assess another engineer\u0027s competency for structural design",
"Professional judgment to identify competency gaps",
"Communication skills to articulate concerns to contractor",
"Ethical courage to report concerns despite potential professional friction"
],
"proeth:temporalMarker": "Referenced prior case (BER Case 94-8); historical precedent cited in case discussion",
"proeth:withinCompetence": true,
"rdfs:label": "Report Engineer B\u0027s Incompetency"
}
Description: An Army official formally requested that Engineer A certify that arms storage rooms and racks on the military installation comply with specific, lengthy, and detailed Army physical security, arms, ammunition, and explosive regulations cross-referenced with other Army regulations.
Temporal Marker: The precipitating event of the case; occurred after Engineer A was established in the Division Chief role
Mental State: deliberate
Intended Outcome: Obtain official professional certification of regulatory compliance for arms storage facilities, likely required for operational, audit, or safety documentation purposes
Fulfills Obligations:
- Institutional obligation to ensure arms storage compliance is documented
- Organizational duty to seek professional certification for safety-critical facilities
Guided By Principles:
- Institutional compliance and accountability
- Public and military personnel safety
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: The Army official was fulfilling a routine administrative or regulatory compliance obligation, likely unaware of or indifferent to Engineer A's specific competency gaps; the official may have assumed that the Division Chief title conferred sufficient expertise, or may have been under pressure to complete required compliance documentation.
Ethical Tension: Organizational efficiency and regulatory compliance deadlines vs. the need to ensure that certifications are issued only by genuinely qualified individuals; the official's procedural duty conflicts with Engineer A's professional duty of competence.
Learning Significance: Illustrates how organizational structures can inadvertently pressure engineers into practicing outside their competence; teaches that a formal request from an authority figure does not override an engineer's ethical obligation to refuse work beyond their expertise.
Stakes: If Engineer A complies, a legally and professionally consequential certification is produced without adequate basis; military personnel safety depends on arms storage integrity; Engineer A's license is at direct risk; the Army's regulatory compliance posture could be falsely represented.
Decision Point: Yes - Story can branch here
- The Army official could have verified Engineer A's qualifications in arms and physical security regulations before issuing the request.
- The official could have accompanied the request with access to a qualified subject-matter expert or regulatory specialist to support Engineer A.
- The official could have escalated the request to a higher authority or contracted an outside specialist with demonstrated expertise in Army physical security regulations.
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Request_Certification_of_Compliance",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"The Army official could have verified Engineer A\u0027s qualifications in arms and physical security regulations before issuing the request.",
"The official could have accompanied the request with access to a qualified subject-matter expert or regulatory specialist to support Engineer A.",
"The official could have escalated the request to a higher authority or contracted an outside specialist with demonstrated expertise in Army physical security regulations."
],
"proeth-scenario:characterMotivation": "The Army official was fulfilling a routine administrative or regulatory compliance obligation, likely unaware of or indifferent to Engineer A\u0027s specific competency gaps; the official may have assumed that the Division Chief title conferred sufficient expertise, or may have been under pressure to complete required compliance documentation.",
"proeth-scenario:consequencesIfAlternative": [
"A pre-request qualification check would have immediately surfaced the competency gap, prompting reassignment of the task to a qualified party and preventing the ethical dilemma from arising.",
"Providing expert support could have enabled a legitimate, co-certified inspection, satisfying both the regulatory requirement and the competency standard.",
"Contracting a qualified outside specialist would have ensured an accurate, defensible certification, though at additional cost and time, better protecting both safety and institutional integrity."
],
"proeth-scenario:decisionSignificance": "Illustrates how organizational structures can inadvertently pressure engineers into practicing outside their competence; teaches that a formal request from an authority figure does not override an engineer\u0027s ethical obligation to refuse work beyond their expertise.",
"proeth-scenario:ethicalTension": "Organizational efficiency and regulatory compliance deadlines vs. the need to ensure that certifications are issued only by genuinely qualified individuals; the official\u0027s procedural duty conflicts with Engineer A\u0027s professional duty of competence.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "If Engineer A complies, a legally and professionally consequential certification is produced without adequate basis; military personnel safety depends on arms storage integrity; Engineer A\u0027s license is at direct risk; the Army\u0027s regulatory compliance posture could be falsely represented.",
"proeth:description": "An Army official formally requested that Engineer A certify that arms storage rooms and racks on the military installation comply with specific, lengthy, and detailed Army physical security, arms, ammunition, and explosive regulations cross-referenced with other Army regulations.",
"proeth:foreseenUnintendedEffects": [
"Placing Engineer A in an ethically untenable position by requesting certification outside Engineer A\u0027s competency",
"Potential creation of a false or misleading certification if Engineer A complied",
"Risk to public health and safety if non-compliant storage is falsely certified"
],
"proeth:fulfillsObligation": [
"Institutional obligation to ensure arms storage compliance is documented",
"Organizational duty to seek professional certification for safety-critical facilities"
],
"proeth:guidedByPrinciple": [
"Institutional compliance and accountability",
"Public and military personnel safety"
],
"proeth:hasAgent": "Army Official (unnamed military/institutional authority figure at U.S. Army installation)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Operational compliance documentation urgency vs. assignment of tasks to competent personnel",
"proeth:resolutionReasoning": "The Army official resolved the conflict by directing the existing on-site engineer to certify compliance, prioritizing administrative convenience and operational need over ensuring technical competency, which the BER identifies as creating institutional pressure that engineers must resist"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Obtain official professional certification of regulatory compliance for arms storage facilities, likely required for operational, audit, or safety documentation purposes",
"proeth:requiresCapability": [
"Deep knowledge of Army physical security regulations",
"Expertise in arms, ammunition, and explosive storage regulatory frameworks",
"Ability to conduct exhaustive physical inspection of storage facilities",
"Capacity to interpret complex cross-referenced Army regulatory documents"
],
"proeth:temporalMarker": "The precipitating event of the case; occurred after Engineer A was established in the Division Chief role",
"proeth:violatesObligation": [
"Duty of care to not place a professional engineer in a position requiring certification beyond their competency",
"Institutional obligation to provide adequate resources (training funds) to enable competent performance of required duties"
],
"proeth:withinCompetence": false,
"rdfs:label": "Request Certification of Compliance"
}
Description: The organization (Army installation or relevant authority) decided not to make training funds available for Engineer A to participate in comprehensive training programs that would have provided the necessary expertise in arms storage and physical security regulations.
Temporal Marker: Prior to or concurrent with the certification request; an ongoing resource allocation decision establishing the conditions of the ethical dilemma
Mental State: deliberate
Intended Outcome: Manage organizational budget constraints by not allocating funds to specialized training programs
Fulfills Obligations:
- Budget management and fiscal constraint adherence
Guided By Principles:
- Fiscal responsibility
- Organizational resource management
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Budget constraints, competing organizational priorities, institutional indifference to the specialized nature of arms and physical security regulations, or a failure to recognize that the Division Chief role carried regulatory certification responsibilities requiring specialized training.
Ethical Tension: Fiscal responsibility and resource scarcity vs. the organization's duty to ensure that personnel assigned to safety-critical certification roles are adequately trained; short-term cost savings conflict with long-term safety and professional ethics obligations.
Learning Significance: Demonstrates that organizational decisions upstream of an engineer's individual choices can create ethical traps; teaches that institutions share ethical responsibility for engineer competency and that withholding necessary training is itself an ethically significant act with downstream consequences.
Stakes: Without training, any certification Engineer A provides is unsupported and potentially dangerous; the organization exposes itself to liability; military personnel face real physical safety risks from improperly stored arms; the integrity of the Army's compliance program is undermined.
Decision Point: Yes - Story can branch here
- Prioritize training funds for arms and physical security regulations as a non-negotiable cost of assigning someone to the Division Chief role.
- Temporarily reassign arms storage certification duties to an already-qualified individual while funding constraints persist.
- Seek alternative funding sources, waivers, or interagency support to provide Engineer A with at minimum the minimum competency threshold for arms-related certifications.
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Withhold_Training_Funds",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Prioritize training funds for arms and physical security regulations as a non-negotiable cost of assigning someone to the Division Chief role.",
"Temporarily reassign arms storage certification duties to an already-qualified individual while funding constraints persist.",
"Seek alternative funding sources, waivers, or interagency support to provide Engineer A with at minimum the minimum competency threshold for arms-related certifications."
],
"proeth-scenario:characterMotivation": "Budget constraints, competing organizational priorities, institutional indifference to the specialized nature of arms and physical security regulations, or a failure to recognize that the Division Chief role carried regulatory certification responsibilities requiring specialized training.",
"proeth-scenario:consequencesIfAlternative": [
"Funding the training would have resolved the competency gap, enabled a legitimate certification, and protected both Engineer A and the organization, at the cost of a budget line item.",
"Reassigning certification duties would have maintained compliance integrity and protected Engineer A from an impossible ethical position, though it may have created workload issues for other personnel.",
"Pursuing alternative funding or waivers would have demonstrated organizational good faith and potentially resolved the issue without a budget impact, though it would require administrative effort and time."
],
"proeth-scenario:decisionSignificance": "Demonstrates that organizational decisions upstream of an engineer\u0027s individual choices can create ethical traps; teaches that institutions share ethical responsibility for engineer competency and that withholding necessary training is itself an ethically significant act with downstream consequences.",
"proeth-scenario:ethicalTension": "Fiscal responsibility and resource scarcity vs. the organization\u0027s duty to ensure that personnel assigned to safety-critical certification roles are adequately trained; short-term cost savings conflict with long-term safety and professional ethics obligations.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "Without training, any certification Engineer A provides is unsupported and potentially dangerous; the organization exposes itself to liability; military personnel face real physical safety risks from improperly stored arms; the integrity of the Army\u0027s compliance program is undermined.",
"proeth:description": "The organization (Army installation or relevant authority) decided not to make training funds available for Engineer A to participate in comprehensive training programs that would have provided the necessary expertise in arms storage and physical security regulations.",
"proeth:foreseenUnintendedEffects": [
"Engineer A remains unqualified to perform arms storage compliance certification",
"Organization must either find alternative qualified personnel or pressure unqualified engineer to certify",
"Risk to public health and safety from unqualified compliance assessment"
],
"proeth:fulfillsObligation": [
"Budget management and fiscal constraint adherence"
],
"proeth:guidedByPrinciple": [
"Fiscal responsibility",
"Organizational resource management"
],
"proeth:hasAgent": "Army Installation / Organizational Authority (unnamed institutional decision-maker responsible for resource allocation)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Budget conservation vs. ensuring competent performance of safety-critical regulatory compliance",
"proeth:resolutionReasoning": "The organization resolved the conflict in favor of budget conservation, effectively creating the conditions that make it impossible for Engineer A to ethically comply with the certification request, and placing institutional pressure on Engineer A to act outside the bounds of professional competency"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Manage organizational budget constraints by not allocating funds to specialized training programs",
"proeth:requiresCapability": [
"Organizational budget management",
"Resource allocation decision-making",
"Assessment of training needs for safety-critical functions"
],
"proeth:temporalMarker": "Prior to or concurrent with the certification request; an ongoing resource allocation decision establishing the conditions of the ethical dilemma",
"proeth:violatesObligation": [
"Institutional duty to provide personnel with resources necessary to perform required duties competently",
"Organizational obligation to protect public health and safety by ensuring compliance tasks are performed by qualified individuals",
"Duty not to place engineers in ethically untenable positions by withholding resources needed for competent practice"
],
"proeth:withinCompetence": true,
"rdfs:label": "Withhold Training Funds"
}
Description: The prospective action under ethical review: Engineer A would certify that arms storage rooms and racks comply with detailed Army physical security, arms, ammunition, and explosive regulations despite lacking the training, knowledge, and ability to conduct the exhaustive inspection required to support such a certification.
Temporal Marker: Prospective/hypothetical; the action Engineer A is being asked to take and which the BER evaluates as unethical
Mental State: deliberate
Intended Outcome: Comply with Army official's request, fulfill perceived employment obligation, and provide the required compliance documentation for the installation
Fulfills Obligations:
- Compliance with employer/Army official directive
- Organizational need for compliance documentation (superficially)
Guided By Principles:
- Professional competency boundaries
- Honesty and non-deception in professional representations
- Public health and safety primacy
- Integrity of professional certification
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Desire to fulfill organizational expectations, fear of professional or career consequences for refusing a superior's request, misplaced sense of duty, or rationalization that general engineering judgment could substitute for specific regulatory expertise; Engineer A might also feel pressure to avoid appearing incompetent to superiors.
Ethical Tension: Loyalty to employer and desire to be cooperative vs. the fundamental engineering ethics obligation not to issue misleading or deceptive professional certifications; short-term organizational harmony conflicts with long-term public safety and professional integrity.
Learning Significance: The central ethical violation under review; illustrates that signing a professional certification carries the full weight of the engineer's license and implies genuine competence-based verification; teaches that no amount of organizational pressure justifies a certification the engineer cannot honestly support.
Stakes: Highest stakes in the scenario: military personnel safety if arms storage is deficient; Engineer A's professional license subject to revocation; potential criminal liability for false certification; institutional credibility of Army compliance programs; precedent that professional certifications can be issued without genuine competency.
Decision Point: Yes - Story can branch here
- Refuse to certify and formally document the refusal with a written explanation of the competency gap submitted to the requesting official and Engineer A's own supervisors.
- Issue a qualified or conditional statement explicitly noting the limits of the inspection performed and the areas where Engineer A lacked the expertise to certify, rather than a full compliance certification.
- Request a delay in certification pending either training completion or assignment of a co-certifier with demonstrated expertise in arms storage regulations.
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Certify_Arms_Storage_Compliance",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Refuse to certify and formally document the refusal with a written explanation of the competency gap submitted to the requesting official and Engineer A\u0027s own supervisors.",
"Issue a qualified or conditional statement explicitly noting the limits of the inspection performed and the areas where Engineer A lacked the expertise to certify, rather than a full compliance certification.",
"Request a delay in certification pending either training completion or assignment of a co-certifier with demonstrated expertise in arms storage regulations."
],
"proeth-scenario:characterMotivation": "Desire to fulfill organizational expectations, fear of professional or career consequences for refusing a superior\u0027s request, misplaced sense of duty, or rationalization that general engineering judgment could substitute for specific regulatory expertise; Engineer A might also feel pressure to avoid appearing incompetent to superiors.",
"proeth-scenario:consequencesIfAlternative": [
"Formal refusal with documentation would protect Engineer A\u0027s license, create an institutional record of the problem, and force the organization to address the competency gap through appropriate channels, though it may cause short-term friction.",
"A qualified statement, while not fully satisfying regulatory requirements, would be more honest than a full certification and might prompt the organization to seek a more qualified certifier, though it might also be rejected as insufficient.",
"Requesting a delay is a reasonable middle path that preserves integrity while giving the organization time to resolve the problem, though it depends on the organization being willing to grant the delay."
],
"proeth-scenario:decisionSignificance": "The central ethical violation under review; illustrates that signing a professional certification carries the full weight of the engineer\u0027s license and implies genuine competence-based verification; teaches that no amount of organizational pressure justifies a certification the engineer cannot honestly support.",
"proeth-scenario:ethicalTension": "Loyalty to employer and desire to be cooperative vs. the fundamental engineering ethics obligation not to issue misleading or deceptive professional certifications; short-term organizational harmony conflicts with long-term public safety and professional integrity.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "Highest stakes in the scenario: military personnel safety if arms storage is deficient; Engineer A\u0027s professional license subject to revocation; potential criminal liability for false certification; institutional credibility of Army compliance programs; precedent that professional certifications can be issued without genuine competency.",
"proeth:description": "The prospective action under ethical review: Engineer A would certify that arms storage rooms and racks comply with detailed Army physical security, arms, ammunition, and explosive regulations despite lacking the training, knowledge, and ability to conduct the exhaustive inspection required to support such a certification.",
"proeth:foreseenUnintendedEffects": [
"Issuance of a misleading and deceptive certification beyond Engineer A\u0027s competency",
"Potential false assurance of safety compliance for arms/ammunition/explosive storage",
"Grave danger to public health and safety if non-compliant conditions are falsely certified",
"Violation of state engineering licensure board rules governing professional certifications",
"Personal professional and legal liability for Engineer A"
],
"proeth:fulfillsObligation": [
"Compliance with employer/Army official directive",
"Organizational need for compliance documentation (superficially)"
],
"proeth:guidedByPrinciple": [
"Professional competency boundaries",
"Honesty and non-deception in professional representations",
"Public health and safety primacy",
"Integrity of professional certification"
],
"proeth:hasAgent": "Engineer A (Civilian Building and Grounds Division Chief, licensed Professional Engineer in civil engineering)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Employer compliance and employment stability vs. professional ethical obligations and public safety",
"proeth:resolutionReasoning": "The BER resolves this conflict unambiguously in favor of refusing certification: the combination of Engineer A\u0027s acknowledged lack of competency, the impossibility of performing the required exhaustive inspection, the misleading and deceptive nature of any certification issued under these conditions, and the grave danger to public health and safety means that no competing consideration justifies compliance with the certification request"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Comply with Army official\u0027s request, fulfill perceived employment obligation, and provide the required compliance documentation for the installation",
"proeth:requiresCapability": [
"Specialized knowledge of Army physical security regulations",
"Expertise in arms, ammunition, and explosive storage regulatory compliance",
"Ability to conduct exhaustive physical inspection of storage rooms and racks",
"Capacity to interpret and apply complex cross-referenced Army regulatory frameworks",
"Competency to evaluate storage facility design against detailed regulatory specifications"
],
"proeth:temporalMarker": "Prospective/hypothetical; the action Engineer A is being asked to take and which the BER evaluates as unethical",
"proeth:violatesObligation": [
"NSPE Code Section II.2.a: Engineers shall practice only in areas of their competence",
"NSPE Code Section II.2.b: Engineers shall not affix signatures/seals to documents they are not competent to prepare",
"Obligation to hold paramount the safety, health, and welfare of the public",
"Prohibition on misleading, deceptive, or dishonest professional conduct",
"State engineering licensure board rules governing professional certifications",
"Duty to refuse assignments beyond one\u0027s professional competency"
],
"proeth:withinCompetence": false,
"rdfs:label": "Certify Arms Storage Compliance"
}
Description: The ethically required action identified by the BER: Engineer A should refuse to certify compliance of arms storage rooms and racks with Army regulations, on the grounds that doing so would constitute practice outside the engineer's area of competency and would produce a misleading, deceptive, and dangerous professional certification.
Temporal Marker: Prospective/prescriptive; the action the BER determines Engineer A is ethically obligated to take in response to the Army official's request
Mental State: deliberate
Intended Outcome: Uphold professional ethical obligations by declining to issue a certification beyond Engineer A's competency, protect public health and safety, and maintain the integrity of professional engineering certification
Fulfills Obligations:
- NSPE Code Section II.2.a: Practice only within areas of competence
- NSPE Code Section II.2.b: Do not affix signatures/seals to documents not competently prepared; do not issue misleading certifications
- Obligation to hold paramount the safety, health, and welfare of the public
- Duty of honesty and non-deception in professional representations
- Obligation to resist employer/client pressure that could cause grave danger to public health and safety
- Compliance with state engineering licensure board rules governing professional certifications
Guided By Principles:
- Public health and safety primacy
- Professional competency boundaries
- Honesty and integrity in professional certifications
- Independence from undue employer/client pressure
- Professional courage in upholding ethical standards
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Adherence to professional ethics codes, recognition that the certification would be dishonest and potentially dangerous, concern for the safety of military personnel, and protection of Engineer A's own professional license and reputation; the BER's conclusion reflects the primacy of competence and honesty in engineering ethics.
Ethical Tension: The duty to serve the organization and comply with superior requests vs. the overriding duty to the public's safety and to honest professional practice; the tension between being a cooperative employee and being an ethical engineer is resolved in favor of ethical obligation.
Learning Significance: The BER's definitive ethical conclusion; teaches that refusal is not merely permissible but required when competency is absent; illustrates the hierarchy of engineering ethical obligations where public safety and honest practice outrank organizational loyalty.
Stakes: Refusal protects public safety, Engineer A's license, and the integrity of the certification system; failure to refuse risks all of these; the resolution also signals to the organization that it must address the structural problem of assigning certification duties without providing necessary training.
Narrative Role: resolution
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Refuse_Certification_Assignment",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Refuse certification but also proactively propose a solution, such as identifying a qualified external certifier or outlining the training path needed to resolve the gap.",
"Refuse and simultaneously file a formal complaint or report about the organizational failure to provide necessary training, escalating the issue beyond the immediate certification request.",
"Refuse the specific certification while offering to certify only those elements of the inspection clearly within Engineer A\u0027s civil engineering competence, with explicit written disclaimers on all other elements."
],
"proeth-scenario:characterMotivation": "Adherence to professional ethics codes, recognition that the certification would be dishonest and potentially dangerous, concern for the safety of military personnel, and protection of Engineer A\u0027s own professional license and reputation; the BER\u0027s conclusion reflects the primacy of competence and honesty in engineering ethics.",
"proeth-scenario:consequencesIfAlternative": [
"Proactive problem-solving alongside refusal would demonstrate professionalism and good faith, potentially preserving the working relationship while still upholding ethical standards.",
"Formal escalation would create systemic pressure for the organization to address training funding and role assignment practices, with broader institutional impact but higher personal risk for Engineer A.",
"A partial certification with explicit scope limitations would be more honest than full refusal to engage, but risks being misread as a full certification or creating a false sense of partial compliance."
],
"proeth-scenario:decisionSignificance": "The BER\u0027s definitive ethical conclusion; teaches that refusal is not merely permissible but required when competency is absent; illustrates the hierarchy of engineering ethical obligations where public safety and honest practice outrank organizational loyalty.",
"proeth-scenario:ethicalTension": "The duty to serve the organization and comply with superior requests vs. the overriding duty to the public\u0027s safety and to honest professional practice; the tension between being a cooperative employee and being an ethical engineer is resolved in favor of ethical obligation.",
"proeth-scenario:isDecisionPoint": false,
"proeth-scenario:narrativeRole": "resolution",
"proeth-scenario:stakes": "Refusal protects public safety, Engineer A\u0027s license, and the integrity of the certification system; failure to refuse risks all of these; the resolution also signals to the organization that it must address the structural problem of assigning certification duties without providing necessary training.",
"proeth:description": "The ethically required action identified by the BER: Engineer A should refuse to certify compliance of arms storage rooms and racks with Army regulations, on the grounds that doing so would constitute practice outside the engineer\u0027s area of competency and would produce a misleading, deceptive, and dangerous professional certification.",
"proeth:foreseenUnintendedEffects": [
"Potential conflict with Army official and institutional authority",
"Risk to Engineer A\u0027s employment relationship and career stability",
"Organizational need for compliance documentation remains unmet",
"May prompt organization to seek properly qualified personnel or provide training funding"
],
"proeth:fulfillsObligation": [
"NSPE Code Section II.2.a: Practice only within areas of competence",
"NSPE Code Section II.2.b: Do not affix signatures/seals to documents not competently prepared; do not issue misleading certifications",
"Obligation to hold paramount the safety, health, and welfare of the public",
"Duty of honesty and non-deception in professional representations",
"Obligation to resist employer/client pressure that could cause grave danger to public health and safety",
"Compliance with state engineering licensure board rules governing professional certifications"
],
"proeth:guidedByPrinciple": [
"Public health and safety primacy",
"Professional competency boundaries",
"Honesty and integrity in professional certifications",
"Independence from undue employer/client pressure",
"Professional courage in upholding ethical standards"
],
"proeth:hasAgent": "Engineer A (Civilian Building and Grounds Division Chief, licensed Professional Engineer in civil engineering)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Professional ethical obligations and public safety vs. employment compliance and institutional authority",
"proeth:resolutionReasoning": "The BER resolves this conflict decisively in favor of refusal: the grave danger to public health and safety, the clear and acknowledged lack of competency, the impossibility of performing the required exhaustive inspection, and the misleading and deceptive nature of any certification issued under these conditions collectively create an unambiguous ethical obligation to refuse, notwithstanding employment consequences or institutional pressure"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Uphold professional ethical obligations by declining to issue a certification beyond Engineer A\u0027s competency, protect public health and safety, and maintain the integrity of professional engineering certification",
"proeth:requiresCapability": [
"Professional judgment to assess own competency boundaries",
"Ethical courage to refuse assignments beyond professional competency",
"Communication skills to articulate refusal and explain ethical basis to Army official",
"Knowledge of NSPE Code obligations and applicable state licensure board rules"
],
"proeth:temporalMarker": "Prospective/prescriptive; the action the BER determines Engineer A is ethically obligated to take in response to the Army official\u0027s request",
"proeth:violatesObligation": [
"Employment obligation to comply with Army official\u0027s directive (subordinated to higher professional ethical duty)",
"Organizational expectation of responsiveness to institutional compliance needs"
],
"proeth:withinCompetence": true,
"rdfs:label": "Refuse Certification Assignment"
}
Description: In BER Case 94-8, Engineer B, a chemical engineer, accepted a contract to design structural footings for an industrial facility despite having a degree and background solely in chemical engineering and no apparent subsequent training in foundation design.
Temporal Marker: Referenced prior case (BER Case 94-8); historical precedent cited in case discussion
Mental State: deliberate
Intended Outcome: Fulfill the contract with the construction contractor and provide structural footing design services as retained
Fulfills Obligations:
- Contractual obligation to the construction contractor
Guided By Principles:
- Professional competency boundaries
- Public health and safety primacy
- Integrity in professional service delivery
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Financial opportunity, overconfidence in the transferability of engineering problem-solving skills across disciplines, possible underestimation of the complexity of structural foundation design, or external pressure from a client who may not have fully understood the distinction between chemical and structural engineering.
Ethical Tension: Economic self-interest and client service vs. the obligation to practice only within demonstrated areas of competence; the engineer's general technical capability conflicts with the specific expertise required for safe foundation design.
Learning Significance: Provides a comparative case illustrating that practicing outside one's engineering discipline is an ethics violation regardless of the specific engineering subdiscipline involved; reinforces that the competency standard applies universally across engineering specializations.
Stakes: Structural failure of industrial facility footings could cause building collapse, worker fatalities, and significant property damage; Engineer B's license is at risk; the contractor and facility owner face liability; the case establishes a precedent used to analyze Engineer A's situation.
Decision Point: Yes - Story can branch here
- Decline the structural footing contract and refer the client to a licensed structural or geotechnical engineer with foundation design expertise.
- Accept the contract only as a project manager or coordinator, subcontracting the foundation design work to a qualified structural engineer while being transparent with the client about this arrangement.
- Disclose the competency gap to the client in writing and allow the client to make an informed decision about whether to proceed, potentially with additional qualified oversight.
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Accept_Structural_Footing_Design",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the structural footing contract and refer the client to a licensed structural or geotechnical engineer with foundation design expertise.",
"Accept the contract only as a project manager or coordinator, subcontracting the foundation design work to a qualified structural engineer while being transparent with the client about this arrangement.",
"Disclose the competency gap to the client in writing and allow the client to make an informed decision about whether to proceed, potentially with additional qualified oversight."
],
"proeth-scenario:characterMotivation": "Financial opportunity, overconfidence in the transferability of engineering problem-solving skills across disciplines, possible underestimation of the complexity of structural foundation design, or external pressure from a client who may not have fully understood the distinction between chemical and structural engineering.",
"proeth-scenario:consequencesIfAlternative": [
"Declining and referring would have protected all parties and maintained professional integrity, though Engineer B would have lost the contract revenue.",
"A coordinator role with qualified subcontractor would have served the client\u0027s needs while keeping the actual engineering work within appropriate competency boundaries, a potentially viable and ethical solution.",
"Written disclosure would have transferred informed decision-making to the client, though it does not fully resolve the ethics concern since the engineer still lacks competency regardless of client consent."
],
"proeth-scenario:decisionSignificance": "Provides a comparative case illustrating that practicing outside one\u0027s engineering discipline is an ethics violation regardless of the specific engineering subdiscipline involved; reinforces that the competency standard applies universally across engineering specializations.",
"proeth-scenario:ethicalTension": "Economic self-interest and client service vs. the obligation to practice only within demonstrated areas of competence; the engineer\u0027s general technical capability conflicts with the specific expertise required for safe foundation design.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "Structural failure of industrial facility footings could cause building collapse, worker fatalities, and significant property damage; Engineer B\u0027s license is at risk; the contractor and facility owner face liability; the case establishes a precedent used to analyze Engineer A\u0027s situation.",
"proeth:description": "In BER Case 94-8, Engineer B, a chemical engineer, accepted a contract to design structural footings for an industrial facility despite having a degree and background solely in chemical engineering and no apparent subsequent training in foundation design.",
"proeth:foreseenUnintendedEffects": [
"Performance of structural engineering design outside area of professional competency",
"Risk of deficient structural design endangering public health and safety",
"Potential professional and legal liability for Engineer B"
],
"proeth:fulfillsObligation": [
"Contractual obligation to the construction contractor"
],
"proeth:guidedByPrinciple": [
"Professional competency boundaries",
"Public health and safety primacy",
"Integrity in professional service delivery"
],
"proeth:hasAgent": "Engineer B (licensed Professional Engineer, chemical engineering background; referenced case BER 94-8)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Contractual fulfillment and commercial interest vs. professional competency boundaries and public safety",
"proeth:resolutionReasoning": "BER Case 94-8 resolved that Engineer B acted unethically by accepting the assignment; the professional obligation to practice within competency and protect public safety must override commercial and contractual pressures"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Fulfill the contract with the construction contractor and provide structural footing design services as retained",
"proeth:requiresCapability": [
"Structural engineering expertise",
"Foundation design knowledge and experience",
"Geotechnical assessment capabilities",
"Structural analysis and calculation competency"
],
"proeth:temporalMarker": "Referenced prior case (BER Case 94-8); historical precedent cited in case discussion",
"proeth:violatesObligation": [
"NSPE Code Section II.2.a: Engineers shall practice only in areas of their competence",
"Obligation to hold paramount the safety, health, and welfare of the public",
"Duty to decline assignments outside professional competency"
],
"proeth:withinCompetence": false,
"rdfs:label": "Accept Structural Footing Design"
}
Description: In BER Case 85-3, a licensed Professional Engineer with expertise solely in chemical engineering accepted appointment as county surveyor, a position whose duties included oversight of surveying reports and highway improvement projects, areas outside the engineer's competency.
Temporal Marker: Referenced prior case (BER Case 85-3); historical precedent cited in case discussion
Mental State: deliberate
Intended Outcome: Fulfill the county commissioner appointment, serve in a professional public role, and meet the statutory requirement that the county surveyor position be filled by a licensed PE
Fulfills Obligations:
- Response to county commissioners' appointment
- Satisfaction of statutory PE licensure requirement for the position (technically, but not substantively)
Guided By Principles:
- Professional competency boundaries
- Public health and safety primacy
- Integrity in professional role acceptance
- Non-deception in professional representations
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Civic duty, professional ambition, community recognition, financial compensation, or a belief that general engineering licensure and problem-solving ability would be sufficient for the administrative and oversight functions of the county surveyor role despite the specific technical domains involved.
Ethical Tension: Desire to serve the public and community vs. the obligation to be honest about one's technical limitations before accepting a role with specific competency requirements; public service motivation conflicts with the professional duty of competence.
Learning Significance: Establishes the foundational precedent case for the main scenario; demonstrates that accepting a titled position implies competency representations across all duties of that position, not just those within the engineer's existing expertise; teaches that role titles do not confer competency.
Stakes: Inaccurate oversight of surveying reports could lead to property boundary errors with legal consequences; flawed highway improvement project oversight could result in unsafe road design and traffic accidents; the engineer's license is at risk; public trust in the county surveyor function is undermined.
Decision Point: Yes - Story can branch here
- Decline the county surveyor appointment and recommend that the appointing authority seek a candidate with surveying and civil/transportation engineering credentials.
- Accept the appointment but immediately and publicly disclose the specific competency limitations in surveying and highway design, and formally request that qualified technical deputies be assigned for those functions.
- Accept the appointment for only those administrative functions clearly within competence, and formally recuse from technical sign-offs on surveying reports and highway projects pending acquisition of necessary expertise.
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Action_Accept_County_Surveyor_Position",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Decline the county surveyor appointment and recommend that the appointing authority seek a candidate with surveying and civil/transportation engineering credentials.",
"Accept the appointment but immediately and publicly disclose the specific competency limitations in surveying and highway design, and formally request that qualified technical deputies be assigned for those functions.",
"Accept the appointment for only those administrative functions clearly within competence, and formally recuse from technical sign-offs on surveying reports and highway projects pending acquisition of necessary expertise."
],
"proeth-scenario:characterMotivation": "Civic duty, professional ambition, community recognition, financial compensation, or a belief that general engineering licensure and problem-solving ability would be sufficient for the administrative and oversight functions of the county surveyor role despite the specific technical domains involved.",
"proeth-scenario:consequencesIfAlternative": [
"Declining would have preserved professional integrity and prompted the appointment of a genuinely qualified county surveyor, at the cost of the civic opportunity and any associated benefits.",
"Accepting with public disclosure and deputy assignment would have been a more honest and organizationally responsible approach, though it depends on the appointing authority\u0027s willingness to provide qualified support.",
"Formal recusal from out-of-competence functions would have partially protected the public while acknowledging the limitation, though it might have created administrative confusion about the scope of the surveyor\u0027s authority."
],
"proeth-scenario:decisionSignificance": "Establishes the foundational precedent case for the main scenario; demonstrates that accepting a titled position implies competency representations across all duties of that position, not just those within the engineer\u0027s existing expertise; teaches that role titles do not confer competency.",
"proeth-scenario:ethicalTension": "Desire to serve the public and community vs. the obligation to be honest about one\u0027s technical limitations before accepting a role with specific competency requirements; public service motivation conflicts with the professional duty of competence.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "Inaccurate oversight of surveying reports could lead to property boundary errors with legal consequences; flawed highway improvement project oversight could result in unsafe road design and traffic accidents; the engineer\u0027s license is at risk; public trust in the county surveyor function is undermined.",
"proeth:description": "In BER Case 85-3, a licensed Professional Engineer with expertise solely in chemical engineering accepted appointment as county surveyor, a position whose duties included oversight of surveying reports and highway improvement projects, areas outside the engineer\u0027s competency.",
"proeth:foreseenUnintendedEffects": [
"Performance of oversight duties in surveying and highway engineering outside area of professional competency",
"Inability to effectively oversee surveying reports and highway improvement projects",
"Risk to public safety and infrastructure quality from incompetent oversight"
],
"proeth:fulfillsObligation": [
"Response to county commissioners\u0027 appointment",
"Satisfaction of statutory PE licensure requirement for the position (technically, but not substantively)"
],
"proeth:guidedByPrinciple": [
"Professional competency boundaries",
"Public health and safety primacy",
"Integrity in professional role acceptance",
"Non-deception in professional representations"
],
"proeth:hasAgent": "Engineer (unnamed licensed PE with chemical engineering background; referenced case BER 85-3)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Public service opportunity and institutional appointment vs. professional competency boundaries",
"proeth:resolutionReasoning": "BER Case 85-3 resolved that accepting the position was unethical because it was practically impossible for the engineer to perform effective oversight of surveying reports and highway improvement projects without relevant expertise; the ethical obligation to practice within competency cannot be satisfied by merely holding a PE license in an unrelated field"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Fulfill the county commissioner appointment, serve in a professional public role, and meet the statutory requirement that the county surveyor position be filled by a licensed PE",
"proeth:requiresCapability": [
"Surveying knowledge and expertise",
"Highway engineering competency",
"Ability to effectively oversee surveying reports",
"Capacity to evaluate highway improvement project quality and compliance"
],
"proeth:temporalMarker": "Referenced prior case (BER Case 85-3); historical precedent cited in case discussion",
"proeth:violatesObligation": [
"NSPE Code Section II.2.a: Engineers shall practice only in areas of their competence",
"NSPE Code Section II.2.b: Obligation not to engage in misleading professional representations (holding a position implying competency one does not possess)",
"Obligation to hold paramount the safety, health, and welfare of the public",
"Duty to decline appointments whose required duties fall outside professional competency"
],
"proeth:withinCompetence": false,
"rdfs:label": "Accept County Surveyor Position"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changesDescription: Comprehensive training programs that would enable Engineer A to develop the requisite physical security expertise are rendered effectively unavailable due to the Army installation's decision to withhold funding, creating a structural barrier to competence development.
Temporal Marker: Prior to and concurrent with the certification request; an ongoing institutional state
Activates Constraints:
- Competence_Maintenance_Constraint
- Institutional_Responsibility_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel frustrated, trapped, and unsupported by the institution; organizational decision-makers may be indifferent or unaware of the downstream ethical consequences; external observers may feel concern about systemic institutional negligence.
- engineer_a: Left without institutional support to meet professional obligations; ethical jeopardy intensified
- army_installation: Created conditions for either non-compliance with safety regulations or unethical certification; bears significant institutional moral responsibility
- army_official: May not understand why a seemingly straightforward certification request is problematic
- soldiers_and_public: Increased risk if the funding gap leads to unqualified certification of arms storage facilities
- engineering_profession: Highlights systemic institutional pressures that can compromise professional standards
Learning Moment: Students should understand that institutional resource decisions are not ethically neutral — withholding training funds from professionals assigned to safety-critical roles creates shared moral responsibility for any resulting harm; engineers must recognize when institutional failures shift the ethical landscape.
Ethical Implications: Exposes the tension between individual professional ethics and institutional resource constraints; demonstrates how organizational decisions can create conditions that make ethical compliance structurally difficult; raises questions about distributed moral responsibility in hierarchical institutions.
- Does the institution's failure to fund training mitigate Engineer A's personal ethical responsibility, or does each party bear independent obligations?
- What recourse does Engineer A have when the institution that created the competence gap also controls the resources to close it?
- How should engineering organizations structure role assignments to prevent this type of institutionally-generated ethical dilemma?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Event_Training_Programs_Rendered_Inaccessible",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Does the institution\u0027s failure to fund training mitigate Engineer A\u0027s personal ethical responsibility, or does each party bear independent obligations?",
"What recourse does Engineer A have when the institution that created the competence gap also controls the resources to close it?",
"How should engineering organizations structure role assignments to prevent this type of institutionally-generated ethical dilemma?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer A may feel frustrated, trapped, and unsupported by the institution; organizational decision-makers may be indifferent or unaware of the downstream ethical consequences; external observers may feel concern about systemic institutional negligence.",
"proeth-scenario:ethicalImplications": "Exposes the tension between individual professional ethics and institutional resource constraints; demonstrates how organizational decisions can create conditions that make ethical compliance structurally difficult; raises questions about distributed moral responsibility in hierarchical institutions.",
"proeth-scenario:learningMoment": "Students should understand that institutional resource decisions are not ethically neutral \u2014 withholding training funds from professionals assigned to safety-critical roles creates shared moral responsibility for any resulting harm; engineers must recognize when institutional failures shift the ethical landscape.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"army_installation": "Created conditions for either non-compliance with safety regulations or unethical certification; bears significant institutional moral responsibility",
"army_official": "May not understand why a seemingly straightforward certification request is problematic",
"engineer_a": "Left without institutional support to meet professional obligations; ethical jeopardy intensified",
"engineering_profession": "Highlights systemic institutional pressures that can compromise professional standards",
"soldiers_and_public": "Increased risk if the funding gap leads to unqualified certification of arms storage facilities"
},
"proeth:activatesConstraint": [
"Competence_Maintenance_Constraint",
"Institutional_Responsibility_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/109#Action_Withhold_Training_Funds",
"proeth:causesStateChange": "The pathway for Engineer A to legitimately acquire the necessary competence is closed; the ethical burden shifts partly onto the institution that both assigned the role and denied the means to fulfill it competently.",
"proeth:createsObligation": [
"Institution_Must_Provide_Competence_Resources",
"Engineer_A_Must_Disclose_Training_Barrier_To_Supervisor",
"Seek_Alternative_Qualified_Certifier"
],
"proeth:description": "Comprehensive training programs that would enable Engineer A to develop the requisite physical security expertise are rendered effectively unavailable due to the Army installation\u0027s decision to withhold funding, creating a structural barrier to competence development.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Prior to and concurrent with the certification request; an ongoing institutional state",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Training Programs Rendered Inaccessible"
}
Description: The process of requesting certification reveals that arms storage rooms and racks at the Army installation may not have been verified for compliance with complex physical security regulations, exposing a latent but potentially serious safety and security risk.
Temporal Marker: Concurrent with and following the Request Certification of Compliance action
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Weapons_Security_Compliance_Constraint
- Do_Not_Certify_Without_Competence_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel the weight of genuine danger — this is not merely a procedural issue but a potential public safety matter; the Army Official may not fully appreciate the gravity if they assumed certification was a formality; soldiers and personnel in proximity to storage facilities face real risk.
- engineer_a: Faces heightened ethical pressure — the stakes of providing an unqualified certification are now clearly life-safety related
- army_official: Must confront the possibility that compliance has not been adequately verified
- soldiers_and_personnel: Directly exposed to physical risk if arms storage is non-compliant
- army_installation: Potential liability and operational risk if non-compliance is discovered after an incident
- public: Arms storage security failures can have broad public safety consequences
Learning Moment: Students must understand that engineering certifications in safety-critical domains carry real-world consequences far beyond paperwork — an unqualified certification of arms storage compliance could directly endanger lives, making the ethical obligation to refuse unambiguous.
Ethical Implications: Demonstrates the primacy of public safety in engineering ethics; reveals how procedural requests can mask genuine safety emergencies; highlights that the duty to protect public safety supersedes institutional convenience or hierarchical pressure.
- How does the life-safety dimension of arms storage compliance change the ethical calculus compared to a lower-stakes certification?
- If Engineer A certifies compliance and a security failure later causes harm, how should moral and legal responsibility be apportioned between Engineer A, the Army Official, and the institution?
- What immediate steps should be taken to address the safety risk while the competence and certification issues are being resolved?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Event_Physical_Security_Risk_Exposed",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"How does the life-safety dimension of arms storage compliance change the ethical calculus compared to a lower-stakes certification?",
"If Engineer A certifies compliance and a security failure later causes harm, how should moral and legal responsibility be apportioned between Engineer A, the Army Official, and the institution?",
"What immediate steps should be taken to address the safety risk while the competence and certification issues are being resolved?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A may feel the weight of genuine danger \u2014 this is not merely a procedural issue but a potential public safety matter; the Army Official may not fully appreciate the gravity if they assumed certification was a formality; soldiers and personnel in proximity to storage facilities face real risk.",
"proeth-scenario:ethicalImplications": "Demonstrates the primacy of public safety in engineering ethics; reveals how procedural requests can mask genuine safety emergencies; highlights that the duty to protect public safety supersedes institutional convenience or hierarchical pressure.",
"proeth-scenario:learningMoment": "Students must understand that engineering certifications in safety-critical domains carry real-world consequences far beyond paperwork \u2014 an unqualified certification of arms storage compliance could directly endanger lives, making the ethical obligation to refuse unambiguous.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"army_installation": "Potential liability and operational risk if non-compliance is discovered after an incident",
"army_official": "Must confront the possibility that compliance has not been adequately verified",
"engineer_a": "Faces heightened ethical pressure \u2014 the stakes of providing an unqualified certification are now clearly life-safety related",
"public": "Arms storage security failures can have broad public safety consequences",
"soldiers_and_personnel": "Directly exposed to physical risk if arms storage is non-compliant"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Weapons_Security_Compliance_Constraint",
"Do_Not_Certify_Without_Competence_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/109#Action_Request_Certification_of_Compliance",
"proeth:causesStateChange": "A latent security and safety risk becomes an active concern requiring immediate qualified attention; the stakes of the certification decision are elevated from a procedural matter to a public and military safety issue.",
"proeth:createsObligation": [
"Escalate_Security_Risk_To_Qualified_Authority",
"Ensure_Qualified_Review_Is_Conducted",
"Refuse_To_Provide_Unqualified_Certification",
"Document_Risk_Disclosure"
],
"proeth:description": "The process of requesting certification reveals that arms storage rooms and racks at the Army installation may not have been verified for compliance with complex physical security regulations, exposing a latent but potentially serious safety and security risk.",
"proeth:emergencyStatus": "critical",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "Concurrent with and following the Request Certification of Compliance action",
"proeth:urgencyLevel": "critical",
"rdfs:label": "Physical Security Risk Exposed"
}
Description: The ethical analysis of Engineer A's situation triggers reference to prior Board of Ethical Review cases (BER 85-3 and BER 94-8), which establish relevant precedent regarding engineers practicing outside their competence, making those precedents operative in evaluating Engineer A's obligations.
Temporal Marker: During the Discussion/Analysis phase of the case narrative
Activates Constraints:
- Precedent_Consistency_Constraint
- Competence_Boundary_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: For Engineer A, the existence of precedent may provide clarity and validation for refusing; for the Army Official, the precedent may feel like an abstract obstacle; for students, the activation of precedent demonstrates that professional ethics is a coherent, cumulative system rather than ad hoc judgment.
- engineer_a: Gains ethical grounding and professional cover for refusing the certification; precedent supports the refusal decision
- army_official: The institutional request is now situated within a professional ethics framework that limits Engineer A's options
- engineering_profession: Demonstrates the self-reinforcing nature of professional ethical standards through consistent application of precedent
- bер_and_nspe: Institutional credibility of the ethics review system is reinforced through consistent precedent application
Learning Moment: Students should understand that engineering ethics is not situational or arbitrary — prior cases create binding precedent that professionals and ethics boards are expected to apply consistently; this gives the profession coherence and predictability.
Ethical Implications: Illustrates the role of institutional memory and precedent in professional ethics; demonstrates that individual ethical decisions exist within a broader professional normative framework; raises questions about the balance between rule-based consistency and contextual ethical judgment.
- How does the existence of prior BER precedent change Engineer A's ethical position — does it make the right course of action clearer or does it constrain legitimate contextual judgment?
- Are the analogies between BER 85-3, BER 94-8, and the present case sufficiently strong to make the precedents controlling, or are there morally relevant distinctions?
- What role should precedent play in engineering ethics compared to fields like law where precedent is formally binding?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Event_Prior_BER_Precedents_Activated",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"How does the existence of prior BER precedent change Engineer A\u0027s ethical position \u2014 does it make the right course of action clearer or does it constrain legitimate contextual judgment?",
"Are the analogies between BER 85-3, BER 94-8, and the present case sufficiently strong to make the precedents controlling, or are there morally relevant distinctions?",
"What role should precedent play in engineering ethics compared to fields like law where precedent is formally binding?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "For Engineer A, the existence of precedent may provide clarity and validation for refusing; for the Army Official, the precedent may feel like an abstract obstacle; for students, the activation of precedent demonstrates that professional ethics is a coherent, cumulative system rather than ad hoc judgment.",
"proeth-scenario:ethicalImplications": "Illustrates the role of institutional memory and precedent in professional ethics; demonstrates that individual ethical decisions exist within a broader professional normative framework; raises questions about the balance between rule-based consistency and contextual ethical judgment.",
"proeth-scenario:learningMoment": "Students should understand that engineering ethics is not situational or arbitrary \u2014 prior cases create binding precedent that professionals and ethics boards are expected to apply consistently; this gives the profession coherence and predictability.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"army_official": "The institutional request is now situated within a professional ethics framework that limits Engineer A\u0027s options",
"b\u0435\u0440_and_nspe": "Institutional credibility of the ethics review system is reinforced through consistent precedent application",
"engineer_a": "Gains ethical grounding and professional cover for refusing the certification; precedent supports the refusal decision",
"engineering_profession": "Demonstrates the self-reinforcing nature of professional ethical standards through consistent application of precedent"
},
"proeth:activatesConstraint": [
"Precedent_Consistency_Constraint",
"Competence_Boundary_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/109#Action_Accept_Division_Chief_Role__background___Request_C",
"proeth:causesStateChange": "The ethical evaluation of Engineer A\u0027s situation is now grounded in established professional precedent; the outcome of the analysis is constrained by prior rulings that consistently prohibit engineers from practicing outside their competence.",
"proeth:createsObligation": [
"Apply_Established_Ethical_Precedent",
"Ensure_Analysis_Consistent_With_Prior_BER_Rulings"
],
"proeth:description": "The ethical analysis of Engineer A\u0027s situation triggers reference to prior Board of Ethical Review cases (BER 85-3 and BER 94-8), which establish relevant precedent regarding engineers practicing outside their competence, making those precedents operative in evaluating Engineer A\u0027s obligations.",
"proeth:emergencyStatus": "low",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "During the Discussion/Analysis phase of the case narrative",
"proeth:urgencyLevel": "low",
"rdfs:label": "Prior BER Precedents Activated"
}
Description: The BER analysis concludes that it would be unethical for Engineer A to provide the arms storage compliance certification, formally establishing the ethical verdict and closing the space for legitimate compliance with the Army Official's request.
Temporal Marker: At the conclusion of the BER Discussion and analysis section
Activates Constraints:
- Do_Not_Certify_Without_Competence_Constraint
- PublicSafety_Paramount_Constraint
- Honest_Representation_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: For Engineer A, the conclusion may bring relief (clarity) mixed with concern about institutional consequences of refusal; for the Army Official, the conclusion may be frustrating or surprising; for students, the conclusion demonstrates that ethical analysis can produce clear, actionable verdicts even in complex institutional contexts.
- engineer_a: Professional ethics clearly require refusal; Engineer A now has formal ethical backing for declining but must navigate institutional consequences
- army_official: Must find an alternative qualified certifier; operational timelines may be affected
- army_installation: Faces the need to either fund training, hire qualified personnel, or contract external expertise
- soldiers_and_public: Protected from the risk of an unqualified certification; safety interests are served by the ethical conclusion
- engineering_profession: Professional standards are upheld; the integrity of engineering certification is preserved
Learning Moment: Students should see that ethical analysis in engineering is not merely abstract — it produces concrete, actionable conclusions with real professional and institutional consequences; the conclusion also demonstrates that protecting the public can require resisting institutional pressure.
Ethical Implications: Demonstrates that professional ethics can and must override institutional hierarchy and convenience; reveals the protective function of engineering ethics codes for the public; highlights that ethical clarity does not eliminate practical difficulty — Engineer A still faces real consequences from refusal within an institutional setting.
- The BER concluded it would be unethical to certify — but what are Engineer A's affirmative obligations beyond simply refusing? Does Engineer A have a duty to help find a solution?
- How should Engineer A communicate the refusal to the Army Official in a way that is honest, professional, and constructive rather than merely obstructive?
- If Engineer A refuses and the Army installation cannot find a qualified certifier, what are the broader implications for arms storage safety and institutional accountability?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Event_Unethical_Certification_Conclusion_Reached",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"The BER concluded it would be unethical to certify \u2014 but what are Engineer A\u0027s affirmative obligations beyond simply refusing? Does Engineer A have a duty to help find a solution?",
"How should Engineer A communicate the refusal to the Army Official in a way that is honest, professional, and constructive rather than merely obstructive?",
"If Engineer A refuses and the Army installation cannot find a qualified certifier, what are the broader implications for arms storage safety and institutional accountability?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "For Engineer A, the conclusion may bring relief (clarity) mixed with concern about institutional consequences of refusal; for the Army Official, the conclusion may be frustrating or surprising; for students, the conclusion demonstrates that ethical analysis can produce clear, actionable verdicts even in complex institutional contexts.",
"proeth-scenario:ethicalImplications": "Demonstrates that professional ethics can and must override institutional hierarchy and convenience; reveals the protective function of engineering ethics codes for the public; highlights that ethical clarity does not eliminate practical difficulty \u2014 Engineer A still faces real consequences from refusal within an institutional setting.",
"proeth-scenario:learningMoment": "Students should see that ethical analysis in engineering is not merely abstract \u2014 it produces concrete, actionable conclusions with real professional and institutional consequences; the conclusion also demonstrates that protecting the public can require resisting institutional pressure.",
"proeth-scenario:narrativePacing": "aftermath",
"proeth-scenario:stakeholderConsequences": {
"army_installation": "Faces the need to either fund training, hire qualified personnel, or contract external expertise",
"army_official": "Must find an alternative qualified certifier; operational timelines may be affected",
"engineer_a": "Professional ethics clearly require refusal; Engineer A now has formal ethical backing for declining but must navigate institutional consequences",
"engineering_profession": "Professional standards are upheld; the integrity of engineering certification is preserved",
"soldiers_and_public": "Protected from the risk of an unqualified certification; safety interests are served by the ethical conclusion"
},
"proeth:activatesConstraint": [
"Do_Not_Certify_Without_Competence_Constraint",
"PublicSafety_Paramount_Constraint",
"Honest_Representation_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/109#Action_Request_Certification_of_Compliance__proximate___W",
"proeth:causesStateChange": "The ethical analysis formally forecloses the option of Engineer A providing the certification; Engineer A\u0027s professional and ethical obligations now unambiguously require refusal, and any certification provided would constitute a clear ethics violation.",
"proeth:createsObligation": [
"Engineer_A_Must_Refuse_Certification",
"Engineer_A_Must_Disclose_Incompetence_To_Army_Official",
"Institution_Must_Identify_Qualified_Certifier",
"Engineer_A_Must_Document_Refusal_And_Rationale"
],
"proeth:description": "The BER analysis concludes that it would be unethical for Engineer A to provide the arms storage compliance certification, formally establishing the ethical verdict and closing the space for legitimate compliance with the Army Official\u0027s request.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "At the conclusion of the BER Discussion and analysis section",
"proeth:urgencyLevel": "high",
"rdfs:label": "Unethical Certification Conclusion Reached"
}
Description: Upon Engineer A's acceptance of the Division Chief role, a structural mismatch between the broad responsibilities of the position and Engineer A's actual specialized competence in civil engineering (but not physical security) is instantiated, creating latent ethical risk.
Temporal Marker: At the moment Engineer A accepted the Division Chief role
Activates Constraints:
- Competence_Boundary_Constraint
- Role_Scope_Awareness_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: At the time of acceptance, Engineer A may have been unaware of the full scope of physical security responsibilities; retrospectively, there is a sense of an avoidable trap being set; institutional actors may have been negligent or indifferent about competence matching.
- engineer_a: Placed in a structurally compromised position from the outset; future ethical dilemmas are made more likely
- army_installation: Created conditions for eventual ethics violations by not verifying competence at role assignment
- army_official: Operating under a false assumption that the Division Chief role is filled by someone competent for all its responsibilities
- engineering_profession: Highlights the risk of role creep and title-based assumptions about competence
Learning Moment: Students should learn that the ethical obligations of competence begin at role acceptance — engineers have a duty to assess whether a role's full responsibilities fall within their competence before accepting, and to disclose limitations if they do not.
Ethical Implications: Reveals that ethical obligations attach to role acceptance, not just task execution; demonstrates how institutional role design and individual professional judgment interact to create or prevent ethical risk; highlights the importance of proactive competence disclosure over reactive refusal.
- Did Engineer A have an ethical obligation to investigate the full scope of the Division Chief role's responsibilities before accepting, and if so, what should that investigation have included?
- How should institutions structure role assignments to prevent competence mismatches, and what is the engineer's responsibility when institutional processes fail?
- Is there a meaningful ethical difference between accepting a role knowing you lack competence for some responsibilities versus discovering the gap only after acceptance?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Event_Role-Competence_Mismatch_Created",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Did Engineer A have an ethical obligation to investigate the full scope of the Division Chief role\u0027s responsibilities before accepting, and if so, what should that investigation have included?",
"How should institutions structure role assignments to prevent competence mismatches, and what is the engineer\u0027s responsibility when institutional processes fail?",
"Is there a meaningful ethical difference between accepting a role knowing you lack competence for some responsibilities versus discovering the gap only after acceptance?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "At the time of acceptance, Engineer A may have been unaware of the full scope of physical security responsibilities; retrospectively, there is a sense of an avoidable trap being set; institutional actors may have been negligent or indifferent about competence matching.",
"proeth-scenario:ethicalImplications": "Reveals that ethical obligations attach to role acceptance, not just task execution; demonstrates how institutional role design and individual professional judgment interact to create or prevent ethical risk; highlights the importance of proactive competence disclosure over reactive refusal.",
"proeth-scenario:learningMoment": "Students should learn that the ethical obligations of competence begin at role acceptance \u2014 engineers have a duty to assess whether a role\u0027s full responsibilities fall within their competence before accepting, and to disclose limitations if they do not.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"army_installation": "Created conditions for eventual ethics violations by not verifying competence at role assignment",
"army_official": "Operating under a false assumption that the Division Chief role is filled by someone competent for all its responsibilities",
"engineer_a": "Placed in a structurally compromised position from the outset; future ethical dilemmas are made more likely",
"engineering_profession": "Highlights the risk of role creep and title-based assumptions about competence"
},
"proeth:activatesConstraint": [
"Competence_Boundary_Constraint",
"Role_Scope_Awareness_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/109#Action_Accept_Division_Chief_Role",
"proeth:causesStateChange": "Engineer A is now formally responsible for tasks that may exceed competence boundaries; the institutional expectation and Engineer A\u0027s actual capability are misaligned from the outset.",
"proeth:createsObligation": [
"Engineer_A_Must_Identify_Competence_Gaps_In_Role",
"Engineer_A_Must_Seek_Training_Or_Disclose_Limitations",
"Institution_Must_Verify_Competence_At_Role_Assignment"
],
"proeth:description": "Upon Engineer A\u0027s acceptance of the Division Chief role, a structural mismatch between the broad responsibilities of the position and Engineer A\u0027s actual specialized competence in civil engineering (but not physical security) is instantiated, creating latent ethical risk.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "At the moment Engineer A accepted the Division Chief role",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Role-Competence Mismatch Created"
}
Description: Engineer A's lack of training and knowledge in Army physical security regulations becomes apparent upon receiving the certification request, exposing a critical mismatch between assigned responsibilities and actual expertise.
Temporal Marker: Upon receipt of certification request from Army Official
Activates Constraints:
- Competence_Boundary_Constraint
- Public_Safety_Paramount_Constraint
- Honest_Representation_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A likely experiences anxiety, self-doubt, and professional discomfort upon recognizing the mismatch; the Army Official may be unaware of the problem and thus feels no tension yet; observers familiar with NSPE ethics codes would recognize this as a foreseeable institutional failure.
- engineer_a: Placed in an immediate ethical dilemma with professional license and integrity at stake
- army_official: Unaware of the gap; may face operational delays if Engineer A refuses or escalates
- army_installation: Systemic vulnerability exposed — role assignments may not be matched to required competencies
- soldiers_and_public: Latent safety risk if arms storage compliance is certified by an unqualified engineer
- engineering_profession: Integrity of professional certification process is at risk if unqualified certifications are issued
Learning Moment: Students should recognize that accepting a role does not automatically confer competence for all tasks within that role; the moment a competence gap is discovered, an ethical obligation to disclose and decline is immediately activated under NSPE Code principles.
Ethical Implications: Reveals tension between institutional loyalty and professional integrity; highlights how organizational role assignments can inadvertently pressure engineers to exceed their competence boundaries; demonstrates that the duty to practice only within areas of competence is non-negotiable regardless of institutional pressure.
- Should Engineer A have anticipated this competence gap before accepting the Division Chief role, and does that prior decision affect current ethical obligations?
- How does the institutional failure (withholding training funds) redistribute moral responsibility between Engineer A and the Army installation?
- At what threshold does a competence gap become an ethical obligation to refuse, rather than an opportunity to seek remediation?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/109#Event_Competence_Gap_Revealed",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Should Engineer A have anticipated this competence gap before accepting the Division Chief role, and does that prior decision affect current ethical obligations?",
"How does the institutional failure (withholding training funds) redistribute moral responsibility between Engineer A and the Army installation?",
"At what threshold does a competence gap become an ethical obligation to refuse, rather than an opportunity to seek remediation?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A likely experiences anxiety, self-doubt, and professional discomfort upon recognizing the mismatch; the Army Official may be unaware of the problem and thus feels no tension yet; observers familiar with NSPE ethics codes would recognize this as a foreseeable institutional failure.",
"proeth-scenario:ethicalImplications": "Reveals tension between institutional loyalty and professional integrity; highlights how organizational role assignments can inadvertently pressure engineers to exceed their competence boundaries; demonstrates that the duty to practice only within areas of competence is non-negotiable regardless of institutional pressure.",
"proeth-scenario:learningMoment": "Students should recognize that accepting a role does not automatically confer competence for all tasks within that role; the moment a competence gap is discovered, an ethical obligation to disclose and decline is immediately activated under NSPE Code principles.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"army_installation": "Systemic vulnerability exposed \u2014 role assignments may not be matched to required competencies",
"army_official": "Unaware of the gap; may face operational delays if Engineer A refuses or escalates",
"engineer_a": "Placed in an immediate ethical dilemma with professional license and integrity at stake",
"engineering_profession": "Integrity of professional certification process is at risk if unqualified certifications are issued",
"soldiers_and_public": "Latent safety risk if arms storage compliance is certified by an unqualified engineer"
},
"proeth:activatesConstraint": [
"Competence_Boundary_Constraint",
"Public_Safety_Paramount_Constraint",
"Honest_Representation_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/109#Action_Request_Certification_of_Compliance",
"proeth:causesStateChange": "Engineer A transitions from passive role-holder to active ethical decision point; the hidden gap between role expectations and actual qualifications becomes operationally consequential.",
"proeth:createsObligation": [
"Disclose_Incompetence_To_Supervisor",
"Seek_Qualified_Alternative",
"Decline_If_Unqualified",
"Notify_Army_Official_Of_Limitation"
],
"proeth:description": "Engineer A\u0027s lack of training and knowledge in Army physical security regulations becomes apparent upon receiving the certification request, exposing a critical mismatch between assigned responsibilities and actual expertise.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Upon receipt of certification request from Army Official",
"proeth:urgencyLevel": "high",
"rdfs:label": "Competence Gap Revealed"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: Upon Engineer A's acceptance of the Division Chief role, a structural mismatch between the broad responsibilities of the position and Engineer A's actual domain expertise was created
Necessary Factors (NESS):
- Engineer A's acceptance of a role with responsibilities exceeding current competence
- The Division Chief role requiring knowledge of Army physical security regulations
- Engineer A lacking prior training in physical security compliance
Sufficient Factors:
- Acceptance of role + absence of requisite physical security expertise + no immediate remediation plan
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Accept Division Chief Role (Action 1)
Engineer A accepts or continues serving as Civilian Building and Grounds Division Chief without verifying full scope of compliance responsibilities -
Role-Competence Mismatch Created (Event 6)
The gap between the role's physical security regulatory demands and Engineer A's actual expertise becomes structurally embedded in the position -
Training Programs Rendered Inaccessible (Event 2)
Withholding of training funds prevents Engineer A from closing the competence gap after the mismatch is established -
Competence Gap Revealed (Event 1)
The certification request exposes Engineer A's lack of training and knowledge in Army physical security regulations -
Unethical Certification Conclusion Reached (Event 5)
BER concludes it would be unethical for Engineer A to certify compliance given the unresolved competence gap
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/109#CausalChain_b6ba2357",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Upon Engineer A\u0027s acceptance of the Division Chief role, a structural mismatch between the broad responsibilities of the position and Engineer A\u0027s actual domain expertise was created",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A accepts or continues serving as Civilian Building and Grounds Division Chief without verifying full scope of compliance responsibilities",
"proeth:element": "Accept Division Chief Role (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "The gap between the role\u0027s physical security regulatory demands and Engineer A\u0027s actual expertise becomes structurally embedded in the position",
"proeth:element": "Role-Competence Mismatch Created (Event 6)",
"proeth:step": 2
},
{
"proeth:description": "Withholding of training funds prevents Engineer A from closing the competence gap after the mismatch is established",
"proeth:element": "Training Programs Rendered Inaccessible (Event 2)",
"proeth:step": 3
},
{
"proeth:description": "The certification request exposes Engineer A\u0027s lack of training and knowledge in Army physical security regulations",
"proeth:element": "Competence Gap Revealed (Event 1)",
"proeth:step": 4
},
{
"proeth:description": "BER concludes it would be unethical for Engineer A to certify compliance given the unresolved competence gap",
"proeth:element": "Unethical Certification Conclusion Reached (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Accept Division Chief Role (Action 1)",
"proeth:counterfactual": "Had Engineer A declined the role or ensured competence-building before acceptance, the mismatch would not have been created; had the role\u0027s requirements been narrower or matched Engineer A\u0027s expertise, no mismatch would exist",
"proeth:effect": "Role-Competence Mismatch Created (Event 6)",
"proeth:necessaryFactors": [
"Engineer A\u0027s acceptance of a role with responsibilities exceeding current competence",
"The Division Chief role requiring knowledge of Army physical security regulations",
"Engineer A lacking prior training in physical security compliance"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Acceptance of role + absence of requisite physical security expertise + no immediate remediation plan"
],
"proeth:withinAgentControl": true
}
Causal Language: The organization decided not to make training funds available, rendering comprehensive training programs that would enable Engineer A to develop the requisite physical security knowledge inaccessible
Necessary Factors (NESS):
- Organizational authority over training budget allocation
- Training programs existing but requiring funded access
- Engineer A's dependence on organizational resources to obtain specialized regulatory training
Sufficient Factors:
- Denial of training funds + absence of alternative free or self-funded training pathways + Engineer A's inability to independently acquire physical security certification
Responsibility Attribution:
Agent: Army installation or relevant organizational authority
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Withhold Training Funds (Action 3)
The organization decides not to allocate training funds necessary for Engineer A to acquire physical security regulatory knowledge -
Training Programs Rendered Inaccessible (Event 2)
Without funding, Engineer A cannot access the comprehensive training programs needed to meet the role's compliance demands -
Competence Gap Revealed (Event 1)
The certification request surfaces Engineer A's unresolved lack of training in Army physical security regulations -
Physical Security Risk Exposed (Event 3)
The certification process reveals that arms storage rooms and racks may not meet required standards, with no qualified certifier available internally -
Unethical Certification Conclusion Reached (Event 5)
BER determines that certifying compliance without requisite knowledge would be unethical, leaving the organization without a compliant certification pathway
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/109#CausalChain_a218cf4a",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "The organization decided not to make training funds available, rendering comprehensive training programs that would enable Engineer A to develop the requisite physical security knowledge inaccessible",
"proeth:causalSequence": [
{
"proeth:description": "The organization decides not to allocate training funds necessary for Engineer A to acquire physical security regulatory knowledge",
"proeth:element": "Withhold Training Funds (Action 3)",
"proeth:step": 1
},
{
"proeth:description": "Without funding, Engineer A cannot access the comprehensive training programs needed to meet the role\u0027s compliance demands",
"proeth:element": "Training Programs Rendered Inaccessible (Event 2)",
"proeth:step": 2
},
{
"proeth:description": "The certification request surfaces Engineer A\u0027s unresolved lack of training in Army physical security regulations",
"proeth:element": "Competence Gap Revealed (Event 1)",
"proeth:step": 3
},
{
"proeth:description": "The certification process reveals that arms storage rooms and racks may not meet required standards, with no qualified certifier available internally",
"proeth:element": "Physical Security Risk Exposed (Event 3)",
"proeth:step": 4
},
{
"proeth:description": "BER determines that certifying compliance without requisite knowledge would be unethical, leaving the organization without a compliant certification pathway",
"proeth:element": "Unethical Certification Conclusion Reached (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Withhold Training Funds (Action 3)",
"proeth:counterfactual": "Had training funds been allocated, Engineer A could have developed the necessary competence in Army physical security regulations, potentially resolving the mismatch before the certification request arose",
"proeth:effect": "Training Programs Rendered Inaccessible (Event 2)",
"proeth:necessaryFactors": [
"Organizational authority over training budget allocation",
"Training programs existing but requiring funded access",
"Engineer A\u0027s dependence on organizational resources to obtain specialized regulatory training"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Army installation or relevant organizational authority",
"proeth:sufficientFactors": [
"Denial of training funds + absence of alternative free or self-funded training pathways + Engineer A\u0027s inability to independently acquire physical security certification"
],
"proeth:withinAgentControl": true
}
Causal Language: The BER analysis concludes that it would be unethical for Engineer A to provide the arms storage compliance certification given the lack of requisite knowledge, and the prospective act of certifying would expose the public and military personnel to unverified physical security risks
Necessary Factors (NESS):
- Engineer A proceeding to certify despite known competence gap
- The certification carrying legal and safety weight regarding arms storage security
- No independent verification or qualified co-signer involved in the certification
Sufficient Factors:
- Unqualified certification + reliance by Army on that certification for physical security decisions + absence of independent expert review
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Role-Competence Mismatch Created (Event 6)
Engineer A holds a role whose compliance responsibilities exceed demonstrated expertise -
Training Programs Rendered Inaccessible (Event 2)
Funding denial prevents Engineer A from resolving the competence gap -
Request Certification of Compliance (Action 2)
Army official requests Engineer A certify arms storage compliance despite unresolved competence gap -
Certify Arms Storage Compliance (Action 4) [prospective]
Engineer A proceeds to certify compliance without requisite knowledge, misrepresenting competence -
Unethical Certification Conclusion Reached (Event 5)
BER determines this action violates engineering ethics codes; physical security risk is falsely attested as resolved
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/109#CausalChain_e500caff",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "The BER analysis concludes that it would be unethical for Engineer A to provide the arms storage compliance certification given the lack of requisite knowledge, and the prospective act of certifying would expose the public and military personnel to unverified physical security risks",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A holds a role whose compliance responsibilities exceed demonstrated expertise",
"proeth:element": "Role-Competence Mismatch Created (Event 6)",
"proeth:step": 1
},
{
"proeth:description": "Funding denial prevents Engineer A from resolving the competence gap",
"proeth:element": "Training Programs Rendered Inaccessible (Event 2)",
"proeth:step": 2
},
{
"proeth:description": "Army official requests Engineer A certify arms storage compliance despite unresolved competence gap",
"proeth:element": "Request Certification of Compliance (Action 2)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A proceeds to certify compliance without requisite knowledge, misrepresenting competence",
"proeth:element": "Certify Arms Storage Compliance (Action 4) [prospective]",
"proeth:step": 4
},
{
"proeth:description": "BER determines this action violates engineering ethics codes; physical security risk is falsely attested as resolved",
"proeth:element": "Unethical Certification Conclusion Reached (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Certify Arms Storage Compliance (Action 4) [prospective]",
"proeth:counterfactual": "If Engineer A refuses to certify (Action 5), the ethical violation does not occur; the physical security risk remains exposed but is not falsely attested to, preserving the integrity of the safety review process",
"proeth:effect": "Unethical Certification Conclusion Reached (Event 5) and Physical Security Risk Exposed (Event 3)",
"proeth:necessaryFactors": [
"Engineer A proceeding to certify despite known competence gap",
"The certification carrying legal and safety weight regarding arms storage security",
"No independent verification or qualified co-signer involved in the certification"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Unqualified certification + reliance by Army on that certification for physical security decisions + absence of independent expert review"
],
"proeth:withinAgentControl": true
}
Causal Language: An Army official formally requested that Engineer A certify compliance, which revealed Engineer A's lack of training and knowledge in Army physical security regulations and exposed that arms storage rooms and racks at the installation may not meet required standards
Necessary Factors (NESS):
- Formal certification request directed specifically at Engineer A
- The certification requiring domain-specific knowledge Engineer A did not possess
- The arms storage facilities potentially being non-compliant or unverified
Sufficient Factors:
- Certification request + Engineer A's pre-existing competence gap + absence of a qualified alternative certifier
Responsibility Attribution:
Agent: Army official issuing the certification request
Type: indirect
Within Agent Control:
Yes
Causal Sequence:
-
Request Certification of Compliance (Action 2)
Army official formally requests Engineer A certify that arms storage rooms and racks meet regulatory standards -
Competence Gap Revealed (Event 1)
Engineer A's lack of training in Army physical security regulations becomes apparent as Engineer A attempts to evaluate the certification request -
Physical Security Risk Exposed (Event 3)
The certification process surfaces the possibility that arms storage facilities are non-compliant or unverified -
Prior BER Precedents Activated (Event 4)
The ethical dilemma triggers reference to BER Cases 94-8 and 85-3 regarding engineers practicing outside their competence -
Unethical Certification Conclusion Reached (Event 5)
BER concludes certification by Engineer A would be unethical, and Engineer A should refuse
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/109#CausalChain_7a4fc120",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "An Army official formally requested that Engineer A certify compliance, which revealed Engineer A\u0027s lack of training and knowledge in Army physical security regulations and exposed that arms storage rooms and racks at the installation may not meet required standards",
"proeth:causalSequence": [
{
"proeth:description": "Army official formally requests Engineer A certify that arms storage rooms and racks meet regulatory standards",
"proeth:element": "Request Certification of Compliance (Action 2)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A\u0027s lack of training in Army physical security regulations becomes apparent as Engineer A attempts to evaluate the certification request",
"proeth:element": "Competence Gap Revealed (Event 1)",
"proeth:step": 2
},
{
"proeth:description": "The certification process surfaces the possibility that arms storage facilities are non-compliant or unverified",
"proeth:element": "Physical Security Risk Exposed (Event 3)",
"proeth:step": 3
},
{
"proeth:description": "The ethical dilemma triggers reference to BER Cases 94-8 and 85-3 regarding engineers practicing outside their competence",
"proeth:element": "Prior BER Precedents Activated (Event 4)",
"proeth:step": 4
},
{
"proeth:description": "BER concludes certification by Engineer A would be unethical, and Engineer A should refuse",
"proeth:element": "Unethical Certification Conclusion Reached (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Request Certification of Compliance (Action 2)",
"proeth:counterfactual": "Without the certification request, Engineer A\u0027s competence gap might have remained latent and the physical security risk unexamined; the request acted as the trigger that made both visible",
"proeth:effect": "Competence Gap Revealed (Event 1) and Physical Security Risk Exposed (Event 3)",
"proeth:necessaryFactors": [
"Formal certification request directed specifically at Engineer A",
"The certification requiring domain-specific knowledge Engineer A did not possess",
"The arms storage facilities potentially being non-compliant or unverified"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "Army official issuing the certification request",
"proeth:sufficientFactors": [
"Certification request + Engineer A\u0027s pre-existing competence gap + absence of a qualified alternative certifier"
],
"proeth:withinAgentControl": true
}
Causal Language: The ethical analysis of Engineer A's situation triggers reference to prior Board of Ethical Review cases (BER 94-8 and BER 85-3), which establish that engineers practicing outside their area of competence violate professional ethics codes, thereby grounding the BER's conclusion that Engineer A must refuse the certification
Necessary Factors (NESS):
- Existence of prior BER precedents addressing competence boundaries
- Factual similarity between Engineer A's situation and prior cases (engineers accepting roles or tasks outside their expertise)
- BER's reliance on precedent-based reasoning to reach ethical conclusions
Sufficient Factors:
- Activated precedents (BER 94-8 and 85-3) + factual analogy to Engineer A's case + NSPE Code provisions on competence = sufficient basis for the ethical refusal conclusion
Responsibility Attribution:
Agent: Engineer A (as the agent who must act on the BER conclusion)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Competence Gap Revealed (Event 1)
The certification request surfaces Engineer A's lack of physical security regulatory expertise -
Prior BER Precedents Activated (Event 4)
BER analysis references Cases 94-8 (Engineer B accepting structural footing design outside chemical engineering expertise) and 85-3 (PE accepting county surveyor role outside competence) as analogous situations -
Unethical Certification Conclusion Reached (Event 5)
BER concludes, grounded in precedent and NSPE Code, that certifying compliance without requisite knowledge is unethical -
Refuse Certification Assignment (Action 5)
The ethically required action identified: Engineer A must refuse to certify compliance and communicate the competence limitation to the requesting authority -
Physical Security Risk Exposed (Event 3) — properly escalated
By refusing, Engineer A ensures the physical security risk is not falsely attested, preserving the integrity of the safety process and prompting the organization to seek a qualified certifier
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/109#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/109#CausalChain_842a6599",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "The ethical analysis of Engineer A\u0027s situation triggers reference to prior Board of Ethical Review cases (BER 94-8 and BER 85-3), which establish that engineers practicing outside their area of competence violate professional ethics codes, thereby grounding the BER\u0027s conclusion that Engineer A must refuse the certification",
"proeth:causalSequence": [
{
"proeth:description": "The certification request surfaces Engineer A\u0027s lack of physical security regulatory expertise",
"proeth:element": "Competence Gap Revealed (Event 1)",
"proeth:step": 1
},
{
"proeth:description": "BER analysis references Cases 94-8 (Engineer B accepting structural footing design outside chemical engineering expertise) and 85-3 (PE accepting county surveyor role outside competence) as analogous situations",
"proeth:element": "Prior BER Precedents Activated (Event 4)",
"proeth:step": 2
},
{
"proeth:description": "BER concludes, grounded in precedent and NSPE Code, that certifying compliance without requisite knowledge is unethical",
"proeth:element": "Unethical Certification Conclusion Reached (Event 5)",
"proeth:step": 3
},
{
"proeth:description": "The ethically required action identified: Engineer A must refuse to certify compliance and communicate the competence limitation to the requesting authority",
"proeth:element": "Refuse Certification Assignment (Action 5)",
"proeth:step": 4
},
{
"proeth:description": "By refusing, Engineer A ensures the physical security risk is not falsely attested, preserving the integrity of the safety process and prompting the organization to seek a qualified certifier",
"proeth:element": "Physical Security Risk Exposed (Event 3) \u2014 properly escalated",
"proeth:step": 5
}
],
"proeth:cause": "Prior BER Precedents Activated (Event 4)",
"proeth:counterfactual": "Without applicable precedents, the BER might still reach the same conclusion via first-principles analysis of the NSPE Code; however, the precedents strengthen and accelerate the ethical determination, making refusal the clearly required action",
"proeth:effect": "Refuse Certification Assignment (Action 5) \u2014 ethically required conclusion",
"proeth:necessaryFactors": [
"Existence of prior BER precedents addressing competence boundaries",
"Factual similarity between Engineer A\u0027s situation and prior cases (engineers accepting roles or tasks outside their expertise)",
"BER\u0027s reliance on precedent-based reasoning to reach ethical conclusions"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A (as the agent who must act on the BER conclusion)",
"proeth:sufficientFactors": [
"Activated precedents (BER 94-8 and 85-3) + factual analogy to Engineer A\u0027s case + NSPE Code provisions on competence = sufficient basis for the ethical refusal conclusion"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (8)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineer B's retention by contractor |
during
Entity1 occurs entirely within the duration of Entity2 |
construction of the project (BER Case 94-8) |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
During the construction of the project, the construction contractor separately retained the services... [more] |
| BER Case 85-3 |
before
Entity1 is before Entity2 |
present case analysis |
time:before
http://www.w3.org/2006/time#before |
Although, the cases cited are not precisely the same as the facts in the present case, the Board bel... [more] |
| Army official's certification request |
before
Entity1 is before Entity2 |
Engineer A's ethical decision |
time:before
http://www.w3.org/2006/time#before |
An Army official requests that Engineer A certify... Engineer A has no significant training or knowl... [more] |
| lack of training funds |
overlaps
Entity1 starts before Entity2 and ends during Entity2 |
Army official's certification request |
time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps |
There are comprehensive training programs available for this type of work, but training funds are no... [more] |
| state engineering board regulation of certifications |
before
Entity1 is before Entity2 |
present case analysis |
time:before
http://www.w3.org/2006/time#before |
the certification of certain facts by an engineer, which has been the subject of state engineering b... [more] |
| first appointee deemed unqualified (BER Case 85-3) |
before
Entity1 is before Entity2 |
county commissioners appointing chemical engineer (BER Case 85-3) |
time:before
http://www.w3.org/2006/time#before |
The first appointee to the position was not a P.E. and was therefore deemed unqualified to continue ... [more] |
| BER Case 85-3 |
before
Entity1 is before Entity2 |
BER Case 94-8 |
time:before
http://www.w3.org/2006/time#before |
Case numbers 85-3 and 94-8 suggest Case 85-3 occurred in 1985 and Case 94-8 occurred in 1994, placin... [more] |
| BER Case 94-8 |
before
Entity1 is before Entity2 |
present case analysis |
time:before
http://www.w3.org/2006/time#before |
After considering the two earlier cases, the Board decided... Although, the cases cited are not prec... [more] |
About Allen Relations & OWL-Time
Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.
Each relation includes both a ProEthica custom property and a
time:* OWL-Time property for maximum compatibility.