{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_City_Engages_Firm_DBA",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "City establishes explicit equity and accessibility standards in Firm DBA\u0027s contract, including required session times, locations, and virtual participation options",
    "City requires Engineer M, as lead engineer, to co-design and approve the outreach plan before any sessions are held",
    "City conducts outreach in-house using community liaisons already trusted by Community P"
  ],
  "proeth-scenario:characterMotivation": "The City sought to fulfill procedural public engagement requirements while managing project timelines and costs, delegating outreach coordination to a specialized firm without establishing adequate oversight mechanisms or equity-centered performance standards.",
  "proeth-scenario:consequencesIfAlternative": [
    "Contractual equity standards would have created enforceable obligations, giving Engineer M and the City legal and professional leverage to demand compliance before the misleading report was produced",
    "Engineer M\u0027s co-design authority would have surfaced scheduling and access problems at the planning stage, preventing biased session design from ever being implemented",
    "In-house outreach with trusted liaisons would have reduced the structural conflict of interest created by engaging a firm with apparent ties or preferences favoring Community Q"
  ],
  "proeth-scenario:decisionSignificance": "Teaches that delegation of professional responsibilities does not eliminate the delegating party\u0027s ethical accountability. Selecting and structuring a contractor relationship without equity safeguards is itself an ethically significant decision, not a neutral administrative act.",
  "proeth-scenario:ethicalTension": "Procedural compliance versus substantive equity: satisfying the formal requirement of public engagement versus ensuring that engagement is genuinely inclusive and representative of all affected communities, particularly historically underserved ones.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The structural conditions for all subsequent failures are established here. If outreach is captured by a biased firm with no accountability mechanisms, Community P\u0027s interests may be systematically excluded from a project that will physically reshape their neighborhood, potentially causing irreversible displacement and harm.",
  "proeth:description": "The City decides to require public engagement sessions and selects Firm DBA as the outreach coordination partner for the highway infrastructure project affecting Community P. This decision establishes the structural conditions under which subsequent outreach failures occur.",
  "proeth:foreseenUnintendedEffects": [
    "Delegation of outreach design to a third party reduces direct City oversight of session quality and accessibility",
    "Risk that Firm DBA\u0027s implementation choices may not equitably serve all affected communities"
  ],
  "proeth:fulfillsObligation": [
    "Procedural requirement to conduct public engagement before infrastructure decisions"
  ],
  "proeth:guidedByPrinciple": [
    "Public welfare paramount",
    "Equitable community engagement",
    "Client accountability for delegated functions"
  ],
  "proeth:hasAgent": "City (municipal client / project authority)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Administrative efficiency vs. equitable public participation",
    "proeth:resolutionReasoning": "City resolved in favor of administrative convenience, delegating outreach design to Firm DBA without imposing accessibility or inclusivity standards that would have protected Community P"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill procedural public engagement requirements and advance the highway project through an organized outreach process",
  "proeth:requiresCapability": [
    "Procurement and vendor selection judgment",
    "Understanding of equitable public engagement standards",
    "Contract scope definition for outreach services"
  ],
  "proeth:temporalMarker": "Planning phase",
  "proeth:violatesObligation": [
    "Duty to ensure equitable access to public participation for historically underserved communities",
    "Obligation to exercise adequate oversight of contracted outreach activities affecting public welfare"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "City Engages Firm DBA"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_Scheduling_Sessions_Inaccessibly",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Schedule multiple sessions at varied times, including evenings and weekends, at locations within or immediately accessible to Community P",
    "Partner with Community P neighborhood organizations, churches, or schools to co-host sessions in trusted, familiar spaces",
    "Conduct targeted outreach to Community P residents through door-to-door canvassing, multilingual flyers, and community radio to maximize awareness and attendance"
  ],
  "proeth-scenario:characterMotivation": "Firm DBA, whether due to explicit City instructions, implicit bias, logistical convenience, or advocacy for Community Q\u0027s preferred route, structured sessions to minimize Community P participation while generating a veneer of public engagement sufficient to satisfy procedural requirements.",
  "proeth-scenario:consequencesIfAlternative": [
    "Accessible scheduling would have produced representative participation data, potentially revealing strong Community P opposition that would need to be formally addressed in the project record",
    "Community-partnered hosting would have built trust, increased attendance, and created accountability to local stakeholders who could independently verify the fairness of the process",
    "Targeted outreach would have ensured that the most affected residents were informed and empowered to participate, producing a legitimately representative engagement record"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how procedural injustice can be engineered through ostensibly neutral logistical decisions. Students learn that time and location choices in public engagement are not merely administrative details but are ethically loaded decisions with distributive consequences.",
  "proeth-scenario:ethicalTension": "Operational convenience and client alignment versus equitable public participation: the tension between designing outreach that is easy to execute and politically favorable versus designing outreach that is genuinely accessible to the most affected and least powerful community.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Community P residents are structurally prevented from meaningfully participating in decisions about infrastructure that will directly affect their homes, businesses, and neighborhood character. The democratic legitimacy of the entire planning process is compromised from this point forward.",
  "proeth:description": "Firm DBA deliberately schedules public outreach sessions during work hours at locations inaccessible to Community P and situated in Community Q, the area favoring the alternate route. This structurally suppresses Community P participation while amplifying Community Q\u0027s voice.",
  "proeth:foreseenUnintendedEffects": [
    "Community P residents would be effectively excluded from meaningful participation",
    "The resulting participation record would misrepresent community sentiment",
    "Engineer M and other stakeholders might raise objections"
  ],
  "proeth:fulfillsObligation": [
    "Nominal procedural compliance with holding sessions (form only)"
  ],
  "proeth:guidedByPrinciple": [
    "Objectivity in professional practice",
    "Public welfare over client convenience",
    "Truthfulness in process design",
    "Equity in access to civic participation"
  ],
  "proeth:hasAgent": "Firm DBA (public outreach contractor)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client instruction compliance vs. independent professional ethical duty",
    "proeth:resolutionReasoning": "Firm DBA resolved in favor of client political and logistical convenience, treating prior precedent as sufficient justification and subordinating its independent ethical duty to equitable outreach design"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Conduct sessions that satisfy procedural outreach requirements while producing a participation record favorable to Community Q and the alternate route, consistent with City instructions",
  "proeth:requiresCapability": [
    "Community engagement planning",
    "Accessibility and logistics assessment",
    "Demographic analysis of affected populations"
  ],
  "proeth:temporalMarker": "Outreach phase",
  "proeth:violatesObligation": [
    "NSPE Code obligation to hold paramount the safety, health, and welfare of the public (Code I.1)",
    "Duty to conduct objective and truthful professional services",
    "Obligation to serve the public interest, not merely client political preferences",
    "Duty of equitable treatment of all affected community stakeholders"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Scheduling Sessions Inaccessibly"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_Excluding_Written_and_Virtual_Participation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Establish a dedicated project website with a written comment submission portal, accessible in multiple languages, open for a minimum 30-day comment period",
    "Hold at least one virtual session via video conferencing platform with recorded proceedings and a public transcript",
    "Distribute written comment cards at community centers, libraries, and local businesses within Community P, with a prepaid return option"
  ],
  "proeth-scenario:characterMotivation": "Firm DBA further narrowed participation channels, either to reduce administrative burden, to limit the volume of documented opposition from Community P, or to ensure that the only voices captured were those of residents able to attend inaccessible in-person sessions, compounding the exclusionary effect of the scheduling decision.",
  "proeth-scenario:consequencesIfAlternative": [
    "A written comment portal would have created a documented, timestamped, and publicly verifiable record of Community P concerns that could not be omitted from the outreach report without obvious falsification",
    "A virtual session with a public transcript would have produced an independent evidentiary record of participation and concerns, directly contradicting any false claims of community support",
    "Distributed comment cards would have extended participation to residents with the highest barriers to in-person attendance, generating documented evidence of community sentiment that would have to be addressed in the project record"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates the compounding nature of exclusionary design decisions. Each individual choice to eliminate a participation channel may appear minor in isolation, but together they constitute a systematic pattern of exclusion that undermines the integrity of the entire public engagement process.",
  "proeth-scenario:ethicalTension": "Minimizing process complexity versus maximizing participatory access: the tension between a streamlined, low-cost engagement process and the professional and ethical obligation to ensure that all affected parties have a meaningful and documented opportunity to be heard.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Residents with disabilities, caregiving responsibilities, transportation barriers, or work schedule conflicts are entirely excluded from the process. The absence of written comments means there is no documented record of Community P concerns, making it easier to falsely claim community support in subsequent reporting.",
  "proeth:description": "Firm DBA decides not to provide written comment submission methods and not to hold virtual meetings, further narrowing participation channels to only those residents able to attend in-person sessions at inaccessible times and locations. This decision compounds the exclusionary effect of the scheduling decision.",
  "proeth:foreseenUnintendedEffects": [
    "Residents with work conflicts, disabilities, or transportation barriers would be entirely excluded",
    "The absence of written comments would make it easier to omit or mischaracterize Community P input in the final report",
    "The decision would later be concealed in the report by omitting mention of what was not offered"
  ],
  "proeth:guidedByPrinciple": [
    "Inclusivity in public engagement",
    "Accessibility as a professional standard",
    "Objectivity and completeness in process design",
    "Public welfare over procedural minimalism"
  ],
  "proeth:hasAgent": "Firm DBA (public outreach contractor)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Outreach scope minimization vs. equitable access to participation",
    "proeth:resolutionReasoning": "Firm DBA prioritized logistical minimalism and client preference, omitting standard accessible participation channels without documented justification"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Limit the volume and diversity of Community P input by restricting participation to a single, logistically burdensome channel, producing a thinner and more controllable participation record",
  "proeth:requiresCapability": [
    "Public engagement channel design",
    "Accessibility standards knowledge",
    "Virtual meeting facilitation capability"
  ],
  "proeth:temporalMarker": "Outreach phase",
  "proeth:violatesObligation": [
    "NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)",
    "Duty to provide objective professional services not distorted by client political preferences",
    "Obligation to ensure meaningful public participation in infrastructure decisions affecting underserved communities",
    "Duty of truthfulness in professional practice"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Excluding Written and Virtual Participation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_Engineer_M_Raises_Concerns",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Engineer M documents concerns in writing to Firm DBA, creating a formal record of the objection and the specific deficiencies identified",
    "Engineer M remains silent, rationalizing that outreach is Firm DBA\u0027s responsibility and outside the scope of engineering judgment",
    "Engineer M raises concerns directly to the City simultaneously with raising them to Firm DBA, bypassing the informal first step"
  ],
  "proeth-scenario:characterMotivation": "Engineer M, observing low and unrepresentative Community P participation, recognized a professional and ethical obligation to act on behalf of the public interest and the affected community. As lead engineer, Engineer M understood that the integrity of the project depended on a legitimate engagement process and that silence would constitute complicity in the exclusion of a vulnerable population.",
  "proeth-scenario:consequencesIfAlternative": [
    "Written documentation would have created an evidentiary record of Engineer M\u0027s objection prior to the misleading report, strengthening Engineer M\u0027s position in subsequent escalation and potentially triggering Firm DBA\u0027s own internal review processes",
    "Silence would have allowed the flawed process to proceed unchallenged, making Engineer M complicit in the exclusion of Community P and potentially exposing Engineer M to professional liability for failing to act in the public interest",
    "Direct escalation to the City at this stage might have produced faster correction but could also have been perceived as bypassing the professional chain of communication, potentially damaging the working relationship and reducing the City\u0027s receptiveness to Engineer M\u0027s concerns"
  ],
  "proeth-scenario:decisionSignificance": "A pivotal teaching moment about the obligation to raise concerns early, directly, and specifically. Students learn that professional ethics requires active intervention, not passive observation, and that the lead engineer\u0027s responsibility to the public interest extends to the conduct of collaborating firms.",
  "proeth-scenario:ethicalTension": "Professional courage versus organizational harmony: the tension between the obligation to speak up when observing unethical conduct by a collaborating firm and the professional and social pressures to defer to established processes, avoid conflict with partners, and maintain working relationships within the project team.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "This is Engineer M\u0027s first opportunity to correct the course of the project before the misleading report is produced. Failure to raise concerns, or raising them ineffectively, allows the exclusionary process to become the official record. Success at this stage could prevent all subsequent escalation steps.",
  "proeth:description": "Engineer M, serving as lead engineer, decides to express concern to Firm DBA about the outreach practices and session locations after observing the low and unrepresentative participation from Community P. This is a direct professional challenge to a collaborating firm\u0027s conduct.",
  "proeth:foreseenUnintendedEffects": [
    "Risk of professional friction with Firm DBA",
    "Risk of being perceived by the City as obstructing project progress",
    "Possible escalation of conflict if Firm DBA dismisses concerns"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)",
    "Duty to notify appropriate parties of potential project failures or ethical violations (Code III.1.b)",
    "Obligation not to remain passive when aware of practices that misrepresent public input"
  ],
  "proeth:guidedByPrinciple": [
    "Public welfare paramount",
    "Professional integrity",
    "Duty to speak up when aware of harmful or dishonest practices",
    "Collegial professional accountability"
  ],
  "proeth:hasAgent": "Engineer M (lead engineer, retained by City)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional collegiality and project continuity vs. ethical duty to flag violations",
    "proeth:resolutionReasoning": "Engineer M correctly prioritized the ethical obligation to Community P and project integrity over the risk of professional friction, consistent with NSPE Code duties"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Prompt Firm DBA to correct the outreach deficiencies, ensure Community P receives genuine engagement opportunities, and protect the integrity of the project record",
  "proeth:requiresCapability": [
    "Professional communication and advocacy",
    "Knowledge of public engagement standards",
    "Ethical judgment under NSPE Code",
    "Lead engineer authority to challenge collaborating firm conduct"
  ],
  "proeth:temporalMarker": "Post-sessions phase",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer M Raises Concerns"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_Firm_DBA_Dismisses_Concerns",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Firm DBA acknowledges Engineer M\u0027s concerns and agrees to schedule additional accessible sessions and open a written comment period before finalizing the outreach report",
    "Firm DBA escalates Engineer M\u0027s concerns internally to its own licensed PE supervisors and firm leadership for a formal review of outreach practices",
    "Firm DBA requests a joint meeting with the City, Engineer M, and Firm DBA to clarify the City\u0027s outreach requirements and resolve the disagreement about adequacy"
  ],
  "proeth-scenario:characterMotivation": "Firm DBA, facing a professional challenge to its conduct, chose to defend its practices by invoking external authority (City instructions) and institutional precedent rather than engaging substantively with Engineer M\u0027s equity concerns. This deflection served to protect the firm from accountability while foreclosing the possibility of voluntary correction.",
  "proeth-scenario:consequencesIfAlternative": [
    "Scheduling additional sessions and opening a written comment period would have partially remediated the exclusionary process, potentially generating a more representative record and reducing the severity of the ethical violation, though it would not have fully corrected the harm already done",
    "Internal escalation to Firm DBA\u0027s licensed PE supervisors would have engaged the firm\u0027s own professional accountability mechanisms, potentially producing a more rigorous internal review and a decision to correct the report before it was issued",
    "A joint meeting with the City would have surfaced the conflict between City instructions and professional equity obligations in a structured forum, potentially prompting the City to revise its instructions and creating a documented record of the disagreement"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the \u0027just following orders\u0027 defense in professional ethics contexts and its inadequacy as a justification for harmful conduct. Students learn that prior practice and client instructions do not override professional ethical obligations, and that invoking them to dismiss legitimate concerns is itself an ethically problematic act.",
  "proeth-scenario:ethicalTension": "Institutional deference versus independent professional judgment: the tension between following client instructions and established precedent as sufficient ethical justification versus the independent professional obligation to refuse participation in practices that harm the public, regardless of client direction or prior practice.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Firm DBA\u0027s refusal to self-correct eliminates the possibility of resolution at the lowest level of the escalation hierarchy. Engineer M is now forced into a more formal and adversarial escalation posture, increasing the professional and relational costs of pursuing the ethical obligation. The misleading report becomes more likely.",
  "proeth:description": "Firm DBA decides to reject Engineer M\u0027s concerns about outreach practices, citing City instructions and prior project precedent as sufficient justification. This decision forecloses voluntary correction and forces Engineer M toward escalation.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer M would be compelled to escalate concerns to the City or licensure board",
    "The project record would remain distorted and legally and reputationally vulnerable",
    "Firm DBA\u0027s licensed PE supervisors and owners would not be engaged in the ethical review"
  ],
  "proeth:guidedByPrinciple": [
    "Truthfulness and objectivity",
    "Responsiveness to peer ethical concerns",
    "Independent professional judgment over client-driven precedent"
  ],
  "proeth:hasAgent": "Firm DBA (public outreach contractor)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client instruction compliance and precedent vs. independent ethical correction obligation",
    "proeth:resolutionReasoning": "Firm DBA resolved in favor of client and precedent, treating these as sufficient justification and failing to exercise independent ethical judgment as required by the NSPE Code"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Maintain current outreach approach without modification, preserve alignment with City instructions, and avoid reopening sessions or revising the participation record",
  "proeth:requiresCapability": [
    "Ethical self-assessment and peer accountability",
    "Willingness to challenge client instructions when they conflict with professional obligations",
    "Knowledge of NSPE Code obligations for outreach and reporting"
  ],
  "proeth:temporalMarker": "Post-concern phase",
  "proeth:violatesObligation": [
    "NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)",
    "Duty to issue truthful and objective reports (Code II.3.b)",
    "Obligation to respond in good faith to substantive ethical concerns raised by a peer engineer",
    "Duty not to engage in deceptive professional practices"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Firm DBA Dismisses Concerns"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_Producing_Misleading_Outreach_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Firm DBA produces an accurate report that fully documents session locations, times, participation rates by community, and the absence of written and virtual participation options, along with the concerns raised by Community P attendees",
    "Firm DBA produces a report that acknowledges the limitations of the outreach process and recommends supplemental engagement before the project advances",
    "Firm DBA declines to produce a final report until the outreach deficiencies identified by Engineer M are remediated"
  ],
  "proeth-scenario:characterMotivation": "Firm DBA, having dismissed Engineer M\u0027s concerns and received no corrective instruction from the City, proceeded to produce a report that served the project\u0027s preferred narrative by omitting evidence of the flawed process and affirmatively misrepresenting Community P\u0027s position. This decision prioritized client satisfaction and project advancement over professional honesty and public interest.",
  "proeth-scenario:consequencesIfAlternative": [
    "An accurate report would have created an honest evidentiary record, potentially triggering regulatory or political scrutiny of the project\u0027s equity implications, but would have protected Firm DBA and Engineer M from professional misconduct liability",
    "A limitations-acknowledging report would have been a professionally honest, if incomplete, response that preserved the integrity of the project record while flagging the need for additional engagement before a final determination",
    "Declining to produce a final report would have been a bold professional integrity decision that might have prompted the City to either remediate the process or seek a different firm, but would have protected Firm DBA from producing a false document"
  ],
  "proeth-scenario:decisionSignificance": "Represents the most serious individual ethical violation in the narrative: deliberate professional dishonesty in an official document. Students learn to distinguish between errors of omission that mislead and affirmative false statements, and to recognize that both constitute professional misconduct. This action also transforms the ethical situation from one involving procedural failures to one involving active deception.",
  "proeth-scenario:ethicalTension": "Client service and project momentum versus professional honesty and public trust: the tension between producing a report that satisfies the client\u0027s apparent preferences and advances the project timeline versus the fundamental professional obligation to produce accurate, complete, and non-misleading documentation in an official project record.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "The misleading report, if accepted, will become the official record of community engagement for the project, potentially influencing funding decisions, regulatory approvals, and political support. Community P\u0027s documented opposition will be erased and replaced with fabricated support. The harm to Community P may become irreversible once the project advances based on this false record.",
  "proeth:description": "Firm DBA decides to prepare and issue a report that omits material details about session locations, times, and the absence of written comment options, and affirmatively frames the report to falsely claim Community P support for the project. This is a deliberate act of professional dishonesty in an official project document.",
  "proeth:foreseenUnintendedEffects": [
    "Engineer M would be placed in the position of associating with a fraudulent report",
    "Community P residents\u0027 documented concerns would be erased from the official record",
    "The project would be legally and reputationally exposed if the report\u0027s omissions were later discovered",
    "The misleading report could influence infrastructure decisions harming Community P"
  ],
  "proeth:guidedByPrinciple": [
    "Truthfulness and objectivity in professional documents",
    "Public welfare over client political convenience",
    "Completeness and accuracy in reporting",
    "Non-deception as a foundational professional norm"
  ],
  "proeth:hasAgent": "Firm DBA (public outreach contractor)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client outcome satisfaction vs. truthfulness and public welfare obligations",
    "proeth:resolutionReasoning": "Firm DBA resolved entirely in favor of client satisfaction, committing a deliberate act of professional dishonesty that constitutes the most serious ethical violation in the case"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Create an official project record that appears to document legitimate Community P engagement and support, enabling the City to proceed with the preferred route while suppressing evidence of the outreach\u0027s structural exclusions",
  "proeth:requiresCapability": [
    "Accurate and complete technical report writing",
    "Ethical judgment in representing participation data",
    "Willingness to document process limitations and constraints"
  ],
  "proeth:temporalMarker": "Report preparation phase",
  "proeth:violatesObligation": [
    "NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)",
    "NSPE Code prohibition on issuing false, misleading, or deceptive statements (Code II.3.b)",
    "NSPE Code prohibition on associating with fraudulent or dishonest enterprises (Code II.1.d)",
    "Duty of objectivity and truthfulness in professional reports",
    "Obligation to accurately represent the scope and limitations of professional work",
    "Duty not to misrepresent community input in public infrastructure planning"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Producing Misleading Outreach Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_Engineer_M_Confronts_Firm_DBA_Formally",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Engineer M sends a formal written communication to Firm DBA\u0027s licensed PE supervisors and firm owners documenting the specific report inaccuracies, citing NSPE Code provisions, and demanding written correction within a defined deadline",
    "Engineer M requests an in-person meeting with Firm DBA leadership and the City simultaneously, bypassing the sequential escalation structure",
    "Engineer M consults with their own firm\u0027s legal counsel and ethics advisor before taking any formal action against Firm DBA"
  ],
  "proeth-scenario:characterMotivation": "Engineer M, now confronting a completed misleading report and having already raised informal concerns that were dismissed, is directed to initiate a formal escalation sequence grounded in NSPE Code obligations. The motivation is both professional duty and public interest protection: Engineer M must create a documented record of formal objection and demand correction before the false report enters the official project record.",
  "proeth-scenario:consequencesIfAlternative": [
    "A formal written communication with a specific deadline would have created a timestamped evidentiary record of the demand for correction, strengthening Engineer M\u0027s position in all subsequent escalation steps and potential licensure board proceedings",
    "Simultaneous confrontation of Firm DBA and the City might have accelerated resolution but could have undermined the sequential escalation structure and reduced the City\u0027s perception of Engineer M as having acted in good faith through proper channels",
    "Consulting legal counsel and an ethics advisor before acting would have ensured that Engineer M\u0027s escalation strategy was both ethically sound and legally protected, reducing personal professional risk while potentially delaying action"
  ],
  "proeth-scenario:decisionSignificance": "Teaches the structure and purpose of professional escalation sequences in engineering ethics. Students learn that formal confrontation, explicitly grounded in code obligations and directed at licensed PE supervisors and firm leadership, is both a procedural requirement and a substantive ethical act that creates accountability and preserves the possibility of correction.",
  "proeth-scenario:ethicalTension": "Professional self-protection versus advocacy for the public: the tension between the personal and professional risks of formally confronting a collaborating firm and demanding correction of an official document versus the ethical obligation to protect Community P from the consequences of a false public record. Also, the tension between collegial professional relationships and accountability.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "If Engineer M fails to formally confront Firm DBA before escalating to the City, Engineer M may be seen as having bypassed the appropriate resolution hierarchy. If Engineer M confronts Firm DBA effectively, there is still a possibility of voluntary correction that avoids the most adversarial and professionally costly escalation steps. Failure to act at all exposes Engineer M to professional liability for complicity.",
  "proeth:description": "Engineer M is directed to immediately confer with Firm DBA, invoking NSPE Code obligations explicitly and engaging Firm DBA\u0027s licensed PE supervisors and firm owners to demand correction of the misleading report and outreach record. This is the first step in a prescribed escalation sequence.",
  "proeth:foreseenUnintendedEffects": [
    "Firm DBA may again refuse, necessitating City-level escalation",
    "The formal invocation of Code obligations may damage the working relationship with Firm DBA",
    "Firm DBA\u0027s PE supervisors may align with the firm\u0027s prior position rather than correct it"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)",
    "Duty not to associate with fraudulent or dishonest enterprises (Code II.1.d)",
    "Obligation to take action when aware of Code violations by other engineers",
    "Duty to advise when project integrity is compromised (Code III.1.b)"
  ],
  "proeth:guidedByPrinciple": [
    "Graduated escalation before external reporting",
    "Peer professional accountability",
    "Public welfare protection through active intervention",
    "Proportionality in professional response"
  ],
  "proeth:hasAgent": "Engineer M (lead engineer, retained by City)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Professional collegiality and project continuity vs. obligation to prevent fraudulent documentation",
    "proeth:resolutionReasoning": "The ethical obligation to prevent a fraudulent report from advancing outweighs the discomfort of formal confrontation; graduated escalation beginning with Firm DBA is the proportionate and professionally appropriate response"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Compel Firm DBA to correct the misleading report and outreach record by invoking formal professional obligations and engaging firm leadership with licensure accountability, avoiding the need for City-level or board-level escalation",
  "proeth:requiresCapability": [
    "Professional advocacy and formal communication",
    "Knowledge of NSPE Code provisions applicable to reporting and public welfare",
    "Lead engineer authority and standing to challenge collaborating firm conduct",
    "Ability to identify and engage PE-licensed supervisors within Firm DBA"
  ],
  "proeth:temporalMarker": "Recommended future action 1 (post-report, forward-looking)",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer M Confronts Firm DBA Formally"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Action_Engineer_M_Escalates_to_City",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Engineer M presents a formal written report to the City documenting all outreach deficiencies, the misleading report, Firm DBA\u0027s refusal to correct, and the specific NSPE Code provisions implicated, with a formal demand for corrective action and a response deadline",
    "Engineer M requests that the City commission an independent third-party audit of the outreach process before the project advances",
    "Engineer M simultaneously notifies the City and files a preliminary inquiry with the state engineering licensure board, rather than treating City escalation as a prerequisite to licensure board reporting"
  ],
  "proeth-scenario:characterMotivation": "If Firm DBA refuses to correct the report, Engineer M must escalate to the City as the client with ultimate authority over the project. The motivation is to present the evidentiary record of outreach deficiencies and report inaccuracies directly to the decision-maker who can compel correction, and to ensure that the City cannot later claim ignorance of the problem.",
  "proeth-scenario:consequencesIfAlternative": [
    "A formal written report to the City would have created a comprehensive evidentiary record of Engineer M\u0027s escalation efforts, protecting Engineer M professionally and giving the City a structured basis for demanding correction from Firm DBA",
    "An independent third-party audit would have removed the conflict of interest from the assessment of outreach adequacy and produced an authoritative, politically defensible finding that could compel correction without requiring Engineer M to be the sole accuser",
    "Simultaneous City and licensure board notification would have accelerated accountability but might have been perceived as disproportionate before the City had an opportunity to respond, potentially reducing the licensure board\u0027s receptiveness to Engineer M\u0027s complaint and damaging Engineer M\u0027s professional relationships"
  ],
  "proeth-scenario:decisionSignificance": "Teaches that the client is not exempt from professional accountability and that the engineer\u0027s duty to the public interest can require formally confronting the client with evidence of harm. Students learn the structure of the second escalation step and the importance of presenting concrete evidence rather than abstract concerns when confronting institutional authority.",
  "proeth-scenario:ethicalTension": "Client relationship preservation versus public interest advocacy: the tension between maintaining a productive working relationship with the City as the primary client and formally confronting the City with evidence that its own instructions or oversight failures contributed to the production of a misleading public record. Also, the tension between the engineer\u0027s duty to the client and the duty to the public.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "If the City accepts Engineer M\u0027s evidence and demands correction from Firm DBA, the false report can be remediated before it causes irreversible harm to Community P. If the City refuses or retaliates against Engineer M, Engineer M faces the most professionally costly escalation step: reporting to the state engineering licensure board. The project\u0027s integrity, Community P\u0027s interests, and Engineer M\u0027s professional standing are all at risk.",
  "proeth:description": "If Firm DBA refuses to correct the report discrepancies, Engineer M must confer directly with the City, potentially with Firm DBA present, presenting the evidence of outreach deficiencies and report inaccuracies and demanding corrective action from the client. This is the second step in the prescribed escalation sequence.",
  "proeth:foreseenUnintendedEffects": [
    "The City may side with Firm DBA, creating direct conflict between Engineer M and the client",
    "Engineer M risks being perceived as obstructing the project and may face professional retaliation",
    "If the City takes no action, Engineer M will face the difficult decision of whether to report to the licensure board"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)",
    "Duty to advise clients when a project may not be successful or when integrity is compromised (Code III.1.b)",
    "Obligation not to associate with fraudulent or dishonest enterprises (Code II.1.d)",
    "Duty to take escalating action when peer-level correction has failed"
  ],
  "proeth:guidedByPrinciple": [
    "Graduated escalation to client authority",
    "Client advisory duty",
    "Public welfare protection through systemic intervention",
    "Transparency with client about professional concerns"
  ],
  "proeth:hasAgent": "Engineer M (lead engineer, retained by City)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client loyalty and professional relationship preservation vs. duty to report project integrity failure to client",
    "proeth:resolutionReasoning": "Escalation to the City is the professionally required intermediate step before external reporting; it gives the client the opportunity to correct while fulfilling Engineer M\u0027s advisory and public welfare obligations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Compel the City to direct Firm DBA to correct the misleading report and conduct remedial outreach for Community P, using the client relationship as leverage when peer-level intervention has failed",
  "proeth:requiresCapability": [
    "Client communication and professional advocacy at senior level",
    "Evidence presentation and documentation of outreach deficiencies",
    "Ethical judgment under NSPE Code in client-conflict situations",
    "Lead engineer standing to raise systemic project integrity concerns with client"
  ],
  "proeth:temporalMarker": "Recommended future action 2 (conditional, forward-looking)",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer M Escalates to City"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Event_Concerns_Formally_Dismissed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "When a subcontractor cites client instructions as justification for ethically problematic conduct, what does this reveal about the structure of responsibility in multi-party engineering projects?",
    "At what point does Engineer M\u0027s knowledge of the dismissal create an affirmative obligation to act, rather than merely a permission to escalate?",
    "How should engineers respond when the client may itself be the source of the ethical problem?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer M experiences frustration, isolation, and heightened moral distress as the informal path is blocked; Firm DBA representatives may feel confident they are protected by City authority; the dismissal signals to Engineer M that the problem is systemic, not individual",
  "proeth-scenario:ethicalImplications": "Exposes the limits of hierarchical deference in engineering ethics; raises questions about whether institutional cover (prior practice, client instructions) can ever legitimize inequitable outcomes; illustrates the tension between loyalty to client and duty to public",
  "proeth-scenario:learningMoment": "Demonstrates the moment when an engineer\u0027s informal concern-raising is insufficient and formal escalation becomes obligatory; illustrates how \u0027following client instructions\u0027 is not an ethical defense when those instructions produce unjust outcomes.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Is now implicated as a possible source of the problematic instructions, raising questions about municipal accountability",
    "community_p": "Loses the benefit of early informal correction; the harm to their participation rights is now more likely to be baked into the official record",
    "engineer_m": "Now faces a harder escalation path; the dismissal increases personal and professional risk of further action while simultaneously making inaction more ethically untenable",
    "firm_dba": "Has created a documented record of refusing to correct a known problem, increasing its legal and ethical exposure"
  },
  "proeth:activatesConstraint": [
    "Escalation_Obligation_Constraint",
    "Engineer_M_Independent_Judgment_Constraint",
    "PublicInterest_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/5#Action_Firm_DBA_Dismisses_Concerns",
  "proeth:causesStateChange": "Informal remediation pathway is closed; Engineer M\u0027s obligation to escalate is now activated; the City is implicated as a potential co-author of the inequitable process",
  "proeth:createsObligation": [
    "Engineer_M_Must_Escalate_Beyond_Firm_DBA",
    "Engineer_M_Must_Document_Dismissal",
    "Engineer_M_Must_Evaluate_City_Complicity"
  ],
  "proeth:description": "After Engineer M raises concerns about the inequitable outreach process, Firm DBA\u0027s dismissal becomes an official organizational response, citing prior City practice and direct City instructions as justification\u2014effectively closing off informal resolution and escalating the ethical stakes.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer M raises concerns to Firm DBA",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Concerns Formally Dismissed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Event_Misleading_Report_Enters_Record",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Once a misleading report enters the official record, what specific steps is Engineer M ethically and professionally required to take, and in what order?",
    "How does the false claim of Community P support differ ethically from merely omitting their concerns\u2014and does that distinction matter for Engineer M\u0027s obligations?",
    "At what point does Engineer M\u0027s continued association with this project, without active correction, constitute a violation of professional ethics codes?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer M faces acute moral distress and professional alarm upon seeing the report; Community P residents, if aware, would feel profound betrayal; Firm DBA representatives may feel relief that the process is \u0027complete\u0027; City officials may be complicit or willfully ignorant",
  "proeth-scenario:ethicalImplications": "Raises fundamental questions about truth-telling in public documents, the engineer\u0027s duty to the public versus the client, the limits of institutional loyalty, and the conditions under which reporting to a licensure board becomes not just permissible but required; also implicates environmental justice and the rights of underserved communities to accurate representation in planning processes",
  "proeth-scenario:learningMoment": "Represents the culminating ethical crisis of the case: a false official record now exists, and Engineer M\u0027s obligations are no longer merely advisory but imperative. Students must grapple with what it means to be the lead engineer on a project whose official record contains known falsehoods.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Has received and may act upon a false report; faces legal vulnerability if project proceeds on this record and is later challenged",
    "community_p_residents": "Their concerns are not only unaddressed but actively misrepresented; project decisions affecting their homes and businesses may proceed on a false premise of their support",
    "engineer_m": "Now bears direct professional and ethical responsibility to correct the record or escalate; continued silence becomes active complicity; license and professional standing are at risk",
    "firm_dba": "Has produced a document that constitutes professional misrepresentation and potentially fraud; faces significant legal, regulatory, and reputational exposure",
    "state_licensure_board": "May become relevant if Engineer M determines that Firm DBA\u0027s conduct rises to the level of reportable professional misconduct"
  },
  "proeth:activatesConstraint": [
    "Truthfulness_In_Public_Documents_Constraint",
    "PublicInterest_Protection_Constraint",
    "Engineer_M_Oversight_And_Correction_Constraint",
    "Professional_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/5#Action_Producing_Misleading_Outreach_Report",
  "proeth:causesStateChange": "Official project record is now corrupted with false information; all downstream project decisions risk being built on a fraudulent foundation; Engineer M\u0027s obligation to act is now at its highest urgency",
  "proeth:createsObligation": [
    "Engineer_M_Must_Formally_Confront_Firm_DBA",
    "Engineer_M_Must_Escalate_To_City_If_Unresolved",
    "Engineer_M_Must_Consider_Licensure_Board_Report",
    "Correct_Or_Supplement_Official_Record",
    "Prevent_Project_Decisions_Based_On_False_Record"
  ],
  "proeth:description": "Firm DBA\u0027s completed outreach report\u2014omitting session location and timing details and falsely claiming Community P support\u2014becomes part of the official project planning record, creating a false evidentiary foundation for subsequent project decisions.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After outreach sessions conclude and Firm DBA produces the report",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Misleading Report Enters Record"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Event_Project_Record_Integrity_Compromised",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What is the difference between Engineer M\u0027s responsibility for Firm DBA\u0027s actions versus Engineer M\u0027s responsibility for the state of the official project record\u2014and does that distinction change what Engineer M must do?",
    "If Engineer M escalates through the full sequence (Firm DBA, City, licensure board) and no correction occurs, what options remain, and are any of them obligatory?",
    "How does the concept of \u0027lead engineer\u0027 responsibility change the ethical calculus compared to a situation where Engineer M was merely one of many project participants?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer M faces the weight of systemic failure and the full burden of professional responsibility; Community P faces the prospect of harmful project decisions proceeding without their voice; the situation produces a sense of institutional betrayal and urgency",
  "proeth-scenario:ethicalImplications": "Crystallizes the core tension of the case: the engineer\u0027s duty to the client versus the duty to the public; raises questions about systemic accountability, the ethics of institutional complicity, and whether engineering ethics codes are adequate to address situations where the client itself may be part of the problem; highlights environmental justice dimensions of infrastructure planning in underserved communities",
  "proeth-scenario:learningMoment": "The cumulative integrity failure illustrates how individual procedural violations compound into systemic ethical crises; students should understand that lead engineers bear responsibility not just for their own actions but for the integrity of the entire process they oversee.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Faces potential legal challenge, civil rights liability, and reputational damage if project proceeds on a compromised record",
    "community_p_residents": "Face project decisions\u2014potentially including displacement and business disruption\u2014made on the basis of a record that falsely claims their support; their interests are at maximum risk",
    "engineer_m": "Bears the heaviest professional burden: as lead engineer, the integrity of the project record is within the scope of professional responsibility; inaction is no longer ethically available",
    "firm_dba": "Has produced a record of professional misconduct that may warrant licensure board referral",
    "future_affected_communities": "The precedent set by this case affects how future underserved communities can expect to be treated in infrastructure planning"
  },
  "proeth:activatesConstraint": [
    "PublicInterest_Protection_Constraint",
    "Professional_Integrity_Constraint",
    "Truthfulness_In_Engineering_Practice_Constraint",
    "Engineer_M_Lead_Responsibility_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/5#Action_Producing_Misleading_Outreach_Report",
  "proeth:causesStateChange": "The planning process has lost its legitimacy as a fair public participation exercise; any project decisions made on the basis of this record are built on a false foundation; Engineer M\u0027s role as lead engineer makes this Engineer M\u0027s professional responsibility to address",
  "proeth:createsObligation": [
    "Halt_Or_Suspend_Reliance_On_False_Record",
    "Initiate_Corrective_Outreach_Process",
    "Engineer_M_Must_Formally_Document_All_Concerns",
    "Engineer_M_Must_Escalate_Through_Full_Sequence"
  ],
  "proeth:description": "As a systemic outcome of the cumulative actions\u2014biased sessions, excluded participation channels, dismissed concerns, and a false report\u2014the entire official planning record for the highway project affecting Community P is rendered unreliable and ethically tainted.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After misleading report enters official record; ongoing through planning phase",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Project Record Integrity Compromised"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Event_Community_P_Participation_Failure",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At what point does a procedural failure in public outreach become an ethical violation, and who bears responsibility for recognizing that threshold?",
    "What specific obligations does Engineer M have as lead engineer when a subcontractor\u0027s choices produce inequitable participation outcomes?",
    "How should engineers weigh \u0027prior City practice\u0027 as a justification when that practice produces discriminatory results?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Community P residents who attempt to participate feel dismissed and powerless; Engineer M experiences growing unease about the integrity of the process; Firm DBA representatives may feel indifferent or justified by prior City practice",
  "proeth-scenario:ethicalImplications": "Reveals a tension between procedural compliance (sessions were held) and substantive justice (the affected community was effectively excluded); raises questions about environmental justice, the duty to serve the public interest, and whether following client instructions absolves engineers of responsibility for inequitable outcomes",
  "proeth-scenario:learningMoment": "Demonstrates how procedural choices in public engagement\u2014timing, location, format\u2014can systematically exclude vulnerable communities even without overt intent, and how structural exclusion is itself an ethical violation requiring active correction by the lead engineer.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Risks producing a planning record that is legally and ethically vulnerable to challenge; potential civil rights and environmental justice implications",
    "community_p_residents": "Structurally excluded from decisions affecting their displacement and livelihoods; concerns about disruption go unrecorded in the official planning process",
    "community_q": "Benefits disproportionately from the skewed outreach process, though this advantage is built on a compromised foundation",
    "engineer_m": "Placed in an ethically precarious position as lead engineer on a process producing inequitable outcomes; professional obligations are now triggered",
    "firm_dba": "Has produced a structurally biased outreach process that may expose it to legal and ethical scrutiny"
  },
  "proeth:activatesConstraint": [
    "EquitableParticipation_Constraint",
    "PublicInterest_Protection_Constraint",
    "NonDiscrimination_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/5#Action_Scheduling_Sessions_Inaccessibly",
  "proeth:causesStateChange": "Public record now reflects skewed participation; Community P\u0027s concerns are structurally absent from the planning record; project legitimacy is compromised",
  "proeth:createsObligation": [
    "Engineer_M_Must_Raise_Concerns",
    "Remedial_Outreach_Required",
    "Document_Participation_Gaps",
    "Notify_City_Of_Inequity"
  ],
  "proeth:description": "Due to inaccessible scheduling and location choices, few Community P residents are able to participate in the public outreach sessions, resulting in a near-total exclusion of the historically underserved neighborhood from the planning process.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During public outreach phase, concurrent with session scheduling",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Community P Participation Failure"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#Event_Displacement_Concerns_Raised",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the fact that some Community P residents were able to raise concerns mitigate the ethical problems with the outreach process, or does it make the subsequent misrepresentation worse?",
    "What responsibility does Engineer M have upon hearing these concerns directly, beyond what was already triggered by the participation failure?",
    "How should displacement and economic disruption concerns from underserved communities be weighted in infrastructure planning decisions?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Community P participants feel a mix of urgency and futility\u2014their concerns are real but the process feels stacked against them; Engineer M hears concerns that reinforce existing unease; Firm DBA representatives may feel these concerns are inconvenient or easily managed",
  "proeth-scenario:ethicalImplications": "Highlights the gap between procedural legitimacy and substantive representation; raises questions about who counts as the \u0027public\u0027 in public interest obligations; demonstrates how engineering decisions have distributional consequences that fall unevenly on vulnerable populations",
  "proeth-scenario:learningMoment": "Illustrates how a compromised process can produce a technically present but practically meaningless public record\u2014and how engineers must distinguish between the appearance of public engagement and its substance.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Is now on constructive notice of displacement and disruption concerns, increasing its legal and ethical exposure if these are not addressed",
    "community_p_residents": "Their concerns are on record but in a thin, easily obscured form given low participation numbers; they face real risks of displacement and economic harm",
    "engineer_m": "Now has direct knowledge of specific community harms, strengthening the obligation to ensure these concerns are faithfully documented and addressed",
    "firm_dba": "The existence of these concerns creates a documentation obligation that will later be violated in the misleading report"
  },
  "proeth:activatesConstraint": [
    "PublicComment_Documentation_Constraint",
    "PublicInterest_Protection_Constraint",
    "Accurate_Reporting_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/5#Action_Scheduling_Sessions_Inaccessibly",
  "proeth:causesStateChange": "A formal, if incomplete, record of Community P objections now exists; these concerns become a benchmark against which the subsequent outreach report can be evaluated for accuracy",
  "proeth:createsObligation": [
    "Firm_DBA_Must_Document_Concerns_Accurately",
    "Engineer_M_Must_Ensure_Concerns_Are_Recorded",
    "City_Must_Address_Displacement_Concerns_In_Planning"
  ],
  "proeth:description": "The small number of Community P residents who do manage to participate in outreach sessions raise concerns about displacement and business disruption caused by the proposed highway project, creating an official\u2014if thin\u2014record of community objection.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During public outreach sessions, after Community P participation failure",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Displacement Concerns Raised"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#CausalChain_3103ae4e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Due to inaccessible scheduling and location choices, few Community P residents are able to participa",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm DBA deliberately schedules sessions during work hours at locations inaccessible to Community P",
      "proeth:element": "Scheduling Sessions Inaccessibly",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA simultaneously removes all alternative participation channels, closing off any compensatory access",
      "proeth:element": "Excluding Written and Virtual Participation",
      "proeth:step": 2
    },
    {
      "proeth:description": "Few Community P residents are able to attend or contribute, producing a structurally unrepresentative outreach process",
      "proeth:element": "Community P Participation Failure",
      "proeth:step": 3
    },
    {
      "proeth:description": "Only the small number who do attend raise displacement concerns, leaving the majority of affected voices absent from the record",
      "proeth:element": "Displacement Concerns Raised",
      "proeth:step": 4
    },
    {
      "proeth:description": "The participation failure feeds into a cumulative record that misrepresents community input and undermines project legitimacy",
      "proeth:element": "Project Record Integrity Compromised",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Scheduling Sessions Inaccessibly",
  "proeth:counterfactual": "Had sessions been scheduled outside work hours at accessible locations, Community P residents would have had a meaningful opportunity to participate, making the participation failure unlikely",
  "proeth:effect": "Community P Participation Failure",
  "proeth:necessaryFactors": [
    "Deliberate scheduling during work hours",
    "Selection of locations inaccessible to Community P residents",
    "Absence of alternative participation channels"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm DBA",
  "proeth:sufficientFactors": [
    "Combination of work-hour scheduling + inaccessible locations + no virtual or written alternatives created a structurally exclusionary process sufficient to suppress Community P participation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#CausalChain_54c14ad0",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm DBA decides not to provide written comment submission methods and not to hold virtual meetings",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm DBA removes all non-in-person participation channels from the outreach process",
      "proeth:element": "Excluding Written and Virtual Participation",
      "proeth:step": 1
    },
    {
      "proeth:description": "Combined with inaccessible scheduling, the removal of alternatives leaves no viable participation path for most Community P residents",
      "proeth:element": "Scheduling Sessions Inaccessibly",
      "proeth:step": 2
    },
    {
      "proeth:description": "Community P residents are structurally excluded from meaningful engagement",
      "proeth:element": "Community P Participation Failure",
      "proeth:step": 3
    },
    {
      "proeth:description": "The low participation is misrepresented in Firm DBA\u0027s report as adequate community engagement",
      "proeth:element": "Misleading Report Enters Record",
      "proeth:step": 4
    },
    {
      "proeth:description": "Decision-makers rely on a record that falsely reflects community consent and input",
      "proeth:element": "Project Record Integrity Compromised",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Excluding Written and Virtual Participation",
  "proeth:counterfactual": "Had written or virtual options been available, residents excluded by scheduling and location barriers could still have submitted input, substantially reducing the participation failure",
  "proeth:effect": "Community P Participation Failure",
  "proeth:necessaryFactors": [
    "Removal of written comment submission as a participation channel",
    "Refusal to hold virtual meetings",
    "No compensatory mechanism offered to residents unable to attend in person"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm DBA",
  "proeth:sufficientFactors": [
    "Even if in-person sessions had been somewhat accessible, the elimination of written and virtual channels independently ensured that residents with work, mobility, or transportation constraints had no viable path to participation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#CausalChain_a93a7a1a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After Engineer M raises concerns about the inequitable outreach process, Firm DBA\u0027s dismissal become",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer M identifies inequitable outreach practices and formally expresses concern to Firm DBA",
      "proeth:element": "Engineer M Raises Concerns",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA rejects Engineer M\u0027s concerns, citing City instructions as justification",
      "proeth:element": "Firm DBA Dismisses Concerns",
      "proeth:step": 2
    },
    {
      "proeth:description": "The dismissal becomes an institutional event that forecloses internal correction and signals that exclusionary practices will continue",
      "proeth:element": "Concerns Formally Dismissed",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer M escalates to a formal invocation of NSPE Code obligations in response to the dismissal",
      "proeth:element": "Engineer M Confronts Firm DBA Formally",
      "proeth:step": 4
    },
    {
      "proeth:description": "Firm DBA\u0027s continued refusal triggers Engineer M\u0027s obligation to confer directly with the City",
      "proeth:element": "Engineer M Escalates to City",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Firm DBA Dismisses Concerns",
  "proeth:counterfactual": "Had Firm DBA engaged with Engineer M\u0027s concerns and initiated corrective action, the formal dismissal event would not have occurred and subsequent escalation would have been unnecessary",
  "proeth:effect": "Concerns Formally Dismissed",
  "proeth:necessaryFactors": [
    "Engineer M having raised concerns formally",
    "Firm DBA\u0027s active decision to reject those concerns",
    "Firm DBA citing City instructions as cover for dismissal without independent verification"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm DBA",
  "proeth:sufficientFactors": [
    "Firm DBA\u0027s authoritative rejection of Engineer M\u0027s concerns, combined with the institutional power differential between the coordinating firm and the lead engineer, was sufficient to formalize the dismissal and allow exclusionary practices to continue uncorrected"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#CausalChain_9901856d",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm DBA\u0027s completed outreach report\u2014omitting session location and timing details and falsely claimi",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm DBA prepares and issues a report omitting material details and misrepresenting community participation",
      "proeth:element": "Producing Misleading Outreach Report",
      "proeth:step": 1
    },
    {
      "proeth:description": "The report is formally submitted and incorporated into the official project record without correction",
      "proeth:element": "Misleading Report Enters Record",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer M formally invokes NSPE Code obligations to demand correction of the report discrepancies",
      "proeth:element": "Engineer M Confronts Firm DBA Formally",
      "proeth:step": 3
    },
    {
      "proeth:description": "Firm DBA\u0027s refusal to correct the report triggers Engineer M\u0027s direct escalation to the City",
      "proeth:element": "Engineer M Escalates to City",
      "proeth:step": 4
    },
    {
      "proeth:description": "The uncorrected misleading report becomes a permanent feature of the project record, undermining the integrity of all downstream decisions",
      "proeth:element": "Project Record Integrity Compromised",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Producing Misleading Outreach Report",
  "proeth:counterfactual": "Had the report accurately disclosed session locations, timing, participation barriers, and the actual scope of community input, decision-makers would have had a materially different evidentiary basis and the record integrity would not have been compromised in this manner",
  "proeth:effect": "Misleading Report Enters Record",
  "proeth:necessaryFactors": [
    "Firm DBA\u0027s decision to omit material details about session locations and timing",
    "Firm DBA\u0027s decision to misrepresent the extent or quality of community participation",
    "The report being formally submitted and accepted into the official project record"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm DBA",
  "proeth:sufficientFactors": [
    "The combination of material omissions and affirmative misrepresentations in a formally submitted document was sufficient to corrupt the evidentiary basis of the project record, regardless of whether decision-makers scrutinized the report"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/5#",
    "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/5#CausalChain_67e7997a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The City decides to require public engagement sessions and selects Firm DBA as the outreach coordina",
  "proeth:causalSequence": [
    {
      "proeth:description": "City selects Firm DBA as outreach coordinator without establishing enforceable accessibility standards or oversight mechanisms",
      "proeth:element": "City Engages Firm DBA",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA, operating without accountability constraints, implements an exclusionary outreach design",
      "proeth:element": "Scheduling Sessions Inaccessibly and Excluding Written and Virtual Participation",
      "proeth:step": 2
    },
    {
      "proeth:description": "The exclusionary design structurally suppresses Community P participation",
      "proeth:element": "Community P Participation Failure",
      "proeth:step": 3
    },
    {
      "proeth:description": "Firm DBA misrepresents the suppressed participation as adequate in the official outreach report",
      "proeth:element": "Misleading Report Enters Record",
      "proeth:step": 4
    },
    {
      "proeth:description": "The cumulative effect of biased sessions, excluded channels, dismissed concerns, and a misleading report permanently compromises the evidentiary integrity of the project record",
      "proeth:element": "Project Record Integrity Compromised",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "City Engages Firm DBA",
  "proeth:counterfactual": "Had the City established clear accessibility requirements, monitored outreach execution, and required independent verification of participation claims, Firm DBA\u0027s exclusionary practices would have been constrained or detected before corrupting the project record",
  "proeth:effect": "Project Record Integrity Compromised",
  "proeth:necessaryFactors": [
    "City\u0027s selection of Firm DBA without adequate vetting of outreach methodology",
    "City\u0027s failure to establish enforceable accessibility and participation standards as conditions of engagement",
    "City\u0027s absence of ongoing oversight of Firm DBA\u0027s outreach execution"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "City (shared with Firm DBA)",
  "proeth:sufficientFactors": [
    "The City\u0027s delegation of outreach coordination to Firm DBA without accountability structures was a necessary precondition, but alone insufficient\u2014it became sufficient only in combination with Firm DBA\u0027s subsequent exclusionary decisions and misrepresentations"
  ],
  "proeth:withinAgentControl": true
}