{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Prepare_and_Seal_Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Include explicit contractual language specifying conditions under which the sealed plans may be used, modified, or transferred",
    "Seal only the final approved version and retain stricter version control documentation",
    "Decline to seal documents until a formal agreement about downstream use and modification rights is executed"
  ],
  "proeth-scenario:characterMotivation": "Engineer A was fulfilling a contracted professional obligation, applying technical expertise to deliver a complete subdivision plan set. Sealing the documents represented a good-faith certification of the work\u0027s accuracy, completeness, and compliance with applicable standards at the time of delivery.",
  "proeth-scenario:consequencesIfAlternative": [
    "Contractual protections could have limited Engineer B\u0027s ability to use the plans without notification, potentially triggering a required consultation clause and reducing downstream liability for Engineer A",
    "Tighter version control would create a clearer evidentiary record of what Engineer A certified, making unauthorized modifications more legally distinguishable from the original work",
    "Delaying sealing until use conditions were formalized might have slowed delivery but would have established a professional boundary that could have prevented the entire downstream ethical crisis"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that affixing a professional seal is not merely a procedural formality \u2014 it is a legally and ethically binding act of certification. Engineers must understand that a seal carries enduring professional accountability, even after project completion or client discharge.",
  "proeth-scenario:ethicalTension": "Professional pride and thoroughness in certification versus the foreseeable risk that sealed documents, once delivered, could be altered by others while retaining the original engineer\u0027s mark of authority. The seal is both a professional asset and a liability once it leaves the engineer\u0027s control.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Engineer A\u0027s professional reputation and license are permanently attached to 43 sheets of documents. Public safety depends on the integrity of those certifications. Any future alteration of sealed documents without proper re-sealing creates immediate liability and public risk.",
  "proeth:description": "Engineer A prepared a 43-sheet subdivision plan set (5-sheet grading plans and 38-sheet public improvement plans) and signed and sealed all sheets in both sets, including cover sheets. This constituted a professional certification of the work\u0027s accuracy and completeness.",
  "proeth:foreseenUnintendedEffects": [
    "Sealed documents would remain in circulation after professional relationship ended, potentially being modified by others while bearing Engineer A\u0027s seal"
  ],
  "proeth:fulfillsObligation": [
    "Professional competence in producing a complete plan set",
    "Proper use of professional seal to certify work Engineer A personally prepared",
    "Full delivery of contracted services"
  ],
  "proeth:guidedByPrinciple": [
    "Professional responsibility for certified work product",
    "Competence",
    "Public safety through proper engineering documentation"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer, original design engineer)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Deliver complete, professionally certified subdivision plans to satisfy the client\u0027s project requirements",
  "proeth:requiresCapability": [
    "Subdivision grading design",
    "Public improvement plan design",
    "Storm drain and utility engineering",
    "Professional plan production and certification"
  ],
  "proeth:temporalMarker": "Initial phase, prior to client discharge",
  "proeth:withinCompetence": true,
  "rdfs:label": "Prepare and Seal Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Surrender_Original_Drawings",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Transfer the drawings with a written cover letter explicitly stating that the sealed documents may not be modified or reused without Engineer A\u0027s written consent or proper re-engineering and re-sealing by a successor engineer",
    "Offer to provide unsealed or \u0027for reference only\u0027 stamped copies, retaining the sealed originals until a formal release agreement is signed",
    "Consult legal counsel before surrendering documents to clarify intellectual property rights and professional liability exposure"
  ],
  "proeth-scenario:characterMotivation": "Engineer A acted in good faith to comply with the client\u0027s legal right to possess the deliverables for which full fees had been paid. Retaining reproducibles reflected a prudent but ultimately insufficient precaution to preserve a record of the original work.",
  "proeth-scenario:consequencesIfAlternative": [
    "A written notice of conditions would have created a documented record of Engineer A\u0027s professional objection to unauthorized reuse, potentially shifting liability and alerting any successor engineer to their obligations",
    "Providing reference-only copies would have preserved Engineer A\u0027s control over the certified documents while still satisfying the client\u0027s practical need to proceed, significantly reducing the risk of seal misuse",
    "Legal consultation might have revealed that Engineer A retained intellectual property rights or professional standing to impose conditions, empowering a more protective transfer arrangement"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that engineers must think beyond the immediate transactional relationship when transferring sealed documents. The act of surrender is not ethically neutral \u2014 it can enable downstream harm if no conditions or safeguards accompany the transfer.",
  "proeth-scenario:ethicalTension": "Respect for client property rights and contractual obligations versus the professional duty to protect the integrity of sealed documents and the public interest. Handing over originals with intact seals creates foreseeable risk of misuse, yet withholding them may breach the client relationship.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Once original sealed drawings leave Engineer A\u0027s custody, Engineer A loses all practical ability to monitor, control, or consent to how those documents are used. The reproducibles retained provide a record but offer no protection against misuse of the originals.",
  "proeth:description": "Upon the client\u0027s request following discharge, Engineer A complied and handed over the original drawings while retaining a set of reproducibles for his own records. This decision transferred physical custody of sealed documents to the client.",
  "proeth:foreseenUnintendedEffects": [
    "Originals bearing Engineer A\u0027s seal could be used, modified, or misrepresented by subsequent parties without Engineer A\u0027s knowledge or consent"
  ],
  "proeth:fulfillsObligation": [
    "Honoring client\u0027s property rights over paid work product",
    "Prudent record retention by keeping reproducibles"
  ],
  "proeth:guidedByPrinciple": [
    "Fidelity to client contractual obligations",
    "Professional record-keeping",
    "Transparency regarding limitations of reuse of sealed documents"
  ],
  "proeth:hasAgent": "Engineer A (Licensed Professional Engineer, discharged design engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client property rights vs. seal integrity protection",
    "proeth:resolutionReasoning": "Engineer A resolved in favor of client property rights, which is defensible, but the absence of any conditions or warnings about the sealed documents represents a missed opportunity to protect the integrity of the professional seal"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Honor the client\u0027s ownership rights over the paid-for work product and maintain a professional record copy via reproducibles",
  "proeth:requiresCapability": [
    "Understanding of client ownership rights",
    "Professional judgment about record retention",
    "Awareness of implications of sealed document transfer"
  ],
  "proeth:temporalMarker": "Post-discharge, immediately following client termination of Engineer A",
  "proeth:violatesObligation": [
    "Arguably could have included explicit terms or warnings regarding alteration of sealed documents before surrendering originals"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Surrender Original Drawings"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Accept_Engagement_Without_Notifying_Engineer_A",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Contact Engineer A before accepting the engagement to inform him of the client\u0027s request and discuss the nature of the redesign work",
    "Condition acceptance of the engagement on the client\u0027s consent to allow Engineer B to consult with Engineer A about the original design",
    "Decline the engagement if the client refused to permit any communication with Engineer A, recognizing the ethical risk of proceeding without that consultation"
  ],
  "proeth-scenario:characterMotivation": "Engineer B was motivated by professional opportunity and client service \u2014 accepting a new engagement is a routine business decision. There may also have been competitive incentive to avoid a potentially awkward or adversarial conversation with a predecessor engineer whose work was being superseded.",
  "proeth-scenario:consequencesIfAlternative": [
    "Notifying Engineer A would have fulfilled NSPE ethical obligations, potentially surfaced critical design context, and created an opportunity for Engineer A to formally address the status of his seal \u2014 preventing the entire downstream misattribution problem",
    "Making consultation a condition of engagement would have placed the ethical burden appropriately on the client and established Engineer B\u0027s professional integrity from the outset",
    "Declining the engagement would have been a principled stand that protected both engineers\u0027 professional standing and signaled to the client that proper engineering protocols are non-negotiable"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that the obligation to communicate with a predecessor engineer is not optional or situational \u2014 it is a baseline professional duty. Students learn that accepting an engagement without this step is itself an ethical violation, independent of what happens next.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to serve the client efficiently and without unnecessary delay conflicts directly with the NSPE ethical obligation to notify a predecessor engineer before beginning work on a project where that engineer\u0027s sealed documents will be used. Collegiality and professional protocol are sacrificed for expediency.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Failure to notify Engineer A denies him the opportunity to raise concerns, correct potential misunderstandings about the original design intent, or formally withdraw his seal. It also sets the tone for a pattern of professional discourtesy that compounds throughout the case.",
  "proeth:description": "Engineer B agreed to be retained by the client to review and redesign the project without notifying or consulting Engineer A, despite the fact that Engineer A\u0027s sealed work product would serve as the foundation for the redesign. No communication between the two engineers was initiated at any point.",
  "proeth:foreseenUnintendedEffects": [
    "Foregoing the technical context and explanations Engineer A could have provided about original design decisions, potentially limiting the quality and safety of the redesign"
  ],
  "proeth:fulfillsObligation": [
    "Responding to a legitimate client request for professional services",
    "Accepting an engagement within his professional scope"
  ],
  "proeth:guidedByPrinciple": [
    "Professional courtesy to fellow engineers",
    "Thorough understanding of prior design context before modification",
    "Public safety through informed redesign"
  ],
  "proeth:hasAgent": "Engineer B (Licensed Professional Engineer, successor design engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client service efficiency vs. professional courtesy and technical thoroughness",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of proceeding without consultation, which the Board found technically permissible but professionally suboptimal, noting that the purpose of Section III.8.a. is to give the original engineer an opportunity to provide technical context for the benefit of the reviewing engineer and ultimately the client"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Accept a legitimate professional engagement to review and redesign the subdivision project for the client",
  "proeth:requiresCapability": [
    "Subdivision plan review",
    "Grading and public improvement design",
    "Inter-engineer professional communication protocols"
  ],
  "proeth:temporalMarker": "Retention point, after client discharged Engineer A and before any redesign work began",
  "proeth:violatesObligation": [
    "NSPE Section III.8.a. \u2014 while the discharge of Engineer A technically satisfies the condition allowing review without notification, the spirit of the provision strongly favors consulting the original engineer; the Board noted it would have been \u0027wiser and more professional\u0027 to consult Engineer A"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accept Engagement Without Notifying Engineer A"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Modify_Grading_Plans_Without_Notation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Remove or void Engineer A\u0027s seal on all modified sheets, sign and seal each revised sheet personally, and annotate all changes with revision clouds and a revision log",
    "Prepare entirely new sheets for all modified elements, clearly labeled as Engineer B\u0027s work, with cross-references to superseded Engineer A sheets",
    "Refuse to proceed with modifications until a formal plan revision protocol was established that met state board of registration requirements"
  ],
  "proeth-scenario:characterMotivation": "Engineer B sought to efficiently complete the redesign task the client requested, likely viewing annotation of changes as an administrative burden rather than a professional obligation. Leaving Engineer A\u0027s seal intact may have been an oversight, a misunderstanding of protocol, or a deliberate choice to avoid the complexity of re-sealing.",
  "proeth-scenario:consequencesIfAlternative": [
    "Properly voiding and re-sealing would have created a legally and ethically accurate record, protected Engineer A from false attribution, and established Engineer B\u0027s full accountability for the modified work",
    "New sheets would have provided maximum clarity about design authorship and change history, supporting regulatory review and contractor understanding of what was revised",
    "Establishing a formal revision protocol would have slowed the project but ensured compliance with professional standards, protecting both engineers and the public"
  ],
  "proeth-scenario:decisionSignificance": "A core teaching moment about the inseparability of design authorship and professional sealing. Students learn that making significant changes to sealed plans without removing or superseding the original seal, and without signing and sealing the modified sheets, is a fundamental ethical and potentially legal violation.",
  "proeth-scenario:ethicalTension": "Efficiency and client service pressure conflict with the engineer\u0027s duty to ensure that sealed documents accurately represent who designed and certified each element. Leaving another engineer\u0027s seal on materially altered work creates a false public record and misattributes professional responsibility.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Public safety is directly at risk if grading changes \u2014 including raised pad elevations and rerouted streets \u2014 are not properly certified by an engineer who takes full responsibility for them. Regulatory authorities and contractors relying on the plans have no way to know who actually designed the modified elements.",
  "proeth:description": "Engineer B made significant changes to the grading plans \u2014 including deletion of one sheet, raising housing pad elevations, and rerouting streets \u2014 without annotating what changes were made, without signing any of the modified sheets, and while leaving Engineer A\u0027s seal and signature intact throughout.",
  "proeth:foreseenUnintendedEffects": [
    "Creating an undocumented hybrid document where it is impossible to distinguish Engineer A\u0027s original work from Engineer B\u0027s modifications",
    "Leaving Engineer A\u0027s seal on work that no longer reflects Engineer A\u0027s design",
    "Misleading future reviewers, contractors, and regulators about the authorship and certification status of the plans"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency and honesty in engineering documentation",
    "Public safety through clear identification of responsible engineer",
    "Non-deception in professional practice"
  ],
  "proeth:hasAgent": "Engineer B (Licensed Professional Engineer, successor design engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Efficiency of modification vs. integrity and transparency of engineering documentation",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of making changes without documentation, which the Board found to be a clear ethical violation under Section III.3.a., constituting deception regardless of whether it was intentional"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Implement design improvements to the grading plans as directed by the client\u0027s redesign requirements",
  "proeth:requiresCapability": [
    "Grading plan design",
    "Housing pad elevation engineering",
    "Street routing design",
    "Engineering drawing revision protocols"
  ],
  "proeth:temporalMarker": "During redesign phase, after accepting the engagement",
  "proeth:violatesObligation": [
    "NSPE Section III.3.a. \u2014 obligation not to engage in deceptive conduct; failure to note changes constitutes a form of deception",
    "NSPE Section III.9. \u2014 obligation to acknowledge responsibility for work; Engineer B failed to sign sheets he substantively modified",
    "Professional obligation to clearly identify authorship of engineering documents",
    "Obligation to protect the public meaning and integrity of a professional engineering seal"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Modify Grading Plans Without Notation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Redesign_Public_Improvements_Without_Attribution",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Sign and seal every modified sheet individually, with a revision block identifying the nature and date of each change, and void Engineer A\u0027s seal on those sheets",
    "Engage Engineer A to review the proposed changes and either co-certify the revised plans or formally release his seal from the affected sheets",
    "Advise the client that the scope of redesign required preparation of a substantially new plan set under Engineer B\u0027s sole authorship and certification"
  ],
  "proeth-scenario:characterMotivation": "Engineer B was executing the client\u0027s redesign directive across the full scope of public infrastructure, likely prioritizing technical problem-solving over documentation discipline. The scale of changes across 38 sheets may have made comprehensive annotation feel overwhelming, leading to rationalization that a single title sheet note would suffice.",
  "proeth-scenario:consequencesIfAlternative": [
    "Individual sheet certification would have created a complete and accurate professional record, protecting the public, both engineers, and regulatory agencies from confusion about design responsibility",
    "Engaging Engineer A would have honored professional collegiality, potentially improved design quality through knowledge transfer, and resolved the seal attribution problem collaboratively",
    "A new plan set would have been more resource-intensive but would have produced a clean, unambiguous professional record with no risk of misattribution or false certification"
  ],
  "proeth-scenario:decisionSignificance": "Reinforces that the magnitude of design changes amplifies rather than diminishes the obligation to properly document, attribute, and certify work. Students learn that systemic shortcuts across a large plan set constitute a systemic ethical failure, not merely isolated oversights.",
  "proeth-scenario:ethicalTension": "The desire to complete a large, complex redesign efficiently conflicts with the professional obligation to maintain accurate, attributable, and fully certified engineering documents. The greater the scale of changes, the greater the ethical obligation to document them \u2014 yet scale also creates the greatest temptation to cut corners.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Storm drain sizing, sewer design, and utility routing are life-safety and public health issues. Incorrect or uncertified changes to these systems could result in flooding, sewage failures, or utility conflicts during construction \u2014 all traceable back to a plan set that falsely appears to be certified by Engineer A.",
  "proeth:description": "Engineer B made major design changes to storm drains, pipe dimensions, sewers, and utilities in the 38-sheet public improvement plans without making any notation of the changes, without signing the plans, and while leaving Engineer A\u0027s seal and signature intact on all sheets.",
  "proeth:foreseenUnintendedEffects": [
    "Creating a fundamentally altered set of public improvement plans that still bear only Engineer A\u0027s seal, falsely implying Engineer A certified the new design",
    "Obscuring Engineer B\u0027s responsibility for major infrastructure decisions affecting public safety",
    "Preventing regulators, contractors, and the public from identifying the responsible engineer for the revised design"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty and transparency in professional documentation",
    "Public safety and welfare as paramount concern",
    "Engineer accountability for certified work product",
    "Non-deception in professional practice"
  ],
  "proeth:hasAgent": "Engineer B (Licensed Professional Engineer, successor design engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Reuse efficiency vs. full accountability for critical infrastructure design",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of making undocumented changes to public infrastructure plans while leaving another engineer\u0027s seal intact, which the Board found to be a serious ethical violation given the public safety implications and the requirements of Sections III.3.a. and III.9."
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Implement major infrastructure design changes to the public improvement plans to meet the client\u0027s redesign requirements",
  "proeth:requiresCapability": [
    "Storm drain design",
    "Pipe sizing and hydraulic engineering",
    "Sewer system design",
    "Utility engineering",
    "Public improvement plan production"
  ],
  "proeth:temporalMarker": "During redesign phase, concurrent with or following grading plan modifications",
  "proeth:violatesObligation": [
    "NSPE Section III.3.a. \u2014 deceptive conduct by leaving Engineer A\u0027s seal on fundamentally altered infrastructure designs",
    "NSPE Section III.9. \u2014 failure to acknowledge responsibility for the full design once fundamental changes were made that affected the entire project\u0027s integrity",
    "Public safety obligation to clearly identify the responsible engineer for critical infrastructure design",
    "Professional obligation to sign and seal work for which one is responsible"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Redesign Public Improvements Without Attribution"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Place_Vague_Responsibility_Note",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Replace the vague note with a detailed revision summary table on the title sheet listing every modified sheet, the nature of each change, and Engineer B\u0027s signature and seal applied to the title sheet and all modified sheets",
    "Issue a formal engineering letter to the client and relevant authorities documenting the scope of revisions, attaching Engineer B\u0027s sealed certification, and formally notifying Engineer A",
    "Withdraw from the project and advise the client to retain an engineer willing to properly certify the full revised plan set under their own seal"
  ],
  "proeth-scenario:characterMotivation": "Engineer B appears to have recognized some obligation to acknowledge his involvement but sought to minimize the scope of that acknowledgment \u2014 perhaps to limit perceived liability, avoid the administrative burden of full re-sealing, or satisfy a minimal compliance instinct without fully understanding the ethical and legal requirements of plan revision.",
  "proeth-scenario:consequencesIfAlternative": [
    "A detailed revision table with proper sealing would have met professional standards, created a usable record for all stakeholders, and established Engineer B\u0027s accountability with specificity and integrity",
    "A formal revision letter would have created a parallel documentation trail that could protect all parties and give regulatory authorities the information needed to evaluate the revised design on its merits",
    "Withdrawal would have been a principled decision that forced the client to confront the reality that proper engineering certification cannot be shortcut, potentially prompting a more ethical resolution"
  ],
  "proeth-scenario:decisionSignificance": "Teaches students that partial or vague disclosure can be more ethically problematic than no disclosure, because it creates a false impression of compliance while actually perpetuating misattribution. Ethical disclosure must be specific, complete, and properly executed \u2014 not symbolic.",
  "proeth-scenario:ethicalTension": "The impulse toward some form of disclosure conflicts with the inadequacy of that disclosure. A vague, unsigned note on a single title sheet creates the illusion of transparency while actually obscuring the true extent of Engineer B\u0027s changes and leaving Engineer A\u0027s seal as the dominant professional certification on the entire plan set.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "A vague title sheet note provides no actionable information to plan reviewers, contractors, or regulators about what was changed, who is responsible for specific elements, or which engineer\u0027s judgment governs any particular design decision. This ambiguity is dangerous in both the construction phase and in any subsequent liability dispute.",
  "proeth:description": "Engineer B added a note to the title sheet of the public improvement plans stating that he was taking responsibility for \u0027revisions of the plans,\u0027 while leaving Engineer A\u0027s signature and seal intact, without specifying what changes were made, and without signing or sealing the individual modified sheets.",
  "proeth:foreseenUnintendedEffects": [
    "Creating a misleading document where the note is \u0027virtually meaningless\u0027 due to lack of specificity about what was changed",
    "Allowing Engineer A\u0027s seal to remain as the primary certification on fundamentally altered plans",
    "Failing to give downstream users any actionable information about the nature or extent of the revisions"
  ],
  "proeth:fulfillsObligation": [
    "Partial acknowledgment of involvement in revisions \u2014 the Board acknowledged Engineer B did note responsibility for \u0027revisions\u0027 on the title sheet"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency and specificity in engineering documentation",
    "Meaningful professional accountability",
    "Honest representation of the scope of professional responsibility"
  ],
  "proeth:hasAgent": "Engineer B (Licensed Professional Engineer, successor design engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Minimal disclosure gesture vs. full transparent accountability for redesign",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of a minimalist disclosure strategy, which the Board found to be ethically insufficient \u2014 the note\u0027s vagueness made it \u0027virtually meaningless\u0027 and did not cure the deceptive character of the undocumented, unsealed modifications throughout the plan set"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide some form of attribution for his involvement in the redesign while minimizing the scope of acknowledged responsibility to only his specific revisions rather than the full integrated design",
  "proeth:requiresCapability": [
    "Understanding of engineering documentation standards",
    "Knowledge of professional sealing obligations",
    "Judgment about scope of professional responsibility"
  ],
  "proeth:temporalMarker": "During or at completion of redesign phase, after making changes to public improvement plans",
  "proeth:violatesObligation": [
    "NSPE Section III.3.a. \u2014 the vague note without specificity constitutes a form of deception by omission, rendering meaningful disclosure impossible",
    "NSPE Section III.9. \u2014 failure to acknowledge full responsibility for the integrated design that his fundamental changes affected",
    "Obligation to provide specific, meaningful documentation of all design changes",
    "Obligation to sign and seal sheets for which Engineer B was responsible rather than relying on a single vague title sheet note"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Place Vague Responsibility Note"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Claim_Partial_Rather_Than_Full_Design_Responsibili",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept full professional responsibility for the entire revised plan set, remove Engineer A\u0027s seals, and re-seal all sheets under Engineer B\u0027s authority after conducting a comprehensive review",
    "Formally document which elements were not changed and obtain Engineer A\u0027s written consent to retain his seal on those specific unchanged sheets, while Engineer B seals all modified sheets",
    "Advise the client in writing that the scope of changes required a full design review and re-certification, and propose a fee structure for that comprehensive service"
  ],
  "proeth-scenario:characterMotivation": "Engineer B may have genuinely believed that accepting responsibility only for \u0027revisions\u0027 was a legally and professionally defensible position \u2014 a misunderstanding of how integrated engineering design works. Alternatively, this may reflect a deliberate attempt to limit liability exposure by avoiding full ownership of a plan set he did not originate.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full assumption of responsibility would have been professionally demanding but ethically correct, producing a plan set with clear, unambiguous certification and protecting the public interest",
    "A formal sheet-by-sheet attribution agreement with Engineer A would have been complex to execute but would have created a legally and ethically defensible record of divided but complete responsibility",
    "Advising the client of the need for comprehensive re-certification would have been commercially honest and professionally responsible, even if unwelcome, and would have protected Engineer B from the much greater liability of proceeding improperly"
  ],
  "proeth-scenario:decisionSignificance": "A critical conceptual teaching point: engineering design is systemic, not modular. Students must understand that when changes to grading, drainage, and utilities are interdependent, the engineer making those changes cannot ethically or practically claim responsibility for only the changed elements while disclaiming the integrated system those changes now govern.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s natural inclination to limit personal liability conflicts with the professional reality that fundamental changes to an integrated design system create holistic responsibility. Engineering ethics does not permit selective accountability \u2014 if your changes affect the integrity of the whole, you are responsible for the whole.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "If Engineer B\u0027s partial responsibility claim is accepted, there is no engineer who has certified the integrated design as a whole. This creates a regulatory and liability vacuum that endangers the public, exposes both engineers to disciplinary action, and leaves the client with a plan set of uncertain professional standing.",
  "proeth:description": "Engineer B implicitly and structurally decided to accept responsibility only for his specific revisions rather than the full integrated design, failing to recognize that his fundamental changes to grading, infrastructure, and utilities had a holistic impact on the entire project design for which he bore professional responsibility.",
  "proeth:foreseenUnintendedEffects": [
    "Creating a design with no single engineer accountable for the integrity of the whole",
    "Leaving the integrated design in a state where fundamental changes to one system (e.g., street routing, pad elevations) may have cascading effects on other systems (e.g., drainage, utilities) with no engineer certifying the integrated result",
    "Exposing the public to safety risks from an uncertified integrated design"
  ],
  "proeth:guidedByPrinciple": [
    "Holistic professional responsibility for integrated engineering systems",
    "Public safety as paramount concern",
    "Engineer accountability for the full scope of work bearing one\u0027s professional certification"
  ],
  "proeth:hasAgent": "Engineer B (Licensed Professional Engineer, successor design engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Limiting personal professional liability vs. full accountability for integrated design integrity",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of partial responsibility, which the Board found to be an ethical violation under Section III.9., noting that once fundamental changes are made to interdependent design systems, the modifying engineer cannot disclaim responsibility for the integrated result"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Limit professional liability and responsibility to only those specific elements Engineer B personally modified, treating the remainder of the design as Engineer A\u0027s continuing responsibility",
  "proeth:requiresCapability": [
    "Systems-level engineering judgment about interdependence of grading, drainage, utilities, and street design",
    "Understanding of the holistic implications of fundamental design changes",
    "Professional judgment about the scope of sealing obligations when modifying integrated infrastructure systems"
  ],
  "proeth:temporalMarker": "Throughout the redesign phase and at its completion, as reflected in the overall documentation approach",
  "proeth:violatesObligation": [
    "NSPE Section III.9. \u2014 obligation to acknowledge responsibility for the full design once fundamental changes were made that affected the entire project",
    "Professional obligation to ensure that every engineering plan set has a clearly identified responsible engineer for the integrated whole",
    "Public safety obligation to certify the integrity of the complete design, not merely isolated components"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Claim Partial Rather Than Full Design Responsibility"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Action_Maintain_Silence_Toward_Engineer_A_Throughout",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Contact Engineer A before beginning the redesign to inform him of the engagement, discuss the original design intent, and negotiate a formal handoff of professional responsibility",
    "Send Engineer A a written notice upon completion of the redesign summarizing the changes made and inviting him to review the modified plans and formally release or withdraw his seal",
    "Engage the state board of registration for guidance on the proper protocol for modifying and re-certifying a predecessor engineer\u0027s sealed plans before proceeding"
  ],
  "proeth-scenario:characterMotivation": "Engineer B\u0027s sustained silence toward Engineer A likely reflects a combination of factors: avoidance of a potentially uncomfortable professional conversation, competitive instinct to establish an independent client relationship, possible client pressure to proceed without involving the predecessor engineer, and failure to internalize the NSPE ethical obligation to notify predecessor engineers.",
  "proeth-scenario:consequencesIfAlternative": [
    "Pre-engagement contact would have fulfilled NSPE ethical obligations, potentially improved the redesign through knowledge transfer, and established a collaborative professional relationship that protected both engineers and the public",
    "Post-completion notification, while late, would still have given Engineer A actionable information and the opportunity to seek removal of his seal or take other protective measures, partially mitigating the ethical harm",
    "Consulting the state board would have provided authoritative procedural guidance, protected Engineer B from unknowing violations of licensing law, and demonstrated the professional good faith that was entirely absent from his actual conduct"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethical violations can be committed through sustained inaction as effectively as through affirmative wrongdoing. Students learn that professional ethics imposes positive duties to communicate, not merely negative duties to avoid harm \u2014 and that silence in the face of a known ethical problem is itself an ethical failure.",
  "proeth-scenario:ethicalTension": "The path of least resistance \u2014 simply proceeding without contact \u2014 conflicts directly with the professional duty of collegiality and the ethical obligation to protect a fellow engineer\u0027s professional standing. Silence is not neutral when it enables ongoing misattribution of sealed work.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Engineer A\u0027s professional reputation and license remain at risk for the entire duration of Engineer B\u0027s silence. Any construction defect, regulatory challenge, or public harm traceable to the modified plans could be attributed to Engineer A\u0027s seal. Engineer B\u0027s silence denies Engineer A any opportunity to defend himself, correct the record, or formally withdraw his certification.",
  "proeth:description": "Engineer B made a sustained decision \u2014 through omission \u2014 to never initiate any communication with Engineer A at any point during or after the redesign process, despite making fundamental changes to Engineer A\u0027s sealed work product that bore Engineer A\u0027s professional seal and signature.",
  "proeth:foreseenUnintendedEffects": [
    "Forgoing technical context about original design decisions that could have improved the quality and safety of the redesign",
    "Leaving Engineer A uninformed that his sealed documents were being fundamentally altered and would continue to circulate bearing his professional seal",
    "Missing an opportunity to resolve technical ambiguities in the original design before making modifications"
  ],
  "proeth:guidedByPrinciple": [
    "Professional courtesy among engineers",
    "Thoroughness in engineering review and redesign",
    "Public safety through informed design modification",
    "Respect for the professional significance of a colleague\u0027s sealed work"
  ],
  "proeth:hasAgent": "Engineer B (Licensed Professional Engineer, successor design engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client relationship management and independence vs. professional consultation for design quality and courtesy",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of complete non-communication, which the Board found to be professionally suboptimal though not a clear-cut ethical violation given the discharge, noting that the purpose of Section III.8.a. \u2014 enabling the reviewing engineer to have a fuller understanding of the original design \u2014 was entirely frustrated by this choice"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Proceed with the redesign independently without engaging the discharged engineer, treating Engineer A\u0027s discharge as severing all professional obligations to communicate",
  "proeth:requiresCapability": [
    "Inter-engineer professional communication",
    "Understanding of the purpose and value of consulting original design engineers",
    "Judgment about when professional courtesy obligations arise despite client preferences"
  ],
  "proeth:temporalMarker": "Throughout the entire engagement \u2014 from acceptance through completion of redesign",
  "proeth:violatesObligation": [
    "Spirit of NSPE Section III.8.a. \u2014 while the discharge technically satisfies the condition for proceeding without notification, the Board found that professional norms strongly favored consultation",
    "Professional courtesy obligation to inform Engineer A that his sealed documents were being substantively altered",
    "Obligation to seek technical context that would enable a more informed and safer redesign"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Maintain Silence Toward Engineer A Throughout"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Event_Engineer_A_Discharged",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "When an engineer is discharged and paid in full, does their professional responsibility for sealed plans truly end?",
    "Should NSPE standards require Engineer A to take proactive steps upon discharge to protect the integrity of sealed plans?",
    "What rights and responsibilities does the client acquire over sealed engineering plans upon discharge of the originating engineer?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Professional disappointment and possible indignation for Engineer A; relief or resolve for the client; no immediate emotional impact on Engineer B or public",
  "proeth-scenario:ethicalImplications": "Highlights the gap between contractual resolution and professional ethical obligations; raises the question of whether professional seals create responsibilities that survive contractual termination",
  "proeth-scenario:learningMoment": "Discharge of an engineer does not erase their professional responsibility for sealed work. Students should understand that a seal is not merely an administrative mark but a continuing professional representation of competence and responsibility.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Freedom to pursue alternative engineering services; bears cost of transition and potential redesign",
    "engineer_a": "Loss of project; full fee received but professional reputation tied to plans now beyond direct control",
    "engineer_b": "Vacancy created; will inherit a complex professional ethics situation",
    "public": "No immediate impact, but project integrity risk increases as plans change hands"
  },
  "proeth:activatesConstraint": [
    "Seal_And_Signature_Integrity_Constraint",
    "Plan_Ownership_Rights_Constraint",
    "Successor_Engineer_Notification_Potential"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/173#Action_Prepare_and_Seal_Plans__by_Engineer_A_",
  "proeth:causesStateChange": "Engineer A\u0027s active project role ends; Engineer A\u0027s professional identity remains embedded in sealed plans; project enters a transitional state awaiting successor engagement",
  "proeth:createsObligation": [
    "Engineer_A_Must_Decide_On_Drawing_Surrender",
    "Client_Must_Disclose_Engineer_A_Involvement_To_Successor"
  ],
  "proeth:description": "Engineer A was formally discharged from the project by the client after receiving full fee payment. This termination of the professional engagement is an outcome event that legally and professionally separates Engineer A from the project while leaving their sealed plans in existence.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After client dissatisfaction; before request for original drawings",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Engineer A Discharged"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Event_Original_Drawings_Transferred",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should Engineer A have placed explicit conditions on the transfer of original drawings to protect the integrity of the seal?",
    "Does complying with a client\u0027s request for original drawings constitute implicit consent to their subsequent modification by another engineer?",
    "What industry practices or contractual provisions could prevent the ethical problems that arise from this transfer?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Possible resignation or unease for Engineer A in relinquishing professional work; satisfaction for client in regaining project documents; no awareness yet for Engineer B or public",
  "proeth-scenario:ethicalImplications": "Exposes the vulnerability of the professional seal once physical custody transfers; raises questions about whether professional responsibility requires engineers to negotiate protective terms when surrendering sealed documents",
  "proeth-scenario:learningMoment": "The physical transfer of sealed engineering plans creates a chain-of-custody risk that NSPE standards must address. Students should consider whether engineers have an obligation to place conditions on plan transfers to protect seal integrity.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Gains full physical custody of plans; now holds the means to engage a successor engineer",
    "engineer_a": "Loses physical control over sealed work; professional identity embedded in plans now fully in client\u0027s hands",
    "engineer_b": "Will receive plans bearing Engineer A\u0027s seal as the starting point for redesign",
    "public": "Unaware but increasingly at risk as plans containing Engineer A\u0027s seal may be modified"
  },
  "proeth:activatesConstraint": [
    "Plan_Integrity_Risk_Constraint",
    "Seal_Vulnerability_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/173#Action_Surrender_Original_Drawings__by_Engineer_A_",
  "proeth:causesStateChange": "Physical custody of original plans transfers to client; Engineer A retains reproducibles but loses control over originals; plans become available for potential modification by successor engineer",
  "proeth:createsObligation": [
    "Client_Obligation_To_Use_Plans_Appropriately",
    "Potential_Obligation_For_Engineer_A_To_Warn_About_Seal_Misuse"
  ],
  "proeth:description": "Following discharge, the client requested the original drawings and Engineer A complied, transferring the originals while retaining reproducibles. This transfer is an outcome of the surrender action that physically relocates the primary artifacts of Engineer A\u0027s professional work.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After discharge; before Engineer B\u0027s engagement",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Original Drawings Transferred"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Event_Engineer_B_Engaged_On_Project",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At the moment of accepting this engagement, what specific actions did NSPE standards require Engineer B to take before proceeding?",
    "Does the client bear any ethical responsibility for facilitating proper notification of Engineer A when engaging Engineer B?",
    "How does the failure to notify Engineer A at this stage compound all subsequent ethical violations by Engineer B?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Opportunity and perhaps professional ambition for Engineer B; continued exclusion and vulnerability for Engineer A who is unaware; public remains unaware but their interests are now dependent on Engineer B\u0027s ethical conduct",
  "proeth-scenario:ethicalImplications": "Reveals the NSPE obligation of successor engineers to notify predecessors; highlights how the absence of a single required communication can cascade into systematic professional misconduct; raises questions about client complicity in engineer-to-engineer ethical violations",
  "proeth-scenario:learningMoment": "The moment a successor engineer accepts engagement on a project with existing sealed plans is the critical ethical inflection point. NSPE standards require immediate notification of the predecessor engineer \u2014 failure to do so at this stage sets the entire subsequent ethical violation in motion.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Project resumes with new engineer; client holds responsibility for facilitating proper transition",
    "engineer_a": "Professional stake in sealed plans now directly threatened by successor\u0027s undisclosed engagement; no opportunity to protect interests",
    "engineer_b": "Assumes professional responsibility for a project with complex predecessor obligations; ethical choices at this moment will define the entire subsequent narrative",
    "public": "Welfare increasingly dependent on whether Engineer B follows proper successor protocols"
  },
  "proeth:activatesConstraint": [
    "Successor_Engineer_Notification_Obligation",
    "Prior_Engineer_Communication_Duty",
    "Seal_Integrity_Review_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/173#Action_Accept_Engagement_Without_Notifying_Engineer_A__by",
  "proeth:causesStateChange": "Project now has two licensed engineers with competing professional stakes; Engineer A\u0027s sealed plans become the active working documents for a second engineer; ethical obligations for successor conduct immediately arise",
  "proeth:createsObligation": [
    "Engineer_B_Must_Notify_Engineer_A",
    "Engineer_B_Must_Review_Existing_Seals_Before_Proceeding",
    "Engineer_B_Must_Assess_Scope_Of_Predecessor_Work"
  ],
  "proeth:description": "Engineer B was retained by the client to review and redesign the project, inheriting Engineer A\u0027s sealed plans as the working basis. This engagement is an exogenous triggering event that introduces a second licensed professional into a situation already fraught with ethical complexity.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After original drawings transferred to client; before any modifications",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer B Engaged On Project"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Event_Engineer_A_s_Seal_Left_Intact",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What is the legal and ethical significance of an engineering seal, and why does leaving Engineer A\u0027s seal on modified work constitute a serious professional violation?",
    "How does the public\u0027s reliance on engineering seals as quality assurances make Engineer B\u0027s omission particularly dangerous?",
    "What specific steps should Engineer B have taken to properly manage Engineer A\u0027s seal upon making significant modifications?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Profound professional violation for Engineer A who is unaware their seal now misrepresents work they did not do; ethical compromise for Engineer B who knowingly allowed this; public trust in engineering credentials undermined",
  "proeth-scenario:ethicalImplications": "Strikes at the heart of what professional licensure means; reveals how seal mismanagement simultaneously harms a specific engineer (A), deceives the public, and erodes systemic trust in engineering credentials; raises questions about regulatory enforcement mechanisms for seal integrity",
  "proeth-scenario:learningMoment": "A professional engineering seal is not decorative \u2014 it is a legal and ethical certification that the sealing engineer has personally reviewed and takes responsibility for the work. Leaving a predecessor\u0027s seal on substantially modified work is a form of professional fraud that harms the predecessor, deceives the public, and undermines the integrity of the entire credentialing system.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Receives plans with ambiguous professional responsibility \u2014 creating legal and liability risks for the project",
    "engineer_a": "Professional seal \u2014 the highest expression of engineering responsibility \u2014 now attached to work Engineer A did not perform, review, or approve; legal and reputational exposure without knowledge or consent",
    "engineer_b": "Avoids professional accountability for modified work while benefiting from Engineer A\u0027s established credibility on the plans",
    "public": "Relies on engineering seals as assurances of professional review and accountability; that assurance is now false on these documents",
    "regulatory_authorities": "Building departments and reviewers will rely on Engineer A\u0027s seal as certification of the modified work \u2014 a reliance that is professionally fraudulent"
  },
  "proeth:activatesConstraint": [
    "Seal_Misrepresentation_Prohibition",
    "Public_Safety_Through_Accurate_Attribution",
    "Professional_Fraud_Prevention_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/173#Action_Modify_Grading_Plans_Without_Notation__by_Engineer",
  "proeth:causesStateChange": "Plans now bear Engineer A\u0027s seal on work that Engineer A did not perform or review; professional misrepresentation is embedded in the document set; any party relying on the seal for assurance of Engineer A\u0027s professional judgment is misled",
  "proeth:createsObligation": [
    "Engineer_B_Must_Remove_Or_Supersede_Predecessor_Seal",
    "Engineer_A_Has_Right_To_Demand_Seal_Removal",
    "Regulatory_Authority_Interest_In_Seal_Accuracy"
  ],
  "proeth:description": "As a result of Engineer B\u0027s modifications without removal or supersession of Engineer A\u0027s seal and signature, Engineer A\u0027s professional credentials remained embedded throughout the modified plan set. This outcome creates a false professional representation on documents that no longer reflect Engineer A\u0027s work.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During and after Engineer B\u0027s modifications; persisting through plan completion",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Engineer A\u0027s Seal Left Intact"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Event_Significant_Design_Changes_Embedded",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Why is change notation on engineering plans a professional ethics obligation rather than merely a best practice?",
    "If a construction error occurs on this project, how does the absence of change notation affect the ability to assign professional responsibility?",
    "What systems or contractual requirements could prevent undocumented changes from being embedded in engineering plan sets?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A is unaware but would experience profound professional violation upon discovery; Engineer B experiences no immediate consequence; contractors and future reviewers face hidden confusion; public safety interests are silently undermined",
  "proeth-scenario:ethicalImplications": "Demonstrates how procedural omissions (failure to note changes) create substantive ethical violations; reveals the connection between documentation integrity and public safety; raises questions about how professional accountability systems depend on accurate records",
  "proeth-scenario:learningMoment": "Engineering documentation is not merely administrative \u2014 it is a safety mechanism. Change notation and proper attribution allow future engineers, contractors, and regulators to understand design intent and assign accountability. Undocumented changes destroy this safety mechanism and create risks that may only materialize during or after construction.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "contractors": "Will construct based on plans where design responsibility is ambiguous \u2014 creating risk of misinterpretation",
    "engineer_a": "Work product misrepresented; unable to defend, explain, or disclaim modifications to their original design",
    "engineer_b": "Avoids accountability for design decisions that may later prove problematic",
    "public": "Infrastructure built from ambiguously attributed plans; if problems arise, accountability chain is broken",
    "regulatory_authorities": "Cannot properly evaluate plan compliance when authorship of specific elements is unknown"
  },
  "proeth:activatesConstraint": [
    "Design_Traceability_Obligation",
    "Professional_Attribution_Requirement",
    "Public_Safety_Through_Accurate_Documentation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/173#Action_Modify_Grading_Plans_Without_Notation__by_Engineer",
  "proeth:causesStateChange": "Plan set now contains a mixture of Engineer A\u0027s original work and Engineer B\u0027s undisclosed redesign; the boundary between the two engineers\u0027 work is invisible; no mechanism exists for future engineers, contractors, or regulators to identify which elements were changed and by whom",
  "proeth:createsObligation": [
    "Obligation_To_Document_All_Changes",
    "Obligation_To_Attribute_Redesign_To_Responsible_Engineer",
    "Obligation_To_Notify_Engineer_A_Of_Changes_To_Their_Work"
  ],
  "proeth:description": "As a result of Engineer B\u0027s undisclosed redesign actions, substantial changes to grading plans, housing pads, street routing, storm drains, pipe dimensions, sewers, and utilities became embedded in the plan set without notation or attribution. These changes are now invisible within documents that appear to be Engineer A\u0027s original work.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During Engineer B\u0027s redesign phase; persisting into final plan set",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Significant Design Changes Embedded"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Event_False_Attribution_State_Created",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "How does the vague responsibility note on the title sheet actually worsen rather than mitigate Engineer B\u0027s ethical violations?",
    "If these plans were submitted to a building department and approved, who would bear professional liability if a design defect caused harm?",
    "How should NSPE standards be interpreted to address the specific situation where a successor engineer makes significant changes but refuses to fully assume the predecessor\u0027s professional role?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A suffers professional harm without awareness or recourse; Engineer B may experience cognitive dissonance between professional self-image and actual conduct; regulatory reviewers and contractors are deceived; public trust in engineering credentials is undermined",
  "proeth-scenario:ethicalImplications": "Reveals how professional ethics violations can be constructed through deliberate omission rather than overt action; demonstrates the systemic importance of clear professional attribution for public safety and accountability; raises questions about whether vague disclaimers can ever satisfy the ethical obligation of honest professional representation",
  "proeth-scenario:learningMoment": "Professional attribution is not a formality \u2014 it is the mechanism by which engineering accountability is maintained. When attribution is falsified or obscured, the entire system of professional responsibility breaks down. This event illustrates how a series of omissions can collectively constitute a serious ethical violation even when no single act appears egregious in isolation.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Holds plans with ambiguous professional responsibility \u2014 creating significant legal and liability exposure",
    "contractors": "Will rely on plans where accountability for design decisions is systematically obscured",
    "engineer_a": "Professional seal attached to unknown modifications; legal liability exposure for work not performed; reputational harm if project problems arise",
    "engineer_b": "Avoids full professional accountability while benefiting from the credibility of Engineer A\u0027s established seal",
    "public": "Infrastructure may be built from plans where no engineer has clearly accepted full responsibility for the complete design",
    "regulatory_authorities": "Misled about who bears professional responsibility for specific design elements"
  },
  "proeth:activatesConstraint": [
    "Professional_Misrepresentation_Prohibition",
    "Public_Reliance_On_Accurate_Attribution",
    "Regulatory_Submission_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/173#Action_Claim_Partial_Rather_Than_Full_Design_Responsibili",
  "proeth:causesStateChange": "A legally and professionally false document set now exists; any submission of these plans to regulatory authorities, contractors, or the public constitutes a misrepresentation of professional responsibility; the integrity of the engineering credentialing system is directly compromised",
  "proeth:createsObligation": [
    "Obligation_To_Correct_False_Attribution",
    "Engineer_A_Right_To_Demand_Seal_Removal_Or_Correction",
    "Regulatory_Authority_Right_To_Reject_Ambiguously_Attributed_Plans"
  ],
  "proeth:description": "The combined result of Engineer B\u0027s modifications, failure to sign sheets, retention of Engineer A\u0027s seal, and placement of a vague responsibility note created a state of false professional attribution throughout the plan set. The plans now misrepresent both who designed the work and who bears professional responsibility for it.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Upon completion of Engineer B\u0027s modifications; persisting into plan submission and use",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "False Attribution State Created"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#Event_Client_Dissatisfaction_Emerges",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does a client\u0027s right to discharge an engineer upon full payment also confer the right to repurpose that engineer\u0027s sealed plans without restriction?",
    "What professional obligations does Engineer A have when a client becomes dissatisfied \u2014 and does fulfilling those obligations end at discharge?",
    "How might proactive communication between Engineer A and the client have altered the ethical landscape that followed?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Frustration and disappointment for the client; potential professional hurt and defensiveness for Engineer A; uncertainty about project future for all stakeholders",
  "proeth-scenario:ethicalImplications": "Reveals tension between client autonomy and engineer\u0027s continuing professional stake in sealed work; raises questions about whether contractual resolution (full payment) fully extinguishes professional obligations tied to sealed documents",
  "proeth-scenario:learningMoment": "Client dissatisfaction, even when resolved through proper fee payment and discharge, creates downstream professional ethics vulnerabilities \u2014 particularly around intellectual property, plan ownership, and successor engineer obligations.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client": "Project uncertainty; financial exposure from needing to hire replacement engineer; potential project delays",
    "engineer_a": "Professional reputation questioned; loss of ongoing project relationship despite full fee payment",
    "engineer_b": "Not yet involved, but vacancy created that will draw them into the situation",
    "public": "Indirect concern \u2014 project delays may affect community development timelines"
  },
  "proeth:activatesConstraint": [
    "Client_Communication_Obligation",
    "Professional_Relationship_Integrity"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/173#Action_Prepare_and_Seal_Plans__by_Engineer_A_",
  "proeth:causesStateChange": "Professional relationship status shifts from active engagement to contested; client begins evaluating alternatives to Engineer A",
  "proeth:createsObligation": [
    "Opportunity_For_Engineer_A_To_Respond",
    "Client_Right_To_Seek_Alternatives"
  ],
  "proeth:description": "The client became dissatisfied with Engineer A\u0027s work, triggering a breakdown in the professional relationship. This dissatisfaction is an exogenous outcome that sets the entire subsequent chain of events in motion.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "After plan completion, before discharge",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Client Dissatisfaction Emerges"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#CausalChain_8dd172ae",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B added a note to the title sheet stating that he was taking responsibility [only for his revisions], and Engineer B implicitly and structurally decided to accept responsibility only for his specific revisions, and the combined result of Engineer B\u0027s modifications, failure to sign sheets, and retention of Engineer A\u0027s seal created a false attribution state",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B makes substantive grading changes without any contemporaneous attribution, creating the initial attribution gap",
      "proeth:element": "Modify Grading Plans Without Notation (Action 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B extends the attribution gap to public improvement plans, compounding the scope of the false attribution problem",
      "proeth:element": "Redesign Public Improvements Without Attribution (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B attempts to address attribution with a single title-sheet note, which is structurally insufficient to clarify sheet-level professional responsibility",
      "proeth:element": "Place Vague Responsibility Note (Action 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B\u0027s partial responsibility claim leaves the remainder of the drawing set implicitly attributed to Engineer A\u0027s seal",
      "proeth:element": "Claim Partial Rather Than Full Design Responsibility (Action 7)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The submitted drawing set falsely represents Engineer A as the certifying engineer for design decisions that are actually Engineer B\u0027s, with material consequences for public safety, regulatory reliance, and Engineer A\u0027s professional standing",
      "proeth:element": "False Attribution State Created (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Place Vague Responsibility Note (Action 6) combined with Claim Partial Rather Than Full Design Responsibility (Action 7)",
  "proeth:counterfactual": "If Engineer B had signed and sealed every sheet he modified and had explicitly voided Engineer A\u0027s seal on those sheets, the responsibility allocation would have been transparent and the false attribution state would not have existed",
  "proeth:effect": "False Attribution State Created (Event 7)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s choice to use a single vague title-sheet note rather than sheet-level attribution",
    "Engineer B\u0027s structural decision to claim only partial responsibility",
    "Engineer A\u0027s seal remaining on sheets containing Engineer B\u0027s design decisions",
    "No regulatory rejection of the inadequate attribution mechanism before plan submission"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Vague title-sheet note + partial responsibility claim + Engineer A\u0027s seal intact on modified sheets = a document set that any reasonable third party would interpret as certified by Engineer A in its entirety"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#CausalChain_2a308a58",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B made significant changes to the grading plans \u2014 including deletion of one sheet, raising [grades] \u2014 without removal or supersession of Engineer A\u0027s seal and signature, resulting in Engineer A\u0027s seal remaining on materially altered work",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A surrenders sealed originals to client upon discharge, making the drawing set available for third-party modification",
      "proeth:element": "Original Drawings Transferred (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B is retained and inherits Engineer A\u0027s sealed drawing set as the working base",
      "proeth:element": "Engineer B Engaged On Project (Event 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B deletes a sheet, raises grades, and makes other substantive changes without adding his own seal or removing Engineer A\u0027s",
      "proeth:element": "Modify Grading Plans Without Notation (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B adds only a general title-sheet note rather than sheet-by-sheet attribution, leaving the seal situation ambiguous",
      "proeth:element": "Place Vague Responsibility Note (Action 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s seal and signature remain on drawings that no longer reflect his design, creating a false professional certification",
      "proeth:element": "Engineer A\u0027s Seal Left Intact (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Modify Grading Plans Without Notation (Action 4)",
  "proeth:counterfactual": "If Engineer B had signed and sealed each modified sheet or clearly marked superseded sheets, Engineer A\u0027s seal would no longer have represented the current design state; the false attribution would have been prevented",
  "proeth:effect": "Engineer A\u0027s Seal Left Intact (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s decision to alter grading plans without adding his own seal",
    "Engineer A\u0027s original seal already present on the drawings",
    "Absence of any notation or supersession marking to distinguish revised from original work",
    "Original drawings physically transferred to client and then to Engineer B"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Combination of Engineer B making substantive design changes + retaining Engineer A\u0027s seal + adding no corrective attribution = seal left intact on altered work"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#CausalChain_cd0a410f",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B made major design changes to storm drains, pipe dimensions, sewers, and utilities in the public improvement plans without attribution, and the combined result of Engineer B\u0027s modifications, failure to sign sheets, and retention of Engineer A\u0027s seal created a false attribution state",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B agrees to the engagement without contacting Engineer A, foreclosing any collaborative transition that might have clarified attribution responsibilities",
      "proeth:element": "Accept Engagement Without Notifying Engineer A (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B makes major changes to storm drains, sewers, and utilities without signing or sealing the affected sheets",
      "proeth:element": "Redesign Public Improvements Without Attribution (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B adds a general note to the title sheet that is insufficient to clarify sheet-level professional responsibility",
      "proeth:element": "Place Vague Responsibility Note (Action 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B structurally limits his acknowledged responsibility to his specific revisions only, leaving the remainder falsely attributed to Engineer A",
      "proeth:element": "Claim Partial Rather Than Full Design Responsibility (Action 7)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The drawing set enters use with Engineer A\u0027s seal certifying design decisions that are actually Engineer B\u0027s, exposing the public, regulators, and Engineer A to undisclosed risk",
      "proeth:element": "False Attribution State Created (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Redesign Public Improvements Without Attribution (Action 5)",
  "proeth:counterfactual": "If Engineer B had applied his own seal to every redesigned sheet and removed or clearly voided Engineer A\u0027s seal on those sheets, the false attribution state would not have been created; third parties would have known whose engineering judgment governed each element",
  "proeth:effect": "False Attribution State Created (Event 7)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s substantive redesign of public improvement elements",
    "Engineer B\u0027s failure to sign and seal the redesigned sheets",
    "Retention of Engineer A\u0027s original seal on those same sheets",
    "Absence of any clear sheet-level notation distinguishing Engineer B\u0027s work from Engineer A\u0027s"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Substantive redesign by Engineer B + no new seal applied + Engineer A\u0027s seal retained + vague title-sheet note only = documents that falsely attribute Engineer B\u0027s design decisions to Engineer A\u0027s professional certification"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#CausalChain_cc22412c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B agreed to be retained by the client to review and redesign the project without notifying Engineer A, and Engineer B made a sustained decision \u2014 through omission \u2014 to never initiate any communication with Engineer A throughout the project",
  "proeth:causalSequence": [
    {
      "proeth:description": "Client dissatisfaction creates an adversarial context that makes client-mediated communication between engineers unlikely",
      "proeth:element": "Client Dissatisfaction Emerges (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Formal discharge severs Engineer A\u0027s direct project relationship, removing the natural channel for engineer-to-engineer communication",
      "proeth:element": "Engineer A Discharged (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B accepts the engagement without fulfilling the professional obligation to notify Engineer A, establishing a pattern of non-communication",
      "proeth:element": "Accept Engagement Without Notifying Engineer A (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Because no communication occurred, Engineer A has no opportunity to provide design intent context or flag risks in Engineer B\u0027s redesign",
      "proeth:element": "Significant Design Changes Embedded (Event 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B\u0027s initial omission hardens into a sustained posture of silence, leaving Engineer A unaware that his sealed drawings have been materially altered and resubmitted",
      "proeth:element": "Maintain Silence Toward Engineer A Throughout (Action 8)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Accept Engagement Without Notifying Engineer A (Action 3)",
  "proeth:counterfactual": "If Engineer B had notified Engineer A at the point of engagement, a professional dialogue would have been opened; Engineer A could have provided design intent documentation, flagged critical assumptions, and the attribution issues may have been resolved collaboratively",
  "proeth:effect": "Maintain Silence Toward Engineer A Throughout (Action 8)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s initial decision not to notify Engineer A at the point of engagement",
    "Engineer B\u0027s ongoing choice to treat the omission as a settled posture rather than a correctable oversight",
    "Absence of any institutional or client mechanism that compelled Engineer B to communicate with Engineer A"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Initial non-notification at engagement + no subsequent outreach + no external compulsion to communicate = sustained silence throughout the project lifecycle"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/173#",
    "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/173#CausalChain_47026d39",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon the client\u0027s request following discharge, Engineer A complied and handed over the original drawings, and Engineer B was retained by the client to review and redesign the project, inheriting Engineer A\u0027s sealed drawing set as the working base, enabling substantial changes to be embedded within the original sealed set",
  "proeth:causalSequence": [
    {
      "proeth:description": "Discharge triggers the client\u0027s request for original drawings and Engineer A\u0027s obligation to respond",
      "proeth:element": "Engineer A Discharged (Event 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A transfers the 43-sheet sealed set to the client, relinquishing physical control over documents bearing his professional seal",
      "proeth:element": "Surrender Original Drawings (Action 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "The sealed drawing set is now in client possession and available for transfer to a successor engineer",
      "proeth:element": "Original Drawings Transferred (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Client provides the sealed originals to Engineer B as the working base, making modification of sealed documents the path of least resistance",
      "proeth:element": "Engineer B Engaged On Project (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B embeds substantive design changes within the original sealed set, creating a document that misrepresents the provenance of its design decisions",
      "proeth:element": "Significant Design Changes Embedded (Event 6)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Surrender Original Drawings (Action 2)",
  "proeth:counterfactual": "If Engineer A had surrendered only reproducible copies clearly marked \u0027for reference only \u2014 not for modification\u0027 or had retained originals, Engineer B would have faced a structural barrier to modifying the sealed set; however, Engineer A likely had a legal obligation to surrender originals upon full fee payment, limiting his practical options",
  "proeth:effect": "Engineer B Engaged On Project (Event 4) / Significant Design Changes Embedded (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s physical surrender of the original sealed drawings",
    "The drawings being in a format that permitted modification while retaining original seals",
    "Client\u0027s decision to provide those drawings to Engineer B as the working base rather than commissioning new drawings"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (partial) and Engineer B (primary)",
  "proeth:sufficientFactors": [
    "Transfer of original sealed drawings to client + client engagement of Engineer B + Engineer B\u0027s willingness to modify rather than supersede = conditions sufficient for embedded undisclosed changes"
  ],
  "proeth:withinAgentControl": true
}