{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Action_J_Departs_BWJ_for_City",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept the City Engineer position but immediately establish a written recusal policy covering all BWJ submissions for a defined cooling-off period.",
    "Decline the City Engineer position to avoid the structural conflict entirely.",
    "Accept the position and proactively notify City C leadership in writing of the prior BWJ relationship and request formal guidance on handling future BWJ submissions."
  ],
  "proeth-scenario:characterMotivation": "J sought career advancement, greater civic responsibility, or job stability by transitioning from private practice to a municipal engineering role, likely without anticipating the specific conflict this would create with his former firm\u0027s future work.",
  "proeth-scenario:consequencesIfAlternative": [
    "A formal recusal policy established at onboarding would have created a documented governance structure, ensuring any BWJ submissions were routed to an independent reviewer from the outset \u2014 likely preventing the conflict-of-interest allegations entirely.",
    "Declining the position eliminates the conflict but sacrifices J\u0027s career opportunity; this is an overly conservative choice and illustrates why proactive disclosure, rather than avoidance, is the preferred professional standard.",
    "Proactive written notification to City C leadership would have demonstrated ethical awareness, created an administrative record, and allowed the city to formally assign BWJ-related reviews to another qualified reviewer \u2014 protecting both J and the city."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how structural conflicts of interest are often created at career transition moments, not at the moment of a specific decision \u2014 and that engineers must proactively establish recusal policies and disclosure protocols when joining public agencies, not wait until a conflict materializes.",
  "proeth-scenario:ethicalTension": "Personal career advancement vs. the foreseeable professional complications of moving from a private firm to a regulatory/approval role over that same firm\u0027s future submissions; loyalty to former colleagues vs. duty to the public as a municipal official.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Future public trust in municipal review processes; J\u0027s professional integrity; the integrity of any approvals granted to former employer BWJ; potential liability for City C if approvals are later challenged.",
  "proeth:description": "City Engineer J voluntarily left private firm BWJ to accept the municipal City Engineer position with City C, creating a structural conflict-of-interest scenario for any future BWJ work submitted to City C for review.",
  "proeth:foreseenUnintendedEffects": [
    "Future conflict of interest if BWJ submits plans to City C for review",
    "Ambiguity about adequacy of cooling-off period to neutralize conflict"
  ],
  "proeth:fulfillsObligation": [
    "Lawful career transition",
    "No specific NSPE canon prohibits changing employers per se"
  ],
  "proeth:guidedByPrinciple": [
    "Public welfare primacy (NSPE Code I.1)",
    "Avoidance of conflict of interest (NSPE Code III.2)",
    "Impartiality in public-sector role"
  ],
  "proeth:hasAgent": "Engineer J (former BWJ Principal, subsequently City Engineer of City C)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Career advancement vs. future conflict-of-interest avoidance",
    "proeth:resolutionReasoning": "Engineer J proceeded with the transition; no documented recusal protocol or disclosure mechanism was established at the time of the transition to govern future BWJ submissions"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Career advancement or public-sector transition; acceptance of municipal engineering role",
  "proeth:requiresCapability": [
    "Awareness of conflict-of-interest provisions in NSPE Code",
    "Ability to establish prospective recusal procedures",
    "Municipal engineering administrative competence"
  ],
  "proeth:temporalMarker": "At least one year before subdivision project commenced",
  "proeth:violatesObligation": [
    "Prospective duty to avoid situations creating conflicts of interest (NSPE Code III.2 \u2014 Engineers shall not accept outside employment to the detriment of their regular work or that may impair their judgment)",
    "Duty to proactively plan for recusal from matters involving former employer (NSPE Code III.2.a \u2014 Engineers shall not be influenced by conflicting outside interests)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "J Departs BWJ for City"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Action_Developer_Retains_Firm_BWJ",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Retain a different engineering firm with no prior relationship to City Engineer J to eliminate any appearance of impropriety.",
    "Retain BWJ but proactively disclose the J-BWJ relationship to City C in writing and request that an independent reviewer be assigned to the project.",
    "Retain BWJ and proceed without disclosure, relying on J to manage any conflict on his end."
  ],
  "proeth-scenario:characterMotivation": "Developer G selected Firm BWJ based on prior working relationship, perceived competence, competitive pricing, or familiarity with local requirements \u2014 likely without full appreciation of the conflict-of-interest implications of BWJ\u0027s former principal now serving as the reviewing City Engineer, or potentially with awareness of that relationship and an expectation it would smooth the approval process.",
  "proeth-scenario:consequencesIfAlternative": [
    "Selecting an unrelated firm removes the conflict entirely, protecting the developer from later allegations that the approval process was compromised \u2014 at the cost of potentially losing a preferred engineering relationship.",
    "Proactive disclosure by the developer, combined with a request for independent review, would have demonstrated good faith and likely insulated both the developer and BWJ from conflict-of-interest allegations, while still allowing BWJ to perform the design work.",
    "Proceeding without disclosure \u2014 the path taken \u2014 places the entire burden of conflict management on J, creates significant reputational and legal risk for all parties if problems emerge post-construction, and ultimately contributes to the cascade of failures that led to the flooding complaints and third-party review."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that conflicts of interest involve multiple parties \u2014 not just the public official \u2014 and that developers and private firms also bear responsibility for recognizing and avoiding arrangements that undermine the integrity of public review processes, even when no explicit wrongdoing is intended.",
  "proeth-scenario:ethicalTension": "Legitimate business interest in selecting a qualified, familiar engineering firm vs. the risk of exploiting or appearing to exploit a personal/professional connection to the reviewing authority; cost and schedule efficiency vs. process integrity.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Integrity of the municipal approval process; Developer G\u0027s project approvals and legal exposure if the conflict is later scrutinized; BWJ\u0027s professional reputation; public confidence that development approvals are merit-based.",
  "proeth:description": "Developer G made a deliberate business decision to retain Firm BWJ, under Principal Engineer R, to design the subdivision in City C, selecting a firm whose former principal now served as the reviewing City Engineer.",
  "proeth:foreseenUnintendedEffects": [
    "Potential appearance of impropriety given Engineer J\u0027s prior BWJ affiliation",
    "Possible conflict-of-interest scrutiny during plan review"
  ],
  "proeth:fulfillsObligation": [
    "Contractual right to select engineering firm of choice",
    "Obligation to retain licensed engineer for design work"
  ],
  "proeth:guidedByPrinciple": [
    "Fair dealing with public regulatory bodies",
    "Avoidance of arrangements that undermine impartial review"
  ],
  "proeth:hasAgent": "Developer G (private developer/client)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Preferred firm selection vs. integrity of public review process",
    "proeth:resolutionReasoning": "Developer retained BWJ without documented disclosure or conflict mitigation; the relationship between BWJ and City Engineer J was not formally addressed prior to plan submission"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure qualified engineering firm to produce approvable subdivision design for City C",
  "proeth:requiresCapability": [
    "Due diligence on potential conflicts of interest in regulatory relationships",
    "Contractor/engineer selection judgment"
  ],
  "proeth:temporalMarker": "Pre-construction, project initiation phase",
  "proeth:violatesObligation": [
    "Implicit duty not to exploit or encourage conflict-of-interest relationships in regulatory review processes"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Developer Retains Firm BWJ"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Action_R_Designs_Stormwater_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct a rigorous independent internal QA/QC review of the stormwater calculations before submission, including sensitivity analysis on key parameters.",
    "Design stormwater infrastructure with a conservative safety margin beyond the minimum compliance threshold to account for modeling uncertainty.",
    "If uncertain about compliance, disclose the uncertainty to BWJ leadership and request peer review before finalizing and submitting the plans."
  ],
  "proeth-scenario:characterMotivation": "R was professionally obligated to produce a compliant stormwater design meeting City C\u0027s 25-year peak flow standard, motivated by client service, firm reputation, project schedule, and fee constraints. R may have made good-faith technical errors, applied incorrect hydrological parameters, or faced pressure to minimize required stormwater infrastructure to reduce project costs.",
  "proeth-scenario:consequencesIfAlternative": [
    "An internal QA/QC review would likely have caught the calculation error before submission, preventing the non-compliant design from ever reaching the approval stage \u2014 the most direct intervention point to prevent the entire downstream harm.",
    "A conservative design approach would have reduced the risk that minor calculation errors or modeling assumptions would result in actual non-compliance, providing a buffer that protects both the public and the engineer.",
    "Requesting peer review before submission demonstrates professional humility and due diligence; it may have identified the error internally and allowed correction without public exposure, protecting BWJ\u0027s reputation and the public."
  ],
  "proeth-scenario:decisionSignificance": "Highlights that technical competence and ethical responsibility are inseparable \u2014 an engineer\u0027s primary obligation is to public safety, not client convenience. It also illustrates the importance of independent internal QA/QC review of stormwater calculations before submission, particularly for designs affecting adjacent property owners.",
  "proeth-scenario:ethicalTension": "Client cost and schedule pressures vs. rigorous technical accuracy and public safety; confidence in one\u0027s own calculations vs. the professional duty to independently verify results, especially for designs with significant downstream impact on neighboring properties.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Downstream property owners\u0027 safety and property from flooding; BWJ\u0027s professional liability and licensure; Developer G\u0027s project viability; public infrastructure integrity; City C\u0027s legal exposure for approving a non-compliant design.",
  "proeth:description": "Principal Engineer R made specific technical design decisions to produce stormwater management calculations and plans intended to demonstrate compliance with City C\u0027s requirement that post-development 25-year peak flows not exceed pre-development levels.",
  "proeth:foreseenUnintendedEffects": [
    "Downstream flooding if calculations were erroneous",
    "Liability exposure for BWJ and Engineer R if design failed post-construction"
  ],
  "proeth:fulfillsObligation": [
    "Formal production of stormwater calculations and plans as required by City C",
    "Submission of sealed engineering documents"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety and welfare primacy (NSPE Code I.1)",
    "Technical accuracy and professional competence (NSPE Code II.2)",
    "Honest representation of compliance with regulatory standards"
  ],
  "proeth:hasAgent": "Engineer R (Principal Engineer, Firm BWJ)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Project delivery efficiency vs. technical rigor and public safety compliance",
    "proeth:resolutionReasoning": "Plans were sealed and submitted as compliant; IBM\u0027s post-construction analysis revealed substantial non-compliance, indicating that technical rigor was insufficient relative to the public safety obligation"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Produce a compliant stormwater design satisfying City C\u0027s peak flow requirements and enabling subdivision approval",
  "proeth:requiresCapability": [
    "Stormwater hydrology and hydraulic modeling",
    "Correct application of 25-year storm event methodology",
    "Pre- and post-development runoff computation",
    "Familiarity with City C stormwater ordinance requirements"
  ],
  "proeth:temporalMarker": "Pre-construction, design phase",
  "proeth:violatesObligation": [
    "NSPE Code II.2 \u2014 Engineers shall perform services only in areas of their competence (if hydrologic methodology was misapplied)",
    "NSPE Code III.1.a \u2014 Engineers shall promptly acknowledge and correct errors (anticipatory obligation; failure materialized post-construction)",
    "NSPE Code III.8 \u2014 Engineers shall accept responsibility for their professional activities",
    "Duty to produce technically accurate work product protective of public safety (NSPE Code I.1)"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "R Designs Stormwater Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Action_J_Reviews_and_Approves_BWJ_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Formally recuse himself from all BWJ submissions and document the recusal in writing, referring the plans to a qualified independent reviewer within or outside City C.",
    "Disclose the prior BWJ employment relationship in writing to City C leadership and the developer, and request formal written authorization or direction before proceeding with any review.",
    "Conduct the review but document the prior relationship in the approval record and apply heightened scrutiny \u2014 including independent verification of the stormwater calculations \u2014 to demonstrate objectivity."
  ],
  "proeth-scenario:characterMotivation": "J may have believed his review was objective and that his prior BWJ relationship was sufficiently distant in time to be immaterial; he may have wanted to avoid the awkwardness of recusing himself from a former colleague\u0027s work; he may have lacked formal city policies requiring recusal; or he may have been motivated by a desire to be collegial or efficient, underestimating the appearance of impropriety.",
  "proeth-scenario:consequencesIfAlternative": [
    "Formal recusal with documented referral to an independent reviewer is the cleanest ethical and legal resolution: it eliminates the conflict, protects J\u0027s integrity, and ensures the review is conducted by someone without a prior relationship \u2014 likely resulting in the calculation error being caught before approval.",
    "Written disclosure and request for authorization demonstrates ethical awareness and creates an administrative record; depending on city policy, leadership might have directed recusal or authorized review with conditions \u2014 either outcome is more defensible than undisclosed self-review.",
    "Documented disclosure with heightened scrutiny is a partial measure that acknowledges the conflict but does not fully resolve it; it may have caught the technical error but would still leave J vulnerable to conflict-of-interest allegations because the structural appearance of bias remains."
  ],
  "proeth-scenario:decisionSignificance": "The central ethical failure of the case. Illustrates the principle that conflicts of interest must be managed based on appearance and structural integrity, not solely on the reviewing engineer\u0027s subjective belief in their own objectivity. Recusal, disclosure, and referral to independent reviewers are not optional courtesies \u2014 they are professional and often legal obligations when a material prior relationship exists.",
  "proeth-scenario:ethicalTension": "Duty of impartiality and public trust as a municipal official vs. collegial loyalty to former employer and colleagues; efficiency of completing the review vs. integrity of the process; self-assessment that the review was objective vs. the public\u0027s reasonable perception of bias.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Public trust in municipal government; J\u0027s professional license and career; City C\u0027s legal liability for approving a non-compliant design; the safety of downstream property owners; the legitimacy of the entire subdivision approval; BWJ\u0027s professional reputation.",
  "proeth:description": "City Engineer J decided to conduct the administrative plan review and formally approve the subdivision stormwater plans submitted by his former employer Firm BWJ, without documented recusal, disclosure of the prior employment relationship, or referral to an independent reviewer.",
  "proeth:foreseenUnintendedEffects": [
    "Appearance of conflict of interest due to prior BWJ affiliation",
    "Risk that prior professional relationship could unconsciously bias technical review",
    "Public trust damage if flooding occurred and conflict was later scrutinized",
    "Potential failure to detect design errors due to compromised impartiality"
  ],
  "proeth:fulfillsObligation": [
    "Formal administrative completion of plan review function",
    "Nominal compliance with municipal approval process timeline"
  ],
  "proeth:guidedByPrinciple": [
    "Conflict-of-interest avoidance (NSPE Code III.2)",
    "Public trust and impartiality in public-sector role",
    "Transparency and disclosure",
    "Protection of public safety and welfare (NSPE Code I.1)"
  ],
  "proeth:hasAgent": "Engineer J (City Engineer, City C; former principal of Firm BWJ)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Administrative efficiency and continuity of municipal duties vs. conflict-of-interest recusal and public impartiality",
    "proeth:resolutionReasoning": "Engineer J proceeded with review, apparently treating elapsed time as sufficient to resolve the conflict; NSPE ethics guidance and the subsequent flooding outcome suggest this resolution was ethically inadequate and that recusal or disclosure was required regardless of elapsed time"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Discharge municipal plan-review duty and authorize subdivision construction to proceed",
  "proeth:requiresCapability": [
    "Stormwater hydrology review competence",
    "Conflict-of-interest identification and recusal judgment",
    "Municipal plan review administrative procedures"
  ],
  "proeth:temporalMarker": "Pre-construction, plan review and approval phase",
  "proeth:violatesObligation": [
    "NSPE Code III.2 \u2014 Engineers shall not be influenced by conflicting interests; shall disclose all known or potential conflicts",
    "NSPE Code III.2.a \u2014 Engineers in public service shall not participate in decisions with respect to services solicited or provided by them or their organizations in private engineering practice",
    "NSPE Code II.4 \u2014 Engineers shall act as faithful agents of their employer (City C) by ensuring impartial review",
    "NSPE Code I.4 \u2014 Engineers shall act in a manner that upholds and enhances the honor, integrity, and dignity of the profession",
    "Duty to disclose prior employment relationship to City C supervisors or governing body",
    "Duty to recuse from review or arrange independent review of BWJ submissions"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "J Reviews and Approves BWJ Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Action_City_Engages_IBM_for_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct an internal review using City C engineering staff rather than an independent third party, accepting the risk of perceived bias.",
    "Immediately admit the conflict-of-interest failure, commission independent review, and proactively offer remediation support to affected property owners before the review is complete.",
    "Defer any review pending litigation, allowing legal proceedings to drive the factual investigation rather than taking proactive administrative action."
  ],
  "proeth-scenario:characterMotivation": "City C was responding to public pressure from flooding complaints and conflict-of-interest allegations, seeking to restore public confidence, establish an objective factual record, determine legal and financial liability, and demonstrate institutional accountability \u2014 while also potentially seeking to shift or confirm responsibility before committing to remediation expenditures.",
  "proeth-scenario:consequencesIfAlternative": [
    "An internal review would be faster and less costly but would likely be viewed as self-serving given J\u0027s role in the original approval, potentially deepening public distrust and failing to provide the credible independent finding needed to resolve disputes.",
    "Proactive admission and remediation support demonstrates strong institutional ethics and may reduce legal liability through good-faith action, but exposes City C to significant financial commitment before the full scope of responsibility is established.",
    "Deferring to litigation is the most defensive posture: it protects City C\u0027s legal position in the short term but prolongs harm to affected property owners, destroys public trust, and ultimately produces a more adversarial and expensive resolution than proactive administrative action."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that institutional ethics requires proactive corrective action when failures are alleged \u2014 not defensive posturing. The decision to engage an independent reviewer is an example of institutional integrity, but it also raises questions about why independent review was not part of the original approval process, and whether the city\u0027s response is driven by genuine accountability or liability management.",
  "proeth-scenario:ethicalTension": "Institutional accountability and transparency vs. the risk that independent review will expose City C\u0027s own approval failures; duty to affected property owners vs. desire to minimize municipal legal exposure; speed of response to public harm vs. thoroughness of investigation.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Definitive determination of design compliance failure; legal liability allocation among City C, BWJ, Developer G, and potentially affected property owners; cost of remediation; public trust in municipal engineering oversight; precedent for how City C handles future conflict-of-interest situations.",
  "proeth:description": "Following post-construction flooding complaints and conflict-of-interest allegations, City C made a deliberate administrative decision to retain independent third-party Firm IBM to conduct a technical review of the subdivision stormwater design.",
  "proeth:foreseenUnintendedEffects": [
    "Findings could expose City C to liability for approving non-compliant plans",
    "Findings could implicate Engineer J\u0027s conduct",
    "Findings could support or undermine property owner complaints"
  ],
  "proeth:fulfillsObligation": [
    "Public duty to investigate citizen complaints about infrastructure performance",
    "Obligation to ensure municipal infrastructure meets adopted standards",
    "NSPE-aligned principle of seeking competent independent review when internal conflict exists",
    "Transparency and accountability to affected property owners"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety and welfare (NSPE Code I.1 by analogy)",
    "Accountability and transparency in public administration",
    "Impartial fact-finding when internal conflict of interest is alleged"
  ],
  "proeth:hasAgent": "City C (municipal government, acting through appropriate officials)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Institutional self-protection vs. transparent independent investigation",
    "proeth:resolutionReasoning": "City C appropriately prioritized transparent independent review over institutional self-protection, consistent with its public-interest obligations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Obtain independent, objective technical analysis of whether the subdivision stormwater design complied with City C\u0027s requirements and whether Engineer J\u0027s approval was compromised",
  "proeth:requiresCapability": [
    "Procurement of qualified independent engineering firm",
    "Definition of review scope covering both technical compliance and conflict-of-interest context",
    "Administrative management of third-party review process"
  ],
  "proeth:temporalMarker": "Post-construction, after flooding complaints were received",
  "proeth:withinCompetence": true,
  "rdfs:label": "City Engages IBM for Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Action_R_Acknowledges_Error_and_Remediates",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Dispute IBM\u0027s findings, commission a competing technical analysis, and resist acknowledgment of error pending further review \u2014 prioritizing legal defensibility over prompt remediation.",
    "Acknowledge the error privately to BWJ leadership and legal counsel but make no public admission, allowing legal proceedings to determine responsibility while quietly working toward a settlement.",
    "Proactively contact affected property owners, acknowledge the design deficiency, engage in transparent communication about the remediation plan, and work collaboratively with City C and IBM to implement corrections \u2014 accepting professional and financial accountability."
  ],
  "proeth-scenario:characterMotivation": "R faces the professional, ethical, and legal obligation to respond to confirmed findings of design non-compliance \u2014 motivated by duties under engineering licensure codes, BWJ\u0027s professional liability exposure, the interests of affected property owners, and R\u0027s own professional integrity. R may also be motivated by self-preservation, seeking to demonstrate good faith before regulatory or legal consequences escalate.",
  "proeth-scenario:consequencesIfAlternative": [
    "Disputing IBM\u0027s findings when IBM\u0027s analysis aligns with objective technical standards prolongs harm to affected property owners, damages R\u0027s and BWJ\u0027s professional credibility, and may result in more severe regulatory and legal consequences \u2014 while being ethically indefensible if the error is genuine.",
    "Private acknowledgment without public transparency may satisfy legal counsel\u0027s short-term risk management goals but violates the spirit of professional engineering ethics, which requires engineers to notify affected parties of known safety-relevant failures; it also risks greater reputational damage if the concealment is later exposed.",
    "Proactive transparent acknowledgment and collaborative remediation is the most ethically consistent response: it aligns with licensure obligations, demonstrates professional integrity, may reduce legal liability through good-faith action, and \u2014 most importantly \u2014 addresses the actual harm to affected property owners in the most direct and timely manner."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the professional engineering obligation to respond to identified failures with honesty, transparency, and corrective action \u2014 not defensiveness or minimization. The NSPE Code of Ethics requires engineers to hold public safety paramount; when a design failure causes harm, acknowledgment and remediation are not optional. Also highlights the importance of engaging risk management and legal counsel early while maintaining ethical obligations independent of legal strategy.",
  "proeth-scenario:ethicalTension": "Professional duty to acknowledge error and protect public safety vs. self-interest in minimizing personal and firm liability; transparency with affected parties vs. legal counsel\u0027s advice to limit admissions; the engineer\u0027s duty to the public vs. loyalty to the client (Developer G) who may resist remediation costs.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "Safety and property rights of affected downstream neighbors; R\u0027s professional license and standing; BWJ\u0027s professional reputation and financial liability; the precedent set for how engineering firms respond to confirmed design failures; the ultimate adequacy of remediation for the affected community.",
  "proeth:description": "Following IBM\u0027s confirmation of substantial stormwater design non-compliance, Principal Engineer R faces the professional obligation to acknowledge the design error, verify IBM\u0027s findings against his own calculations, notify BWJ\u0027s risk management team, and engage in remediation of the stormwater problem.",
  "proeth:foreseenUnintendedEffects": [
    "Acknowledgment increases BWJ\u0027s and R\u0027s professional liability exposure",
    "May trigger professional discipline proceedings",
    "May result in financial cost to BWJ for remediation",
    "Failure to acknowledge perpetuates public safety risk and constitutes ongoing ethical violation"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code III.1.a \u2014 Engineers shall promptly acknowledge errors and omissions and shall make no misrepresentations or omit material facts",
    "NSPE Code III.8 \u2014 Engineers shall accept personal responsibility for all professional activities",
    "BER Case 16-7 and 95-5 \u2014 Obligation to disclose errors and inaccurate data to clients and the public",
    "NSPE Code I.1 \u2014 Protection of public safety and welfare through corrective action"
  ],
  "proeth:guidedByPrinciple": [
    "Professional honesty and integrity (NSPE Code II.3, III.1.a)",
    "Public safety primacy (NSPE Code I.1)",
    "Personal accountability for professional work product (NSPE Code III.8)",
    "Transparency with clients and the public regarding errors (BER 16-7, 95-5)"
  ],
  "proeth:hasAgent": "Engineer R (Principal Engineer, Firm BWJ)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional self-preservation and liability minimization vs. ethical obligation to acknowledge error and protect public safety",
    "proeth:resolutionReasoning": "NSPE Code III.1.a and III.8, reinforced by BER Cases 16-7 and 95-5, establish that acknowledgment of error and engagement with remediation are non-negotiable professional obligations that supersede personal or firm liability considerations; Engineer R must acknowledge the error, engage BWJ\u0027s risk management team, and participate in corrective design"
  },
  "proeth:hasMentalState": "deliberate (obligatory \u2014 action not yet confirmed as taken)",
  "proeth:intendedOutcome": "Fulfill professional ethical obligations by acknowledging the error, cooperating with remediation, and protecting public safety through corrected stormwater design",
  "proeth:requiresCapability": [
    "Independent verification of IBM\u0027s hydrologic analysis against original calculations",
    "Identification of specific calculation errors in pre/post-development runoff modeling",
    "Development of corrective stormwater design options",
    "Communication with BWJ risk management and legal counsel",
    "Transparent reporting to Developer G and City C"
  ],
  "proeth:temporalMarker": "Post-IBM analysis; present obligation and future required action",
  "proeth:violatesObligation": [
    "If acknowledgment is withheld: NSPE Code III.1.a, III.8, and I.1 would all be violated",
    "Withholding findings under litigation pressure would violate NSPE Code II.3 \u2014 Engineers shall not attempt to injure the professional reputation of other engineers"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "R Acknowledges Error and Remediates"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Event_IBM_Confirms_Design_Non-Compliance",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What does the IBM finding reveal about the adequacy of City C\u0027s original plan review process, and what systemic reforms might prevent similar failures?",
    "How does the confirmation of design non-compliance change the ethical obligations of R, J, and City C, compared to before the IBM review?",
    "IBM also found contributing factors (undersized culvert, neighbor\u0027s paving) \u2014 how should engineers and decision-makers weigh shared causation when assigning responsibility for harm?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "R faces the professional and personal devastation of having a peer-reviewed analysis confirm a significant design error; J faces compounded crisis \u2014 the design failure validates the complaint that the approval process was inadequate; City C officials experience institutional alarm; neighboring property owners feel vindicated but remain anxious about remediation; IBM analysts experience professional gravity of delivering a finding with serious consequences",
  "proeth-scenario:ethicalImplications": "Reveals the ethical importance of independent verification in engineering approval processes. Raises questions about whether J\u0027s approval reflected genuine engineering judgment or rubber-stamping influenced (consciously or not) by prior professional relationships. Highlights the tension between institutional loyalty and objective technical standards.",
  "proeth-scenario:learningMoment": "Demonstrates the critical role of independent technical review in accountability systems \u2014 IBM\u0027s analysis removed ambiguity and created an objective basis for remediation and accountability. Students should understand that independent review is not merely procedural but is a substantive safeguard for public protection.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "city_c": "Regulatory process shown to have failed; must now enforce remediation and address internal ethics question",
    "city_engineer_j": "Approval of a now-confirmed non-compliant design deepens conflict-of-interest scrutiny \u2014 the question shifts from \u0027did J show bias?\u0027 to \u0027how did J miss this?\u0027",
    "developer_g": "Confirmed design failure creates direct legal exposure for damages and remediation costs",
    "engineer_r": "Professional competence formally questioned by independent analysis; exposure to licensing board review, civil liability, and reputational damage; obligation to remediate now unambiguous",
    "firm_bwj": "Institutional liability crystallized; professional reputation damaged; potential civil and regulatory exposure",
    "neighboring_property_owners": "Validation of claims; pathway to remediation and potential compensation opened"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Duty_to_Correct_Documented_Deficiency",
    "Professional_Accountability_Constraint",
    "Mandatory_Remediation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/11#Action_City_Engages_IBM_for_Review",
  "proeth:causesStateChange": "Design failure shifts from alleged to confirmed; all parties now have constructive knowledge of the deficiency; continued inaction becomes affirmative ethical and legal violation; remediation obligation is immediate and non-negotiable",
  "proeth:createsObligation": [
    "R_Must_Acknowledge_and_Correct_Design_Failure",
    "City_C_Must_Require_Remediation",
    "Professional_Licensing_Board_Notification_Consideration",
    "J_Conflict_of_Interest_Allegation_Must_Be_Formally_Addressed",
    "Compensate_or_Remediate_Affected_Neighbors"
  ],
  "proeth:description": "Independent reviewer Firm IBM determined through technical analysis that post-development stormwater runoff flows were substantially larger than pre-development flows for the 25-year, two-hour storm event, directly confirming that Engineer R\u0027s design failed to comply with City C\u0027s stated requirement. This finding transformed the flooding from an alleged harm into a documented engineering failure.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After City C engages IBM; during independent review phase",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "IBM Confirms Design Non-Compliance"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Event_IBM_Identifies_Contributing_Factors",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the discovery that property owners contributed to their own flooding reduce the ethical responsibility of R and J, and if so, by how much?",
    "How should an independent reviewer handle findings that implicate the complaining parties themselves \u2014 is there an obligation to report these findings fully even if it complicates the complainants\u0027 case?",
    "What obligations, if any, do property owners have to ensure their own modifications do not harm neighbors?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Property owners who complained may feel defensive or betrayed upon learning their own actions contributed to harm; R and J may feel some relief that causation is shared; other stakeholders must grapple with a more complex picture of responsibility than initially presented",
  "proeth-scenario:ethicalImplications": "Raises questions about comparative responsibility and the ethics of complete disclosure \u2014 IBM\u0027s obligation to report all findings, even those unfavorable to the complaining parties, reflects the engineer\u0027s duty to objective truth over advocacy. Also surfaces questions about individual property rights versus community drainage obligations.",
  "proeth-scenario:learningMoment": "Illustrates that real-world engineering failures rarely have single causes \u2014 contributing factors from multiple parties are common. Students should learn to conduct thorough causal analysis before assigning responsibility, and to understand that shared causation does not eliminate primary professional obligations.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "city_c": "Must address not only the subdivision design failure but also whether property owners\u0027 independent modifications required permits and whether those were properly reviewed",
    "complaining_property_owners": "Their own actions are now part of the causal record \u2014 the property owner with the undersized culvert and the one who added paving face scrutiny of their own choices; moral standing in the dispute becomes more complex",
    "developer_g": "Potentially reduced exposure if shared causation is legally recognized",
    "engineer_r": "Shared causation does not eliminate the primary design failure but may reduce proportional liability; still obligated to remediate the core deficiency",
    "neighboring_property_owners_broadly": "Reminder that property modifications can have downstream consequences and may carry regulatory obligations"
  },
  "proeth:activatesConstraint": [
    "Accurate_Causation_Determination_Constraint",
    "Proportional_Liability_Assessment_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/11#Action_City_Engages_IBM_for_Review",
  "proeth:causesStateChange": "Causation picture becomes multi-factorial; responsibility for flooding distributed across subdivision design failure, municipal approval failure, and independent actions of affected property owners themselves; remediation and liability analysis must account for proportional contribution",
  "proeth:createsObligation": [
    "Address_Undersized_Culvert_as_Separate_Remediation_Item",
    "Notify_Property_Owner_of_Their_Contributing_Construction",
    "Incorporate_Shared_Causation_into_Remediation_and_Liability_Analysis"
  ],
  "proeth:description": "In addition to confirming the primary design deficiency, IBM\u0027s review found that one complaining property owner had an undersized driveway culvert and that another property owner had constructed paved areas and an outbuilding that independently exacerbated flooding on their own and neighboring properties. These findings introduced shared causation into the harm analysis.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Concurrent with IBM design non-compliance finding; during independent review phase",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "IBM Identifies Contributing Factors"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Event_Subdivision_Construction_Completed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what stage in the design-approval-construction sequence was intervention most feasible and least costly?",
    "Does the physical completion of a non-compliant project change the ethical obligations of the engineers involved?",
    "Who bears responsibility for post-construction monitoring, and what systems should exist to catch compliance failures before harm occurs?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Developer G experiences satisfaction at project completion; neighbors remain unaware of impending risk; R and J have no immediate signal that anything is wrong; a false sense of successful closure pervades all parties",
  "proeth-scenario:ethicalImplications": "Reveals the compounding nature of professional failures \u2014 a design error combined with an inadequate review becomes irreversible harm once construction is complete. Raises questions about the duty to verify, not merely approve, and whether administrative sign-off constitutes genuine engineering judgment.",
  "proeth-scenario:learningMoment": "Illustrates how the completion of construction marks a point of no easy return \u2014 design errors become embedded in physical reality, escalating the cost and complexity of correction. Students should recognize that approval and construction do not equal compliance.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "city_c": "Municipal infrastructure and approval process implicitly endorsed a non-compliant design",
    "city_engineer_j": "Approval decision is now irrevocable without formal remediation process; conflict-of-interest exposure locked in",
    "developer_g": "Financial investment realized but latent liability created",
    "engineer_r": "Professional exposure crystallized \u2014 the design flaw is now physically embedded in the landscape",
    "neighboring_property_owners": "Unknowingly now subject to increased flood risk with each storm event"
  },
  "proeth:activatesConstraint": [
    "Post_Construction_Monitoring",
    "As_Built_Compliance_Verification"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/11#Action_J_Reviews_and_Approves_BWJ_Plans",
  "proeth:causesStateChange": "Project transitions from design/approval phase to operational phase; hydrological impacts of increased impervious surface now physically realized and irreversible without remediation",
  "proeth:createsObligation": [
    "Monitor_Stormwater_Performance",
    "Verify_As_Built_Conditions_Match_Approved_Plans"
  ],
  "proeth:description": "The subdivision designed by Firm BWJ was fully constructed, including extensive paved areas that materially increased impervious surface coverage across the development site. This physical transformation of the land locked in the hydrological conditions that would drive downstream flooding.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After plan approval; before flooding complaints",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Subdivision Construction Completed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Event_Neighboring_Properties_Flood",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How does the identity of the harmed parties (uninvolved neighbors) affect the ethical weight of the design and approval failures?",
    "At what point did the engineers involved have an obligation to proactively disclose the risk, even before flooding occurred?",
    "How should the presence of contributing factors (undersized culvert, neighbor\u0027s own paving) affect the moral and legal responsibility of R and J?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Neighboring property owners experience fear, frustration, and financial distress from flood damage; anger mounts as they suspect the approval process was compromised; Developer G faces anxiety over liability; R confronts the concrete human consequences of the design error; J faces professional and personal crisis as the conflict-of-interest allegation surfaces",
  "proeth-scenario:ethicalImplications": "Exposes the core tension between professional self-interest (avoiding disclosure of error) and the paramount duty to public safety. Raises questions about the ethics of silence when a professional suspects or knows of a deficiency that could harm others. Also surfaces the structural vulnerability created when a former colleague reviews another\u0027s work without recusal.",
  "proeth-scenario:learningMoment": "Demonstrates that engineering decisions have real human consequences \u2014 the flooding is the moment when abstract technical non-compliance becomes tangible harm. Students must understand that compliance requirements exist to protect real people, and that approval processes are not merely bureaucratic formalities.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "city_c": "Municipal credibility and regulatory effectiveness called into question; obligation to respond publicly and transparently",
    "city_engineer_j": "Prior relationship with BWJ now publicly scrutinized; approval decision questioned; personal and professional integrity challenged",
    "developer_g": "Completed project now subject to legal claims; financial exposure for remediation and damages",
    "engineer_r": "Professional negligence now has a human face \u2014 real people harmed by the design failure; exposure to disciplinary action, civil liability, and reputational damage",
    "firm_bwj": "Institutional reputation at risk; potential civil liability",
    "neighboring_property_owners": "Direct property damage, financial loss, emotional distress, and disruption of daily life; forced into adversarial posture with City C and Firm BWJ"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Harm_Mitigation_Obligation",
    "Duty_to_Disclose_Known_Deficiency"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/11#Action_R_Designs_Stormwater_Plans",
  "proeth:causesStateChange": "Latent design deficiency becomes manifest harm; case transitions from administrative/technical matter to active public safety and legal liability situation; affected third parties now have standing to demand accountability",
  "proeth:createsObligation": [
    "Investigate_Cause_of_Flooding",
    "Notify_Affected_Parties_of_Risk",
    "Remediate_Design_Deficiency",
    "Disclose_Potential_Conflict_of_Interest_in_Approval_Process",
    "Engage_Independent_Review"
  ],
  "proeth:description": "Following completion of the subdivision, neighboring properties experienced flooding events attributable to increased stormwater runoff from the newly developed site. This flooding caused property damage and personal harm to residents who had no role in the subdivision\u0027s design or approval.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After subdivision construction completion; triggers complaint phase",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Neighboring Properties Flood"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#Event_Property_Owners_Lodge_Complaints",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does it matter whether J\u0027s prior relationship with BWJ actually influenced the approval decision, or is the appearance of influence sufficient to constitute an ethical violation?",
    "What proactive steps could J have taken at the time of review to prevent this complaint from arising?",
    "How should a municipality structure its review processes to prevent situations where a city engineer reviews work from a former employer?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Property owners feel vindicated in raising concerns but anxious about whether the city will take them seriously; J experiences acute professional anxiety and personal stress as the conflict-of-interest allegation becomes public; City C officials face institutional embarrassment and pressure to act decisively",
  "proeth-scenario:ethicalImplications": "Highlights the distinction between actual and apparent conflicts of interest, and the professional obligation to avoid both. Raises questions about institutional design \u2014 whether individual ethical choices are sufficient, or whether systemic safeguards (recusal rules, disclosure requirements) are necessary to protect public trust.",
  "proeth-scenario:learningMoment": "Illustrates how the appearance of a conflict of interest \u2014 even if actual bias cannot be proven \u2014 erodes public trust and triggers mandatory accountability processes. Students should understand that conflict-of-interest rules exist to protect institutional legitimacy, not just to prevent actual wrongdoing.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "city_c": "Forced to confront both a technical regulatory failure and an internal ethics question simultaneously; credibility of approval process publicly questioned",
    "city_engineer_j": "Prior relationship with BWJ now a matter of public record and formal inquiry; professional standing and possibly employment at risk",
    "developer_g": "Increased legal and financial exposure as complaints create a paper trail",
    "engineer_r_and_firm_bwj": "Now subject to external scrutiny; the complaint formalizes the pathway to independent technical review that will confirm the design failure",
    "neighboring_property_owners": "Transition from passive victims to active participants in accountability process; empowered but uncertain of outcome"
  },
  "proeth:activatesConstraint": [
    "Municipal_Duty_to_Respond_to_Public_Complaints",
    "Conflict_of_Interest_Investigation_Constraint",
    "Transparency_and_Accountability_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/11#Action_J_Reviews_and_Approves_BWJ_Plans",
  "proeth:causesStateChange": "Dispute moves from private harm to public record; City C now has formal notice of both a technical failure allegation and an ethical process allegation; inaction is no longer a viable option for the municipality",
  "proeth:createsObligation": [
    "City_C_Must_Investigate_Flooding_Cause",
    "City_C_Must_Address_Conflict_of_Interest_Allegation",
    "Engage_Independent_Technical_Reviewer",
    "J_Must_Disclose_Prior_Relationship_Formally_If_Not_Already_Done"
  ],
  "proeth:description": "Affected neighboring property owners formally complained to City C about both the flooding damage they sustained and a perceived conflict of interest arising from City Engineer J\u0027s prior association with Firm BWJ. This dual complaint \u2014 technical and ethical \u2014 forced the city into an investigative posture.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After flooding events; triggers independent review engagement",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Property Owners Lodge Complaints"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#CausalChain_5d58838a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "City Engineer J decided to conduct the administrative plan review and formally approve the subdivision plans despite a material conflict of interest arising from his prior employment at Firm BWJ",
  "proeth:causalSequence": [
    {
      "proeth:description": "J transitions from private practice at BWJ to the municipal City Engineer role, establishing the conditions for a future conflict of interest",
      "proeth:element": "J Departs BWJ for City",
      "proeth:step": 1
    },
    {
      "proeth:description": "Developer G retains BWJ under R to design the subdivision, directly creating the conflict-of-interest scenario for J as the reviewing authority",
      "proeth:element": "Developer Retains Firm BWJ",
      "proeth:step": 2
    },
    {
      "proeth:description": "J proceeds with plan review without recusal or disclosure, providing municipal approval to R\u0027s non-compliant stormwater design",
      "proeth:element": "J Reviews and Approves BWJ Plans",
      "proeth:step": 3
    },
    {
      "proeth:description": "Approved plans are constructed, embedding the stormwater deficiency into permanent infrastructure",
      "proeth:element": "Subdivision Construction Completed",
      "proeth:step": 4
    },
    {
      "proeth:description": "The constructed deficiency causes flooding of neighboring properties, resulting in property damage and complaints",
      "proeth:element": "Neighboring Properties Flood",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "J Reviews and Approves BWJ Plans",
  "proeth:counterfactual": "Had J recused himself and an unconflicted engineer conducted a rigorous technical review, the stormwater design deficiencies would likely have been identified and corrected prior to construction, preventing the flooding",
  "proeth:effect": "Neighboring Properties Flood",
  "proeth:necessaryFactors": [
    "J\u0027s decision to personally conduct the review rather than recuse himself",
    "J\u0027s prior professional relationship with R and BWJ creating a conflict of interest",
    "Absence of independent technical scrutiny that recusal would have mandated",
    "The underlying design non-compliance in R\u0027s plans requiring detection"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "City Engineer J",
  "proeth:sufficientFactors": [
    "Conflicted reviewer + non-compliant plans + no compensating independent review = approval of deficient design proceeding to construction"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#CausalChain_6df261c7",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Developer G made a deliberate business decision to retain Firm BWJ, under Principal Engineer R, to design the subdivision, which produced the stormwater management plans subsequently confirmed by IBM to be substantially non-compliant",
  "proeth:causalSequence": [
    {
      "proeth:description": "Developer G contracts BWJ and R to produce subdivision engineering plans, including stormwater management",
      "proeth:element": "Developer Retains Firm BWJ",
      "proeth:step": 1
    },
    {
      "proeth:description": "R produces stormwater calculations with substantial errors, underestimating post-development runoff relative to regulatory requirements",
      "proeth:element": "R Designs Stormwater Plans",
      "proeth:step": 2
    },
    {
      "proeth:description": "Conflicted review by J fails to detect or correct R\u0027s design deficiencies, granting municipal approval",
      "proeth:element": "J Reviews and Approves BWJ Plans",
      "proeth:step": 3
    },
    {
      "proeth:description": "Post-construction flooding and conflict-of-interest allegations prompt formal complaints to City C, triggering independent review",
      "proeth:element": "Property Owners Lodge Complaints",
      "proeth:step": 4
    },
    {
      "proeth:description": "IBM\u0027s independent technical analysis formally attributes the flooding to BWJ\u0027s non-compliant stormwater design, confirming the causal chain",
      "proeth:element": "IBM Confirms Design Non-Compliance",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Developer Retains Firm BWJ",
  "proeth:counterfactual": "Had Developer G retained a different firm, or had BWJ under R produced compliant designs, IBM\u0027s review would not have confirmed design non-compliance as the cause of flooding; however, Developer G\u0027s selection of BWJ is a more distal cause, as the proximate design responsibility rests with R",
  "proeth:effect": "IBM Confirms Design Non-Compliance",
  "proeth:necessaryFactors": [
    "Developer G\u0027s selection of BWJ as the design firm",
    "R\u0027s role as principal engineer responsible for the stormwater calculations",
    "BWJ\u0027s production of non-compliant stormwater management plans",
    "IBM\u0027s independent technical review confirming the non-compliance"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Developer G (firm selection) and Principal Engineer R (design execution) \u2014 shared",
  "proeth:sufficientFactors": [
    "Developer\u0027s firm selection + R\u0027s design errors + absence of pre-construction correction = confirmed non-compliant design"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#CausalChain_29bc8b00",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "IBM determined through technical analysis that post-development stormwater runoff exceeded pre-development levels due to design deficiencies in BWJ\u0027s stormwater management calculations",
  "proeth:causalSequence": [
    {
      "proeth:description": "Principal Engineer R produces stormwater management calculations that are substantially non-compliant with applicable standards, underestimating post-development runoff",
      "proeth:element": "R Designs Stormwater Plans",
      "proeth:step": 1
    },
    {
      "proeth:description": "City Engineer J, in a conflicted position as former BWJ colleague, approves the non-compliant plans without independent technical scrutiny, allowing them to proceed to construction",
      "proeth:element": "J Reviews and Approves BWJ Plans",
      "proeth:step": 2
    },
    {
      "proeth:description": "The subdivision is fully constructed per the flawed plans, introducing extensive impervious paved areas that materially increase stormwater runoff volumes",
      "proeth:element": "Subdivision Construction Completed",
      "proeth:step": 3
    },
    {
      "proeth:description": "Elevated post-development runoff, unmitigated by the deficient stormwater system, inundates neighboring properties causing property damage",
      "proeth:element": "Neighboring Properties Flood",
      "proeth:step": 4
    },
    {
      "proeth:description": "Independent review formally confirms that R\u0027s design deficiencies were the primary technical cause of the excess runoff and resulting flood damage",
      "proeth:element": "IBM Confirms Design Non-Compliance",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "R Designs Stormwater Plans",
  "proeth:counterfactual": "Had R produced compliant stormwater calculations meeting regulatory standards, post-development runoff would not have exceeded pre-development levels and neighboring flooding would likely not have occurred",
  "proeth:effect": "Neighboring Properties Flood",
  "proeth:necessaryFactors": [
    "R\u0027s specific technical design decisions producing non-compliant stormwater calculations",
    "Subdivision construction materializing the flawed design into physical infrastructure",
    "Increased impervious surface area from paved areas altering natural drainage patterns"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Principal Engineer R (Firm BWJ)",
  "proeth:sufficientFactors": [
    "Non-compliant stormwater design + completed construction of impervious surfaces + absence of corrective review prior to construction"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#CausalChain_1c535db1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Affected neighboring property owners formally complained to City C about both the flooding damage and the conflict-of-interest allegations, following which City C made a deliberate decision to engage independent firm IBM to conduct a technical review",
  "proeth:causalSequence": [
    {
      "proeth:description": "Post-construction flooding causes property damage to neighboring landowners, creating the factual basis for complaints",
      "proeth:element": "Neighboring Properties Flood",
      "proeth:step": 1
    },
    {
      "proeth:description": "Affected property owners formally submit complaints to City C alleging both flood damage causation and conflict-of-interest in the plan approval process",
      "proeth:element": "Property Owners Lodge Complaints",
      "proeth:step": 2
    },
    {
      "proeth:description": "City C responds to complaints by commissioning independent firm IBM to conduct an objective technical and procedural review",
      "proeth:element": "City Engages IBM for Review",
      "proeth:step": 3
    },
    {
      "proeth:description": "IBM\u0027s analysis confirms stormwater design deficiencies as the primary cause of flooding, and identifies contributing factors including a complainant\u0027s own drainage issue",
      "proeth:element": "IBM Confirms Design Non-Compliance",
      "proeth:step": 4
    },
    {
      "proeth:description": "Faced with IBM\u0027s confirmed findings, R formally acknowledges the design error and undertakes remediation of the stormwater system",
      "proeth:element": "R Acknowledges Error and Remediates",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Property Owners Lodge Complaints",
  "proeth:counterfactual": "Without formal complaints from property owners, City C would likely not have initiated an independent review, and the design non-compliance and conflict of interest may have remained unaddressed; the complaints were the direct trigger for IBM\u0027s engagement",
  "proeth:effect": "City Engages IBM for Review",
  "proeth:necessaryFactors": [
    "Neighboring property owners experiencing and documenting flood damage",
    "Property owners formally lodging complaints with City C regarding both flooding and the conflict of interest",
    "City C\u0027s institutional response obligation upon receiving formal complaints",
    "City C\u0027s recognition that J\u0027s conflict of interest compromised the integrity of the original review"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "City C (decision to engage IBM); property owners as initiating actors",
  "proeth:sufficientFactors": [
    "Formal complaints alleging both technical failure and ethical breach + City C\u0027s accountability obligation = decision to commission independent review"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/11#",
    "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/11#CausalChain_69e6e3d9",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Following IBM\u0027s confirmation of substantial stormwater design non-compliance, Principal Engineer R formally acknowledged the design error and undertook remediation of the stormwater system",
  "proeth:causalSequence": [
    {
      "proeth:description": "R\u0027s original non-compliant design decisions create the technical error that will later require acknowledgment and remediation",
      "proeth:element": "R Designs Stormwater Plans",
      "proeth:step": 1
    },
    {
      "proeth:description": "IBM\u0027s independent technical analysis produces authoritative, documented confirmation that R\u0027s stormwater design was substantially non-compliant",
      "proeth:element": "IBM Confirms Design Non-Compliance",
      "proeth:step": 2
    },
    {
      "proeth:description": "IBM additionally identifies that one complainant\u0027s property had its own drainage issue, providing partial context but not negating R\u0027s primary design responsibility",
      "proeth:element": "IBM Identifies Contributing Factors",
      "proeth:step": 3
    },
    {
      "proeth:description": "Confronted with IBM\u0027s findings and professional obligations, R formally acknowledges the design error and commits to and executes remediation of the stormwater system",
      "proeth:element": "R Acknowledges Error and Remediates",
      "proeth:step": 4
    },
    {
      "proeth:description": "Corrected stormwater infrastructure addresses the design deficiency, mitigating ongoing flood risk to neighboring properties",
      "proeth:element": "Remediation Outcome",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "IBM Confirms Design Non-Compliance",
  "proeth:counterfactual": "Without IBM\u0027s independent confirmation, R might have contested the flooding causation or attributed it to other factors; IBM\u0027s findings created the evidentiary and professional basis that made acknowledgment and remediation the necessary response",
  "proeth:effect": "R Acknowledges Error and Remediates",
  "proeth:necessaryFactors": [
    "IBM\u0027s independent and authoritative technical confirmation of the design deficiency",
    "The formal, documented nature of IBM\u0027s findings creating professional and legal accountability for R",
    "R\u0027s professional obligation as a licensed engineer to correct identified errors",
    "The absence of a credible technical basis for R to contest IBM\u0027s findings"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Principal Engineer R",
  "proeth:sufficientFactors": [
    "Authoritative independent confirmation of error + professional licensing obligations + legal/reputational exposure = R\u0027s acknowledgment and remediation commitment"
  ],
  "proeth:withinAgentControl": true
}