Step 2: Normative Requirements Pass (Facts Section)
Extract principles, obligations, constraints, and capabilities from the facts section
Impaired Engineering
Step 2 of 5
Facts Section
Section Content:
Facts: Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development. Business has been very successful, so much so that Engineer A has taken steps to expand the business. Among other things, Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design. Construction drawings were completed, permits were issued, a contract was let, and the contractor began construction of the new office building – which included a basement. However, early during the process of constructing the basement there was a significant structural failure. While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details. To obtain a second opinion about the failure, Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure. Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet. Engineer A retained Engineer R to completely redesign the structure. As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report. At this meeting, Engineer B divulged he had suffered a stroke a few months prior. Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office. Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience. The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review. Ultimately, this process led to the failure of Engineer A’s building. Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board.
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 (facts 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:
Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development. Business has been very successful, so much so that Engineer A has taken steps to expand the business. Among other things, Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design.
Construction drawings were completed, permits were issued, a contract was let, and the contractor began construction of the new office building – which included a basement. However, early during the process of constructing the basement there was a significant structural failure. While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details. To obtain a second opinion about the failure, Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure.
Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet. Engineer A retained Engineer R to completely redesign the structure.
As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report. At this meeting, Engineer B divulged he had suffered a stroke a few months prior. Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office. Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience. The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review. Ultimately, this process led to the failure of Engineer A’s building.
Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board.
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:26
LLM Response
```json
{
"new_principle_classes": [
{
"label": "Professional Compassion",
"definition": "Principle that professional obligations must be balanced with humane consideration of personal circumstances and relationships",
"abstract_nature": "Mercy, empathy, and human dignity in professional contexts",
"extensional_examples": ["Considering health impairments in reporting decisions", "Balancing friendship with professional duties", "Weighing personal hardship against public safety"],
"value_basis": "Human dignity and compassionate response to suffering",
"application_context": ["Professional misconduct reporting", "Colleague relationships", "Enforcement decisions"],
"operationalization": "Through private confrontation before formal reporting, consideration of mitigating circumstances, seeking remedial rather than punitive solutions",
"balancing_requirements": ["Public safety obligations", "Professional integrity standards", "Legal reporting requirements"],
"examples_from_case": ["Because of their long friendship and consideration of Engineer B's impairment", "As a professional courtesy, and because he considered Engineer B a personal friend"],
"source_text": "Because of their long friendship and consideration of Engineer B's impairment, Engineer A did not report Engineer B to the State Board"
},
{
"label": "Professional Self-Limitation",
"definition": "Principle requiring professionals to recognize and respond appropriately to their own limitations, whether temporary or permanent",
"abstract_nature": "Self-awareness, humility, and responsible practice boundaries",
"extensional_examples": ["Suspending practice during illness", "Seeking supervision when impaired", "Closing practice if unable to meet standards"],
"value_basis": "Professional responsibility and public trust",
"application_context": ["Health impairments", "Competence limitations", "Capacity constraints"],
"operationalization": "Through practice suspension, increased supervision, delegation with proper oversight, or practice closure",
"balancing_requirements": ["Financial pressures", "Client needs", "Business continuity"],
"examples_from_case": ["Engineer B felt he could not afford to suspend work or close his office", "Engineer B had suffered a stroke"],
"source_text": "Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office"
}
],
"principle_individuals": [
{
"identifier": "PublicSafety_StructuralFailure_Facts",
"principle_class": "Public Welfare Principle",
"concrete_expression": "significant structural failure... serious structural design errors, omissions, and faulty details",
"invoked_by": ["Implicit in case narrative"],
"applied_to": ["Structural design and construction of office building"],
"interpretation": "Public safety was compromised by faulty structural design leading to actual failure",
"source_text": "Engineer R's review revealed a surprising number of serious structural design errors, omissions, and faulty details",
"balancing_with": ["Financial pressures", "Business continuity"],
"tension_resolution": "Safety failures occurred when financial pressures overrode proper engineering oversight",
"case_relevance": "Central to understanding the severity of Engineer B's professional breach"
},
{
"identifier": "Competence_EngineerB_Impairment",
"principle_class": "Competence Principle",
"concrete_expression": "Engineer B had suffered a stroke... delegated practically all design work to Engineer Intern C",
"invoked_by": ["Engineer B (violated)"],
"applied_to": ["Continued practice despite impairment"],
"interpretation": "Competence principle violated by continuing to seal drawings without proper review while impaired",
"source_text": "Engineer B would sign and seal the drawings with little to no review",
"balancing_with": ["Financial needs", "Business obligations"],
"tension_resolution": "Financial pressures led to violation of competence requirements",
"case_relevance": "Demonstrates failure to recognize and respond to professional limitations"
},
{
"identifier": "ProfessionalIntegrity_EngineerA_Reporting",
"principle_class": "Integrity Principle",
"concrete_expression": "Engineer A did not report Engineer B to the State Board",
"invoked_by": ["Engineer A (compromised)"],
"applied_to": ["Decision whether to report professional misconduct"],
"interpretation": "Integrity principle compromised by prioritizing friendship over reporting obligations",
"source_text": "Because of their long friendship and consideration of Engineer B's impairment, Engineer A did not report Engineer B to the State Board",
"balancing_with": ["Friendship", "Compassion for impairment"],
"tension_resolution": "Personal relationship and sympathy overrode reporting obligation",
"case_relevance": "Highlights conflict between professional integrity and personal loyalty"
},
{
"identifier": "Transparency_PrivateMeeting",
"principle_class": "Transparency Principle",
"concrete_expression": "Engineer A met privately with Engineer B and confronted him with the faulty design",
"invoked_by": ["Engineer A"],
"applied_to": ["Addressing the structural failures"],
"interpretation": "Limited transparency - private confrontation rather than public/official disclosure",
"source_text": "As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B",
"balancing_with": ["Professional courtesy", "Friendship"],
"tension_resolution": "Chose private transparency over public disclosure",
"case_relevance": "Shows attempt to address issue while protecting colleague"
},
{
"identifier": "ProfessionalAccountability_EngineerB",
"principle_class": "Professional Virtue Principle",
"concrete_expression": "Engineer B would sign and seal the drawings with little to no review",
"invoked_by": ["Engineer B (violated)"],
"applied_to": ["Taking responsibility for engineering work"],
"interpretation": "Accountability principle violated by sealing work not properly reviewed",
"source_text": "Engineer Intern C... would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review",
"balancing_with": ["Financial survival", "Business continuity"],
"tension_resolution": "Abandoned accountability to maintain business operations",
"case_relevance": "Core violation leading to structural failure"
}
]
}
```
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 facts section:
Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development. Business has been very successful, so much so that Engineer A has taken steps to expand the business. Among other things, Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design.
Construction drawings were completed, permits were issued, a contract was let, and the contractor began construction of the new office building – which included a basement. However, early during the process of constructing the basement there was a significant structural failure. While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details. To obtain a second opinion about the failure, Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure.
Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet. Engineer A retained Engineer R to completely redesign the structure.
As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report. At this meeting, Engineer B divulged he had suffered a stroke a few months prior. Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office. Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience. The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review. Ultimately, this process led to the failure of Engineer A’s building.
Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board.
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:27
LLM Response
```json
{
"new_obligation_classes": [
{
"label": "Supervision Obligation",
"definition": "Requirement for licensed professionals to maintain direct supervision and review of work performed by unlicensed staff under their authority",
"derived_from_principle": "Professional Responsibility",
"duty_type": "professional",
"enforcement_mechanism": "State licensing board review and sanctions",
"violation_consequences": "License suspension/revocation, project failures, legal liability",
"examples_from_case": ["Engineer B failed to review Engineer Intern C's work", "Engineer B signed and sealed drawings with little to no review"],
"source_text": "Engineer Intern C would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review",
"confidence": 0.95,
"reasoning": "Distinct from Responsible Charge - focuses specifically on supervision of subordinates rather than overall project control"
},
{
"label": "Fitness to Practice Obligation",
"definition": "Duty to suspend or limit professional practice when physical or mental impairment compromises ability to perform safely and competently",
"derived_from_principle": "Public Safety",
"duty_type": "ethical",
"enforcement_mechanism": "Self-regulation, peer reporting, board investigation",
"violation_consequences": "Endangerment of public safety, professional sanctions, civil liability",
"examples_from_case": ["Engineer B continued practice after stroke", "Engineer B felt he could not afford to suspend work despite impairment"],
"source_text": "Engineer B divulged he had suffered a stroke a few months prior...Engineer B felt he could not afford to suspend work or close his office",
"confidence": 0.9,
"reasoning": "Not covered by existing Competence Obligation - addresses medical/health fitness rather than technical competence"
}
],
"obligation_individuals": [
{
"identifier": "EngineerB_SupervisionObligation_InternC",
"obligation_class": "Supervision Obligation",
"obligated_party": "Engineer B",
"obligation_statement": "Must properly review and supervise all structural design work performed by Engineer Intern C before signing and sealing",
"derived_from": "State PE licensing requirements",
"enforcement_context": "State Board enforcement through complaint process",
"temporal_scope": "Throughout employment of Engineer Intern C",
"compliance_status": "unmet",
"case_context": "Engineer B delegated design work to inexperienced intern without proper review, leading to structural failure",
"source_text": "Engineer B would sign and seal the drawings with little to no review",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "EngineerB_FitnessToPractice",
"obligation_class": "Fitness to Practice Obligation",
"obligated_party": "Engineer B",
"obligation_statement": "Must suspend or limit practice following stroke until capable of performing engineering duties safely",
"derived_from": "NSPE Code - Public Safety",
"enforcement_context": "Self-enforcement and peer reporting",
"temporal_scope": "From stroke occurrence until recovery",
"compliance_status": "unmet",
"case_context": "Engineer B continued practicing despite stroke-related impairment",
"source_text": "Engineer B divulged he had suffered a stroke a few months prior",
"is_existing_class": false,
"confidence": 0.9
},
{
"identifier": "EngineerA_ReportingObligation_BoardViolation",
"obligation_class": "Reporting Obligation",
"obligated_party": "Engineer A",
"obligation_statement": "Must report Engineer B's violations to State Board upon knowledge of incompetent practice endangering public",
"derived_from": "NSPE Code II.1.e",
"enforcement_context": "Professional ethics enforcement",
"temporal_scope": "Upon discovery of violations",
"compliance_status": "unmet",
"case_context": "Engineer A chose not to report due to friendship despite knowing about violations",
"source_text": "Because of their long friendship and consideration of Engineer B's impairment, Engineer A did not report Engineer B to the State Board",
"is_existing_class": true,
"confidence": 0.95
},
{
"identifier": "EngineerB_CompetenceObligation_StructuralDesign",
"obligation_class": "Competence Obligation",
"obligated_party": "Engineer B",
"obligation_statement": "Must only perform structural engineering services when competent and capable",
"derived_from": "NSPE Code II.2",
"enforcement_context": "State licensing board enforcement",
"temporal_scope": "During entire project period",
"compliance_status": "unmet",
"case_context": "Engineer B accepted and sealed structural work despite impaired condition",
"source_text": "serious structural design errors, omissions, and faulty details",
"is_existing_class": true,
"confidence": 0.95
},
{
"identifier": "EngineerInternC_DisclosureObligation_Supervision",
"obligation_class": "Disclosure Obligation",
"obligated_party": "Engineer Intern C",
"obligation_statement": "Must disclose lack of proper supervision and Engineer B's impairment to appropriate authorities",
"derived_from": "Professional ethics",
"enforcement_context": "Professional conduct standards",
"temporal_scope": "Upon awareness of improper practice",
"compliance_status": "unmet",
"case_context": "Engineer Intern C was fully aware of Engineer B's impaired condition but continued work",
"source_text": "Engineer Intern C (who was fully aware of Engineer B's impaired condition)",
"is_existing_class": true,
"confidence": 0.85
},
{
"identifier": "EngineerB_ResponsibleChargeObligation",
"obligation_class": "Responsible Charge Obligation",
"obligated_party": "Engineer B",
"obligation_statement": "Must maintain active engagement and personal decision-making authority throughout structural design process",
"derived_from": "State PE regulations",
"enforcement_context": "State Board enforcement",
"temporal_scope": "Throughout project duration",
"compliance_status": "unmet",
"case_context": "Engineer B delegated practically all design work without maintaining responsible charge",
"source_text": "Engineer B delegated practically all design work to Engineer Intern C",
"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 facts section:
Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development. Business has been very successful, so much so that Engineer A has taken steps to expand the business. Among other things, Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design.
Construction drawings were completed, permits were issued, a contract was let, and the contractor began construction of the new office building – which included a basement. However, early during the process of constructing the basement there was a significant structural failure. While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details. To obtain a second opinion about the failure, Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure.
Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet. Engineer A retained Engineer R to completely redesign the structure.
As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report. At this meeting, Engineer B divulged he had suffered a stroke a few months prior. Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office. Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience. The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review. Ultimately, this process led to the failure of Engineer A’s building.
Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board.
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:27
LLM Response
```json
{
"new_constraint_classes": [
{
"label": "Health Impairment Constraint",
"definition": "Physical or cognitive limitations resulting from medical conditions that restrict an engineer's ability to perform professional duties safely and competently",
"constraint_type": "physical",
"flexibility": "hard",
"violation_impact": "Risk of errors, failures, and potential harm to public safety",
"mitigation_possible": "Through delegation to qualified professionals, temporary suspension of practice, or medical treatment",
"examples_from_case": ["Engineer B's stroke limiting his ability to review designs", "Cognitive impairment affecting professional judgment"],
"source_text": "Engineer B divulged he had suffered a stroke a few months prior",
"confidence": 0.9,
"reasoning": "This represents physical/medical limitations on professional capacity, distinct from general competence constraints as it involves health-related impairment"
},
{
"label": "Financial Survival Constraint",
"definition": "Economic pressures that limit an engineer's ability to make ethically optimal decisions due to business survival needs",
"constraint_type": "resource",
"flexibility": "soft",
"violation_impact": "Business closure, financial ruin, loss of livelihood",
"mitigation_possible": "Through insurance, temporary closure, partnership, or selling practice",
"examples_from_case": ["Engineer B unable to suspend work due to financial reasons", "Need to maintain business operations despite impairment"],
"source_text": "for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office",
"confidence": 0.85,
"reasoning": "Distinct from general resource constraints as it specifically involves existential business/financial pressures that create ethical dilemmas"
}
],
"constraint_individuals": [
{
"identifier": "EngineerB_StrokeImpairment",
"constraint_class": "Health Impairment Constraint",
"constrained_entity": "Engineer B",
"constraint_statement": "Cannot perform adequate design review due to stroke-related impairment",
"source": "Medical condition (stroke)",
"enforcement_mechanism": "Physical/cognitive limitations",
"temporal_scope": "From stroke occurrence onward",
"severity": "critical",
"case_context": "Engineer B signed and sealed drawings with little to no review due to impairment",
"source_text": "Engineer B would sign and seal the drawings with little to no review",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "EngineerB_CompetenceLimit",
"constraint_class": "Competence Constraint",
"constrained_entity": "Engineer B",
"constraint_statement": "Limited ability to perform structural design work post-stroke",
"source": "Medical impairment affecting technical capabilities",
"enforcement_mechanism": "Physical and cognitive limitations",
"temporal_scope": "Post-stroke period",
"severity": "critical",
"case_context": "Delegated practically all design work to inexperienced engineer intern",
"source_text": "Engineer B delegated practically all design work to Engineer Intern C",
"is_existing_class": true,
"confidence": 0.9
},
{
"identifier": "InternC_ExperienceLimit",
"constraint_class": "Competence Constraint",
"constrained_entity": "Engineer Intern C",
"constraint_statement": "Limited to approximately two years of engineering experience",
"source": "Professional experience level",
"enforcement_mechanism": "Lack of professional licensure and experience",
"temporal_scope": "Current employment period",
"severity": "major",
"case_context": "Insufficient experience to handle complex structural design independently",
"source_text": "Engineer Intern C, a graduate engineer employee with about two years' experience",
"is_existing_class": true,
"confidence": 0.95
},
{
"identifier": "EngineerB_FinancialPressure",
"constraint_class": "Financial Survival Constraint",
"constrained_entity": "Engineer B",
"constraint_statement": "Cannot afford to suspend operations or close office",
"source": "Business financial requirements",
"enforcement_mechanism": "Economic necessity",
"temporal_scope": "Post-stroke period",
"severity": "major",
"case_context": "Led to continued operation despite impairment",
"source_text": "for financial and other reasons, Engineer B felt he could not afford to suspend work",
"is_existing_class": false,
"confidence": 0.85
},
{
"identifier": "EngineerB_SolePractitioner",
"constraint_class": "Resource Constraint",
"constrained_entity": "Engineer B's firm",
"constraint_statement": "Only one licensed professional engineer available in firm",
"source": "Firm structure and staffing",
"enforcement_mechanism": "Legal requirement for PE supervision",
"temporal_scope": "Ongoing",
"severity": "critical",
"case_context": "No backup PE to take over when Engineer B became impaired",
"source_text": "Being the only licensed professional engineer in his firm",
"is_existing_class": true,
"confidence": 0.9
},
{
"identifier": "StructuralFailure_Safety",
"constraint_class": "Safety Constraint",
"constrained_entity": "Building construction",
"constraint_statement": "Structure must meet safety standards to prevent failure",
"source": "Engineering standards and building codes",
"enforcement_mechanism": "Building permits and inspections",
"temporal_scope": "Construction and operation phases",
"severity": "critical",
"case_context": "Violated resulting in basement structural failure",
"source_text": "early during the process of constructing the basement there was a significant structural failure",
"is_existing_class": true,
"confidence": 0.95
}
]
}
```
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 facts section:
Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development. Business has been very successful, so much so that Engineer A has taken steps to expand the business. Among other things, Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design.
Construction drawings were completed, permits were issued, a contract was let, and the contractor began construction of the new office building – which included a basement. However, early during the process of constructing the basement there was a significant structural failure. While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details. To obtain a second opinion about the failure, Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure.
Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet. Engineer A retained Engineer R to completely redesign the structure.
As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report. At this meeting, Engineer B divulged he had suffered a stroke a few months prior. Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office. Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience. The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review. Ultimately, this process led to the failure of Engineer A’s building.
Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board.
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:28
LLM Response
```json
{
"new_capability_classes": [
{
"label": "Structural Design Review Capability",
"definition": "The competency to critically evaluate and identify errors, omissions, and faulty details in structural engineering designs",
"capability_type": "technical",
"norm_competence_related": "Enables fulfillment of duty to ensure public safety and structural integrity",
"skill_level": "expert",
"acquisition_method": "Advanced structural engineering education, extensive experience in structural analysis and failure investigation",
"examples_from_case": ["Engineer R's review revealed serious structural design errors", "Engineer A noticed odd structural bracing"],
"source_text": "Engineer R's review revealed a surprising number of serious structural design errors, omissions, and faulty details",
"confidence": 0.9,
"reasoning": "Distinct from general Technical Capability - specifically focuses on critical review and error detection in structural designs, not covered by existing classes"
},
{
"label": "Professional Impairment Recognition Capability",
"definition": "The competency to recognize when personal health conditions impair one's ability to perform professional duties safely and competently",
"capability_type": "ethical",
"norm_competence_related": "Enables self-assessment of fitness to practice and protection of public welfare",
"skill_level": "intermediate",
"acquisition_method": "Professional ethics training, self-awareness development, understanding of professional standards",
"examples_from_case": ["Engineer B failed to recognize need to suspend work after stroke", "Engineer B delegated work inappropriately due to impairment"],
"source_text": "Engineer B divulged he had suffered a stroke a few months prior...felt he could not afford to suspend work or close his office",
"confidence": 0.85,
"reasoning": "Not covered by existing ethical capabilities - addresses self-assessment of fitness to practice, crucial for public safety"
}
],
"capability_individuals": [
{
"identifier": "EngineerR_StructuralReview",
"capability_class": "Structural Design Review Capability",
"possessed_by": "Engineer R",
"capability_statement": "Perform independent review of structural drawings and identify design errors",
"demonstrated_through": "Successfully identified multiple serious structural design errors in Engineer B's work",
"proficiency_level": "expert",
"enables_obligations": "Duty to protect public safety through competent structural analysis",
"temporal_aspect": "During independent review after structural failure",
"case_context": "Retained as independent reviewer to assess failed basement structure",
"source_text": "Engineer R's review revealed a surprising number of serious structural design errors, omissions, and faulty details",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "EngineerB_ResponsibleCharge_Deficient",
"capability_class": "Responsible Charge Capability",
"possessed_by": "Engineer B",
"capability_statement": "Maintain active engagement and supervisory control of engineering work",
"demonstrated_through": "Failed to maintain - signed and sealed drawings with little to no review",
"proficiency_level": "basic",
"enables_obligations": "Failed to fulfill duty of responsible charge over structural designs",
"temporal_aspect": "After stroke, during delegation to Engineer Intern C",
"case_context": "Improperly delegated design work without adequate supervision",
"source_text": "Engineer Intern C would perform the structural design...and Engineer B would sign and seal the drawings with little to no review",
"is_existing_class": true,
"confidence": 0.9
},
{
"identifier": "EngineerInternC_Technical_Limited",
"capability_class": "Technical Capability",
"possessed_by": "Engineer Intern C",
"capability_statement": "Perform structural design work",
"demonstrated_through": "Two years of experience as graduate engineer",
"proficiency_level": "basic",
"enables_obligations": "Insufficient experience to independently handle complex structural designs",
"temporal_aspect": "During inappropriate delegation from Engineer B",
"case_context": "Performed structural design beyond competency level without proper supervision",
"source_text": "Engineer Intern C, a graduate engineer employee with about two years' experience",
"is_existing_class": true,
"confidence": 0.85
},
{
"identifier": "EngineerA_ProfessionalJudgment",
"capability_class": "Technology Integration Capability",
"possessed_by": "Engineer A",
"capability_statement": "Recognize when structural details appear questionable",
"demonstrated_through": "Noticed odd structural bracing and questionable details during failure observation",
"proficiency_level": "advanced",
"enables_obligations": "Duty to ensure quality and safety of construction projects",
"temporal_aspect": "During observation of structural failure",
"case_context": "Applied professional judgment to identify potential design issues",
"source_text": "While observing the failed system, Engineer A noticed what he believed was 'odd' structural bracing",
"is_existing_class": true,
"confidence": 0.8
}
]
}
```