{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Action_Chose_AI_for_Report_Drafting",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the engagement until a replacement QA mentor or peer reviewer could be identified and engaged.",
    "Request a timeline extension from Client W to allow adequate time to independently draft the report and design documents without AI assistance.",
    "Engage a qualified sub-consultant or peer reviewer to provide the QA function previously filled by Engineer B before adopting any AI tools."
  ],
  "proeth-scenario:characterMotivation": "Engineer A faced the dual pressure of delivering complex work products without the mentorship safety net of Engineer B, and sought an efficiency tool to compensate for the loss of quality assurance support while still meeting client expectations and contractual obligations.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining the engagement would protect Engineer A from ethical and technical risk but could damage the client relationship and result in lost revenue; however, it would uphold the duty not to undertake work beyond one\u0027s competent capacity.",
    "Requesting an extension might strain client relations but would allow Engineer A to produce work meeting professional standards, avoiding the downstream errors that ultimately required costly revisions anyway.",
    "Engaging a sub-consultant would distribute risk appropriately, maintain quality assurance, and could have allowed AI use in a supervised, validated context\u2014likely the most ethically sound path forward."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how the absence of mentorship or peer review can push engineers toward risky compensatory behaviors; teaches that adopting new technology requires its own due diligence and that unfamiliarity with a tool does not excuse its misuse under NSPE Canon 2 (competence).",
  "proeth-scenario:ethicalTension": "Professional competence and independent judgment versus the pragmatic adoption of unfamiliar emerging technology; the duty to deliver quality work versus the temptation to rely on an unvetted tool to fill a capability gap left by mentor\u0027s retirement.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The professional competence standard Engineer A is held to; client trust in deliverable quality; potential downstream errors if the AI tool produces unreliable outputs that Engineer A cannot critically evaluate; Engineer A\u0027s professional reputation and license.",
  "proeth:description": "Engineer A decided to use open-source AI software, unfamiliar to them, to generate an initial draft of the comprehensive report rather than drafting it independently or seeking alternative quality assurance support.",
  "proeth:foreseenUnintendedEffects": [
    "Risk of unfamiliar tool producing unreliable output",
    "Potential loss of direction-and-control over work product",
    "Possible stylistic inconsistency in final deliverable"
  ],
  "proeth:fulfillsObligation": [
    "Attempted to meet contractual delivery obligation to Client W",
    "Sought a productivity tool to compensate for loss of mentorship support"
  ],
  "proeth:guidedByPrinciple": [
    "Technological innovation as a productivity supplement (BER Case 90-6, BER Case 98-3)",
    "Professional self-reliance in absence of mentorship",
    "Efficiency in project delivery"
  ],
  "proeth:hasAgent": "Engineer A (Environmental Engineer, Responsible Charge)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Delivery efficiency vs. tool competence requirement",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict in favor of efficiency, accepting the risk of using an unfamiliar tool rather than seeking alternative quality assurance mechanisms or disclosing limitations to Client W"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Efficiently produce a report draft without the mentorship support previously provided by Engineer B, meeting delivery obligations to Client W",
  "proeth:requiresCapability": [
    "Proficiency with AI drafting tools",
    "Ability to critically evaluate AI-generated technical content",
    "Environmental engineering report writing expertise"
  ],
  "proeth:temporalMarker": "Early project phase, after Engineer B\u0027s retirement and project initiation",
  "proeth:violatesObligation": [
    "NSPE Code Section II.2 \u2014 obligation to perform services only in areas of competence (tool was unfamiliar)",
    "NSPE Code Section III.2.a \u2014 obligation to maintain direction and control over work products",
    "Responsible Charge obligation to ensure adequate quality assurance processes are in place"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Chose AI for Report Drafting"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Action_Input_Confidential_Data_into_Public_AI",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Obtain explicit written informed consent from Client W before inputting any proprietary data into any third-party AI platform, disclosing the tool\u0027s data handling practices.",
    "Anonymize or de-identify the client\u0027s site data before inputting it into the AI, using only generic parameters sufficient to generate a structural draft without exposing confidential specifics.",
    "Use a privately hosted or enterprise-licensed AI tool with contractual confidentiality and data non-retention guarantees before processing any client data."
  ],
  "proeth-scenario:characterMotivation": "Engineer A needed to provide the AI with sufficient project-specific context to generate a useful and accurate report draft, and did not pause to consider the data governance implications of using a public open-source platform that may not offer confidentiality protections.",
  "proeth-scenario:consequencesIfAlternative": [
    "Obtaining prior consent would have been the ethically correct path; Client W might have approved, restricted, or denied AI use\u2014but the decision would have been theirs to make, preserving trust and fulfilling Engineer A\u0027s fiduciary duty.",
    "Anonymizing data would reduce confidentiality risk but might also reduce the AI output\u0027s relevance and accuracy, requiring more engineer input to contextualize results\u2014an acceptable trade-off that preserves ethical compliance.",
    "Using a private or enterprise AI platform with data protection agreements would allow AI-assisted drafting while honoring confidentiality obligations, though it requires advance procurement and vetting of the tool."
  ],
  "proeth-scenario:decisionSignificance": "Highlights that confidentiality obligations extend to the tools and platforms engineers use; teaches that NSPE Canon 4 (acting as faithful agents) and Canon 3 (avoiding deceptive acts) require engineers to evaluate third-party data handling before exposing client information, and that informed client consent is a prerequisite\u2014not an afterthought.",
  "proeth-scenario:ethicalTension": "Duty of loyalty and confidentiality to the client versus the operational convenience of using a publicly accessible AI tool; the engineer\u0027s obligation to protect proprietary client data conflicts directly with the data ingestion practices of open-source AI systems that may retain, log, or expose input data.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Client W\u0027s proprietary site data and competitive information; potential breach of contract or professional confidentiality obligations; legal liability for Engineer A if data is exposed or misused by the AI platform; erosion of client trust if discovered.",
  "proeth:description": "Engineer A uploaded Client W\u0027s confidential and proprietary site data into a public open-source AI interface without obtaining Client W\u0027s prior informed consent, in order to generate the report draft.",
  "proeth:foreseenUnintendedEffects": [
    "Potential exposure of Client W\u0027s confidential information to third parties via public AI interface",
    "Possible data retention or use by AI platform operator"
  ],
  "proeth:fulfillsObligation": [
    "Used project-specific data to attempt accurate report generation"
  ],
  "proeth:guidedByPrinciple": [
    "Client trust and confidentiality as foundational to the engineer-client relationship",
    "Informed consent before use of client data in novel technology contexts"
  ],
  "proeth:hasAgent": "Engineer A (Environmental Engineer, Responsible Charge)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client confidentiality vs. AI tool utility requiring data input",
    "proeth:resolutionReasoning": "Engineer A resolved in favor of practical utility of the AI tool, disregarding or underweighting the confidentiality risk posed by inputting data into a public platform without client consent"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Leverage client-specific data to produce a contextually accurate AI-generated report draft",
  "proeth:requiresCapability": [
    "Understanding of data privacy risks associated with public AI platforms",
    "Ability to assess terms of service and data retention policies of AI tools",
    "Client communication skills to obtain informed consent"
  ],
  "proeth:temporalMarker": "Report drafting phase",
  "proeth:violatesObligation": [
    "NSPE Code Section II.1.c \u2014 obligation to keep client information confidential and not disclose without consent",
    "General fiduciary duty to protect client proprietary information",
    "Obligation to obtain informed client consent before exposing data to third-party platforms"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Input Confidential Data into Public AI"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Action_Conducted_Thorough_Report_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Submit the AI-generated report with no substantive review, relying entirely on the AI\u0027s output accuracy.",
    "Conduct an even more rigorous review including independent recalculation of all data points, consultation with subject matter experts, and a structured technical audit of all AI-generated claims.",
    "Engage a peer reviewer or technical editor to independently verify the AI-generated content before Engineer A\u0027s final review and submission."
  ],
  "proeth-scenario:characterMotivation": "Engineer A recognized the professional obligation to validate AI-generated content and invested effort in cross-referencing factual claims and verifying phrasing, demonstrating an understanding that the engineer\u2014not the AI\u2014bears responsibility for the final work product.",
  "proeth-scenario:consequencesIfAlternative": [
    "Submitting without review would represent a clear ethical violation and likely produce a deficient report with errors, exposing Engineer A to disciplinary action and client harm\u2014mirroring the outcome seen with the design documents.",
    "A more rigorous independent review would have been the gold standard, likely producing a higher-quality report and potentially detecting the stylistic inconsistency Client W noted; it would also have set a consistent standard of care across both deliverables.",
    "Peer review would have added an external quality check that compensates for Engineer A\u0027s unfamiliarity with the AI tool, strengthening the ethical defensibility of the AI-assisted workflow."
  ],
  "proeth-scenario:decisionSignificance": "Serves as a positive contrast to Action 6; demonstrates that when AI is used as a drafting aid, substantive human review is the ethical minimum required to satisfy NSPE Canon 2 (competence) and Canon 3 (truthfulness); teaches students to distinguish between appropriate AI-assisted workflows and inappropriate delegation of professional judgment.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to exercise independent professional judgment and ensure accuracy versus the efficiency gains that motivated AI use in the first place; thorough review partially negates the time-saving rationale for AI assistance but is ethically necessary to meet the standard of care.",
  "proeth-scenario:isDecisionPoint": false,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Accuracy and reliability of the report submitted to Client W; Engineer A\u0027s professional credibility and seal validity; the precedent this review standard sets relative to the far weaker review applied to the design documents.",
  "proeth:description": "Engineer A performed a substantive review of the AI-generated report draft, cross-checking factual content against professional journals and verifying phrasing through search engine queries, then made minor wording adjustments before submission.",
  "proeth:foreseenUnintendedEffects": [
    "Minor stylistic inconsistencies may persist from AI-generated prose",
    "Review may not catch all errors without mentorship support"
  ],
  "proeth:fulfillsObligation": [
    "NSPE Code Section II.2 \u2014 exercised professional judgment in reviewing work product",
    "NSPE Code Section III.2.a \u2014 maintained meaningful direction and control over the report through substantive review",
    "Responsible Charge obligation to verify accuracy of work bearing professional seal",
    "Obligation to deliver a technically accurate work product to Client W"
  ],
  "proeth:guidedByPrinciple": [
    "Engineer as final responsible authority over sealed work products",
    "Professional judgment must supplement and verify technological outputs (BER Case 90-6)",
    "Due diligence in quality assurance"
  ],
  "proeth:hasAgent": "Engineer A (Environmental Engineer, Responsible Charge)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Efficiency of AI drafting vs. rigor of professional review",
    "proeth:resolutionReasoning": "Engineer A resolved this conflict appropriately for the report by investing in substantive review, partially compensating for the lack of mentorship oversight, though stylistic inconsistencies remained"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Ensure factual accuracy and professional quality of the AI-generated report before submission to Client W, exercising professional judgment over the final work product",
  "proeth:requiresCapability": [
    "Environmental engineering domain expertise to validate report content",
    "Ability to cross-reference technical literature",
    "Critical evaluation of AI-generated prose and factual claims"
  ],
  "proeth:temporalMarker": "Report review phase, prior to report submission",
  "proeth:violatesObligation": [
    "Possible residual obligation to disclose AI involvement to Client W (transparency best practices, NSPE Code Section III.9)",
    "Full competence obligation if AI tool limitations were not fully understood during review"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Conducted Thorough Report Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Action_Submitted_Report_Without_AI_Disclosure",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Disclose AI use proactively in a cover letter or methodology section of the report, describing the tool used, the data inputted, and the review process applied.",
    "Consult the state engineering licensing board or NSPE ethics guidance on AI disclosure obligations before submitting the sealed document.",
    "Reframe the submission as a draft without a seal, pending client review and explicit approval of the AI-assisted methodology before affixing the professional seal."
  ],
  "proeth-scenario:characterMotivation": "Engineer A may have assumed that disclosure of AI use was not legally required under current state licensing law, or feared that disclosing AI involvement might undermine Client W\u0027s confidence in the deliverable or raise questions about the value of professional fees charged for the engagement.",
  "proeth-scenario:consequencesIfAlternative": [
    "Proactive disclosure would uphold transparency, allow Client W to make an informed judgment about the methodology, and protect Engineer A from later accusations of misrepresentation\u2014likely the most ethically defensible path.",
    "Consulting the licensing board would demonstrate good-faith ethical diligence; even if no clear rule existed, the inquiry itself would create a documented record of Engineer A\u0027s intent to comply and might yield guidance that shapes the submission approach.",
    "Withholding the seal pending client approval would slow the process but ensure that the professional certification reflects genuine informed endorsement of the work product and methodology, preserving the integrity of the sealing act."
  ],
  "proeth-scenario:decisionSignificance": "Teaches that ethical obligations often exceed legal minimums; the absence of a statutory disclosure requirement does not eliminate the professional duty of transparency under NSPE Canon 3 (engineers shall not misrepresent their professional qualifications or work); students learn that sealing AI-assisted work without disclosure raises questions of professional integrity even when technically lawful.",
  "proeth-scenario:ethicalTension": "Transparency and honesty obligations to the client versus concerns about professional perception, client confidence, and the absence of explicit legal disclosure mandates; the engineer\u0027s duty to be a faithful agent conflicts with the omission of material information about how the work product was generated.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s professional integrity and trustworthiness; Client W\u0027s right to informed understanding of how their deliverable was produced; the validity and meaning of the professional seal as a representation of the engineer\u0027s personal judgment and responsibility; potential disciplinary exposure if non-disclosure is later deemed deceptive.",
  "proeth:description": "Engineer A submitted the AI-assisted report draft to Client W with a professional seal affixed consistent with state law but did not disclose that AI software had been used in its drafting, nor cite the AI tool as a contributing resource.",
  "proeth:foreseenUnintendedEffects": [
    "Client W may not be aware of AI involvement and cannot assess associated risks",
    "Non-disclosure may undermine trust if AI use is later discovered",
    "Potential attribution issue if AI-generated language is not credited"
  ],
  "proeth:fulfillsObligation": [
    "Complied with state law requirements for professional seal application",
    "Submitted deliverable labeled as a draft, providing some transparency about preliminary status"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty and transparency in professional communications",
    "Client\u0027s right to informed understanding of deliverable provenance",
    "Professional integrity in representation of work product"
  ],
  "proeth:hasAgent": "Engineer A (Environmental Engineer, Responsible Charge)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Transparency and attribution obligations vs. absence of universal AI disclosure mandate",
    "proeth:resolutionReasoning": "Engineer A chose non-disclosure by defaulting to the minimum legal standard rather than the higher ethical standard, which the Discussion concludes was marginally acceptable for the report given the thorough review but fell short of best practices"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Deliver a professionally sealed report to Client W that satisfies contractual obligations, relying on the adequacy of the review process to justify the seal without disclosing the AI drafting method",
  "proeth:requiresCapability": [
    "Understanding of professional sealing obligations",
    "Judgment regarding disclosure obligations in novel technology contexts",
    "Knowledge of NSPE attribution and transparency standards"
  ],
  "proeth:temporalMarker": "Report submission phase",
  "proeth:violatesObligation": [
    "NSPE Code Section III.9 \u2014 obligation to give proper credit and acknowledge contributions of others, including AI tools",
    "Transparency best practices in professional engineering communication",
    "Implied obligation to inform client of material aspects of how work was produced, particularly novel methods involving third-party tools"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Submitted Report Without AI Disclosure"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Action_Used_AI_for_Design_Document_Generation",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Use AI only as a preliminary ideation tool for design concepts, then independently develop all technical specifications, dimensions, and safety features from scratch using verified engineering methods.",
    "Engage a licensed structural or design engineer as a sub-consultant to develop and verify the design documents, with AI used only for formatting or documentation support.",
    "Decline to produce the design documents under the current constraints and advise Client W that additional time, resources, or personnel are required to meet the professional standard of care for safety-critical design work."
  ],
  "proeth-scenario:characterMotivation": "Emboldened by the apparent success of AI assistance in drafting the report, Engineer A extended the same workflow to the design documents, likely underestimating the higher technical precision and safety-critical nature of engineering design specifications compared to narrative report writing.",
  "proeth-scenario:consequencesIfAlternative": [
    "Using AI only for ideation while independently developing technical content would preserve Engineer A\u0027s professional judgment in the safety-critical elements, likely preventing the dimensional and safety feature errors that ultimately required revision.",
    "Engaging a sub-consultant would ensure qualified oversight of the design documents, distribute professional responsibility appropriately, and likely produce compliant, accurate plans\u2014at the cost of additional fees and coordination.",
    "Declining to produce design documents would protect public safety and Engineer A\u0027s license but require transparent communication with Client W about the engineer\u0027s capacity limitations\u2014an uncomfortable but ethically sound boundary-setting action."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the danger of applying a uniform AI-assisted workflow across qualitatively different work products; teaches that the stakes of engineering design\u2014where errors can cause physical harm\u2014require a higher threshold of human verification than narrative reporting, and that AI tools trained on general data may not reliably meet domain-specific safety and code requirements.",
  "proeth-scenario:ethicalTension": "Efficiency and consistency of approach across deliverables versus the recognition that engineering design documents carry a fundamentally different and higher standard of care than written reports, given their direct implications for public health, safety, and welfare under NSPE Canon 1.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Public safety and welfare if design errors propagate to construction; Client W\u0027s project viability and budget; Engineer A\u0027s professional license and liability exposure; the integrity of the engineering design process as a safety-critical professional function.",
  "proeth:description": "Engineer A input Client W\u0027s project information into an AI-assisted drafting tool and relied on it to generate preliminary engineering plans, layouts, and technical specifications for the design documents.",
  "proeth:foreseenUnintendedEffects": [
    "AI-generated designs may contain technical errors requiring expert review",
    "Unfamiliarity with AI tool increases risk of undetected errors in safety-critical documents",
    "Design documents carry higher public safety stakes than narrative reports"
  ],
  "proeth:fulfillsObligation": [
    "Attempted to meet contractual obligation to deliver design documents to Client W"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety as the paramount obligation in engineering design",
    "AI as a supplement to, not substitute for, engineering judgment (BER Case 98-3)",
    "Heightened diligence required for safety-critical deliverables"
  ],
  "proeth:hasAgent": "Engineer A (Environmental Engineer, Responsible Charge)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "AI-assisted efficiency vs. public safety paramount obligation in design work",
    "proeth:resolutionReasoning": "Engineer A resolved in favor of AI-assisted efficiency without adequately accounting for the heightened review obligations that apply to safety-critical design documents, resulting in an ethically deficient outcome"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Efficiently produce preliminary engineering design documents to fulfill the second deliverable obligation to Client W, using AI to substitute for independent drafting capacity",
  "proeth:requiresCapability": [
    "Proficiency with AI-assisted engineering design tools",
    "Deep familiarity with regulatory safety requirements for the site type",
    "Ability to critically evaluate AI-generated structural dimensions and safety specifications",
    "Environmental and civil engineering design expertise"
  ],
  "proeth:temporalMarker": "Design document drafting phase",
  "proeth:violatesObligation": [
    "NSPE Fundamental Canon I.1 \u2014 obligation to hold paramount public safety, health, and welfare",
    "NSPE Code Section II.2 \u2014 obligation to perform services only within areas of competence (unfamiliar tool applied to safety-critical work)",
    "NSPE Code Section III.2.a \u2014 obligation to maintain direction and control over engineering work products",
    "Responsible Charge obligation to ensure design documents meet professional and regulatory standards"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Used AI for Design Document Generation"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Action_Conducted_Cursory_Design_Document_Review",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Conduct a full independent technical review of every dimension, specification, and safety feature in the AI-generated design documents, verifying compliance with applicable codes and standards before making any adjustments or submitting.",
    "Bring in a qualified peer reviewer or check engineer to independently audit the AI-generated design documents against project requirements, site data, and regulatory standards before Engineer A\u0027s final review and sealing.",
    "Recognize the inadequacy of the available review time and resources, and communicate transparently to Client W that the design document deadline cannot be met to the required standard of care, requesting an extension or scope modification."
  ],
  "proeth-scenario:characterMotivation": "Engineer A may have been fatigued, overconfident following the report experience, operating under time pressure, or insufficiently aware of the technical complexity and safety implications of the AI-generated design content, leading to a superficial review that failed to catch critical errors.",
  "proeth-scenario:consequencesIfAlternative": [
    "A full independent technical review would have detected the misaligned dimensions and missing safety features before submission, preventing client dissatisfaction, avoiding revision costs, and fulfilling Engineer A\u0027s professional duty\u2014the correct ethical and professional path.",
    "Peer review would have introduced an independent technical check that compensates for both Engineer A\u0027s workload constraints and the AI tool\u0027s limitations, likely producing compliant design documents and modeling the kind of collaborative QA that Engineer B\u0027s mentorship previously provided.",
    "Requesting an extension or scope modification would have been professionally honest and ethically sound; while potentially disappointing Client W in the short term, it would have prevented the greater harm of submitting deficient design documents and preserved the integrity of the professional relationship."
  ],
  "proeth-scenario:decisionSignificance": "The central ethical failure of the case and its most important teaching moment: engineers bear non-delegable responsibility for sealed work products, particularly in safety-critical design; a cursory review of AI-generated design documents represents a clear violation of the standard of care and NSPE Canon 2, regardless of the quality of the AI tool used; students learn that the seal represents personal professional accountability, not merely process compliance.",
  "proeth-scenario:ethicalTension": "The fundamental obligation to protect public health, safety, and welfare (NSPE Canon 1) versus the pressures of workload, timeline, and the false confidence that AI-generated technical content is sufficiently reliable to require only cursory verification; professional responsibility cannot be delegated to an AI tool.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Immediate: misaligned dimensions and missing safety features requiring costly revisions and damaging client trust. Downstream: if errors had reached construction, physical harm to workers or the public, catastrophic liability for Engineer A, potential license revocation, and reputational damage to the profession. The highest-stakes action in the narrative.",
  "proeth:description": "Engineer A performed only a superficial review of the AI-generated engineering design documents, making limited site-specific adjustments without conducting a comprehensive technical verification, thereby failing to detect misaligned dimensions and omitted required safety features.",
  "proeth:foreseenUnintendedEffects": [
    "Critical design errors may go undetected",
    "Omitted safety features may create regulatory non-compliance",
    "Public safety risk from structurally or operationally deficient design documents",
    "Client W may identify errors, requiring costly revisions"
  ],
  "proeth:fulfillsObligation": [
    "Conducted some degree of review before submission",
    "Made limited site-specific adjustments"
  ],
  "proeth:guidedByPrinciple": [
    "Public safety as the non-negotiable paramount obligation (NSPE Fundamental Canon I.1)",
    "Engineer must not delegate professional judgment to AI tools (BER Case 90-6, BER Case 98-3)",
    "Responsible Charge requires substantive, not perfunctory, oversight of work products",
    "Higher standard of review required for safety-critical engineering design than for narrative reports"
  ],
  "proeth:hasAgent": "Engineer A (Environmental Engineer, Responsible Charge)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Delivery expediency vs. paramount public safety obligation and thorough review standard",
    "proeth:resolutionReasoning": "Engineer A\u0027s resolution was ethically deficient: the Discussion concludes that the cursory review failed to meet the professional standard of care, as the paramount obligation to public safety cannot be traded off against delivery efficiency, particularly when AI-generated safety-critical documents contain detectable errors that thorough review would have identified"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Complete the design document review process sufficiently to submit deliverables to Client W without investing the full effort required for comprehensive technical verification",
  "proeth:requiresCapability": [
    "Comprehensive engineering design review skills",
    "Knowledge of regulatory safety feature requirements for the site type",
    "Ability to detect dimensional misalignments and specification omissions in technical drawings",
    "Critical evaluation of AI-generated engineering plans against professional standards"
  ],
  "proeth:temporalMarker": "Design document review phase, prior to submission to Client W",
  "proeth:violatesObligation": [
    "NSPE Fundamental Canon I.1 \u2014 paramount obligation to protect public safety, health, and welfare (omitted safety features directly implicate this)",
    "NSPE Code Section II.2 \u2014 obligation to perform services competently, including thorough review of design work",
    "NSPE Code Section III.2.a \u2014 obligation to maintain meaningful direction and control over all engineering work products",
    "Responsible Charge obligation to verify that design documents meet professional, regulatory, and safety standards before submission",
    "Duty of care to Client W to deliver accurate and compliant design documents"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Conducted Cursory Design Document Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Event_AI_Report_Draft_Generated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "When an AI generates a document that an engineer then reviews, who is the author of the final work product?",
    "What specific review steps should an engineer perform on AI-generated technical content before sealing it?",
    "Does the speed advantage of AI-generated drafts create psychological pressure that undermines thorough review?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A may feel relief at having a draft quickly; there is a risk of anchoring bias where the AI output feels authoritative; professional observers would note this as the moment where Engineer A\u0027s professional judgment becomes critical",
  "proeth-scenario:ethicalImplications": "Raises questions about authorship, accountability, and the meaning of professional certification when AI generates primary content; highlights risk of automation bias in professional practice",
  "proeth-scenario:learningMoment": "Illustrates that AI output is not a professional work product until validated by a licensed engineer; the generation of AI content activates, rather than satisfies, professional review obligations",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_w": "Quality of final report depends entirely on Engineer A\u0027s ability to critically evaluate AI output",
    "engineer_a": "Now holds a document that may contain errors, hallucinations, or stylistic inconsistencies that require expert identification",
    "public": "If report informs environmental decisions, accuracy is a public interest matter"
  },
  "proeth:activatesConstraint": [
    "Professional_Review_Obligation",
    "Accuracy_Verification_Constraint",
    "Seal_Responsibility_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/7#Action_Input_Confidential_Data_into_Public_AI",
  "proeth:causesStateChange": "A machine-generated document now exists that requires professional engineering judgment to validate before it can carry a professional seal; Engineer A\u0027s review obligations are activated",
  "proeth:createsObligation": [
    "Verify_All_Technical_Content",
    "Cross_Check_Against_Source_Data",
    "Assess_AI_Phrasing_For_Accuracy",
    "Determine_Fitness_For_Submission"
  ],
  "proeth:description": "The open-source AI software produced a draft environmental report based on the confidential data Engineer A input. This output became the primary document upon which Engineer A\u0027s review and subsequent submission were based.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "During report drafting phase; immediately following data input action",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "AI Report Draft Generated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Event_AI_Design_Documents_Generated",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Why are the ethical obligations for AI-generated design documents categorically more serious than for AI-generated narrative reports?",
    "What specific review protocols should be mandatory before any AI-generated design document receives a professional seal?",
    "If these design documents had been implemented without correction, how would professional liability be distributed?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A is unaware of the embedded errors at this stage; Client W is unknowingly receiving documents with safety deficiencies; professional observers would recognize this as the highest-risk moment in the narrative; the invisibility of the errors creates dramatic irony",
  "proeth-scenario:ethicalImplications": "Exposes the fundamental tension between efficiency and safety in engineering practice; demonstrates that professional seals on AI-generated documents without thorough review constitute a misrepresentation of professional oversight; highlights that public safety obligations are non-negotiable regardless of tool used",
  "proeth-scenario:learningMoment": "Engineering design documents carry direct public safety implications that make AI-generated content particularly high-risk without comprehensive review; the stakes for design documents are categorically higher than for narrative reports",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client_w": "Receiving design documents with safety deficiencies that could result in construction errors or regulatory violations",
    "engineer_a": "Professional liability for defective design documents is fully established at this moment; potential for harm to reputation, license, and legal standing",
    "public": "If design documents are implemented without correction, safety features omitted could pose direct physical risk",
    "regulatory_bodies": "Environmental and construction regulations may be violated by documents that omit required safety features"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Design_Competence_Constraint",
    "Thorough_Engineering_Review_Required"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/7#Action_Used_AI_for_Design_Document_Generation",
  "proeth:causesStateChange": "Machine-generated design documents exist containing latent errors including misaligned dimensions and omitted safety features; these errors are present but not yet discovered; public safety risk is embedded in the documents",
  "proeth:createsObligation": [
    "Conduct_Comprehensive_Design_Review",
    "Verify_All_Dimensions",
    "Confirm_Safety_Feature_Inclusion",
    "Assess_AI_Competence_For_Design_Tasks"
  ],
  "proeth:description": "The open-source AI software produced preliminary engineering design documents, which became the basis for the deliverables Engineer A submitted to Client W after only cursory review. These documents contained substantive technical errors.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "During design document phase; after or concurrent with report drafting",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "AI Design Documents Generated"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Event_Report_Stylistic_Inconsistency_Detected",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Should the detection of stylistic inconsistency have prompted Engineer A to disclose AI use to Client W at the revision stage?",
    "What does it mean for a professional document to have \u0027stylistic inconsistency\u0027 and why does it matter in engineering reports?",
    "How does this relatively minor outcome foreshadow the more serious issues discovered in the design documents?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Client W feels mild dissatisfaction and perhaps subtle suspicion about the report\u0027s authorship or quality; Engineer A, upon learning of this, may feel embarrassed or defensive; the detection creates an implicit question about how the report was produced",
  "proeth-scenario:ethicalImplications": "Raises questions about transparency and the duty to disclose AI use; reveals that even marginally acceptable AI use leaves quality traces; highlights the gap between \u0027technically acceptable\u0027 and \u0027professionally transparent\u0027 practice",
  "proeth-scenario:learningMoment": "Demonstrates that AI-generated content has detectable artifacts that professional review should address; also shows that even a \u0027largely satisfactory\u0027 AI-assisted report leaves traces that raise questions about professional authorship and transparency",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "client_w": "Reduced confidence in deliverable quality; must invest time in review and revision requests",
    "engineer_a": "Professional reputation mildly affected; faces pressure to explain or revise; risk that stylistic inconsistency prompts questions about AI use",
    "project": "Minor delay and rework required"
  },
  "proeth:activatesConstraint": [
    "Client_Satisfaction_Obligation",
    "Revision_Response_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/7#Action_Conducted_Thorough_Report_Review",
  "proeth:causesStateChange": "Client W\u0027s confidence in the report is partially diminished; a quality gap is identified; Engineer A\u0027s review process is implicitly questioned though not yet explicitly challenged",
  "proeth:createsObligation": [
    "Address_Stylistic_Concerns",
    "Consider_Disclosing_AI_Use_In_Revision_Discussion"
  ],
  "proeth:description": "Upon reviewing the submitted report, Client W identified stylistic inconsistencies in the document, which were a detectable artifact of AI-generated content that Engineer A\u0027s review did not fully address. This outcome revealed limitations in the review process.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After report submission; during Client W\u0027s review phase",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Report Stylistic Inconsistency Detected"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Event_Design_Document_Defects_Discovered",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What specific review steps, if performed, would have caught the misaligned dimensions and omitted safety features before submission?",
    "Given that safety features were omitted, does Engineer A have obligations beyond simply revising the documents\u2014such as reporting to a professional body or notifying regulators?",
    "How does this outcome change the ethical analysis of Engineer A\u0027s decision to use AI for design documents compared to their use of AI for the report?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Client W experiences alarm, frustration, and loss of confidence in Engineer A; Engineer A experiences professional shame, anxiety about liability, and recognition of the gravity of the review failure; professional observers see a clear case of inadequate supervision of AI tools; the omission of safety features elevates emotional stakes beyond mere inconvenience to genuine concern",
  "proeth-scenario:ethicalImplications": "Reveals the non-negotiable nature of public safety obligations in engineering; demonstrates that professional seals carry substantive meaning that cannot be delegated to AI systems; highlights the ethical asymmetry between report writing (primarily informational) and design documents (directly safety-implicating); raises questions about whether Engineer A\u0027s conduct constitutes professional misconduct requiring disclosure to licensing authorities",
  "proeth-scenario:learningMoment": "This is the central ethical failure of the case: the cursory review of AI-generated design documents allowed safety-critical errors to reach the client. It demonstrates that professional seals and signatures represent a guarantee of competent review, not merely a formality, and that AI tools do not reduce the engineer\u0027s review obligations\u2014they may increase them",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "client_w": "Project delayed; additional costs for revision; trust in Engineer A severely compromised; potential regulatory exposure if documents had been submitted to authorities",
    "engineer_a": "Professional reputation seriously damaged; potential license disciplinary action; legal liability for defective design documents; must now conduct the comprehensive review that should have been done initially",
    "engineering_profession": "Case illustrates systemic risk of inadequate AI oversight in professional practice",
    "public": "Safety features that were omitted could have resulted in physical harm if documents had been implemented; the discovery prevents downstream harm",
    "regulatory_bodies": "If documents had been filed, regulatory violations would have resulted; discovery at client review stage prevents this outcome"
  },
  "proeth:activatesConstraint": [
    "PublicSafety_Paramount_Constraint",
    "Immediate_Correction_Required_Constraint",
    "Professional_Accountability_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/7#Action_Conducted_Cursory_Design_Document_Review",
  "proeth:causesStateChange": "Project enters crisis phase; design documents are formally defective; public safety risk is identified and acknowledged; Engineer A\u0027s professional competence and review process are under direct scrutiny; Client W\u0027s trust is significantly damaged",
  "proeth:createsObligation": [
    "Immediately_Correct_Design_Errors",
    "Restore_Omitted_Safety_Features",
    "Conduct_Comprehensive_Re_Review",
    "Assess_Whether_Other_Errors_Exist",
    "Consider_Disclosure_Of_AI_Use_And_Review_Process",
    "Notify_Relevant_Parties_If_Safety_Risk_Materialized"
  ],
  "proeth:description": "Client W\u0027s review of the submitted design documents revealed misaligned dimensions and omitted required safety features\u2014substantive technical errors that directly implicate public safety and engineering competence standards. This discovery triggered immediate demands for revision.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After design document submission; during Client W\u0027s review phase",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Design Document Defects Discovered"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Event_Engineer_B_Retirement_Occurs",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What professional obligations does an engineer have when their established QA support disappears before a major project?",
    "Should Engineer A have disclosed to Client W that their usual quality assurance process had changed?",
    "How does the loss of mentorship relate to the concept of practicing within one\u0027s competence under NSPE codes?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A experiences anxiety and vulnerability about working without mentorship; Engineer B may feel relief at retirement but concern for mentee; observers in the profession recognize a common transitional risk moment for mid-career engineers",
  "proeth-scenario:ethicalImplications": "Reveals tension between professional self-sufficiency obligations and the systemic value of mentorship; raises questions about whether engineers have duties to proactively secure QA resources before accepting engagements; highlights how institutional knowledge loss creates ethical risk",
  "proeth-scenario:learningMoment": "Illustrates that professional competence includes maintaining adequate support structures; retirement of a mentor is a foreseeable transition that engineers should plan for proactively rather than reactively filling the gap with unfamiliar tools",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_w": "Unknowingly exposed to increased risk because their retained engineer lacks established QA backstop",
    "engineer_a": "Left without QA support at a critical project moment; increased professional risk; pressure to self-manage quality",
    "engineer_b": "Exits the narrative but bears indirect responsibility for transition planning",
    "public": "Downstream risk if Engineer A\u0027s independent competence is insufficient for the project scope"
  },
  "proeth:activatesConstraint": [
    "Competence_Assurance_Constraint",
    "QualityReview_Requirement"
  ],
  "proeth:causesStateChange": "Engineer A transitions from mentored practice to independent practice without established QA backstop; professional support network diminished",
  "proeth:createsObligation": [
    "Seek_Alternative_QA_Support",
    "Assess_Own_Competence_Gap",
    "Disclose_Limitations_If_Relevant"
  ],
  "proeth:description": "Engineer B, who served as mentor providing quality assurance and writing guidance to Engineer A, retired from practice. This exogenous event removed the established support structure Engineer A had relied upon for professional oversight.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to engagement with Client W; immediately before the project began",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Engineer B Retirement Occurs"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Event_Client_W_Engagement_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At the moment of accepting this engagement, what should Engineer A have assessed about their own competence and support structures?",
    "Does accepting a project without disclosing the loss of your QA mentor constitute a form of misrepresentation?",
    "How do professional codes treat the act of accepting work beyond one\u0027s current support capacity?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineer A likely feels professional confidence and perhaps pressure given the recent loss of mentorship; Client W feels assured that a competent professional is engaged; no immediate tension but foundational stakes are set",
  "proeth-scenario:ethicalImplications": "Highlights that professional engagement creates non-waivable ethical duties; raises questions about informed consent in professional services relationships; reveals the ethical weight of the decision to accept work",
  "proeth-scenario:learningMoment": "Demonstrates that professional engagement is not merely contractual but activates a full suite of ethical obligations under engineering codes; accepting a project is itself an ethical act that presupposes competence",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "client_w": "Trusts that retained engineer will deliver competent, confidential work; vulnerable to any competence gaps",
    "engineer_a": "Assumes full professional liability for both deliverables; obligations to competence and confidentiality now legally and ethically binding",
    "public": "Has indirect interest in the quality of design documents that may affect environmental safety"
  },
  "proeth:activatesConstraint": [
    "Confidentiality_Constraint",
    "Competence_Obligation",
    "PublicSafety_Paramount_Constraint",
    "Faithful_Agency_Constraint"
  ],
  "proeth:causesStateChange": "Engineer A assumes professional responsibility for two distinct deliverables; confidentiality obligations attach to all client data; professional seal obligations activated for design documents",
  "proeth:createsObligation": [
    "Deliver_Comprehensive_Report",
    "Deliver_Engineering_Design_Documents",
    "Protect_Client_Confidential_Data",
    "Perform_Within_Competence",
    "Exercise_Professional_Judgment_On_All_Deliverables"
  ],
  "proeth:description": "Engineer A was formally retained by Client W to produce a comprehensive environmental report and engineering design documents for a site that had been monitored for over a year. This engagement created binding professional and contractual obligations.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Beginning of the project timeline; after Engineer B\u0027s retirement",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Client W Engagement Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#Event_Confidential_Data_Exposed_to_AI",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer A\u0027s lack of awareness about the AI\u0027s data retention practices mitigate or eliminate their ethical responsibility for the confidentiality breach?",
    "What due diligence should an engineer perform before inputting client data into any third-party software tool?",
    "Should Client W be notified of this data exposure, and what are the professional and legal implications of that notification?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely unaware of the gravity in the moment; Client W, if informed, would feel betrayed and alarmed; professional observers would recognize this as a serious confidentiality violation; the AI platform\u0027s role is invisible, creating a false sense of security for Engineer A",
  "proeth-scenario:ethicalImplications": "Reveals that technological ignorance does not suspend professional obligations; highlights the gap between traditional confidentiality frameworks and emerging AI tool realities; raises questions about informed consent when clients do not know their data will be processed by AI systems",
  "proeth-scenario:learningMoment": "Demonstrates that confidentiality is not merely about intent but about actual data control; using public AI tools with client data constitutes a confidentiality breach regardless of good intentions; engineers must assess data handling practices of any tool before use",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "ai_platform": "May retain, analyze, or use input data per its terms of service",
    "client_w": "Proprietary site data potentially accessible to third parties; competitive, legal, or regulatory exposure possible",
    "engineer_a": "Has violated confidentiality obligations potentially without awareness; faces professional discipline risk if discovered",
    "public": "If site data relates to environmental hazards, exposure could have broader implications"
  },
  "proeth:activatesConstraint": [
    "Confidentiality_Constraint",
    "Client_Trust_Protection_Constraint",
    "Data_Security_Obligation"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/7#Action_Input_Confidential_Data_into_Public_AI",
  "proeth:causesStateChange": "Client W\u0027s confidential data now resides in or has been processed by an external AI system; confidentiality perimeter breached; potential for data retention, reuse, or exposure by AI platform",
  "proeth:createsObligation": [
    "Assess_Scope_Of_Exposure",
    "Consider_Client_Notification",
    "Remediate_Future_Data_Handling_Practices"
  ],
  "proeth:description": "When Engineer A input Client W\u0027s confidential site monitoring data into the open-source AI software, that data was transmitted to and processed by an external, publicly accessible system. This created an automatic exposure event regardless of Engineer A\u0027s intent.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "During report drafting phase; after engagement established and AI tool selected",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Confidential Data Exposed to AI"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#CausalChain_a9fc8732",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Client W\u0027s review of the submitted design documents revealed misaligned dimensions and omitted requirements, defects attributable to Engineer A\u0027s superficial review of the AI-generated documents",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A input project information into an AI drafting tool and relied on it to produce engineering design documents",
      "proeth:element": "Used AI for Design Document Generation",
      "proeth:step": 1
    },
    {
      "proeth:description": "AI produced preliminary design documents containing misaligned dimensions and omitted requirements",
      "proeth:element": "AI Design Documents Generated",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A performed only a superficial review, failing to identify the embedded defects",
      "proeth:element": "Conducted Cursory Design Document Review",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A submitted the defective AI-generated documents under professional certification",
      "proeth:element": "Submitted Design Documents with Professional Seal",
      "proeth:step": 4
    },
    {
      "proeth:description": "Client W\u0027s review uncovered misaligned dimensions and omitted requirements in the submitted documents",
      "proeth:element": "Design Document Defects Discovered",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Conducted Cursory Design Document Review",
  "proeth:counterfactual": "Had Engineer A conducted a thorough, substantive review of the AI-generated design documents, the misaligned dimensions and omitted requirements would likely have been identified and corrected before submission",
  "proeth:effect": "Design Document Defects Discovered",
  "proeth:necessaryFactors": [
    "Reliance on AI-generated design documents without adequate independent verification",
    "Superficial rather than substantive technical review by Engineer A",
    "Submission of design documents containing AI-introduced errors"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "AI-generated document errors + cursory review + submission without correction was sufficient to result in defective documents reaching Client W"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#CausalChain_d0d48e08",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "When Engineer A input Client W\u0027s confidential site monitoring data into the open-source AI software, the data was exposed to the public AI system",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A decided to use an unfamiliar open-source AI tool to generate an initial report draft",
      "proeth:element": "Chose AI for Report Drafting",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A uploaded Client W\u0027s confidential site monitoring data into the public AI system",
      "proeth:element": "Input Confidential Data into Public AI",
      "proeth:step": 2
    },
    {
      "proeth:description": "The public AI platform processed and potentially retained or exposed the confidential data",
      "proeth:element": "Confidential Data Exposed to AI",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A\u0027s professional duty to protect Client W\u0027s proprietary information was violated",
      "proeth:element": "Client W Confidentiality Obligation Breached",
      "proeth:step": 4
    },
    {
      "proeth:description": "Client W faces risk of competitive harm or regulatory consequences from data exposure",
      "proeth:element": "Potential Reputational and Legal Harm to Client W",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Input Confidential Data into Public AI",
  "proeth:counterfactual": "Had Engineer A used a secure, private AI tool or refrained from uploading confidential data, the exposure would not have occurred",
  "proeth:effect": "Confidential Data Exposed to AI",
  "proeth:necessaryFactors": [
    "Decision to use a public open-source AI platform",
    "Uploading of Client W\u0027s confidential and proprietary site data",
    "Lack of familiarity with AI software\u0027s data handling and privacy policies"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of public AI platform + confidential data upload + absence of prior vetting of AI privacy safeguards"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#CausalChain_9d5373df",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The open-source AI software produced a draft environmental report based on the confidential data Engineer A provided",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A selected an unfamiliar open-source AI tool to assist with report generation",
      "proeth:element": "Chose AI for Report Drafting",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A provided the AI with Client W\u0027s site data as input",
      "proeth:element": "Input Confidential Data into Public AI",
      "proeth:step": 2
    },
    {
      "proeth:description": "The AI produced a preliminary environmental report draft",
      "proeth:element": "AI Report Draft Generated",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A reviewed the AI draft, cross-checking factual content",
      "proeth:element": "Conducted Thorough Report Review",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A submitted the AI-assisted report with a professional seal and no disclosure of AI involvement",
      "proeth:element": "Submitted Report Without AI Disclosure",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Chose AI for Report Drafting",
  "proeth:counterfactual": "Without the decision to use AI, Engineer A would have drafted the report manually, and the AI-generated draft would not have existed",
  "proeth:effect": "AI Report Draft Generated",
  "proeth:necessaryFactors": [
    "Decision to use AI software for report drafting",
    "Input of site data into the AI system",
    "AI system\u0027s capability to generate a structured report draft"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of AI tool selection + data input + AI generative capability was sufficient to produce the draft"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#CausalChain_97e2c48a",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B, who served as mentor providing quality assurance and writing guidance to Engineer A, retired, removing the oversight layer that previously supported Engineer A\u0027s professional output quality",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B retires, removing quality assurance and mentorship support for Engineer A",
      "proeth:element": "Engineer B Retirement Occurs",
      "proeth:step": 1
    },
    {
      "proeth:description": "Neither Engineer A nor the organization establishes an alternative quality assurance process",
      "proeth:element": "No Replacement QA Mechanism Established",
      "proeth:step": 2
    },
    {
      "proeth:description": "Without mentorship oversight, Engineer A performs only a superficial review of AI-generated documents",
      "proeth:element": "Conducted Cursory Design Document Review",
      "proeth:step": 3
    },
    {
      "proeth:description": "Defective AI-generated documents are submitted to Client W under Engineer A\u0027s professional seal",
      "proeth:element": "AI Design Documents Generated and Submitted",
      "proeth:step": 4
    },
    {
      "proeth:description": "Client W identifies misaligned dimensions and omitted requirements in submitted documents",
      "proeth:element": "Design Document Defects Discovered",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Retirement Occurs",
  "proeth:counterfactual": "Had Engineer B remained or a replacement QA process been established, the design document defects may have been caught before submission; however, Engineer B\u0027s retirement alone was not sufficient \u2014 Engineer A\u0027s own review failures were the proximate cause",
  "proeth:effect": "Design Document Defects Discovered",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s dependence on Engineer B for quality assurance",
    "Absence of a replacement mentorship or quality assurance mechanism after Engineer B\u0027s retirement",
    "Engineer A\u0027s subsequent independent decisions to use AI without adequate review"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Engineer A (primary); Engineer A\u0027s organization (shared)",
  "proeth:sufficientFactors": [
    "Retirement of QA mentor + no replacement oversight + Engineer A\u0027s cursory review practices together were sufficient to allow defects to reach Client W"
  ],
  "proeth:withinAgentControl": false
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/7#",
    "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/7#CausalChain_7dae5c61",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The AI software produced report text with a polished, consistent style distinct from Engineer A own analytical writing, creating a detectable two-author artifact that Client W identified upon review",
  "proeth:causalSequence": [
    {
      "proeth:description": "AI software produced a polished introduction and contaminant discussion with a distinct writing style",
      "proeth:element": "AI Report Draft Generated",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A reviewed and made minor wording adjustments but did not fully rewrite the AI-generated sections",
      "proeth:element": "Conducted Thorough Report Review",
      "proeth:step": 2
    },
    {
      "proeth:description": "Client W identified that the report read as if written by two different authors, with the AI-generated introduction notably more polished than the data analysis sections",
      "proeth:element": "Report Stylistic Inconsistency Detected",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "AI Report Draft Generated",
  "proeth:counterfactual": "Had Engineer A drafted the report independently or more substantially rewritten the AI-generated text, the stylistic inconsistency would not have been detectable by Client W",
  "proeth:effect": "Report Stylistic Inconsistency Detected",
  "proeth:necessaryFactors": [
    "AI software generating text with a different stylistic register than Engineer A own writing",
    "Engineer A making only minor wording adjustments rather than a full rewrite",
    "Client W having sufficient domain expertise to detect the stylistic discontinuity"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "AI-generated polished prose juxtaposed with Engineer A more technical analytical writing was sufficient to create a detectable inconsistency"
  ],
  "proeth:withinAgentControl": true
}