Step 2: Normative Requirements Pass (Facts Section)
Extract principles, obligations, constraints, and capabilities from the facts section
Acknowledging Errors in Design
Step 2 of 5
Facts Section
Section Content:
Facts: Engineer T, a senior structural engineer who designs commercial buildings in the employ of XYZ Consulting Engineers, was in responsible charge of the design of major structural modifications to an existing building. In establishing the project scope for the structural modifications, Engineer T selected a straightforward approach that required making structural connections immediately beneath floor level on an upper floor, in a tightly constrained space. Engineer T proceeded with the project per these parameters and did not explore alternative design approaches. Rather, Engineer T completed the design within the identified constraints and issued construction documents for the modifications. The new structural connections were located in such a way that access was limited, and the drawings clearly noted the constrained access. This design detail required the construction workers to make the connections in a contorted fashion. During construction, an accident occurred with a serious and permanent injury to a construction worker. Following the accident, Engineer T revisited the site and realized that had alternative design concepts been explored early on, the new structural modifications could have been proposed in a fundamentally different, more complex, but functionally equivalent way. The alternative approach would have been more costly and taken more time, but it would have allowed the construction workers to make all connections while standing on the floor such that injury would have been far less likely. Engineer T felt some personal responsibility for the accident. Engineer T met with XYZ’s Chief Structural Engineer, Engineer B, explained the situation, and expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged. Engineer B responded that Engineer T and XYZ Consulting Engineers had responded professionally to the design project, they had recommended a straightforward structural modification approach, and they were not expected or asked to consider alternative concepts. Further, Engineer T had specifically identified the constrained area of the new connections in the design documents, but because T was not trained in construction safety either by education (since civil engineering education typically does not include construction safety) or by specific experience (working for a construction contractor), Engineer T could not have reasonably known or assessed the level of worker safety risk posed by the connection location. The contractor had not raised questions regarding the construction safety risk or safer construction alternatives. Having thus thoughtfully considered the matter, both Engineer T and Engineer B decided that the situation did not merit acknowledgement of “an error.”Months later, after a construction claim had been submitted and a lawsuit had been filed, Engineer T met with attorneys representing XYZ and XYZ’s insurance company to prepare for a deposition of Engineer T. During preparation, Engineer T reviewed and discussed the project history, including the conversation with Engineer B relative to T’s feeling there was, potentially, a professional obligation to acknowledge an error – i.e., not exploring alternative, safer design concepts. Both of XYZ Consulting Engineers’ attorneys agreed that a clear obligation existed not to distort or alter any facts, and that Engineer T should respond to questions with complete transparency during the deposition. They pointed out, however, that whether an error was made was not up to Engineer T and was not clear in this set of circumstances, including for the reasons that Engineer B had indicated to Engineer T earlier. They also pointed out that one of the purposes of the legal process was to determine what errors might have been made and by whom, and what impact such errors might have had on the accident. The attorneys indicated that the legal process would determine whether, based on the facts, an error had been made, and that Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error. In the deposition, Engineer T responded factually to all questions regarding the design and the design process. Engineer T was not asked if an error had been made and did not offer an acknowledgement of a possible error.
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 T, a senior structural engineer who designs commercial buildings in the employ of XYZ Consulting Engineers, was in responsible charge of the design of major structural modifications to an existing building. In establishing the project scope for the structural modifications, Engineer T selected a straightforward approach that required making structural connections immediately beneath floor level on an upper floor, in a tightly constrained space. Engineer T proceeded with the project per these parameters and did not explore alternative design approaches. Rather, Engineer T completed the design within the identified constraints and issued construction documents for the modifications.
The new structural connections were located in such a way that access was limited, and the drawings clearly noted the constrained access. This design detail required the construction workers to make the connections in a contorted fashion. During construction, an accident occurred with a serious and permanent injury to a construction worker. Following the accident, Engineer T revisited the site and realized that had alternative design concepts been explored early on, the new structural modifications could have been proposed in a fundamentally different, more complex, but functionally equivalent way. The alternative approach would have been more costly and taken more time, but it would have allowed the construction workers to make all connections while standing on the floor such that injury would have been far less likely. Engineer T felt some personal responsibility for the accident.
Engineer T met with XYZ’s Chief Structural Engineer, Engineer B, explained the situation, and expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged. Engineer B responded that Engineer T and XYZ Consulting Engineers had responded professionally to the design project, they had recommended a straightforward structural modification approach, and they were not expected or asked to consider alternative concepts. Further, Engineer T had specifically identified the constrained area of the new connections in the design documents, but because T was not trained in construction safety either by education (since civil engineering education typically does not include construction safety) or by specific experience (working for a construction contractor), Engineer T could not have reasonably known or assessed the level of worker safety risk posed by the connection location. The contractor had not raised questions regarding the construction safety risk or safer construction alternatives. Having thus thoughtfully considered the matter, both Engineer T and Engineer B decided that the situation did not merit acknowledgement of “an error.”
Months later, after a construction claim had been submitted and a lawsuit had been filed, Engineer T met with attorneys representing XYZ and XYZ’s insurance company to prepare for a deposition of Engineer T. During preparation, Engineer T reviewed and discussed the project history, including the conversation with Engineer B relative to T’s feeling there was, potentially, a professional obligation to acknowledge an error – i.e., not exploring alternative, safer design concepts. Both of XYZ Consulting Engineers’ attorneys agreed that a clear obligation existed not to distort or alter any facts, and that Engineer T should respond to questions with complete transparency during the deposition. They pointed out, however, that whether an error was made was not up to Engineer T and was not clear in this set of circumstances, including for the reasons that Engineer B had indicated to Engineer T earlier. They also pointed out that one of the purposes of the legal process was to determine what errors might have been made and by whom, and what impact such errors might have had on the accident. The attorneys indicated that the legal process would determine whether, based on the facts, an error had been made, and that Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error.
In the deposition, Engineer T responded factually to all questions regarding the design and the design process. Engineer T was not asked if an error had been made and did not offer an acknowledgement of a possible error.
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 13:39
LLM Response
```json
{
"new_principle_classes": [
{
"label": "Design Safety Consideration",
"definition": "Principle that design professionals should anticipate and mitigate safety risks for all stakeholders affected by their designs, including construction workers",
"abstract_nature": "Preventive care and harm prevention in the design phase",
"extensional_examples": ["Constructability reviews", "Worker safety in design", "Maintenance access planning", "Hazard elimination through design"],
"value_basis": "Responsibility for foreseeable consequences of design decisions",
"application_context": ["Structural engineering", "Construction planning", "Industrial design", "Infrastructure projects"],
"operationalization": "Through exploration of alternative designs, safety risk assessments, constructability analysis, consultation with construction professionals",
"balancing_requirements": ["Cost efficiency", "Time constraints", "Design simplicity", "Client expectations"],
"examples_from_case": ["The alternative approach would have been more costly and taken more time, but it would have allowed the construction workers to make all connections while standing on the floor such that injury would have been far less likely"],
"source_text": "The alternative approach would have been more costly and taken more time, but it would have allowed the construction workers to make all connections while standing on the floor such that injury would have been far less likely"
},
{
"label": "Professional Error Acknowledgment",
"definition": "Principle that professionals have an obligation to acknowledge errors or potential errors in their work when they become aware of them",
"abstract_nature": "Truthfulness and professional accountability",
"extensional_examples": ["Self-reporting design oversights", "Admitting calculation errors", "Acknowledging judgment mistakes", "Disclosing potential deficiencies"],
"value_basis": "Professional integrity and commitment to continuous improvement",
"application_context": ["Engineering practice", "Medical practice", "Legal practice", "All professional domains"],
"operationalization": "Through formal error reporting, client notification, peer review processes, professional board disclosures",
"balancing_requirements": ["Legal liability concerns", "Professional reputation", "Client relationships", "Insurance considerations"],
"examples_from_case": ["Engineer T... expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged"],
"source_text": "expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged"
}
],
"principle_individuals": [
{
"identifier": "PublicWelfare_WorkerSafety_EngineerT",
"principle_class": "Public Welfare Principle",
"concrete_expression": "Engineer T felt some personal responsibility for the accident",
"invoked_by": ["Engineer T"],
"applied_to": ["The serious injury to construction worker due to design constraints"],
"interpretation": "Public welfare extends to construction workers' safety, not just end users",
"source_text": "Engineer T felt some personal responsibility for the accident",
"balancing_with": ["Design efficiency", "Cost considerations", "Time constraints"],
"tension_resolution": "Initially not considered; retrospectively recognized as requiring greater weight",
"case_relevance": "Drives Engineer T's desire to acknowledge potential error"
},
{
"identifier": "Integrity_ErrorAcknowledgment_EngineerT",
"principle_class": "Integrity Principle",
"concrete_expression": "expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged",
"invoked_by": ["Engineer T"],
"applied_to": ["Decision whether to acknowledge design oversight"],
"interpretation": "Professional integrity requires acknowledging errors when recognized",
"source_text": "expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged",
"balancing_with": ["Legal liability", "Professional reputation", "Company interests"],
"tension_resolution": "Ultimately deferred to legal process and attorney advice",
"case_relevance": "Central ethical tension in the case"
},
{
"identifier": "Competence_LimitationsRecognition_EngineerB",
"principle_class": "Competence Principle",
"concrete_expression": "T was not trained in construction safety either by education (since civil engineering education typically does not include construction safety) or by specific experience (working for a construction contractor), Engineer T could not have reasonably known or assessed the level of worker safety risk",
"invoked_by": ["Engineer B"],
"applied_to": ["Engineer T's responsibility for construction safety"],
"interpretation": "Professionals cannot be held responsible for expertise outside their training",
"source_text": "T was not trained in construction safety either by education (since civil engineering education typically does not include construction safety) or by specific experience (working for a construction contractor), Engineer T could not have reasonably known or assessed the level of worker safety risk",
"balancing_with": ["Safety responsibility", "Error acknowledgment"],
"tension_resolution": "Used to justify not acknowledging error",
"case_relevance": "Provides rationale for not acknowledging design oversight"
},
{
"identifier": "Transparency_Deposition_Attorneys",
"principle_class": "Transparency Principle",
"concrete_expression": "a clear obligation existed not to distort or alter any facts, and that Engineer T should respond to questions with complete transparency during the deposition",
"invoked_by": ["XYZ's attorneys"],
"applied_to": ["Engineer T's deposition testimony"],
"interpretation": "Transparency requires factual accuracy but not voluntary self-incrimination",
"source_text": "a clear obligation existed not to distort or alter any facts, and that Engineer T should respond to questions with complete transparency during the deposition",
"balancing_with": ["Self-incrimination concerns", "Legal strategy"],
"tension_resolution": "Limited to responding factually to direct questions",
"case_relevance": "Defines the boundaries of truthfulness in legal proceedings"
},
{
"identifier": "ProfessionalJudgment_StandardPractice_EngineerB",
"principle_class": "Professional Virtue Principle",
"concrete_expression": "Engineer T and XYZ Consulting Engineers had responded professionally to the design project, they had recommended a straightforward structural modification approach, and they were not expected or asked to consider alternative concepts",
"invoked_by": ["Engineer B"],
"applied_to": ["Evaluation of Engineer T's design approach"],
"interpretation": "Professional judgment exercised within standard practice parameters is sufficient",
"source_text": "Engineer T and XYZ Consulting Engineers had responded professionally to the design project, they had recommended a straightforward structural modification approach, and they were not expected or asked to consider alternative concepts",
"balancing_with": ["Safety optimization", "Error acknowledgment"],
"tension_resolution": "Standard practice deemed sufficient despite accident",
"case_relevance": "Justifies decision not to acknowledge error"
}
]
}
```
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 T, a senior structural engineer who designs commercial buildings in the employ of XYZ Consulting Engineers, was in responsible charge of the design of major structural modifications to an existing building. In establishing the project scope for the structural modifications, Engineer T selected a straightforward approach that required making structural connections immediately beneath floor level on an upper floor, in a tightly constrained space. Engineer T proceeded with the project per these parameters and did not explore alternative design approaches. Rather, Engineer T completed the design within the identified constraints and issued construction documents for the modifications.
The new structural connections were located in such a way that access was limited, and the drawings clearly noted the constrained access. This design detail required the construction workers to make the connections in a contorted fashion. During construction, an accident occurred with a serious and permanent injury to a construction worker. Following the accident, Engineer T revisited the site and realized that had alternative design concepts been explored early on, the new structural modifications could have been proposed in a fundamentally different, more complex, but functionally equivalent way. The alternative approach would have been more costly and taken more time, but it would have allowed the construction workers to make all connections while standing on the floor such that injury would have been far less likely. Engineer T felt some personal responsibility for the accident.
Engineer T met with XYZ’s Chief Structural Engineer, Engineer B, explained the situation, and expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged. Engineer B responded that Engineer T and XYZ Consulting Engineers had responded professionally to the design project, they had recommended a straightforward structural modification approach, and they were not expected or asked to consider alternative concepts. Further, Engineer T had specifically identified the constrained area of the new connections in the design documents, but because T was not trained in construction safety either by education (since civil engineering education typically does not include construction safety) or by specific experience (working for a construction contractor), Engineer T could not have reasonably known or assessed the level of worker safety risk posed by the connection location. The contractor had not raised questions regarding the construction safety risk or safer construction alternatives. Having thus thoughtfully considered the matter, both Engineer T and Engineer B decided that the situation did not merit acknowledgement of “an error.”
Months later, after a construction claim had been submitted and a lawsuit had been filed, Engineer T met with attorneys representing XYZ and XYZ’s insurance company to prepare for a deposition of Engineer T. During preparation, Engineer T reviewed and discussed the project history, including the conversation with Engineer B relative to T’s feeling there was, potentially, a professional obligation to acknowledge an error – i.e., not exploring alternative, safer design concepts. Both of XYZ Consulting Engineers’ attorneys agreed that a clear obligation existed not to distort or alter any facts, and that Engineer T should respond to questions with complete transparency during the deposition. They pointed out, however, that whether an error was made was not up to Engineer T and was not clear in this set of circumstances, including for the reasons that Engineer B had indicated to Engineer T earlier. They also pointed out that one of the purposes of the legal process was to determine what errors might have been made and by whom, and what impact such errors might have had on the accident. The attorneys indicated that the legal process would determine whether, based on the facts, an error had been made, and that Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error.
In the deposition, Engineer T responded factually to all questions regarding the design and the design process. Engineer T was not asked if an error had been made and did not offer an acknowledgement of a possible error.
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 13:39
LLM Response
```json
{
"new_obligation_classes": [
{
"label": "Design Alternative Exploration Obligation",
"definition": "Duty to explore and evaluate alternative design approaches that could impact safety, constructability, or risk factors before finalizing design decisions",
"derived_from_principle": "Public Safety",
"duty_type": "professional",
"enforcement_mechanism": "Professional review boards, litigation, insurance claims",
"violation_consequences": "Potential liability for injuries, professional sanctions, insurance claims",
"examples_from_case": ["Not exploring alternative safer design concepts", "Selecting straightforward approach without considering construction worker safety"],
"source_text": "Engineer T selected a straightforward approach that required making structural connections immediately beneath floor level...and did not explore alternative design approaches",
"confidence": 0.85,
"reasoning": "This represents a specific design process obligation not covered by existing Safety or Competence obligations - it's about the duty to explore alternatives specifically"
},
{
"label": "Factual Testimony Obligation",
"definition": "Duty to provide complete, accurate, and transparent factual information during legal proceedings without distortion or alteration",
"derived_from_principle": "Honesty and Integrity",
"duty_type": "legal",
"enforcement_mechanism": "Legal sanctions for perjury, professional ethics boards",
"violation_consequences": "Perjury charges, loss of professional license, legal penalties",
"examples_from_case": ["Respond to questions with complete transparency during deposition", "Not distort or alter any facts"],
"source_text": "Both of XYZ Consulting Engineers' attorneys agreed that a clear obligation existed not to distort or alter any facts",
"confidence": 0.9,
"reasoning": "While related to disclosure, this is specifically about legal testimony obligations distinct from general disclosure duties"
}
],
"obligation_individuals": [
{
"identifier": "T_Safety_Design_Obligation",
"obligation_class": "Safety Obligation",
"obligated_party": "Engineer T",
"obligation_statement": "Hold paramount the safety, health, and welfare of the public including construction workers",
"derived_from": "NSPE I.1",
"enforcement_context": "Professional standards review and potential litigation",
"temporal_scope": "During design phase of structural modifications",
"compliance_status": "unclear",
"case_context": "Design resulted in constrained workspace that contributed to worker injury",
"source_text": "Engineer T felt some personal responsibility for the accident",
"is_existing_class": true,
"confidence": 0.95
},
{
"identifier": "T_Alternative_Exploration_Duty",
"obligation_class": "Design Alternative Exploration Obligation",
"obligated_party": "Engineer T",
"obligation_statement": "Explore alternative design concepts that could impact construction worker safety",
"derived_from": "Professional standard of care",
"enforcement_context": "Post-accident review and litigation",
"temporal_scope": "During initial design phase",
"compliance_status": "unmet",
"case_context": "Failed to explore safer but more complex alternatives before finalizing design",
"source_text": "had alternative design concepts been explored early on...injury would have been far less likely",
"is_existing_class": false,
"confidence": 0.8
},
{
"identifier": "T_Error_Acknowledgment_Consideration",
"obligation_class": "Disclosure Obligation",
"obligated_party": "Engineer T",
"obligation_statement": "Acknowledge design errors when identified",
"derived_from": "NSPE Code of Ethics",
"enforcement_context": "Internal company review with Chief Engineer",
"temporal_scope": "Post-accident review period",
"compliance_status": "unclear",
"case_context": "Engineer T believed error should be acknowledged but was advised otherwise",
"source_text": "expressed a belief that a design error...had been made and the NSPE Code of Ethics required that the error be acknowledged",
"is_existing_class": true,
"confidence": 0.75
},
{
"identifier": "T_Factual_Deposition_Duty",
"obligation_class": "Factual Testimony Obligation",
"obligated_party": "Engineer T",
"obligation_statement": "Provide complete, transparent, and factual responses during deposition without distorting facts",
"derived_from": "Legal requirements",
"enforcement_context": "Legal deposition proceedings",
"temporal_scope": "During deposition",
"compliance_status": "met",
"case_context": "Engineer T responded factually to all questions without volunteering error characterization",
"source_text": "Engineer T should respond to questions with complete transparency during the deposition",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "T_Responsible_Charge_Duty",
"obligation_class": "Responsible Charge Obligation",
"obligated_party": "Engineer T",
"obligation_statement": "Maintain active engagement and decision-making authority throughout structural modification design",
"derived_from": "Professional engineering standards",
"enforcement_context": "Professional practice standards",
"temporal_scope": "Throughout project duration",
"compliance_status": "met",
"case_context": "Engineer T was in responsible charge of the design of major structural modifications",
"source_text": "Engineer T, a senior structural engineer...was in responsible charge of the design of major structural modifications",
"is_existing_class": true,
"confidence": 0.9
}
]
}
```
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 T, a senior structural engineer who designs commercial buildings in the employ of XYZ Consulting Engineers, was in responsible charge of the design of major structural modifications to an existing building. In establishing the project scope for the structural modifications, Engineer T selected a straightforward approach that required making structural connections immediately beneath floor level on an upper floor, in a tightly constrained space. Engineer T proceeded with the project per these parameters and did not explore alternative design approaches. Rather, Engineer T completed the design within the identified constraints and issued construction documents for the modifications.
The new structural connections were located in such a way that access was limited, and the drawings clearly noted the constrained access. This design detail required the construction workers to make the connections in a contorted fashion. During construction, an accident occurred with a serious and permanent injury to a construction worker. Following the accident, Engineer T revisited the site and realized that had alternative design concepts been explored early on, the new structural modifications could have been proposed in a fundamentally different, more complex, but functionally equivalent way. The alternative approach would have been more costly and taken more time, but it would have allowed the construction workers to make all connections while standing on the floor such that injury would have been far less likely. Engineer T felt some personal responsibility for the accident.
Engineer T met with XYZ’s Chief Structural Engineer, Engineer B, explained the situation, and expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged. Engineer B responded that Engineer T and XYZ Consulting Engineers had responded professionally to the design project, they had recommended a straightforward structural modification approach, and they were not expected or asked to consider alternative concepts. Further, Engineer T had specifically identified the constrained area of the new connections in the design documents, but because T was not trained in construction safety either by education (since civil engineering education typically does not include construction safety) or by specific experience (working for a construction contractor), Engineer T could not have reasonably known or assessed the level of worker safety risk posed by the connection location. The contractor had not raised questions regarding the construction safety risk or safer construction alternatives. Having thus thoughtfully considered the matter, both Engineer T and Engineer B decided that the situation did not merit acknowledgement of “an error.”
Months later, after a construction claim had been submitted and a lawsuit had been filed, Engineer T met with attorneys representing XYZ and XYZ’s insurance company to prepare for a deposition of Engineer T. During preparation, Engineer T reviewed and discussed the project history, including the conversation with Engineer B relative to T’s feeling there was, potentially, a professional obligation to acknowledge an error – i.e., not exploring alternative, safer design concepts. Both of XYZ Consulting Engineers’ attorneys agreed that a clear obligation existed not to distort or alter any facts, and that Engineer T should respond to questions with complete transparency during the deposition. They pointed out, however, that whether an error was made was not up to Engineer T and was not clear in this set of circumstances, including for the reasons that Engineer B had indicated to Engineer T earlier. They also pointed out that one of the purposes of the legal process was to determine what errors might have been made and by whom, and what impact such errors might have had on the accident. The attorneys indicated that the legal process would determine whether, based on the facts, an error had been made, and that Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error.
In the deposition, Engineer T responded factually to all questions regarding the design and the design process. Engineer T was not asked if an error had been made and did not offer an acknowledgement of a possible error.
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 13:40
LLM Response
```json
{
"new_constraint_classes": [
{
"label": "Physical Access Constraint",
"definition": "Physical limitations on workspace accessibility that restrict how work can be performed or accessed",
"constraint_type": "physical",
"flexibility": "hard",
"violation_impact": "Work cannot be performed or requires dangerous/contorted positioning",
"mitigation_possible": "Can be mitigated through alternative design approaches that avoid constrained spaces",
"examples_from_case": ["Structural connections in tightly constrained space", "Limited access requiring contorted positioning"],
"source_text": "structural connections immediately beneath floor level on an upper floor, in a tightly constrained space",
"confidence": 0.9,
"reasoning": "Distinct from general Resource Constraint - specifically addresses physical workspace limitations affecting worker safety and access"
},
{
"label": "Design Scope Constraint",
"definition": "Limitations on the range of design alternatives that can be explored based on project parameters",
"constraint_type": "procedural",
"flexibility": "negotiable",
"violation_impact": "May result in suboptimal or potentially unsafe designs",
"mitigation_possible": "Can be expanded through explicit client request or proactive exploration of alternatives",
"examples_from_case": ["Not expected to consider alternative concepts", "Straightforward approach selected without exploring alternatives"],
"source_text": "they were not expected or asked to consider alternative concepts",
"confidence": 0.85,
"reasoning": "Different from Procedural Constraint - specifically limits the breadth of design exploration rather than process steps"
},
{
"label": "Legal Testimony Constraint",
"definition": "Boundaries on what can be voluntarily disclosed or characterized during legal proceedings",
"constraint_type": "legal",
"flexibility": "hard",
"violation_impact": "May prejudice legal proceedings or create liability",
"mitigation_possible": "Cannot be mitigated - must respond factually to direct questions only",
"examples_from_case": ["Should not voluntarily characterize work as error", "Respond factually but not offer acknowledgement"],
"source_text": "should clearly report the facts, but should not voluntarily characterize the design work as an error",
"confidence": 0.95,
"reasoning": "Specific type of legal constraint governing testimony behavior, distinct from general Legal Constraint"
}
],
"constraint_individuals": [
{
"identifier": "Structural_Connection_Physical_Access",
"constraint_class": "Physical Access Constraint",
"constrained_entity": "Construction workers",
"constraint_statement": "Connections must be made in tightly constrained space beneath floor level requiring contorted positioning",
"source": "Engineer T's design placement",
"enforcement_mechanism": "Physical impossibility of alternative positioning",
"temporal_scope": "During construction phase",
"severity": "critical",
"case_context": "Led to serious permanent injury during construction",
"source_text": "required the construction workers to make the connections in a contorted fashion",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "Project_Scope_Design_Alternatives",
"constraint_class": "Design Scope Constraint",
"constrained_entity": "Engineer T",
"constraint_statement": "Limited to straightforward approach without exploring alternative design concepts",
"source": "Project scope parameters",
"enforcement_mechanism": "Professional expectations and project parameters",
"temporal_scope": "Design phase",
"severity": "major",
"case_context": "Prevented exploration of safer but more complex alternatives",
"source_text": "did not explore alternative design approaches",
"is_existing_class": false,
"confidence": 0.85
},
{
"identifier": "Engineer_T_Competence_Construction_Safety",
"constraint_class": "Competence Constraint",
"constrained_entity": "Engineer T",
"constraint_statement": "Cannot assess construction safety risks due to lack of training in construction safety",
"source": "Educational and professional background",
"enforcement_mechanism": "Lack of knowledge and experience",
"temporal_scope": "Throughout project",
"severity": "major",
"case_context": "Could not reasonably assess worker safety risk of connection location",
"source_text": "T was not trained in construction safety either by education...or by specific experience",
"is_existing_class": true,
"confidence": 0.9
},
{
"identifier": "Deposition_Voluntary_Characterization",
"constraint_class": "Legal Testimony Constraint",
"constrained_entity": "Engineer T",
"constraint_statement": "Cannot voluntarily characterize design work as an error during deposition",
"source": "Legal counsel advice",
"enforcement_mechanism": "Legal strategy and attorney guidance",
"temporal_scope": "During deposition",
"severity": "critical",
"case_context": "Must respond factually but not offer acknowledgement of error",
"source_text": "should not voluntarily characterize the design work as an error",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "Truth_Disclosure_Legal_Proceedings",
"constraint_class": "Inviolable Constraint",
"constrained_entity": "Engineer T",
"constraint_statement": "Cannot distort or alter any facts during legal proceedings",
"source": "Legal and ethical requirements",
"enforcement_mechanism": "Legal penalties for perjury",
"temporal_scope": "During all legal proceedings",
"severity": "critical",
"case_context": "Must respond with complete transparency during deposition",
"source_text": "a clear obligation existed not to distort or alter any facts",
"is_existing_class": true,
"confidence": 1.0
}
]
}
```
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 T, a senior structural engineer who designs commercial buildings in the employ of XYZ Consulting Engineers, was in responsible charge of the design of major structural modifications to an existing building. In establishing the project scope for the structural modifications, Engineer T selected a straightforward approach that required making structural connections immediately beneath floor level on an upper floor, in a tightly constrained space. Engineer T proceeded with the project per these parameters and did not explore alternative design approaches. Rather, Engineer T completed the design within the identified constraints and issued construction documents for the modifications.
The new structural connections were located in such a way that access was limited, and the drawings clearly noted the constrained access. This design detail required the construction workers to make the connections in a contorted fashion. During construction, an accident occurred with a serious and permanent injury to a construction worker. Following the accident, Engineer T revisited the site and realized that had alternative design concepts been explored early on, the new structural modifications could have been proposed in a fundamentally different, more complex, but functionally equivalent way. The alternative approach would have been more costly and taken more time, but it would have allowed the construction workers to make all connections while standing on the floor such that injury would have been far less likely. Engineer T felt some personal responsibility for the accident.
Engineer T met with XYZ’s Chief Structural Engineer, Engineer B, explained the situation, and expressed a belief that a design error – i.e., not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged. Engineer B responded that Engineer T and XYZ Consulting Engineers had responded professionally to the design project, they had recommended a straightforward structural modification approach, and they were not expected or asked to consider alternative concepts. Further, Engineer T had specifically identified the constrained area of the new connections in the design documents, but because T was not trained in construction safety either by education (since civil engineering education typically does not include construction safety) or by specific experience (working for a construction contractor), Engineer T could not have reasonably known or assessed the level of worker safety risk posed by the connection location. The contractor had not raised questions regarding the construction safety risk or safer construction alternatives. Having thus thoughtfully considered the matter, both Engineer T and Engineer B decided that the situation did not merit acknowledgement of “an error.”
Months later, after a construction claim had been submitted and a lawsuit had been filed, Engineer T met with attorneys representing XYZ and XYZ’s insurance company to prepare for a deposition of Engineer T. During preparation, Engineer T reviewed and discussed the project history, including the conversation with Engineer B relative to T’s feeling there was, potentially, a professional obligation to acknowledge an error – i.e., not exploring alternative, safer design concepts. Both of XYZ Consulting Engineers’ attorneys agreed that a clear obligation existed not to distort or alter any facts, and that Engineer T should respond to questions with complete transparency during the deposition. They pointed out, however, that whether an error was made was not up to Engineer T and was not clear in this set of circumstances, including for the reasons that Engineer B had indicated to Engineer T earlier. They also pointed out that one of the purposes of the legal process was to determine what errors might have been made and by whom, and what impact such errors might have had on the accident. The attorneys indicated that the legal process would determine whether, based on the facts, an error had been made, and that Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error.
In the deposition, Engineer T responded factually to all questions regarding the design and the design process. Engineer T was not asked if an error had been made and did not offer an acknowledgement of a possible error.
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 13:41
LLM Response
```json
{
"new_capability_classes": [
{
"label": "Construction Safety Assessment Capability",
"definition": "The competency to identify and evaluate safety risks to construction workers during the design phase of engineering projects",
"capability_type": "technical",
"norm_competence_related": "Enables fulfillment of duty to hold paramount the safety, health, and welfare of the public including construction workers",
"skill_level": "advanced",
"acquisition_method": "Specialized training in construction safety, experience working with construction contractors, or formal education in construction methods",
"examples_from_case": ["Assessing worker safety risk posed by connection location", "Identifying safer construction alternatives"],
"source_text": "Engineer T could not have reasonably known or assessed the level of worker safety risk posed by the connection location",
"confidence": 0.9,
"reasoning": "This capability is distinct from general safety compliance - it specifically addresses the ability to anticipate and mitigate construction worker safety risks during design phase"
},
{
"label": "Alternative Design Exploration Capability",
"definition": "The competency to systematically explore and evaluate multiple design approaches to identify optimal solutions considering various constraints and impacts",
"capability_type": "analytical",
"norm_competence_related": "Enables fulfillment of professional duty to consider broader impacts and optimize designs beyond immediate functional requirements",
"skill_level": "intermediate",
"acquisition_method": "Professional experience, design methodology training, mentorship in comprehensive design practices",
"examples_from_case": ["Exploring alternative, safer design concepts", "Considering fundamentally different approaches"],
"source_text": "not exploring alternative, safer design concepts – had been made and the NSPE Code of Ethics required that the error be acknowledged",
"confidence": 0.85,
"reasoning": "While related to technical capability, this specifically addresses the analytical competency to systematically consider alternatives, which is distinct from technical execution"
},
{
"label": "Legal Process Navigation Capability",
"definition": "The competency to appropriately participate in legal proceedings while maintaining professional integrity and factual accuracy",
"capability_type": "ethical",
"norm_competence_related": "Enables fulfillment of obligations to be truthful while respecting legal process boundaries and professional judgment",
"skill_level": "advanced",
"acquisition_method": "Legal training, experience with depositions and litigation, guidance from legal counsel",
"examples_from_case": ["Responding factually in depositions", "Understanding boundaries of professional judgment in legal contexts"],
"source_text": "Engineer T should clearly report the facts, but should not voluntarily characterize the design work as an error",
"confidence": 0.8,
"reasoning": "This capability addresses the specific competency needed to navigate legal proceedings while maintaining professional ethics, distinct from general regulatory compliance"
}
],
"capability_individuals": [
{
"identifier": "EngineerT_StructuralDesign",
"capability_class": "Technical Capability",
"possessed_by": "Engineer T",
"capability_statement": "Design major structural modifications to existing commercial buildings",
"demonstrated_through": "Position as senior structural engineer in responsible charge of design",
"proficiency_level": "expert",
"enables_obligations": "Fulfillment of professional engineering design responsibilities",
"temporal_aspect": "Throughout the project design phase",
"case_context": "Successfully completed structural modification design within identified constraints",
"source_text": "Engineer T, a senior structural engineer who designs commercial buildings...was in responsible charge of the design",
"is_existing_class": true,
"confidence": 1.0
},
{
"identifier": "EngineerT_LackingConstructionSafety",
"capability_class": "Construction Safety Assessment Capability",
"possessed_by": "Engineer T",
"capability_statement": "Limited ability to assess construction worker safety risks",
"demonstrated_through": "Lack of training in construction safety through education or specific experience",
"proficiency_level": "basic",
"enables_obligations": "Insufficient to fulfill complete safety assessment obligations",
"temporal_aspect": "During design phase",
"case_context": "Could not reasonably assess worker safety risk despite noting constrained access",
"source_text": "T was not trained in construction safety either by education...or by specific experience",
"is_existing_class": false,
"confidence": 0.95
},
{
"identifier": "EngineerB_ProfessionalJudgment",
"capability_class": "Justification Capability",
"possessed_by": "Engineer B",
"capability_statement": "Evaluate and justify professional decisions based on standard practice",
"demonstrated_through": "Position as Chief Structural Engineer providing guidance",
"proficiency_level": "expert",
"enables_obligations": "Determination of professional standards and error acknowledgment requirements",
"temporal_aspect": "Post-accident review",
"case_context": "Provided reasoning why the situation did not constitute an error requiring acknowledgment",
"source_text": "Engineer B responded that Engineer T and XYZ Consulting Engineers had responded professionally to the design project",
"is_existing_class": true,
"confidence": 0.9
},
{
"identifier": "EngineerT_AlternativeDesignLimited",
"capability_class": "Alternative Design Exploration Capability",
"possessed_by": "Engineer T",
"capability_statement": "Limited exploration of alternative design approaches",
"demonstrated_through": "Selection of straightforward approach without exploring alternatives",
"proficiency_level": "basic",
"enables_obligations": "Partial fulfillment of comprehensive design obligations",
"temporal_aspect": "Initial design phase",
"case_context": "Did not explore alternative concepts that could have been safer",
"source_text": "Engineer T selected a straightforward approach...and did not explore alternative design approaches",
"is_existing_class": false,
"confidence": 0.85
},
{
"identifier": "EngineerT_LegalTestimony",
"capability_class": "Legal Process Navigation Capability",
"possessed_by": "Engineer T",
"capability_statement": "Provide factual testimony in legal proceedings",
"demonstrated_through": "Deposition performance responding factually to all questions",
"proficiency_level": "advanced",
"enables_obligations": "Fulfillment of legal and ethical obligations in litigation",
"temporal_aspect": "During deposition",
"case_context": "Responded factually without voluntarily characterizing work as error",
"source_text": "In the deposition, Engineer T responded factually to all questions regarding the design and the design process",
"is_existing_class": false,
"confidence": 0.9
},
{
"identifier": "EngineerT_ResponsibleCharge",
"capability_class": "Responsible Charge Capability",
"possessed_by": "Engineer T",
"capability_statement": "Maintain responsible charge of structural modification projects",
"demonstrated_through": "Active engagement from conception through construction documentation",
"proficiency_level": "expert",
"enables_obligations": "Professional responsibility for project outcomes",
"temporal_aspect": "Throughout project lifecycle",
"case_context": "Maintained responsible charge despite not exploring all alternatives",
"source_text": "Engineer T...was in responsible charge of the design of major structural modifications",
"is_existing_class": true,
"confidence": 1.0
}
]
}
```