{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Action_Accepting_Chief_Engineer_Role",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept the role but immediately audit the firm\u0027s existing sealing and supervision practices to establish a compliant oversight framework before taking responsibility for any documents.",
    "Negotiate a restructured role in which multiple licensed engineers share sealing authority across project divisions, distributing supervisory responsibility to a manageable scope.",
    "Decline the Chief Engineer role and instead accept a senior technical advisor position without sealing authority, contributing expertise without assuming unsustainable legal responsibility."
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought career advancement, professional prestige, and organizational influence by accepting the Chief Engineer role. He likely believed his experience and confidence in his team made him well-suited to oversee a large portfolio of projects, and may have underestimated the legal and ethical weight that the title and sealing authority would carry across all documents produced under his watch.",
  "proeth-scenario:consequencesIfAlternative": [
    "An upfront audit would likely reveal the inadequacy of the existing supervision model before any violations occur, allowing Engineer A to implement direct control protocols, potentially delay some project timelines, but avoid ethical and legal breaches entirely.",
    "Restructuring sealing authority across multiple licensed engineers would distribute supervisory load appropriately, reduce risk, and model a compliant organizational structure \u2014 though it might require negotiation with firm leadership and added cost.",
    "Declining the role preserves Engineer A\u0027s ethical standing and avoids the systemic problem entirely, but forgoes the career opportunity and leaves the firm potentially vulnerable to the same problem under a different Chief Engineer who may be equally unprepared."
  ],
  "proeth-scenario:decisionSignificance": "Students learn that accepting a senior engineering role is not merely an organizational or administrative act \u2014 it is an ethical commitment. The Chief Engineer title implicitly binds the individual to the full legal and ethical standard of supervision for all sealed work, regardless of team size or project volume. Roles must be accepted with clear-eyed understanding of their professional obligations.",
  "proeth-scenario:ethicalTension": "Professional ambition and organizational value versus the fiduciary duty to the public that accompanies a licensed engineer\u0027s sealing authority. The tension is between what the role offers (status, influence, compensation) and what it demands (direct, personal accountability for every sealed document).",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "By accepting this role without fully reckoning with its supervisory obligations, Engineer A sets in motion a systemic practice that puts public safety at risk across all projects, exposes the firm to legal liability, and places his own professional license in jeopardy. The scale of a large firm amplifies every downstream error.",
  "proeth:description": "Engineer A accepts and maintains the role of Chief Engineer in a large firm with a high volume of concurrent projects, implicitly taking on responsibility for all sealed documents produced by the organization.",
  "proeth:foreseenUnintendedEffects": [
    "Volume of concurrent projects would make detailed personal review of all sealed documents practically impossible",
    "Legal and ethical responsibility for all sealed work would rest with Engineer A regardless of actual involvement"
  ],
  "proeth:fulfillsObligation": [
    "Accepting work within a domain where he possesses general engineering competence (Section II.2.a)"
  ],
  "proeth:guidedByPrinciple": [
    "Professional competence",
    "Responsible charge",
    "Public safety through accountable engineering oversight"
  ],
  "proeth:hasAgent": "Engineer A (Chief Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Managerial leadership role vs. legally required personal supervision of sealed work",
    "proeth:resolutionReasoning": "Engineer A prioritized the managerial and organizational function of the Chief Engineer role, assuming his general involvement was ethically and legally sufficient, without restructuring workflows to meet the direct control standard"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill a senior leadership role within a large engineering firm, providing organizational oversight and professional authority over all design output",
  "proeth:requiresCapability": [
    "Broad engineering judgment across project types",
    "Organizational and managerial leadership",
    "Capacity to exercise direct control and personal supervision over sealed documents"
  ],
  "proeth:temporalMarker": "Ongoing; initial acceptance predates case facts",
  "proeth:violatesObligation": [
    "Obligation to ensure that the scope of responsibility accepted does not exceed the engineer\u0027s capacity to exercise direct control and personal supervision (NCEE Model Law, Section II.2.b)",
    "Obligation to ensure each technical segment is sealed only by the qualified engineer who prepared it (Section II.2.c)"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Accepting Chief Engineer Role"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Action_Defining_General_Supervision_Standard",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Research applicable state licensing board rules, NSPE Code provisions, and prior BER case decisions (such as Case 85-3) to establish a supervision definition that is externally validated and compliant before formalizing any internal practice.",
    "Implement a tiered supervision model in which high-level involvement is supplemented by mandatory detailed design reviews at defined project milestones before any seal is affixed.",
    "Consult with the firm\u0027s legal counsel and ethics advisor to develop a written supervision protocol that explicitly maps Engineer A\u0027s activities to the \u0027direct control and personal supervision\u0027 standard, with documented sign-off at each phase."
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to create an operationally scalable oversight model that allowed him to function effectively across a high volume of concurrent projects. He rationalized that high-level involvement \u2014 setting concepts, defining requirements, and being available for consultation \u2014 represented meaningful engineering judgment and constituted sufficient professional engagement, likely influenced by organizational pressure to maintain throughput.",
  "proeth-scenario:consequencesIfAlternative": [
    "Researching applicable standards would almost certainly reveal that Engineer A\u0027s proposed model falls short, prompting him to either redesign his oversight approach or restructure the organization \u2014 preventing the ethical violation before it begins.",
    "A tiered model with mandatory detailed reviews would be more burdensome but would bring Engineer A\u0027s practice into compliance, ensuring that his seal genuinely represents personal technical accountability for the work.",
    "A formally documented and legally reviewed protocol would create an auditable record of compliant supervision, protect Engineer A and the firm in the event of scrutiny, and likely surface the inadequacy of the original model during the drafting process."
  ],
  "proeth-scenario:decisionSignificance": "This action illustrates the danger of self-serving redefinition of professional standards. Students learn that ethical and legal standards for engineering supervision are externally defined by codes, licensing boards, and case precedent \u2014 not by individual practitioners based on personal confidence or convenience. The act of consciously defining a lower standard is itself an ethical failure, not merely a procedural one.",
  "proeth-scenario:ethicalTension": "Operational efficiency and organizational scalability versus the legally and ethically mandated standard of \u0027direct control and personal supervision.\u0027 Engineer A is attempting to redefine a professional standard to fit his circumstances rather than adapting his circumstances to meet the standard.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "By institutionalizing an insufficient supervision standard, Engineer A creates a repeatable, firm-wide practice that systematically violates the requirements for sealing documents. Every project processed under this model carries the same deficiency, multiplying risk to public safety and legal exposure with each sealed document.",
  "proeth:description": "Engineer A deliberately defines \u0027general direction and supervision\u0027 as involvement in concept establishment, design requirements, periodic progress reviews, and answering technical questions, explicitly excluding detailed review or checking of designs as a component of his oversight model.",
  "proeth:foreseenUnintendedEffects": [
    "Sealed documents may contain errors or deficiencies that Engineer A has not personally identified or approved",
    "The standard falls short of \u0027direct control and personal supervision\u0027 required by the NCEE Model Law"
  ],
  "proeth:fulfillsObligation": [
    "Partial fulfillment of managerial guidance role recognized as legitimate for chief engineers (concept-setting, design requirements, progress review, technical consultation)"
  ],
  "proeth:guidedByPrinciple": [
    "Responsible charge",
    "Public protection through engineering oversight",
    "Professional honesty about the limits of one\u0027s supervisory involvement"
  ],
  "proeth:hasAgent": "Engineer A (Chief Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Operational efficiency and scalability vs. ethical requirement for direct control and personal supervision",
    "proeth:resolutionReasoning": "Engineer A prioritized firm-scale operational capacity, substituting confidence in subordinates for the personal review and direct control required by the Code, a rationalization the Board found ethically insufficient"
  },
  "proeth:hasMentalState": "deliberate and rationalized",
  "proeth:intendedOutcome": "Establish a workable oversight model that allows the firm to operate efficiently at scale while Engineer A believes he remains ethically and legally compliant",
  "proeth:requiresCapability": [
    "Capacity to conduct detailed technical review of engineering plans and specifications",
    "Judgment to identify design deficiencies across multiple engineering domains",
    "Organizational design skill to create review workflows compatible with the direct control standard"
  ],
  "proeth:temporalMarker": "Ongoing; established as a standing operational policy",
  "proeth:violatesObligation": [
    "Obligation to exercise direct control and personal supervision over all work bearing his seal (NCEE Model Law; Section II.2.b)",
    "Obligation to possess understanding and cognizance of sealed documents (Section II.2.b)",
    "Obligation to protect public safety by ensuring thorough review of engineering designs"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Defining General Supervision Standard"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Action_Sealing_Registered_Engineers__Plans_Without_Their_",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Require each registered engineer who prepares plans to affix their own seal alongside Engineer A\u0027s, creating a dual-accountability record that reflects both the preparer\u0027s and the supervising engineer\u0027s professional responsibility.",
    "Establish a clear internal policy distinguishing when Engineer A\u0027s seal alone is appropriate (work he personally directed in detail) versus when the preparing engineer\u0027s seal is required, based on the actual level of supervision exercised.",
    "Engage with the state licensing board to clarify whether the firm\u0027s proposed sealing practice complies with applicable regulations before implementing it as standard procedure."
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to streamline the document approval process by centralizing sealing authority, likely believing this simplified administrative workflows, presented a unified professional front for the firm, and reflected his role as the senior responsible engineer. He may also have believed that having registered engineers under his direction made their independent sealing redundant or unnecessary.",
  "proeth-scenario:consequencesIfAlternative": [
    "Dual sealing would increase transparency and distribute accountability appropriately, ensuring that each registered engineer\u0027s professional judgment is documented and that the public record accurately reflects who is responsible for the work.",
    "A clear internal policy would prevent blanket application of Engineer A\u0027s seal to all work regardless of supervision level, reducing systemic risk and ensuring that sealing decisions are made deliberately rather than as a matter of routine.",
    "Proactive engagement with the licensing board would provide authoritative guidance, protect Engineer A from inadvertent violations, and demonstrate good faith \u2014 potentially resulting in formal written guidance that protects the firm."
  ],
  "proeth-scenario:decisionSignificance": "Students learn that sealing is not merely an administrative formality \u2014 it is a professional declaration of personal accountability. When a registered engineer prepares plans, their seal communicates to the public and regulatory bodies that they have exercised direct professional judgment over that work. Suppressing that seal and substituting another engineer\u0027s seal obscures accountability, potentially misleads regulators, and removes a critical layer of professional responsibility.",
  "proeth-scenario:ethicalTension": "Administrative efficiency and centralized accountability versus the professional responsibility of each registered engineer to stand behind their own work with their own seal. There is also a tension between Engineer A\u0027s confidence in his team and the public\u0027s right to know which licensed professional personally reviewed and is accountable for a given set of plans.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "If plans sealed solely by Engineer A contain errors introduced by the preparing engineer, there is no documented record of the preparing engineer\u0027s professional accountability. In a failure scenario, this complicates liability determination, may constitute misrepresentation to regulatory bodies, and deprives the public of the transparency that the sealing system is designed to provide.",
  "proeth:description": "Engineer A affixes his own seal to plans prepared by registered engineers working under his general direction, while those registered engineers do not affix their own seals to the same plans, consolidating all sealing authority in Engineer A alone.",
  "proeth:foreseenUnintendedEffects": [
    "Registered engineers who actually prepared the work are not individually accountable via their seals, obscuring true authorship and responsible charge",
    "Engineer A assumes full legal liability for work he has not personally reviewed in detail",
    "The Code requirement that each technical segment be sealed by its preparer is bypassed"
  ],
  "proeth:fulfillsObligation": [
    "Ensuring that a licensed professional engineer\u0027s seal appears on all submitted plans"
  ],
  "proeth:guidedByPrinciple": [
    "Individual engineer accountability",
    "Transparency in professional responsibility",
    "Public protection through accurate identification of responsible engineers"
  ],
  "proeth:hasAgent": "Engineer A (Chief Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Centralized firm-level accountability vs. individual engineer segment-level accountability required by Code",
    "proeth:resolutionReasoning": "Engineer A prioritized administrative consolidation and his role as the firm\u0027s professional authority, bypassing the Code\u0027s individual accountability requirement without an ethically or legally valid basis for doing so"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide a unified point of professional accountability and streamline the sealing process within the firm, with Engineer A serving as the single responsible professional of record",
  "proeth:requiresCapability": [
    "Detailed technical review of each plan set sufficient to constitute direct control and personal supervision",
    "Full understanding and cognizance of each document bearing his seal"
  ],
  "proeth:temporalMarker": "Ongoing; recurring practice across multiple projects",
  "proeth:violatesObligation": [
    "Code Section II.2.c: each technical segment shall be signed and sealed only by the qualified engineer who prepared that segment",
    "Code Section II.2.b: the sealing engineer must have understanding and cognizance of the work sealed",
    "Obligation to maintain transparent and accurate attribution of professional responsibility"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Sealing Registered Engineers\u0027 Plans Without Their Seals"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Action_Sealing_Non-Registered_Engineers__Plans",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Restrict non-registered graduate engineers to preparatory, computational, or drafting tasks that are fully reviewed and verified by Engineer A or another registered engineer before any seal is affixed, ensuring the licensed professional has directly checked all technical content.",
    "Implement a formal mentorship and review structure in which each non-registered engineer\u0027s work is assigned to a specific registered engineer who exercises direct supervision and affixes their own seal after detailed review, with Engineer A providing oversight at the organizational level.",
    "Decline to seal work produced by non-registered engineers unless Engineer A has personally reviewed the detailed design, calculations, and drawings \u2014 accepting that this limits throughput but ensures compliance with the direct control standard."
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to leverage the capabilities of talented non-registered graduate engineers \u2014 who may be highly competent technically \u2014 while maintaining formal compliance with the requirement that a licensed engineer seal all documents. He likely viewed this as a pragmatic use of available talent, believing his general supervisory involvement was sufficient to ethically bridge the gap between the preparers\u0027 unlicensed status and the legal requirement for a sealed document.",
  "proeth-scenario:consequencesIfAlternative": [
    "Restricting non-registered engineers to reviewed preparatory tasks would slow output but ensure that every sealed document reflects genuine direct supervision, protecting the public, the firm, and Engineer A\u0027s license.",
    "A formal mentorship and review structure would develop non-registered engineers professionally, distribute supervisory responsibility appropriately among licensed staff, and create a documented chain of accountability for every sealed document.",
    "Declining to seal without direct review would reduce the volume of work Engineer A can personally certify, potentially requiring the firm to hire additional registered engineers \u2014 a costly but ethically and legally sound response to the supervision requirement."
  ],
  "proeth-scenario:decisionSignificance": "This action represents the most legally and ethically precarious element of the case. Students learn that sealing work produced by unlicensed individuals requires the highest standard of supervision \u2014 direct control and personal involvement in the technical details \u2014 precisely because there is no independent professional credential to serve as a baseline assurance of competency. The seal in this context is not a rubber stamp of confidence; it is a personal attestation that the licensed engineer has exercised direct professional judgment over the work.",
  "proeth-scenario:ethicalTension": "Organizational productivity and talent utilization versus the heightened duty of care owed to the public when unlicensed individuals produce engineering work. Non-registered engineers have not yet demonstrated to a licensing body that they meet the minimum competency threshold required for independent engineering judgment, making the supervising engineer\u0027s direct oversight even more critical \u2014 not less.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "If work produced by non-registered engineers and sealed by Engineer A without direct control contains errors, the consequences are severe: public safety risk from flawed engineering, potential structural failures or harm, professional license revocation for Engineer A, civil and criminal liability, firm reputational damage, and harm to the non-registered engineers whose careers may be affected by the fallout.",
  "proeth:description": "Engineer A affixes his seal to plans prepared by non-registered graduate engineers working under his general supervision, assuming sole legal and ethical responsibility for work produced by unlicensed individuals without exercising direct control and personal supervision over that work.",
  "proeth:foreseenUnintendedEffects": [
    "Non-registered engineers\u0027 work enters the public domain under a seal that does not reflect direct control and personal supervision",
    "Public safety risk is elevated because unlicensed individuals\u0027 work lacks the independent professional check that individual sealing by a responsible engineer would provide",
    "Engineer A assumes full legal liability for work he cannot have personally reviewed in detail across a large project portfolio"
  ],
  "proeth:fulfillsObligation": [
    "Ensuring a licensed engineer\u0027s seal appears on plans before public submission",
    "Providing some level of technical guidance and consultation to non-registered staff"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety and welfare as paramount obligation",
    "Responsible charge as a non-delegable duty when sealing work by unlicensed individuals",
    "Honest representation of the nature and extent of professional oversight"
  ],
  "proeth:hasAgent": "Engineer A (Chief Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Firm workforce resource utilization vs. heightened ethical obligation for direct supervision of unlicensed engineers\u0027 work",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by extending his general supervision model \u2014 developed for registered engineers \u2014 to non-registered engineers, despite the heightened standard required; the Board found this practice ethically impermissible"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Enable the firm to utilize non-registered graduate engineers as productive design contributors while providing professional cover through Engineer A\u0027s seal, leveraging their technical capabilities within a licensed framework",
  "proeth:requiresCapability": [
    "Direct, hands-on technical review and supervision of each design element produced by non-registered engineers",
    "Capacity to identify and correct errors in work produced by unlicensed individuals before sealing",
    "Personal understanding and cognizance of every document sealed"
  ],
  "proeth:temporalMarker": "Ongoing; recurring practice across multiple projects",
  "proeth:violatesObligation": [
    "Obligation that work by non-registered engineers be performed under direct control and personal supervision of a registered engineer who seals the document (Code Section II.2.b; NCEE Model Law)",
    "Code Section II.2.b: the sealing engineer must possess understanding and cognizance of the sealed work",
    "Obligation to protect public safety by ensuring unlicensed work receives rigorous licensed oversight",
    "Code Section II.2.c: technical segments must be sealed by the qualified engineer who prepared them \u2014 non-registered engineers cannot seal, making direct control by the sealing engineer even more critical"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Sealing Non-Registered Engineers\u0027 Plans"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Action_Consciously_Omitting_Detailed_Design_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Establish a mandatory pre-seal review protocol requiring Engineer A to personally review and document his review of all critical design elements, calculations, and assumptions before affixing his seal to any document, regardless of his confidence in the preparer.",
    "Acknowledge the impossibility of directly reviewing all work across the firm\u0027s project volume and restructure the organization so that sealing authority is distributed among multiple registered engineers who can each exercise genuine direct supervision over a manageable scope of work.",
    "Seek a formal ethics opinion from the NSPE Board of Ethical Review or the relevant state licensing board regarding whether his current oversight model satisfies the \u0027direct control and personal supervision\u0027 standard, and commit to adjusting his practice based on the authoritative response."
  ],
  "proeth-scenario:characterMotivation": "Engineer A rationalized the omission of detailed design review as acceptable on the grounds of his trust in his staff\u0027s competence, his belief that his high-level involvement constituted sufficient oversight, and likely the practical reality that detailed review of all work across a large firm would be time-prohibitive given his other responsibilities. This rationalization allowed him to maintain his self-image as a responsible professional while avoiding the uncomfortable conclusion that his practice was non-compliant.",
  "proeth-scenario:consequencesIfAlternative": [
    "A mandatory pre-seal review protocol would be demanding and might slow document production, but it would ensure that Engineer A\u0027s seal genuinely represents personal technical accountability, protecting the public and his professional standing.",
    "Restructuring sealing authority across multiple engineers is the systemic solution that addresses the root cause \u2014 the mismatch between one engineer\u0027s supervisory capacity and the firm\u0027s document production volume \u2014 and would bring the firm into full compliance.",
    "Seeking a formal ethics opinion would demonstrate good faith, provide authoritative external guidance, and almost certainly result in Engineer A being directed to modify his practice \u2014 allowing him to correct course before a violation is formally adjudicated, potentially preserving his license and reputation."
  ],
  "proeth-scenario:decisionSignificance": "This action is the ethical core of the case and its most important teaching moment. Students learn that rationalization \u2014 the process of constructing post-hoc justifications for a decision already made on other grounds \u2014 is one of the most common and dangerous patterns in professional ethics failures. Engineer A did not arrive at his omission through careful ethical reasoning; he arrived at it through convenience and then constructed a rationale. The case teaches students to recognize rationalization in their own thinking and to test their justifications against external standards rather than internal comfort.",
  "proeth-scenario:ethicalTension": "Personal confidence in subordinates and operational pragmatism versus the non-negotiable public safety obligation encoded in the engineering seal. The seal is a legal and ethical instrument that communicates to the public that a licensed professional has personally verified the work \u2014 not merely trusted others to do so. Confidence in staff competence, however well-founded, is not a substitute for direct professional review.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "The ongoing, explicit decision to omit detailed review is the mechanism by which all downstream risks are realized. Every sealed document produced under this practice is a potential liability event. If any of those documents contain errors that cause harm, Engineer A has no defense \u2014 he cannot claim he reviewed the work, and the record of his practice demonstrates a deliberate choice not to do so. This exposes him to license revocation, civil suits, and potentially criminal charges for professional misconduct.",
  "proeth:description": "Engineer A makes an explicit, ongoing decision not to perform detailed review or checking of designs before affixing his seal, rationalizing this omission as ethically and legally acceptable on the basis of his confidence in the competence of his staff.",
  "proeth:foreseenUnintendedEffects": [
    "Errors or design deficiencies in sealed documents may go undetected by the responsible engineer of record",
    "The professional seal becomes a representation of oversight that did not actually occur at the level the Code requires",
    "Public reliance on the seal as a guarantee of competent review is undermined"
  ],
  "proeth:fulfillsObligation": [
    "None identified with respect to the sealing obligation; general managerial involvement is fulfilled but does not satisfy the sealing standard"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety and welfare as the paramount professional obligation",
    "Integrity of the professional seal as a representation of competent personal oversight",
    "Responsible charge as requiring direct, not merely general, involvement in work product"
  ],
  "proeth:hasAgent": "Engineer A (Chief Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Firm productivity and scalability vs. personal professional obligation to review and understand all sealed work",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by treating staff competence as an ethical substitute for personal review, a rationalization the Board rejected; the Code requires personal understanding and cognizance, not delegated confidence"
  },
  "proeth:hasMentalState": "deliberate and self-rationalized",
  "proeth:intendedOutcome": "Maintain firm productivity and throughput by avoiding the bottleneck that detailed personal review of all designs would create, while believing that staff competence substitutes for personal review as an ethical matter",
  "proeth:requiresCapability": [
    "Technical capacity to review and evaluate engineering designs across the firm\u0027s project domains",
    "Judgment to identify design errors, omissions, and deficiencies in plans prepared by subordinates",
    "Organizational ability to structure review workflows that enable meaningful personal oversight at scale"
  ],
  "proeth:temporalMarker": "Ongoing; established as a deliberate standing policy",
  "proeth:violatesObligation": [
    "Code Section II.2.b: engineer must sign and seal only documents in which he has understanding and cognizance \u2014 omitting detailed review undermines the basis for such cognizance",
    "NCEE Model Law: \u0027direct control and personal supervision\u0027 cannot be satisfied without meaningful review of the work product",
    "Obligation to protect public safety by ensuring engineering designs are personally verified by the responsible engineer before sealing",
    "Obligation of professional honesty \u2014 affixing a seal implies a level of review that Engineer A acknowledges he is not performing"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Consciously Omitting Detailed Design Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Event_Supervision_Standard_Institutionalized",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does positional authority affect the likelihood that a non-compliant practice will go unchallenged within an organization?",
    "At what point does a repeated professional shortcut become an ethical violation rather than a judgment call?",
    "What mechanisms should firms have in place to ensure that senior engineers\u0027 practices remain aligned with legal standards?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A likely feels confident and justified given his seniority and experience; subordinate engineers may feel relieved of burden or uncertain about their own professional responsibilities; external observers would feel concern about systemic risk",
  "proeth-scenario:ethicalImplications": "Reveals tension between experiential confidence and codified professional standards; raises questions about institutional accountability and the ethical risks of self-referential standard-setting by authority figures; highlights how organizational culture can silently erode professional obligations",
  "proeth-scenario:learningMoment": "Illustrates how professional misconduct can become normalized over time when authority figures define their own standards rather than adhering to established legal and ethical requirements. The slow institutionalization of a flawed practice is often more dangerous than a single isolated error.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Accumulating ethical and legal liability without awareness; professional reputation at latent risk",
    "firm": "Institutional culture misaligned with professional standards; systemic legal exposure",
    "non_registered_graduate_engineers": "Work is sealed without adequate oversight, creating risk of unchecked errors reaching clients and the public",
    "public": "Receives engineering documents that may not have received the legally required level of expert review",
    "subordinate_registered_engineers": "Abdication of individual professional sealing responsibility; potential complicity in non-compliant practice"
  },
  "proeth:activatesConstraint": [
    "Professional_Competence_Constraint",
    "Code_Compliance_Obligation",
    "Seal_Authenticity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/163#Action_Defining_General_Supervision_Standard",
  "proeth:causesStateChange": "Firm\u0027s internal practice diverges from legal and ethical standards; a culture of inadequate oversight becomes entrenched; subordinate engineers are implicitly relieved of individual sealing responsibility contrary to regulation",
  "proeth:createsObligation": [
    "Obligation_To_Review_Firm_Practices",
    "Obligation_To_Align_With_Legal_Standard",
    "Obligation_To_Inform_Subordinates_Of_Correct_Standard"
  ],
  "proeth:description": "Engineer A\u0027s self-defined \u0027general supervision\u0027 standard becomes the de facto institutional practice within the firm, replacing the legally required \u0027direct control and personal supervision\u0027 standard. This normalization occurs gradually as the practice is repeated without challenge.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Early in Engineer A\u0027s tenure as Chief Engineer; ongoing over time",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Supervision Standard Institutionalized"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Event_Registered_Engineers_Relieved_of_Sealing",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What is the purpose of requiring individual engineers to seal their own work, and what is lost when that requirement is bypassed?",
    "Do subordinate registered engineers bear any ethical responsibility for allowing their work to be sealed by another without their own seal?",
    "How should a registered engineer respond if a superior instructs them not to affix their seal to their own work?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Registered engineers may feel relieved of administrative burden or quietly uncomfortable about their professional abdication; Engineer A feels justified by his oversight role; external reviewers or regulators discovering this would feel alarm",
  "proeth-scenario:ethicalImplications": "Exposes the conflict between hierarchical organizational authority and individual professional responsibility; raises questions about complicity and professional courage among subordinate engineers; highlights how systemic practices can obscure individual accountability",
  "proeth-scenario:learningMoment": "Demonstrates that professional seals are not merely administrative formalities but legal and ethical attestations of personal responsibility. When sealing practices deviate from regulations, the entire system of professional accountability is weakened.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "clients": "May believe documents have been reviewed by the engineer whose seal appears, without understanding the supervision gap",
    "engineer_a": "Bears sole documented professional responsibility for work he did not personally perform in sufficient detail",
    "public": "Reduced assurance that engineering documents reflect the professional judgment of the engineers who prepared them",
    "regulatory_bodies": "Enforcement of individual professional accountability is undermined",
    "subordinate_registered_engineers": "Individual professional records do not reflect their actual design work; potential loss of professional accountability and credit"
  },
  "proeth:activatesConstraint": [
    "Individual_Professional_Responsibility_Constraint",
    "Seal_Authenticity_Constraint",
    "Code_Compliance_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/163#Action_Sealing_Registered_Engineers__Plans_Without_Their_",
  "proeth:causesStateChange": "Professional accountability chain is broken; registered engineers\u0027 individual responsibility is obscured; documents enter the public record without the professional attestation required by law from the engineers who prepared them",
  "proeth:createsObligation": [
    "Obligation_For_Registered_Engineers_To_Assert_Sealing_Rights",
    "Obligation_For_Registered_Engineers_To_Report_Non_Compliant_Practice",
    "Obligation_For_Engineer_A_To_Restore_Individual_Sealing_Accountability"
  ],
  "proeth:description": "As a direct outcome of Engineer A\u0027s sealing practice, registered engineers under his direction are effectively relieved of their individual professional sealing obligations, creating a structural gap in the chain of professional accountability required by engineering regulations.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Concurrent with and ongoing throughout Engineer A\u0027s sealing practice",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Registered Engineers Relieved of Sealing"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Event_Non-Registered_Work_Enters_Public_Record",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What specific harms could result if a non-registered engineer\u0027s unreviewed design error reaches construction or implementation?",
    "How does the public\u0027s reliance on professional seals change the ethical weight of sealing decisions?",
    "Should there be mandatory audits of sealed documents when supervision practices are found to be non-compliant?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A is confident and unaware of risk; non-registered engineers may feel validated but are unaware of the liability gap; the public is entirely unaware; regulators and ethics reviewers feel significant concern upon discovery",
  "proeth-scenario:ethicalImplications": "Reveals the deepest tension in this case: the professional seal as a public trust instrument versus its use as an administrative convenience; raises questions about the engineer\u0027s duty to the public versus loyalty to organizational efficiency; highlights how the erosion of supervision standards directly threatens the foundational promise of professional engineering",
  "proeth-scenario:learningMoment": "Illustrates the highest-stakes consequence of inadequate supervision: engineering work that may contain unchecked errors reaches the public under the false assurance of professional certification. The seal is only as meaningful as the supervision behind it.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "clients": "Received documents that do not carry the professional assurance they appear to carry",
    "engineer_a": "Maximum professional and legal liability for work he cannot fully attest to; potential license revocation",
    "non_registered_graduate_engineers": "Work is in use without adequate professional validation; if errors exist, they may cause harm without any registered engineer having truly verified the work",
    "public": "Exposed to potential safety risks from engineering work that lacked required oversight; trust in engineering credentials undermined",
    "regulatory_bodies": "Integrity of the professional seal system is compromised"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Seal_Authenticity_Constraint",
    "Direct_Control_Supervision_Constraint",
    "Competence_Verification_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/163#Action_Sealing_Non-Registered_Engineers__Plans",
  "proeth:causesStateChange": "Engineering documents prepared without adequate registered oversight are in active use; public safety risk is latent; professional misrepresentation is embedded in the official record",
  "proeth:createsObligation": [
    "Obligation_To_Audit_Previously_Sealed_Documents",
    "Obligation_To_Implement_Direct_Supervision_Going_Forward",
    "Obligation_To_Disclose_Supervision_Gap_If_Safety_Risk_Identified"
  ],
  "proeth:description": "Plans prepared by non-registered graduate engineers, sealed solely by Engineer A under general supervision, are completed and enter the public and professional record as if they carry the full weight of direct professional oversight, when in fact they do not.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Ongoing throughout Engineer A\u0027s practice of sealing non-registered engineers\u0027 plans",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Non-Registered Work Enters Public Record"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Event_Ethics_Violation_Determination_Reached",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Why is it insufficient for an experienced senior engineer to rely on his own judgment about what constitutes adequate supervision, rather than the standard established by the profession?",
    "How should the existence of prior case precedent (Case 85-3) have influenced Engineer A\u0027s practice before this review occurred?",
    "What reforms to firm practice and individual behavior would be required to bring Engineer A into compliance going forward?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences shock, defensiveness, and professional distress; subordinate engineers may feel anxiety about their own exposure; the engineering community observing the case gains clarity on the standard; ethics reviewers feel the weight of establishing precedent",
  "proeth-scenario:ethicalImplications": "Crystallizes the central ethical tension of the case: individual professional judgment versus codified professional standards; reveals how good intentions and genuine competence do not excuse non-compliance with rules designed to protect the public; demonstrates the profession\u0027s self-regulatory function and its importance for public trust",
  "proeth-scenario:learningMoment": "Demonstrates that professional confidence and seniority do not substitute for compliance with established legal and ethical standards. The formal determination illustrates how the ethics review process functions to protect the public and the profession, and why precedent matters in professional ethics.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "clients_and_public": "Gain assurance that the professional standards system is functioning; latent risks from past documents may need review",
    "engineer_a": "Formal finding of ethical violation; potential license suspension or revocation; reputational damage; requirement to reform practice",
    "engineering_profession": "Precedent is reinforced; the meaning and weight of the professional seal is publicly reaffirmed",
    "firm": "Must overhaul supervision and sealing practices; potential legal liability review for past projects",
    "subordinate_engineers": "Indirect exposure; may need to re-examine their own professional conduct and obligations"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Professional_Discipline_Constraint",
    "Corrective_Action_Obligation",
    "Code_Compliance_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/163#Action_Consciously_Omitting_Detailed_Design_Review",
  "proeth:causesStateChange": "Engineer A\u0027s practice is formally classified as ethically and legally non-compliant; the self-defined supervision standard is invalidated; professional consequences are now triggered; the firm\u0027s sealing practices must be reformed",
  "proeth:createsObligation": [
    "Obligation_For_Engineer_A_To_Cease_Non_Compliant_Sealing",
    "Obligation_To_Implement_Direct_Control_Supervision_Standard",
    "Obligation_For_Firm_To_Review_Previously_Sealed_Documents",
    "Obligation_To_Cooperate_With_Disciplinary_Process"
  ],
  "proeth:description": "Following analysis against applicable Code provisions and prior case precedent (Case 85-3, 1985), the reviewing body determines that Engineer A\u0027s level of oversight does not meet the ethical and legal standard of \u0027direct control and personal supervision\u0027 required for sealing documents, constituting a formal finding of ethical violation.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During the Discussion/Analysis phase of the ethics case review; after the practice is examined",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Ethics Violation Determination Reached"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#Event_Precedent_Standard_Activated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What responsibility does a Chief Engineer have to stay current with ethics rulings and precedents that affect their supervisory practices?",
    "How does the existence of prior precedent change the moral assessment of Engineer A\u0027s conduct \u2014 does it make it worse, better, or the same?",
    "Should professional ethics precedents be more widely disseminated to practicing engineers, and whose responsibility is that?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Ethics reviewers gain confidence and clarity; Engineer A (upon learning of the precedent) may feel that the standard was pre-established and that he should have known it; students observing the case feel the weight of professional precedent as a real constraint",
  "proeth-scenario:ethicalImplications": "Highlights the tension between individual professional judgment and the profession\u0027s collective, codified wisdom; raises questions about the accessibility and awareness of professional ethics precedents; demonstrates how the self-regulatory system of the engineering profession operates through accumulated case law",
  "proeth-scenario:learningMoment": "Illustrates the importance of professional precedent as a real constraint on engineering practice. Engineers must be aware of prior rulings and established interpretations of professional codes, not merely their own reading of the rules. Ignorance of precedent does not excuse non-compliance.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "clients_and_public": "Benefit from consistent enforcement of protective professional standards",
    "engineer_a": "His self-defined standard is formally invalidated by an authoritative prior ruling he may not have been aware of or heeded",
    "engineering_profession": "Consistency and predictability of professional standards is reinforced; the precedent system is shown to function",
    "future_engineers": "Gain clear guidance on what supervision standard is required before sealing others\u0027 work"
  },
  "proeth:activatesConstraint": [
    "Precedent_Compliance_Constraint",
    "Direct_Control_Supervision_Constraint",
    "Seal_Authenticity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/163#Action_Defining_General_Supervision_Standard",
  "proeth:causesStateChange": "The interpretive framework for evaluating Engineer A\u0027s conduct is fixed by precedent; Engineer A\u0027s self-defined standard is displaced by the profession\u0027s established standard; the outcome of the ethics review becomes more predictable and certain",
  "proeth:createsObligation": [
    "Obligation_To_Apply_Established_Standard_To_Engineer_A_Conduct",
    "Obligation_To_Evaluate_Supervision_Against_Direct_Control_Threshold"
  ],
  "proeth:description": "The prior ethics ruling in Case 85-3 (1985) is applied as binding precedent to Engineer A\u0027s situation, automatically triggering the established interpretation of \u0027direct control and personal supervision\u0027 as the applicable standard against which Engineer A\u0027s conduct is measured.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "During the ethics case analysis/discussion phase, when Case 85-3 is identified and applied",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Precedent Standard Activated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#CausalChain_7f14abdb",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A deliberately defines \u0027general direction and supervision\u0027 as involvement in concept establishment, which becomes the de facto institutional practice",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A accepts positional authority that grants him power to define supervision standards firm-wide",
      "proeth:element": "Accepting Chief Engineer Role",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A deliberately narrows \u0027general direction and supervision\u0027 to concept-level involvement only",
      "proeth:element": "Defining General Supervision Standard",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A operationalizes his definition by explicitly not performing detailed checks",
      "proeth:element": "Consciously Omitting Detailed Design Review",
      "proeth:step": 3
    },
    {
      "proeth:description": "The self-defined standard becomes the de facto norm across the firm\u0027s engineering practice",
      "proeth:element": "Supervision Standard Institutionalized",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Defining General Supervision Standard",
  "proeth:counterfactual": "Without Engineer A\u0027s deliberate redefinition, the standard supervision practice would have remained aligned with professional code requirements; institutionalization would not have occurred",
  "proeth:effect": "Supervision Standard Institutionalized",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s authority as Chief Engineer to set institutional standards",
    "Deliberate self-definition of supervision scope",
    "Absence of external correction or override of the standard",
    "Ongoing application of the standard across high-volume work"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Chief Engineer authority + deliberate definitional act + institutional deference to role = institutionalization of substandard supervision norm"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#CausalChain_fb9e015a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A affixes his own seal to plans prepared by registered engineers working under his general direction, and as a direct outcome registered engineers under his direction are effectively relieved of sealing responsibility",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A defines supervision as concept-level, creating justification for sole sealing without detailed review",
      "proeth:element": "Defining General Supervision Standard",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A affixes only his seal to plans prepared by registered subordinate engineers",
      "proeth:element": "Sealing Registered Engineers\u0027 Plans Without Their Seals",
      "proeth:step": 2
    },
    {
      "proeth:description": "Registered engineers are effectively absolved of their individual professional sealing obligations",
      "proeth:element": "Registered Engineers Relieved of Sealing",
      "proeth:step": 3
    },
    {
      "proeth:description": "The displacement of sealing accountability is identified as a Code violation upon ethics review",
      "proeth:element": "Ethics Violation Determination Reached",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Sealing Registered Engineers\u0027 Plans Without Their Seals",
  "proeth:counterfactual": "If Engineer A had required registered engineers to seal their own work, individual professional accountability would have been preserved and the displacement of responsibility would not have occurred",
  "proeth:effect": "Registered Engineers Relieved of Sealing",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s unilateral decision to seal plans prepared by others",
    "Registered engineers\u0027 acquiescence or inability to override Engineer A\u0027s sealing practice",
    "Absence of firm or regulatory mechanism requiring co-sealing by the preparing engineer",
    "Engineer A\u0027s positional authority as Chief Engineer"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Chief Engineer authority + unilateral sealing practice + subordinate registered engineers\u0027 deference = systematic displacement of individual professional accountability"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#CausalChain_4d434180",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A affixes his seal to plans prepared by non-registered graduate engineers working under his general supervision, and plans prepared by non-registered graduate engineers, sealed solely by Engineer A under general supervision, enter the public record",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A explicitly decides not to perform detailed review of designs, including those by non-registered engineers",
      "proeth:element": "Consciously Omitting Detailed Design Review",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A affixes his professional seal, certifying plans he has not substantively reviewed",
      "proeth:element": "Sealing Non-Registered Engineers\u0027 Plans",
      "proeth:step": 2
    },
    {
      "proeth:description": "Unverified plans by non-licensed engineers are submitted and recorded as professionally certified documents",
      "proeth:element": "Non-Registered Work Enters Public Record",
      "proeth:step": 3
    },
    {
      "proeth:description": "The sealing of inadequately supervised non-registered work is confirmed as a Code violation",
      "proeth:element": "Ethics Violation Determination Reached",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Sealing Non-Registered Engineers\u0027 Plans",
  "proeth:counterfactual": "If Engineer A had either performed detailed review before sealing or declined to seal work he had not adequately supervised, non-registered work would not have entered the public record under false certification",
  "proeth:effect": "Non-Registered Work Enters Public Record",
  "proeth:necessaryFactors": [
    "Non-registered engineers preparing plans without independent licensure",
    "Engineer A\u0027s decision to seal those plans with only concept-level supervision",
    "Consciously omitting detailed design review of non-registered engineers\u0027 work",
    "No intervening qualified review before public submission"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Non-registered authorship + Engineer A\u0027s sole seal under inadequate supervision + omission of detailed review = unverified non-registered work entering public record as professionally certified"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#CausalChain_aff97bd1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A makes an explicit, ongoing decision not to perform detailed review or checking of designs; following analysis against applicable Code provisions and prior case precedent (Case 85-3, 1985), the ethics violation determination is reached",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A establishes a self-serving, narrow definition of supervision that excludes detailed review",
      "proeth:element": "Defining General Supervision Standard",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A operationalizes the standard by explicitly not reviewing designs in detail before sealing",
      "proeth:element": "Consciously Omitting Detailed Design Review",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A seals plans across both categories without adequate supervisory review",
      "proeth:element": "Sealing Non-Registered Engineers\u0027 Plans and Registered Engineers\u0027 Plans Without Their Seals",
      "proeth:step": 3
    },
    {
      "proeth:description": "Case 85-3 (1985) is applied as binding precedent, establishing the analytical standard against which Engineer A\u0027s conduct is measured",
      "proeth:element": "Precedent Standard Activated",
      "proeth:step": 4
    },
    {
      "proeth:description": "Ethics review body concludes Engineer A\u0027s conduct violates applicable Code provisions based on facts and precedent",
      "proeth:element": "Ethics Violation Determination Reached",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Consciously Omitting Detailed Design Review",
  "proeth:counterfactual": "If Engineer A had performed detailed review before sealing, the core factual predicate for the ethics violation would have been absent, and the determination would likely not have been reached",
  "proeth:effect": "Ethics Violation Determination Reached",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s explicit and ongoing omission of detailed design review",
    "Engineer A\u0027s sealing of plans without adequate supervision",
    "Existence of applicable Code provisions prohibiting such conduct",
    "Activation of Case 85-3 precedent as binding standard",
    "Ethics review body\u0027s analysis of the conduct against Code and precedent"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Documented omission of detailed review + sealing practice + Code provisions + binding precedent from Case 85-3 = sufficient basis for ethics violation determination"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/163#",
    "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/163#CausalChain_7793985c",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The prior ethics ruling in Case 85-3 (1985) is applied as binding precedent to Engineer A\u0027s situation; following analysis against applicable Code provisions and prior case precedent, the ethics violation determination is reached",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A\u0027s substandard supervision norm becomes embedded in firm practice, creating a documentable pattern of conduct",
      "proeth:element": "Supervision Standard Institutionalized",
      "proeth:step": 1
    },
    {
      "proeth:description": "Inadequately supervised plans enter public record, providing concrete evidence of the supervision and sealing practice",
      "proeth:element": "Non-Registered Work Enters Public Record",
      "proeth:step": 2
    },
    {
      "proeth:description": "Ethics review body identifies Case 85-3 (1985) as directly applicable and applies it as binding precedent",
      "proeth:element": "Precedent Standard Activated",
      "proeth:step": 3
    },
    {
      "proeth:description": "Convergence of Code provisions, factual record, and binding precedent produces the violation determination",
      "proeth:element": "Ethics Violation Determination Reached",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Precedent Standard Activated",
  "proeth:counterfactual": "Without Case 85-3 as binding precedent, the ethics determination might have required more extensive original analysis; however, given the Code provisions independently applicable, the determination would likely still have been reached, making the precedent a reinforcing rather than strictly necessary cause",
  "proeth:effect": "Ethics Violation Determination Reached",
  "proeth:necessaryFactors": [
    "Existence of Case 85-3 (1985) as established prior ruling",
    "Factual similarity between Engineer A\u0027s conduct and the conduct addressed in Case 85-3",
    "Ethics review body\u0027s recognition and application of the precedent",
    "Engineer A\u0027s conduct meeting the threshold established by the precedent"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Binding precedent from Case 85-3 + factual similarity of Engineer A\u0027s conduct + ethics body\u0027s application = sufficient analytical foundation for violation determination even absent new Code interpretation"
  ],
  "proeth:withinAgentControl": true
}