{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Action_Retain_Engineer_A_as_Subconsultant",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Retain Engineer A with a broader scope that includes flagging any apparent structural or safety anomalies encountered during pavement inspection, even if not the primary deliverable.",
    "Retain multiple subconsultants with overlapping observational duties and a clear protocol for escalating out-of-scope safety concerns.",
    "Include a contractual clause explicitly requiring all subconsultants to report any observed conditions that may pose a public safety risk, regardless of primary scope."
  ],
  "proeth-scenario:characterMotivation": "VWX sought a cost-efficient, specialized subconsultant to handle a discrete technical task (pavement assessment) within a larger bridge overhaul project, deliberately limiting Engineer A\u0027s scope to control project boundaries, liability exposure, and budget.",
  "proeth-scenario:consequencesIfAlternative": [
    "A broader scope would have given Engineer A clear contractual authority \u2014 and obligation \u2014 to formally document and report the wall defect, potentially preventing the ethical ambiguity that follows and creating a cleaner paper trail for the public agency.",
    "Overlapping observational duties would reduce the risk of safety gaps but increase cost and coordination complexity; however, the wall defect would more likely have been formally captured and escalated.",
    "An explicit safety-reporting clause would have resolved the later ethical dilemma by making Engineer A\u0027s duty to report unambiguous, regardless of the public agency\u0027s subsequent instruction to omit \u2014 potentially triggering a direct conflict with that instruction much earlier in the process."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how scope-of-work definitions in engineering contracts can inadvertently create \u0027responsibility voids\u0027 for public safety observations, and raises the question of whether prime consultants bear an obligation to ensure holistic safety coverage when retaining subconsultants on public projects.",
  "proeth-scenario:ethicalTension": "Operational efficiency and contractual clarity vs. the systemic risk that narrowly siloed scopes of work may leave critical safety observations without a designated responsible party \u2014 creating gaps in professional accountability on public infrastructure.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public safety on a heavily used bridge; structural conditions that may be invisible to any single narrowly scoped engineer; potential liability for VWX, Engineer A, and the public agency if gaps in scope lead to undetected hazards; the integrity of the overall inspection process.",
  "proeth:description": "VWX Architects and Engineers deliberately retained Engineer A as a subconsultant with a narrowly defined scope limited exclusively to identifying pavement damage on the bridge, excluding structural or wall assessment.",
  "proeth:foreseenUnintendedEffects": [
    "Narrow scope may prevent subconsultant from formally reporting safety conditions observed outside that scope",
    "Scope limitation could create ambiguity about subconsultant\u0027s reporting obligations if broader hazards are encountered"
  ],
  "proeth:fulfillsObligation": [
    "Contractual duty to define scope of services clearly",
    "Professional obligation to engage competent specialists for specific tasks"
  ],
  "proeth:guidedByPrinciple": [
    "Scope management and contractual clarity",
    "Engagement of competent professionals for defined tasks"
  ],
  "proeth:hasAgent": "VWX Architects and Engineers (Prime Consultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Operational scope management vs. public safety reporting latitude",
    "proeth:resolutionReasoning": "VWX prioritized clear scope definition and operational efficiency, without building in explicit protocols for subconsultant safety observations beyond the contracted scope"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Obtain specialized pavement inspection services from a qualified subconsultant within a defined and manageable scope of work",
  "proeth:requiresCapability": [
    "Project management and subconsultant coordination",
    "Scope of work drafting",
    "Assessment of appropriate specialist engagement"
  ],
  "proeth:temporalMarker": "Prior to scheduled overhaul commencement",
  "proeth:violatesObligation": [
    "Potential failure to anticipate and address how out-of-scope safety observations by subconsultant would be handled",
    "Obligation to structure subconsultant agreements in ways that do not inadvertently suppress public safety reporting"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Retain Engineer A as Subconsultant"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Action_Document_Out-of-Scope_Defect_in_Field_Notes",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Choose not to document the observation at all, treating it as entirely outside his scope and professional responsibility.",
    "Document the observation formally in a written memorandum to VWX at the time of discovery, rather than only in personal field notes.",
    "Document the observation in field notes and simultaneously flag it in writing to VWX as requiring urgent attention before proceeding further with the inspection."
  ],
  "proeth-scenario:characterMotivation": "Engineer A\u0027s professional training and ethical instincts compelled him to document what he observed \u2014 a potentially dangerous pre-existing condition near a fatal accident site \u2014 even though it fell outside his contracted scope. Documenting in field notes allowed him to preserve the observation without immediately escalating beyond his authority, reflecting a cautious middle-ground professional judgment.",
  "proeth-scenario:consequencesIfAlternative": [
    "Failing to document would eliminate any professional record of the observation, exposing Engineer A to greater ethical and legal risk if the defect is later confirmed as a contributing cause of Officer B\u0027s death, and would represent a clear failure of professional duty.",
    "A formal written memorandum to VWX would have created a more robust paper trail, put VWX on formal written notice of the condition, and made it harder for the public agency to later instruct omission without that instruction itself being formally documented.",
    "Flagging it urgently in writing would have accelerated the escalation process and potentially prompted VWX or the public agency to commission an immediate structural review, though it may also have triggered earlier pressure to suppress the information."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that professional observation and documentation are baseline ethical duties that persist regardless of contractual scope limitations \u2014 field notes represent the minimum threshold of professional integrity \u2014 while also raising the question of whether documentation alone is sufficient when public safety may be implicated.",
  "proeth-scenario:ethicalTension": "Fidelity to contracted scope and client expectations vs. the engineer\u0027s broader duty to public safety and professional integrity; the tension between acting conservatively within defined boundaries and exercising independent professional judgment when public welfare may be at stake.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Accuracy of the engineering record; Engineer A\u0027s professional credibility and liability exposure; the possibility that the observation, if left undocumented, could be lost entirely; the integrity of any future investigation into Officer B\u0027s death.",
  "proeth:description": "Engineer A made a deliberate professional decision to note an apparent pre-existing defective wall condition \u2014 observed during the inspection but outside his contracted scope \u2014 in his engineering field notes, including his surmise that it may have contributed to the fatal wall failure.",
  "proeth:foreseenUnintendedEffects": [
    "Field notes could become subject to legal discovery in proceedings related to Officer B\u0027s death",
    "Documentation of speculative observations could expose Engineer A or his client to liability",
    "Retaining the information could create future pressure to act on or disclose it"
  ],
  "proeth:fulfillsObligation": [
    "Professional obligation to maintain accurate and complete engineering field notes",
    "Obligation not to alter or suppress professional observations made during the course of work",
    "Duty to preserve information that may bear on public health and safety"
  ],
  "proeth:guidedByPrinciple": [
    "Integrity and honesty in professional documentation",
    "Paramount obligation to public health and safety",
    "Professional responsibility to record observations accurately"
  ],
  "proeth:hasAgent": "Engineer A (Civil Engineer, Subconsultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Scope adherence and professional caution vs. honest documentation of safety-relevant observations",
    "proeth:resolutionReasoning": "Engineer A resolved the tension by documenting the observation in field notes \u2014 a private professional record \u2014 rather than in a formal report, balancing honesty with appropriate caution about speculative conclusions outside his expertise"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Create a contemporaneous professional record of an observed condition that may be relevant to public safety and the prior fatal accident, preserving the information for potential future reference",
  "proeth:requiresCapability": [
    "Professional observation and field documentation skills",
    "Judgment to recognize potentially safety-relevant conditions",
    "Understanding of limits of own expertise"
  ],
  "proeth:temporalMarker": "During bridge inspection",
  "proeth:withinCompetence": true,
  "rdfs:label": "Document Out-of-Scope Defect in Field Notes"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Action_Verbally_Report_Defect_to_Client",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Report the observation verbally and simultaneously follow up in writing (email or formal letter) to VWX to create a documented record of the disclosure.",
    "Report directly to the public agency rather than routing through VWX, given the severity of the potential public safety implication and the connection to a fatality.",
    "Decline to report verbally and instead prepare a formal written supplemental report to VWX flagging the out-of-scope observation as a matter requiring immediate client decision."
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognized that silence in the face of a potentially safety-critical observation \u2014 particularly one connected to a recent fatality \u2014 was professionally and ethically untenable. Verbal reporting to his client represented an attempt to fulfill his duty of care while respecting the chain of command and his contractual relationship with VWX.",
  "proeth-scenario:consequencesIfAlternative": [
    "A written follow-up would have created an unambiguous record that Engineer A fulfilled his reporting duty, protecting him professionally and making any subsequent instruction to omit the information a documented, traceable directive rather than an informal verbal instruction.",
    "Direct reporting to the public agency would have bypassed the client chain but might have been seen as a breach of contractual protocol; however, it would have ensured the information reached the party with ultimate authority and responsibility for the bridge, and may have been ethically required given the fatality context.",
    "A formal written supplemental report would have forced VWX to respond in writing, creating accountability at each level of the chain and making it significantly harder to instruct omission without that instruction being formally recorded."
  ],
  "proeth-scenario:decisionSignificance": "Highlights the critical inadequacy of verbal-only reporting chains for safety-critical information in engineering contexts \u2014 verbal reports are unverifiable, easily lost, and provide no accountability trail \u2014 and raises the question of what constitutes \u0027sufficient\u0027 reporting when a death may be involved.",
  "proeth-scenario:ethicalTension": "Duty to report safety-relevant information vs. deference to contractual hierarchy and client authority; the adequacy of informal verbal communication vs. the need for formal, documented reporting when public safety and a fatality investigation are involved; timeliness of disclosure vs. risk of overstepping professional boundaries.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Whether the safety-critical information actually reaches decision-makers with authority to act; the risk that verbal communication is misrepresented, forgotten, or deliberately ignored at any point in the chain; Engineer A\u0027s professional liability if the verbal report is later denied; the public agency\u0027s ability to respond appropriately to a potential ongoing safety hazard.",
  "proeth:description": "Engineer A made a deliberate decision to verbally report the observed pre-existing defective wall condition and his surmise about its potential role in the fatal accident to his client, VWX, rather than remaining silent or waiting for formal reporting channels.",
  "proeth:foreseenUnintendedEffects": [
    "Verbal reporting without written follow-up may limit the enforceability or traceability of the communication",
    "Client may choose to suppress or not act on the information",
    "Verbal report may be mischaracterized or lost without a written record"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to hold paramount public health and safety by surfacing potentially relevant hazard information",
    "Duty of candor and transparency with client regarding professionally observed conditions",
    "Obligation to bring safety-relevant information to the attention of those with authority and expertise to act"
  ],
  "proeth:guidedByPrinciple": [
    "Paramount obligation to public health and safety",
    "Honesty and transparency with clients",
    "Appropriate escalation within professional hierarchy"
  ],
  "proeth:hasAgent": "Engineer A (Civil Engineer, Subconsultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Scope adherence and client deference vs. proactive public safety disclosure",
    "proeth:resolutionReasoning": "Engineer A chose verbal reporting to the client as a proportionate response \u2014 sufficient to surface the concern to those with authority and broader context, without formally overstepping his scope or making unverified written claims"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Ensure that the prime consultant was made aware of a potentially safety-relevant condition observed during the inspection, enabling the client chain to evaluate and respond appropriately given their broader project context and expertise",
  "proeth:requiresCapability": [
    "Professional judgment about when to escalate observations beyond contracted scope",
    "Communication skills to convey technical observations and their limitations clearly",
    "Understanding of professional hierarchy and reporting responsibilities"
  ],
  "proeth:temporalMarker": "During or immediately following bridge inspection",
  "proeth:violatesObligation": [
    "Arguably, failure to follow up verbal report in writing reduced the enforceability and traceability of the disclosure"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Verbally Report Defect to Client"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Action_Comply_with_Instruction_to_Omit_from_Final_Report",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Refuse to comply with the omission instruction and insist that the observation be included in the final report, even if flagged as outside primary scope, citing professional ethical obligations.",
    "Comply with the omission from the final report but simultaneously notify the public agency directly in writing that the observation exists, ensuring the information is formally on record with the party bearing ultimate responsibility.",
    "Withdraw from the engagement rather than comply with an instruction perceived as requiring suppression of safety-critical information, and document the reason for withdrawal."
  ],
  "proeth-scenario:characterMotivation": "Engineer A faced direct instruction from his client (VWX, relaying the public agency\u0027s directive) to omit the out-of-scope observation from his final report. He complied, likely reasoning that the observation was speculative, that he had already verbally reported it through the chain, that it fell outside his contracted scope, and that defying a client directive on a public agency project carried significant professional and contractual risk.",
  "proeth-scenario:consequencesIfAlternative": [
    "Refusing to comply would have upheld Engineer A\u0027s ethical duty to public safety and created a formal record of the observation, but risked termination of the contract, damage to the professional relationship with VWX, and potential blacklisting from future public agency work \u2014 illustrating the real professional costs of ethical courage.",
    "Complying with omission from the report while separately notifying the public agency in writing would have represented a pragmatic middle path \u2014 honoring the client\u0027s report format directive while ensuring the information was not truly suppressed \u2014 though it may have been perceived as insubordinate and would have required significant professional courage.",
    "Withdrawal would have been the most dramatic form of ethical protest and would have protected Engineer A from complicity in the omission, but would have left the project without his expertise and potentially delayed the overhaul, while also raising questions about whether withdrawal alone fulfills the duty to ensure safety information reaches appropriate authorities."
  ],
  "proeth-scenario:decisionSignificance": "This is the ethical crux of the case \u2014 the point at which Engineer A\u0027s compliance most directly tests the limits of client deference in engineering ethics. It illustrates that the duty to hold public safety paramount can, in some circumstances, override client instructions, and that \u0027I was told to omit it\u0027 is not always a sufficient ethical defense, particularly when a death is involved.",
  "proeth-scenario:ethicalTension": "Obligation to follow lawful client directives and respect contractual scope vs. the engineer\u0027s independent duty to public safety under NSPE codes of ethics; the risk that compliance with the omission instruction makes Engineer A complicit in suppressing potentially safety-critical information connected to a fatality; deference to institutional authority vs. exercise of independent professional judgment.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s professional integrity and license; the public\u0027s right to safety-relevant information about infrastructure connected to a fatality; the risk that omission from the final report effectively buries the observation; potential civil and criminal liability for Engineer A, VWX, and the public agency if the defect is later confirmed as a contributing cause of the accident; the precedent set for how engineers respond to client pressure to suppress safety observations.",
  "proeth:description": "After being instructed by VWX (relaying the public agency\u0027s directive) not to include the out-of-scope wall condition information in his final report, Engineer A deliberately chose to comply with that instruction and omit the information from the final report.",
  "proeth:foreseenUnintendedEffects": [
    "Omission from the final report reduces the formal evidentiary record of the observed defect",
    "Reliance on the client chain to act on the verbally reported information may prove misplaced if no corrective action is taken",
    "Omission could later be characterized as suppression of safety-relevant information if the defect contributes to future harm"
  ],
  "proeth:fulfillsObligation": [
    "Fidelity to client instructions within reasonable professional bounds",
    "Professional responsibility to limit formal report content to areas of competence and verified findings",
    "Obligation not to include speculative, unverified conclusions in a formal engineering report"
  ],
  "proeth:guidedByPrinciple": [
    "Professional accuracy and responsibility in formal reporting",
    "Fidelity to client within ethical limits",
    "Avoidance of unverified speculation in formal engineering documents"
  ],
  "proeth:hasAgent": "Engineer A (Civil Engineer, Subconsultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client fidelity and professional reporting accuracy vs. formal documentation of a potentially safety-critical observation",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by accepting omission from the final report \u2014 judged appropriate given the speculative nature of the observation and his limited structural expertise \u2014 while preserving the information in field notes and relying on the verbal reporting chain to trigger corrective action"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Comply with client direction to limit the final report to contracted scope, avoiding inclusion of speculative, unverified structural observations outside his area of expertise, while preserving the information in field notes",
  "proeth:requiresCapability": [
    "Judgment about appropriate content boundaries for formal engineering reports",
    "Understanding of the distinction between field notes and formal deliverables",
    "Assessment of when client compliance crosses into ethical violation"
  ],
  "proeth:temporalMarker": "During final report preparation, after receiving client instruction",
  "proeth:violatesObligation": [
    "Arguably, omission from the formal record weakens the enforceability of the safety concern and reduces accountability for follow-up action",
    "Ongoing obligation to ensure corrective action is taken was not yet discharged at this point"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Comply with Instruction to Omit from Final Report"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Action_Retain_Observation_in_Field_Notes_Only",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Provide copies of the relevant field notes to VWX and the public agency as a formal supplement to the final report, ensuring the observation is in the possession of responsible parties even if excluded from the main deliverable.",
    "Retain the field notes and simultaneously notify Engineer A\u0027s professional liability insurer and legal counsel of the situation, seeking guidance on further disclosure obligations.",
    "Destroy or expunge the field note entries related to the out-of-scope observation to avoid any appearance of having identified a defect that was then suppressed \u2014 a clearly unethical choice that nevertheless represents a realistic temptation."
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to preserve a professional record of his observation \u2014 protecting himself against future claims that he had seen and said nothing \u2014 while simultaneously complying with the client\u0027s directive to exclude the information from the formal deliverable. Retaining the field notes represented a minimal act of professional self-preservation and integrity within the constraints imposed on him.",
  "proeth-scenario:consequencesIfAlternative": [
    "Providing copies of field notes to VWX and the public agency as a supplement would have ensured the information was formally in the hands of responsible parties, creating accountability without technically violating the report omission directive \u2014 a stronger ethical posture than retention alone.",
    "Consulting legal counsel and the insurer would have provided Engineer A with professional guidance on his disclosure obligations, potentially identifying a duty to report to external authorities (such as the investigating police department or transportation safety board) that he had not considered.",
    "Destroying the field note entries would have been a serious ethical and potentially criminal violation \u2014 obstruction of a potential fatality investigation \u2014 illustrating the floor of professional conduct and why retention, however passive, is ethically superior to destruction."
  ],
  "proeth-scenario:decisionSignificance": "Raises important questions about the legal and ethical status of engineering field notes as professional records \u2014 their discoverability in litigation, their role in professional accountability, and whether an engineer\u0027s duty to public safety is fulfilled by documentation alone when no active disclosure to responsible authorities occurs.",
  "proeth-scenario:ethicalTension": "The value of preserving an accurate professional record vs. the question of whether retention in field notes alone is ethically sufficient when the observation may be relevant to a fatality investigation; the tension between passive preservation (keeping notes) and active disclosure (reporting to authorities); whether field note retention constitutes meaningful fulfillment of a safety duty or merely symbolic compliance.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "The long-term accessibility and integrity of the safety observation; Engineer A\u0027s professional protection if the defect is later litigated; the risk that field notes, as private documents, may never reach the parties who need them; the adequacy of passive record-keeping as an ethical response to a potential public safety hazard.",
  "proeth:description": "Engineer A deliberately chose to retain the defective wall condition observation exclusively in his engineering field notes rather than including it in the final report or any other formal document, preserving the information for potential future reference while complying with the client\u0027s directive.",
  "proeth:foreseenUnintendedEffects": [
    "Field notes may be discoverable in litigation related to Officer B\u0027s death",
    "Retention in field notes alone may be insufficient to prompt corrective action if the client chain does not follow through",
    "The distinction between field notes and formal report may not be understood or respected by all parties"
  ],
  "proeth:fulfillsObligation": [
    "Professional obligation to maintain accurate and unaltered engineering field notes",
    "Integrity in professional documentation \u2014 not destroying or altering records of professional observations",
    "Preservation of information that may be relevant to public safety and legal accountability"
  ],
  "proeth:guidedByPrinciple": [
    "Integrity and honesty in professional records",
    "Obligation not to alter field notes under any circumstances",
    "Preservation of professional documentation for accountability"
  ],
  "proeth:hasAgent": "Engineer A (Civil Engineer, Subconsultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client compliance vs. integrity of professional documentation record",
    "proeth:resolutionReasoning": "Engineer A treated the field note as a non-negotiable professional record that could not be altered regardless of client instruction, while accepting that the formal report could legitimately be scoped to contracted deliverables"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Preserve an accurate professional record of the observed condition for potential future reference \u2014 including legal proceedings \u2014 while respecting the client\u0027s instruction to exclude it from the formal report",
  "proeth:requiresCapability": [
    "Understanding of the professional and legal status of engineering field notes",
    "Judgment about the distinction between field documentation and formal deliverables",
    "Commitment to documentation integrity under client pressure"
  ],
  "proeth:temporalMarker": "During and after final report preparation",
  "proeth:withinCompetence": true,
  "rdfs:label": "Retain Observation in Field Notes Only"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Action_Decline_to_Report_to_External_Authorities",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Report the observation directly to the relevant public authority (e.g., state transportation department, law enforcement investigating Officer B\u0027s death, or a transportation safety board), citing the public safety exception to client confidentiality under NSPE ethics codes.",
    "Consult the NSPE ethics hotline or a professional ethics board for guidance before deciding whether to report externally, using the available professional support infrastructure rather than making the decision in isolation.",
    "Report the observation to the media or a public interest organization as a last resort if internal and regulatory channels are unavailable or unresponsive, accepting the significant professional risk of whistleblowing in exchange for ensuring public awareness of a potential ongoing hazard."
  ],
  "proeth-scenario:characterMotivation": "Engineer A concluded \u2014 based on the speculative nature of his observation, his limited scope of engagement, and the fact that he had verbally reported through the client chain \u2014 that he had discharged his professional duty sufficiently and that further unilateral disclosure to external authorities was not warranted. He may also have been motivated by a desire to avoid professional conflict, contractual breach claims, and the reputational risks of going outside the client relationship.",
  "proeth-scenario:consequencesIfAlternative": [
    "Direct external reporting would have fulfilled the strongest interpretation of the engineer\u0027s public safety duty and ensured the information reached parties with investigative authority, but would have risked breach of contract claims from VWX, damage to the professional relationship, and potential blacklisting \u2014 while also potentially protecting Engineer A from future liability by demonstrating he took all reasonable steps to disclose.",
    "Consulting the NSPE ethics board or legal counsel would have provided structured professional guidance and potentially identified a clear ethical path, while also creating a record that Engineer A sought expert advice \u2014 a defensible, professionally responsible approach that many engineers in similar situations overlook.",
    "Media or public interest disclosure would represent the most extreme form of whistleblowing, likely only appropriate if all other channels had been exhausted or were clearly compromised; it would carry the highest professional risk but also the highest potential for public benefit, and raises important questions about the role of engineers as public safety advocates beyond their contractual roles."
  ],
  "proeth-scenario:decisionSignificance": "Represents the ultimate ethical test of the case \u2014 whether an engineer\u0027s duty to public safety, particularly in the context of a fatality, requires disclosure to external authorities when internal reporting channels have been blocked or rendered ineffective. This action directly engages NSPE Code Section III.2 and the comparison to Case No. 89-7, and is the central teaching moment about the limits of client deference in public safety engineering.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to hold public safety paramount (which may require disclosure beyond the client chain) vs. deference to client authority, contractual obligations, and the judgment that verbal reporting was sufficient; the tension between the speculative nature of the observation (which counsels caution) and the severity of the potential consequence (a fatality and ongoing public safety risk, which counsels action); individual professional courage vs. institutional compliance.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "The public\u0027s ongoing exposure to a potentially defective bridge wall; the integrity of the investigation into Officer B\u0027s death; Engineer A\u0027s long-term professional and legal liability if the defect is later confirmed as a contributing cause; the precedent set for how engineers navigate the conflict between client authority and public safety duty; the adequacy of the NSPE ethical framework for resolving such conflicts in practice.",
  "proeth:description": "Engineer A made a deliberate decision not to report the observed defective wall condition or his surmise about its role in the fatal accident to any public authority or agency beyond his immediate client chain, accepting that the verbal reporting chain was sufficient under the circumstances.",
  "proeth:foreseenUnintendedEffects": [
    "If the public agency does not take corrective action, the defective condition may persist and cause future harm",
    "Failure to independently report may be viewed as complicity in suppression if the defect is later confirmed as causal in Officer B\u0027s death",
    "Engineer A\u0027s ongoing obligation to follow through on corrective action was not yet discharged"
  ],
  "proeth:fulfillsObligation": [
    "Reasonable deference to the prime consultant and public agency who have broader project authority and context",
    "Avoidance of premature escalation based on unverified, speculative observations",
    "Fidelity to client relationship within ethical limits"
  ],
  "proeth:guidedByPrinciple": [
    "Proportionality in professional response to uncertain safety observations",
    "Deference to those with broader authority and expertise when observation is speculative",
    "Paramount obligation to public health and safety as an ongoing, not one-time, duty"
  ],
  "proeth:hasAgent": "Engineer A (Civil Engineer, Subconsultant)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Proactive public safety reporting vs. proportionate professional deference to client chain and avoidance of overreaction",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by accepting that verbal reporting through the client chain to the public agency was sufficient for the moment, given the speculative nature of the observation \u2014 but this decision carries a residual obligation to follow through if corrective action is not taken, as noted in the Discussion"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Defer to the client chain \u2014 which had already verbally communicated the information to the public agency \u2014 rather than independently escalating a speculative, unverified observation to external authorities, thereby avoiding overreaction and protecting the professional reputations of the client and public agency",
  "proeth:requiresCapability": [
    "Judgment about when professional observations rise to the level requiring independent external reporting",
    "Assessment of the sufficiency of existing reporting channels",
    "Understanding of the limits of one\u0027s own expertise in evaluating a potential hazard"
  ],
  "proeth:temporalMarker": "After final report submission and post-inspection",
  "proeth:violatesObligation": [
    "Ongoing obligation to follow through and ensure corrective action is actually taken \u2014 not yet discharged",
    "Arguably, paramount duty to public health and safety may require independent reporting if client chain fails to act",
    "Obligation to consider alternatives if public agency does not take corrective action (per Discussion)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Decline to Report to External Authorities"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Event_Information_Confined_to_Field_Notes",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is retaining information only in private field notes ethically equivalent to reporting it? What is the practical difference for public safety?",
    "If the defect later causes another accident, what is Engineer A\u0027s moral and legal exposure given that he documented but did not formally report?",
    "What does this outcome reveal about the adequacy of relying on client chains of command to protect public safety information?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Unease or moral residue for Engineer A\u2014the information exists in his notes but not in the official record; possible relief at having avoided conflict with clients; potential ongoing anxiety about whether the defect poses continuing risk; institutional actors may feel the matter is closed",
  "proeth-scenario:ethicalImplications": "Reveals the gap between private documentation and public accountability; raises questions about whether partial compliance with professional obligations (documenting but not reporting) is ethically sufficient; highlights how institutional suppression of safety information can create ongoing public risk while appearing procedurally compliant; implicates the long-term consequences of prioritizing professional relationships over public safety duty",
  "proeth-scenario:learningMoment": "Demonstrates the real-world consequence of compliance with suppression instructions: safety information disappears from institutional record. Students should understand that private documentation, while valuable for personal protection, does not fulfill the public safety reporting obligations of a licensed engineer when the information concerns a potential hazard linked to a fatality.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Holds private documentation that may become significant in future legal proceedings; his professional integrity is preserved only partially\u2014he documented but did not formally report",
    "future_engineers": "Will not have access to the observation in official project records, potentially missing a safety-relevant pattern",
    "general_public": "If defect is real and ongoing, continues to use a potentially unsafe bridge without knowledge of the risk",
    "officer_bs_family": "Denied access to potentially relevant information about the cause of the fatal accident through official channels",
    "public_agency": "Has successfully contained the information institutionally, but at significant ethical and potential legal cost"
  },
  "proeth:activatesConstraint": [
    "Information_Accessibility_Constraint",
    "Public_Record_Integrity_Constraint",
    "Ongoing_Safety_Risk_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/100#Action_Comply_with_Instruction_to_Omit_from_Final_Report",
  "proeth:causesStateChange": "The defect observation is effectively removed from institutional memory and official record; the public agency, future engineers, and the public have no official access to the information; Engineer A\u0027s field notes represent the only surviving documentation; the situation reaches a state of enforced institutional silence",
  "proeth:description": "As a result of Engineer A\u0027s compliance with the suppression instruction, the defect observation exists only in his private field notes and is absent from any official report or external communication. This creates a state where safety-relevant information is institutionally invisible.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer A complies with suppression instruction; at time of final report submission",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Information Confined to Field Notes"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Event_Officer_B_Fatal_Crash",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the death of Officer B change the ethical weight of any subsequent decision by Engineer A to remain silent about the defect he observes? Why or why not?",
    "At what point does a known or suspected structural deficiency become a public safety emergency that overrides contractual scope limitations?",
    "Who bears moral and legal responsibility when a fatality may be linked to a pre-existing defect that was never formally reported?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Profound grief and shock for Officer B\u0027s family and colleagues; alarm among public agency officials regarding liability; urgency and professional gravity felt by engineering consultants called to inspect; public anxiety about bridge safety",
  "proeth-scenario:ethicalImplications": "Reveals the tension between contractual scope of work and the engineer\u0027s broader duty to protect public safety; raises questions about whether institutional inertia or scope limitations can ever ethically justify silence in the face of evidence linked to a fatality; foregrounds the irreversibility of harm when safety warnings are suppressed or delayed",
  "proeth-scenario:learningMoment": "A real-world fatality demonstrates the concrete, irreversible consequences of unaddressed structural deficiencies. Students should recognize that engineering decisions\u2014or failures to act\u2014can have life-or-death consequences, and that a fatality creates urgent professional and ethical obligations for engineers who subsequently encounter related evidence.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Placed in professional situation requiring observation and judgment about a safety-critical condition",
    "general_public": "Continued use of potentially unsafe bridge; safety risk unresolved at time of crash",
    "officer_b": "Fatal outcome; loss of life",
    "officer_bs_family": "Irreversible personal loss; potential wrongful death legal action",
    "public_agency": "Exposed to legal liability; reputational damage; obligation to investigate and respond",
    "vwx_architects_engineers": "Scope of engagement implicitly expanded; potential liability exposure"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Bridge_Integrity_Investigation_Required",
    "Incident_Reporting_Obligation"
  ],
  "proeth:causesStateChange": "Bridge becomes subject to mandatory inspection; public safety emergency declared; legal and investigative processes initiated; Officer B\u0027s death triggers institutional response from public agency and engineering consultants",
  "proeth:createsObligation": [
    "Conduct_Bridge_Inspection",
    "Investigate_Cause_of_Wall_Failure",
    "Notify_Relevant_Authorities",
    "Assess_Bridge_Safety_for_Continued_Use"
  ],
  "proeth:description": "Police Officer B dies when his patrol car crashes through a bridge wall and falls into the river below. This fatal accident occurs three months before the scheduled bridge overhaul begins.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Three months before scheduled overhaul",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Officer B Fatal Crash"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Event_Bridge_Inspection_Initiated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the fact that the inspection was triggered by a fatality impose any special professional obligations on Engineer A beyond his contracted scope?",
    "How should an engineer mentally and professionally prepare when conducting an inspection in the aftermath of a fatal accident?",
    "What documentation standards should apply when an inspection is conducted in a post-accident context?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Heightened professional alertness for Engineer A given the fatal context; solemnity and urgency felt by all inspection participants; public agency officials anxious about what the inspection will reveal",
  "proeth-scenario:ethicalImplications": "Highlights how the context of a fatal accident elevates the moral stakes of professional observation and reporting; raises questions about whether scope of work can ethically constrain what an engineer chooses to notice or document when life-safety evidence is present",
  "proeth-scenario:learningMoment": "Illustrates how a fatality triggers mandatory professional engagement and how an engineer\u0027s routine presence on a project can suddenly acquire heightened ethical significance. Students should understand that professional obligations do not pause at scope boundaries when safety evidence is encountered.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Placed in direct observational contact with potentially safety-critical evidence; professional obligations activated",
    "general_public": "Inspection represents the institutional response meant to protect ongoing public safety",
    "public_agency": "Gains access to professional assessment of bridge condition post-accident",
    "vwx_architects_engineers": "Prime consultant\u0027s subconsultant is now embedded in a safety-critical investigation"
  },
  "proeth:activatesConstraint": [
    "Structural_Integrity_Assessment_Constraint",
    "Engineer_Observation_Duty",
    "Professional_Competence_Constraint"
  ],
  "proeth:causesStateChange": "Engineer A is physically present at the bridge site and in a position to observe conditions; professional duty to observe and report is activated; the inspection context places Engineer A in proximity to the pre-existing defective condition",
  "proeth:createsObligation": [
    "Observe_and_Document_Findings",
    "Report_Safety-Relevant_Observations",
    "Exercise_Professional_Judgment_on_Findings"
  ],
  "proeth:description": "Following Officer B\u0027s fatal crash, a bridge inspection is conducted, during which Engineer A is present and examines the structure. This inspection is the direct consequence of the accident and sets the stage for Engineer A\u0027s discovery.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Shortly after Officer B\u0027s death, prior to scheduled overhaul",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Bridge Inspection Initiated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Event_Pre-existing_Defect_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the speculative or uncertain nature of Engineer A\u0027s observation reduce his ethical obligation to report it, or does it merely change how he should frame the report?",
    "At what threshold of certainty should an engineer feel obligated to report a potential safety defect to authorities beyond the client chain?",
    "How does the fact that this observation may be causally linked to a death\u2014rather than a hypothetical future risk\u2014change the ethical calculus?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Profound professional unease for Engineer A\u2014awareness that he may hold evidence relevant to a man\u0027s death; moral weight of the discovery; potential conflict between professional loyalty to client and duty to public; anxiety about what reporting or not reporting will mean for his career",
  "proeth-scenario:ethicalImplications": "Exposes the core tension of the case: contractual scope of work versus the engineer\u0027s fundamental duty to protect public safety and human life; raises questions about epistemic standards for safety reporting (how certain must an engineer be before reporting?); reveals how institutional hierarchies can create pressure to suppress safety-relevant information; implicates the ethics of professional loyalty when it conflicts with public welfare",
  "proeth-scenario:learningMoment": "This is the pivotal moment of the case. Students should understand that an engineer\u0027s duty to public safety is not bounded by contractual scope when safety-critical evidence is encountered. The speculative nature of the observation does not eliminate the obligation to report\u2014it shapes how the report should be framed (as a professional observation warranting further investigation, not a definitive finding).",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Becomes the central ethical actor; his subsequent choices will define his professional integrity and potential legal exposure",
    "general_public": "If defect poses ongoing risk and is suppressed, other bridge users remain endangered",
    "officer_bs_family": "The defect, if confirmed, may be causally linked to their loved one\u0027s death; their access to justice may depend on whether this information surfaces",
    "public_agency": "Discovery creates institutional liability exposure; agency\u0027s subsequent instruction to suppress information becomes ethically and legally fraught",
    "vwx_architects_engineers": "Prime consultant is now in the chain of a potential cover-up if information is suppressed"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Engineer_Duty_to_Report_Safety_Hazards",
    "Professional_Honesty_Constraint",
    "Documentation_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/100#Action_Document_Out-of-Scope_Defect_in_Field_Notes",
  "proeth:causesStateChange": "Engineer A transitions from routine inspection participant to holder of safety-critical information potentially linked to a fatality; the ethical and professional stakes of his subsequent decisions are fundamentally elevated; a new obligation chain is activated",
  "proeth:createsObligation": [
    "Document_Defect_Formally",
    "Report_Defect_to_Client",
    "Assess_Whether_Defect_Poses_Ongoing_Public_Risk",
    "Consider_Reporting_to_External_Authority_if_Client_Does_Not_Act",
    "Determine_Whether_Observation_Is_Sufficiently_Certain_to_Mandate_Action"
  ],
  "proeth:description": "During the post-accident bridge inspection, Engineer A notices an apparent pre-existing defective condition near the accident site and surmises it may have contributed to the wall failure that killed Officer B. This discovery is an observational outcome of the inspection.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During post-accident bridge inspection",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Pre-existing Defect Discovered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Event_Defect_Information_Relayed_Upward",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is verbal reporting through a client chain sufficient to discharge an engineer\u0027s safety reporting obligation, or does public safety require written, formal, or direct reporting to authorities?",
    "Once the public agency is informed of a potential safety defect, does Engineer A\u0027s ethical obligation end, or does it persist if the agency fails to act?",
    "How does the informal, verbal nature of this communication affect accountability if the defect later proves to have caused additional harm?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Temporary relief for Engineer A that information has been passed up the chain; growing institutional anxiety at the public agency level as liability implications become apparent; VWX caught in an uncomfortable intermediary position",
  "proeth-scenario:ethicalImplications": "Raises questions about the adequacy of informal communication channels for safety-critical information; highlights how institutional hierarchies can diffuse and ultimately suppress safety information while maintaining plausible deniability; reveals the tension between professional deference to client authority and independent duty to public safety",
  "proeth-scenario:learningMoment": "Illustrates that verbal reporting through a chain of command may be insufficient when public safety is at stake. Students should consider whether the adequacy of reporting depends on the reliability and accountability of the chain, and whether verbal-only communication provides sufficient protection for the public or for the reporting engineer.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Believes his reporting obligation has been partially fulfilled through the chain; may feel his hands are tied as a subconsultant",
    "officer_bs_family": "The information that might support their legal case has reached the agency but may be suppressed before it becomes part of any official record",
    "public_agency": "Now the informed decision-maker; their subsequent instruction to suppress the information becomes ethically and potentially legally indefensible",
    "vwx_architects_engineers": "Now complicit in whatever decision the agency makes; their relay of the information makes them part of the knowledge chain"
  },
  "proeth:activatesConstraint": [
    "Public_Agency_Decision_Authority_Constraint",
    "Institutional_Response_Obligation",
    "Informed_Client_Responsibility_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/100#Action_Verbally_Report_Defect_to_Client",
  "proeth:causesStateChange": "The public agency is now formally aware (verbally) of the potential defect; the locus of decision-making authority shifts to the agency; Engineer A\u0027s direct reporting obligation is partially discharged, though questions remain about adequacy of verbal-only reporting",
  "proeth:createsObligation": [
    "Public_Agency_Must_Decide_How_to_Respond",
    "VWX_Must_Follow_Agency_Instructions",
    "Engineer_A_Obligation_Partially_Discharged_Through_Chain"
  ],
  "proeth:description": "After Engineer A verbally reports the defect observation to his client (VWX), VWX verbally relays the information to the public agency. This creates a documented chain of verbal communication that the information reached the responsible authority.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Shortly after Engineer A\u0027s verbal report to VWX, during post-accident inspection period",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Defect Information Relayed Upward"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#Event_Suppression_Instruction_Issued",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Can a contractual scope limitation ever ethically justify an engineer\u0027s silence about a safety defect potentially linked to a fatality?",
    "What options does Engineer A have at this point, and what are the professional and personal consequences of each?",
    "Does the fact that the public agency\u2014the ultimate client\u2014is the source of the suppression instruction change Engineer A\u0027s ethical obligations compared to if the instruction came from VWX alone?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Significant professional distress for Engineer A\u2014caught between institutional authority and professional ethics; VWX uncomfortable as the relay of an ethically questionable instruction; public agency officials may feel relief at containing liability but are exposed to serious ethical and legal risk",
  "proeth-scenario:ethicalImplications": "Crystallizes the central ethical conflict of the case: institutional authority versus professional independence and public safety duty; raises questions about the limits of client deference in engineering ethics; implicates the ethics of using procedural/contractual arguments to suppress substantive safety information; highlights the vulnerability of subconsultants in multi-tiered consulting arrangements to unethical pressure from above",
  "proeth-scenario:learningMoment": "This is the second major turning point of the case. Students should understand that an institutional instruction to omit safety-relevant information does not relieve an engineer of professional and ethical obligations. Scope of work is a contractual concept, not an ethical one, and cannot override the engineer\u0027s duty to public safety.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Faces the defining ethical choice of the case; compliance risks professional integrity; resistance risks professional relationships and career",
    "general_public": "If the defect is real and ongoing, continued suppression leaves other bridge users at risk",
    "officer_bs_family": "The instruction, if followed, may prevent them from ever learning the full circumstances of their loved one\u0027s death",
    "public_agency": "Formally requests suppression of potentially safety-critical information linked to a fatality\u2014a decision with serious legal and ethical consequences",
    "vwx_architects_engineers": "Becomes a conduit for suppression; their professional reputation and legal exposure are implicated"
  },
  "proeth:activatesConstraint": [
    "Engineer_Independence_Constraint",
    "PublicSafety_Paramount_Constraint",
    "Professional_Honesty_Constraint",
    "Whistleblower_Consideration_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/100#Action_Verbally_Report_Defect_to_Client",
  "proeth:causesStateChange": "Engineer A is now under explicit institutional pressure to omit safety-relevant information from an official report; the ethical decision point is fully crystallized; the chain of command has formally aligned against disclosure; Engineer A\u0027s professional independence is directly challenged",
  "proeth:createsObligation": [
    "Engineer_A_Must_Decide_Whether_to_Comply_or_Resist",
    "Engineer_A_Must_Assess_Whether_Suppression_Violates_Professional_Code",
    "Engineer_A_Must_Consider_External_Reporting_Options"
  ],
  "proeth:description": "The public agency instructs VWX, who in turn instructs Engineer A, to exclude the defect observation from the final report on the grounds that it falls outside Engineer A\u0027s contracted scope of work. This creates a formal institutional directive to omit safety-relevant information.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After public agency receives verbal report of defect, prior to final report preparation",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Suppression Instruction Issued"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#CausalChain_738bb7e5",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "VWX Architects and Engineers deliberately retained Engineer A as a subconsultant with a narrowly defined scope, placing him in the position of conducting the post-accident bridge inspection during which the defect was observed",
  "proeth:causalSequence": [
    {
      "proeth:description": "VWX deliberately retains Engineer A with a narrowly defined scope for bridge-related work",
      "proeth:element": "Retain Engineer A as Subconsultant",
      "proeth:step": 1
    },
    {
      "proeth:description": "Officer B\u0027s patrol car crashes through the bridge wall, triggering a formal inspection",
      "proeth:element": "Officer B Fatal Crash",
      "proeth:step": 2
    },
    {
      "proeth:description": "Post-accident inspection is conducted with Engineer A present on site",
      "proeth:element": "Bridge Inspection Initiated",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A\u0027s professional competence leads him to notice the apparent pre-existing defective wall condition",
      "proeth:element": "Pre-existing Defect Discovered",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A exercises professional judgment to document the defect despite it falling outside his defined scope",
      "proeth:element": "Document Out-of-Scope Defect in Field Notes",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Retain Engineer A as Subconsultant",
  "proeth:counterfactual": "Without Engineer A\u0027s retention and presence at the inspection, the pre-existing defect may not have been identified by a less qualified observer, or may have been identified but handled differently by a different subconsultant",
  "proeth:effect": "Pre-existing Defect Discovered",
  "proeth:necessaryFactors": [
    "VWX\u0027s decision to retain Engineer A specifically",
    "Engineer A\u0027s presence at the post-accident bridge inspection",
    "Narrowly defined subconsultant scope that nonetheless placed Engineer A at the site"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "VWX Architects and Engineers",
  "proeth:sufficientFactors": [
    "Retention of Engineer A + his physical presence at inspection + his professional competence to identify structural defects"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#CausalChain_5267268b",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A made a deliberate professional decision to note an apparent pre-existing defective wall condition in his field notes, which formed the basis for his subsequent verbal report to VWX, who then relayed the information to the public agency",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A observes the apparent pre-existing defective wall condition during inspection",
      "proeth:element": "Pre-existing Defect Discovered",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A makes a deliberate professional decision to record the observation formally",
      "proeth:element": "Document Out-of-Scope Defect in Field Notes",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A verbally communicates the defect observation to VWX as his client contact",
      "proeth:element": "Verbally Report Defect to Client",
      "proeth:step": 3
    },
    {
      "proeth:description": "VWX verbally relays the defect information to the public agency",
      "proeth:element": "Defect Information Relayed Upward",
      "proeth:step": 4
    },
    {
      "proeth:description": "The public agency, now aware of the defect, instructs VWX to suppress it from the final report",
      "proeth:element": "Suppression Instruction Issued",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Document Out-of-Scope Defect in Field Notes",
  "proeth:counterfactual": "Had Engineer A not documented and verbally reported the defect, the information would not have reached VWX or the public agency, and the suppression instruction would never have been issued",
  "proeth:effect": "Defect Information Relayed Upward",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s professional recognition of the defect as significant",
    "His decision to formally document it in field notes",
    "His subsequent verbal report to VWX as his client"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Documentation in field notes + verbal report to VWX + VWX\u0027s decision to relay information upward to the public agency"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#CausalChain_69df970b",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The public agency instructs VWX, who in turn instructs Engineer A, to exclude the defect observation from the final report; after being instructed by VWX (relaying the public agency\u0027s directive) not to include the out-of-scope defect, Engineer A complied",
  "proeth:causalSequence": [
    {
      "proeth:description": "Public agency becomes aware of the pre-existing defect through VWX\u0027s relay of Engineer A\u0027s verbal report",
      "proeth:element": "Defect Information Relayed Upward",
      "proeth:step": 1
    },
    {
      "proeth:description": "Public agency directs VWX to instruct Engineer A to exclude the defect from the final report",
      "proeth:element": "Suppression Instruction Issued",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A, under client pressure relayed through VWX, omits the defect observation from the final report",
      "proeth:element": "Comply with Instruction to Omit from Final Report",
      "proeth:step": 3
    },
    {
      "proeth:description": "The defect observation survives only in Engineer A\u0027s field notes, inaccessible to the public or remediation authorities",
      "proeth:element": "Retain Observation in Field Notes Only",
      "proeth:step": 4
    },
    {
      "proeth:description": "The defect information is effectively suppressed from any actionable public safety channel",
      "proeth:element": "Information Confined to Field Notes",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Suppression Instruction Issued",
  "proeth:counterfactual": "Had the public agency not issued the suppression instruction, or had VWX refused to relay it, or had Engineer A refused to comply, the defect would likely have appeared in the final report and been subject to formal remediation processes",
  "proeth:effect": "Comply with Instruction to Omit from Final Report",
  "proeth:necessaryFactors": [
    "Public agency\u0027s issuance of the suppression directive",
    "VWX\u0027s decision to relay rather than refuse the instruction",
    "Engineer A\u0027s decision to comply rather than resist or escalate"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Public Agency (primary), VWX Architects and Engineers (secondary), Engineer A (tertiary)",
  "proeth:sufficientFactors": [
    "Suppression instruction from public agency + VWX\u0027s relay of instruction + Engineer A\u0027s compliance = omission of defect from final report"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#CausalChain_ae8583f2",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After complying with the suppression instruction and retaining the observation in field notes only, Engineer A made a deliberate decision not to report the observed defective wall condition or his suppression concerns to external authorities",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A omits the defect from the final report under client pressure",
      "proeth:element": "Comply with Instruction to Omit from Final Report",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A retains the defect observation exclusively in personal field notes",
      "proeth:element": "Retain Observation in Field Notes Only",
      "proeth:step": 2
    },
    {
      "proeth:description": "The defect information exists only in a non-public, non-actionable format",
      "proeth:element": "Information Confined to Field Notes",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A makes a deliberate decision not to escalate to external regulatory or professional bodies",
      "proeth:element": "Decline to Report to External Authorities",
      "proeth:step": 4
    },
    {
      "proeth:description": "The defective wall condition remains unaddressed, posing ongoing risk to public safety at the bridge",
      "proeth:element": "Continued Public Safety Risk",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Comply with Instruction to Omit from Final Report",
  "proeth:counterfactual": "Had Engineer A reported to external authorities (e.g., state engineering board, transportation safety authority), the defect would have entered formal remediation channels regardless of the public agency\u0027s suppression instruction",
  "proeth:effect": "Decline to Report to External Authorities",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s prior compliance with the suppression instruction, establishing a pattern of deference",
    "Engineer A\u0027s awareness that the defect was not being formally addressed",
    "Engineer A\u0027s deliberate choice not to escalate to external regulatory or professional bodies"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Compliance with suppression + retention of information in field notes only + decision not to escalate = complete suppression of safety-critical information from public channels"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/100#",
    "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/100#CausalChain_611d1496",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a result of Engineer A\u0027s compliance with the suppression instruction, the defect observation exists only in field notes; Engineer A deliberately chose to retain the defective wall condition observation exclusively in his field notes rather than escalating through formal reporting channels",
  "proeth:causalSequence": [
    {
      "proeth:description": "Public agency through VWX instructs Engineer A to exclude defect from final report",
      "proeth:element": "Suppression Instruction Issued",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A omits the defect observation from the formal final report",
      "proeth:element": "Comply with Instruction to Omit from Final Report",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A retains the observation in personal field notes as the sole surviving record",
      "proeth:element": "Retain Observation in Field Notes Only",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A does not escalate to external bodies, leaving field notes as the only record",
      "proeth:element": "Decline to Report to External Authorities",
      "proeth:step": 4
    },
    {
      "proeth:description": "Safety-critical defect information is effectively suppressed from all actionable public safety channels",
      "proeth:element": "Information Confined to Field Notes",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Retain Observation in Field Notes Only",
  "proeth:counterfactual": "Had Engineer A included the defect in the final report or reported to external authorities, the information would not have been confined to field notes and would have entered actionable safety channels",
  "proeth:effect": "Information Confined to Field Notes",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s compliance with the suppression instruction removing defect from final report",
    "Engineer A\u0027s decision to retain rather than destroy the field note record",
    "Engineer A\u0027s decision not to escalate the information to external authorities"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary compliance decision), Public Agency (suppression instruction originator), VWX (instruction relay and failure to protect Engineer A)",
  "proeth:sufficientFactors": [
    "Omission from final report + retention only in field notes + non-escalation = information effectively confined and inaccessible to public safety remediation"
  ],
  "proeth:withinAgentControl": true
}