Step 2: Normative Requirements Pass (Facts Section)

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

Sharing As-Built Drawings
Step 2 of 5

Facts Section

Section Content:
Facts:
Engineer D is a fire protection engineer in the public sector and works for a state agency.
The agency advertises for bids on major building renovation projects; the bid documents made no reference to existing as-builts or drawings for the bidders’ or awarded contractor’s use.
After bids are opened and contracts are awarded, the successful sprinkler contractor asks Engineer D for as-built drawings of the existing sprinkler system.
D provides the drawings.
Over time, sprinkler contractors who received as-built drawings from Engineer D in the past begin to ask for these documents when projects are advertised, before bids are turned in.
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: Acting as a faithful agent or trustee for a client or employer is an obligation for any engineer and is one of the fundamental canons in NSPE’s code of ethics. Engineer D’s efforts to make as-built drawings available for reference appears to be acting in the employer’s best interest. Providing more information about existing conditions should help produce a better design. When D provides as-built drawings after bid openings, is employer information being shared without consent? In addition, if information is shared selectively with contractors before bids are opened; will D’s actions influence the award of a contract? BER Case 82-2 is a useful starting point in this discussion. In that case, an engineer offers a service providing inspection of residences to prospective homeowners. For the situation in question, the engineer produced a report for their client and provided a copy to the real estate firm handling the home sale. The client complained the engineer acted unethically by providing a copy to the real estate firm and caused harm by lessening their bargaining position with the owners of the residence. Case discussion notes there was no transmission of the client’s confidential information by the engineer (presumably the real estate firm could have had the home inspected and gained the same knowledge). The BER states “we read into this case an assumption that Engineer A acted without thought or consideration of any ulterior motive; that he, as a matter of course, considered it right and proper to make his findings known to all interested parties …” The board exonerated the engineer of substantial or deliberate wrongdoing, but determined it was incorrect to not recognize the confidentiality of a client relationship. The engineer acted unethically in submitting a copy of the home inspection report to the real estate agent. BER Case 15-7 involves the ubiquitous Engineer A working for Firm X. A’s firm is retained by a municipality to design a water treatment facility. A believes the project can benefit from a discussion of constructability issues, and is tempted to begin a discussion with local Contractor B. A is concerned that potential discussions with B will provide an unfair advantage. The board advised that “rather than consulting solely with Contractor B, Engineer A could have conducted a publically (sic) advertised constructability meeting, inviting all interested contractors to provide Engineer A with the input necessary to achieve a better design and construction outcome. Such a process would avoid any appearance of favoritism toward one particular contractor, serve the client’s interests, and gain the benefit of broader input to improve the design and construction process.” The above summary of case history focused on engineers providing or being in position to have access to information not generally available to others. BER Case 16-3 involves Engineer A who receives a submittal by a highly qualified engineering firm (Firm B) a few hours after a well-publicized deadline. In 16-3, “the Board is concerned that allowing Firm B’s submittal to be considered would open the procurement to challenge or at the very least create a climate in which non-adherence to public procurement rules and policies are tolerated. Such a situation would not reflect well on that process, the city, or the engineering profession.” The conclusion was that A should return the submittal to firm B, unopened and explain that the bid/submittal was received late. Returning to the case at hand, Engineer D seems to be acting without what was termed in case 82-2, an ulterior motive - D’s desire is to make information available to improve designs. Even so, informally sharing as-built information is troubling. Working through informal mechanisms on public projects can give the appearance of impropriety or favoritism. Engineer D can advise that as-built drawings are available, but D should direct subcontractors to request them as part of the standard project process. D should not share documents on their own initiative or without formal permission. Because as-builts are useful and can help improve designs, Engineer D should initiate a process to include as-built drawings, when available, on projects going forward. It would be unethical for D to share as-builts with selected contractors pre-bid. Respond with valid JSON in this format: { "new_principle_classes": [ { "label": "Sustainable Development", "definition": "Principle that engineering solutions must balance current needs with long-term environmental and societal impacts", "abstract_nature": "Intergenerational justice and environmental stewardship", "extensional_examples": ["Green building design", "Renewable energy projects", "Resource conservation"], "value_basis": "Responsibility to future generations", "application_context": ["Infrastructure projects", "Environmental engineering", "Urban planning"], "operationalization": "Through environmental impact assessments, lifecycle analysis, sustainable design criteria", "balancing_requirements": ["Economic feasibility", "Immediate safety needs", "Client requirements"], "examples_from_case": ["Engineer considered long-term environmental impacts", "balanced immediate needs with sustainability"], "source_text": "Engineer considered long-term environmental impacts and balanced immediate needs with sustainability" } ], "principle_individuals": [ { "identifier": "PublicSafety_Case8_Facts", "principle_class": "Public Safety", "concrete_expression": "the safety of the public must be held paramount", "invoked_by": ["Engineer L"], "applied_to": ["stormwater management system design"], "interpretation": "Safety considerations override cost savings in drainage design", "source_text": "the safety of the public must be held paramount", "balancing_with": ["Cost Efficiency", "Client Interests"], "tension_resolution": "Safety takes precedence even if it increases project costs", "case_relevance": "Critical for evaluating adequacy of proposed drainage solution" } ] }
Saved: 2025-12-29 20:25
LLM Response
```json
{
    "new_principle_classes": [
        {
            "label": "Procedural Fairness",
            "definition": "Principle that professional processes must ensure equal treatment and avoid favoritism or unfair advantage in competitive situations",
            "abstract_nature": "Justice through impartial and transparent procedures",
            "extensional_examples": ["Public bidding processes", "Contractor selection", "Information disclosure during procurement"],
            "value_basis": "Equality of opportunity and impartial treatment",
            "application_context": ["Public procurement", "Competitive bidding", "Contract awards", "Professional selection processes"],
            "operationalization": "Through standardized procedures, public announcements, equal access to information, adherence to deadlines",
            "balancing_requirements": ["Efficiency", "Client benefit", "Design improvement", "Practical considerations"],
            "examples_from_case": ["avoid any appearance of favoritism toward one particular contractor", "create a climate in which non-adherence to public procurement rules and policies are tolerated"],
            "source_text": "avoid any appearance of favoritism toward one particular contractor, serve the client's interests, and gain the benefit of broader input"
        }
    ],
    "principle_individuals": [
        {
            "identifier": "FaithfulAgent_CaseD_Canon",
            "principle_class": "Loyalty",
            "concrete_expression": "Acting as a faithful agent or trustee for a client or employer is an obligation for any engineer and is one of the fundamental canons in NSPE's code of ethics",
            "invoked_by": ["NSPE Code", "Case narrative"],
            "applied_to": ["Engineer D's sharing of as-built drawings"],
            "interpretation": "Acting in employer's best interest by providing information to improve designs",
            "source_text": "Acting as a faithful agent or trustee for a client or employer is an obligation for any engineer and is one of the fundamental canons in NSPE's code of ethics",
            "balancing_with": ["Procedural Fairness", "Confidentiality"],
            "tension_resolution": "Must balance improving design quality with avoiding unauthorized information sharing",
            "case_relevance": "Central to evaluating whether D's actions serve employer interests appropriately"
        },
        {
            "identifier": "Confidentiality_Case82-2",
            "principle_class": "Confidentiality",
            "concrete_expression": "it was incorrect to not recognize the confidentiality of a client relationship",
            "invoked_by": ["BER in Case 82-2"],
            "applied_to": ["Sharing of home inspection report with real estate agent"],
            "interpretation": "Client information should not be shared without consent even if no ulterior motive exists",
            "source_text": "it was incorrect to not recognize the confidentiality of a client relationship",
            "balancing_with": ["Transparency", "Good intentions"],
            "tension_resolution": "Confidentiality obligations persist regardless of engineer's good intentions",
            "case_relevance": "Establishes precedent that information sharing requires client consent"
        },
        {
            "identifier": "ProceduralFairness_Case15-7",
            "principle_class": "Procedural Fairness",
            "concrete_expression": "avoid any appearance of favoritism toward one particular contractor, serve the client's interests, and gain the benefit of broader input",
            "invoked_by": ["BER in Case 15-7"],
            "applied_to": ["Constructability discussions with contractors"],
            "interpretation": "Public processes must provide equal opportunity to all potential contractors",
            "source_text": "avoid any appearance of favoritism toward one particular contractor, serve the client's interests, and gain the benefit of broader input to improve the design and construction process",
            "balancing_with": ["Design improvement", "Efficiency"],
            "tension_resolution": "Use public meetings rather than selective consultation to maintain fairness",
            "case_relevance": "Directly applicable to D's selective sharing of as-built drawings"
        },
        {
            "identifier": "ProceduralIntegrity_Case16-3",
            "principle_class": "Procedural Fairness",
            "concrete_expression": "allowing Firm B's submittal to be considered would open the procurement to challenge or at the very least create a climate in which non-adherence to public procurement rules and policies are tolerated",
            "invoked_by": ["BER in Case 16-3"],
            "applied_to": ["Late submittal acceptance"],
            "interpretation": "Strict adherence to procedural rules maintains integrity of public processes",
            "source_text": "allowing Firm B's submittal to be considered would open the procurement to challenge or at the very least create a climate in which non-adherence to public procurement rules and policies are tolerated",
            "balancing_with": ["Merit-based selection", "Practical considerations"],
            "tension_resolution": "Procedural integrity overrides consideration of submittal quality",
            "case_relevance": "Reinforces importance of formal processes in public projects"
        },
        {
            "identifier": "TransparencyAvoidance_CaseD",
            "principle_class": "Transparency",
            "concrete_expression": "Working through informal mechanisms on public projects can give the appearance of impropriety or favoritism",
            "invoked_by": ["Case analysis"],
            "applied_to": ["Engineer D's informal sharing of as-built drawings"],
            "interpretation": "Informal information sharing undermines transparency requirements in public projects",
            "source_text": "Working through informal mechanisms on public projects can give the appearance of impropriety or favoritism",
            "balancing_with": ["Efficiency", "Design improvement"],
            "tension_resolution": "Formal processes must be followed despite inefficiency",
            "case_relevance": "Identifies the ethical problem with D's informal approach"
        },
        {
            "identifier": "ProceduralFairness_CaseD_Conclusion",
            "principle_class": "Procedural Fairness",
            "concrete_expression": "It would be unethical for D to share as-builts with selected contractors pre-bid",
            "invoked_by": ["Case conclusion"],
            "applied_to": ["Selective pre-bid information sharing"],
            "interpretation": "Selective information sharing violates fair competition principles",
            "source_text": "It would be unethical for D to share as-builts with selected contractors pre-bid",
            "balancing_with": ["Design improvement", "Practical efficiency"],
            "tension_resolution": "Fairness in bidding process takes precedence over design benefits",
            "case_relevance": "Final determination that selective sharing violates ethical principles"
        }
    ]
}
```
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: Acting as a faithful agent or trustee for a client or employer is an obligation for any engineer and is one of the fundamental canons in NSPE’s code of ethics. Engineer D’s efforts to make as-built drawings available for reference appears to be acting in the employer’s best interest. Providing more information about existing conditions should help produce a better design. When D provides as-built drawings after bid openings, is employer information being shared without consent? In addition, if information is shared selectively with contractors before bids are opened; will D’s actions influence the award of a contract? BER Case 82-2 is a useful starting point in this discussion. In that case, an engineer offers a service providing inspection of residences to prospective homeowners. For the situation in question, the engineer produced a report for their client and provided a copy to the real estate firm handling the home sale. The client complained the engineer acted unethically by providing a copy to the real estate firm and caused harm by lessening their bargaining position with the owners of the residence. Case discussion notes there was no transmission of the client’s confidential information by the engineer (presumably the real estate firm could have had the home inspected and gained the same knowledge). The BER states “we read into this case an assumption that Engineer A acted without thought or consideration of any ulterior motive; that he, as a matter of course, considered it right and proper to make his findings known to all interested parties …” The board exonerated the engineer of substantial or deliberate wrongdoing, but determined it was incorrect to not recognize the confidentiality of a client relationship. The engineer acted unethically in submitting a copy of the home inspection report to the real estate agent. BER Case 15-7 involves the ubiquitous Engineer A working for Firm X. A’s firm is retained by a municipality to design a water treatment facility. A believes the project can benefit from a discussion of constructability issues, and is tempted to begin a discussion with local Contractor B. A is concerned that potential discussions with B will provide an unfair advantage. The board advised that “rather than consulting solely with Contractor B, Engineer A could have conducted a publically (sic) advertised constructability meeting, inviting all interested contractors to provide Engineer A with the input necessary to achieve a better design and construction outcome. Such a process would avoid any appearance of favoritism toward one particular contractor, serve the client’s interests, and gain the benefit of broader input to improve the design and construction process.” The above summary of case history focused on engineers providing or being in position to have access to information not generally available to others. BER Case 16-3 involves Engineer A who receives a submittal by a highly qualified engineering firm (Firm B) a few hours after a well-publicized deadline. In 16-3, “the Board is concerned that allowing Firm B’s submittal to be considered would open the procurement to challenge or at the very least create a climate in which non-adherence to public procurement rules and policies are tolerated. Such a situation would not reflect well on that process, the city, or the engineering profession.” The conclusion was that A should return the submittal to firm B, unopened and explain that the bid/submittal was received late. Returning to the case at hand, Engineer D seems to be acting without what was termed in case 82-2, an ulterior motive - D’s desire is to make information available to improve designs. Even so, informally sharing as-built information is troubling. Working through informal mechanisms on public projects can give the appearance of impropriety or favoritism. Engineer D can advise that as-built drawings are available, but D should direct subcontractors to request them as part of the standard project process. D should not share documents on their own initiative or without formal permission. Because as-builts are useful and can help improve designs, Engineer D should initiate a process to include as-built drawings, when available, on projects going forward. It would be unethical for D to share as-builts with selected contractors pre-bid. Extract obligations following this JSON structure: { "new_obligation_classes": [ { "label": "Clear, specific obligation class name", "definition": "What this type of obligation requires professionals to do", "derived_from_principle": "Which principle this operationalizes (e.g., 'Public Safety', 'Honesty')", "duty_type": "professional|legal|ethical|societal", "enforcement_mechanism": "How this obligation is typically enforced", "violation_consequences": "What happens when this obligation is violated", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this obligation is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "obligation_individuals": [ { "identifier": "Unique name for this specific obligation instance", "obligation_class": "Name of the obligation class (new or existing)", "obligated_party": "Who has this obligation (e.g., 'Engineer L', 'All Licensed PEs')", "obligation_statement": "The specific duty statement (e.g., 'Report safety risks to authorities')", "derived_from": "Source principle or law (e.g., 'NSPE Code', 'State Law')", "enforcement_context": "How enforced in this case", "temporal_scope": "When this obligation applies", "compliance_status": "met|unmet|unclear|pending", "case_context": "How this obligation manifests in the specific case", "source_text": "EXACT text snippet from case where this obligation is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW obligation types that represent novel professional duties 2. Specific obligation instances showing how duties apply in this case 3. The relationship between obligations and the principles they operationalize 4. Enforcement mechanisms and compliance status Return ONLY the JSON structure, no additional text.
Saved: 2025-12-29 20:26
LLM Response
```json
{
  "new_obligation_classes": [
    {
      "label": "Faithful Agency Obligation",
      "definition": "Duty to act as a faithful agent or trustee for clients and employers, prioritizing their interests while maintaining professional integrity",
      "derived_from_principle": "Fidelity",
      "duty_type": "professional",
      "enforcement_mechanism": "Professional review boards, ethics committees, employment contracts",
      "violation_consequences": "Ethics violations, loss of professional standing, termination of employment",
      "examples_from_case": ["Acting in employer's best interest", "Not sharing employer information without consent"],
      "source_text": "Acting as a faithful agent or trustee for a client or employer is an obligation for any engineer and is one of the fundamental canons in NSPE's code of ethics",
      "confidence": 0.9,
      "reasoning": "While related to professional obligations, this specifically addresses the fiduciary-like duty to act as a faithful agent, which is distinct from general professional duties"
    },
    {
      "label": "Fair Competition Obligation",
      "definition": "Requirement to ensure fair and equal access to information and opportunities in competitive bidding and procurement processes",
      "derived_from_principle": "Fairness",
      "duty_type": "professional",
      "enforcement_mechanism": "Public procurement rules, professional ethics boards, legal challenges",
      "violation_consequences": "Bid challenges, ethics violations, contract invalidation, damage to professional reputation",
      "examples_from_case": ["Not providing unfair advantage to specific contractors", "Ensuring all bidders have equal access to information"],
      "source_text": "A is concerned that potential discussions with B will provide an unfair advantage",
      "confidence": 0.85,
      "reasoning": "Distinct from general professional obligations - specifically addresses maintaining fairness in competitive processes and avoiding favoritism"
    },
    {
      "label": "Procurement Integrity Obligation",
      "definition": "Duty to strictly adhere to public procurement rules, deadlines, and procedures to maintain the integrity of the bidding process",
      "derived_from_principle": "Integrity",
      "duty_type": "legal",
      "enforcement_mechanism": "Procurement regulations, legal review, bid protest procedures",
      "violation_consequences": "Bid protests, contract challenges, legal liability, professional sanctions",
      "examples_from_case": ["Returning late submittals unopened", "Following standard project processes for information requests"],
      "source_text": "allowing Firm B's submittal to be considered would open the procurement to challenge or at the very least create a climate in which non-adherence",
      "confidence": 0.8,
      "reasoning": "Specific to procurement processes and goes beyond general legal obligations to address the unique requirements of public bidding"
    }
  ],
  "obligation_individuals": [
    {
      "identifier": "EngineerD_FaithfulAgency_Employer",
      "obligation_class": "Faithful Agency Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Act as faithful agent for employer while managing as-built drawings",
      "derived_from": "NSPE Code of Ethics Fundamental Canon",
      "enforcement_context": "Professional ethics review",
      "temporal_scope": "During employment relationship",
      "compliance_status": "unclear",
      "case_context": "D's efforts to make as-built drawings available appears to be acting in employer's best interest",
      "source_text": "Engineer D's efforts to make as-built drawings available for reference appears to be acting in the employer's best interest",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerD_Confidentiality_AsBuilts",
      "obligation_class": "Confidentiality Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Must not share employer's as-built drawings without formal permission",
      "derived_from": "NSPE III.4",
      "enforcement_context": "Employment agreement and professional standards",
      "temporal_scope": "Ongoing",
      "compliance_status": "unmet",
      "case_context": "D provides as-built drawings after bid openings without clear consent",
      "source_text": "When D provides as-built drawings after bid openings, is employer information being shared without consent?",
      "is_existing_class": true,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerD_FairCompetition_Contractors",
      "obligation_class": "Fair Competition Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Must not selectively share information with contractors that provides unfair advantage",
      "derived_from": "Professional ethics and procurement regulations",
      "enforcement_context": "Public procurement rules",
      "temporal_scope": "During bidding process",
      "compliance_status": "pending",
      "case_context": "D must avoid sharing information selectively with contractors before bids are opened",
      "source_text": "if information is shared selectively with contractors before bids are opened; will D's actions influence the award of a contract?",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerA_Case82-2_Confidentiality",
      "obligation_class": "Confidentiality Obligation",
      "obligated_party": "Engineer A (Case 82-2)",
      "obligation_statement": "Must recognize confidentiality of client relationship and not share reports without permission",
      "derived_from": "Professional ethics standards",
      "enforcement_context": "BER review",
      "temporal_scope": "During client engagement",
      "compliance_status": "unmet",
      "case_context": "Engineer provided home inspection report to real estate firm without client consent",
      "source_text": "determined it was incorrect to not recognize the confidentiality of a client relationship",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerA_Case15-7_FairCompetition",
      "obligation_class": "Fair Competition Obligation",
      "obligated_party": "Engineer A (Case 15-7)",
      "obligation_statement": "Must avoid appearance of favoritism by ensuring equal access to constructability discussions",
      "derived_from": "Professional ethics",
      "enforcement_context": "Professional standards",
      "temporal_scope": "During design phase",
      "compliance_status": "pending",
      "case_context": "A must conduct public constructability meeting rather than consulting solely with one contractor",
      "source_text": "Such a process would avoid any appearance of favoritism toward one particular contractor",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerA_Case16-3_ProcurementIntegrity",
      "obligation_class": "Procurement Integrity Obligation",
      "obligated_party": "Engineer A (Case 16-3)",
      "obligation_statement": "Must return late submittals unopened to maintain procurement integrity",
      "derived_from": "Public procurement rules and policies",
      "enforcement_context": "Legal and professional review",
      "temporal_scope": "During procurement process",
      "compliance_status": "met",
      "case_context": "A should return late submittal from Firm B unopened despite high qualifications",
      "source_text": "A should return the submittal to firm B, unopened and explain that the bid/submittal was received late",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerD_Disclosure_AsBuiltAvailability",
      "obligation_class": "Disclosure Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Should advise that as-built drawings are available through standard project process",
      "derived_from": "NSPE II.3.a",
      "enforcement_context": "Professional standards",
      "temporal_scope": "During project bidding",
      "compliance_status": "pending",
      "case_context": "D can advise about availability but should direct contractors to formal request process",
      "source_text": "Engineer D can advise that as-built drawings are available, but D should direct subcontractors to request them as part of the standard project process",
      "is_existing_class": true,
      "confidence": 0.8
    }
  ]
}
```
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: Acting as a faithful agent or trustee for a client or employer is an obligation for any engineer and is one of the fundamental canons in NSPE’s code of ethics. Engineer D’s efforts to make as-built drawings available for reference appears to be acting in the employer’s best interest. Providing more information about existing conditions should help produce a better design. When D provides as-built drawings after bid openings, is employer information being shared without consent? In addition, if information is shared selectively with contractors before bids are opened; will D’s actions influence the award of a contract? BER Case 82-2 is a useful starting point in this discussion. In that case, an engineer offers a service providing inspection of residences to prospective homeowners. For the situation in question, the engineer produced a report for their client and provided a copy to the real estate firm handling the home sale. The client complained the engineer acted unethically by providing a copy to the real estate firm and caused harm by lessening their bargaining position with the owners of the residence. Case discussion notes there was no transmission of the client’s confidential information by the engineer (presumably the real estate firm could have had the home inspected and gained the same knowledge). The BER states “we read into this case an assumption that Engineer A acted without thought or consideration of any ulterior motive; that he, as a matter of course, considered it right and proper to make his findings known to all interested parties …” The board exonerated the engineer of substantial or deliberate wrongdoing, but determined it was incorrect to not recognize the confidentiality of a client relationship. The engineer acted unethically in submitting a copy of the home inspection report to the real estate agent. BER Case 15-7 involves the ubiquitous Engineer A working for Firm X. A’s firm is retained by a municipality to design a water treatment facility. A believes the project can benefit from a discussion of constructability issues, and is tempted to begin a discussion with local Contractor B. A is concerned that potential discussions with B will provide an unfair advantage. The board advised that “rather than consulting solely with Contractor B, Engineer A could have conducted a publically (sic) advertised constructability meeting, inviting all interested contractors to provide Engineer A with the input necessary to achieve a better design and construction outcome. Such a process would avoid any appearance of favoritism toward one particular contractor, serve the client’s interests, and gain the benefit of broader input to improve the design and construction process.” The above summary of case history focused on engineers providing or being in position to have access to information not generally available to others. BER Case 16-3 involves Engineer A who receives a submittal by a highly qualified engineering firm (Firm B) a few hours after a well-publicized deadline. In 16-3, “the Board is concerned that allowing Firm B’s submittal to be considered would open the procurement to challenge or at the very least create a climate in which non-adherence to public procurement rules and policies are tolerated. Such a situation would not reflect well on that process, the city, or the engineering profession.” The conclusion was that A should return the submittal to firm B, unopened and explain that the bid/submittal was received late. Returning to the case at hand, Engineer D seems to be acting without what was termed in case 82-2, an ulterior motive - D’s desire is to make information available to improve designs. Even so, informally sharing as-built information is troubling. Working through informal mechanisms on public projects can give the appearance of impropriety or favoritism. Engineer D can advise that as-built drawings are available, but D should direct subcontractors to request them as part of the standard project process. D should not share documents on their own initiative or without formal permission. Because as-builts are useful and can help improve designs, Engineer D should initiate a process to include as-built drawings, when available, on projects going forward. It would be unethical for D to share as-builts with selected contractors pre-bid. Extract constraints following this JSON structure: { "new_constraint_classes": [ { "label": "Clear, specific constraint class name", "definition": "What this type of constraint limits or restricts", "constraint_type": "legal|physical|resource|temporal|procedural", "flexibility": "hard|soft|negotiable", "violation_impact": "What happens if this constraint is violated", "mitigation_possible": "Whether and how this constraint can be mitigated", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this constraint is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "constraint_individuals": [ { "identifier": "Unique name for this specific constraint instance", "constraint_class": "Name of the constraint class (new or existing)", "constrained_entity": "What or who is constrained (e.g., 'Engineer L', 'Project')", "constraint_statement": "The specific limitation (e.g., 'Cannot exceed budget of $X')", "source": "Origin of constraint (e.g., 'Client budget', 'Environmental law')", "enforcement_mechanism": "How this constraint is enforced", "temporal_scope": "When this constraint applies", "severity": "critical|major|minor", "case_context": "How this constraint manifests in the specific case", "source_text": "EXACT text snippet from case where this constraint is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW constraint types that represent novel limitations or boundaries 2. Specific constraint instances showing how limitations apply in this case 3. The difference between constraints (boundaries) and obligations (duties) 4. Impact and severity of constraints on decision-making Return ONLY the JSON structure, no additional text.
Saved: 2025-12-29 20:26
LLM Response
```json
{
  "new_constraint_classes": [
    {
      "label": "Information Timing Constraint",
      "definition": "Limitations on when information can be shared or disclosed during competitive bidding or procurement processes",
      "constraint_type": "procedural",
      "flexibility": "hard",
      "violation_impact": "Creates unfair competitive advantage, undermines procurement integrity, potential legal challenges",
      "mitigation_possible": "Can be mitigated through public disclosure mechanisms that ensure equal access",
      "examples_from_case": ["Information shared after bid openings", "Information shared selectively with contractors before bids"],
      "source_text": "When D provides as-built drawings after bid openings, is employer information being shared without consent?",
      "confidence": 0.85,
      "reasoning": "Distinct from procedural constraints as it specifically addresses temporal boundaries in information disclosure during competitive processes"
    },
    {
      "label": "Competitive Fairness Constraint",
      "definition": "Boundaries preventing actions that create unfair advantages or appearance of favoritism in competitive professional contexts",
      "constraint_type": "procedural",
      "flexibility": "hard",
      "violation_impact": "Undermines fair competition, creates appearance of impropriety, damages professional reputation",
      "mitigation_possible": "Through transparent, publicly advertised processes that ensure equal access",
      "examples_from_case": ["Avoiding favoritism toward one contractor", "Ensuring all contractors have equal information access"],
      "source_text": "Such a process would avoid any appearance of favoritism toward one particular contractor",
      "confidence": 0.9,
      "reasoning": "Goes beyond ethical constraints to specifically address competitive equity and appearance of impropriety in professional competitions"
    }
  ],
  "constraint_individuals": [
    {
      "identifier": "D_Information_Sharing_Timing",
      "constraint_class": "Information Timing Constraint",
      "constrained_entity": "Engineer D",
      "constraint_statement": "Cannot share as-built drawings with contractors after bid openings without formal permission",
      "source": "Public procurement rules and employer consent requirements",
      "enforcement_mechanism": "Employer policies and public procurement regulations",
      "temporal_scope": "During and after bidding process",
      "severity": "major",
      "case_context": "D's sharing of as-built drawings after bid opening may violate timing constraints",
      "source_text": "When D provides as-built drawings after bid openings, is employer information being shared without consent?",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "D_Selective_Disclosure_Prohibition",
      "constraint_class": "Competitive Fairness Constraint",
      "constrained_entity": "Engineer D",
      "constraint_statement": "Cannot selectively share information with specific contractors pre-bid",
      "source": "Professional ethics and public procurement standards",
      "enforcement_mechanism": "Professional ethics review and potential legal challenge",
      "temporal_scope": "Before bid opening",
      "severity": "critical",
      "case_context": "D must not share as-builts with selected contractors before bidding",
      "source_text": "It would be unethical for D to share as-builts with selected contractors pre-bid",
      "is_existing_class": false,
      "confidence": 0.95
    },
    {
      "identifier": "D_Employer_Consent_Requirement",
      "constraint_class": "Confidentiality Constraint",
      "constrained_entity": "Engineer D",
      "constraint_statement": "Cannot share employer information without formal consent",
      "source": "Employer-employee relationship and confidentiality obligations",
      "enforcement_mechanism": "Employment agreement and professional ethics standards",
      "temporal_scope": "Throughout employment and project duration",
      "severity": "major",
      "case_context": "D needs formal permission before sharing employer's as-built drawings",
      "source_text": "is employer information being shared without consent?",
      "is_existing_class": true,
      "confidence": 0.9
    },
    {
      "identifier": "Public_Procurement_Deadline",
      "constraint_class": "Procedural Constraint",
      "constrained_entity": "All bidding firms",
      "constraint_statement": "Must submit bids/proposals before published deadline",
      "source": "Public procurement rules and policies",
      "enforcement_mechanism": "Automatic rejection of late submissions",
      "temporal_scope": "Until bid deadline",
      "severity": "critical",
      "case_context": "Late submittal from Firm B must be returned unopened",
      "source_text": "allowing Firm B's submittal to be considered would open the procurement to challenge",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "D_Informal_Mechanism_Prohibition",
      "constraint_class": "Procedural Constraint",
      "constrained_entity": "Engineer D",
      "constraint_statement": "Cannot use informal mechanisms to share information on public projects",
      "source": "Public procurement standards and professional ethics",
      "enforcement_mechanism": "Professional review and potential disciplinary action",
      "temporal_scope": "Throughout public project lifecycle",
      "severity": "major",
      "case_context": "D must direct contractors through standard project processes",
      "source_text": "Working through informal mechanisms on public projects can give the appearance of impropriety or favoritism",
      "is_existing_class": true,
      "confidence": 0.85
    }
  ]
}
```
Capabilities Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for capabilities (competencies and skills required for professional practice). Based on the literature: - Capabilities are COMPETENCIES that enable norm compliance (Hallamaa & Kalliokoski 2022) - They represent the skills needed to fulfill professional obligations (Dennis et al. 2016) - Capabilities include technical, ethical, communicative, and analytical competencies - They constitute "norm competence" - the ability to act ethically (Kong et al. 2020) Your task is to: 1. Identify NEW CAPABILITY CLASSES not in the existing ontology 2. Extract SPECIFIC CAPABILITY INDIVIDUALS from the case EXISTING CAPABILITIES IN ONTOLOGY (check if your identified capabilities match these before creating new classes): - AI Tool Evaluation Capability: The competency to assess, validate, and appropriately use AI-generated content in professional work - Capability: A realizable entity that can be realized by specific types of actions or processes in professional contexts. This is the Ca component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Capability Type: Meta-class for specific capability types recognized by the ProEthica system - Data Privacy Protection Capability: The competency to safeguard confidential client information when using digital tools and platforms - Justification Capability: Capability to trace reasoning paths connecting decisions to authoritative sources (McLaren 2003, Anderson & Anderson 2018) - Regulatory Compliance Capability: The competency to ensure designs and documents meet local regulations and safety standards - Responsible Charge Capability: The competency to maintain active engagement and supervisory control from conception to completion of engineering work - Technical Capability: A specialized technical skill or competency in a professional domain - Technical Writing Capability: The competency to produce clear, accurate, and professional technical documentation and reports - Technology Integration Capability: The competency to appropriately integrate new technologies while maintaining professional judgment Analyze this facts section: Engineer D is a fire protection engineer in the public sector and works for a state agency. The agency advertises for bids on major building renovation projects; the bid documents made no reference to existing as-builts or drawings for the bidders’ or awarded contractor’s use. After bids are opened and contracts are awarded, the successful sprinkler contractor asks Engineer D for as-built drawings of the existing sprinkler system. D provides the drawings. Over time, sprinkler contractors who received as-built drawings from Engineer D in the past begin to ask for these documents when projects are advertised, before bids are turned in. Extract capabilities following this JSON structure: { "new_capability_classes": [ { "label": "Clear, specific capability class name", "definition": "What competency or skill this capability represents", "capability_type": "technical|ethical|communicative|analytical", "norm_competence_related": "Which professional obligations this capability enables", "skill_level": "basic|intermediate|advanced|expert", "acquisition_method": "How this capability is typically acquired (education, training, experience)", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this capability is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "capability_individuals": [ { "identifier": "Unique name for this specific capability instance", "capability_class": "Name of the capability class (new or existing)", "possessed_by": "Who has this capability (e.g., 'Engineer L', 'All Licensed PEs')", "capability_statement": "The specific competency (e.g., 'Design stormwater systems')", "demonstrated_through": "How shown in the case (e.g., 'Years of experience', 'Professional license')", "proficiency_level": "basic|intermediate|advanced|expert", "enables_obligations": "Which obligations this capability enables", "temporal_aspect": "When this capability is relevant", "case_context": "How this capability manifests in the specific case", "source_text": "EXACT text snippet from case where this capability is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW capability types that represent novel competencies 2. Specific capability instances showing professional competencies in this case 3. The relationship between capabilities and norm competence 4. How capabilities enable fulfillment of professional obligations Return ONLY the JSON structure, no additional text.
Saved: 2025-12-29 20:25
LLM Response
```json
{
  "new_capability_classes": [
    {
      "label": "Public Procurement Management Capability",
      "definition": "The competency to properly manage bidding processes, documentation, and contractor interactions in public sector procurement",
      "capability_type": "ethical",
      "norm_competence_related": "Ensures fair and transparent bidding processes, maintains competitive integrity",
      "skill_level": "intermediate",
      "acquisition_method": "Public sector experience, procurement training, understanding of government contracting regulations",
      "examples_from_case": ["Managing bid document preparation", "Controlling information release timing"],
      "source_text": "The agency advertises for bids on major building renovation projects; the bid documents made no reference to existing as-builts",
      "confidence": 0.85,
      "reasoning": "Not covered by existing capabilities - specific to public sector procurement ethics and bid management processes"
    },
    {
      "label": "Information Equity Capability",
      "definition": "The competency to ensure equal access to project information for all bidders to maintain fair competition",
      "capability_type": "ethical",
      "norm_competence_related": "Maintains fairness in competitive bidding, prevents preferential treatment",
      "skill_level": "intermediate",
      "acquisition_method": "Ethics training, public sector experience, understanding of fair competition principles",
      "examples_from_case": ["Selective sharing of as-built drawings", "Timing of information release"],
      "source_text": "sprinkler contractors who received as-built drawings from Engineer D in the past begin to ask for these documents when projects are advertised",
      "confidence": 0.9,
      "reasoning": "Distinct from data privacy - focuses on equitable information distribution rather than protection"
    }
  ],
  "capability_individuals": [
    {
      "identifier": "EngineerD_FireProtectionExpertise",
      "capability_class": "Technical Capability",
      "possessed_by": "Engineer D",
      "capability_statement": "Fire protection engineering expertise for building renovation projects",
      "demonstrated_through": "Position as fire protection engineer in state agency",
      "proficiency_level": "advanced",
      "enables_obligations": "Technical review and oversight of fire protection systems",
      "temporal_aspect": "Throughout employment at state agency",
      "case_context": "Manages fire protection aspects of major building renovation projects",
      "source_text": "Engineer D is a fire protection engineer in the public sector and works for a state agency",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerD_InformationEquity",
      "capability_class": "Information Equity Capability",
      "possessed_by": "Engineer D",
      "capability_statement": "Should ensure equal access to as-built drawings for all bidders",
      "demonstrated_through": "Selective provision of drawings post-bid",
      "proficiency_level": "basic",
      "enables_obligations": "Fair competition in public bidding processes",
      "temporal_aspect": "During bid advertisement and award phases",
      "case_context": "Failed to include as-builts in bid documents but provided them selectively",
      "source_text": "D provides the drawings. Over time, sprinkler contractors who received as-built drawings from Engineer D in the past",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerD_ProcurementManagement",
      "capability_class": "Public Procurement Management Capability",
      "possessed_by": "Engineer D",
      "capability_statement": "Manage public sector bidding and documentation processes",
      "demonstrated_through": "Involvement in bid advertisement and contractor interactions",
      "proficiency_level": "intermediate",
      "enables_obligations": "Transparent and fair public procurement processes",
      "temporal_aspect": "Throughout project procurement lifecycle",
      "case_context": "Manages bid documents and post-award contractor requests",
      "source_text": "The agency advertises for bids on major building renovation projects",
      "is_existing_class": false,
      "confidence": 0.8
    }
  ]
}
```