Step 2: Normative Requirements Pass (Discussion Section)

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

Competence in Design Services
Step 2 of 5

Discussion Section

Section Content:
Discussion:
The Code of Ethics specifically states Engineers shall not affix their signature to any plans dealing with subject matter in which they lack competence.
The Board of Ethical Review has reviewed this requirement in past cases.
In BER Case 02-5 , the Board studied a situation in which a structural engineer, competent in severe weather structural engineering, designed a building that had a structural failure from a severe weather condition.
This failure could have been avoided if the engineer had incorporated design parameters suggested in recent technical literature with which the engineer was not familiar.
The Board concluded that it was not unethical for the engineer to fail to follow the most recent design parameters for structural design in severe weather areas published in the most recent technical literature, because those recently proposed design parameters had not yet become standards.
In Case 02-5 , the engineer was considered competent in all other respects, it was just that the engineer was not familiar with the recently proposed design parameters.
In the present case, the question is whether Engineer B is competent.
In BER Case 98-8 , a professional engineer in civil engineering was asked to certify certain arms storage rooms and racks for the Army.
This engineer had no significant training or knowledge in that area, although the engineer was considered a qualified engineer.
The Board concluded that, because the engineer lacked competence in the specific area, it would not be ethical for the engineer to certify the arms storage rooms and arms storage racks.
That case is analogous to the present case.
In both instances, while competent in some areas, the engineer in question may not have been competent in the specific areas of practice in question, in which case, the engineer acted unethically.
BER Case 94-8 provided an extreme example of incompetence.
In that case, a professional engineer with a degree and background in chemical engineering was asked to provide a foundation design for an industrial facility.
The Board determined that it would be unethical for the engineer to perform the design of the structural footings as part of the facility.
The Code of Ethics provides guidance when evaluating competence.
II.2.a. states that “Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.” However, does education or experience alone provide one with competence?
Education provides scientific and technical knowledge which are a necessary foundation for professional competence, but it is also the experiences of working within the technical fields that build competence.
II.2.a., alone does not settle the ethical questions of this case since it allows for the undertaking of assignments when engineers are qualified by education “or” experience.
II.2.b. indicates further that Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence.
In this case, it is clear that Engineer B, as a water and wastewater engineer without identified significant roadway design skills, did not possess the competence to perform the rural highway design services.
The problems that occurred during construction would have been avoided if the design met standards.
Finally, I.6 indicates that engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession.
Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence.
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 Code of Ethics specifically states Engineers shall not affix their signature to any plans dealing with subject matter in which they lack competence. The Board of Ethical Review has reviewed this requirement in past cases. In BER Case 02-5 , the Board studied a situation in which a structural engineer, competent in severe weather structural engineering, designed a building that had a structural failure from a severe weather condition. This failure could have been avoided if the engineer had incorporated design parameters suggested in recent technical literature with which the engineer was not familiar. The Board concluded that it was not unethical for the engineer to fail to follow the most recent design parameters for structural design in severe weather areas published in the most recent technical literature, because those recently proposed design parameters had not yet become standards. In Case 02-5 , the engineer was considered competent in all other respects, it was just that the engineer was not familiar with the recently proposed design parameters. In the present case, the question is whether Engineer B is competent. In BER Case 98-8 , a professional engineer in civil engineering was asked to certify certain arms storage rooms and racks for the Army. This engineer had no significant training or knowledge in that area, although the engineer was considered a qualified engineer. The Board concluded that, because the engineer lacked competence in the specific area, it would not be ethical for the engineer to certify the arms storage rooms and arms storage racks. That case is analogous to the present case. In both instances, while competent in some areas, the engineer in question may not have been competent in the specific areas of practice in question, in which case, the engineer acted unethically. BER Case 94-8 provided an extreme example of incompetence. In that case, a professional engineer with a degree and background in chemical engineering was asked to provide a foundation design for an industrial facility. The Board determined that it would be unethical for the engineer to perform the design of the structural footings as part of the facility. The Code of Ethics provides guidance when evaluating competence. II.2.a. states that “Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.” However, does education or experience alone provide one with competence? Education provides scientific and technical knowledge which are a necessary foundation for professional competence, but it is also the experiences of working within the technical fields that build competence. II.2.a., alone does not settle the ethical questions of this case since it allows for the undertaking of assignments when engineers are qualified by education “or” experience.  II.2.b. indicates further that Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence. In this case, it is clear that Engineer B, as a water and wastewater engineer without identified significant roadway design skills, did not possess the competence to perform the rural highway design services. The problems that occurred during construction would have been avoided if the design met standards. Finally, I.6 indicates that engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession. Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence. 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-20 17:34
LLM Response
```json
{
    "new_principle_classes": [
        {
            "label": "Professional Honor Principle",
            "definition": "Principle that professional conduct must enhance the honor, reputation, and usefulness of the engineering profession as a whole",
            "abstract_nature": "Collective professional integrity and social trust",
            "extensional_examples": ["Declining work outside competence", "Maintaining high standards", "Transparent professional limitations"],
            "value_basis": "Preservation of public trust in the profession",
            "application_context": ["Contract bidding", "Professional representation", "Public-facing engineering work"],
            "operationalization": "Through competent practice, honest representation of capabilities, and maintaining professional standards",
            "balancing_requirements": ["Economic opportunities", "Client demands", "Competitive pressures"],
            "examples_from_case": ["Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence"],
            "source_text": "engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession"
        }
    ],
    "principle_individuals": [
        {
            "identifier": "Competence_SignaturePlans_Discussion",
            "principle_class": "Competence Principle",
            "concrete_expression": "Engineers shall not affix their signature to any plans dealing with subject matter in which they lack competence",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineer B's rural highway design"],
            "interpretation": "Competence required before certifying any engineering plans",
            "source_text": "Engineers shall not affix their signature to any plans dealing with subject matter in which they lack competence",
            "balancing_with": [],
            "tension_resolution": "Absolute requirement - no balancing permitted",
            "case_relevance": "Central to determining whether Engineer B acted ethically"
        },
        {
            "identifier": "Competence_EducationExperience_Discussion",
            "principle_class": "Competence Principle",
            "concrete_expression": "Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved",
            "invoked_by": ["Code of Ethics"],
            "applied_to": ["Engineer B's qualifications for highway design"],
            "interpretation": "Either education OR experience can establish competence, but must be in specific technical field",
            "source_text": "Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved",
            "balancing_with": [],
            "tension_resolution": "Education alone insufficient without relevant experience",
            "case_relevance": "Helps evaluate whether Engineer B had requisite competence"
        },
        {
            "identifier": "ProfessionalHonor_EngineerB_Discussion",
            "principle_class": "Professional Honor Principle",
            "concrete_expression": "engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession",
            "invoked_by": ["Code of Ethics I.6"],
            "applied_to": ["Engineer B's bidding and accepting contract"],
            "interpretation": "Taking on incompetent work damages profession's reputation",
            "source_text": "engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession. Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence",
            "balancing_with": ["Economic opportunity", "Business development"],
            "tension_resolution": "Professional reputation takes precedence over business opportunities",
            "case_relevance": "Additional ethical violation beyond competence requirements"
        },
        {
            "identifier": "Competence_NoSignature_Discussion",
            "principle_class": "Competence Principle",
            "concrete_expression": "Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence",
            "invoked_by": ["Code of Ethics II.2.b"],
            "applied_to": ["Engineer B's highway design certification"],
            "interpretation": "Water/wastewater engineer lacks competence for rural highway design",
            "source_text": "Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence. In this case, it is clear that Engineer B, as a water and wastewater engineer without identified significant roadway design skills, did not possess the competence to perform the rural highway design services",
            "balancing_with": [],
            "tension_resolution": "No exceptions - competence is prerequisite for certification",
            "case_relevance": "Direct application showing Engineer B violated this principle"
        }
    ]
}
```
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 Code of Ethics specifically states Engineers shall not affix their signature to any plans dealing with subject matter in which they lack competence. The Board of Ethical Review has reviewed this requirement in past cases. In BER Case 02-5 , the Board studied a situation in which a structural engineer, competent in severe weather structural engineering, designed a building that had a structural failure from a severe weather condition. This failure could have been avoided if the engineer had incorporated design parameters suggested in recent technical literature with which the engineer was not familiar. The Board concluded that it was not unethical for the engineer to fail to follow the most recent design parameters for structural design in severe weather areas published in the most recent technical literature, because those recently proposed design parameters had not yet become standards. In Case 02-5 , the engineer was considered competent in all other respects, it was just that the engineer was not familiar with the recently proposed design parameters. In the present case, the question is whether Engineer B is competent. In BER Case 98-8 , a professional engineer in civil engineering was asked to certify certain arms storage rooms and racks for the Army. This engineer had no significant training or knowledge in that area, although the engineer was considered a qualified engineer. The Board concluded that, because the engineer lacked competence in the specific area, it would not be ethical for the engineer to certify the arms storage rooms and arms storage racks. That case is analogous to the present case. In both instances, while competent in some areas, the engineer in question may not have been competent in the specific areas of practice in question, in which case, the engineer acted unethically. BER Case 94-8 provided an extreme example of incompetence. In that case, a professional engineer with a degree and background in chemical engineering was asked to provide a foundation design for an industrial facility. The Board determined that it would be unethical for the engineer to perform the design of the structural footings as part of the facility. The Code of Ethics provides guidance when evaluating competence. II.2.a. states that “Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.” However, does education or experience alone provide one with competence? Education provides scientific and technical knowledge which are a necessary foundation for professional competence, but it is also the experiences of working within the technical fields that build competence. II.2.a., alone does not settle the ethical questions of this case since it allows for the undertaking of assignments when engineers are qualified by education “or” experience.  II.2.b. indicates further that Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence. In this case, it is clear that Engineer B, as a water and wastewater engineer without identified significant roadway design skills, did not possess the competence to perform the rural highway design services. The problems that occurred during construction would have been avoided if the design met standards. Finally, I.6 indicates that engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession. Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence. 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-20 17:34
LLM Response
```json
{
  "new_obligation_classes": [
    {
      "label": "Signature Authority Obligation",
      "definition": "The duty to affix one's professional signature only to plans, documents, or certifications dealing with subject matter in which the professional possesses demonstrated competence",
      "derived_from_principle": "Professional Integrity",
      "duty_type": "professional",
      "enforcement_mechanism": "Board of Ethical Review sanctions, license suspension or revocation",
      "violation_consequences": "Ethical violations, potential liability for failures, damage to professional reputation",
      "examples_from_case": ["Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence", "certify certain arms storage rooms and racks"],
      "source_text": "Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence",
      "confidence": 0.85,
      "reasoning": "While related to competence, this specifically addresses the act of signing/certifying documents, which carries distinct legal and professional weight beyond general competence requirements"
    },
    {
      "label": "Professional Reputation Obligation",
      "definition": "The duty to conduct oneself in ways that enhance the honor, reputation, and usefulness of the profession as a whole",
      "derived_from_principle": "Professional Honor",
      "duty_type": "professional",
      "enforcement_mechanism": "Professional association sanctions, peer review, public trust mechanisms",
      "violation_consequences": "Damage to profession's reputation, loss of public trust, disciplinary action",
      "examples_from_case": ["engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession"],
      "source_text": "engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession",
      "confidence": 0.9,
      "reasoning": "This represents a distinct duty to the profession itself, beyond individual competence or safety obligations - it's about maintaining professional standing"
    }
  ],
  "obligation_individuals": [
    {
      "identifier": "EngineerB_Competence_RoadwayDesign",
      "obligation_class": "Competence Obligation",
      "obligated_party": "Engineer B",
      "obligation_statement": "Must not perform rural highway design services without adequate roadway design competence",
      "derived_from": "NSPE Code II.2.a",
      "enforcement_context": "Board of Ethical Review determination",
      "temporal_scope": "At time of bidding and accepting contract",
      "compliance_status": "unmet",
      "case_context": "Engineer B, a water and wastewater engineer, accepted rural highway design work outside competence area",
      "source_text": "Engineer B, as a water and wastewater engineer without identified significant roadway design skills, did not possess the competence",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerB_Signature_HighwayPlans",
      "obligation_class": "Signature Authority Obligation",
      "obligated_party": "Engineer B",
      "obligation_statement": "Must not affix signature to highway design plans lacking competence in roadway design",
      "derived_from": "NSPE Code II.2.b",
      "enforcement_context": "Board of Ethical Review sanctions",
      "temporal_scope": "When signing design documents",
      "compliance_status": "unmet",
      "case_context": "Engineer B signed highway design plans despite lacking roadway design competence",
      "source_text": "Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerB_ProfessionalReputation",
      "obligation_class": "Professional Reputation Obligation",
      "obligated_party": "Engineer B",
      "obligation_statement": "Must conduct practice to enhance honor and reputation of engineering profession",
      "derived_from": "NSPE Code I.6",
      "enforcement_context": "Professional ethics review",
      "temporal_scope": "Throughout professional practice",
      "compliance_status": "unmet",
      "case_context": "Engineer B damaged profession's reputation by accepting incompetent work",
      "source_text": "Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "Case98-8_Engineer_Certification",
      "obligation_class": "Competence Obligation",
      "obligated_party": "Professional engineer in Case 98-8",
      "obligation_statement": "Must not certify arms storage rooms and racks without specific training or knowledge in that area",
      "derived_from": "NSPE Code II.2",
      "enforcement_context": "Board determination of unethical conduct",
      "temporal_scope": "When asked to certify",
      "compliance_status": "unmet",
      "case_context": "Civil engineer asked to certify military storage facilities outside competence",
      "source_text": "it would not be ethical for the engineer to certify the arms storage rooms and arms storage racks",
      "is_existing_class": true,
      "confidence": 0.9
    },
    {
      "identifier": "Case94-8_ChemicalEngineer_StructuralDesign",
      "obligation_class": "Competence Obligation",
      "obligated_party": "Chemical engineer in Case 94-8",
      "obligation_statement": "Must not perform structural footing design without structural engineering competence",
      "derived_from": "NSPE Code II.2",
      "enforcement_context": "Board ethical review",
      "temporal_scope": "When asked to provide foundation design",
      "compliance_status": "unmet",
      "case_context": "Chemical engineer asked to design structural footings for industrial facility",
      "source_text": "it would be unethical for the engineer to perform the design of the structural footings",
      "is_existing_class": true,
      "confidence": 0.95
    }
  ]
}
```
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 Code of Ethics specifically states Engineers shall not affix their signature to any plans dealing with subject matter in which they lack competence. The Board of Ethical Review has reviewed this requirement in past cases. In BER Case 02-5 , the Board studied a situation in which a structural engineer, competent in severe weather structural engineering, designed a building that had a structural failure from a severe weather condition. This failure could have been avoided if the engineer had incorporated design parameters suggested in recent technical literature with which the engineer was not familiar. The Board concluded that it was not unethical for the engineer to fail to follow the most recent design parameters for structural design in severe weather areas published in the most recent technical literature, because those recently proposed design parameters had not yet become standards. In Case 02-5 , the engineer was considered competent in all other respects, it was just that the engineer was not familiar with the recently proposed design parameters. In the present case, the question is whether Engineer B is competent. In BER Case 98-8 , a professional engineer in civil engineering was asked to certify certain arms storage rooms and racks for the Army. This engineer had no significant training or knowledge in that area, although the engineer was considered a qualified engineer. The Board concluded that, because the engineer lacked competence in the specific area, it would not be ethical for the engineer to certify the arms storage rooms and arms storage racks. That case is analogous to the present case. In both instances, while competent in some areas, the engineer in question may not have been competent in the specific areas of practice in question, in which case, the engineer acted unethically. BER Case 94-8 provided an extreme example of incompetence. In that case, a professional engineer with a degree and background in chemical engineering was asked to provide a foundation design for an industrial facility. The Board determined that it would be unethical for the engineer to perform the design of the structural footings as part of the facility. The Code of Ethics provides guidance when evaluating competence. II.2.a. states that “Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.” However, does education or experience alone provide one with competence? Education provides scientific and technical knowledge which are a necessary foundation for professional competence, but it is also the experiences of working within the technical fields that build competence. II.2.a., alone does not settle the ethical questions of this case since it allows for the undertaking of assignments when engineers are qualified by education “or” experience.  II.2.b. indicates further that Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence. In this case, it is clear that Engineer B, as a water and wastewater engineer without identified significant roadway design skills, did not possess the competence to perform the rural highway design services. The problems that occurred during construction would have been avoided if the design met standards. Finally, I.6 indicates that engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession. Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence. 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-20 17:35
LLM Response
```json
{
  "new_constraint_classes": [
    {
      "label": "Signature Authority Constraint",
      "definition": "Limitations on an engineer's authority to sign, certify, or approve documents based on their competence in the subject matter",
      "constraint_type": "legal",
      "flexibility": "hard",
      "violation_impact": "Invalid certification, potential legal liability, professional misconduct charges",
      "mitigation_possible": "Can be mitigated by obtaining additional qualifications or partnering with competent professionals",
      "examples_from_case": ["Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence"],
      "source_text": "Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence",
      "confidence": 0.85,
      "reasoning": "While related to competence constraints, this specifically addresses the boundary on signature/certification authority, which is a distinct legal limitation not captured in existing classes"
    },
    {
      "label": "Standards Adoption Constraint",
      "definition": "Boundaries on professional liability when new technical standards or parameters have not yet been formally adopted by the profession",
      "constraint_type": "procedural",
      "flexibility": "soft",
      "violation_impact": "May result in suboptimal design but not necessarily unethical conduct if standards are not yet adopted",
      "mitigation_possible": "Engineers can choose to adopt emerging best practices even before formal standardization",
      "examples_from_case": ["Recently proposed design parameters that had not yet become standards"],
      "source_text": "recently proposed design parameters had not yet become standards",
      "confidence": 0.75,
      "reasoning": "Represents a temporal boundary between proposed and adopted standards that limits liability - distinct from procedural or regulatory constraints"
    }
  ],
  "constraint_individuals": [
    {
      "identifier": "Engineer_B_Signature_Constraint",
      "constraint_class": "Signature Authority Constraint",
      "constrained_entity": "Engineer B",
      "constraint_statement": "Cannot affix signature to rural highway design plans due to lack of competence in roadway design",
      "source": "Code of Ethics II.2.b",
      "enforcement_mechanism": "Board of Ethical Review enforcement, potential license suspension",
      "temporal_scope": "Permanent unless additional qualifications obtained",
      "severity": "critical",
      "case_context": "Engineer B, as water/wastewater engineer, signed highway design documents outside competence area",
      "source_text": "Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence",
      "is_existing_class": false,
      "confidence": 0.95
    },
    {
      "identifier": "Engineer_B_Competence_Boundary",
      "constraint_class": "Competence Constraint",
      "constrained_entity": "Engineer B",
      "constraint_statement": "Limited to water and wastewater engineering work only",
      "source": "Professional background and training",
      "enforcement_mechanism": "Professional standards enforcement",
      "temporal_scope": "Current professional status",
      "severity": "critical",
      "case_context": "Engineer B's competence limited to water/wastewater, excluding rural highway design",
      "source_text": "Engineer B, as a water and wastewater engineer without identified significant roadway design skills",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "Assignment_Acceptance_Constraint",
      "constraint_class": "Ethical Constraint",
      "constrained_entity": "Engineer B",
      "constraint_statement": "Cannot undertake assignments outside education or experience qualifications",
      "source": "Code of Ethics II.2.a",
      "enforcement_mechanism": "Professional ethics review",
      "temporal_scope": "All professional engagements",
      "severity": "critical",
      "case_context": "Engineer B violated by accepting rural highway design contract",
      "source_text": "Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved",
      "is_existing_class": true,
      "confidence": 0.90
    },
    {
      "identifier": "Recent_Literature_Standards_Boundary",
      "constraint_class": "Standards Adoption Constraint",
      "constrained_entity": "Structural engineer in Case 02-5",
      "constraint_statement": "Not required to follow design parameters not yet adopted as standards",
      "source": "Professional standards adoption process",
      "enforcement_mechanism": "Board determination of ethical standards",
      "temporal_scope": "Until formal adoption of standards",
      "severity": "minor",
      "case_context": "Engineer not found unethical for not following unadopted parameters",
      "source_text": "recently proposed design parameters had not yet become standards",
      "is_existing_class": false,
      "confidence": 0.80
    },
    {
      "identifier": "Professional_Reputation_Constraint",
      "constraint_class": "Ethical Constraint",
      "constrained_entity": "Engineer B",
      "constraint_statement": "Must not engage in conduct that damages profession's honor and reputation",
      "source": "Code of Ethics I.6",
      "enforcement_mechanism": "Professional conduct review",
      "temporal_scope": "All professional activities",
      "severity": "major",
      "case_context": "Violated by accepting incompetent work that resulted in construction problems",
      "source_text": "engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession",
      "is_existing_class": true,
      "confidence": 0.85
    }
  ]
}
```
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 Code of Ethics specifically states Engineers shall not affix their signature to any plans dealing with subject matter in which they lack competence. The Board of Ethical Review has reviewed this requirement in past cases. In BER Case 02-5 , the Board studied a situation in which a structural engineer, competent in severe weather structural engineering, designed a building that had a structural failure from a severe weather condition. This failure could have been avoided if the engineer had incorporated design parameters suggested in recent technical literature with which the engineer was not familiar. The Board concluded that it was not unethical for the engineer to fail to follow the most recent design parameters for structural design in severe weather areas published in the most recent technical literature, because those recently proposed design parameters had not yet become standards. In Case 02-5 , the engineer was considered competent in all other respects, it was just that the engineer was not familiar with the recently proposed design parameters. In the present case, the question is whether Engineer B is competent. In BER Case 98-8 , a professional engineer in civil engineering was asked to certify certain arms storage rooms and racks for the Army. This engineer had no significant training or knowledge in that area, although the engineer was considered a qualified engineer. The Board concluded that, because the engineer lacked competence in the specific area, it would not be ethical for the engineer to certify the arms storage rooms and arms storage racks. That case is analogous to the present case. In both instances, while competent in some areas, the engineer in question may not have been competent in the specific areas of practice in question, in which case, the engineer acted unethically. BER Case 94-8 provided an extreme example of incompetence. In that case, a professional engineer with a degree and background in chemical engineering was asked to provide a foundation design for an industrial facility. The Board determined that it would be unethical for the engineer to perform the design of the structural footings as part of the facility. The Code of Ethics provides guidance when evaluating competence. II.2.a. states that “Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.” However, does education or experience alone provide one with competence? Education provides scientific and technical knowledge which are a necessary foundation for professional competence, but it is also the experiences of working within the technical fields that build competence. II.2.a., alone does not settle the ethical questions of this case since it allows for the undertaking of assignments when engineers are qualified by education “or” experience.  II.2.b. indicates further that Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence. In this case, it is clear that Engineer B, as a water and wastewater engineer without identified significant roadway design skills, did not possess the competence to perform the rural highway design services. The problems that occurred during construction would have been avoided if the design met standards. Finally, I.6 indicates that engineers shall conduct themselves in a way so to enhance the honor, reputation, and usefulness of the profession. Engineer B did not meet this standard when bidding and accepting a contract involving work for which the firm did not have adequate competence. 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-20 17:35
LLM Response
```json
{
  "new_capability_classes": [
    {
      "label": "Domain-Specific Competence Assessment Capability",
      "definition": "The competency to accurately evaluate one's own or others' qualifications and expertise boundaries in specific technical domains before undertaking professional assignments",
      "capability_type": "ethical",
      "norm_competence_related": "Enables compliance with the obligation to only undertake work within one's competence",
      "skill_level": "advanced",
      "acquisition_method": "Developed through professional experience, self-reflection, and understanding of technical domain boundaries",
      "examples_from_case": ["Recognizing lack of roadway design skills", "Determining competence in specific vs general engineering areas"],
      "source_text": "Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved",
      "confidence": 0.85,
      "reasoning": "Differs from general Technical Capability by focusing on the meta-skill of recognizing competence boundaries rather than the technical skills themselves"
    },
    {
      "label": "Standards Currency Maintenance Capability",
      "definition": "The competency to stay current with evolving technical standards, recent literature, and emerging best practices in one's field of practice",
      "capability_type": "technical",
      "norm_competence_related": "Enables meeting professional obligations to maintain current knowledge and avoid preventable failures",
      "skill_level": "intermediate",
      "acquisition_method": "Continuous professional development, reading technical literature, attending conferences, professional training",
      "examples_from_case": ["Keeping up with recent technical literature", "Incorporating new design parameters"],
      "source_text": "recently proposed design parameters had not yet become standards",
      "confidence": 0.75,
      "reasoning": "Goes beyond basic Technical Capability to specifically address maintaining currency with evolving standards and literature"
    }
  ],
  "capability_individuals": [
    {
      "identifier": "EngineerB_WaterWastewaterCapability",
      "capability_class": "Technical Capability",
      "possessed_by": "Engineer B",
      "capability_statement": "Design and manage water and wastewater engineering projects",
      "demonstrated_through": "Professional designation as water and wastewater engineer",
      "proficiency_level": "expert",
      "enables_obligations": "Competent practice in water/wastewater domain",
      "temporal_aspect": "Throughout career",
      "case_context": "Engineer B's established area of expertise",
      "source_text": "Engineer B, as a water and wastewater engineer",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerB_LackingRoadwayDesignCapability",
      "capability_class": "Technical Capability",
      "possessed_by": "Engineer B",
      "capability_statement": "Design rural highways and roadways",
      "demonstrated_through": "Absence of roadway design skills or experience",
      "proficiency_level": "basic",
      "enables_obligations": "Cannot fulfill obligations for roadway design",
      "temporal_aspect": "At time of accepting contract",
      "case_context": "Lack of capability led to construction problems",
      "source_text": "without identified significant roadway design skills, did not possess the competence",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "StructuralEngineer_SevereWeatherCapability",
      "capability_class": "Technical Capability",
      "possessed_by": "Structural engineer from Case 02-5",
      "capability_statement": "Design structures for severe weather conditions",
      "demonstrated_through": "Professional practice and experience",
      "proficiency_level": "advanced",
      "enables_obligations": "Competent structural design in severe weather areas",
      "temporal_aspect": "At time of Case 02-5",
      "case_context": "Competent despite not knowing latest proposed parameters",
      "source_text": "structural engineer, competent in severe weather structural engineering",
      "is_existing_class": true,
      "confidence": 0.90
    },
    {
      "identifier": "ChemicalEngineer_LackingStructuralCapability",
      "capability_class": "Technical Capability",
      "possessed_by": "Chemical engineer from Case 94-8",
      "capability_statement": "Design structural footings and foundations",
      "demonstrated_through": "Lack of relevant education or experience",
      "proficiency_level": "basic",
      "enables_obligations": "Cannot fulfill structural design obligations",
      "temporal_aspect": "At time of Case 94-8",
      "case_context": "Extreme example of incompetence outside domain",
      "source_text": "professional engineer with a degree and background in chemical engineering",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerB_CompetenceAssessmentDeficiency",
      "capability_class": "Domain-Specific Competence Assessment Capability",
      "possessed_by": "Engineer B",
      "capability_statement": "Assess own competence boundaries before accepting contracts",
      "demonstrated_through": "Failed to recognize incompetence in roadway design",
      "proficiency_level": "basic",
      "enables_obligations": "Failed to meet obligation to undertake only qualified work",
      "temporal_aspect": "When bidding and accepting contract",
      "case_context": "Accepted work outside competence area",
      "source_text": "bidding and accepting a contract involving work for which the firm did not have adequate competence",
      "is_existing_class": false,
      "confidence": 0.85
    }
  ]
}
```