Step 2: Normative Requirements Pass (Discussion Section)

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

Community Engagement for Infrastructure Projects
Step 2 of 5

Discussion Section

Section Content:
Discussion:
The overriding issue for the Board of Ethical Review (BER) to consider in this case is that of the actions of Firm DBA.
The ethical requirements of Firm DBA must be clarified before establishing what actions are required by Engineer M.
As stated, Firm DBA provided a report that omitted details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted.
Additionally, Firm DBA’s report claimed Community P supported the project, without any evidence to support that claim.
These actions likely violated the NSPE Code of Ethics ( Code) regarding issuing statements in an objective and truthful manner, deceptive acts, misrepresentation of fact, and omitting a material fact However, does the Code apply to Firm DBA?
If the individuals most heavily involved in the project at Firm DBA are Certified Public Relations Professionals, they would be held to a code of ethics that provides for honest and truthful conduct.
However, the BER will not comment on these potential obligations, as it is beyond the BER’s duties to review other codes.
In BER Case 60-3 , the facts indicated that an engineering firm was providing sub-professional services and, because of that, the firm was not required to abide by the provisions of the Canons of Ethics and Rules of Professional Conduct.
The conclusion by the BER in BER Case 60-3 was that the Canons and Rules did not apply.
However, the Code has been revised since that time.
The most fundamental and primary Canon of the Code is to hold paramount the safety, health, and welfare of the public.
The facts in this case state that Firm DBA has licensed professional engineers in charge or in supervisory roles of all departments in the firm as well as ownership.
It would be difficult to believe that through their duties as licensed professional engineers, the Code would be irrelevant to the Firm’s business dealings simply because the services being provided were not engineering from a design, calculation, or engineering judgment perspective but were confined to communication and public relation services.
The Preamble of the Code of states that professional behavior requires adherence to the highest principles of ethical conduct.
Therefore, the Code applies to Firm DBA.
BER Case 98-2 addressed the ethical concerns of an international NSPE member that encountered separate and conflicting legal and ethical issues working in a county other than the U.
S.
In that case the BER determined that the engineer was bound by the Code and stated that “it would be a major error for NSPE to apply one standard of conduct to one set of NSPE members and another standard of conduct to another set of NSPE members.” Although that case was based on geographical concerns rather than the type of services provided, it was determined that the Code applied to members universally.
In BER Case 88-6 , Engineer A had the responsibility for a city’s waste disposal plant and is also directly responsible to City Administrator C.
Engineer A informed City Administrator C of the inadequacy of the disposal plant in a certain potential scenario.
City Administrator C told Engineer A to discuss this matter only with him and, subsequentially, removed Engineer A from responsibility of the disposal plant.
Engineer A took no further action.
The critical scenario did, in fact, happen and a release of partially-treated wastewater occurred.
The BER found that Engineer A did not fulfill ethical obligations of holding paramount the safety, health, and welfare of the public.
As in this case, Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public.
In BER Case 09-10 , Engineer A owned ABC Engineering in State P.
Engineer X owned XYZ Engineering in State Q.
Engineer X was retained to provide engineering services for Client L located in State P for a project in State P.
Client L was a former client of Engineer A’s firm.
Engineer A learned that XYZ Engineering did not have a current certificate of authority to practice engineering in State P.
The question to the BER was to evaluate what Engineer A’s ethical obligations would be under these facts.
The BER found that Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question.
The BER further found that if Engineer A was not sufficiently satisfied with Engineer X’s explanation, Engineer A may be required to report this matter to the state engineering licensure board.
In BER Case 21-7 , the question put to the BER was as follows: should an Engineer include information about the utility generation mix and rolling blackouts in the report to an organization?
The BER found that as a registered professional, that Engineer was obliged to include relevant and pertinent information in a report to the organization.
A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare.
Likewise, in this case, pertinent information was missing from the report.
By this reasoning, Engineer M not only has the right to challenge the validity of the DBA report but also must consider their involvement in the project as they shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise as stated in Code section II.1.d.
The result of going forward with the project could also have disastrous consequences.
If the facts come out later that relevant information was not disclosed in the report, the impact of such could be very negative.
Again, Engineer M has an additional obligation to advise their clients or employers when they believe a project will not be successful as stated in Code section III.1.b.
As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA.
Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code.
The licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved in these discussions as they have the ultimate responsibility to see that ethical practices are followed.
Should Firm DBA acknowledge their ethical obligations after being confronted by Engineer M, a more immediate resolution to the issues may be realized and Firm DBA could correct the discrepancies.
A more unfavorable result would be anticipated if Firm DBA takes the position that it performed the work under the direction of the City and are, therefore, unwilling to make the corrections.
Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved.
After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board.
Although seemingly extreme, reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future.
Principles Extraction
LLM Prompt
DUAL PRINCIPLE EXTRACTION - Ethical Principles Analysis THEORETICAL CONTEXT (Chapter 2.2.2): - Principles are ABSTRACT ethical foundations requiring extensional definition through cases - They function like constitutional principles - open-textured and requiring interpretation - Principles mediate moral ideals into concrete reality through context-specific application - They cannot be applied deductively but require balancing and interpretation EXISTING PRINCIPLE CLASSES IN ONTOLOGY: - Competence Principle: Balances professional autonomy with recognition of limitations and need for collaboration. - Confidentiality Principle: Must be balanced against public safety obligations and legal disclosure requirements. - Domain-Specific Principle: Examples: Environmental Stewardship (engineering), Patient Autonomy (medicine), Academic Freedom (education). These address domain-specific ethical ch - Environmental Stewardship Principle: Bridges engineering practice with broader environmental and societal responsibilities. - Ethical Principle: Legacy synonym for Principle. Use :Principle for new concepts. - Fundamental Ethical Principle: Examples: Public Welfare Paramount, Respect for Persons, Justice, Beneficence. These require extensive interpretation and balancing in specific contex - Integrity Principle: Central to professional identity formation and trust maintenance in professional relationships. - Principle: An information content entity representing ethical values and guidelines for conduct. This is the P component of the formal specification D=(R,P,O,S,R - Principle Argument: An argument based on fundamental ethical principles or values. - Principle Refinement: Capability to evolve principles as inconsistencies are resolved and new cases are added (GenEth system, Anderson & Anderson 2018) - Professional Virtue Principle: Examples: Integrity, Competence, Honesty, Professional Courage, Accountability. These shape professional character and decision-making. - Public Welfare Principle: Requires contextual interpretation to balance against client confidentiality and employer loyalty when public safety is at risk. - Relational Principle: Examples: Confidentiality, Loyalty, Fairness, Transparency, Respect for Autonomy. These govern interpersonal professional dynamics. - Transparency Principle: Essential for maintaining trust and enabling stakeholder participation in professional decisions. === TASK === From the following case text (discussion section), extract information at TWO levels: LEVEL 1 - NEW PRINCIPLE CLASSES: Identify ethical principles that appear to be NEW types not covered by existing classes above. Look for: - Fundamental ethical values being invoked - Abstract moral ideals guiding decisions - Constitutional-like principles requiring interpretation - Values that transcend specific rules or obligations For each NEW principle class, provide: - label: Clear principle name (e.g., "Environmental Stewardship", "Professional Autonomy") - definition: What moral ideal this principle represents - abstract_nature: The abstract ethical foundation (justice, welfare, autonomy, etc.) - extensional_examples: Concrete cases/situations where this principle applies - value_basis: Core moral value underlying the principle - application_context: Professional domains or situations where relevant - operationalization: How this abstract principle becomes concrete in practice - balancing_requirements: What other principles it typically must be balanced against - examples_from_case: How this principle appears in the case text LEVEL 2 - PRINCIPLE INDIVIDUALS: Identify specific instances where principles are invoked or applied. For each instance: - identifier: Unique identifier for this principle instance (e.g., "PublicSafety_Case8_Discussion") - principle_class: Which principle class it instantiates (use existing classes when possible) - concrete_expression: EXACT text showing how the principle is expressed - invoked_by: Who invokes or appeals to this principle - applied_to: What decision/situation/dilemma it applies to - interpretation: How the principle is interpreted in this specific context - balancing_with: Other principles that must be balanced against it - tension_resolution: How conflicts between principles are resolved - case_relevance: Why this principle matters in this specific case IMPORTANT: - Focus on ABSTRACT ethical foundations, not specific rules or procedures - Principles are broader than obligations - they generate obligations in context - Use EXACT quotes from case text where principles are expressed - Distinguish between the abstract principle CLASS and its concrete APPLICATION CASE TEXT: The overriding issue for the Board of Ethical Review (BER) to consider in this case is that of the actions of Firm DBA. The ethical requirements of Firm DBA must be clarified before establishing what actions are required by Engineer M. As stated, Firm DBA provided a report that omitted details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted. Additionally, Firm DBA’s report claimed Community P supported the project, without any evidence to support that claim. These actions likely violated the NSPE Code of Ethics ( Code) regarding issuing statements in an objective and truthful manner, deceptive acts, misrepresentation of fact, and omitting a material fact However, does the Code apply to Firm DBA? If the individuals most heavily involved in the project at Firm DBA are Certified Public Relations Professionals, they would be held to a code of ethics that provides for honest and truthful conduct. However, the BER will not comment on these potential obligations, as it is beyond the BER’s duties to review other codes. In BER Case 60-3 , the facts indicated that an engineering firm was providing sub-professional services and, because of that, the firm was not required to abide by the provisions of the Canons of Ethics and Rules of Professional Conduct. The conclusion by the BER in BER Case 60-3 was that the Canons and Rules did not apply. However, the Code has been revised since that time. The most fundamental and primary Canon of the Code is to hold paramount the safety, health, and welfare of the public. The facts in this case state that Firm DBA has licensed professional engineers in charge or in supervisory roles of all departments in the firm as well as ownership. It would be difficult to believe that through their duties as licensed professional engineers, the Code would be irrelevant to the Firm’s business dealings simply because the services being provided were not engineering from a design, calculation, or engineering judgment perspective but were confined to communication and public relation services. The Preamble of the Code of states that professional behavior requires adherence to the highest principles of ethical conduct. Therefore, the Code applies to Firm DBA. BER Case 98-2 addressed the ethical concerns of an international NSPE member that encountered separate and conflicting legal and ethical issues working in a county other than the U.S. In that case the BER determined that the engineer was bound by the Code and stated that “it would be a major error for NSPE to apply one standard of conduct to one set of NSPE members and another standard of conduct to another set of NSPE members.” Although that case was based on geographical concerns rather than the type of services provided, it was determined that the Code applied to members universally. In BER Case 88-6 , Engineer A had the responsibility for a city’s waste disposal plant and is also directly responsible to City Administrator C. Engineer A informed City Administrator C of the inadequacy of the disposal plant in a certain potential scenario. City Administrator C told Engineer A to discuss this matter only with him and, subsequentially, removed Engineer A from responsibility of the disposal plant. Engineer A took no further action. The critical scenario did, in fact, happen and a release of partially-treated wastewater occurred. The BER found that Engineer A did not fulfill ethical obligations of holding paramount the safety, health, and welfare of the public. As in this case, Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public. In BER Case 09-10 , Engineer A owned ABC Engineering in State P. Engineer X owned XYZ Engineering in State Q. Engineer X was retained to provide engineering services for Client L located in State P for a project in State P. Client L was a former client of Engineer A’s firm. Engineer A learned that XYZ Engineering did not have a current certificate of authority to practice engineering in State P. The question to the BER was to evaluate what Engineer A’s ethical obligations would be under these facts. The BER found that Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question. The BER further found that if Engineer A was not sufficiently satisfied with Engineer X’s explanation, Engineer A may be required to report this matter to the state engineering licensure board. In BER Case 21-7 , the question put to the BER was as follows: should an Engineer include information about the utility generation mix and rolling blackouts in the report to an organization? The BER found that as a registered professional, that Engineer was obliged to include relevant and pertinent information in a report to the organization. A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare. Likewise, in this case, pertinent information was missing from the report. By this reasoning, Engineer M not only has the right to challenge the validity of the DBA report but also must consider their involvement in the project as they shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise as stated in Code section II.1.d. The result of going forward with the project could also have disastrous consequences. If the facts come out later that relevant information was not disclosed in the report, the impact of such could be very negative. Again, Engineer M has an additional obligation to advise their clients or employers when they believe a project will not be successful as stated in Code section III.1.b. As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code. The licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved in these discussions as they have the ultimate responsibility to see that ethical practices are followed. Should Firm DBA acknowledge their ethical obligations after being confronted by Engineer M, a more immediate resolution to the issues may be realized and Firm DBA could correct the discrepancies. A more unfavorable result would be anticipated if Firm DBA takes the position that it performed the work under the direction of the City and are, therefore, unwilling to make the corrections. Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved. After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board. Although seemingly extreme, reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future. 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-19 19:00
LLM Response
```json
{
    "new_principle_classes": [
        {
            "label": "Universal Application Principle",
            "definition": "Principle that ethical standards apply uniformly to all professionals regardless of geographical location, type of service provided, or specific context",
            "abstract_nature": "Universality and consistency of ethical obligations",
            "extensional_examples": ["International practice", "Non-engineering services by engineers", "Cross-jurisdictional work"],
            "value_basis": "Equal moral standing and consistent professional standards",
            "application_context": ["International engineering", "Multi-disciplinary firms", "Cross-border practice"],
            "operationalization": "Through consistent application of codes regardless of service type or location",
            "balancing_requirements": ["Local laws and customs", "Service-specific standards", "Jurisdictional variations"],
            "examples_from_case": ["Code applies to Firm DBA despite providing PR services", "NSPE members held to same standards globally"],
            "source_text": "it would be a major error for NSPE to apply one standard of conduct to one set of NSPE members and another standard of conduct to another set of NSPE members"
        },
        {
            "label": "Truthful Communication Principle",
            "definition": "Principle requiring complete, accurate, and non-misleading communication of material facts in professional reports and statements",
            "abstract_nature": "Truth, completeness, and transparency in professional communication",
            "extensional_examples": ["Engineering reports", "Public consultation summaries", "Project impact assessments"],
            "value_basis": "Honesty and respect for stakeholder autonomy through informed decision-making",
            "application_context": ["Report writing", "Public communications", "Client advisement"],
            "operationalization": "Through inclusion of all material facts, objective presentation, avoiding misrepresentation",
            "balancing_requirements": ["Client confidentiality", "Business interests", "Public relations objectives"],
            "examples_from_case": ["Omitting session details and timing", "Claiming community support without evidence"],
            "source_text": "Firm DBA provided a report that omitted details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted"
        }
    ],
    "principle_individuals": [
        {
            "identifier": "PublicWelfare_Primary_Canon",
            "principle_class": "Public Welfare Principle",
            "concrete_expression": "The most fundamental and primary Canon of the Code is to hold paramount the safety, health, and welfare of the public",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Firm DBA's obligations", "Engineer M's responsibilities"],
            "interpretation": "Public welfare overrides business considerations and applies even to non-engineering services",
            "source_text": "The most fundamental and primary Canon of the Code is to hold paramount the safety, health, and welfare of the public",
            "balancing_with": ["Business interests", "Client loyalty"],
            "tension_resolution": "Public welfare takes absolute precedence",
            "case_relevance": "Establishes that Code applies to Firm DBA despite providing PR services"
        },
        {
            "identifier": "Integrity_Professional_Behavior",
            "principle_class": "Integrity Principle",
            "concrete_expression": "professional behavior requires adherence to the highest principles of ethical conduct",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Firm DBA's business dealings"],
            "interpretation": "Integrity extends beyond technical engineering to all professional activities",
            "source_text": "The Preamble of the Code of states that professional behavior requires adherence to the highest principles of ethical conduct",
            "balancing_with": ["Business efficiency", "Client demands"],
            "tension_resolution": "Ethical conduct cannot be compromised for business purposes",
            "case_relevance": "Supports application of Code to PR services by engineering firm"
        },
        {
            "identifier": "Transparency_Truthful_Reporting",
            "principle_class": "Transparency Principle",
            "concrete_expression": "issuing statements in an objective and truthful manner",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Firm DBA's report on public sessions"],
            "interpretation": "Reports must include all material facts for informed decision-making",
            "source_text": "These actions likely violated the NSPE Code of Ethics (Code) regarding issuing statements in an objective and truthful manner, deceptive acts, misrepresentation of fact, and omitting a material fact",
            "balancing_with": ["Client preferences", "Project advocacy"],
            "tension_resolution": "Truth and completeness override client desires for favorable presentation",
            "case_relevance": "Central to evaluating Firm DBA's ethical violations"
        },
        {
            "identifier": "PublicWelfare_Engineer_M_Duty",
            "principle_class": "Public Welfare Principle",
            "concrete_expression": "Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineer M's response to misleading report"],
            "interpretation": "Individual engineers must act when public welfare is threatened by misleading information",
            "source_text": "Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public",
            "balancing_with": ["Business relationships", "Employer loyalty"],
            "tension_resolution": "Public welfare requires challenging the misleading report",
            "case_relevance": "Establishes Engineer M's obligation to act"
        },
        {
            "identifier": "Transparency_Informed_Decision",
            "principle_class": "Transparency Principle",
            "concrete_expression": "A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare",
            "invoked_by": ["Board of Ethical Review", "Reference to BER Case 21-7"],
            "applied_to": ["Completeness of public consultation report"],
            "interpretation": "Transparency requires inclusion of all relevant information for stakeholder decision-making",
            "source_text": "A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare",
            "balancing_with": ["Report brevity", "Favorable presentation"],
            "tension_resolution": "Complete information takes precedence over simplified messaging",
            "case_relevance": "Supports finding that omissions violate ethical obligations"
        },
        {
            "identifier": "Integrity_Business_Association",
            "principle_class": "Integrity Principle",
            "concrete_expression": "they shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineer M's continued involvement with project"],
            "interpretation": "Professional integrity requires disassociation from dishonest practices",
            "source_text": "they shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise as stated in Code section II.1.d",
            "balancing_with": ["Employment security", "Project continuity"],
            "tension_resolution": "Integrity requires challenging or withdrawing from dishonest ventures",
            "case_relevance": "Guides Engineer M's required response to misleading report"
        },
        {
            "identifier": "Competence_Advisory_Duty",
            "principle_class": "Competence Principle",
            "concrete_expression": "advise their clients or employers when they believe a project will not be successful",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineer M's obligation to warn about project risks"],
            "interpretation": "Professional competence includes duty to warn of likely failure",
            "source_text": "Engineer M has an additional obligation to advise their clients or employers when they believe a project will not be successful as stated in Code section III.1.b",
            "balancing_with": ["Optimistic project promotion", "Employer preferences"],
            "tension_resolution": "Honest assessment overrides desire for positive messaging",
            "case_relevance": "Requires Engineer M to warn about consequences of misleading report"
        }
    ]
}
```
Obligations Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for obligations (professional duties and requirements). Based on the literature: - Obligations are CONCRETE PROFESSIONAL DUTIES derived from abstract principles (Hallamaa & Kalliokoski 2022) - They specify what professionals MUST, SHOULD, or MUST NOT do (Dennis et al. 2016) - Obligations have deontic force and are enforceable (Wooldridge & Jennings 1995) - They operationalize principles in specific contexts (Kong et al. 2020) Your task is to: 1. Identify NEW OBLIGATION CLASSES not in the existing ontology 2. Extract SPECIFIC OBLIGATION INDIVIDUALS from the case EXISTING OBLIGATIONS IN ONTOLOGY (check if your identified obligations match these before creating new classes): - Attribution Obligation: Duty to properly cite and acknowledge all sources, tools, and methods used in creating professional deliverables - Collegial Obligation: Duties toward professional peers including respect, fairness, and credit for work - Competence Obligation: Requirement to perform services only in areas of competence (NSPE II.2) - Conditional Obligation: Obligations that apply only when specific conditions are met - Confidentiality Obligation: Duty to protect confidential information of clients or employers (NSPE III.4) - Defeasible Obligation: Obligations that admit justified exceptions under specified conditions (Ganascia 2007) - Disclosure Obligation: Requirement to inform stakeholders about conflicts, limitations, or risks (NSPE II.3.a) - Ethical Obligation: Obligations arising from ethical principles beyond legal requirements - Legal Obligation: Obligations arising from legal requirements and regulations - Mandatory Obligation: Obligations that MUST be fulfilled (deontic force: mandatory) - Obligation: An information content entity expressing required actions or behaviors in professional contexts. This is the O component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Prima Facie Obligation: Obligations that hold at first appearance but may be overridden by stronger duties (Anderson & Anderson) - Professional Obligation: A duty or responsibility arising from professional role or standards - Quality Assurance Obligation: Requirement to implement appropriate review and verification processes for all professional deliverables before submission - Reporting Obligation: Duty to report violations or unsafe conditions to appropriate authorities - Responsible Charge Obligation: Duty to maintain active engagement and personal decision-making authority throughout engineering process from conception to completion - Safety Obligation: Duty to hold paramount the safety, health, and welfare of the public (NSPE I.1) - Technology Competence Obligation: Requirement to understand and verify the capabilities, limitations, and risks of technological tools used in professional practice - Technology Verification Obligation: Requirement to thoroughly verify and validate outputs from technological tools including AI before incorporating them into professional work Analyze this discussion section: The overriding issue for the Board of Ethical Review (BER) to consider in this case is that of the actions of Firm DBA. The ethical requirements of Firm DBA must be clarified before establishing what actions are required by Engineer M. As stated, Firm DBA provided a report that omitted details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted. Additionally, Firm DBA’s report claimed Community P supported the project, without any evidence to support that claim. These actions likely violated the NSPE Code of Ethics ( Code) regarding issuing statements in an objective and truthful manner, deceptive acts, misrepresentation of fact, and omitting a material fact However, does the Code apply to Firm DBA? If the individuals most heavily involved in the project at Firm DBA are Certified Public Relations Professionals, they would be held to a code of ethics that provides for honest and truthful conduct. However, the BER will not comment on these potential obligations, as it is beyond the BER’s duties to review other codes. In BER Case 60-3 , the facts indicated that an engineering firm was providing sub-professional services and, because of that, the firm was not required to abide by the provisions of the Canons of Ethics and Rules of Professional Conduct. The conclusion by the BER in BER Case 60-3 was that the Canons and Rules did not apply. However, the Code has been revised since that time. The most fundamental and primary Canon of the Code is to hold paramount the safety, health, and welfare of the public. The facts in this case state that Firm DBA has licensed professional engineers in charge or in supervisory roles of all departments in the firm as well as ownership. It would be difficult to believe that through their duties as licensed professional engineers, the Code would be irrelevant to the Firm’s business dealings simply because the services being provided were not engineering from a design, calculation, or engineering judgment perspective but were confined to communication and public relation services. The Preamble of the Code of states that professional behavior requires adherence to the highest principles of ethical conduct. Therefore, the Code applies to Firm DBA. BER Case 98-2 addressed the ethical concerns of an international NSPE member that encountered separate and conflicting legal and ethical issues working in a county other than the U.S. In that case the BER determined that the engineer was bound by the Code and stated that “it would be a major error for NSPE to apply one standard of conduct to one set of NSPE members and another standard of conduct to another set of NSPE members.” Although that case was based on geographical concerns rather than the type of services provided, it was determined that the Code applied to members universally. In BER Case 88-6 , Engineer A had the responsibility for a city’s waste disposal plant and is also directly responsible to City Administrator C. Engineer A informed City Administrator C of the inadequacy of the disposal plant in a certain potential scenario. City Administrator C told Engineer A to discuss this matter only with him and, subsequentially, removed Engineer A from responsibility of the disposal plant. Engineer A took no further action. The critical scenario did, in fact, happen and a release of partially-treated wastewater occurred. The BER found that Engineer A did not fulfill ethical obligations of holding paramount the safety, health, and welfare of the public. As in this case, Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public. In BER Case 09-10 , Engineer A owned ABC Engineering in State P. Engineer X owned XYZ Engineering in State Q. Engineer X was retained to provide engineering services for Client L located in State P for a project in State P. Client L was a former client of Engineer A’s firm. Engineer A learned that XYZ Engineering did not have a current certificate of authority to practice engineering in State P. The question to the BER was to evaluate what Engineer A’s ethical obligations would be under these facts. The BER found that Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question. The BER further found that if Engineer A was not sufficiently satisfied with Engineer X’s explanation, Engineer A may be required to report this matter to the state engineering licensure board. In BER Case 21-7 , the question put to the BER was as follows: should an Engineer include information about the utility generation mix and rolling blackouts in the report to an organization? The BER found that as a registered professional, that Engineer was obliged to include relevant and pertinent information in a report to the organization. A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare. Likewise, in this case, pertinent information was missing from the report. By this reasoning, Engineer M not only has the right to challenge the validity of the DBA report but also must consider their involvement in the project as they shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise as stated in Code section II.1.d. The result of going forward with the project could also have disastrous consequences. If the facts come out later that relevant information was not disclosed in the report, the impact of such could be very negative. Again, Engineer M has an additional obligation to advise their clients or employers when they believe a project will not be successful as stated in Code section III.1.b. As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code. The licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved in these discussions as they have the ultimate responsibility to see that ethical practices are followed. Should Firm DBA acknowledge their ethical obligations after being confronted by Engineer M, a more immediate resolution to the issues may be realized and Firm DBA could correct the discrepancies. A more unfavorable result would be anticipated if Firm DBA takes the position that it performed the work under the direction of the City and are, therefore, unwilling to make the corrections. Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved. After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board. Although seemingly extreme, reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future. 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-19 19:01
LLM Response
```json
{
  "new_obligation_classes": [
    {
      "label": "Confrontation Obligation",
      "definition": "Duty to directly confront and address unethical conduct with the responsible party before escalating to authorities",
      "derived_from_principle": "Professional Responsibility",
      "duty_type": "professional",
      "enforcement_mechanism": "Professional conduct review and peer accountability",
      "violation_consequences": "Failure to address known violations, potential complicity in unethical conduct",
      "examples_from_case": ["Engineer M should confer immediately with Firm DBA", "Engineer A should communicate with Engineer X to obtain clarification"],
      "source_text": "the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA",
      "confidence": 0.85,
      "reasoning": "This represents a procedural duty to attempt direct resolution before escalation, distinct from reporting obligations"
    },
    {
      "label": "Dissociation Obligation",
      "definition": "Duty to withdraw from or refuse association with entities engaged in fraudulent or dishonest practices",
      "derived_from_principle": "Integrity",
      "duty_type": "ethical",
      "enforcement_mechanism": "Professional licensing board review and sanctions",
      "violation_consequences": "Reputational damage, potential loss of license, complicity in fraud",
      "examples_from_case": ["Engineer M must consider their involvement in the project", "shall not permit use of name with fraudulent enterprise"],
      "source_text": "shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent",
      "confidence": 0.90,
      "reasoning": "Goes beyond disclosure to require active dissociation from unethical entities, not covered by existing obligation classes"
    },
    {
      "label": "Completeness Obligation",
      "definition": "Duty to include all relevant and pertinent information necessary for informed decision-making in professional reports",
      "derived_from_principle": "Truthfulness",
      "duty_type": "professional",
      "enforcement_mechanism": "Professional standards review and client complaints",
      "violation_consequences": "Invalid reports, uninformed decisions, potential public harm",
      "examples_from_case": ["Report omitted details about sessions", "Engineer was obliged to include relevant information"],
      "source_text": "Engineer was obliged to include relevant and pertinent information in a report to the organization",
      "confidence": 0.88,
      "reasoning": "Distinct from disclosure obligations as it focuses on completeness of technical content rather than conflicts or risks"
    }
  ],
  "obligation_individuals": [
    {
      "identifier": "FirmDBA_Truthful_Statements",
      "obligation_class": "Disclosure Obligation",
      "obligated_party": "Firm DBA",
      "obligation_statement": "Issue statements in an objective and truthful manner without omitting material facts",
      "derived_from": "NSPE Code of Ethics",
      "enforcement_context": "State engineering licensure board review",
      "temporal_scope": "During report preparation and submission",
      "compliance_status": "unmet",
      "case_context": "Firm DBA omitted session details and falsely claimed community support",
      "source_text": "likely violated the NSPE Code of Ethics regarding issuing statements in an objective and truthful manner",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerM_Confront_FirmDBA",
      "obligation_class": "Confrontation Obligation",
      "obligated_party": "Engineer M",
      "obligation_statement": "Confer immediately with Firm DBA and state objections regarding ethical violations",
      "derived_from": "BER Recommendation",
      "enforcement_context": "Professional peer review process",
      "temporal_scope": "Immediately upon discovering violations",
      "compliance_status": "pending",
      "case_context": "Engineer M must directly address concerns with Firm DBA before escalation",
      "source_text": "the BER recommends Engineer M to confer immediately with Firm DBA",
      "is_existing_class": false,
      "confidence": 0.92
    },
    {
      "identifier": "EngineerM_Safety_Paramount",
      "obligation_class": "Safety Obligation",
      "obligated_party": "Engineer M",
      "obligation_statement": "Hold paramount the safety, health, and welfare of the public",
      "derived_from": "NSPE Code Canon I",
      "enforcement_context": "Professional licensing board enforcement",
      "temporal_scope": "Continuous throughout professional practice",
      "compliance_status": "pending",
      "case_context": "Engineer M must ensure public welfare despite misleading report",
      "source_text": "Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public",
      "is_existing_class": true,
      "confidence": 0.98
    },
    {
      "identifier": "EngineerM_Dissociate_Fraud",
      "obligation_class": "Dissociation Obligation",
      "obligated_party": "Engineer M",
      "obligation_statement": "Not permit use of name or associate with any firm believed to be engaged in fraudulent enterprise",
      "derived_from": "NSPE Code II.1.d",
      "enforcement_context": "Professional conduct review",
      "temporal_scope": "Upon discovery of fraudulent behavior",
      "compliance_status": "pending",
      "case_context": "Engineer M must consider withdrawing from project if Firm DBA continues unethical practices",
      "source_text": "shall not permit the use of their name or associate in business ventures with any person or firm",
      "is_existing_class": false,
      "confidence": 0.89
    },
    {
      "identifier": "EngineerM_Report_Board",
      "obligation_class": "Reporting Obligation",
      "obligated_party": "Engineer M",
      "obligation_statement": "Report Firm DBA's actions to state engineering licensure board if corrections not made",
      "derived_from": "NSPE Code and BER precedent",
      "enforcement_context": "State licensure board investigation",
      "temporal_scope": "After unsuccessful attempts at direct resolution",
      "compliance_status": "pending",
      "case_context": "Conditional reporting if Firm DBA refuses to correct discrepancies",
      "source_text": "Engineer M must decide whether to report Firm DBA's actions to the state's engineering licensure board",
      "is_existing_class": true,
      "confidence": 0.87
    },
    {
      "identifier": "FirmDBA_Complete_Report",
      "obligation_class": "Completeness Obligation",
      "obligated_party": "Firm DBA",
      "obligation_statement": "Include all relevant information about session locations, times, and comment procedures in report",
      "derived_from": "NSPE Code - Truthfulness",
      "enforcement_context": "Client review and professional standards",
      "temporal_scope": "During report preparation",
      "compliance_status": "unmet",
      "case_context": "Firm DBA omitted critical details about public engagement sessions",
      "source_text": "Firm DBA provided a report that omitted details about where the sessions were held and at what time",
      "is_existing_class": false,
      "confidence": 0.91
    },
    {
      "identifier": "EngineerM_Advise_Client",
      "obligation_class": "Disclosure Obligation",
      "obligated_party": "Engineer M",
      "obligation_statement": "Advise clients when believing a project will not be successful",
      "derived_from": "NSPE Code III.1.b",
      "enforcement_context": "Professional standards review",
      "temporal_scope": "Upon discovery of project risks",
      "compliance_status": "pending",
      "case_context": "Engineer M must inform City about report deficiencies affecting project success",
      "source_text": "Engineer M has an additional obligation to advise their clients or employers when they believe a project will not be successful",
      "is_existing_class": true,
      "confidence": 0.93
    },
    {
      "identifier": "FirmDBA_Engineers_Supervision",
      "obligation_class": "Responsible Charge Obligation",
      "obligated_party": "Licensed PEs at Firm DBA",
      "obligation_statement": "Ensure ethical practices are followed in all firm activities under their supervision",
      "derived_from": "NSPE Code - Professional Responsibility",
      "enforcement_context": "Licensing board review of supervisory duties",
      "temporal_scope": "Continuous during supervisory roles",
      "compliance_status": "unmet",
      "case_context": "PE supervisors and owners failed to ensure ethical report preparation",
      "source_text": "they have the ultimate responsibility to see that ethical practices are followed",
      "is_existing_class": true,
      "confidence": 0.86
    }
  ]
}
```
Constraints Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for constraints (boundaries, limitations, and restrictions). Based on the literature: - Constraints are INVIOLABLE BOUNDARIES that limit acceptable actions (Dennis et al. 2016) - They differ from obligations by being restrictions rather than requirements - Constraints can be legal, physical, resource-based, or procedural - They define the space within which ethical decisions must be made Your task is to: 1. Identify NEW CONSTRAINT CLASSES not in the existing ontology 2. Extract SPECIFIC CONSTRAINT INDIVIDUALS from the case EXISTING CONSTRAINTS IN ONTOLOGY (check if your identified constraints match these before creating new classes): - Attribution Constraint: Requirements and limitations regarding the disclosure and citation of tools, methods, or sources used in professional work products - Competence Constraint: Boundaries defined by agent capabilities and technical limitations (Hallamaa & Kalliokoski 2022) - Confidentiality Constraint: Boundaries on information disclosure and privacy (Dennis et al. 2016) - Constraint: An information content entity expressing limitations or restrictions on professional actions or decisions. This is the Cs component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Defeasible Constraint: Constraints that admit justified exceptions under specified conditions (Ganascia 2007) - Ethical Constraint: Professional ethical boundaries beyond legal requirements (Benzmüller et al. 2020) - Inviolable Constraint: Absolute constraints that cannot be overridden under any circumstances (Dennis et al. 2016) - Jurisdictional Constraint: Boundaries of authority and geographical or organizational scope (Dennis et al. 2016) - Legal Constraint: Constraints arising from legal requirements and statutes that establish inviolable boundaries (Kroll 2020, Stenseke 2024) - Priority Constraint: Constraints establishing precedence when multiple requirements conflict (Scheutz & Malle 2014) - Procedural Constraint: Requirements for following specific processes or protocols (Furbach et al. 2014) - Regulatory Constraint: Constraints from regulatory bodies and professional standards organizations (Taddeo et al. 2024) - Resource Constraint: Limitations on available time, budget, materials, or human resources (Ganascia 2007) - Safety Constraint: Constraints ensuring safety requirements are met (Arkin 2008) - Technology Substitution Constraint: Boundaries preventing technology from replacing professional judgment and human oversight in critical decision-making Analyze this discussion section: The overriding issue for the Board of Ethical Review (BER) to consider in this case is that of the actions of Firm DBA. The ethical requirements of Firm DBA must be clarified before establishing what actions are required by Engineer M. As stated, Firm DBA provided a report that omitted details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted. Additionally, Firm DBA’s report claimed Community P supported the project, without any evidence to support that claim. These actions likely violated the NSPE Code of Ethics ( Code) regarding issuing statements in an objective and truthful manner, deceptive acts, misrepresentation of fact, and omitting a material fact However, does the Code apply to Firm DBA? If the individuals most heavily involved in the project at Firm DBA are Certified Public Relations Professionals, they would be held to a code of ethics that provides for honest and truthful conduct. However, the BER will not comment on these potential obligations, as it is beyond the BER’s duties to review other codes. In BER Case 60-3 , the facts indicated that an engineering firm was providing sub-professional services and, because of that, the firm was not required to abide by the provisions of the Canons of Ethics and Rules of Professional Conduct. The conclusion by the BER in BER Case 60-3 was that the Canons and Rules did not apply. However, the Code has been revised since that time. The most fundamental and primary Canon of the Code is to hold paramount the safety, health, and welfare of the public. The facts in this case state that Firm DBA has licensed professional engineers in charge or in supervisory roles of all departments in the firm as well as ownership. It would be difficult to believe that through their duties as licensed professional engineers, the Code would be irrelevant to the Firm’s business dealings simply because the services being provided were not engineering from a design, calculation, or engineering judgment perspective but were confined to communication and public relation services. The Preamble of the Code of states that professional behavior requires adherence to the highest principles of ethical conduct. Therefore, the Code applies to Firm DBA. BER Case 98-2 addressed the ethical concerns of an international NSPE member that encountered separate and conflicting legal and ethical issues working in a county other than the U.S. In that case the BER determined that the engineer was bound by the Code and stated that “it would be a major error for NSPE to apply one standard of conduct to one set of NSPE members and another standard of conduct to another set of NSPE members.” Although that case was based on geographical concerns rather than the type of services provided, it was determined that the Code applied to members universally. In BER Case 88-6 , Engineer A had the responsibility for a city’s waste disposal plant and is also directly responsible to City Administrator C. Engineer A informed City Administrator C of the inadequacy of the disposal plant in a certain potential scenario. City Administrator C told Engineer A to discuss this matter only with him and, subsequentially, removed Engineer A from responsibility of the disposal plant. Engineer A took no further action. The critical scenario did, in fact, happen and a release of partially-treated wastewater occurred. The BER found that Engineer A did not fulfill ethical obligations of holding paramount the safety, health, and welfare of the public. As in this case, Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public. In BER Case 09-10 , Engineer A owned ABC Engineering in State P. Engineer X owned XYZ Engineering in State Q. Engineer X was retained to provide engineering services for Client L located in State P for a project in State P. Client L was a former client of Engineer A’s firm. Engineer A learned that XYZ Engineering did not have a current certificate of authority to practice engineering in State P. The question to the BER was to evaluate what Engineer A’s ethical obligations would be under these facts. The BER found that Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question. The BER further found that if Engineer A was not sufficiently satisfied with Engineer X’s explanation, Engineer A may be required to report this matter to the state engineering licensure board. In BER Case 21-7 , the question put to the BER was as follows: should an Engineer include information about the utility generation mix and rolling blackouts in the report to an organization? The BER found that as a registered professional, that Engineer was obliged to include relevant and pertinent information in a report to the organization. A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare. Likewise, in this case, pertinent information was missing from the report. By this reasoning, Engineer M not only has the right to challenge the validity of the DBA report but also must consider their involvement in the project as they shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise as stated in Code section II.1.d. The result of going forward with the project could also have disastrous consequences. If the facts come out later that relevant information was not disclosed in the report, the impact of such could be very negative. Again, Engineer M has an additional obligation to advise their clients or employers when they believe a project will not be successful as stated in Code section III.1.b. As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code. The licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved in these discussions as they have the ultimate responsibility to see that ethical practices are followed. Should Firm DBA acknowledge their ethical obligations after being confronted by Engineer M, a more immediate resolution to the issues may be realized and Firm DBA could correct the discrepancies. A more unfavorable result would be anticipated if Firm DBA takes the position that it performed the work under the direction of the City and are, therefore, unwilling to make the corrections. Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved. After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board. Although seemingly extreme, reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future. 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-19 19:01
LLM Response
```json
{
  "new_constraint_classes": [
    {
      "label": "Professional Association Constraint",
      "definition": "Limitations on actions based on professional association with entities engaged in questionable practices",
      "constraint_type": "procedural",
      "flexibility": "hard",
      "violation_impact": "Damage to professional reputation and potential ethics violations",
      "mitigation_possible": "Can be mitigated by disassociating from the entity or correcting the practices",
      "examples_from_case": ["Cannot associate with firms engaged in fraudulent enterprises", "Must not permit use of name with dishonest ventures"],
      "source_text": "shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise",
      "confidence": 0.85,
      "reasoning": "This constraint specifically limits professional associations and partnerships, distinct from general ethical constraints"
    },
    {
      "label": "Reporting Completeness Constraint",
      "definition": "Boundaries requiring inclusion of all material facts and relevant information in professional reports",
      "constraint_type": "procedural",
      "flexibility": "hard",
      "violation_impact": "Misleading stakeholders and potential harm to public welfare",
      "mitigation_possible": "Can be corrected by amending reports to include missing information",
      "examples_from_case": ["Cannot omit material facts", "Must include relevant and pertinent information"],
      "source_text": "A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare",
      "confidence": 0.9,
      "reasoning": "Distinct from general ethical constraints as it specifically addresses completeness requirements in professional documentation"
    }
  ],
  "constraint_individuals": [
    {
      "identifier": "DBA_Code_Applicability_Constraint",
      "constraint_class": "Jurisdictional Constraint",
      "constrained_entity": "Firm DBA",
      "constraint_statement": "Must adhere to NSPE Code of Ethics due to having licensed professional engineers in supervisory and ownership roles",
      "source": "NSPE Code of Ethics",
      "enforcement_mechanism": "State engineering licensure board oversight",
      "temporal_scope": "Continuous during all business operations",
      "severity": "critical",
      "case_context": "Despite providing PR services, firm is bound by engineering ethics code",
      "source_text": "licensed professional engineers in charge or in supervisory roles of all departments in the firm as well as ownership",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "Engineer_M_Association_Constraint",
      "constraint_class": "Professional Association Constraint",
      "constrained_entity": "Engineer M",
      "constraint_statement": "Cannot permit use of name or associate with Firm DBA if they believe it is engaged in fraudulent enterprise",
      "source": "NSPE Code section II.1.d",
      "enforcement_mechanism": "Professional ethics review and potential licensure board action",
      "temporal_scope": "During project involvement",
      "severity": "critical",
      "case_context": "Engineer M must consider disassociation if DBA doesn't correct report discrepancies",
      "source_text": "shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "DBA_Report_Completeness_Constraint",
      "constraint_class": "Reporting Completeness Constraint",
      "constrained_entity": "Firm DBA",
      "constraint_statement": "Cannot omit material facts including session locations, times, and acceptance of written comments",
      "source": "NSPE Code regarding truthful statements",
      "enforcement_mechanism": "Ethics review and potential corrective action",
      "temporal_scope": "During report preparation and submission",
      "severity": "major",
      "case_context": "DBA's report violated this by omitting critical details about public sessions",
      "source_text": "omitted details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments",
      "is_existing_class": false,
      "confidence": 0.95
    },
    {
      "identifier": "Engineer_M_Reporting_Obligation_Constraint",
      "constraint_class": "Procedural Constraint",
      "constrained_entity": "Engineer M",
      "constraint_statement": "Must follow escalation procedure: confer with DBA, then City, then potentially report to licensure board",
      "source": "BER recommendations and precedent cases",
      "enforcement_mechanism": "Professional ethics standards",
      "temporal_scope": "Sequential steps following discovery of issues",
      "severity": "major",
      "case_context": "Engineer M must follow specific steps before reporting to authorities",
      "source_text": "Engineer M to confer immediately with Firm DBA...Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City",
      "is_existing_class": true,
      "confidence": 0.85
    },
    {
      "identifier": "DBA_Truthfulness_Constraint",
      "constraint_class": "Ethical Constraint",
      "constrained_entity": "Firm DBA",
      "constraint_statement": "Cannot make unsupported claims about community support without evidence",
      "source": "NSPE Code regarding objective and truthful statements",
      "enforcement_mechanism": "Ethics review and potential sanctions",
      "temporal_scope": "During all professional communications",
      "severity": "critical",
      "case_context": "DBA claimed Community P supported project without evidence",
      "source_text": "Firm DBA's report claimed Community P supported the project, without any evidence to support that claim",
      "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 discussion section: The overriding issue for the Board of Ethical Review (BER) to consider in this case is that of the actions of Firm DBA. The ethical requirements of Firm DBA must be clarified before establishing what actions are required by Engineer M. As stated, Firm DBA provided a report that omitted details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted. Additionally, Firm DBA’s report claimed Community P supported the project, without any evidence to support that claim. These actions likely violated the NSPE Code of Ethics ( Code) regarding issuing statements in an objective and truthful manner, deceptive acts, misrepresentation of fact, and omitting a material fact However, does the Code apply to Firm DBA? If the individuals most heavily involved in the project at Firm DBA are Certified Public Relations Professionals, they would be held to a code of ethics that provides for honest and truthful conduct. However, the BER will not comment on these potential obligations, as it is beyond the BER’s duties to review other codes. In BER Case 60-3 , the facts indicated that an engineering firm was providing sub-professional services and, because of that, the firm was not required to abide by the provisions of the Canons of Ethics and Rules of Professional Conduct. The conclusion by the BER in BER Case 60-3 was that the Canons and Rules did not apply. However, the Code has been revised since that time. The most fundamental and primary Canon of the Code is to hold paramount the safety, health, and welfare of the public. The facts in this case state that Firm DBA has licensed professional engineers in charge or in supervisory roles of all departments in the firm as well as ownership. It would be difficult to believe that through their duties as licensed professional engineers, the Code would be irrelevant to the Firm’s business dealings simply because the services being provided were not engineering from a design, calculation, or engineering judgment perspective but were confined to communication and public relation services. The Preamble of the Code of states that professional behavior requires adherence to the highest principles of ethical conduct. Therefore, the Code applies to Firm DBA. BER Case 98-2 addressed the ethical concerns of an international NSPE member that encountered separate and conflicting legal and ethical issues working in a county other than the U.S. In that case the BER determined that the engineer was bound by the Code and stated that “it would be a major error for NSPE to apply one standard of conduct to one set of NSPE members and another standard of conduct to another set of NSPE members.” Although that case was based on geographical concerns rather than the type of services provided, it was determined that the Code applied to members universally. In BER Case 88-6 , Engineer A had the responsibility for a city’s waste disposal plant and is also directly responsible to City Administrator C. Engineer A informed City Administrator C of the inadequacy of the disposal plant in a certain potential scenario. City Administrator C told Engineer A to discuss this matter only with him and, subsequentially, removed Engineer A from responsibility of the disposal plant. Engineer A took no further action. The critical scenario did, in fact, happen and a release of partially-treated wastewater occurred. The BER found that Engineer A did not fulfill ethical obligations of holding paramount the safety, health, and welfare of the public. As in this case, Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public. In BER Case 09-10 , Engineer A owned ABC Engineering in State P. Engineer X owned XYZ Engineering in State Q. Engineer X was retained to provide engineering services for Client L located in State P for a project in State P. Client L was a former client of Engineer A’s firm. Engineer A learned that XYZ Engineering did not have a current certificate of authority to practice engineering in State P. The question to the BER was to evaluate what Engineer A’s ethical obligations would be under these facts. The BER found that Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question. The BER further found that if Engineer A was not sufficiently satisfied with Engineer X’s explanation, Engineer A may be required to report this matter to the state engineering licensure board. In BER Case 21-7 , the question put to the BER was as follows: should an Engineer include information about the utility generation mix and rolling blackouts in the report to an organization? The BER found that as a registered professional, that Engineer was obliged to include relevant and pertinent information in a report to the organization. A report that does not contain relevant information will not help stakeholders make an informed decision and does not protect public safety, health, and welfare. Likewise, in this case, pertinent information was missing from the report. By this reasoning, Engineer M not only has the right to challenge the validity of the DBA report but also must consider their involvement in the project as they shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise as stated in Code section II.1.d. The result of going forward with the project could also have disastrous consequences. If the facts come out later that relevant information was not disclosed in the report, the impact of such could be very negative. Again, Engineer M has an additional obligation to advise their clients or employers when they believe a project will not be successful as stated in Code section III.1.b. As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code. The licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved in these discussions as they have the ultimate responsibility to see that ethical practices are followed. Should Firm DBA acknowledge their ethical obligations after being confronted by Engineer M, a more immediate resolution to the issues may be realized and Firm DBA could correct the discrepancies. A more unfavorable result would be anticipated if Firm DBA takes the position that it performed the work under the direction of the City and are, therefore, unwilling to make the corrections. Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved. After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board. Although seemingly extreme, reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future. 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-19 19:02
LLM Response
```json
{
  "new_capability_classes": [
    {
      "label": "Ethical Challenge Capability",
      "definition": "The competency to identify and challenge unethical practices or misrepresentations by colleagues, firms, or clients",
      "capability_type": "ethical",
      "norm_competence_related": "Enables professionals to uphold integrity standards and prevent fraudulent or dishonest practices",
      "skill_level": "advanced",
      "acquisition_method": "Professional experience, ethics training, case study analysis",
      "examples_from_case": ["Engineer M's right and duty to challenge DBA's report validity", "Confronting firms about ethical obligations"],
      "source_text": "Engineer M not only has the right to challenge the validity of the DBA report but also must consider their involvement in the project",
      "confidence": 0.9,
      "reasoning": "Distinct from existing capabilities - focuses on actively confronting and challenging unethical behavior rather than just compliance or evaluation"
    },
    {
      "label": "Stakeholder Communication Capability",
      "definition": "The competency to effectively communicate ethical concerns and obligations to multiple stakeholders including firms, clients, and regulatory bodies",
      "capability_type": "communicative",
      "norm_competence_related": "Enables professionals to escalate ethical issues through appropriate channels and ensure all parties understand their obligations",
      "skill_level": "advanced",
      "acquisition_method": "Professional development, conflict resolution training, experience in multi-stakeholder environments",
      "examples_from_case": ["Conferring with Firm DBA", "Discussion with City officials", "Potential reporting to licensure board"],
      "source_text": "Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations",
      "confidence": 0.85,
      "reasoning": "Goes beyond technical writing to include complex ethical communication across organizational boundaries and hierarchies"
    },
    {
      "label": "Material Fact Assessment Capability",
      "definition": "The competency to identify and evaluate the completeness and truthfulness of information in professional reports and statements",
      "capability_type": "analytical",
      "norm_competence_related": "Enables professionals to ensure objective and truthful reporting, preventing deception through omission",
      "skill_level": "intermediate",
      "acquisition_method": "Critical thinking training, report review experience, professional standards education",
      "examples_from_case": ["Identifying omitted session details", "Recognizing unsupported claims about community support"],
      "source_text": "Firm DBA provided a report that omitted details about where the sessions were held and at what time of day the sessions were held",
      "confidence": 0.8,
      "reasoning": "Specific to identifying material omissions and misrepresentations, distinct from general AI tool evaluation or technical writing"
    }
  ],
  "capability_individuals": [
    {
      "identifier": "EngineerM_EthicalChallenge",
      "capability_class": "Ethical Challenge Capability",
      "possessed_by": "Engineer M",
      "capability_statement": "Challenge the validity of Firm DBA's report and confront ethical violations",
      "demonstrated_through": "Professional obligation to uphold Code of Ethics",
      "proficiency_level": "advanced",
      "enables_obligations": "Preventing association with fraudulent enterprises, protecting public welfare",
      "temporal_aspect": "Upon discovering report discrepancies",
      "case_context": "Must challenge DBA's misrepresentations and omissions in public engagement report",
      "source_text": "Engineer M not only has the right to challenge the validity of the DBA report but also must consider their involvement",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "FirmDBA_ResponsibleCharge",
      "capability_class": "Responsible Charge Capability",
      "possessed_by": "Licensed PEs at Firm DBA",
      "capability_statement": "Maintain supervisory control and ethical oversight of firm operations",
      "demonstrated_through": "Supervisory and ownership roles in the firm",
      "proficiency_level": "expert",
      "enables_obligations": "Ensuring ethical practices are followed throughout the firm",
      "temporal_aspect": "Continuous during all business operations",
      "case_context": "Licensed PEs in charge of departments must ensure ethical conduct even in non-engineering services",
      "source_text": "licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved",
      "is_existing_class": true,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerM_StakeholderCommunication",
      "capability_class": "Stakeholder Communication Capability",
      "possessed_by": "Engineer M",
      "capability_statement": "Communicate ethical concerns to Firm DBA, City officials, and potentially licensure board",
      "demonstrated_through": "Recommended escalation process in the case",
      "proficiency_level": "advanced",
      "enables_obligations": "Ensuring all parties understand ethical obligations and consequences",
      "temporal_aspect": "Sequential escalation as needed",
      "case_context": "Must navigate complex communication with multiple stakeholders about ethical violations",
      "source_text": "Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA)",
      "is_existing_class": false,
      "confidence": 0.8
    },
    {
      "identifier": "FirmDBA_MaterialFactAssessment",
      "capability_class": "Material Fact Assessment Capability",
      "possessed_by": "Firm DBA",
      "capability_statement": "Identify and include all material facts in public engagement reports",
      "demonstrated_through": "Failed demonstration - omitted critical information",
      "proficiency_level": "basic",
      "enables_obligations": "Providing objective and truthful statements without material omissions",
      "temporal_aspect": "During report preparation",
      "case_context": "Failed to include session timing, location, and comment acceptance details",
      "source_text": "omitted details about where the sessions were held and at what time of day...not identifying that written comments were not accepted",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerM_RegulatoryCompliance",
      "capability_class": "Regulatory Compliance Capability",
      "possessed_by": "Engineer M",
      "capability_statement": "Report violations to state engineering licensure board when necessary",
      "demonstrated_through": "Understanding of reporting obligations under the Code",
      "proficiency_level": "intermediate",
      "enables_obligations": "Preventing future violations and upholding professional standards",
      "temporal_aspect": "After exhausting direct resolution attempts",
      "case_context": "May need to report Firm DBA to state board if corrections aren't made",
      "source_text": "reporting Firm DBA to the state's engineering licensure board may be necessary to prevent similar situations",
      "is_existing_class": true,
      "confidence": 0.75
    }
  ]
}
```