PASS 3: Temporal Dynamics
Case 116: Duty To Report Violation—Anonymous Complaint
Timeline Overview
OWL-Time Temporal Structure 6 relations time: = w3.org/2006/time
Extracted Actions (4)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A witnesses what he believes is a serious violation of the state board's rules of professional conduct by Engineer B and makes a conscious judgment that the conduct warrants action. This assessment initiates the chain of volitional decisions that follow.
Temporal Marker: Initial observation period, prior to filing any complaint
Mental State: deliberate and evaluative
Intended Outcome: Accurately characterize Engineer B's conduct as a serious professional rules violation warranting formal response
Fulfills Obligations:
- Duty of vigilance over professional standards in the engineering community
- NSPE Code obligation to be aware of and respond to unprofessional conduct
Guided By Principles:
- Self-policing nature of the engineering profession
- Protection of public health, safety, and welfare
- Paramount duty to the public over deference to colleagues
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A, as a licensed professional, recognizes a potential serious breach of professional conduct standards and feels a duty-bound compulsion to assess whether what he witnessed crosses the threshold requiring action. His motivation is a combination of professional conscience, awareness of self-policing norms in engineering, and concern for public welfare or the integrity of the profession.
Ethical Tension: Personal non-involvement vs. professional obligation: Engineer A has no direct stake in the matter — Engineer B is a stranger and non-competitor — creating tension between the comfort of disengagement and the ethical duty to uphold professional standards even when inconvenient. There is also tension between charitable interpretation of Engineer B's conduct and the seriousness of the apparent violation.
Learning Significance: Students learn that the ethical obligation to assess and respond to misconduct is not limited to situations involving personal interest or direct harm to oneself. The mere act of witnessing a violation triggers a professional responsibility to evaluate and potentially act, regardless of relationship or competitive stake.
Stakes: Public trust in the engineering profession, potential public safety depending on the nature of the violation, Engineer B's licensure and reputation, and Engineer A's own professional integrity if he chooses to ignore what he has seen.
Decision Point: Yes - Story can branch here
- Dismiss the observation as a misunderstanding and take no further action
- Seek informal clarification or more information before making any judgment
- Consult a trusted colleague or ethics resource to validate whether the conduct truly constitutes a violation
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Action_Observe_and_Assess_Violation",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Dismiss the observation as a misunderstanding and take no further action",
"Seek informal clarification or more information before making any judgment",
"Consult a trusted colleague or ethics resource to validate whether the conduct truly constitutes a violation"
],
"proeth-scenario:characterMotivation": "Engineer A, as a licensed professional, recognizes a potential serious breach of professional conduct standards and feels a duty-bound compulsion to assess whether what he witnessed crosses the threshold requiring action. His motivation is a combination of professional conscience, awareness of self-policing norms in engineering, and concern for public welfare or the integrity of the profession.",
"proeth-scenario:consequencesIfAlternative": [
"If dismissed: A genuine violation goes unaddressed, potentially harming the public or profession; Engineer A may later feel complicit through inaction",
"If seeking more information: A more informed and defensible assessment is reached, reducing the risk of a wrongful complaint, but may delay necessary reporting",
"If consulting a colleague or ethics resource: Engineer A benefits from external validation, reducing personal bias risk, but introduces confidentiality concerns about Engineer B\u0027s identity"
],
"proeth-scenario:decisionSignificance": "Students learn that the ethical obligation to assess and respond to misconduct is not limited to situations involving personal interest or direct harm to oneself. The mere act of witnessing a violation triggers a professional responsibility to evaluate and potentially act, regardless of relationship or competitive stake.",
"proeth-scenario:ethicalTension": "Personal non-involvement vs. professional obligation: Engineer A has no direct stake in the matter \u2014 Engineer B is a stranger and non-competitor \u2014 creating tension between the comfort of disengagement and the ethical duty to uphold professional standards even when inconvenient. There is also tension between charitable interpretation of Engineer B\u0027s conduct and the seriousness of the apparent violation.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "Public trust in the engineering profession, potential public safety depending on the nature of the violation, Engineer B\u0027s licensure and reputation, and Engineer A\u0027s own professional integrity if he chooses to ignore what he has seen.",
"proeth:description": "Engineer A witnesses what he believes is a serious violation of the state board\u0027s rules of professional conduct by Engineer B and makes a conscious judgment that the conduct warrants action. This assessment initiates the chain of volitional decisions that follow.",
"proeth:foreseenUnintendedEffects": [
"Potential misidentification of conduct as a violation when it may not be",
"Initiating a process that could harm Engineer B\u0027s professional standing if the assessment is incorrect"
],
"proeth:fulfillsObligation": [
"Duty of vigilance over professional standards in the engineering community",
"NSPE Code obligation to be aware of and respond to unprofessional conduct"
],
"proeth:guidedByPrinciple": [
"Self-policing nature of the engineering profession",
"Protection of public health, safety, and welfare",
"Paramount duty to the public over deference to colleagues"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer, non-competitor and stranger to Engineer B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Accuracy of assessment vs. timeliness of reporting",
"proeth:resolutionReasoning": "Engineer A, having no personal or competitive stake, proceeds with the assessment in good faith based on direct observation, which lends credibility to the evaluation"
},
"proeth:hasMentalState": "deliberate and evaluative",
"proeth:intendedOutcome": "Accurately characterize Engineer B\u0027s conduct as a serious professional rules violation warranting formal response",
"proeth:requiresCapability": [
"Knowledge of state board rules of professional conduct",
"Professional judgment to distinguish serious from minor infractions",
"Objectivity as a disinterested third-party observer"
],
"proeth:temporalMarker": "Initial observation period, prior to filing any complaint",
"proeth:withinCompetence": true,
"rdfs:label": "Observe and Assess Violation"
}
Description: Engineer A makes the volitional decision to submit a formal complaint to the state engineering licensure board against Engineer B rather than remaining silent or pursuing informal channels. This decision reflects the exercise of the engineer's self-policing obligation.
Temporal Marker: After initial observation, before submission of the complaint
Mental State: deliberate and purposeful
Intended Outcome: Initiate formal board review of Engineer B's alleged professional conduct violation to uphold professional standards and protect the public
Fulfills Obligations:
- NSPE Code of Ethics obligation to report violations of professional conduct rules to appropriate authorities
- Duty to cooperate with the state licensure board
- Paramount duty to protect public health, safety, and welfare
- Self-policing obligation of the licensed engineering profession
Guided By Principles:
- Engineering as a self-policing profession
- Public health and safety as paramount concern (NSPE Code Section I.1)
- Accountability within the professional community
- Obligation to act even when not personally or competitively affected
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Having assessed the conduct as a serious violation, Engineer A feels compelled by his understanding of the engineering profession's self-policing obligation to escalate the matter through an official channel. He chooses formal complaint over silence or informal confrontation because he believes the severity of the violation warrants institutional accountability rather than a private resolution.
Ethical Tension: Self-policing duty vs. reluctance to judge or harm a peer: Filing a formal complaint against a fellow engineer — especially a stranger with whom Engineer A has no grievance — requires overcoming social hesitation, fear of being wrong, and discomfort with adversarial processes. There is also tension between loyalty to the professional community and the obligation to hold that community to its own standards.
Learning Significance: This action illustrates the core principle that professional licensure carries with it a collective responsibility to maintain standards. Students learn that ethical conduct is not merely about one's own practice but includes actively participating in the integrity of the profession as a whole, even when doing so is uncomfortable or carries personal risk.
Stakes: Engineer B's licensure and career, the credibility of the state board's enforcement process, public safety if the violation is ongoing, and the precedent set for whether engineers take self-policing seriously in practice.
Decision Point: Yes - Story can branch here
- Remain silent and take no formal action, rationalizing that it is not his place to intervene
- Confront Engineer B directly and informally, urging him to self-correct without involving the board
- Report the violation to Engineer B's employer or client rather than the licensure board
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Action_Decision_to_File_Complaint",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Remain silent and take no formal action, rationalizing that it is not his place to intervene",
"Confront Engineer B directly and informally, urging him to self-correct without involving the board",
"Report the violation to Engineer B\u0027s employer or client rather than the licensure board"
],
"proeth-scenario:characterMotivation": "Having assessed the conduct as a serious violation, Engineer A feels compelled by his understanding of the engineering profession\u0027s self-policing obligation to escalate the matter through an official channel. He chooses formal complaint over silence or informal confrontation because he believes the severity of the violation warrants institutional accountability rather than a private resolution.",
"proeth-scenario:consequencesIfAlternative": [
"If remaining silent: The violation continues unaddressed; Engineer A fails his professional obligation and potentially enables ongoing harm to the public or profession",
"If confronting Engineer B directly: May resolve the issue without formal consequences, but risks being ignored, retaliated against, or allowing a serious violation to escape institutional scrutiny",
"If reporting to employer or client: May prompt internal corrective action but bypasses the official regulatory mechanism designed for exactly this purpose, and may not result in accountability proportionate to the violation"
],
"proeth-scenario:decisionSignificance": "This action illustrates the core principle that professional licensure carries with it a collective responsibility to maintain standards. Students learn that ethical conduct is not merely about one\u0027s own practice but includes actively participating in the integrity of the profession as a whole, even when doing so is uncomfortable or carries personal risk.",
"proeth-scenario:ethicalTension": "Self-policing duty vs. reluctance to judge or harm a peer: Filing a formal complaint against a fellow engineer \u2014 especially a stranger with whom Engineer A has no grievance \u2014 requires overcoming social hesitation, fear of being wrong, and discomfort with adversarial processes. There is also tension between loyalty to the professional community and the obligation to hold that community to its own standards.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "Engineer B\u0027s licensure and career, the credibility of the state board\u0027s enforcement process, public safety if the violation is ongoing, and the precedent set for whether engineers take self-policing seriously in practice.",
"proeth:description": "Engineer A makes the volitional decision to submit a formal complaint to the state engineering licensure board against Engineer B rather than remaining silent or pursuing informal channels. This decision reflects the exercise of the engineer\u0027s self-policing obligation.",
"proeth:foreseenUnintendedEffects": [
"Potential reputational or professional harm to Engineer B if complaint is investigated",
"Possible professional or social friction if Engineer A\u0027s identity becomes known",
"Risk that the complaint may not be substantiated upon board review"
],
"proeth:fulfillsObligation": [
"NSPE Code of Ethics obligation to report violations of professional conduct rules to appropriate authorities",
"Duty to cooperate with the state licensure board",
"Paramount duty to protect public health, safety, and welfare",
"Self-policing obligation of the licensed engineering profession"
],
"proeth:guidedByPrinciple": [
"Engineering as a self-policing profession",
"Public health and safety as paramount concern (NSPE Code Section I.1)",
"Accountability within the professional community",
"Obligation to act even when not personally or competitively affected"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer, non-competitor and stranger to Engineer B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Non-interference in a stranger\u0027s professional affairs vs. professional duty to self-police the engineering community",
"proeth:resolutionReasoning": "The Board concludes that Engineer A had a clear and fundamental ethical obligation to report; the absence of personal or competitive motivation actually strengthens the legitimacy of the complaint"
},
"proeth:hasMentalState": "deliberate and purposeful",
"proeth:intendedOutcome": "Initiate formal board review of Engineer B\u0027s alleged professional conduct violation to uphold professional standards and protect the public",
"proeth:requiresCapability": [
"Understanding of state board complaint procedures",
"Knowledge of NSPE Code of Ethics reporting obligations",
"Ability to document and articulate the observed violation clearly"
],
"proeth:temporalMarker": "After initial observation, before submission of the complaint",
"proeth:withinCompetence": true,
"rdfs:label": "Decision to File Complaint"
}
Description: Engineer A chooses to submit the complaint to the state engineering licensure board without identifying himself, opting for anonymity rather than attaching his name as the complainant. This is a distinct volitional decision layered on top of the decision to file.
Temporal Marker: At the time of complaint submission to the state board
Mental State: deliberate and self-protective
Intended Outcome: Bring the alleged violation to the board's attention while shielding his own identity from Engineer B and the public
Fulfills Obligations:
- Partial fulfillment of the duty to report (complaint is filed, bringing the matter to the board's attention)
- Duty to act rather than remain silent, even if imperfectly
Guided By Principles:
- Fundamental fairness and due process (right to know one's accuser)
- Effectiveness of professional self-policing mechanisms
- Policy preference for transparent, accountable reporting within the profession
- Pragmatic principle that a weak complaint is better than no complaint when public safety is at risk
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A chooses anonymity primarily out of self-protection — fear of retaliation, professional awkwardness, social discomfort, or legal exposure from making a formal accusation against another licensed professional. He may also rationalize that the substance of the complaint matters more than his identity, and that anonymity allows the board to evaluate the facts without bias toward or against the complainant.
Ethical Tension: Personal safety and privacy vs. professional courage and accountability: The NSPE Code and professional norms favor transparency and signed complaints because they carry greater credibility and demonstrate willingness to stand behind one's accusations. Anonymous reporting, while legally permissible and ethically tolerated, creates tension with the virtue of professional courage — the expectation that engineers will act with integrity even at personal cost. There is also tension between the legitimate fear of retaliation and the duty to fully own one's ethical actions.
Learning Significance: This is the central ethical nuance of the case. Students learn to distinguish between what is ethically permissible and what is ethically ideal. Anonymous reporting fulfills the minimum obligation to report but falls short of the higher standard of professional courage. It opens discussion about when self-protection justifies reduced transparency, and what conditions might make anonymity more or less justifiable.
Stakes: The credibility and investigative viability of the complaint (anonymous complaints may be harder to act on), Engineer A's own integrity and moral completeness, the board's ability to follow up with the complainant for additional information, and the broader norm of whether engineers are willing to stand publicly behind their professional judgments.
Decision Point: Yes - Story can branch here
- Submit the complaint with his full name and contact information attached
- Submit the complaint anonymously but include detailed, verifiable documentation to compensate for the lack of a named complainant
- Decline to file any complaint, citing discomfort with both signed and anonymous reporting
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Action_Submit_Complaint_Anonymously",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Submit the complaint with his full name and contact information attached",
"Submit the complaint anonymously but include detailed, verifiable documentation to compensate for the lack of a named complainant",
"Decline to file any complaint, citing discomfort with both signed and anonymous reporting"
],
"proeth-scenario:characterMotivation": "Engineer A chooses anonymity primarily out of self-protection \u2014 fear of retaliation, professional awkwardness, social discomfort, or legal exposure from making a formal accusation against another licensed professional. He may also rationalize that the substance of the complaint matters more than his identity, and that anonymity allows the board to evaluate the facts without bias toward or against the complainant.",
"proeth-scenario:consequencesIfAlternative": [
"If filing with full name: The complaint carries greater credibility and the board can follow up directly; Engineer A demonstrates professional courage but accepts the personal and professional risks of being identified as the complainant",
"If filing anonymously with strong documentation: Partially mitigates the weakness of anonymity by providing the board with actionable evidence, though Engineer A still avoids full accountability for the accusation",
"If declining to file: Engineer A avoids all personal risk but wholly abandons his professional obligation, leaving the violation unaddressed and potentially enabling continued harm"
],
"proeth-scenario:decisionSignificance": "This is the central ethical nuance of the case. Students learn to distinguish between what is ethically permissible and what is ethically ideal. Anonymous reporting fulfills the minimum obligation to report but falls short of the higher standard of professional courage. It opens discussion about when self-protection justifies reduced transparency, and what conditions might make anonymity more or less justifiable.",
"proeth-scenario:ethicalTension": "Personal safety and privacy vs. professional courage and accountability: The NSPE Code and professional norms favor transparency and signed complaints because they carry greater credibility and demonstrate willingness to stand behind one\u0027s accusations. Anonymous reporting, while legally permissible and ethically tolerated, creates tension with the virtue of professional courage \u2014 the expectation that engineers will act with integrity even at personal cost. There is also tension between the legitimate fear of retaliation and the duty to fully own one\u0027s ethical actions.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "The credibility and investigative viability of the complaint (anonymous complaints may be harder to act on), Engineer A\u0027s own integrity and moral completeness, the board\u0027s ability to follow up with the complainant for additional information, and the broader norm of whether engineers are willing to stand publicly behind their professional judgments.",
"proeth:description": "Engineer A chooses to submit the complaint to the state engineering licensure board without identifying himself, opting for anonymity rather than attaching his name as the complainant. This is a distinct volitional decision layered on top of the decision to file.",
"proeth:foreseenUnintendedEffects": [
"Engineer B is denied knowledge of his accuser, raising fairness concerns",
"The complaint may be weakened evidentiary due to the absence of an identifiable complainant willing to participate in proceedings",
"The board\u0027s ability to investigate and prosecute the case may be diminished without a named complainant",
"The policy goal of encouraging engineers to publicly stand behind ethical concerns is undermined"
],
"proeth:fulfillsObligation": [
"Partial fulfillment of the duty to report (complaint is filed, bringing the matter to the board\u0027s attention)",
"Duty to act rather than remain silent, even if imperfectly"
],
"proeth:guidedByPrinciple": [
"Fundamental fairness and due process (right to know one\u0027s accuser)",
"Effectiveness of professional self-policing mechanisms",
"Policy preference for transparent, accountable reporting within the profession",
"Pragmatic principle that a weak complaint is better than no complaint when public safety is at risk"
],
"proeth:hasAgent": "Engineer A (Licensed Professional Engineer, non-competitor and stranger to Engineer B)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Complainant self-protection and anonymity vs. fairness to the accused and effectiveness of enforcement",
"proeth:resolutionReasoning": "The Board applies a pragmatic balancing approach: while a signed complaint is preferable on fairness and policy grounds, the anonymous complaint is not ruled unethical because it still serves the core purpose of alerting the board to a potential violation. The threshold question is whether something is accomplished versus nothing \u2014 and anonymous reporting clears that bar."
},
"proeth:hasMentalState": "deliberate and self-protective",
"proeth:intendedOutcome": "Bring the alleged violation to the board\u0027s attention while shielding his own identity from Engineer B and the public",
"proeth:requiresCapability": [
"Knowledge of state board complaint procedures, including whether anonymous submissions are accepted",
"Ability to document the alleged violation with sufficient specificity to enable board investigation without a named complainant",
"Judgment about the risks and tradeoffs of anonymous vs. signed reporting"
],
"proeth:temporalMarker": "At the time of complaint submission to the state board",
"proeth:violatesObligation": [
"Policy-level obligation to stand publicly behind ethical concerns and cooperate fully with the board",
"Implicit obligation of fairness to Engineer B \u2014 the accused\u0027s interest in knowing his accuser",
"Obligation to provide the strongest possible basis for the board\u0027s investigation and enforcement action"
],
"proeth:withinCompetence": true,
"rdfs:label": "Submit Complaint Anonymously"
}
Description: In the referenced precedent case (BER Case 89-7), Engineer A chose not to report known electrical and mechanical safety deficiencies to any third-party public authority, instead honoring client confidentiality by limiting disclosure to a brief mention in his structural report. This action was ruled unethical by the Board.
Temporal Marker: After completing structural investigation and receiving client confidential disclosure of code violations, prior to finalizing and delivering report
Mental State: deliberate and deferential to client agreement
Intended Outcome: Honor the confidentiality terms of the client agreement and avoid breaching the contractual and professional duty of confidentiality owed to the client
Fulfills Obligations:
- Contractual and professional duty of client confidentiality (honored in the short term)
- Duty to inform the client of the safety concern (Engineer A did notify the client)
Guided By Principles:
- Public health and safety as paramount obligation under NSPE Code (word 'paramount' in Section I.1 is dispositive)
- Limits of client confidentiality when third-party public safety is at stake
- Engineer's obligation to act even outside his specific technical discipline when safety is implicated
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: The engineer in BER Case 89-7 was primarily motivated by client confidentiality obligations and a desire to avoid overstepping his defined role as a structural engineer. He may have rationalized that the electrical and mechanical deficiencies were outside his scope of engagement, and that mentioning them briefly in his structural report discharged whatever marginal duty he had without breaching the client relationship.
Ethical Tension: Client confidentiality and scope limitations vs. obligation to protect public safety: This case presents one of the most fundamental tensions in engineering ethics — the duty of loyalty to the client who hired the engineer versus the paramount duty to protect the health, safety, and welfare of the public. The engineer treated these as roughly equal competing obligations and chose client loyalty, but the Board ruled that public safety must take precedence when the stakes involve known safety deficiencies.
Learning Significance: BER Case 89-7 serves as a cautionary precedent that anchors the primary case's analysis. Students learn that the duty to report safety violations to appropriate public authorities is not optional or subordinate to client preferences, and that a token mention in a private report does not satisfy the obligation to ensure safety deficiencies are actually addressed. This precedent also illustrates how past Board rulings shape current ethical reasoning.
Stakes: Public safety from known electrical and mechanical hazards, the engineer's professional license and reputation, the client's exposure to liability if the deficiencies cause harm, and the integrity of the profession's commitment to prioritizing public welfare over client convenience.
Decision Point: Yes - Story can branch here
- Report the safety deficiencies directly to the relevant public authority (e.g., building inspector, safety regulator) regardless of client preference
- Refuse to complete or certify the structural report until the safety deficiencies are addressed by the client
- Explicitly document in writing to the client that the deficiencies must be reported and corrected, and notify the client that the engineer will report to authorities if corrective action is not taken within a defined timeframe
Narrative Role: falling_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Action_Withhold_Safety_Violation_Report__BER_89-7_",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Report the safety deficiencies directly to the relevant public authority (e.g., building inspector, safety regulator) regardless of client preference",
"Refuse to complete or certify the structural report until the safety deficiencies are addressed by the client",
"Explicitly document in writing to the client that the deficiencies must be reported and corrected, and notify the client that the engineer will report to authorities if corrective action is not taken within a defined timeframe"
],
"proeth-scenario:characterMotivation": "The engineer in BER Case 89-7 was primarily motivated by client confidentiality obligations and a desire to avoid overstepping his defined role as a structural engineer. He may have rationalized that the electrical and mechanical deficiencies were outside his scope of engagement, and that mentioning them briefly in his structural report discharged whatever marginal duty he had without breaching the client relationship.",
"proeth-scenario:consequencesIfAlternative": [
"If reporting to public authority: The safety hazards are brought to the attention of those with authority to compel correction; the engineer fulfills his paramount public safety obligation but risks damaging the client relationship and potentially losing future work",
"If refusing to certify: Creates immediate pressure on the client to address the deficiencies before the project can proceed, but may result in the engineer being dismissed from the project without the safety issues being resolved",
"If issuing a written ultimatum to the client: Gives the client an opportunity to self-correct while establishing a clear paper trail of the engineer\u0027s awareness and good-faith effort, and preserves the option for escalation \u2014 a more measured approach that balances client relationship with public safety duty"
],
"proeth-scenario:decisionSignificance": "BER Case 89-7 serves as a cautionary precedent that anchors the primary case\u0027s analysis. Students learn that the duty to report safety violations to appropriate public authorities is not optional or subordinate to client preferences, and that a token mention in a private report does not satisfy the obligation to ensure safety deficiencies are actually addressed. This precedent also illustrates how past Board rulings shape current ethical reasoning.",
"proeth-scenario:ethicalTension": "Client confidentiality and scope limitations vs. obligation to protect public safety: This case presents one of the most fundamental tensions in engineering ethics \u2014 the duty of loyalty to the client who hired the engineer versus the paramount duty to protect the health, safety, and welfare of the public. The engineer treated these as roughly equal competing obligations and chose client loyalty, but the Board ruled that public safety must take precedence when the stakes involve known safety deficiencies.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "falling_action",
"proeth-scenario:stakes": "Public safety from known electrical and mechanical hazards, the engineer\u0027s professional license and reputation, the client\u0027s exposure to liability if the deficiencies cause harm, and the integrity of the profession\u0027s commitment to prioritizing public welfare over client convenience.",
"proeth:description": "In the referenced precedent case (BER Case 89-7), Engineer A chose not to report known electrical and mechanical safety deficiencies to any third-party public authority, instead honoring client confidentiality by limiting disclosure to a brief mention in his structural report. This action was ruled unethical by the Board.",
"proeth:foreseenUnintendedEffects": [
"Known electrical and mechanical deficiencies posing injury risk to building occupants go unreported to public authorities",
"Future occupants of the building remain exposed to safety hazards without knowledge or protection",
"Engineer A\u0027s structural report provides only a brief, indirect reference to the deficiencies without triggering regulatory response"
],
"proeth:fulfillsObligation": [
"Contractual and professional duty of client confidentiality (honored in the short term)",
"Duty to inform the client of the safety concern (Engineer A did notify the client)"
],
"proeth:guidedByPrinciple": [
"Public health and safety as paramount obligation under NSPE Code (word \u0027paramount\u0027 in Section I.1 is dispositive)",
"Limits of client confidentiality when third-party public safety is at stake",
"Engineer\u0027s obligation to act even outside his specific technical discipline when safety is implicated"
],
"proeth:hasAgent": "Engineer A in BER Case 89-7 (Licensed Structural Engineer retained by building owner-client)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client confidentiality and contractual fidelity vs. paramount public safety reporting obligation",
"proeth:resolutionReasoning": "The Board applied the NSPE Code\u0027s use of \u0027paramount\u0027 to resolve the conflict decisively in favor of public safety reporting; confidentiality obligations, while significant, cannot override the engineer\u0027s duty to protect the public from known safety hazards. The ruling establishes this as a clear ethical bright line."
},
"proeth:hasMentalState": "deliberate and deferential to client agreement",
"proeth:intendedOutcome": "Honor the confidentiality terms of the client agreement and avoid breaching the contractual and professional duty of confidentiality owed to the client",
"proeth:requiresCapability": [
"Recognition of safety-significant code violations even outside one\u0027s primary engineering discipline",
"Knowledge of applicable reporting obligations to public authorities",
"Judgment to distinguish confidentiality obligations that can be honored from those that must yield to public safety"
],
"proeth:temporalMarker": "After completing structural investigation and receiving client confidential disclosure of code violations, prior to finalizing and delivering report",
"proeth:violatesObligation": [
"Paramount duty to protect public health, safety, and welfare (NSPE Code Section I.1)",
"Obligation to report safety violations to appropriate public authorities when public health and safety are at risk",
"Duty to hold public safety as superseding confidentiality obligations in cases of imminent risk to third parties"
],
"proeth:withinCompetence": false,
"rdfs:label": "Withhold Safety Violation Report (BER 89-7)"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changesDescription: Engineer A observes Engineer B's professional conduct violation, transforming a latent ethical situation into an active one that directly implicates Engineer A's own professional obligations. This observation is the triggering event for the entire ethical dilemma.
Temporal Marker: After the violation occurs; the first event in the narrative from Engineer A's perspective
Activates Constraints:
- Peer_Reporting_Obligation_Constraint
- Professional_Duty_To_Act_Constraint
- NSPE_Code_Section_III.2.b_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A experiences a moment of recognition and moral discomfort — the burden of knowledge creates tension between inaction (easier) and obligation (harder); Engineer B remains unaware of being observed; potential sense of moral urgency for Engineer A
- engineer_a: Now bears an active professional and ethical obligation; inaction would itself constitute an ethical failure; faces personal and professional risk in deciding how to respond
- engineer_b: Unaware; exposure to accountability now becomes possible for the first time
- public: Protection mechanisms of the profession are now activated through Engineer A's awareness
- licensure_board: Potential recipient of a complaint; investigative jurisdiction may be activated
Learning Moment: Knowledge creates obligation. The moment a licensed engineer becomes aware of a serious violation by a peer, they are no longer a neutral bystander — they become an ethically responsible actor. Students should grapple with the weight of professional knowledge and the duty it imposes.
Ethical Implications: Crystallizes the core tension between passive non-interference and active professional responsibility; reveals that professional codes impose positive duties, not merely prohibitions; raises questions about the costs of professional integrity to the individual who must bear them
- Does Engineer A's obligation to report change based on the nature of the violation — for example, whether it involves public safety versus financial misconduct?
- Is 'I wasn't sure it was really a violation' a morally adequate reason for Engineer A to remain silent? What standard of certainty should apply?
- How does the stranger/non-competitor relationship between Engineer A and Engineer B affect the psychological and ethical dynamics of this moment?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Event_Violation_Becomes_Observed",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Does Engineer A\u0027s obligation to report change based on the nature of the violation \u2014 for example, whether it involves public safety versus financial misconduct?",
"Is \u0027I wasn\u0027t sure it was really a violation\u0027 a morally adequate reason for Engineer A to remain silent? What standard of certainty should apply?",
"How does the stranger/non-competitor relationship between Engineer A and Engineer B affect the psychological and ethical dynamics of this moment?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A experiences a moment of recognition and moral discomfort \u2014 the burden of knowledge creates tension between inaction (easier) and obligation (harder); Engineer B remains unaware of being observed; potential sense of moral urgency for Engineer A",
"proeth-scenario:ethicalImplications": "Crystallizes the core tension between passive non-interference and active professional responsibility; reveals that professional codes impose positive duties, not merely prohibitions; raises questions about the costs of professional integrity to the individual who must bear them",
"proeth-scenario:learningMoment": "Knowledge creates obligation. The moment a licensed engineer becomes aware of a serious violation by a peer, they are no longer a neutral bystander \u2014 they become an ethically responsible actor. Students should grapple with the weight of professional knowledge and the duty it imposes.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"engineer_a": "Now bears an active professional and ethical obligation; inaction would itself constitute an ethical failure; faces personal and professional risk in deciding how to respond",
"engineer_b": "Unaware; exposure to accountability now becomes possible for the first time",
"licensure_board": "Potential recipient of a complaint; investigative jurisdiction may be activated",
"public": "Protection mechanisms of the profession are now activated through Engineer A\u0027s awareness"
},
"proeth:activatesConstraint": [
"Peer_Reporting_Obligation_Constraint",
"Professional_Duty_To_Act_Constraint",
"NSPE_Code_Section_III.2.b_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/116#Action_Observe_and_Assess_Violation",
"proeth:causesStateChange": "Engineer A transitions from a bystander with no obligations to an ethically implicated professional with active reporting duties; the situation is no longer purely about Engineer B \u2014 it now concerns Engineer A\u0027s own professional integrity",
"proeth:createsObligation": [
"Obligation_To_Report_Violation_To_Appropriate_Authority",
"Obligation_To_Assess_Severity_And_Nature_Of_Violation",
"Obligation_Not_To_Ignore_Known_Violations"
],
"proeth:description": "Engineer A observes Engineer B\u0027s professional conduct violation, transforming a latent ethical situation into an active one that directly implicates Engineer A\u0027s own professional obligations. This observation is the triggering event for the entire ethical dilemma.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "After the violation occurs; the first event in the narrative from Engineer A\u0027s perspective",
"proeth:urgencyLevel": "high",
"rdfs:label": "Violation Becomes Observed"
}
Description: As an automatic consequence of Engineer A's observation and assessment of a serious violation, Engineer A's professional reporting obligation under engineering ethics codes becomes fully active and enforceable. This is not a decision but a status change triggered by the combination of knowledge and professional licensure.
Temporal Marker: Simultaneous with or immediately following the observation event; before any decision about how to respond
Activates Constraints:
- NSPE_Code_Section_III.2.b_Reporting_Constraint
- Professional_Self_Regulation_Constraint
- Duty_Not_To_Condone_Violations_By_Silence_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel the weight of unwanted responsibility — the obligation arrives whether or not it is welcome; there may be reluctance, anxiety about consequences, or conflict between loyalty to professional norms and desire to avoid involvement; no emotional change for Engineer B who remains unaware
- engineer_a: Now faces a clear ethical duty with no morally neutral exit; choosing not to report becomes an active ethical failure, not merely a passive omission
- engineer_b: Accountability is now structurally available through the reporting mechanism
- engineering_profession: The self-regulatory system's integrity depends on this obligation being honored
- public: Public protection through professional accountability is now potentially activated
Learning Moment: Professional obligations are not optional responses to situations — they are automatically triggered by combinations of status (licensure) and circumstances (knowledge of violations). Students should understand that professional codes create binding positive duties, not merely aspirational guidelines, and that inaction in the face of known violations is itself an ethical violation.
Ethical Implications: Reveals the positive duty structure embedded in professional codes — engineers are not merely prohibited from wrongdoing but affirmatively required to act as guardians of professional integrity; raises the question of whether professional self-regulation can function without individuals bearing the personal costs of peer accountability
- The BER concludes Engineer A had a 'clear ethical obligation' to report. What makes this obligation 'clear' rather than discretionary? What factors would make it less clear?
- If Engineer A had reported to Engineer B directly rather than the licensure board, would that satisfy the obligation? What does the answer reveal about the purpose of the reporting duty?
- BER Case 89-7 involved an engineer who failed to report safety violations. Does the nature of the violation (safety vs. professional conduct) affect the strength of the reporting obligation?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Event_Reporting_Obligation_Activated",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"The BER concludes Engineer A had a \u0027clear ethical obligation\u0027 to report. What makes this obligation \u0027clear\u0027 rather than discretionary? What factors would make it less clear?",
"If Engineer A had reported to Engineer B directly rather than the licensure board, would that satisfy the obligation? What does the answer reveal about the purpose of the reporting duty?",
"BER Case 89-7 involved an engineer who failed to report safety violations. Does the nature of the violation (safety vs. professional conduct) affect the strength of the reporting obligation?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A may feel the weight of unwanted responsibility \u2014 the obligation arrives whether or not it is welcome; there may be reluctance, anxiety about consequences, or conflict between loyalty to professional norms and desire to avoid involvement; no emotional change for Engineer B who remains unaware",
"proeth-scenario:ethicalImplications": "Reveals the positive duty structure embedded in professional codes \u2014 engineers are not merely prohibited from wrongdoing but affirmatively required to act as guardians of professional integrity; raises the question of whether professional self-regulation can function without individuals bearing the personal costs of peer accountability",
"proeth-scenario:learningMoment": "Professional obligations are not optional responses to situations \u2014 they are automatically triggered by combinations of status (licensure) and circumstances (knowledge of violations). Students should understand that professional codes create binding positive duties, not merely aspirational guidelines, and that inaction in the face of known violations is itself an ethical violation.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"engineer_a": "Now faces a clear ethical duty with no morally neutral exit; choosing not to report becomes an active ethical failure, not merely a passive omission",
"engineer_b": "Accountability is now structurally available through the reporting mechanism",
"engineering_profession": "The self-regulatory system\u0027s integrity depends on this obligation being honored",
"public": "Public protection through professional accountability is now potentially activated"
},
"proeth:activatesConstraint": [
"NSPE_Code_Section_III.2.b_Reporting_Constraint",
"Professional_Self_Regulation_Constraint",
"Duty_Not_To_Condone_Violations_By_Silence_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/116#Action_Observe_and_Assess_Violation",
"proeth:causesStateChange": "Engineer A\u0027s ethical status shifts from \u0027uninvolved third party\u0027 to \u0027obligated reporter\u0027; silence or inaction now constitutes an independent ethical violation; the profession\u0027s self-regulatory mechanism depends on Engineer A acting",
"proeth:createsObligation": [
"Obligation_To_Report_To_Appropriate_Authority (state licensure board)",
"Obligation_To_Not_Remain_Silent_About_Known_Violations",
"Obligation_To_Choose_Reporting_Method_That_Maximizes_Effectiveness"
],
"proeth:description": "As an automatic consequence of Engineer A\u0027s observation and assessment of a serious violation, Engineer A\u0027s professional reporting obligation under engineering ethics codes becomes fully active and enforceable. This is not a decision but a status change triggered by the combination of knowledge and professional licensure.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "automatic_trigger",
"proeth:temporalMarker": "Simultaneous with or immediately following the observation event; before any decision about how to respond",
"proeth:urgencyLevel": "high",
"rdfs:label": "Reporting Obligation Activated"
}
Description: The state engineering licensure board receives Engineer A's complaint against Engineer B without identifying information, creating a procedural and investigative situation where the board must evaluate an allegation without a named complainant. This is an outcome of Engineer A's submission action.
Temporal Marker: Immediately following the submission of the anonymous complaint by Engineer A
Activates Constraints:
- Licensure_Board_Investigative_Obligation_Constraint
- Due_Process_For_Engineer_B_Constraint
- Anonymous_Complaint_Procedural_Limitations_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel a sense of partial relief (obligation discharged) mixed with residual discomfort about the anonymous nature; Engineer B is unaware but now faces potential investigation; the licensure board faces a procedurally awkward situation; the public interest is served in some measure but imperfectly
- engineer_a: Reporting obligation substantially discharged; personal exposure minimized; but ethical question about anonymous vs. signed complaint remains unresolved
- engineer_b: Now subject to potential regulatory investigation; due process rights may be impaired by inability to confront anonymous accuser; professional reputation at risk
- licensure_board: Receives actionable information but faces investigative limitations — cannot call complainant as witness, cannot verify complainant's credibility through cross-examination, may have reduced ability to build a complete evidentiary record
- public: Professional accountability mechanism is activated, though less effectively than if complaint were signed
Learning Moment: The act of reporting, while ethically required, has degrees of effectiveness. An anonymous complaint satisfies the minimum ethical obligation but sacrifices accountability, credibility, and investigative utility. Students should understand that ethical compliance is not binary — how one fulfills an obligation matters, not just whether one fulfills it.
Ethical Implications: Exposes the tension between self-protection (anonymity) and the full discharge of professional duty (accountability and effectiveness); raises questions about whether ethical obligations have a 'quality' dimension beyond mere compliance; implicates Engineer B's due process rights against Engineer A's interest in protection from retaliation
- The BER concludes anonymous reporting is 'ethically permissible but not ideal.' What values are in tension that make this a judgment call rather than a clear rule?
- What procedural disadvantages does the licensure board face when investigating an anonymous complaint? Do those disadvantages affect Engineer A's ethical assessment?
- If Engineer B is ultimately not disciplined because the anonymous complaint cannot be adequately investigated, has Engineer A fully met their ethical obligation? Why or why not?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Event_Anonymous_Complaint_Received",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"The BER concludes anonymous reporting is \u0027ethically permissible but not ideal.\u0027 What values are in tension that make this a judgment call rather than a clear rule?",
"What procedural disadvantages does the licensure board face when investigating an anonymous complaint? Do those disadvantages affect Engineer A\u0027s ethical assessment?",
"If Engineer B is ultimately not disciplined because the anonymous complaint cannot be adequately investigated, has Engineer A fully met their ethical obligation? Why or why not?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer A may feel a sense of partial relief (obligation discharged) mixed with residual discomfort about the anonymous nature; Engineer B is unaware but now faces potential investigation; the licensure board faces a procedurally awkward situation; the public interest is served in some measure but imperfectly",
"proeth-scenario:ethicalImplications": "Exposes the tension between self-protection (anonymity) and the full discharge of professional duty (accountability and effectiveness); raises questions about whether ethical obligations have a \u0027quality\u0027 dimension beyond mere compliance; implicates Engineer B\u0027s due process rights against Engineer A\u0027s interest in protection from retaliation",
"proeth-scenario:learningMoment": "The act of reporting, while ethically required, has degrees of effectiveness. An anonymous complaint satisfies the minimum ethical obligation but sacrifices accountability, credibility, and investigative utility. Students should understand that ethical compliance is not binary \u2014 how one fulfills an obligation matters, not just whether one fulfills it.",
"proeth-scenario:narrativePacing": "aftermath",
"proeth-scenario:stakeholderConsequences": {
"engineer_a": "Reporting obligation substantially discharged; personal exposure minimized; but ethical question about anonymous vs. signed complaint remains unresolved",
"engineer_b": "Now subject to potential regulatory investigation; due process rights may be impaired by inability to confront anonymous accuser; professional reputation at risk",
"licensure_board": "Receives actionable information but faces investigative limitations \u2014 cannot call complainant as witness, cannot verify complainant\u0027s credibility through cross-examination, may have reduced ability to build a complete evidentiary record",
"public": "Professional accountability mechanism is activated, though less effectively than if complaint were signed"
},
"proeth:activatesConstraint": [
"Licensure_Board_Investigative_Obligation_Constraint",
"Due_Process_For_Engineer_B_Constraint",
"Anonymous_Complaint_Procedural_Limitations_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/116#Action_Submit_Complaint_Anonymously",
"proeth:causesStateChange": "The violation is now formally before a regulatory authority; Engineer B\u0027s professional status is now subject to potential investigation; Engineer A\u0027s reporting obligation is discharged in substance though the anonymous form raises secondary ethical questions; the board faces procedural constraints in acting on an anonymous complaint",
"proeth:createsObligation": [
"Licensure_Board_Obligation_To_Review_Complaint",
"Obligation_To_Assess_Sufficiency_Of_Anonymous_Complaint",
"Potential_Obligation_To_Investigate_If_Facially_Sufficient"
],
"proeth:description": "The state engineering licensure board receives Engineer A\u0027s complaint against Engineer B without identifying information, creating a procedural and investigative situation where the board must evaluate an allegation without a named complainant. This is an outcome of Engineer A\u0027s submission action.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Immediately following the submission of the anonymous complaint by Engineer A",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Anonymous Complaint Received"
}
Description: In the referenced prior case (BER Case 89-7), the engineer's failure to report safety violations results in the continuation of unsafe conditions, allowing potential or actual harm to occur that proper reporting might have prevented. This outcome illustrates the real-world consequences of non-reporting.
Temporal Marker: Referenced retrospectively in the Discussion section; occurred in the BER 89-7 case timeline following the Withhold Safety Violation Report action
Activates Constraints:
- PublicSafety_Paramount_Constraint
- Mandatory_Reporting_Of_Safety_Violations_Constraint
- Engineer_Duty_To_Protect_Public_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Retrospective horror and moral weight — the harm that occurred was preventable; the engineer in BER 89-7 must confront the causal connection between their silence and the harm; for students reading the case, this creates a visceral understanding of why reporting obligations exist
- engineer_in_89_7: Professional discipline; moral culpability for harm that reporting could have prevented; career consequences
- public_affected: Actual harm suffered from safety violations that a professional had the power and obligation to report
- building_owner_client: Legal and financial liability; potential harm to occupants
- engineering_profession: Reputational damage; demonstration that self-regulation failed in this instance
- engineer_a_in_current_case: BER 89-7 serves as a cautionary precedent that makes Engineer A's obligation to report clear and non-discretionary
Learning Moment: The BER invokes BER 89-7 not as abstract precedent but as a concrete illustration that non-reporting has victims. Students must understand that professional silence is never truly neutral — it is an active choice that can be causally connected to harm. The reporting obligation exists precisely because professionals are often the only ones positioned to know about dangers that affect others.
Ethical Implications: Demonstrates that professional obligations to the public can override duties to clients; reveals the causal responsibility engineers bear when they fail to act as the public's last line of defense; raises the question of whether professional silence in the face of known danger constitutes a form of complicity in resulting harm
- The engineer in BER 89-7 was retained by the building owner — does that client relationship create a competing obligation that could justify non-reporting? How should that tension be resolved?
- How does the severity of potential harm affect the strength of the reporting obligation? Is there a threshold below which non-reporting is ethically permissible?
- BER uses 89-7 as precedent in the current case even though the violations differ (safety vs. professional conduct). Is that analogical reasoning sound? What are its limits?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Event_BER_89-7_Safety_Harm_Materializes",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"The engineer in BER 89-7 was retained by the building owner \u2014 does that client relationship create a competing obligation that could justify non-reporting? How should that tension be resolved?",
"How does the severity of potential harm affect the strength of the reporting obligation? Is there a threshold below which non-reporting is ethically permissible?",
"BER uses 89-7 as precedent in the current case even though the violations differ (safety vs. professional conduct). Is that analogical reasoning sound? What are its limits?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Retrospective horror and moral weight \u2014 the harm that occurred was preventable; the engineer in BER 89-7 must confront the causal connection between their silence and the harm; for students reading the case, this creates a visceral understanding of why reporting obligations exist",
"proeth-scenario:ethicalImplications": "Demonstrates that professional obligations to the public can override duties to clients; reveals the causal responsibility engineers bear when they fail to act as the public\u0027s last line of defense; raises the question of whether professional silence in the face of known danger constitutes a form of complicity in resulting harm",
"proeth-scenario:learningMoment": "The BER invokes BER 89-7 not as abstract precedent but as a concrete illustration that non-reporting has victims. Students must understand that professional silence is never truly neutral \u2014 it is an active choice that can be causally connected to harm. The reporting obligation exists precisely because professionals are often the only ones positioned to know about dangers that affect others.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"building_owner_client": "Legal and financial liability; potential harm to occupants",
"engineer_a_in_current_case": "BER 89-7 serves as a cautionary precedent that makes Engineer A\u0027s obligation to report clear and non-discretionary",
"engineer_in_89_7": "Professional discipline; moral culpability for harm that reporting could have prevented; career consequences",
"engineering_profession": "Reputational damage; demonstration that self-regulation failed in this instance",
"public_affected": "Actual harm suffered from safety violations that a professional had the power and obligation to report"
},
"proeth:activatesConstraint": [
"PublicSafety_Paramount_Constraint",
"Mandatory_Reporting_Of_Safety_Violations_Constraint",
"Engineer_Duty_To_Protect_Public_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/116#Action_Withhold_Safety_Violation_Report__BER_89-7_",
"proeth:causesStateChange": "Unsafe conditions persist and cause harm because the professional reporting mechanism was not activated; the engineer\u0027s silence becomes causally connected to the harm; the BER uses this outcome to establish the precedent that non-reporting is itself an ethical violation with real consequences",
"proeth:createsObligation": [
"Retrospective_Obligation_To_Have_Reported (violated)",
"Lesson_Obligation_For_Future_Cases: Report_Safety_Violations_Immediately"
],
"proeth:description": "In the referenced prior case (BER Case 89-7), the engineer\u0027s failure to report safety violations results in the continuation of unsafe conditions, allowing potential or actual harm to occur that proper reporting might have prevented. This outcome illustrates the real-world consequences of non-reporting.",
"proeth:emergencyStatus": "critical",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Referenced retrospectively in the Discussion section; occurred in the BER 89-7 case timeline following the Withhold Safety Violation Report action",
"proeth:urgencyLevel": "critical",
"rdfs:label": "BER 89-7 Safety Harm Materializes"
}
Description: The Board of Ethical Review's analysis concludes that anonymous reporting, while not ideal, is ethically permissible — establishing a normative outcome that defines the ethical status of Engineer A's conduct and creates guidance for future cases. This is an outcome of the BER's deliberative process.
Temporal Marker: At the conclusion of the BER's analysis; the final evaluative event in the narrative
Activates Constraints:
- Professional_Norm_Setting_Constraint
- Guidance_For_Future_Cases_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel vindicated that the anonymous approach was permissible, but the 'not ideal' qualifier may create residual discomfort; Engineer B's situation is unresolved by this ruling (it concerns Engineer A's conduct, not Engineer B's fate); students may feel the tension between the ruling's pragmatism and its implicit moral preference for courage
- engineer_a: Conduct declared ethically permissible; no professional sanction; but implicitly encouraged to sign complaints in future situations
- engineer_b: Unaffected by the BER ruling directly; fate depends on the licensure board's investigation
- engineering_profession: Gains clearer normative guidance on a previously uncertain question; the self-regulatory system is strengthened by the clarification
- future_engineers: Now have a precedent establishing both the obligation to report and the permissibility (with caveats) of anonymous reporting
Learning Moment: Ethical analysis rarely produces simple binary answers. The BER's 'permissible but not ideal' conclusion teaches students that professional ethics involves degrees of compliance and that meeting the minimum standard is not the same as acting with full integrity. The ideal is a signed complaint; the minimum is any complaint. Students should aspire to the ideal while understanding the minimum.
Ethical Implications: Reveals that professional ethics standards can accommodate human limitations (fear of retaliation, desire for privacy) without abandoning the underlying obligation; raises the question of whether 'permissible' and 'ethical' are the same thing; demonstrates that professional codes must balance idealism with practical enforceability to remain credible and followed
- The BER says anonymous reporting is 'ethically permissible but not ideal.' What would need to change in Engineer A's circumstances to make a signed complaint the clear ethical requirement rather than merely preferred?
- Is the BER's two-tier standard (permissible vs. ideal) a useful ethical framework, or does it risk encouraging engineers to settle for the minimum? How should professional ethics standards be structured?
- If you were Engineer A and read this BER ruling, would it change how you would act in a similar future situation? What does your answer reveal about the relationship between ethical rules and moral character?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Event_Ethical_Permissibility_Established",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"The BER says anonymous reporting is \u0027ethically permissible but not ideal.\u0027 What would need to change in Engineer A\u0027s circumstances to make a signed complaint the clear ethical requirement rather than merely preferred?",
"Is the BER\u0027s two-tier standard (permissible vs. ideal) a useful ethical framework, or does it risk encouraging engineers to settle for the minimum? How should professional ethics standards be structured?",
"If you were Engineer A and read this BER ruling, would it change how you would act in a similar future situation? What does your answer reveal about the relationship between ethical rules and moral character?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer A may feel vindicated that the anonymous approach was permissible, but the \u0027not ideal\u0027 qualifier may create residual discomfort; Engineer B\u0027s situation is unresolved by this ruling (it concerns Engineer A\u0027s conduct, not Engineer B\u0027s fate); students may feel the tension between the ruling\u0027s pragmatism and its implicit moral preference for courage",
"proeth-scenario:ethicalImplications": "Reveals that professional ethics standards can accommodate human limitations (fear of retaliation, desire for privacy) without abandoning the underlying obligation; raises the question of whether \u0027permissible\u0027 and \u0027ethical\u0027 are the same thing; demonstrates that professional codes must balance idealism with practical enforceability to remain credible and followed",
"proeth-scenario:learningMoment": "Ethical analysis rarely produces simple binary answers. The BER\u0027s \u0027permissible but not ideal\u0027 conclusion teaches students that professional ethics involves degrees of compliance and that meeting the minimum standard is not the same as acting with full integrity. The ideal is a signed complaint; the minimum is any complaint. Students should aspire to the ideal while understanding the minimum.",
"proeth-scenario:narrativePacing": "aftermath",
"proeth-scenario:stakeholderConsequences": {
"engineer_a": "Conduct declared ethically permissible; no professional sanction; but implicitly encouraged to sign complaints in future situations",
"engineer_b": "Unaffected by the BER ruling directly; fate depends on the licensure board\u0027s investigation",
"engineering_profession": "Gains clearer normative guidance on a previously uncertain question; the self-regulatory system is strengthened by the clarification",
"future_engineers": "Now have a precedent establishing both the obligation to report and the permissibility (with caveats) of anonymous reporting"
},
"proeth:activatesConstraint": [
"Professional_Norm_Setting_Constraint",
"Guidance_For_Future_Cases_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/116#Action_Submit_Complaint_Anonymously",
"proeth:causesStateChange": "The ethical status of anonymous reporting is clarified from uncertain to \u0027permissible but suboptimal\u0027; a two-tier normative standard is established \u2014 signed complaints are the ethical ideal, anonymous complaints satisfy the minimum obligation; future engineers have clearer guidance",
"proeth:createsObligation": [
"Future_Engineers_Obligation_To_Report_When_Aware_Of_Violations",
"Preference_Obligation_To_Sign_Complaints_When_Safely_Possible"
],
"proeth:description": "The Board of Ethical Review\u0027s analysis concludes that anonymous reporting, while not ideal, is ethically permissible \u2014 establishing a normative outcome that defines the ethical status of Engineer A\u0027s conduct and creates guidance for future cases. This is an outcome of the BER\u0027s deliberative process.",
"proeth:emergencyStatus": "routine",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "At the conclusion of the BER\u0027s analysis; the final evaluative event in the narrative",
"proeth:urgencyLevel": "low",
"rdfs:label": "Ethical Permissibility Established"
}
Description: Engineer B commits what appears to be a serious professional conduct violation, creating an observable breach of engineering ethical or practice standards. This occurrence is independent of Engineer A's awareness and precedes any reporting obligation.
Temporal Marker: Prior to Engineer A's observation; exact timing unspecified but earliest event in the causal chain
Activates Constraints:
- Professional_Standards_Compliance_Constraint
- Public_Protection_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer B may be unaware of the ethical gravity of the conduct or may be rationalizing it; no emotional impact on Engineer A yet as observation has not occurred; potential public harm exists in latent form
- engineer_b: Professional standing at risk; potential disciplinary exposure; reputation vulnerable once violation becomes known
- public: Potentially exposed to harm or substandard engineering practice depending on nature of violation
- engineering_profession: Integrity of self-regulatory system implicated; peer reporting norms activated
- engineer_a: Not yet affected; consequence arrives only upon observation
Learning Moment: Professional violations do not require an observer to be ethically significant — they create real-world consequences and regulatory obligations the moment they occur. Students should understand that professional standards exist independently of enforcement.
Ethical Implications: Reveals the foundational tension between individual professional autonomy and the profession's collective responsibility to self-regulate for public protection; raises questions about what makes conduct a 'violation' versus a judgment call
- Does a professional ethics violation matter if no one observes it? What does your answer reveal about the purpose of professional codes?
- At what threshold does a professional conduct issue become 'serious' enough to trigger a peer reporting obligation?
- How does the fact that Engineer B is a stranger and non-competitor to Engineer A affect the ethical weight of the situation?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#Event_Professional_Violation_Occurs",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Does a professional ethics violation matter if no one observes it? What does your answer reveal about the purpose of professional codes?",
"At what threshold does a professional conduct issue become \u0027serious\u0027 enough to trigger a peer reporting obligation?",
"How does the fact that Engineer B is a stranger and non-competitor to Engineer A affect the ethical weight of the situation?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer B may be unaware of the ethical gravity of the conduct or may be rationalizing it; no emotional impact on Engineer A yet as observation has not occurred; potential public harm exists in latent form",
"proeth-scenario:ethicalImplications": "Reveals the foundational tension between individual professional autonomy and the profession\u0027s collective responsibility to self-regulate for public protection; raises questions about what makes conduct a \u0027violation\u0027 versus a judgment call",
"proeth-scenario:learningMoment": "Professional violations do not require an observer to be ethically significant \u2014 they create real-world consequences and regulatory obligations the moment they occur. Students should understand that professional standards exist independently of enforcement.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"engineer_a": "Not yet affected; consequence arrives only upon observation",
"engineer_b": "Professional standing at risk; potential disciplinary exposure; reputation vulnerable once violation becomes known",
"engineering_profession": "Integrity of self-regulatory system implicated; peer reporting norms activated",
"public": "Potentially exposed to harm or substandard engineering practice depending on nature of violation"
},
"proeth:activatesConstraint": [
"Professional_Standards_Compliance_Constraint",
"Public_Protection_Constraint"
],
"proeth:causesStateChange": "A reportable professional violation now exists in the world; the engineering community\u0027s self-regulatory mechanisms become relevant; Engineer B\u0027s licensure standing is potentially at risk",
"proeth:createsObligation": [
"Obligation_To_Report_Known_Violations (latent, not yet triggered until observed)",
"Licensure_Board_Investigative_Authority_Activated"
],
"proeth:description": "Engineer B commits what appears to be a serious professional conduct violation, creating an observable breach of engineering ethical or practice standards. This occurrence is independent of Engineer A\u0027s awareness and precedes any reporting obligation.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "Prior to Engineer A\u0027s observation; exact timing unspecified but earliest event in the causal chain",
"proeth:urgencyLevel": "high",
"rdfs:label": "Professional Violation Occurs"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: As an automatic consequence of Engineer A's observation and assessment of a serious violation, Engineer A's professional reporting obligation is activated under the state board's rules of professional conduct
Necessary Factors (NESS):
- Engineer A's direct observation of the violation
- Engineer A's assessment that the violation is serious and falls under reportable conduct
- Existence of a professional code or rule mandating reporting of such violations
Sufficient Factors:
- Observation + assessment of seriousness + applicable professional reporting rule = obligation automatically activated
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Violation Becomes Observed (Event 2)
Engineer A witnesses Engineer B's professional conduct violation -
Observe and Assess Violation (Action 1)
Engineer A consciously evaluates the conduct against professional standards -
Reporting Obligation Activated (Event 3)
Professional duty to report is automatically triggered by the assessment -
Decision to File Complaint (Action 2)
Engineer A decides to fulfill the activated obligation by filing a formal complaint -
Submit Complaint Anonymously (Action 3)
Engineer A chooses the manner of fulfilling the obligation — anonymously
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#CausalChain_8bb17ffd",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "As an automatic consequence of Engineer A\u0027s observation and assessment of a serious violation, Engineer A\u0027s professional reporting obligation is activated under the state board\u0027s rules of professional conduct",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A witnesses Engineer B\u0027s professional conduct violation",
"proeth:element": "Violation Becomes Observed (Event 2)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A consciously evaluates the conduct against professional standards",
"proeth:element": "Observe and Assess Violation (Action 1)",
"proeth:step": 2
},
{
"proeth:description": "Professional duty to report is automatically triggered by the assessment",
"proeth:element": "Reporting Obligation Activated (Event 3)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A decides to fulfill the activated obligation by filing a formal complaint",
"proeth:element": "Decision to File Complaint (Action 2)",
"proeth:step": 4
},
{
"proeth:description": "Engineer A chooses the manner of fulfilling the obligation \u2014 anonymously",
"proeth:element": "Submit Complaint Anonymously (Action 3)",
"proeth:step": 5
}
],
"proeth:cause": "Observe and Assess Violation (Action 1)",
"proeth:counterfactual": "If Engineer A had not observed or had not assessed the conduct as a serious violation, the reporting obligation would not have been triggered; similarly, without a governing professional rule, no formal obligation would exist",
"proeth:effect": "Reporting Obligation Activated (Event 3)",
"proeth:necessaryFactors": [
"Engineer A\u0027s direct observation of the violation",
"Engineer A\u0027s assessment that the violation is serious and falls under reportable conduct",
"Existence of a professional code or rule mandating reporting of such violations"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Observation + assessment of seriousness + applicable professional reporting rule = obligation automatically activated"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer B commits what appears to be a serious professional conduct violation, creating an observable situation that Engineer A witnesses, transforming a latent ethical situation into an active one
Necessary Factors (NESS):
- Engineer B's commission of a professional conduct violation
- Engineer A's physical or professional proximity to the violation
- Violation being of sufficient visibility or severity to be noticed
Sufficient Factors:
- Occurrence of violation + Engineer A's presence and awareness = observation event triggered
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Professional Violation Occurs (Event 1)
Engineer B commits a serious professional conduct violation against state board rules -
Violation Becomes Observed (Event 2)
Engineer A witnesses the violation, activating an ethical obligation scenario -
Observe and Assess Violation (Action 1)
Engineer A evaluates the severity and nature of what was witnessed -
Reporting Obligation Activated (Event 3)
Engineer A's professional duty to report is triggered by observation and assessment -
Decision to File Complaint (Action 2)
Engineer A makes the volitional decision to submit a formal complaint
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#CausalChain_fa79015c",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer B commits what appears to be a serious professional conduct violation, creating an observable situation that Engineer A witnesses, transforming a latent ethical situation into an active one",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B commits a serious professional conduct violation against state board rules",
"proeth:element": "Professional Violation Occurs (Event 1)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A witnesses the violation, activating an ethical obligation scenario",
"proeth:element": "Violation Becomes Observed (Event 2)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A evaluates the severity and nature of what was witnessed",
"proeth:element": "Observe and Assess Violation (Action 1)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A\u0027s professional duty to report is triggered by observation and assessment",
"proeth:element": "Reporting Obligation Activated (Event 3)",
"proeth:step": 4
},
{
"proeth:description": "Engineer A makes the volitional decision to submit a formal complaint",
"proeth:element": "Decision to File Complaint (Action 2)",
"proeth:step": 5
}
],
"proeth:cause": "Professional Violation Occurs (Event 1)",
"proeth:counterfactual": "Without Engineer B\u0027s violation occurring, there would be nothing for Engineer A to observe; the ethical dilemma would never have been activated",
"proeth:effect": "Violation Becomes Observed (Event 2)",
"proeth:necessaryFactors": [
"Engineer B\u0027s commission of a professional conduct violation",
"Engineer A\u0027s physical or professional proximity to the violation",
"Violation being of sufficient visibility or severity to be noticed"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"Occurrence of violation + Engineer A\u0027s presence and awareness = observation event triggered"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A makes the volitional decision to submit a formal complaint to the state engineering licensure board, and subsequently chooses to submit the complaint without identifying himself, resulting in the board receiving an anonymous complaint against Engineer B
Necessary Factors (NESS):
- Engineer A's volitional decision to file a complaint at all
- Engineer A's secondary decision to withhold his identity
- Existence and accessibility of the state engineering licensure board as a reporting body
Sufficient Factors:
- Decision to file + decision to remain anonymous + submission to the board = anonymous complaint received
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Reporting Obligation Activated (Event 3)
Engineer A's professional duty to report is triggered -
Decision to File Complaint (Action 2)
Engineer A volitionally decides to act on the obligation by filing formally -
Submit Complaint Anonymously (Action 3)
Engineer A chooses not to identify himself when submitting -
Anonymous Complaint Received (Event 4)
The state board receives the complaint without identifying information -
Ethical Permissibility Established (Event 6)
The Board of Ethical Review concludes anonymous reporting is ethically permissible under these circumstances
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#CausalChain_df6abd21",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A makes the volitional decision to submit a formal complaint to the state engineering licensure board, and subsequently chooses to submit the complaint without identifying himself, resulting in the board receiving an anonymous complaint against Engineer B",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A\u0027s professional duty to report is triggered",
"proeth:element": "Reporting Obligation Activated (Event 3)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A volitionally decides to act on the obligation by filing formally",
"proeth:element": "Decision to File Complaint (Action 2)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A chooses not to identify himself when submitting",
"proeth:element": "Submit Complaint Anonymously (Action 3)",
"proeth:step": 3
},
{
"proeth:description": "The state board receives the complaint without identifying information",
"proeth:element": "Anonymous Complaint Received (Event 4)",
"proeth:step": 4
},
{
"proeth:description": "The Board of Ethical Review concludes anonymous reporting is ethically permissible under these circumstances",
"proeth:element": "Ethical Permissibility Established (Event 6)",
"proeth:step": 5
}
],
"proeth:cause": "Decision to File Complaint (Action 2)",
"proeth:counterfactual": "Without Engineer A\u0027s decision to file, no complaint would have been received; without the anonymity decision specifically, the complaint would have been received but with identifying information, altering the board\u0027s procedural handling",
"proeth:effect": "Anonymous Complaint Received (Event 4)",
"proeth:necessaryFactors": [
"Engineer A\u0027s volitional decision to file a complaint at all",
"Engineer A\u0027s secondary decision to withhold his identity",
"Existence and accessibility of the state engineering licensure board as a reporting body"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Decision to file + decision to remain anonymous + submission to the board = anonymous complaint received"
],
"proeth:withinAgentControl": true
}
Causal Language: The Board of Ethical Review's analysis concludes that anonymous reporting, while not ideal, is ethically permissible, with Engineer A's act of anonymous submission being the direct subject of the ethical review that produces this determination
Necessary Factors (NESS):
- Engineer A's act of submitting the complaint anonymously
- The complaint being referred to or reviewed by the Board of Ethical Review
- The Board's application of professional ethics standards to the anonymous submission
- The BER 89-7 precedent establishing the harms of non-reporting as a comparative baseline
Sufficient Factors:
- Anonymous submission + BER review + professional ethics standards + BER 89-7 precedent = ethical permissibility determination
Responsibility Attribution:
Agent: Board of Ethical Review (determination); Engineer A (conduct under review)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Submit Complaint Anonymously (Action 3)
Engineer A submits the complaint without identifying himself -
Anonymous Complaint Received (Event 4)
The state board receives and processes the anonymous complaint -
BER Ethical Review Initiated
The Board of Ethical Review examines whether anonymous reporting satisfies professional obligations -
BER 89-7 Precedent Applied
The BER weighs the harms of non-reporting (BER 89-7) against the imperfection of anonymous reporting -
Ethical Permissibility Established (Event 6)
BER concludes anonymous reporting is ethically permissible, though identified reporting remains the ideal
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#CausalChain_4b95a824",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "The Board of Ethical Review\u0027s analysis concludes that anonymous reporting, while not ideal, is ethically permissible, with Engineer A\u0027s act of anonymous submission being the direct subject of the ethical review that produces this determination",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A submits the complaint without identifying himself",
"proeth:element": "Submit Complaint Anonymously (Action 3)",
"proeth:step": 1
},
{
"proeth:description": "The state board receives and processes the anonymous complaint",
"proeth:element": "Anonymous Complaint Received (Event 4)",
"proeth:step": 2
},
{
"proeth:description": "The Board of Ethical Review examines whether anonymous reporting satisfies professional obligations",
"proeth:element": "BER Ethical Review Initiated",
"proeth:step": 3
},
{
"proeth:description": "The BER weighs the harms of non-reporting (BER 89-7) against the imperfection of anonymous reporting",
"proeth:element": "BER 89-7 Precedent Applied",
"proeth:step": 4
},
{
"proeth:description": "BER concludes anonymous reporting is ethically permissible, though identified reporting remains the ideal",
"proeth:element": "Ethical Permissibility Established (Event 6)",
"proeth:step": 5
}
],
"proeth:cause": "Submit Complaint Anonymously (Action 3)",
"proeth:counterfactual": "If Engineer A had filed with full identification, the ethical permissibility question would not have arisen; if Engineer A had not filed at all, the BER 89-7 precedent suggests a finding of ethical violation rather than permissibility",
"proeth:effect": "Ethical Permissibility Established (Event 6)",
"proeth:necessaryFactors": [
"Engineer A\u0027s act of submitting the complaint anonymously",
"The complaint being referred to or reviewed by the Board of Ethical Review",
"The Board\u0027s application of professional ethics standards to the anonymous submission",
"The BER 89-7 precedent establishing the harms of non-reporting as a comparative baseline"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Board of Ethical Review (determination); Engineer A (conduct under review)",
"proeth:sufficientFactors": [
"Anonymous submission + BER review + professional ethics standards + BER 89-7 precedent = ethical permissibility determination"
],
"proeth:withinAgentControl": true
}
Causal Language: In the referenced prior case (BER Case 89-7), the engineer's failure to report known electrical and safety violations resulted in harm materializing, establishing the precedent that non-reporting of serious violations carries direct causal responsibility for resulting harm
Necessary Factors (NESS):
- Engineer's knowledge of the existing electrical and safety violations
- Engineer's volitional decision not to report those violations
- Absence of any other reporting mechanism that could have substituted for the engineer's report
- Causal connection between the unreported violations and the harm that materialized
Sufficient Factors:
- Known violations + deliberate non-reporting + no alternative reporting pathway + harm-prone conditions = harm materializes
Responsibility Attribution:
Agent: Engineer A in BER Case 89-7 (the non-reporting engineer)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Safety Violations Exist (BER 89-7 context)
Known electrical and safety violations are present in the engineering context -
Withhold Safety Violation Report (Action 4)
Engineer in BER 89-7 chooses not to report the known violations -
Violations Persist Uncorrected
Without reporting, no corrective action is taken and hazardous conditions remain -
BER 89-7 Safety Harm Materializes (Event 5)
The unreported violations result in actual harm occurring -
Ethical Permissibility Established (Event 6)
BER 89-7 outcome informs the current case analysis, reinforcing that reporting — even anonymously — is ethically required and that non-reporting bears causal responsibility for resulting harm
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/116#",
"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/116#CausalChain_80aa6d6e",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "In the referenced prior case (BER Case 89-7), the engineer\u0027s failure to report known electrical and safety violations resulted in harm materializing, establishing the precedent that non-reporting of serious violations carries direct causal responsibility for resulting harm",
"proeth:causalSequence": [
{
"proeth:description": "Known electrical and safety violations are present in the engineering context",
"proeth:element": "Safety Violations Exist (BER 89-7 context)",
"proeth:step": 1
},
{
"proeth:description": "Engineer in BER 89-7 chooses not to report the known violations",
"proeth:element": "Withhold Safety Violation Report (Action 4)",
"proeth:step": 2
},
{
"proeth:description": "Without reporting, no corrective action is taken and hazardous conditions remain",
"proeth:element": "Violations Persist Uncorrected",
"proeth:step": 3
},
{
"proeth:description": "The unreported violations result in actual harm occurring",
"proeth:element": "BER 89-7 Safety Harm Materializes (Event 5)",
"proeth:step": 4
},
{
"proeth:description": "BER 89-7 outcome informs the current case analysis, reinforcing that reporting \u2014 even anonymously \u2014 is ethically required and that non-reporting bears causal responsibility for resulting harm",
"proeth:element": "Ethical Permissibility Established (Event 6)",
"proeth:step": 5
}
],
"proeth:cause": "Withhold Safety Violation Report (Action 4 \u2014 BER 89-7)",
"proeth:counterfactual": "Had the engineer in BER 89-7 reported the known violations, corrective action could have been taken and the resulting harm would likely have been prevented or mitigated",
"proeth:effect": "BER 89-7 Safety Harm Materializes (Event 5)",
"proeth:necessaryFactors": [
"Engineer\u0027s knowledge of the existing electrical and safety violations",
"Engineer\u0027s volitional decision not to report those violations",
"Absence of any other reporting mechanism that could have substituted for the engineer\u0027s report",
"Causal connection between the unreported violations and the harm that materialized"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer A in BER Case 89-7 (the non-reporting engineer)",
"proeth:sufficientFactors": [
"Known violations + deliberate non-reporting + no alternative reporting pathway + harm-prone conditions = harm materializes"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (6)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineer A's structural tests on building (BER Case 89-7) |
before
Entity1 is before Entity2 |
client's disclosure of electrical and mechanical deficiencies (BER Case 89-7) |
time:before
http://www.w3.org/2006/time#before |
Engineer A performed several structural tests on the building and determined that the building is st... [more] |
| Engineer A's observation of Engineer B's violation |
before
Entity1 is before Entity2 |
Engineer A's submission of anonymous complaint |
time:before
http://www.w3.org/2006/time#before |
Engineer A observes what he believes is a serious violation... Thereafter, Engineer A submits an ano... [more] |
| client's disclosure of building deficiencies to Engineer A (BER Case 89-7) |
during
Entity1 occurs entirely within the duration of Entity2 |
Engineer A's provision of structural engineering services (BER Case 89-7) |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
during the course of providing services, the client confided in Engineer A and informed him that the... [more] |
| Engineer A's structural investigation (BER Case 89-7) |
before
Entity1 is before Entity2 |
planned sale of the building (BER Case 89-7) |
time:before
http://www.w3.org/2006/time#before |
his client was planning to sell... he is not planning to take any remedial action to repair or renov... [more] |
| Engineer A informing client of deficiencies (BER Case 89-7) |
before
Entity1 is before Entity2 |
Engineer A writing structural report (BER Case 89-7) |
time:before
http://www.w3.org/2006/time#before |
Engineer A did realize those deficiencies could cause injury to the occupants of the building and so... [more] |
| BER Case 89-7 ruling |
before
Entity1 is before Entity2 |
present case analysis |
time:before
http://www.w3.org/2006/time#before |
The Board has addressed issues relating to the obligations of engineers to report violations and imp... [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.