Step 2: Normative Requirements Pass (Discussion Section)

Extract principles, obligations, constraints, and capabilities from the discussion section

Impaired Engineering
Step 2 of 5

Discussion Section

Section Content:
Discussion:
The primary issues of this case are the competency and professional actions of Engineer B, Engineer Intern C’s apparent complicity in the matter, the “compassion” of Engineer A and any subsequent actions by Engineer A, and the ethical obligations of Engineer R.
The critical assessment of Engineer B’s competency and professional actions is overriding and will lead to other required determinations.
The evaluation of this issue can be determined by separate facts.
The facts are that Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal.
While suffering a stroke by itself was not an ethical problem, the fact that Engineer B chose to sign and seal design drawings without proper review while impaired by this stroke was a problem.
The BER has not previously examined competence as it relates to mental health; however, the facts in this case make the determination of [non]competence straightforward.
Engineer B violated Section II. 2. of the code because he affixed his signature and seal to documents prepared without his direction or control.
This also shows Engineer B was practicing in violation of the state licensure law (Section III.8.a).
The Board further notes that Engineer B’s actions were in violation of NSPE’s Position Statement No. 10-1778: Responsible Charge which states: “The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion.
Engineering decisions must be personally made by the professional engineer or by others over which the professional engineer provides supervisory direction and control authority.
Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.” The actions of Engineer Intern C should be evaluated as well.
Granted, Engineer Intern C is not yet a licensed professional engineer but an intern, and thus is working within the safety net of Engineer B’s guidance and direct supervision.
While this might keep Engineer Intern C from legal censure per the State Engineering Practice Act, it does not absolve Engineer Intern C of ethical responsibility.
The facts suggest Engineer Intern C, a subordinate of Engineer B, was fully aware of Engineer B’s impaired condition.
Further, it appears Engineer Intern C cooperated with Engineer B in their arrangement to continue to deliver engineering design services as soon as it was realized Engineer B was unable to provide guidance, direct supervision or review.
A similar ethical violation is discussed in BER Case 15-2 , in which an engineering report was revised after the report was signed and sealed inappropriately.
The BER determined that the Engineer had an obligation to seek an immediate correction by contacting appropriate authorities, including the state engineering licensure board and other enforcement officials as appropriate.
In summary, Engineer Intern C is ethically culpable through violation of Section II.1.e, Section II.1.f, and Section III.8.a of the Code of Ethics.
What about Engineer A’s actions?
Reference is made to Section I.1 of the Code, engineers shall hold paramount the safety, health, and welfare of the public and, more specifically, Section II.1.e, engineers shall not aid or abet the unlawful practice of engineering by a person or firm and Section II.1.f, engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required.
The BER has almost always taken the position that whenever any violation of the Code or issues of public health, safety, and welfare are uncovered, the proper authorities should be notified.
In BER Case 17-7 , the BER determined that an Engineer had an obligation to further report the situation to the appropriate the local, state, and/or federal authorities to ensure that relevant engineering standards were consistent with the public health, safety, and welfare.
This was a case where a proposed change to an ordinance was contrary to established engineering standards.
Even though Engineer A was a friend of Engineer B, their friendship was not an ethical justification for Engineer A to ignore or conceal Engineer B’s violations.
Code Section III.7, engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action, unambiguously requires that such violations be reported to the appropriate professional body, in this case the State Board.
This determination is also strengthened by Section III.8.a, engineers shall conform with state licensure law.
That being said, the friendship between Engineer A and Engineer B warrants consideration.
Hypothetically, what might an engineer do that would have been both ethical and would also have respected the friendship?
Section III.7 of the Code says engineers “shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers.” By this view and with Engineer B’s knowledge and approval, Engineer A could have privately discussed the matter with proper authorities at the State Board.
Working together, the parties might cooperatively identify a practice alternative consistent with ethical and legal engineering consulting work, say, hiring a qualified temporary engineer – possibly Engineer R – until Engineer B was able to return to full duty.
Further, under such a scenario, the Board might exercise discretion relative to formal sanction (or not) of Engineer B.
Other approaches are also possible.
But any of them must begin with the conviction that the ethics code does not permit engineers to turn a blind eye to the unethical practice of engineering.
Finally, what are Engineer R’s ethical obligations?
The facts reveal it was Engineer R who technically uncovered the incompetent nature of Engineer B’s design and construction documents.
Further, in the aftermath of Engineer R’s discovery, it is reasonable to think Engineer R was informed of Engineer B’s impairment due to a stroke, and also the series of actions by Engineer B and Engineer Intern C that followed.
Since Engineer A was the person who got Engineer R involved in the first place, if Engineer A took the lead in reporting the matter, the report could be styled to note Engineer R’s concurrence.
Otherwise, Engineer R would be obligated to report Engineer B to the State Board (Section II.1.f).
Principles Extraction
LLM Prompt
DUAL PRINCIPLE EXTRACTION - Ethical Principles Analysis THEORETICAL CONTEXT (Chapter 2.2.2): - Principles are ABSTRACT ethical foundations requiring extensional definition through cases - They function like constitutional principles - open-textured and requiring interpretation - Principles mediate moral ideals into concrete reality through context-specific application - They cannot be applied deductively but require balancing and interpretation EXISTING PRINCIPLE CLASSES IN ONTOLOGY: - Competence Principle: Balances professional autonomy with recognition of limitations and need for collaboration. - Confidentiality Principle: Must be balanced against public safety obligations and legal disclosure requirements. - Domain-Specific Principle: Examples: Environmental Stewardship (engineering), Patient Autonomy (medicine), Academic Freedom (education). These address domain-specific ethical ch - Environmental Stewardship Principle: Bridges engineering practice with broader environmental and societal responsibilities. - Ethical Principle: Legacy synonym for Principle. Use :Principle for new concepts. - Fundamental Ethical Principle: Examples: Public Welfare Paramount, Respect for Persons, Justice, Beneficence. These require extensive interpretation and balancing in specific contex - Integrity Principle: Central to professional identity formation and trust maintenance in professional relationships. - Principle: An information content entity representing ethical values and guidelines for conduct. This is the P component of the formal specification D=(R,P,O,S,R - Principle Argument: An argument based on fundamental ethical principles or values. - Principle Refinement: Capability to evolve principles as inconsistencies are resolved and new cases are added (GenEth system, Anderson & Anderson 2018) - Professional Virtue Principle: Examples: Integrity, Competence, Honesty, Professional Courage, Accountability. These shape professional character and decision-making. - Public Welfare Principle: Requires contextual interpretation to balance against client confidentiality and employer loyalty when public safety is at risk. - Relational Principle: Examples: Confidentiality, Loyalty, Fairness, Transparency, Respect for Autonomy. These govern interpersonal professional dynamics. - Transparency Principle: Essential for maintaining trust and enabling stakeholder participation in professional decisions. === TASK === From the following case text (discussion section), extract information at TWO levels: LEVEL 1 - NEW PRINCIPLE CLASSES: Identify ethical principles that appear to be NEW types not covered by existing classes above. Look for: - Fundamental ethical values being invoked - Abstract moral ideals guiding decisions - Constitutional-like principles requiring interpretation - Values that transcend specific rules or obligations For each NEW principle class, provide: - label: Clear principle name (e.g., "Environmental Stewardship", "Professional Autonomy") - definition: What moral ideal this principle represents - abstract_nature: The abstract ethical foundation (justice, welfare, autonomy, etc.) - extensional_examples: Concrete cases/situations where this principle applies - value_basis: Core moral value underlying the principle - application_context: Professional domains or situations where relevant - operationalization: How this abstract principle becomes concrete in practice - balancing_requirements: What other principles it typically must be balanced against - examples_from_case: How this principle appears in the case text LEVEL 2 - PRINCIPLE INDIVIDUALS: Identify specific instances where principles are invoked or applied. For each instance: - identifier: Unique identifier for this principle instance (e.g., "PublicSafety_Case8_Discussion") - principle_class: Which principle class it instantiates (use existing classes when possible) - concrete_expression: EXACT text showing how the principle is expressed - invoked_by: Who invokes or appeals to this principle - applied_to: What decision/situation/dilemma it applies to - interpretation: How the principle is interpreted in this specific context - balancing_with: Other principles that must be balanced against it - tension_resolution: How conflicts between principles are resolved - case_relevance: Why this principle matters in this specific case IMPORTANT: - Focus on ABSTRACT ethical foundations, not specific rules or procedures - Principles are broader than obligations - they generate obligations in context - Use EXACT quotes from case text where principles are expressed - Distinguish between the abstract principle CLASS and its concrete APPLICATION CASE TEXT: The primary issues of this case are the competency and professional actions of Engineer B, Engineer Intern C’s apparent complicity in the matter, the “compassion” of Engineer A and any subsequent actions by Engineer A, and the ethical obligations of Engineer R. The critical assessment of Engineer B’s competency and professional actions is overriding and will lead to other required determinations. The evaluation of this issue can be determined by separate facts. The facts are that Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal. While suffering a stroke by itself was not an ethical problem, the fact that Engineer B chose to sign and seal design drawings without proper review while impaired by this stroke was a problem. The BER has not previously examined competence as it relates to mental health; however, the facts in this case make the determination of [non]competence straightforward. Engineer B violated Section II. 2. of the code because he affixed his signature and seal to documents prepared without his direction or control. This also shows Engineer B was practicing in violation of the state licensure law (Section III.8.a). The Board further notes that Engineer B’s actions were in violation of NSPE’s Position Statement No. 10-1778: Responsible Charge which states: “The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion. Engineering decisions must be personally made by the professional engineer or by others over which the professional engineer provides supervisory direction and control authority. Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.” The actions of Engineer Intern C should be evaluated as well. Granted, Engineer Intern C is not yet a licensed professional engineer but an intern, and thus is working within the safety net of Engineer B’s guidance and direct supervision. While this might keep Engineer Intern C from legal censure per the State Engineering Practice Act, it does not absolve Engineer Intern C of ethical responsibility. The facts suggest Engineer Intern C, a subordinate of Engineer B, was fully aware of Engineer B’s impaired condition. Further, it appears Engineer Intern C cooperated with Engineer B in their arrangement to continue to deliver engineering design services as soon as it was realized Engineer B was unable to provide guidance, direct supervision or review. A similar ethical violation is discussed in BER Case 15-2 , in which an engineering report was revised after the report was signed and sealed inappropriately. The BER determined that the Engineer had an obligation to seek an immediate correction by contacting appropriate authorities, including the state engineering licensure board and other enforcement officials as appropriate. In summary, Engineer Intern C is ethically culpable through violation of Section II.1.e, Section II.1.f, and Section III.8.a of the Code of Ethics. What about Engineer A’s actions? Reference is made to Section I.1 of the Code, engineers shall hold paramount the safety, health, and welfare of the public and, more specifically, Section II.1.e, engineers shall not aid or abet the unlawful practice of engineering by a person or firm and Section II.1.f, engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required. The BER has almost always taken the position that whenever any violation of the Code or issues of public health, safety, and welfare are uncovered, the proper authorities should be notified. In BER Case 17-7 , the BER determined that an Engineer had an obligation to further report the situation to the appropriate the local, state, and/or federal authorities to ensure that relevant engineering standards were consistent with the public health, safety, and welfare. This was a case where a proposed change to an ordinance was contrary to established engineering standards. Even though Engineer A was a friend of Engineer B, their friendship was not an ethical justification for Engineer A to ignore or conceal Engineer B’s violations. Code Section III.7, engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action, unambiguously requires that such violations be reported to the appropriate professional body, in this case the State Board. This determination is also strengthened by Section III.8.a, engineers shall conform with state licensure law. That being said, the friendship between Engineer A and Engineer B warrants consideration. Hypothetically, what might an engineer do that would have been both ethical and would also have respected the friendship? Section III.7 of the Code says engineers “shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers.” By this view and with Engineer B’s knowledge and approval, Engineer A could have privately discussed the matter with proper authorities at the State Board. Working together, the parties might cooperatively identify a practice alternative consistent with ethical and legal engineering consulting work, say, hiring a qualified temporary engineer – possibly Engineer R – until Engineer B was able to return to full duty. Further, under such a scenario, the Board might exercise discretion relative to formal sanction (or not) of Engineer B. Other approaches are also possible. But any of them must begin with the conviction that the ethics code does not permit engineers to turn a blind eye to the unethical practice of engineering. Finally, what are Engineer R’s ethical obligations? The facts reveal it was Engineer R who technically uncovered the incompetent nature of Engineer B’s design and construction documents. Further, in the aftermath of Engineer R’s discovery, it is reasonable to think Engineer R was informed of Engineer B’s impairment due to a stroke, and also the series of actions by Engineer B and Engineer Intern C that followed. Since Engineer A was the person who got Engineer R involved in the first place, if Engineer A took the lead in reporting the matter, the report could be styled to note Engineer R’s concurrence. Otherwise, Engineer R would be obligated to report Engineer B to the State Board (Section II.1.f). Respond with valid JSON in this format: { "new_principle_classes": [ { "label": "Sustainable Development", "definition": "Principle that engineering solutions must balance current needs with long-term environmental and societal impacts", "abstract_nature": "Intergenerational justice and environmental stewardship", "extensional_examples": ["Green building design", "Renewable energy projects", "Resource conservation"], "value_basis": "Responsibility to future generations", "application_context": ["Infrastructure projects", "Environmental engineering", "Urban planning"], "operationalization": "Through environmental impact assessments, lifecycle analysis, sustainable design criteria", "balancing_requirements": ["Economic feasibility", "Immediate safety needs", "Client requirements"], "examples_from_case": ["Engineer considered long-term environmental impacts", "balanced immediate needs with sustainability"], "source_text": "Engineer considered long-term environmental impacts and balanced immediate needs with sustainability" } ], "principle_individuals": [ { "identifier": "PublicSafety_Case8_Facts", "principle_class": "Public Safety", "concrete_expression": "the safety of the public must be held paramount", "invoked_by": ["Engineer L"], "applied_to": ["stormwater management system design"], "interpretation": "Safety considerations override cost savings in drainage design", "source_text": "the safety of the public must be held paramount", "balancing_with": ["Cost Efficiency", "Client Interests"], "tension_resolution": "Safety takes precedence even if it increases project costs", "case_relevance": "Critical for evaluating adequacy of proposed drainage solution" } ] }
Saved: 2025-12-29 16:29
LLM Response
```json
{
    "new_principle_classes": [
        {
            "label": "Professional Compassion",
            "definition": "Principle that recognizes human vulnerability and personal relationships while maintaining professional standards",
            "abstract_nature": "Balancing empathy and human dignity with professional obligations",
            "extensional_examples": ["Colleague experiencing health crisis", "Professional facing personal tragedy", "Impaired practitioner situations"],
            "value_basis": "Human dignity and care ethics",
            "application_context": ["Professional impairment cases", "Colleague assistance programs", "Ethics enforcement"],
            "operationalization": "Through collaborative problem-solving with authorities while respecting personal dignity",
            "balancing_requirements": ["Public safety obligations", "Reporting requirements", "Professional standards"],
            "examples_from_case": "The 'compassion' of Engineer A and the consideration of friendship while maintaining ethical obligations",
            "source_text": "The primary issues of this case are...the 'compassion' of Engineer A"
        },
        {
            "label": "Cooperative Resolution",
            "definition": "Principle that ethical violations can be addressed through collaborative approaches that maintain professional dignity while ensuring compliance",
            "abstract_nature": "Restorative justice and collaborative problem-solving in professional ethics",
            "extensional_examples": ["Working with boards on remediation", "Temporary coverage arrangements", "Voluntary compliance programs"],
            "value_basis": "Professional rehabilitation and constructive resolution",
            "application_context": ["Professional misconduct cases", "Impairment situations", "Ethics enforcement"],
            "operationalization": "Through private discussions with authorities, cooperative identification of alternatives, discretionary enforcement",
            "balancing_requirements": ["Public protection", "Enforcement requirements", "Professional accountability"],
            "examples_from_case": "Engineer A could have privately discussed with State Board to identify practice alternatives",
            "source_text": "Engineer A could have privately discussed the matter with proper authorities at the State Board. Working together, the parties might cooperatively identify a practice alternative"
        }
    ],
    "principle_individuals": [
        {
            "identifier": "PublicWelfare_Paramount_Case",
            "principle_class": "Public Welfare Principle",
            "concrete_expression": "engineers shall hold paramount the safety, health, and welfare of the public",
            "invoked_by": ["BER"],
            "applied_to": ["Engineer A's obligation to report Engineer B's impairment"],
            "interpretation": "Public welfare overrides personal friendship and requires reporting violations",
            "source_text": "Section I.1 of the Code, engineers shall hold paramount the safety, health, and welfare of the public",
            "balancing_with": ["Friendship/loyalty to Engineer B"],
            "tension_resolution": "Public welfare takes precedence over personal relationships",
            "case_relevance": "Establishes primary obligation that overrides compassion for impaired colleague"
        },
        {
            "identifier": "Competence_EngineerB_Impairment",
            "principle_class": "Competence Principle",
            "concrete_expression": "Engineer B suffered a stroke and was unable to adequately direct and review engineering designs",
            "invoked_by": ["BER"],
            "applied_to": ["Engineer B's continued practice while impaired"],
            "interpretation": "Mental/physical impairment that prevents adequate review violates competence requirements",
            "source_text": "Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal",
            "balancing_with": ["Professional autonomy", "Right to practice"],
            "tension_resolution": "Competence requirements are non-negotiable regardless of cause of impairment",
            "case_relevance": "Central violation that triggers all other ethical obligations"
        },
        {
            "identifier": "Transparency_Reporting_Obligation",
            "principle_class": "Transparency Principle",
            "concrete_expression": "engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies",
            "invoked_by": ["BER"],
            "applied_to": ["Engineer A's knowledge of Engineer B's violations"],
            "interpretation": "Knowledge of violations creates mandatory reporting obligation",
            "source_text": "Section II.1.f, engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies",
            "balancing_with": ["Personal loyalty", "Friendship"],
            "tension_resolution": "Reporting obligation is mandatory and cannot be overridden by personal relationships",
            "case_relevance": "Establishes Engineer A's clear duty to report despite friendship"
        },
        {
            "identifier": "Professional_Integrity_NonMalicious",
            "principle_class": "Integrity Principle",
            "concrete_expression": "engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation",
            "invoked_by": ["BER"],
            "applied_to": ["How Engineer A should handle reporting"],
            "interpretation": "Reporting violations must be done without malice and with respect for professional dignity",
            "source_text": "Section III.7 of the Code says engineers 'shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers.'",
            "balancing_with": ["Reporting obligations", "Public protection"],
            "tension_resolution": "Report factually and cooperatively without unnecessary harm to reputation",
            "case_relevance": "Guides how reporting can be done ethically while respecting friendship"
        },
        {
            "identifier": "Responsible_Charge_Principle",
            "principle_class": "Competence Principle",
            "concrete_expression": "The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion",
            "invoked_by": ["NSPE Position Statement"],
            "applied_to": ["Engineer B's signing and sealing without proper review"],
            "interpretation": "Responsible charge requires active engagement throughout design process, not just review",
            "source_text": "The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion",
            "balancing_with": ["Efficiency", "Trust in subordinates"],
            "tension_resolution": "Active engagement is non-negotiable requirement for responsible charge",
            "case_relevance": "Clarifies that Engineer B's arrangement violated responsible charge requirements"
        }
    ]
}
```
Obligations Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for obligations (professional duties and requirements). Based on the literature: - Obligations are CONCRETE PROFESSIONAL DUTIES derived from abstract principles (Hallamaa & Kalliokoski 2022) - They specify what professionals MUST, SHOULD, or MUST NOT do (Dennis et al. 2016) - Obligations have deontic force and are enforceable (Wooldridge & Jennings 1995) - They operationalize principles in specific contexts (Kong et al. 2020) Your task is to: 1. Identify NEW OBLIGATION CLASSES not in the existing ontology 2. Extract SPECIFIC OBLIGATION INDIVIDUALS from the case EXISTING OBLIGATIONS IN ONTOLOGY (check if your identified obligations match these before creating new classes): - Attribution Obligation: Duty to properly cite and acknowledge all sources, tools, and methods used in creating professional deliverables - Collegial Obligation: Duties toward professional peers including respect, fairness, and credit for work - Competence Obligation: Requirement to perform services only in areas of competence (NSPE II.2) - Conditional Obligation: Obligations that apply only when specific conditions are met - Confidentiality Obligation: Duty to protect confidential information of clients or employers (NSPE III.4) - Defeasible Obligation: Obligations that admit justified exceptions under specified conditions (Ganascia 2007) - Disclosure Obligation: Requirement to inform stakeholders about conflicts, limitations, or risks (NSPE II.3.a) - Ethical Obligation: Obligations arising from ethical principles beyond legal requirements - Legal Obligation: Obligations arising from legal requirements and regulations - Mandatory Obligation: Obligations that MUST be fulfilled (deontic force: mandatory) - Obligation: An information content entity expressing required actions or behaviors in professional contexts. This is the O component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Prima Facie Obligation: Obligations that hold at first appearance but may be overridden by stronger duties (Anderson & Anderson) - Professional Obligation: A duty or responsibility arising from professional role or standards - Quality Assurance Obligation: Requirement to implement appropriate review and verification processes for all professional deliverables before submission - Reporting Obligation: Duty to report violations or unsafe conditions to appropriate authorities - Responsible Charge Obligation: Duty to maintain active engagement and personal decision-making authority throughout engineering process from conception to completion - Safety Obligation: Duty to hold paramount the safety, health, and welfare of the public (NSPE I.1) - Technology Competence Obligation: Requirement to understand and verify the capabilities, limitations, and risks of technological tools used in professional practice - Technology Verification Obligation: Requirement to thoroughly verify and validate outputs from technological tools including AI before incorporating them into professional work Analyze this discussion section: The primary issues of this case are the competency and professional actions of Engineer B, Engineer Intern C’s apparent complicity in the matter, the “compassion” of Engineer A and any subsequent actions by Engineer A, and the ethical obligations of Engineer R. The critical assessment of Engineer B’s competency and professional actions is overriding and will lead to other required determinations. The evaluation of this issue can be determined by separate facts. The facts are that Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal. While suffering a stroke by itself was not an ethical problem, the fact that Engineer B chose to sign and seal design drawings without proper review while impaired by this stroke was a problem. The BER has not previously examined competence as it relates to mental health; however, the facts in this case make the determination of [non]competence straightforward. Engineer B violated Section II. 2. of the code because he affixed his signature and seal to documents prepared without his direction or control. This also shows Engineer B was practicing in violation of the state licensure law (Section III.8.a). The Board further notes that Engineer B’s actions were in violation of NSPE’s Position Statement No. 10-1778: Responsible Charge which states: “The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion. Engineering decisions must be personally made by the professional engineer or by others over which the professional engineer provides supervisory direction and control authority. Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.” The actions of Engineer Intern C should be evaluated as well. Granted, Engineer Intern C is not yet a licensed professional engineer but an intern, and thus is working within the safety net of Engineer B’s guidance and direct supervision. While this might keep Engineer Intern C from legal censure per the State Engineering Practice Act, it does not absolve Engineer Intern C of ethical responsibility. The facts suggest Engineer Intern C, a subordinate of Engineer B, was fully aware of Engineer B’s impaired condition. Further, it appears Engineer Intern C cooperated with Engineer B in their arrangement to continue to deliver engineering design services as soon as it was realized Engineer B was unable to provide guidance, direct supervision or review. A similar ethical violation is discussed in BER Case 15-2 , in which an engineering report was revised after the report was signed and sealed inappropriately. The BER determined that the Engineer had an obligation to seek an immediate correction by contacting appropriate authorities, including the state engineering licensure board and other enforcement officials as appropriate. In summary, Engineer Intern C is ethically culpable through violation of Section II.1.e, Section II.1.f, and Section III.8.a of the Code of Ethics. What about Engineer A’s actions? Reference is made to Section I.1 of the Code, engineers shall hold paramount the safety, health, and welfare of the public and, more specifically, Section II.1.e, engineers shall not aid or abet the unlawful practice of engineering by a person or firm and Section II.1.f, engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required. The BER has almost always taken the position that whenever any violation of the Code or issues of public health, safety, and welfare are uncovered, the proper authorities should be notified. In BER Case 17-7 , the BER determined that an Engineer had an obligation to further report the situation to the appropriate the local, state, and/or federal authorities to ensure that relevant engineering standards were consistent with the public health, safety, and welfare. This was a case where a proposed change to an ordinance was contrary to established engineering standards. Even though Engineer A was a friend of Engineer B, their friendship was not an ethical justification for Engineer A to ignore or conceal Engineer B’s violations. Code Section III.7, engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action, unambiguously requires that such violations be reported to the appropriate professional body, in this case the State Board. This determination is also strengthened by Section III.8.a, engineers shall conform with state licensure law. That being said, the friendship between Engineer A and Engineer B warrants consideration. Hypothetically, what might an engineer do that would have been both ethical and would also have respected the friendship? Section III.7 of the Code says engineers “shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers.” By this view and with Engineer B’s knowledge and approval, Engineer A could have privately discussed the matter with proper authorities at the State Board. Working together, the parties might cooperatively identify a practice alternative consistent with ethical and legal engineering consulting work, say, hiring a qualified temporary engineer – possibly Engineer R – until Engineer B was able to return to full duty. Further, under such a scenario, the Board might exercise discretion relative to formal sanction (or not) of Engineer B. Other approaches are also possible. But any of them must begin with the conviction that the ethics code does not permit engineers to turn a blind eye to the unethical practice of engineering. Finally, what are Engineer R’s ethical obligations? The facts reveal it was Engineer R who technically uncovered the incompetent nature of Engineer B’s design and construction documents. Further, in the aftermath of Engineer R’s discovery, it is reasonable to think Engineer R was informed of Engineer B’s impairment due to a stroke, and also the series of actions by Engineer B and Engineer Intern C that followed. Since Engineer A was the person who got Engineer R involved in the first place, if Engineer A took the lead in reporting the matter, the report could be styled to note Engineer R’s concurrence. Otherwise, Engineer R would be obligated to report Engineer B to the State Board (Section II.1.f). Extract obligations following this JSON structure: { "new_obligation_classes": [ { "label": "Clear, specific obligation class name", "definition": "What this type of obligation requires professionals to do", "derived_from_principle": "Which principle this operationalizes (e.g., 'Public Safety', 'Honesty')", "duty_type": "professional|legal|ethical|societal", "enforcement_mechanism": "How this obligation is typically enforced", "violation_consequences": "What happens when this obligation is violated", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this obligation is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "obligation_individuals": [ { "identifier": "Unique name for this specific obligation instance", "obligation_class": "Name of the obligation class (new or existing)", "obligated_party": "Who has this obligation (e.g., 'Engineer L', 'All Licensed PEs')", "obligation_statement": "The specific duty statement (e.g., 'Report safety risks to authorities')", "derived_from": "Source principle or law (e.g., 'NSPE Code', 'State Law')", "enforcement_context": "How enforced in this case", "temporal_scope": "When this obligation applies", "compliance_status": "met|unmet|unclear|pending", "case_context": "How this obligation manifests in the specific case", "source_text": "EXACT text snippet from case where this obligation is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW obligation types that represent novel professional duties 2. Specific obligation instances showing how duties apply in this case 3. The relationship between obligations and the principles they operationalize 4. Enforcement mechanisms and compliance status Return ONLY the JSON structure, no additional text.
Saved: 2025-12-29 16:29
LLM Response
```json
{
  "new_obligation_classes": [
    {
      "label": "Subordinate Reporting Obligation",
      "definition": "Duty of subordinate professionals to report unethical practices even when working under supervision of a licensed professional",
      "derived_from_principle": "Professional Integrity",
      "duty_type": "ethical",
      "enforcement_mechanism": "Professional board review and potential disciplinary action",
      "violation_consequences": "Ethical censure, potential impact on future licensure",
      "examples_from_case": ["Engineer Intern C's duty to report Engineer B's impairment", "Subordinate's ethical responsibility despite working under supervision"],
      "source_text": "it does not absolve Engineer Intern C of ethical responsibility",
      "confidence": 0.85,
      "reasoning": "Distinct from general Reporting Obligation as it specifically addresses subordinates/interns who work under supervision but still have independent ethical duties"
    },
    {
      "label": "Cooperative Remediation Obligation",
      "definition": "Duty to work cooperatively with authorities to identify practice alternatives when violations are discovered, balancing professional relationships with ethical duties",
      "derived_from_principle": "Professional Collegiality and Public Safety",
      "duty_type": "ethical",
      "enforcement_mechanism": "Professional board discretion and cooperative resolution",
      "violation_consequences": "Loss of opportunity for reduced sanctions, damage to professional relationships",
      "examples_from_case": ["Engineer A could have privately discussed with authorities", "Working together to identify practice alternatives"],
      "source_text": "Engineer A could have privately discussed the matter with proper authorities at the State Board",
      "confidence": 0.75,
      "reasoning": "Goes beyond simple reporting to include cooperative problem-solving with authorities while respecting professional relationships"
    }
  ],
  "obligation_individuals": [
    {
      "identifier": "EngineerB_CompetenceObligation",
      "obligation_class": "Competence Obligation",
      "obligated_party": "Engineer B",
      "obligation_statement": "Must not sign and seal design drawings without proper review while impaired",
      "derived_from": "NSPE Code Section II.2",
      "enforcement_context": "State licensure board review",
      "temporal_scope": "During period of impairment following stroke",
      "compliance_status": "unmet",
      "case_context": "Engineer B violated by signing/sealing documents while unable to adequately direct and review",
      "source_text": "Engineer B violated Section II. 2. of the code because he affixed his signature and seal to documents prepared without his direction or control",
      "is_existing_class": true,
      "confidence": 1.0
    },
    {
      "identifier": "EngineerB_ResponsibleChargeObligation",
      "obligation_class": "Responsible Charge Obligation",
      "obligated_party": "Engineer B",
      "obligation_statement": "Must be actively engaged in engineering process from conception to completion",
      "derived_from": "NSPE Position Statement No. 10-1778",
      "enforcement_context": "Professional standards enforcement",
      "temporal_scope": "Throughout all engineering projects",
      "compliance_status": "unmet",
      "case_context": "Engineer B failed to maintain active engagement and personal decision-making due to stroke impairment",
      "source_text": "Engineer B's actions were in violation of NSPE's Position Statement No. 10-1778: Responsible Charge",
      "is_existing_class": true,
      "confidence": 1.0
    },
    {
      "identifier": "EngineerInternC_ReportingObligation",
      "obligation_class": "Subordinate Reporting Obligation",
      "obligated_party": "Engineer Intern C",
      "obligation_statement": "Must report Engineer B's impaired condition and inability to provide supervision",
      "derived_from": "NSPE Code Section II.1.f",
      "enforcement_context": "Ethical review despite lack of licensure",
      "temporal_scope": "Upon awareness of Engineer B's impairment",
      "compliance_status": "unmet",
      "case_context": "Engineer Intern C cooperated with impaired arrangement instead of reporting",
      "source_text": "Engineer Intern C is ethically culpable through violation of Section II.1.e, Section II.1.f",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerA_ReportingObligation",
      "obligation_class": "Reporting Obligation",
      "obligated_party": "Engineer A",
      "obligation_statement": "Must report Engineer B's violations to State Board despite friendship",
      "derived_from": "NSPE Code Section III.7",
      "enforcement_context": "State Board reporting requirements",
      "temporal_scope": "Upon discovery of violations",
      "compliance_status": "unclear",
      "case_context": "Engineer A's friendship with Engineer B does not excuse reporting duty",
      "source_text": "Code Section III.7, engineers who believe others are guilty of unethical or illegal practice shall present such information",
      "is_existing_class": true,
      "confidence": 1.0
    },
    {
      "identifier": "EngineerA_SafetyObligation",
      "obligation_class": "Safety Obligation",
      "obligated_party": "Engineer A",
      "obligation_statement": "Must hold paramount public safety by reporting unsafe engineering practices",
      "derived_from": "NSPE Code Section I.1",
      "enforcement_context": "Professional ethics enforcement",
      "temporal_scope": "Upon awareness of safety risks",
      "compliance_status": "unclear",
      "case_context": "Engineer A must prioritize public safety over personal friendship",
      "source_text": "engineers shall hold paramount the safety, health, and welfare of the public",
      "is_existing_class": true,
      "confidence": 1.0
    },
    {
      "identifier": "EngineerR_ReportingObligation",
      "obligation_class": "Reporting Obligation",
      "obligated_party": "Engineer R",
      "obligation_statement": "Must report Engineer B's incompetent design work to State Board",
      "derived_from": "NSPE Code Section II.1.f",
      "enforcement_context": "State Board reporting",
      "temporal_scope": "Upon discovery of incompetent work",
      "compliance_status": "pending",
      "case_context": "Engineer R discovered incompetent nature of Engineer B's documents",
      "source_text": "Engineer R would be obligated to report Engineer B to the State Board (Section II.1.f)",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerB_LegalObligation",
      "obligation_class": "Legal Obligation",
      "obligated_party": "Engineer B",
      "obligation_statement": "Must conform with state licensure law",
      "derived_from": "State Engineering Practice Act",
      "enforcement_context": "State licensure board enforcement",
      "temporal_scope": "Throughout professional practice",
      "compliance_status": "unmet",
      "case_context": "Engineer B practiced in violation of state licensure law",
      "source_text": "Engineer B was practicing in violation of the state licensure law (Section III.8.a)",
      "is_existing_class": true,
      "confidence": 1.0
    }
  ]
}
```
Constraints Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for constraints (boundaries, limitations, and restrictions). Based on the literature: - Constraints are INVIOLABLE BOUNDARIES that limit acceptable actions (Dennis et al. 2016) - They differ from obligations by being restrictions rather than requirements - Constraints can be legal, physical, resource-based, or procedural - They define the space within which ethical decisions must be made Your task is to: 1. Identify NEW CONSTRAINT CLASSES not in the existing ontology 2. Extract SPECIFIC CONSTRAINT INDIVIDUALS from the case EXISTING CONSTRAINTS IN ONTOLOGY (check if your identified constraints match these before creating new classes): - Attribution Constraint: Requirements and limitations regarding the disclosure and citation of tools, methods, or sources used in professional work products - Competence Constraint: Boundaries defined by agent capabilities and technical limitations (Hallamaa & Kalliokoski 2022) - Confidentiality Constraint: Boundaries on information disclosure and privacy (Dennis et al. 2016) - Constraint: An information content entity expressing limitations or restrictions on professional actions or decisions. This is the Cs component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Defeasible Constraint: Constraints that admit justified exceptions under specified conditions (Ganascia 2007) - Ethical Constraint: Professional ethical boundaries beyond legal requirements (Benzmüller et al. 2020) - Inviolable Constraint: Absolute constraints that cannot be overridden under any circumstances (Dennis et al. 2016) - Jurisdictional Constraint: Boundaries of authority and geographical or organizational scope (Dennis et al. 2016) - Legal Constraint: Constraints arising from legal requirements and statutes that establish inviolable boundaries (Kroll 2020, Stenseke 2024) - Priority Constraint: Constraints establishing precedence when multiple requirements conflict (Scheutz & Malle 2014) - Procedural Constraint: Requirements for following specific processes or protocols (Furbach et al. 2014) - Regulatory Constraint: Constraints from regulatory bodies and professional standards organizations (Taddeo et al. 2024) - Resource Constraint: Limitations on available time, budget, materials, or human resources (Ganascia 2007) - Safety Constraint: Constraints ensuring safety requirements are met (Arkin 2008) - Technology Substitution Constraint: Boundaries preventing technology from replacing professional judgment and human oversight in critical decision-making Analyze this discussion section: The primary issues of this case are the competency and professional actions of Engineer B, Engineer Intern C’s apparent complicity in the matter, the “compassion” of Engineer A and any subsequent actions by Engineer A, and the ethical obligations of Engineer R. The critical assessment of Engineer B’s competency and professional actions is overriding and will lead to other required determinations. The evaluation of this issue can be determined by separate facts. The facts are that Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal. While suffering a stroke by itself was not an ethical problem, the fact that Engineer B chose to sign and seal design drawings without proper review while impaired by this stroke was a problem. The BER has not previously examined competence as it relates to mental health; however, the facts in this case make the determination of [non]competence straightforward. Engineer B violated Section II. 2. of the code because he affixed his signature and seal to documents prepared without his direction or control. This also shows Engineer B was practicing in violation of the state licensure law (Section III.8.a). The Board further notes that Engineer B’s actions were in violation of NSPE’s Position Statement No. 10-1778: Responsible Charge which states: “The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion. Engineering decisions must be personally made by the professional engineer or by others over which the professional engineer provides supervisory direction and control authority. Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.” The actions of Engineer Intern C should be evaluated as well. Granted, Engineer Intern C is not yet a licensed professional engineer but an intern, and thus is working within the safety net of Engineer B’s guidance and direct supervision. While this might keep Engineer Intern C from legal censure per the State Engineering Practice Act, it does not absolve Engineer Intern C of ethical responsibility. The facts suggest Engineer Intern C, a subordinate of Engineer B, was fully aware of Engineer B’s impaired condition. Further, it appears Engineer Intern C cooperated with Engineer B in their arrangement to continue to deliver engineering design services as soon as it was realized Engineer B was unable to provide guidance, direct supervision or review. A similar ethical violation is discussed in BER Case 15-2 , in which an engineering report was revised after the report was signed and sealed inappropriately. The BER determined that the Engineer had an obligation to seek an immediate correction by contacting appropriate authorities, including the state engineering licensure board and other enforcement officials as appropriate. In summary, Engineer Intern C is ethically culpable through violation of Section II.1.e, Section II.1.f, and Section III.8.a of the Code of Ethics. What about Engineer A’s actions? Reference is made to Section I.1 of the Code, engineers shall hold paramount the safety, health, and welfare of the public and, more specifically, Section II.1.e, engineers shall not aid or abet the unlawful practice of engineering by a person or firm and Section II.1.f, engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required. The BER has almost always taken the position that whenever any violation of the Code or issues of public health, safety, and welfare are uncovered, the proper authorities should be notified. In BER Case 17-7 , the BER determined that an Engineer had an obligation to further report the situation to the appropriate the local, state, and/or federal authorities to ensure that relevant engineering standards were consistent with the public health, safety, and welfare. This was a case where a proposed change to an ordinance was contrary to established engineering standards. Even though Engineer A was a friend of Engineer B, their friendship was not an ethical justification for Engineer A to ignore or conceal Engineer B’s violations. Code Section III.7, engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action, unambiguously requires that such violations be reported to the appropriate professional body, in this case the State Board. This determination is also strengthened by Section III.8.a, engineers shall conform with state licensure law. That being said, the friendship between Engineer A and Engineer B warrants consideration. Hypothetically, what might an engineer do that would have been both ethical and would also have respected the friendship? Section III.7 of the Code says engineers “shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers.” By this view and with Engineer B’s knowledge and approval, Engineer A could have privately discussed the matter with proper authorities at the State Board. Working together, the parties might cooperatively identify a practice alternative consistent with ethical and legal engineering consulting work, say, hiring a qualified temporary engineer – possibly Engineer R – until Engineer B was able to return to full duty. Further, under such a scenario, the Board might exercise discretion relative to formal sanction (or not) of Engineer B. Other approaches are also possible. But any of them must begin with the conviction that the ethics code does not permit engineers to turn a blind eye to the unethical practice of engineering. Finally, what are Engineer R’s ethical obligations? The facts reveal it was Engineer R who technically uncovered the incompetent nature of Engineer B’s design and construction documents. Further, in the aftermath of Engineer R’s discovery, it is reasonable to think Engineer R was informed of Engineer B’s impairment due to a stroke, and also the series of actions by Engineer B and Engineer Intern C that followed. Since Engineer A was the person who got Engineer R involved in the first place, if Engineer A took the lead in reporting the matter, the report could be styled to note Engineer R’s concurrence. Otherwise, Engineer R would be obligated to report Engineer B to the State Board (Section II.1.f). Extract constraints following this JSON structure: { "new_constraint_classes": [ { "label": "Clear, specific constraint class name", "definition": "What this type of constraint limits or restricts", "constraint_type": "legal|physical|resource|temporal|procedural", "flexibility": "hard|soft|negotiable", "violation_impact": "What happens if this constraint is violated", "mitigation_possible": "Whether and how this constraint can be mitigated", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this constraint is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "constraint_individuals": [ { "identifier": "Unique name for this specific constraint instance", "constraint_class": "Name of the constraint class (new or existing)", "constrained_entity": "What or who is constrained (e.g., 'Engineer L', 'Project')", "constraint_statement": "The specific limitation (e.g., 'Cannot exceed budget of $X')", "source": "Origin of constraint (e.g., 'Client budget', 'Environmental law')", "enforcement_mechanism": "How this constraint is enforced", "temporal_scope": "When this constraint applies", "severity": "critical|major|minor", "case_context": "How this constraint manifests in the specific case", "source_text": "EXACT text snippet from case where this constraint is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW constraint types that represent novel limitations or boundaries 2. Specific constraint instances showing how limitations apply in this case 3. The difference between constraints (boundaries) and obligations (duties) 4. Impact and severity of constraints on decision-making Return ONLY the JSON structure, no additional text.
Saved: 2025-12-29 16:30
LLM Response
```json
{
  "new_constraint_classes": [
    {
      "label": "Impairment Constraint",
      "definition": "Limitations on professional practice arising from physical or mental conditions that prevent adequate performance of engineering duties",
      "constraint_type": "physical",
      "flexibility": "hard",
      "violation_impact": "Compromises public safety and violates professional standards",
      "mitigation_possible": "Temporary delegation of responsibilities or medical leave until recovery",
      "examples_from_case": ["Engineer B's stroke preventing adequate review", "Unable to direct and review engineering designs"],
      "source_text": "Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal",
      "confidence": 0.9,
      "reasoning": "Distinct from Competence Constraint as it specifically addresses temporary or permanent medical/physical impairments rather than skill limitations"
    },
    {
      "label": "Supervisory Authority Constraint",
      "definition": "Boundaries on what actions can be taken without proper supervisory direction and control from a licensed professional",
      "constraint_type": "procedural",
      "flexibility": "hard",
      "violation_impact": "Invalid work products and potential legal liability",
      "mitigation_possible": "Only through proper supervision by qualified professional",
      "examples_from_case": ["Engineer Intern C working without proper supervision", "Documents prepared without Engineer B's direction or control"],
      "source_text": "Engineer Intern C is not yet a licensed professional engineer but an intern, and thus is working within the safety net of Engineer B's guidance",
      "confidence": 0.85,
      "reasoning": "Goes beyond Procedural Constraint to specifically address the hierarchical supervision requirements in engineering practice"
    }
  ],
  "constraint_individuals": [
    {
      "identifier": "EngineerB_StrokeImpairment",
      "constraint_class": "Impairment Constraint",
      "constrained_entity": "Engineer B",
      "constraint_statement": "Cannot adequately direct and review engineering designs due to stroke",
      "source": "Medical condition (stroke)",
      "enforcement_mechanism": "Professional standards and state licensure law",
      "temporal_scope": "During period of impairment from stroke",
      "severity": "critical",
      "case_context": "Engineer B continued signing and sealing documents despite being unable to review them",
      "source_text": "Engineer B suffered a stroke and was unable to adequately direct and review engineering designs",
      "is_existing_class": false,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerB_ResponsibleChargeRequirement",
      "constraint_class": "Procedural Constraint",
      "constrained_entity": "Engineer B",
      "constraint_statement": "Must be actively engaged from conception to completion to be in Responsible Charge",
      "source": "NSPE Position Statement No. 10-1778",
      "enforcement_mechanism": "Professional standards enforcement",
      "temporal_scope": "Whenever signing and sealing documents",
      "severity": "critical",
      "case_context": "Engineer B violated responsible charge requirements by not being involved in design process",
      "source_text": "The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion",
      "is_existing_class": true,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerInternC_SupervisionRequirement",
      "constraint_class": "Supervisory Authority Constraint",
      "constrained_entity": "Engineer Intern C",
      "constraint_statement": "Cannot practice engineering without guidance and direct supervision of licensed PE",
      "source": "State Engineering Practice Act",
      "enforcement_mechanism": "State licensure board",
      "temporal_scope": "Until obtaining PE license",
      "severity": "critical",
      "case_context": "Engineer Intern C continued work despite knowing Engineer B could not provide supervision",
      "source_text": "Engineer Intern C is not yet a licensed professional engineer but an intern, and thus is working within the safety net",
      "is_existing_class": false,
      "confidence": 0.88
    },
    {
      "identifier": "EngineerA_ReportingBoundary",
      "constraint_class": "Ethical Constraint",
      "constrained_entity": "Engineer A",
      "constraint_statement": "Cannot conceal or ignore known violations despite personal relationships",
      "source": "Code Section III.7",
      "enforcement_mechanism": "Professional ethics board",
      "temporal_scope": "Upon discovery of violations",
      "severity": "major",
      "case_context": "Engineer A's friendship with Engineer B does not override reporting obligations",
      "source_text": "their friendship was not an ethical justification for Engineer A to ignore or conceal Engineer B's violations",
      "is_existing_class": true,
      "confidence": 0.92
    },
    {
      "identifier": "AllEngineers_StateLicensureLaw",
      "constraint_class": "Legal Constraint",
      "constrained_entity": "All Engineers (A, B, C, R)",
      "constraint_statement": "Must conform with state licensure law requirements",
      "source": "State licensure law",
      "enforcement_mechanism": "State Board enforcement actions",
      "temporal_scope": "Continuous during practice",
      "severity": "critical",
      "case_context": "Multiple violations of state licensure law identified",
      "source_text": "Section III.8.a, engineers shall conform with state licensure law",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerR_DiscoveryReporting",
      "constraint_class": "Procedural Constraint",
      "constrained_entity": "Engineer R",
      "constraint_statement": "Must report discovered incompetent design work to State Board",
      "source": "Code Section II.1.f",
      "enforcement_mechanism": "Professional ethics enforcement",
      "temporal_scope": "Upon discovery of incompetent work",
      "severity": "major",
      "case_context": "Engineer R discovered incompetent nature of Engineer B's documents",
      "source_text": "Engineer R would be obligated to report Engineer B to the State Board (Section II.1.f)",
      "is_existing_class": true,
      "confidence": 0.87
    }
  ]
}
```
Capabilities Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for capabilities (competencies and skills required for professional practice). Based on the literature: - Capabilities are COMPETENCIES that enable norm compliance (Hallamaa & Kalliokoski 2022) - They represent the skills needed to fulfill professional obligations (Dennis et al. 2016) - Capabilities include technical, ethical, communicative, and analytical competencies - They constitute "norm competence" - the ability to act ethically (Kong et al. 2020) Your task is to: 1. Identify NEW CAPABILITY CLASSES not in the existing ontology 2. Extract SPECIFIC CAPABILITY INDIVIDUALS from the case EXISTING CAPABILITIES IN ONTOLOGY (check if your identified capabilities match these before creating new classes): - AI Tool Evaluation Capability: The competency to assess, validate, and appropriately use AI-generated content in professional work - Capability: A realizable entity that can be realized by specific types of actions or processes in professional contexts. This is the Ca component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Capability Type: Meta-class for specific capability types recognized by the ProEthica system - Data Privacy Protection Capability: The competency to safeguard confidential client information when using digital tools and platforms - Justification Capability: Capability to trace reasoning paths connecting decisions to authoritative sources (McLaren 2003, Anderson & Anderson 2018) - Regulatory Compliance Capability: The competency to ensure designs and documents meet local regulations and safety standards - Responsible Charge Capability: The competency to maintain active engagement and supervisory control from conception to completion of engineering work - Technical Capability: A specialized technical skill or competency in a professional domain - Technical Writing Capability: The competency to produce clear, accurate, and professional technical documentation and reports - Technology Integration Capability: The competency to appropriately integrate new technologies while maintaining professional judgment Analyze this discussion section: The primary issues of this case are the competency and professional actions of Engineer B, Engineer Intern C’s apparent complicity in the matter, the “compassion” of Engineer A and any subsequent actions by Engineer A, and the ethical obligations of Engineer R. The critical assessment of Engineer B’s competency and professional actions is overriding and will lead to other required determinations. The evaluation of this issue can be determined by separate facts. The facts are that Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal. While suffering a stroke by itself was not an ethical problem, the fact that Engineer B chose to sign and seal design drawings without proper review while impaired by this stroke was a problem. The BER has not previously examined competence as it relates to mental health; however, the facts in this case make the determination of [non]competence straightforward. Engineer B violated Section II. 2. of the code because he affixed his signature and seal to documents prepared without his direction or control. This also shows Engineer B was practicing in violation of the state licensure law (Section III.8.a). The Board further notes that Engineer B’s actions were in violation of NSPE’s Position Statement No. 10-1778: Responsible Charge which states: “The professional engineer in Responsible Charge is actively engaged in the engineering process, from conception to completion. Engineering decisions must be personally made by the professional engineer or by others over which the professional engineer provides supervisory direction and control authority. Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.” The actions of Engineer Intern C should be evaluated as well. Granted, Engineer Intern C is not yet a licensed professional engineer but an intern, and thus is working within the safety net of Engineer B’s guidance and direct supervision. While this might keep Engineer Intern C from legal censure per the State Engineering Practice Act, it does not absolve Engineer Intern C of ethical responsibility. The facts suggest Engineer Intern C, a subordinate of Engineer B, was fully aware of Engineer B’s impaired condition. Further, it appears Engineer Intern C cooperated with Engineer B in their arrangement to continue to deliver engineering design services as soon as it was realized Engineer B was unable to provide guidance, direct supervision or review. A similar ethical violation is discussed in BER Case 15-2 , in which an engineering report was revised after the report was signed and sealed inappropriately. The BER determined that the Engineer had an obligation to seek an immediate correction by contacting appropriate authorities, including the state engineering licensure board and other enforcement officials as appropriate. In summary, Engineer Intern C is ethically culpable through violation of Section II.1.e, Section II.1.f, and Section III.8.a of the Code of Ethics. What about Engineer A’s actions? Reference is made to Section I.1 of the Code, engineers shall hold paramount the safety, health, and welfare of the public and, more specifically, Section II.1.e, engineers shall not aid or abet the unlawful practice of engineering by a person or firm and Section II.1.f, engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required. The BER has almost always taken the position that whenever any violation of the Code or issues of public health, safety, and welfare are uncovered, the proper authorities should be notified. In BER Case 17-7 , the BER determined that an Engineer had an obligation to further report the situation to the appropriate the local, state, and/or federal authorities to ensure that relevant engineering standards were consistent with the public health, safety, and welfare. This was a case where a proposed change to an ordinance was contrary to established engineering standards. Even though Engineer A was a friend of Engineer B, their friendship was not an ethical justification for Engineer A to ignore or conceal Engineer B’s violations. Code Section III.7, engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action, unambiguously requires that such violations be reported to the appropriate professional body, in this case the State Board. This determination is also strengthened by Section III.8.a, engineers shall conform with state licensure law. That being said, the friendship between Engineer A and Engineer B warrants consideration. Hypothetically, what might an engineer do that would have been both ethical and would also have respected the friendship? Section III.7 of the Code says engineers “shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers.” By this view and with Engineer B’s knowledge and approval, Engineer A could have privately discussed the matter with proper authorities at the State Board. Working together, the parties might cooperatively identify a practice alternative consistent with ethical and legal engineering consulting work, say, hiring a qualified temporary engineer – possibly Engineer R – until Engineer B was able to return to full duty. Further, under such a scenario, the Board might exercise discretion relative to formal sanction (or not) of Engineer B. Other approaches are also possible. But any of them must begin with the conviction that the ethics code does not permit engineers to turn a blind eye to the unethical practice of engineering. Finally, what are Engineer R’s ethical obligations? The facts reveal it was Engineer R who technically uncovered the incompetent nature of Engineer B’s design and construction documents. Further, in the aftermath of Engineer R’s discovery, it is reasonable to think Engineer R was informed of Engineer B’s impairment due to a stroke, and also the series of actions by Engineer B and Engineer Intern C that followed. Since Engineer A was the person who got Engineer R involved in the first place, if Engineer A took the lead in reporting the matter, the report could be styled to note Engineer R’s concurrence. Otherwise, Engineer R would be obligated to report Engineer B to the State Board (Section II.1.f). Extract capabilities following this JSON structure: { "new_capability_classes": [ { "label": "Clear, specific capability class name", "definition": "What competency or skill this capability represents", "capability_type": "technical|ethical|communicative|analytical", "norm_competence_related": "Which professional obligations this capability enables", "skill_level": "basic|intermediate|advanced|expert", "acquisition_method": "How this capability is typically acquired (education, training, experience)", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this capability is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "capability_individuals": [ { "identifier": "Unique name for this specific capability instance", "capability_class": "Name of the capability class (new or existing)", "possessed_by": "Who has this capability (e.g., 'Engineer L', 'All Licensed PEs')", "capability_statement": "The specific competency (e.g., 'Design stormwater systems')", "demonstrated_through": "How shown in the case (e.g., 'Years of experience', 'Professional license')", "proficiency_level": "basic|intermediate|advanced|expert", "enables_obligations": "Which obligations this capability enables", "temporal_aspect": "When this capability is relevant", "case_context": "How this capability manifests in the specific case", "source_text": "EXACT text snippet from case where this capability is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW capability types that represent novel competencies 2. Specific capability instances showing professional competencies in this case 3. The relationship between capabilities and norm competence 4. How capabilities enable fulfillment of professional obligations Return ONLY the JSON structure, no additional text.
Saved: 2025-12-29 16:30
LLM Response
```json
{
  "new_capability_classes": [
    {
      "label": "Impairment Recognition Capability",
      "definition": "The competency to identify when oneself or colleagues are unable to perform professional duties due to physical or mental impairment",
      "capability_type": "ethical",
      "norm_competence_related": "Enables fulfillment of duty to protect public safety by recognizing when professional judgment is compromised",
      "skill_level": "intermediate",
      "acquisition_method": "Professional experience, ethics training, mentorship",
      "examples_from_case": ["Recognizing stroke-related impairment", "Identifying inability to review designs"],
      "source_text": "Engineer B suffered a stroke and was unable to adequately direct and review engineering designs and drawings being prepared under his signature and seal",
      "confidence": 0.9,
      "reasoning": "Not covered by existing capabilities - specific to recognizing professional impairment affecting competence"
    },
    {
      "label": "Ethical Reporting Capability",
      "definition": "The competency to properly report ethical violations to appropriate authorities while maintaining professional relationships",
      "capability_type": "ethical",
      "norm_competence_related": "Enables compliance with obligation to report violations while respecting professional dignity",
      "skill_level": "advanced",
      "acquisition_method": "Ethics training, professional development, case study analysis",
      "examples_from_case": ["Reporting to State Board", "Balancing friendship with ethical duty"],
      "source_text": "engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies",
      "confidence": 0.85,
      "reasoning": "Distinct from general compliance - focuses on the specific skill of ethical reporting and whistleblowing"
    },
    {
      "label": "Subordinate Ethics Capability",
      "definition": "The competency of junior professionals to recognize and respond to ethical violations by supervisors despite power imbalance",
      "capability_type": "ethical",
      "norm_competence_related": "Enables junior professionals to uphold ethical standards even when working under supervision",
      "skill_level": "intermediate",
      "acquisition_method": "Ethics education, internship supervision, professional mentoring",
      "examples_from_case": ["Engineer Intern C's situation", "Working under impaired supervisor"],
      "source_text": "Engineer Intern C, a subordinate of Engineer B, was fully aware of Engineer B's impaired condition",
      "confidence": 0.8,
      "reasoning": "Addresses unique ethical challenges faced by subordinates/interns not covered by existing capabilities"
    }
  ],
  "capability_individuals": [
    {
      "identifier": "EngineerB_ResponsibleCharge_Deficient",
      "capability_class": "Responsible Charge Capability",
      "possessed_by": "Engineer B",
      "capability_statement": "Failed to maintain active engagement and supervisory control due to stroke impairment",
      "demonstrated_through": "Inability to review designs while signing and sealing them",
      "proficiency_level": "basic",
      "enables_obligations": "Failed to enable proper supervision and control of engineering work",
      "temporal_aspect": "Post-stroke period",
      "case_context": "Engineer B violated responsible charge by signing documents without proper review",
      "source_text": "Engineer B chose to sign and seal design drawings without proper review while impaired by this stroke",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerR_TechnicalReview",
      "capability_class": "Technical Capability",
      "possessed_by": "Engineer R",
      "capability_statement": "Ability to identify incompetent design and construction documents",
      "demonstrated_through": "Technical review that uncovered deficiencies",
      "proficiency_level": "expert",
      "enables_obligations": "Enables proper technical review and quality assurance",
      "temporal_aspect": "During document review",
      "case_context": "Engineer R discovered the incompetent nature of Engineer B's documents",
      "source_text": "Engineer R who technically uncovered the incompetent nature of Engineer B's design and construction documents",
      "is_existing_class": true,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerA_EthicalReporting_Required",
      "capability_class": "Ethical Reporting Capability",
      "possessed_by": "Engineer A",
      "capability_statement": "Obligation to report known violations to State Board despite friendship",
      "demonstrated_through": "Knowledge of violations requiring action",
      "proficiency_level": "intermediate",
      "enables_obligations": "Enables compliance with reporting requirements in Code Section III.7",
      "temporal_aspect": "Upon discovery of violations",
      "case_context": "Engineer A must balance friendship with reporting obligations",
      "source_text": "Engineer A could have privately discussed the matter with proper authorities at the State Board",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerInternC_SubordinateEthics_Failed",
      "capability_class": "Subordinate Ethics Capability",
      "possessed_by": "Engineer Intern C",
      "capability_statement": "Failed to respond appropriately to supervisor's impairment despite awareness",
      "demonstrated_through": "Continued cooperation with impaired supervisor",
      "proficiency_level": "basic",
      "enables_obligations": "Failed to uphold ethical standards despite subordinate position",
      "temporal_aspect": "During Engineer B's impairment",
      "case_context": "Intern C cooperated with impaired Engineer B instead of reporting",
      "source_text": "Engineer Intern C cooperated with Engineer B in their arrangement to continue to deliver engineering design services",
      "is_existing_class": false,
      "confidence": 0.8
    },
    {
      "identifier": "EngineerB_ImpairmentRecognition_Absent",
      "capability_class": "Impairment Recognition Capability",
      "possessed_by": "Engineer B",
      "capability_statement": "Failed to recognize own inability to perform professional duties post-stroke",
      "demonstrated_through": "Continued signing and sealing despite impairment",
      "proficiency_level": "basic",
      "enables_obligations": "Failed to enable self-assessment of fitness for practice",
      "temporal_aspect": "Post-stroke period",
      "case_context": "Engineer B did not recognize or act on own impairment",
      "source_text": "Engineer B suffered a stroke and was unable to adequately direct and review engineering designs",
      "is_existing_class": false,
      "confidence": 0.9
    }
  ]
}
```