{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Action_Accept_Development_Analysis_Engagement",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the engagement due to perceived conflicts of interest or insufficient expertise in wetlands-adjacent environmental analysis",
    "Accept the engagement but proactively disclose to the client upfront that any material environmental findings \u2014 including threats to protected species \u2014 will be fully documented in all written deliverables",
    "Accept the engagement with a narrowed scope explicitly excluding ecological or species-impact assessment, and recommend the client separately retain a qualified ecologist"
  ],
  "proeth-scenario:characterMotivation": "Engineer A accepted the engagement as a routine professional service opportunity, motivated by business development, client relationship maintenance, and the legitimate professional role of environmental engineers in evaluating land development feasibility. There is no indication of improper intent at this stage \u2014 acceptance reflected standard practice.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining would have avoided the ethical dilemma entirely but foregone legitimate professional work; it would only be ethically required if Engineer A lacked competence or had a genuine conflict of interest \u2014 neither of which is established in the case.",
    "Proactively setting disclosure expectations at engagement would have created a transparent framework, likely preventing the later omission by aligning client expectations with professional obligations from the start \u2014 this is arguably the most constructive alternative.",
    "Narrowing scope might have been appropriate if ecological assessment was outside the firm\u0027s competence, but it would not relieve Engineer A of the obligation to flag known environmental risks encountered during the analysis, and could create a false sense of a \u0027clean\u0027 report."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that professional ethical obligations are not triggered only at moments of crisis \u2014 they attach at the point of engagement. Students should recognize that accepting an environmental analysis assignment adjacent to protected lands implicitly commits the engineer to honest, complete reporting regardless of findings, and that this commitment exists before any data is collected.",
  "proeth-scenario:ethicalTension": "Commercial interest in securing and retaining client work versus the prospective but not-yet-realized obligation to serve the public interest. At the point of engagement acceptance, these tensions are latent rather than active, but the engineer\u0027s dual accountability to client and public is established from the outset.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Establishes the professional relationship and scope of duty. If Engineer A later compromises the integrity of the analysis, the reputational, legal, and ethical consequences trace back to this foundational commitment. A protected wetlands adjacency signals elevated environmental sensitivity that a competent engineer should recognize as a risk factor from the start.",
  "proeth:description": "Engineer A, as principal of an environmental engineering firm, accepted a client request to prepare an analysis of property adjacent to a wetlands area for potential residential condominium development. This decision initiated Engineer A\u0027s professional obligations to both the developer client and the broader public interest.",
  "proeth:foreseenUnintendedEffects": [
    "Potential discovery of environmental concerns that could conflict with client\u0027s development interests",
    "Creation of fiduciary and reporting obligations to both client and public authority"
  ],
  "proeth:fulfillsObligation": [
    "Provision of professional engineering services within area of competence (environmental engineering)",
    "Responsiveness to client needs"
  ],
  "proeth:guidedByPrinciple": [
    "Professional competence and service",
    "Faithful agency to client",
    "NSPE Code Section III.2.d. \u2014 encouragement to adhere to sustainable development principles"
  ],
  "proeth:hasAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide professional environmental analysis services to developer client and fulfill contractual obligations",
  "proeth:requiresCapability": [
    "Environmental engineering analysis",
    "Wetlands assessment",
    "Regulatory knowledge of federal and state environmental law",
    "Project management of multidisciplinary team including biologists"
  ],
  "proeth:temporalMarker": "At project inception, prior to analysis",
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Development Analysis Engagement"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Action_Integrate_Biologist_s_Threatened_Species_Finding",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Dismiss or minimize the biologist\u0027s finding on the grounds that it is speculative or outside the strict scope of the property analysis, and exclude it from further consideration",
    "Immediately communicate to the client in writing that the biologist\u0027s finding is material and will be included in the final report, giving the client the opportunity to adjust the project scope or consult legal counsel before submission",
    "Pause the analysis and recommend the client commission a formal species-impact study before proceeding, ensuring the finding is addressed with appropriate rigor before any report is submitted to a public authority"
  ],
  "proeth-scenario:characterMotivation": "Engineer A, acting as principal of the firm, treated the biologist\u0027s finding as professionally credible and materially relevant to the analysis \u2014 a reasonable and ethically appropriate response. The motivation was likely a combination of professional diligence, recognition of the biologist\u0027s expertise, and awareness that ignoring a threatened-species concern could expose the firm to liability. However, integrating the finding into the analysis did not automatically translate into full disclosure, revealing a gap between internal acknowledgment and external reporting.",
  "proeth-scenario:consequencesIfAlternative": [
    "Dismissing the finding would compound the ethical violation and potentially constitute professional negligence; it would also expose the firm to greater liability if the species impact materialized post-development.",
    "Written communication to the client at this stage would have been the most professionally transparent course \u2014 it would have preserved the engineer-client relationship while establishing a clear record that the finding was disclosed and would be reported, likely preventing the subsequent omission.",
    "Recommending a formal species-impact study would reflect best practice in environmental engineering, potentially delaying the project but ensuring regulatory compliance and protecting both the client and the public from downstream legal and environmental consequences."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethical failure is not always a matter of ignoring inconvenient findings \u2014 it can involve acknowledging a finding internally while failing to carry that acknowledgment through to all required disclosures. Students should understand that \u0027knowing but not fully reporting\u0027 is itself an ethical violation, and that the integrity of a professional report depends on consistency between what the engineer knows and what the engineer documents.",
  "proeth-scenario:ethicalTension": "Epistemic integrity (accurately representing what the analysis found) versus client-serving pressure to minimize findings that could jeopardize the development proposal. Engineer A\u0027s decision to treat the finding as material internally was correct, but the tension between serving the client\u0027s commercial interests and serving the public\u0027s right to complete information began to intensify at this stage.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The threatened bird species and its protected wetlands habitat are at risk if the finding is not properly communicated to decision-makers. The developer faces potential regulatory and legal exposure if the project proceeds without addressing the concern. Engineer A\u0027s professional credibility and license are at risk if the omission is later discovered. The public authority\u0027s ability to make an informed regulatory decision is contingent on receiving complete information.",
  "proeth:description": "Upon receiving the biologist\u0027s report that the condominium project could threaten a \u0027threatened\u0027 bird species inhabiting the adjacent protected wetlands, Engineer A incorporated this finding into the firm\u0027s ongoing analysis rather than dismissing or disregarding it. This decision to treat the biologist\u0027s report as a material finding set the stage for subsequent disclosure decisions.",
  "proeth:foreseenUnintendedEffects": [
    "Finding would need to be communicated to client and potentially to public authority",
    "Finding could jeopardize or complicate developer\u0027s project approval"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to oversee and integrate work of subordinate team members",
    "Obligation to consider all relevant and pertinent environmental information in the course of professional analysis",
    "NSPE Code Section II.3.a. \u2014 objectivity and truthfulness in professional reports"
  ],
  "proeth:guidedByPrinciple": [
    "Objectivity and completeness in professional analysis",
    "Reliance on qualified specialists within the firm",
    "NSPE Code Section III.2.d. \u2014 sustainable development and environmental protection for future generations"
  ],
  "proeth:hasAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client interest in unimpeded development vs. professional obligation to account for material environmental findings",
    "proeth:resolutionReasoning": "Engineer A treated the finding as material, consistent with professional obligation to be objective and thorough, though ultimate disclosure decisions remained pending"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Acknowledge and process a professionally significant environmental finding generated by a qualified member of the engineering team",
  "proeth:requiresCapability": [
    "Environmental engineering judgment to evaluate significance of biologist\u0027s finding",
    "Supervisory and integrative capacity over multidisciplinary team",
    "Knowledge of threatened species regulatory framework"
  ],
  "proeth:temporalMarker": "During the firm\u0027s analysis, after biologist\u0027s internal report",
  "proeth:withinCompetence": true,
  "rdfs:label": "Integrate Biologist\u0027s Threatened Species Finding"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Action_Verbally_Disclose_Concern_to_Client",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Follow up the verbal discussion with a written memorandum to the client documenting the biologist\u0027s finding and Engineer A\u0027s professional assessment of its significance, creating a formal record of disclosure",
    "Inform the client verbally and simultaneously notify them that the finding will be included in the written report submitted to the public authority, giving the client the option to withdraw or modify the proposal before submission",
    "Recommend that the client retain independent legal counsel to assess the regulatory implications of the threatened species finding before the report is finalized and submitted"
  ],
  "proeth-scenario:characterMotivation": "Engineer A likely chose verbal disclosure as a compromise \u2014 satisfying a personal sense of having \u0027told the client\u0027 while avoiding the formal documentation that would have obligated both parties to address the finding more rigorously. This may reflect a desire to maintain the client relationship, avoid conflict, or preserve the project\u0027s viability, while still being able to claim the concern was communicated. It may also reflect a misunderstanding of what constitutes adequate professional disclosure.",
  "proeth-scenario:consequencesIfAlternative": [
    "A written follow-up memo would have created an auditable record of disclosure and signaled to the client that the finding was being treated with professional seriousness, making it far less likely that the omission from the written report would occur \u2014 or go unnoticed.",
    "Notifying the client that the finding would appear in the written report would have respected both the client relationship and the public interest, giving the client agency while preserving the engineer\u0027s professional integrity; this is arguably the most ethically complete alternative at this stage.",
    "Recommending legal counsel would have been prudent risk management for the client and would have introduced a third professional voice reinforcing the seriousness of the finding, potentially creating the conditions for a more complete and compliant submission."
  ],
  "proeth-scenario:decisionSignificance": "This action is a critical teaching moment about the difference between disclosure and adequate disclosure. Verbal communication of a material environmental finding to a private client does not fulfill the engineer\u0027s obligation to ensure that a public authority receives complete information. Students should learn that the medium and formality of disclosure matter \u2014 especially when a written report is the primary instrument through which a regulatory body will evaluate a proposal. Oral disclosure that is not followed through in writing can function as a way of technically \u0027saying something\u0027 while practically ensuring it has no regulatory effect.",
  "proeth-scenario:ethicalTension": "Loyalty to the client\u0027s commercial interests and the engineer-client relationship versus the obligation to communicate material findings completely and in a form that ensures they are acted upon. There is also a tension between the engineer\u0027s comfort with informal communication norms and the formal accountability structures of public regulatory processes, which require written documentation to function properly.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "This is the pivotal decision point of the case. The engineer\u0027s choice of verbal-only disclosure determines whether the public authority will have access to material environmental information. The stakes include: the integrity of the regulatory review process, the protection of a threatened species and its habitat, the developer\u0027s legal exposure if the project proceeds on the basis of an incomplete report, and Engineer A\u0027s professional standing and potential license consequences.",
  "proeth:description": "In subsequent discussions with the developer client, Engineer A chose to verbally mention the biologist\u0027s concern about the threatened bird species rather than formally documenting it or escalating it to a written recommendation. This oral disclosure was Engineer A\u0027s primary \u2014 and ultimately insufficient \u2014 mechanism for communicating a material environmental finding to the client.",
  "proeth:foreseenUnintendedEffects": [
    "Client would be aware of the concern but could choose to ignore it without a written record",
    "Public authority reviewing the development proposal would remain uninformed",
    "Engineer A\u0027s professional reporting obligations under NSPE Code Section II.3.a. would remain unfulfilled"
  ],
  "proeth:fulfillsObligation": [
    "Partial fulfillment of duty to inform client of material findings affecting the project",
    "Faithful communication with client as agent/trustee"
  ],
  "proeth:guidedByPrinciple": [
    "Client faithfulness and agency",
    "Minimum disclosure as a compromise between competing obligations",
    "Avoidance of harm to client\u0027s business interests"
  ],
  "proeth:hasAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client interest in unimpeded development vs. public authority\u0027s right to complete environmental information and protection of threatened species",
    "proeth:resolutionReasoning": "Engineer A chose verbal disclosure as a compromise, apparently prioritizing client business interests and avoiding formal documentation of an adverse finding; the Board found this resolution ethically inadequate given Engineer A\u0027s competence, the unambiguous nature of the finding, the absence of client confidentiality claims, and the obligations under NSPE Code Sections II.3.a. and III.2.d."
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Satisfy a perceived minimum disclosure obligation to the client while avoiding formal documentation of an adverse finding that could complicate the developer\u0027s project approval",
  "proeth:requiresCapability": [
    "Environmental engineering judgment to assess significance of threatened species concern",
    "Client communication and advisory skills",
    "Knowledge of professional reporting obligations under the NSPE Code"
  ],
  "proeth:temporalMarker": "During subsequent client discussions, after biologist\u0027s internal report and before written report submission",
  "proeth:violatesObligation": [
    "NSPE Code Section II.3.a. \u2014 obligation to be objective and truthful in professional reports and to include all relevant and pertinent information",
    "NSPE Code Section III.2.d. \u2014 encouragement to adhere to sustainable development principles protecting the environment for future generations",
    "Obligation to hold paramount public health, safety, and environmental welfare over client interests",
    "Obligation to provide complete and accurate information to the public authority reviewing the development proposal"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Verbally Disclose Concern to Client"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Action_Omit_Finding_from_Written_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Include the biologist\u0027s threatened species finding in the written report with a full professional assessment of its implications, fulfilling the obligation to provide complete and objective information to the public authority",
    "Include the finding in the report but frame it conservatively \u2014 acknowledging the concern while recommending further study \u2014 thereby informing the public authority without prejudging the outcome",
    "Refuse to submit the written report until the client agrees to either address the threatened species concern through additional study or accept that the finding will be disclosed in the report as submitted"
  ],
  "proeth-scenario:characterMotivation": "Engineer A\u0027s decision to omit the finding from the written report was most likely motivated by a desire to protect the client\u0027s development interests, avoid producing a report that would trigger regulatory scrutiny or project denial, and preserve the business relationship. Engineer A may have rationalized the omission by pointing to the verbal disclosure as sufficient, or by characterizing the biologist\u0027s concern as speculative rather than definitive. This reflects a pattern of motivated reasoning in which professional judgment is shaped by desired outcomes rather than objective analysis.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full inclusion would have fulfilled Engineer A\u0027s ethical and professional obligations, provided the public authority with the information needed for an informed decision, and \u2014 while potentially jeopardizing the development \u2014 protected the engineer, the client, and the public from downstream legal and environmental consequences. This is the action the NSPE BER concluded was required.",
    "Conservative framing with a recommendation for further study would have been ethically compliant and professionally defensible \u2014 it would have disclosed the finding without overstating its certainty, and would have given the regulatory body and the client a constructive path forward rather than a binary outcome.",
    "Conditioning report submission on client agreement to disclosure would have been a strong professional boundary-setting action; while it might have resulted in the client terminating the engagement, it would have protected Engineer A\u0027s integrity and avoided the ethical violation entirely \u2014 illustrating that professional independence sometimes requires accepting business consequences."
  ],
  "proeth-scenario:decisionSignificance": "This action represents the central ethical violation of the case and carries the most direct teaching value. Students should understand: (1) that written professional reports submitted to public authorities carry a higher standard of completeness than private client communications; (2) that omission of material information is an active ethical violation, not merely a passive failure; (3) that verbal disclosure to a private party does not substitute for written disclosure to a regulatory body; (4) that the NSPE Code\u0027s evolution \u2014 particularly the addition of sustainable development obligations \u2014 reinforces rather than creates this duty; and (5) that engineers who allow client interests to override public disclosure obligations risk their professional license, public trust in the profession, and real-world environmental harm.",
  "proeth-scenario:ethicalTension": "The starkest ethical conflict in the case: the engineer\u0027s contractual and relational obligation to the client directly collides with the engineer\u0027s duty to the public and to the integrity of the regulatory process. NSPE Code obligations \u2014 including the duty to hold public safety and welfare paramount, to be objective and truthful in professional reports, and (post-2006) to consider sustainable development \u2014 all point unambiguously toward inclusion. The omission represents a choice to subordinate public interest to client interest in the most consequential possible context.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Maximum stakes across all dimensions: a threatened bird species and protected wetland habitat may be irreversibly harmed; the public authority is deprived of information essential to its regulatory function; the developer may proceed with a project that later faces legal challenge or regulatory sanction; Engineer A faces potential license revocation, professional censure, and civil liability; and the credibility of environmental engineering as a profession that serves the public interest is undermined.",
  "proeth:description": "Engineer A made the deliberate decision not to include the biologist\u0027s threatened species concern in the written report submitted to the public authority considering the developer\u0027s proposal. This omission constituted the central ethical violation identified by the NSPE Board of Ethical Review, as it deprived the public authority of material environmental information relevant to its regulatory decision.",
  "proeth:foreseenUnintendedEffects": [
    "Public authority would make a regulatory decision without full environmental information",
    "Threatened bird species and adjacent protected wetlands would remain unprotected through the regulatory process",
    "Engineer A\u0027s professional reporting obligations would be violated",
    "If the project proceeded and harmed the threatened species, Engineer A\u0027s omission could be implicated in the resulting environmental damage"
  ],
  "proeth:fulfillsObligation": [
    "Protection of developer client\u0027s immediate commercial interests (though not a recognized ethical justification under the circumstances)"
  ],
  "proeth:guidedByPrinciple": [
    "Client faithfulness and fiduciary duty as agent/trustee",
    "Avoidance of harm to client\u0027s business interests",
    "Misapplication of confidentiality principles where no confidentiality was requested"
  ],
  "proeth:hasAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Developer client\u0027s commercial interest in project approval vs. public authority\u0027s right to complete environmental information and protection of threatened species and wetlands",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by omitting the finding, effectively prioritizing client commercial interests over public reporting obligations. The NSPE Board of Ethical Review concluded this resolution was ethically impermissible: unlike BER 89-7 (where confidentiality was requested and engineer lacked relevant expertise) and BER 97-13 (where findings were speculative and outside engineer\u0027s expertise), Engineer A here had technical competence, the findings were unambiguous, no confidentiality was requested, and the obligations under NSPE Code Sections II.3.a. and III.2.d. clearly required inclusion of the information in the written report."
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Protect the developer client\u0027s interests by preventing adverse environmental findings from entering the public record and potentially obstructing project approval",
  "proeth:requiresCapability": [
    "Environmental engineering judgment to assess materiality and relevance of threatened species finding",
    "Professional report writing for public authority submission",
    "Knowledge of NSPE Code reporting obligations",
    "Understanding of federal and state threatened species regulatory framework"
  ],
  "proeth:temporalMarker": "At report preparation and submission stage, before public authority review",
  "proeth:violatesObligation": [
    "NSPE Code Section II.3.a. \u2014 obligation to be objective and truthful in professional reports, statements, or testimony and to include all relevant and pertinent information",
    "NSPE Code Section III.2.d. \u2014 obligation (or strong encouragement) to adhere to sustainable development principles to protect the environment for future generations",
    "Fundamental obligation to hold paramount the safety, health, and welfare of the public",
    "Obligation to provide complete and accurate information to a public authority conducting regulatory review",
    "Obligation not to suppress material findings generated by qualified team members"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Omit Finding from Written Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Event_BER_Ethical_Violation_Conclusion_Reached",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "The BER concluded that Engineer A was obligated to include the finding in the written report \u2014 does this conclusion change your assessment of whether Engineer A acted in good faith, and why does good faith not excuse the omission?",
    "How does the BER\u0027s reference to prior cases (89-7, 97-13, 04-8) function in professional ethics reasoning \u2014 what role does precedent play in engineering ethics compared to legal ethics?",
    "If you were Engineer A receiving this BER conclusion, what steps would you take next, and what does your answer reveal about the ongoing nature of professional ethical obligations?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "For Engineer A, the conclusion carries professional consequences and reputational impact; for the developer client, the conclusion may create legal and regulatory exposure; for the engineering profession, the conclusion reinforces the primacy of public welfare over client interests; for students, the conclusion provides clear authoritative guidance on the correct course of action",
  "proeth-scenario:ethicalImplications": "Demonstrates the institutional enforcement dimension of professional ethics \u2014 individual conduct is subject to collective professional judgment; illustrates how the public welfare mandate operates as a constraint that overrides client preference in cases of material environmental risk; raises questions about the relationship between legal compliance and ethical obligation; shows how the BER process translates abstract ethical principles into concrete professional standards with practical guidance for practitioners",
  "proeth-scenario:learningMoment": "The BER conclusion demonstrates that professional ethics violations have real consequences and that the engineering profession takes its public welfare obligations seriously. Students should understand that the BER process exists precisely to adjudicate ambiguous cases and establish clear professional standards \u2014 and that the conclusion here is unambiguous: material environmental findings must be included in written reports to public authorities, regardless of client preference.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "developer_client": "Development proposal may face renewed scrutiny if the BER conclusion prompts disclosure of the omitted finding to the public authority",
    "engineer_a": "Professional ethics violation formally established; potential licensure, disciplinary, and reputational consequences; the conclusion may prompt corrective action regarding the original omission",
    "engineering_profession": "The conclusion reinforces professional norms and provides clear precedent for future cases involving environmental disclosure obligations",
    "engineering_students_and_practitioners": "The published BER opinion serves as an educational resource establishing clear professional standards",
    "public_authority": "May become aware of the omission and be able to fulfill its regulatory mandate with complete information",
    "threatened_bird_species_and_wetlands": "If the BER conclusion leads to proper disclosure, ecological protection mechanisms may yet be activated"
  },
  "proeth:activatesConstraint": [
    "Professional_Accountability_Constraint",
    "Precedent_Setting_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/83#Action_Omit_Finding_from_Written_Report",
  "proeth:causesStateChange": "Engineer A\u0027s conduct is formally adjudicated as a professional ethics violation; the BER conclusion establishes precedent for how similar cases should be handled; the professional standard for environmental disclosure in engineering reports is authoritatively clarified",
  "proeth:createsObligation": [
    "Engineer_A_Remediate_Omission_If_Possible",
    "Profession_Wide_Adherence_To_Established_Standard"
  ],
  "proeth:description": "The NSPE Board of Ethical Review concludes, after analyzing the facts against the Code of Ethics and prior BER cases, that Engineer A was obligated to include the environmental threat information in the written report submitted to the public authority. This conclusion constitutes an authoritative professional ethics judgment.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "At conclusion of BER case analysis \u2014 post-facto evaluation",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "BER Ethical Violation Conclusion Reached"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Event_NSPE_Code_Section_III_2_d_Enacted",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the evolution of the NSPE Code to include sustainable development obligations change what engineers are required to consider and disclose in environmental analyses?",
    "Should an engineer\u0027s ethical obligations regarding environmental findings exist independently of whether a specific code section addresses them \u2014 or does codification matter?",
    "How should engineers stay current with code revisions, and what is the professional consequence of ignorance of updated standards?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "For engineers practicing at the time, the code addition signals a shift in professional expectations; for Engineer A specifically, it means the omission is evaluated against an explicit standard rather than general principles alone; for students, it illustrates that professional ethics is a living, evolving framework",
  "proeth-scenario:ethicalImplications": "Illustrates the dynamic nature of professional ethics and the role of professional societies in setting evolving standards; raises questions about whether ethical obligations precede their codification; demonstrates the relationship between societal values (environmental protection), professional norms, and formal code language; highlights the sustainable development obligation as a specific instantiation of the broader public welfare mandate",
  "proeth-scenario:learningMoment": "Professional ethics codes are not static \u2014 they evolve to reflect emerging societal values and professional responsibilities. The addition of Section III.2.d demonstrates that the engineering profession has formally recognized sustainable development as a core obligation, not merely a best practice. Students should understand that staying current with code revisions is itself a professional responsibility.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Conduct is evaluated against a specific, recently codified standard \u2014 the code evolution strengthens the BER\u0027s conclusion that Engineer A violated professional obligations",
    "engineering_profession": "The code addition reflects and reinforces the profession\u0027s commitment to environmental stewardship as a core value",
    "future_engineers": "The code evolution sets a clear standard for how environmental findings must be handled in professional practice",
    "public_and_environment": "Formal codification of sustainable development obligations strengthens the protective framework for environmental interests in engineering practice"
  },
  "proeth:activatesConstraint": [
    "NSPE_Code_III.2.d_Sustainable_Development_Constraint",
    "Environmental_Stewardship_Professional_Obligation"
  ],
  "proeth:causesStateChange": "The professional standard governing environmental disclosure in engineering practice is formally elevated; Engineer A\u0027s conduct is now evaluated against an explicit sustainable development obligation codified in the NSPE Code",
  "proeth:createsObligation": [
    "Adhere_To_Sustainable_Development_Standards_In_Practice",
    "Consider_Environmental_Impact_In_Engineering_Analysis"
  ],
  "proeth:description": "The NSPE Board of Ethical Review contextualizes Engineer A\u0027s conduct against the January 2006 addition (and July 2007 modification) of Section III.2.d to the NSPE Code of Ethics, which addresses sustainable development obligations. This code evolution establishes the formal professional standard against which Engineer A\u0027s omission is evaluated.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "January 2006 (addition); July 2007 (modification) \u2014 referenced in Discussion section as backdrop to case evaluation",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "NSPE Code Section III.2.d Enacted"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Event_Threatened_Species_Risk_Identified",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At the moment the biologist identifies the threatened species risk, what obligations does Engineer A immediately acquire, and to whom are those obligations owed?",
    "Does the fact that Engineer A verbally informed the client of the concern satisfy the ethical obligation to disclose \u2014 and if not, why is the written report to the public authority specifically required?",
    "How should an engineer balance a client\u0027s financial interests against environmental findings that could materially affect a public regulatory review?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "The biologist experiences professional duty and concern for the species; Engineer A faces immediate tension between client loyalty and environmental obligation; the developer client may feel threatened by the discovery; public stakeholders remain unaware but would be materially affected",
  "proeth-scenario:ethicalImplications": "Reveals the foundational tension in engineering ethics between client service and public welfare obligations; demonstrates that environmental knowledge is not proprietary to the client relationship but carries duties to the broader public; raises questions about the sufficiency of partial disclosure (verbal vs. written) and whether form of disclosure matters ethically; connects to NSPE Code obligations regarding sustainable development and honest reporting",
  "proeth-scenario:learningMoment": "This event illustrates that professional knowledge creates professional obligation \u2014 once an engineer\u0027s team identifies a material environmental risk, the engineer cannot selectively disclose it. The discovery is a turning point where Engineer A\u0027s subsequent choices will define their ethical standing. Students should understand that environmental findings in engineering analysis are not optional disclosures subject to client preference.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "biologist": "Professional finding is on record; has a stake in whether their expert assessment is properly communicated and acted upon",
    "developer_client": "Development plans may be significantly constrained or delayed; financial interests are directly threatened by the finding",
    "engineer_a": "Now bears direct knowledge of an environmental risk, creating inescapable ethical and professional obligations; failure to act fully exposes Engineer A to professional discipline and legal liability",
    "general_public": "Residents near the development and the broader public have an interest in environmental protection that is activated by this finding",
    "public_authority": "Without disclosure, the reviewing authority cannot fulfill its regulatory function; its decision-making is compromised",
    "threatened_bird_species_and_wetlands": "Future survival of the species and integrity of the protected wetlands depend on whether this finding is properly disclosed and acted upon"
  },
  "proeth:activatesConstraint": [
    "PublicWelfare_Protection_Constraint",
    "Environmental_Harm_Prevention_Constraint",
    "Endangered_Species_Act_Compliance_Constraint",
    "Honest_Reporting_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/83#Action_Accept_Development_Analysis_Engagement",
  "proeth:causesStateChange": "Project status elevated from routine analysis to environmentally sensitive review; Engineer A now possesses knowledge of a material environmental risk that must be disclosed to all relevant parties including the public authority",
  "proeth:createsObligation": [
    "Disclose_Finding_To_Client",
    "Include_Finding_In_Written_Report",
    "Notify_Public_Authority_Reviewing_Development",
    "Assess_Environmental_Impact_On_Wetlands"
  ],
  "proeth:description": "A biologist on Engineer A\u0027s team identifies a potential threat to a \u0027threatened\u0027 bird species in the adjacent protected wetlands during the property analysis. This discovery transforms a routine development analysis into an environmentally sensitive situation with regulatory and ethical implications.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During property analysis, prior to report submission",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Threatened Species Risk Identified"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Event_Written_Report_Submitted_to_Authority",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer A\u0027s prior verbal disclosure to the client in any way mitigate the ethical violation of omitting the finding from the written report to the public authority \u2014 why or why not?",
    "What responsibilities does a public authority have when it receives a professional engineering report, and how does an incomplete submission undermine the entire regulatory system?",
    "If Engineer A believed the threatened species concern was speculative or inconclusive, would that justify omission from the written report, or would a different approach be required?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A may experience cognitive dissonance or rationalization having already verbally disclosed to the client; the public authority reviewers are unaware of the omission and proceed in good faith; the developer client may feel protected; the biologist whose finding was omitted may be unaware of the omission or feel professionally undermined if aware",
  "proeth-scenario:ethicalImplications": "Exposes the distinction between client-facing disclosure and public-authority disclosure as ethically non-equivalent; reveals how selective transparency can constitute a form of deception even without explicit falsehood; highlights the engineer\u0027s role as a trustworthy information source in public regulatory processes; raises questions about whether client confidentiality can ever legitimately override public disclosure obligations in environmental contexts; connects to NSPE Code Section III.2.d on sustainable development and the broader obligation to hold public safety, health, and welfare paramount",
  "proeth-scenario:learningMoment": "The formal submission of an incomplete report to a public authority is the moment at which a private ethical lapse becomes a public professional violation. Students should understand that written reports to regulatory bodies carry a heightened duty of completeness because third parties \u2014 including the public \u2014 will rely on them. The distinction between verbal and written disclosure is not merely procedural; it is substantively ethical.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "developer_client": "Short-term protection from disclosure may be perceived, but long-term legal and reputational exposure increases if development proceeds and environmental harm results",
    "engineer_a": "Professional liability crystallizes at the moment of submission; the omission is now a documented, actionable ethics violation subject to NSPE Board of Ethical Review scrutiny and potential licensure consequences",
    "engineering_profession": "Public trust in engineers as honest stewards of public welfare is undermined",
    "general_public": "Public interest in environmental protection and honest regulatory processes is directly harmed by the incomplete submission",
    "public_authority": "Regulatory decision-making is compromised by reliance on an incomplete report; the authority cannot fulfill its public protection mandate without the omitted information",
    "threatened_bird_species_and_wetlands": "Protection mechanisms that would have been triggered by proper disclosure are bypassed; ecological harm risk increases"
  },
  "proeth:activatesConstraint": [
    "Public_Record_Integrity_Constraint",
    "Regulatory_Reliance_Constraint",
    "Honest_And_Complete_Reporting_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/83#Action_Omit_Finding_from_Written_Report",
  "proeth:causesStateChange": "An incomplete official record now exists before the public authority; the regulatory review process proceeds on a materially deficient information base; Engineer A\u0027s omission is now formalized and actionable as a professional ethics violation",
  "proeth:createsObligation": [
    "Correct_Or_Supplement_Submitted_Report",
    "Notify_Public_Authority_Of_Omitted_Finding",
    "Remediate_Incomplete_Disclosure"
  ],
  "proeth:description": "Engineer A\u0027s written report on the property analysis is formally submitted to the public authority reviewing the development proposal, without inclusion of the threatened species finding. This submission constitutes an official record that the public authority will rely upon in its regulatory decision-making.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After verbal disclosure to client; at conclusion of analysis engagement",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Written Report Submitted to Authority"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#Event_Public_Authority_Review_Initiated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what point does Engineer A\u0027s ongoing silence about the omission transition from a single ethical lapse to a continuing violation?",
    "What mechanisms exist \u2014 or should exist \u2014 to allow engineers to correct submitted reports after a regulatory review has begun?",
    "How does the systemic reliance on professional engineering reports by public authorities change the ethical weight of what engineers choose to include or omit?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Public authority reviewers proceed in good faith, unaware of the omission; Engineer A may experience escalating anxiety as the review proceeds; the developer may feel momentum toward approval; environmental advocates and the public remain unaware of the risk",
  "proeth-scenario:ethicalImplications": "Demonstrates the systemic dimension of engineering ethics \u2014 individual decisions ripple through institutional processes; reveals the engineer\u0027s role as a gatekeeper of technically complex information that regulators depend upon; raises questions about continuing duties after a report is submitted; highlights how omission can be as harmful as commission in professional practice",
  "proeth-scenario:learningMoment": "This event illustrates how an engineer\u0027s omission creates cascading systemic effects beyond the immediate client relationship. Once a regulatory process is set in motion on incomplete information, the harm compounds over time. Engineers should understand that their reports are not merely deliverables to clients \u2014 they are inputs to public decision-making systems with real-world consequences.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "developer_client": "Regulatory approval becomes more likely in the short term, increasing investment in a potentially non-viable project",
    "engineer_a": "Each day the review proceeds without correction increases Engineer A\u0027s culpability and the difficulty of remediation",
    "general_public": "Public interest is being adjudicated without full information",
    "public_authority": "Unknowingly proceeding toward a potentially flawed regulatory decision; institutional credibility at risk if omission later discovered",
    "threatened_bird_species_and_wetlands": "Regulatory protection mechanisms are not being applied; ecological risk window is open"
  },
  "proeth:activatesConstraint": [
    "Regulatory_Process_Integrity_Constraint",
    "Public_Interest_Protection_Constraint",
    "Timely_Correction_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/83#Action_Omit_Finding_from_Written_Report",
  "proeth:causesStateChange": "Regulatory machinery is now in motion based on incomplete information; the window for correction narrows as the review progresses; potential for irreversible environmental harm increases with each step toward approval",
  "proeth:createsObligation": [
    "Supplement_Report_Before_Authority_Decision",
    "Prevent_Regulatory_Decision_Based_On_Incomplete_Information"
  ],
  "proeth:description": "The public authority begins its formal review of the development proposal based on the submitted materials, including Engineer A\u0027s incomplete written report. The regulatory process is now underway on a materially deficient information base.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Following submission of Engineer A\u0027s written report",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Public Authority Review Initiated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#CausalChain_aac92c0f",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A, as principal of an environmental engineering firm, accepted a client request to prepare [the analysis], which necessitated assembling a team including a biologist whose work led to the identification of the threatened species risk",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A agrees to conduct environmental analysis for the developer client",
      "proeth:element": "Accept Development Analysis Engagement",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A assembles a multidisciplinary team, including a biologist, to conduct the analysis",
      "proeth:element": "Team Assembly Including Biologist",
      "proeth:step": 2
    },
    {
      "proeth:description": "Biologist performs professional evaluation of the project site\u0027s ecological conditions",
      "proeth:element": "Biologist Conducts Field Assessment",
      "proeth:step": 3
    },
    {
      "proeth:description": "Biologist formally identifies that the condominium project could threaten a protected bird species",
      "proeth:element": "Threatened Species Risk Identified",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A receives and must decide how to handle the biologist\u0027s finding within the broader report",
      "proeth:element": "Integrate Biologist\u0027s Threatened Species Finding",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accept Development Analysis Engagement",
  "proeth:counterfactual": "Without accepting the engagement, no team would have been assembled and the threatened species risk would not have been formally identified in this context; however, the ecological risk itself existed independently of the engagement",
  "proeth:effect": "Threatened Species Risk Identified",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s decision to accept the engagement",
    "Assembly of a multidisciplinary team including a biologist",
    "Biologist\u0027s professional obligation to identify environmental risks",
    "Presence of threatened bird species on or near the project site"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:sufficientFactors": [
    "Acceptance of engagement + deployment of qualified biologist + existence of threatened species on site"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#CausalChain_63548582",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon receiving the biologist\u0027s report that the condominium project could threaten a \u0027threatened\u0027 bird species, Engineer A chose to verbally mention the biological concern in subsequent discussions with the developer client",
  "proeth:causalSequence": [
    {
      "proeth:description": "Biologist delivers finding of threatened species risk to Engineer A",
      "proeth:element": "Threatened Species Risk Identified",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A processes and acknowledges the finding internally",
      "proeth:element": "Integrate Biologist\u0027s Threatened Species Finding",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A considers how and whether to communicate the finding to client and authorities",
      "proeth:element": "Engineer A Evaluates Disclosure Options",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A chooses verbal-only communication of the finding to the developer client",
      "proeth:element": "Verbally Disclose Concern to Client",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A simultaneously decides not to include the finding in the formal written report",
      "proeth:element": "Omit Finding from Written Report",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Integrate Biologist\u0027s Threatened Species Finding",
  "proeth:counterfactual": "Without integrating the biologist\u0027s finding, Engineer A would have had no basis for even the partial verbal disclosure that occurred; the verbal disclosure was a direct downstream consequence of receiving the finding",
  "proeth:effect": "Verbally Disclose Concern to Client",
  "proeth:necessaryFactors": [
    "Receipt and integration of the biologist\u0027s finding by Engineer A",
    "Engineer A\u0027s awareness of the finding\u0027s significance",
    "Ongoing communication channel between Engineer A and the developer client",
    "Engineer A\u0027s partial recognition of a disclosure obligation"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:sufficientFactors": [
    "Awareness of finding + client communication opportunity + partial sense of professional obligation = verbal disclosure"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#CausalChain_1da8dc00",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A made the deliberate decision not to include the biologist\u0027s threatened species concern in [the written report], which was then formally submitted to the public authority, creating an incomplete evidentiary record for regulatory review",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A receives and processes the biologist\u0027s material finding",
      "proeth:element": "Integrate Biologist\u0027s Threatened Species Finding",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A deliberately excludes the threatened species concern from the formal written report",
      "proeth:element": "Omit Finding from Written Report",
      "proeth:step": 2
    },
    {
      "proeth:description": "Incomplete written report is formally submitted to the public authority",
      "proeth:element": "Written Report Submitted to Authority",
      "proeth:step": 3
    },
    {
      "proeth:description": "Public authority begins review based solely on the incomplete submitted materials",
      "proeth:element": "Public Authority Review Initiated",
      "proeth:step": 4
    },
    {
      "proeth:description": "NSPE BER concludes Engineer A violated professional ethical obligations through the omission",
      "proeth:element": "BER Ethical Violation Conclusion Reached",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Omit Finding from Written Report",
  "proeth:counterfactual": "Had Engineer A included the biologist\u0027s finding in the written report, the public authority would have received complete information and could have initiated appropriate regulatory scrutiny of the threatened species concern from the outset",
  "proeth:effect": "Written Report Submitted to Authority",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s deliberate decision to exclude the threatened species finding",
    "Completion and submission of the written report to the public authority",
    "Public authority\u0027s reliance on submitted materials as the basis for review",
    "Absence of any other mechanism by which the finding would reach the public authority"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:sufficientFactors": [
    "Deliberate omission + report submission + authority reliance on written record = incomplete regulatory review basis"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#CausalChain_443afaf5",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A\u0027s written report on the property analysis is formally submitted to the public authority, which then begins its formal review of the development proposal based on the submitted materials",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A deliberately excludes material threatened species finding from report",
      "proeth:element": "Omit Finding from Written Report",
      "proeth:step": 1
    },
    {
      "proeth:description": "Incomplete report formally submitted to public authority as the basis for development review",
      "proeth:element": "Written Report Submitted to Authority",
      "proeth:step": 2
    },
    {
      "proeth:description": "Authority begins formal review relying on the incomplete report as its primary information source",
      "proeth:element": "Public Authority Review Initiated",
      "proeth:step": 3
    },
    {
      "proeth:description": "Regulatory and ethical context crystallizes around Engineer A\u0027s conduct",
      "proeth:element": "NSPE Code Section III.2.d Enacted",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER determines Engineer A\u0027s omission constituted a violation of professional ethics",
      "proeth:element": "BER Ethical Violation Conclusion Reached",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Written Report Submitted to Authority",
  "proeth:counterfactual": "Without the submission of the written report, the public authority review would not have been initiated in this form; the review was directly triggered by and dependent upon the submitted report",
  "proeth:effect": "Public Authority Review Initiated",
  "proeth:necessaryFactors": [
    "Formal submission of the written report to the public authority",
    "Public authority\u0027s jurisdiction over the development proposal",
    "Regulatory framework requiring authority review of such development proposals",
    "Report\u0027s status as the primary evidentiary basis for the review"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:sufficientFactors": [
    "Formal report submission + regulatory jurisdiction + standard review procedures = initiation of public authority review"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/83#",
    "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/83#CausalChain_c60af035",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A made the deliberate decision not to include the biologist\u0027s threatened species concern in [the written report], which the NSPE Board of Ethical Review concluded, after analyzing the facts against the Code of Ethics, constituted an ethical violation",
  "proeth:causalSequence": [
    {
      "proeth:description": "Biologist identifies material threatened species risk, creating Engineer A\u0027s knowledge and disclosure obligation",
      "proeth:element": "Threatened Species Risk Identified",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A deliberately excludes the finding, choosing verbal-only client disclosure instead",
      "proeth:element": "Omit Finding from Written Report",
      "proeth:step": 2
    },
    {
      "proeth:description": "Incomplete report submitted, depriving public authority of material environmental information",
      "proeth:element": "Written Report Submitted to Authority",
      "proeth:step": 3
    },
    {
      "proeth:description": "Ethical framework formally codifies the obligation Engineer A violated, providing BER with clear evaluative standard",
      "proeth:element": "NSPE Code Section III.2.d Enacted",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER concludes Engineer A\u0027s deliberate omission violated professional ethical obligations to public welfare and honest communication with public authorities",
      "proeth:element": "BER Ethical Violation Conclusion Reached",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Omit Finding from Written Report",
  "proeth:counterfactual": "Had Engineer A included the threatened species finding in the written report, the BER would have had no basis to conclude an ethical violation occurred; the verbal disclosure alone was insufficient to satisfy the written disclosure obligation to the public authority",
  "proeth:effect": "BER Ethical Violation Conclusion Reached",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s deliberate omission of the threatened species finding from the written report",
    "The existence and applicability of NSPE Code Section III.2.d requiring disclosure of environmental risks",
    "The BER\u0027s jurisdiction and mandate to evaluate Engineer A\u0027s conduct",
    "The public authority\u0027s reliance on the written report for regulatory decision-making",
    "Engineer A\u0027s full knowledge of the finding\u0027s significance at the time of omission"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A (Principal, Environmental Engineering Firm)",
  "proeth:sufficientFactors": [
    "Deliberate omission of material environmental finding + applicable ethical code provision + BER review = ethical violation conclusion",
    "The verbal-only disclosure to client, without written disclosure to the public authority, was insufficient to satisfy professional obligations under the Code"
  ],
  "proeth:withinAgentControl": true
}