{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Action_Sign_and_Seal_Own_CADD_Work",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Refuse to use CADD and insist on manual drafting to avoid any ambiguity about personal preparation",
    "Delegate CADD production to technicians and seal the result without conducting a detailed review, conflating Engineer A\u0027s scenario with Engineer B\u0027s",
    "Seek a formal advisory opinion before sealing any CADD-produced documents, halting workflow pending clarification"
  ],
  "proeth-scenario:characterMotivation": "Engineer A seeks to fulfill professional obligations using modern technology while maintaining clear personal accountability, ensuring that the adoption of CADD tools does not erode the foundational principle that an engineer stands behind work they directly produced.",
  "proeth-scenario:consequencesIfAlternative": [
    "Refusing CADD would render Engineer A uncompetitive and technologically obsolete without any ethical benefit, since the tool does not change the nature of personal preparation",
    "Sealing delegated work without proper review would collapse the ethical distinction between Engineers A and B, exposing the public to unverified designs and Engineer A to disciplinary action",
    "Seeking an advisory opinion first would be prudent but would delay projects and might reveal the very ambiguity that BER Case 86-2 had already created, forcing earlier resolution of the 1986 controversy"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the baseline, unambiguous case of ethical sealing practice \u2014 when an engineer personally produces and seals their own work, establishing the reference standard against which more complex delegation scenarios can be measured.",
  "proeth-scenario:ethicalTension": "Embracing technological advancement (CADD) while preserving traditional standards of personal professional responsibility; the tension between efficiency gains from new tools and the integrity of the professional seal as a personal attestation.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Public safety depends on the seal accurately representing who is responsible for the work; if CADD-produced documents are treated as categorically different from hand-drafted ones, a dangerous regulatory gap could emerge. Engineer A\u0027s credibility and license are also at risk if standards are misapplied.",
  "proeth:description": "Engineer A personally prepares documents using a CADD system and then signs and seals those documents, taking full professional responsibility for work he directly produced.",
  "proeth:foreseenUnintendedEffects": [
    "Sets a precedent for CADD document authentication",
    "Implies personal preparation is sufficient basis for sealing without necessarily requiring deeper review protocols"
  ],
  "proeth:fulfillsObligation": [
    "Only sealing documents he personally prepared",
    "Exercising direct professional responsibility over work product",
    "Maintaining competence over CADD tools used in preparation",
    "Adhering to Code requirement not to seal documents not prepared under direction and control"
  ],
  "proeth:guidedByPrinciple": [
    "Personal professional accountability",
    "Competence in tools and methods used",
    "Integrity of the professional seal"
  ],
  "proeth:hasAgent": "Engineer A (Registered Professional Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Reliance on CADD system outputs vs. independent professional judgment",
    "proeth:resolutionReasoning": "Engineer A resolves the tradeoff by virtue of personal preparation, which is the clearest basis for sealing under the Code; however, the discussion notes that even personal use of CADD requires competence in the system\u0027s limitations"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Formally certify and authenticate CADD-produced documents that he personally prepared, fulfilling professional registration obligations",
  "proeth:requiresCapability": [
    "Proficiency with CADD systems including understanding of system limitations",
    "Engineering judgment to evaluate CADD-generated outputs",
    "Knowledge of applicable design standards and codes"
  ],
  "proeth:temporalMarker": "Present case",
  "proeth:withinCompetence": true,
  "rdfs:label": "Sign and Seal Own CADD Work"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Action_Seal_Others__CADD_Documents",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Refuse to seal any document not personally prepared, forcing all subordinates to obtain their own licenses before their work can be submitted",
    "Seal the documents after only a cursory review, treating the seal as an administrative formality rather than a substantive professional attestation",
    "Develop and document a formal internal review protocol \u2014 checklists, sign-off sheets, review meetings \u2014 to make \u0027direction and control\u0027 transparent and auditable before sealing"
  ],
  "proeth-scenario:characterMotivation": "Engineer B seeks to leverage a team of subordinates to scale professional output beyond what a single engineer could personally produce, believing that active direction, control, and review of others\u0027 work is sufficient to justify placing a professional seal on the resulting documents.",
  "proeth-scenario:consequencesIfAlternative": [
    "Refusing to seal subordinates\u0027 work would make large-scale engineering practice nearly impossible, since most firms rely on licensed engineers overseeing teams; it would also contradict decades of accepted practice and harm project delivery",
    "Cursory review before sealing would be the most dangerous outcome \u2014 it creates the appearance of professional accountability without the substance, directly endangering public safety and exposing Engineer B to fraud and negligence liability",
    "Implementing a documented review protocol would represent best practice, providing a defensible record of responsible charge and potentially serving as a model standard for the profession \u2014 though it requires significant process investment"
  ],
  "proeth-scenario:decisionSignificance": "This is the central ethical dilemma of the case \u2014 it forces students to grapple with what the professional seal actually certifies and how much delegation is permissible before the seal becomes misleading or fraudulent. It highlights that most real-world engineering involves supervised teams, making this tension unavoidable.",
  "proeth-scenario:ethicalTension": "Organizational efficiency and the practical reality of engineering practice (work is always collaborative) versus the strict interpretation of personal accountability embedded in the professional seal; the risk that \u0027direction and control\u0027 becomes a rubber-stamp justification for inadequate oversight.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "If Engineer B\u0027s oversight is genuinely rigorous, public safety is preserved and professional practice is sustainable. If \u0027direction and control\u0027 is superficial, flawed designs may enter the built environment under the false assurance of a professional seal. Engineer B\u0027s license, reputation, and legal liability are all at stake, as is the credibility of the sealing system itself.",
  "proeth:description": "Engineer B signs and seals CADD-produced documents that were prepared by other individuals working under Engineer B\u0027s direction and control, taking professional responsibility for work he did not personally produce.",
  "proeth:foreseenUnintendedEffects": [
    "Assumes legal and professional liability for work not personally executed",
    "Risk that direction and control may be insufficient to fully understand all CADD-generated design decisions",
    "May normalize delegation of CADD work without sufficiently rigorous review protocols"
  ],
  "proeth:fulfillsObligation": [
    "Exercising direction and control over subordinates producing the documents",
    "Assuming full professional responsibility for the work product",
    "Operating within the clarified standard requiring detailed review rather than personal preparation"
  ],
  "proeth:guidedByPrinciple": [
    "Responsible charge as the basis for professional sealing",
    "Delegation to qualified subordinates under meaningful supervision",
    "Professional accountability for the final work product",
    "Competence in overseeing CADD-based workflows"
  ],
  "proeth:hasAgent": "Engineer B (Registered Professional Engineer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Organizational productivity through delegation vs. depth of personal review required for ethical sealing",
    "proeth:resolutionReasoning": "Engineer B resolves the tradeoff by relying on the direction and control framework, consistent with the Board\u0027s clarified standard; the ethical permissibility depends entirely on whether the review is sufficiently detailed rather than merely general supervision"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Formally certify documents produced by subordinates under his supervision, fulfilling the responsible charge role while leveraging team-based CADD production",
  "proeth:requiresCapability": [
    "Competence in CADD systems and their limitations to meaningfully review subordinates\u0027 outputs",
    "Engineering judgment to evaluate and check CADD-generated designs in detail",
    "Supervisory and organizational capability to maintain meaningful direction and control",
    "Ability to identify errors or inappropriate reliance on CADD outputs by subordinates"
  ],
  "proeth:temporalMarker": "Present case",
  "proeth:violatesObligation": [
    "Potential violation of obligation to check and review plans in sufficient detail if direction and control is only general rather than specific",
    "Risk of violating obligation not to seal documents not adequately reviewed if CADD outputs are accepted without full scrutiny"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Seal Others\u0027 CADD Documents"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Action_Adopt_Strict_Sealing_Interpretation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Issue a more nuanced 1986 ruling that distinguishes between rubber-stamp supervision and genuine responsible charge, avoiding the strict personal-preparation standard",
    "Decline to rule on the broader sealing question in 1986 and refer the matter to state licensing boards for statutory clarification",
    "Adopt the strict standard but include explicit safe-harbor provisions defining what level of review would satisfy \u0027checked in detail\u0027 for supervised work"
  ],
  "proeth-scenario:characterMotivation": "The 1986 Board sought to protect public safety and the integrity of the professional seal by drawing a bright, unambiguous line: the seal means the named engineer personally did or checked the work in detail. Faced with emerging CADD technology and uncertainty about delegation, the Board prioritized caution and literal textual interpretation of licensing statutes.",
  "proeth-scenario:consequencesIfAlternative": [
    "A nuanced 1986 ruling would have avoided a decade of controversy and might have preemptively established the standard the present Board ultimately reaches, saving the profession significant uncertainty \u2014 but it would have required the Board to resolve ambiguities it may not have felt ready to address",
    "Declining to rule would have left practitioners without guidance during a critical technological transition period, potentially resulting in inconsistent state-level standards and continued ethical confusion",
    "Including safe-harbor provisions would have made the strict standard more workable in practice, but defining \u0027checked in detail\u0027 precisely enough to be useful would itself have been a complex undertaking that might have generated further controversy"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethics rulings have long-term consequences and can create unintended contradictions with professional practice norms. Teaches students that overly rigid ethical standards, even when well-intentioned, can generate their own ethical problems by making routine good-faith practice technically impermissible.",
  "proeth-scenario:ethicalTension": "The value of clear, enforceable bright-line rules that prevent abuse versus the practical reality that engineering has always involved supervised teams; strict literalism protects against rubber-stamping but may render legitimate, well-supervised collaborative work technically unethical, undermining the profession\u0027s ability to function.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The 1986 ruling, if left standing, would effectively prohibit standard engineering firm structures where licensed engineers supervise teams. It risked either mass non-compliance (engineers sealing work they didn\u0027t personally prepare, now technically unethical) or paralysis of engineering practice. The ruling\u0027s credibility and the Board\u0027s authority were also at stake if the standard proved unworkable.",
  "proeth:description": "In BER Case 86-2 (1986), the Board decided it was unethical for a chief engineer to seal plans not personally prepared or checked in detail, even when those plans were prepared by registered engineers under his general supervision, establishing a strict literal reading of \u0027direction and control.\u0027",
  "proeth:foreseenUnintendedEffects": [
    "May impose an impractical standard inconsistent with prevailing engineering practice",
    "Could place a significant number of practitioners in conflict with the Code",
    "May discourage appropriate delegation within large engineering organizations"
  ],
  "proeth:fulfillsObligation": [
    "Literal enforcement of Code Section II.2.b on direction and control",
    "Protecting public safety by ensuring engineers have direct knowledge of sealed work",
    "Maintaining the integrity and meaning of the professional seal"
  ],
  "proeth:guidedByPrinciple": [
    "Strict textual interpretation of the Code",
    "Public safety and protection",
    "Professional accountability through direct personal knowledge"
  ],
  "proeth:hasAgent": "NSPE Board of Ethical Review (BER Case 86-2)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Rigorous public protection through strict personal preparation requirements vs. practical feasibility of engineering practice in large organizations",
    "proeth:resolutionReasoning": "The 1986 Board resolved the conflict in favor of strict interpretation, prioritizing the literal Code standard over practical feasibility, a position later clarified by the present Board as imposing an impossible standard"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Protect public safety and professional integrity by requiring engineers to have direct, detailed knowledge of all work they seal, preventing rubber-stamping of others\u0027 work",
  "proeth:requiresCapability": [
    "Interpretation of Code language and authoritative legal sources",
    "Understanding of engineering practice norms and organizational structures",
    "Ethical reasoning and precedent analysis"
  ],
  "proeth:temporalMarker": "1986, BER Case 86-2",
  "proeth:violatesObligation": [
    "Obligation to establish a realistic and credible ethical standard consistent with prevailing professional practice",
    "Obligation to avoid imposing an impossible or idealistic standard that undermines Code adherence"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Adopt Strict Sealing Interpretation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Action_Clarify_and_Modify_1986_Ruling",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Reaffirm the 1986 strict standard and call on state legislatures to modernize licensing statutes to accommodate team-based practice, rather than modifying the ethical interpretation",
    "Adopt an even more permissive standard that requires only general supervision rather than detailed review, prioritizing practice efficiency over rigorous oversight",
    "Decline to issue a general clarification and instead rule narrowly on the specific facts of Engineers A and B without disturbing the 1986 precedent"
  ],
  "proeth-scenario:characterMotivation": "The present Board recognizes that the 1986 strict standard, while well-intentioned, is inconsistent with the practical realities of engineering practice and the way technology has evolved. The Board is motivated to restore a workable ethical standard that protects public safety through substantive oversight rather than the impossible requirement of personal preparation of all work, and to restore the profession\u0027s confidence in the Board\u0027s guidance.",
  "proeth-scenario:consequencesIfAlternative": [
    "Reaffirming the strict standard while deferring to legislatures would preserve Board consistency but leave practitioners in limbo for years during a slow legislative process, continuing to force a choice between compliance and functional engineering practice",
    "Adopting a general-supervision-only standard would go too far, weakening the professional seal to the point where it provides little meaningful assurance to the public \u2014 effectively gutting the accountability function of licensure",
    "A narrow ruling on Engineers A and B without disturbing 1986 precedent would resolve the immediate case but perpetuate the underlying ambiguity, guaranteeing future cases would relitigate the same tension without the benefit of clear guidance"
  ],
  "proeth-scenario:decisionSignificance": "This is the capstone teaching moment of the entire case: it shows students that ethical standards are not static, that professional bodies must adapt interpretations to technological and practical realities, and that \u0027responsible charge\u0027 \u2014 defined by genuine oversight, detailed review, and accountability \u2014 is the true ethical core of the sealing requirement, not the mechanical act of personal drafting.",
  "proeth-scenario:ethicalTension": "Institutional consistency and respect for precedent (overturning a prior ruling risks undermining the Board\u0027s authority and predictability) versus the obligation to correct a standard that has proven unworkable and potentially harmful to legitimate professional practice; also, the tension between public safety through strict rules versus public safety through practical, enforceable standards that engineers will actually follow.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "If the Board fails to clarify, thousands of engineers continue operating under an unworkable standard, either violating it routinely (normalizing non-compliance) or hobbling their practices unnecessarily. A poorly crafted clarification could swing too far in the other direction, enabling rubber-stamp sealing. The Board\u0027s own credibility and the legitimacy of the ethics advisory system depend on producing a standard that is both principled and practical.",
  "proeth:description": "The present Board decides to clarify and effectively modify the strict standard established in BER Case 86-2, concluding that personal preparation of all sealed documents is not required, provided the engineer conducts a detailed review, assumes full responsible charge, and carefully directs and controls the work.",
  "proeth:foreseenUnintendedEffects": [
    "Risk that lowering the personal preparation requirement could be interpreted as permitting insufficient review",
    "May be perceived as accommodating convenience or common but potentially problematic practices rather than upholding rigorous standards",
    "Could create ambiguity about what constitutes \u0027sufficient detail\u0027 in review, leading to inconsistent application"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to ensure the Code reflects and is consistent with generally prevailing professional practices",
    "Obligation to establish a realistic and credible benchmark rather than an impossible standard",
    "Maintaining public protection through the requirement of detailed review and responsible charge",
    "Ensuring the Code maintains adherence by being practically enforceable"
  ],
  "proeth:guidedByPrinciple": [
    "Responsible charge as the operative standard for sealing delegated work",
    "Code of Ethics as a living document responsive to professional evolution",
    "Balancing rigorous accountability with practical feasibility",
    "Public protection through meaningful rather than nominal review"
  ],
  "proeth:hasAgent": "NSPE Board of Ethical Review (Present Case)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Maintaining rigorous ethical standards vs. adapting the Code to reflect technological and organizational realities of modern engineering practice",
    "proeth:resolutionReasoning": "The Board resolves the conflict by anchoring the modified standard in the requirement for detailed review and full responsible charge, arguing this preserves meaningful accountability while acknowledging the practical realities of modern engineering practice; the Board explicitly frames the change as clarification to preserve institutional continuity"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Establish a realistic, credible, and enforceable ethical standard for sealing CADD-produced documents that reflects prevailing professional practice while maintaining meaningful accountability and public protection",
  "proeth:requiresCapability": [
    "Ethical reasoning and Code interpretation",
    "Understanding of modern engineering organizational structures and CADD workflows",
    "Ability to balance competing principles of public protection and professional practicality",
    "Precedent analysis and institutional reasoning"
  ],
  "proeth:temporalMarker": "Present case, Board deliberation",
  "proeth:violatesObligation": [
    "Risk of weakening the standard of personal accountability associated with the professional seal",
    "Potential tension with the obligation to prioritize public safety above professional convenience"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Clarify and Modify 1986 Ruling"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Event_Drafting_Technology_Evolution",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "When a new technology changes how work is performed, who is responsible for updating professional ethical standards, and how quickly must they act?",
    "Does the introduction of CADD genuinely change what it means for an engineer to \u0027prepare\u0027 a document, or only the mechanism of preparation?",
    "How should engineering ethics anticipate future technologies like AI rather than always reacting after adoption?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Excitement and optimism among technology-forward engineers; anxiety and resistance among traditionalists; uncertainty across the profession about what professional responsibility means in a new technological context",
  "proeth-scenario:ethicalImplications": "Reveals the tension between static codified standards and a dynamic technological environment; raises questions about whether professional responsibility is tied to the act of creation or the act of oversight; foreshadows the AI question explicitly mentioned in the narrative",
  "proeth-scenario:learningMoment": "Technological change does not automatically update professional ethical standards; the profession must actively revisit obligations when the context of practice changes fundamentally. Students should recognize that ethics codes are written in historical moments and require reinterpretation.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "clients": "Benefited from faster, more accurate documents but faced new risks if oversight standards lagged",
    "engineering_firms": "Gained efficiency but faced new questions about supervision and accountability",
    "engineers": "Required to learn new tools and adapt professional practice; faced ambiguity about ethical obligations",
    "public": "Potentially exposed to risk if professional standards did not keep pace with technological change",
    "regulatory_bodies": "Faced pressure to update rules that were written for a different era"
  },
  "proeth:activatesConstraint": [
    "Competence_In_New_Technology_Constraint",
    "Professional_Standards_Adaptation_Constraint"
  ],
  "proeth:causesStateChange": "Industry standard shifted from manual to digital document production; the meaning of \u0027personally prepared\u0027 became ambiguous and contested in professional ethics discourse",
  "proeth:createsObligation": [
    "Obligation_To_Maintain_Competence_In_Current_Tools",
    "Obligation_To_Revisit_Standards_For_New_Contexts"
  ],
  "proeth:description": "The engineering profession underwent a historical technological transition from manual drafting to CAD and then to CADD, with AI anticipated as the next evolution. This shift fundamentally changed how engineering documents are produced and who can be said to have \u0027prepared\u0027 them.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Historical period preceding the present case",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Drafting Technology Evolution"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Event_BER_86-2_Controversy_Emerges",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Is a professional ethics ruling legitimate if the majority of practitioners find it unworkable? What mechanisms exist to challenge such rulings?",
    "Does widespread non-compliance with an ethics standard indicate the standard is wrong, or that the profession has a compliance problem?",
    "How should a professional ethics board balance the desire for clear, strict rules with the practical realities of how work is performed?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Frustration among practicing engineers who felt the ruling was disconnected from reality; concern among ethicists and board members about the legitimacy of a contested standard; relief among some who felt the strict standard protected public safety",
  "proeth-scenario:ethicalImplications": "Exposes the tension between rule-based ethical clarity and practical workability; raises questions about the authority and accountability of professional ethics bodies; illustrates how overly rigid standards can paradoxically weaken ethical culture by encouraging evasion",
  "proeth-scenario:learningMoment": "A professional standard that is widely considered unworkable or disconnected from practice can undermine the legitimacy of the entire ethics framework. Students should consider what happens when codified ethics and lived practice diverge significantly.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "BER": "Institutional credibility challenged by widespread professional disagreement",
    "engineering_firms": "Operational disruption if strict compliance required restructuring of CADD workflows",
    "practicing_engineers": "Faced uncertainty about compliance; risk of being found in violation of a standard they considered unworkable",
    "public": "Uncertain whether the controversy would weaken or strengthen actual oversight of engineering documents"
  },
  "proeth:activatesConstraint": [
    "Professional_Standards_Legitimacy_Constraint",
    "Obligation_To_Revisit_Unworkable_Standards"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/120#Action_Adopt_Strict_Sealing_Interpretation__BER_Case_86-2",
  "proeth:causesStateChange": "The 1986 ruling lost practical authority as widespread non-compliance and professional dissent signaled a gap between the codified standard and accepted practice; pressure mounted on BER to revisit the ruling",
  "proeth:createsObligation": [
    "Obligation_Of_BER_To_Reconsider_Ruling",
    "Obligation_To_Engage_Community_Concerns"
  ],
  "proeth:description": "Following the adoption of the strict sealing interpretation in BER Case 86-2 (1986), significant controversy erupted within the engineering community over the ruling\u0027s practical workability and its alignment with modern CADD-based practice. This controversy was an unintended outcome of the ruling itself.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Post-1986, following publication of BER Case 86-2",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "BER 86-2 Controversy Emerges"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Event_Standard_Interpretation_Gap_Identified",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Is Engineer B acting unethically by sealing work prepared by others, or is Engineer B exercising appropriate professional judgment in a gap left by an outdated standard?",
    "What responsibility do individual practitioners have when they recognize that a professional standard may be outdated or unworkable?",
    "How does the contrast between Engineer A and Engineer B\u0027s situations help clarify what the ethical core of the sealing requirement actually is?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Anticipation among engineers awaiting clarification; intellectual engagement for BER members confronting a genuine interpretive challenge; anxiety for Engineer B whose practice was more clearly in tension with the 1986 ruling",
  "proeth-scenario:ethicalImplications": "Illustrates the difference between the letter and spirit of professional standards; raises questions about individual responsibility during periods of standards ambiguity; highlights how concrete cases drive ethical standard evolution",
  "proeth-scenario:learningMoment": "The gap between a written standard and actual practice is itself an ethically significant condition that demands resolution. Students should recognize that presenting contrasting cases to an ethics body is a legitimate mechanism for evolving professional standards.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Relatively secure; personal preparation aligns with even the strict 1986 standard",
    "engineer_b": "Professionally exposed; practice of sealing others\u0027 work directly challenged by 1986 ruling",
    "engineering_community": "Awaiting guidance that would either validate or require restructuring of common CADD workflows",
    "public": "Interests at stake in whether the resulting standard would ensure adequate oversight of sealed documents"
  },
  "proeth:activatesConstraint": [
    "Professional_Standards_Clarity_Constraint",
    "Obligation_To_Provide_Guidance_To_Practitioners"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/120#Action_Sign_and_Seal_Own_CADD_Work__Engineer_A___Seal_Oth",
  "proeth:causesStateChange": "The coexistence of two different sealing practices in the same case created an unavoidable need for the BER to articulate a coherent and updated standard applicable to CADD-produced documents",
  "proeth:createsObligation": [
    "Obligation_Of_BER_To_Clarify_Applicable_Standard",
    "Obligation_To_Address_Both_Engineer_Scenarios"
  ],
  "proeth:description": "The present case revealed an active gap between the 1986 strict standard and current engineering practice, as evidenced by both Engineer A and Engineer B openly sealing CADD-produced documents under different circumstances. This gap became the triggering condition for the BER\u0027s review.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Present case, prior to BER deliberation",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Standard Interpretation Gap Identified"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Event_Sealing_Standard_Moderated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the new \u0027responsible charge and detailed review\u0027 standard adequately protect the public, or does it risk becoming a rubber-stamp justification for insufficient oversight?",
    "The narrative anticipates AI as the next step after CADD \u2014 how should the responsible charge standard be applied when AI generates engineering documents?",
    "What does this evolution in standards reveal about the relationship between professional ethics bodies and the communities they govern?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Relief among practitioners whose CADD-based workflows are now validated; satisfaction for BER members who resolved a long-standing controversy; possible concern among strict constructionists who worry the new standard weakens public protection; vindication for Engineer B",
  "proeth-scenario:ethicalImplications": "Demonstrates that professional ethics is not static but must be responsive to technological and social change; raises questions about the minimum threshold of personal involvement required for professional accountability; highlights the tension between formalistic rule-following and substantive ethical protection of the public interest; establishes a precedent with significant implications for AI-assisted engineering practice",
  "proeth-scenario:learningMoment": "Professional ethical standards are living documents that must evolve with technology and practice. The shift from \u0027personal preparation\u0027 to \u0027responsible charge and detailed review\u0027 reflects a deeper understanding of what the sealing requirement is actually designed to protect: not the act of creation, but the assurance of professional accountability. Students should also note the AI precedent being set.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "BER": "Institutional credibility restored by demonstrating responsiveness to professional community concerns",
    "engineer_a": "Practice unchanged and confirmed as ethical; minimal impact",
    "engineer_b": "Practice now explicitly permissible under the new standard; professional exposure resolved",
    "engineering_firms": "CADD-based workflows using supervised subordinates now clearly permissible; operational certainty restored",
    "future_engineers": "Precedent set for how AI-assisted document production may eventually be evaluated under similar responsible-charge reasoning",
    "public": "Protected by a more workable standard that ensures detailed review rather than relying on a formalistic personal-preparation requirement that was widely ignored"
  },
  "proeth:activatesConstraint": [
    "Responsible_Charge_And_Review_Constraint",
    "Obligation_To_Conduct_Detailed_Review_Before_Sealing"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/120#Action_Clarify_and_Modify_1986_Ruling__NSPE_Board_of_Ethi",
  "proeth:causesStateChange": "The operative professional standard shifted from \u0027personal preparation of all tasks\u0027 to \u0027detailed review and responsible charge\u0027; Engineer B\u0027s practice became ethically permissible under the new standard while remaining subject to robust oversight obligations",
  "proeth:createsObligation": [
    "Obligation_To_Conduct_Detailed_Review_Of_All_Sealed_Documents",
    "Obligation_To_Maintain_Responsible_Charge_Over_Work_Prepared_By_Others",
    "Obligation_To_Update_Practice_To_Conform_To_New_Standard"
  ],
  "proeth:description": "As an outcome of the BER\u0027s deliberation in the present case, the strict 1986 standard requiring personal preparation of all tasks was formally moderated to require detailed review and responsible charge rather than personal preparation. This represented a substantive change in the operative professional standard.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Present case, following BER deliberation and ruling",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Sealing Standard Moderated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#Event_AI_Anticipation_Registered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "If an AI system generates a complete structural engineering design, can a professional engineer exercise \u0027responsible charge\u0027 over that document by reviewing it, or does the opacity of AI reasoning undermine the possibility of genuine professional accountability?",
    "Should the profession wait for AI-generated engineering documents to become common before developing standards, or should it develop standards proactively? What are the risks of each approach?",
    "How does the CADD-to-AI analogy hold up, and where does it break down? Are there features of AI that make the responsible-charge model insufficient?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Intellectual excitement among forward-thinking engineers and ethicists; unease among those who recognize that the profession may again lag behind technological change; a sense of unfinished business even as the CADD standard is resolved",
  "proeth-scenario:ethicalImplications": "Raises profound questions about the nature of professional accountability when the \u0027author\u0027 of a document is an algorithm; challenges the assumption that detailed review is sufficient when the reviewer may not be able to fully understand or verify AI-generated reasoning; connects historical standard evolution to a live and urgent contemporary ethics challenge",
  "proeth-scenario:learningMoment": "The most important lesson from this event is that professional ethics must be anticipatory, not merely reactive. The explicit acknowledgment of AI in the case framing invites students to apply the responsible-charge reasoning developed for CADD to the emerging AI context \u2014 a directly relevant and unresolved professional ethics challenge.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "BER": "Implicitly committed to future deliberation on AI; credibility enhanced if it acts proactively",
    "engineering_profession": "Put on notice that another standard revision will be required as AI matures; opportunity to be proactive rather than reactive",
    "public": "Long-term interest in ensuring that AI-generated engineering documents are subject to the same quality of professional oversight as manually or CADD-produced documents",
    "students_and_emerging_engineers": "Will practice in an environment where AI document generation is likely common; must understand the responsible-charge framework that will govern it",
    "technology_developers": "Signals that engineering ethics bodies are aware of and will eventually regulate AI use in document production"
  },
  "proeth:activatesConstraint": [
    "Future_Proofing_Standards_Constraint",
    "Obligation_To_Anticipate_Technological_Change_In_Standard_Setting"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/120#Action_Clarify_and_Modify_1986_Ruling__NSPE_Board_of_Ethi",
  "proeth:causesStateChange": "The professional ethics discourse is formally placed on notice that the responsible-charge standard being articulated for CADD will need to be extended and reinterpreted for AI-generated engineering documents in the foreseeable future",
  "proeth:createsObligation": [
    "Obligation_To_Monitor_AI_Development_In_Engineering",
    "Obligation_To_Proactively_Revisit_Standards_As_AI_Matures"
  ],
  "proeth:description": "The case narrative explicitly identifies AI as the anticipated next technological step beyond CADD, placing the current standard-setting exercise within a forward-looking context. This acknowledgment functions as an exogenous signal that the profession\u0027s current deliberations will have implications beyond CADD.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Present case narrative framing, forward-looking",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "AI Anticipation Registered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#CausalChain_3e5f05bb",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The engineering profession underwent a historical technological transition from manual drafting to CADD, which created new ambiguities about what it meant for an engineer to \u0027prepare\u0027 documents, ultimately generating controversy around the strict 1986 sealing standard",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineering profession transitions from manual drafting to CADD systems, changing how documents are produced and who produces them",
      "proeth:element": "Drafting Technology Evolution (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineers begin delegating CADD document preparation to technicians and non-engineer staff, a practice not contemplated by existing sealing rules",
      "proeth:element": "Delegation of CADD Work",
      "proeth:step": 2
    },
    {
      "proeth:description": "BER Case 86-2 applies existing sealing ethics to CADD context, ruling it unethical to seal plans not personally prepared",
      "proeth:element": "Adopt Strict Sealing Interpretation (Action 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Widespread engineering practice of delegating CADD work collides with the newly articulated strict standard",
      "proeth:element": "Practice-Standard Conflict",
      "proeth:step": 4
    },
    {
      "proeth:description": "Significant professional controversy arises as engineers recognize the strict standard is incompatible with common CADD workflows",
      "proeth:element": "BER 86-2 Controversy Emerges (Event 2)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Drafting Technology Evolution (Event 1)",
  "proeth:counterfactual": "Without the shift to CADD technology, manual drafting norms would have remained compatible with the strict sealing standard, and no controversy would have emerged from BER 86-2",
  "proeth:effect": "BER 86-2 Controversy Emerges (Event 2)",
  "proeth:necessaryFactors": [
    "Widespread adoption of CADD technology in engineering practice",
    "Existence of a strict sealing standard requiring personal preparation",
    "Divergence between how CADD work is produced versus how manual drafting was produced",
    "Professional community awareness of the resulting compliance tension"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Engineering profession collectively / technology adoption leaders",
  "proeth:sufficientFactors": [
    "CADD adoption + strict personal-preparation sealing rule + delegation of CADD tasks to non-engineers = inevitable conflict between practice and ethics standard"
  ],
  "proeth:withinAgentControl": false
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#CausalChain_397e8869",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The present case revealed an active gap between the 1986 strict standard and current engineering practice, implying that the strict standard\u0027s rigidity \u2014 established in BER Case 86-2 \u2014 was the originating condition that made the gap possible and identifiable",
  "proeth:causalSequence": [
    {
      "proeth:description": "BER 86-2 establishes that sealing documents not personally prepared is unethical",
      "proeth:element": "Adopt Strict Sealing Interpretation (Action 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "CADD becomes ubiquitous; delegation of CADD work becomes standard industry practice post-1986",
      "proeth:element": "Drafting Technology Evolution Continues (Event 1)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B seals CADD documents prepared by others under supervision, directly contravening the 1986 strict standard",
      "proeth:element": "Seal Others\u0027 CADD Documents (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The conflict between Engineer B\u0027s conduct and the 1986 standard brings the case before the present Board",
      "proeth:element": "BER 86-2 Controversy Emerges (Event 2)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Present Board formally recognizes the gap between the strict 1986 standard and actual engineering practice",
      "proeth:element": "Standard Interpretation Gap Identified (Event 3)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Adopt Strict Sealing Interpretation (Action 3)",
  "proeth:counterfactual": "Without the strict 1986 standard, there would be no fixed reference point against which a \u0027gap\u0027 could be measured; the gap exists only because the standard was set strictly and practice diverged from it",
  "proeth:effect": "Standard Interpretation Gap Identified (Event 3)",
  "proeth:necessaryFactors": [
    "Existence of the strict 1986 standard requiring personal preparation",
    "Continued and growing prevalence of delegated CADD work in engineering firms",
    "A new case presenting facts that directly implicated the gap",
    "Board willingness to re-examine the prior ruling"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "BER Board (1986 composition) / Engineer B (present case)",
  "proeth:sufficientFactors": [
    "Strict 1986 standard + widespread contrary practice + new case presenting Engineer B\u0027s conduct = sufficient to surface and confirm the interpretation gap"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#CausalChain_116af38b",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The present case revealed an active gap between the 1986 strict standard and current engineering practice, directly motivating the present Board to clarify and effectively modify the strict standard established in BER Case 86-2",
  "proeth:causalSequence": [
    {
      "proeth:description": "Present Board recognizes that the 1986 strict standard no longer reflects or accommodates actual engineering practice",
      "proeth:element": "Standard Interpretation Gap Identified (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Accumulated professional controversy provides additional impetus and legitimacy for revisiting the prior ruling",
      "proeth:element": "BER 86-2 Controversy Emerges (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Board notes AI as the next technological step, reinforcing the need for a flexible, forward-looking standard rather than a rigid one",
      "proeth:element": "AI Anticipation Registered (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Present Board issues a clarified ruling that moderates the strict personal-preparation requirement, allowing supervised delegation",
      "proeth:element": "Clarify and Modify 1986 Ruling (Action 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The strict 1986 standard is effectively replaced by a supervision-based standard applicable to CADD and anticipated future technologies",
      "proeth:element": "Sealing Standard Moderated (Event 4)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Standard Interpretation Gap Identified (Event 3)",
  "proeth:counterfactual": "Without the formally identified gap, the Board would have had no principled basis to depart from its 1986 precedent; the gap identification was the necessary trigger for modification",
  "proeth:effect": "Clarify and Modify 1986 Ruling (Action 4)",
  "proeth:necessaryFactors": [
    "Formal identification of the gap between 1986 standard and current practice",
    "A live case presenting facts requiring the Board to render a new opinion",
    "Board authority to revisit and modify prior rulings",
    "Sufficient professional consensus that the 1986 standard was unworkable"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Present BER Board",
  "proeth:sufficientFactors": [
    "Identified gap + live case + Board authority + professional consensus = sufficient to trigger formal modification of the 1986 ruling"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#CausalChain_0e2f1a85",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The case narrative explicitly identifies AI as the anticipated next technological step beyond CADD, with the historical trajectory from manual drafting to CADD providing the causal template by which the Board recognized that AI would create analogous sealing and supervision challenges requiring proactive ethical framing",
  "proeth:causalSequence": [
    {
      "proeth:description": "Transition from manual drafting to CADD establishes the pattern by which new technologies disrupt existing sealing ethics",
      "proeth:element": "Drafting Technology Evolution (Event 1)",
      "proeth:step": 1
    },
    {
      "proeth:description": "The CADD-driven controversy demonstrates the professional cost of reactive rather than proactive ethics standard-setting",
      "proeth:element": "BER 86-2 Controversy Emerges (Event 2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "The present case confirms that technology-driven gaps can persist for decades without formal resolution",
      "proeth:element": "Standard Interpretation Gap Identified (Event 3)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Board issues a moderated standard designed to be technology-neutral and forward-looking",
      "proeth:element": "Clarify and Modify 1986 Ruling (Action 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Board explicitly names AI as the next anticipated technology, embedding proactive guidance into the ruling to prevent recurrence of the CADD controversy pattern",
      "proeth:element": "AI Anticipation Registered (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Drafting Technology Evolution (Event 1)",
  "proeth:counterfactual": "Without the CADD technology evolution having already demonstrated how new drafting technologies disrupt sealing norms, the Board would have had no experiential basis for anticipating and addressing AI\u0027s analogous impact",
  "proeth:effect": "AI Anticipation Registered (Event 5)",
  "proeth:necessaryFactors": [
    "Historical precedent of CADD disrupting existing sealing norms",
    "Board awareness of AI as an emerging technology in engineering",
    "Recognition that the CADD-to-AI transition would replicate the manual-drafting-to-CADD pattern",
    "Board intent to issue forward-looking rather than merely reactive guidance"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Present BER Board",
  "proeth:sufficientFactors": [
    "CADD disruption precedent + Board awareness of AI + forward-looking intent = sufficient for the Board to formally register AI anticipation in its ruling"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/120#",
    "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/120#CausalChain_c0565984",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B\u0027s act of signing and sealing CADD-produced documents prepared by other individuals working under supervision served as the proximate factual trigger that brought the tension between practice and the 1986 standard before the Board, ultimately resulting in the moderation of that standard",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B seals CADD documents prepared by supervised subordinates, creating a concrete ethics question under the 1986 standard",
      "proeth:element": "Seal Others\u0027 CADD Documents (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "The case surfaces the gap between the strict 1986 standard and widespread engineering practice",
      "proeth:element": "Standard Interpretation Gap Identified (Event 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Present Board uses the case to formally clarify and moderate the 1986 strict standard",
      "proeth:element": "Clarify and Modify 1986 Ruling (Action 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The new standard permits sealing of supervised others\u0027 CADD work, replacing the strict personal-preparation requirement",
      "proeth:element": "Sealing Standard Moderated (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "The moderated standard is explicitly framed to extend to future technologies including AI, embedding forward-looking flexibility",
      "proeth:element": "AI Anticipation Registered (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Seal Others\u0027 CADD Documents (Action 2)",
  "proeth:counterfactual": "Without Engineer B\u0027s conduct presenting a concrete case, the abstract controversy over the 1986 standard might not have produced a formal ruling modification; a live case was necessary to compel a definitive Board response",
  "proeth:effect": "Sealing Standard Moderated (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s decision to seal documents prepared by supervised others",
    "That conduct being recognized as ethically questionable under the 1986 standard",
    "The case being brought before the BER for formal review",
    "The Board\u0027s willingness to use the case as an occasion to revisit the 1986 ruling"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer B (proximate); Present BER Board (ultimate)",
  "proeth:sufficientFactors": [
    "Engineer B\u0027s conduct + formal BER review + identified practice gap + Board authority = sufficient to produce a moderated standard"
  ],
  "proeth:withinAgentControl": true
}