DP14
Individual
http://proethica.org/ontology/case/7#DP14
Properties
Instance of
Decision Point Id
DP14
Decision question
Should Engineer A proactively disclose AI tool usage to the client and conduct independent verification of all AI-generated design and report content before sealing and submitting deliverables, or is it sufficient to apply standard QA protocols without separate disclosure?
Focus
Engineer A used an AI tool to generate substantial portions of both the design documents and the project report without disclosing this to the client, without maintaining adequate direction and control over AI outputs in the design phase, and without verifying AI-generated design content before sealing. Multiple obligations related to disclosure, responsible charge, and design verification remain unmet. The core tension is whether Engineer A must proactively disclose AI involvement and conduct independent verification before sealing and submitting deliverables, or whether existing QA practices and professional judgment are sufficient.
Option1
Proactively inform the client of AI tool involvement in both the design and report deliverables, conduct independent technical verification of all AI-generated content before sealing, and correct any safety or technical deficiencies identified during review.
Option2
Treat the AI tool as equivalent to conventional engineering software such as CAD or finite element analysis programs, applying the firm's standard quality assurance protocols without issuing a separate disclosure to the client, on the basis that method selection is an internal professional judgment.
Option3
Acknowledge AI tool usage within the project report's methodology section and design document notes without a separate client notification, and apply enhanced verification only to safety-critical design elements while relying on domain expertise for remaining outputs.
Role
Engineer A
TTL
@prefix case7: <http://proethica.org/ontology/case/7#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix proeth: <http://proethica.org/ontology/intermediate#> .
@prefix proeth-cases: <http://proethica.org/ontology/cases#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
case7:DP14 a proeth-cases:DecisionPoint,
owl:NamedIndividual ;
rdfs:label "DP14" ;
proeth:decisionPointId "DP14" ;
proeth:decisionQuestion "Should Engineer A proactively disclose AI tool usage to the client and conduct independent verification of all AI-generated design and report content before sealing and submitting deliverables, or is it sufficient to apply standard QA protocols without separate disclosure?" ;
proeth:focus "Engineer A used an AI tool to generate substantial portions of both the design documents and the project report without disclosing this to the client, without maintaining adequate direction and control over AI outputs in the design phase, and without verifying AI-generated design content before sealing. Multiple obligations related to disclosure, responsible charge, and design verification remain unmet. The core tension is whether Engineer A must proactively disclose AI involvement and conduct independent verification before sealing and submitting deliverables, or whether existing QA practices and professional judgment are sufficient." ;
proeth:option1 "Proactively inform the client of AI tool involvement in both the design and report deliverables, conduct independent technical verification of all AI-generated content before sealing, and correct any safety or technical deficiencies identified during review." ;
proeth:option2 "Treat the AI tool as equivalent to conventional engineering software such as CAD or finite element analysis programs, applying the firm's standard quality assurance protocols without issuing a separate disclosure to the client, on the basis that method selection is an internal professional judgment." ;
proeth:option3 "Acknowledge AI tool usage within the project report's methodology section and design document notes without a separate client notification, and apply enhanced verification only to safety-critical design elements while relying on domain expertise for remaining outputs." ;
proeth:roleLabel "Engineer A" ;
prov:wasAttributedTo "claude-sonnet-4-6" ;
prov:wasGeneratedBy "ProEthica Case 7 Extraction" .
Metadata
Extraction details
Attributed to
claude-sonnet-4-6
Generated by
ProEthica Case 7 Extraction