AI-Assisted Design Engineer
type: Class
confidence: 0.82
role category: provider_client
text references: Engineer A applied their seal consistent with state law
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
text references: Engineer A opted to use open-sourced artificial intelligence (AI) software to create an initial draft of the necessary report and to use AI-assisted drafting tools to generate preliminary design documents
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T13:59:26.869728+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A opted to use open-sourced artificial intelligence (AI) software to create an initial draft of the necessary report and to use AI-assisted drafting tools to generate preliminary design documents
comment: A professional engineering role in which the practitioner uses AI-assisted drafting or synthesis tools to generate preliminary design documents or reports, while retaining full professional accountability for the accuracy, completeness, and regulatory compliance of the final work product bearing their seal.
subclass of: EngineerRole
subclass of: ProviderClientRole
generated at time: 2026-06-03T13:59:26.869728+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI-Generated Work Product State
type: Class
action constraints: Should not omit disclosure of AI use where professional standards or client expectations require transparency
action constraints: Should not rely on AI outputs for safety-critical design elements without independent verification
action constraints: Should not seal or submit AI-generated work without thorough independent review
activation conditions: AI output is incorporated into a deliverable submitted to a client or stamped with a professional seal
activation conditions: AI software is used to generate a draft report, design document, or other professional work product
confidence: 0.9
obligation activation: Obligation to disclose AI tool use to clients and relevant parties
obligation activation: Obligation to ensure AI-generated work meets professional and regulatory standards before sealing or submitting
obligation activation: Obligation to take professional responsibility for all content regardless of its generative origin
obligation activation: Obligation to verify accuracy, originality, and completeness of AI-generated content
persistence type: inertial
principle transformation: Transforms general honesty, competence, and professional accountability principles into specific duties of disclosure, verification, and independent review when AI tools contribute substantially to a professional work product.
state category: information
termination conditions: AI-generated content is fully replaced by independently authored content
termination conditions: Disclosure of AI use is made and work product is re-evaluated under applicable standards
text references: Engineer A did not cite the AI-assisted drafting tools they used to generate the engineering design documents
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
text references: Engineer A opted to use open-sourced artificial intelligence (AI) software to create an initial draft of the necessary report and to use AI-assisted drafting tools to generate preliminary design documents
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T14:00:13.061399+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A opted to use open-sourced artificial intelligence (AI) software to create an initial draft of the necessary report and to use AI-assisted drafting tools to generate preliminary design documents
comment: State in which a professional's work product has been substantially generated or drafted by artificial intelligence tools, creating obligations regarding disclosure of AI use, verification of accuracy and originality, professional accountability for the output, and compliance with applicable professional and legal standards governing AI-assisted work.
subclass of: InformationState
generated at time: 2026-06-03T14:00:13.061399+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Authorship Honesty Obligation
type: Class
confidence: 0.88
derived from principle: Intellectual Honesty in Authorship Principle
enforcement level: mandatory
monitoring criteria: Accurate attribution of AI-generated content in submitted work products and transmittal documents
nspe reference: III.2, II.5.a
obligation type: ethical
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Professional licensing board
text references: Engineer A also made minor adjustments to some of the wording to personalize the content.
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
text references: The Client commented that the report read as if written by two different authors but was otherwise satisfactory.
violation consequences: Misrepresentation of professional work; breach of client trust; potential disciplinary action for dishonest professional conduct
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:05:12.288818+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A also made minor adjustments to some of the wording to personalize the content.
comment: Duty of an engineer to accurately represent the intellectual origin and authorship of professional work products, including disclosure when AI tools have substantially generated the content, and to refrain from presenting AI-generated work as the engineer's own original intellectual product.
subclass of: EthicalObligation
generated at time: 2026-06-03T14:05:12.288818+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Contribution Attribution Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Professional licensing board
affected stakeholders: Public
confidence: 0.82
constraint type: ethical
flexibility: soft
mitigation strategies: Follow emerging best practices and professional society guidance on AI attribution
mitigation strategies: Include a methodology section describing AI tool contributions
mitigation strategies: Proactively disclose AI use in cover letters or report headers
text references: BER Case 98-3 emphasized that engineers must acknowledge significant contributions by others. AI, while not a human contributor, fundamentally shaped the report and design documents, warranting disclosure under Code section III.9, '[e]ngineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.'
text references: There are currently no universal guidelines mandating AI disclosure in engineering work, but best practices suggest informing clients when AI substantially contributes to a work product.
violation impact: Misrepresentation of work product authorship, undermining client trust, ethics code violation under attribution and honesty provisions
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:08.316438+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: BER Case 98-3 emphasized that engineers must acknowledge significant contributions by others. AI, while not a human contributor, fundamentally shaped the report and design documents, warranting disclosure under Code section III.9, '[e]ngineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.'
comment: Ethical constraint requiring that an engineer disclose and appropriately attribute the substantial contribution of AI tools to a professional work product, consistent with the professional obligation to give credit for engineering work to those to whom credit is due, so that clients and reviewers can accurately assess the origin and nature of the work.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
generated at time: 2026-06-03T14:11:08.316438+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Contribution Disclosure Obligation
type: Class
confidence: 0.9
derived from principle: AI Tool Disclosure Principle
enforcement level: prima_facie
monitoring criteria: Documented disclosure to client that AI tools substantially contributed to the work product, made prior to or concurrent with delivery
nspe reference: III.9
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: Employer
stakeholders affected: Regulatory bodies
text references: Given that Client W identified issues in the engineering design and questioned inconsistencies in the report, proactive disclosure could have prevented misunderstandings and strengthened trust.
text references: There are currently no universal guidelines mandating AI disclosure in engineering work, but best practices suggest informing clients when AI substantially contributes to a work product.
text references: While Engineer A reviewed the content, the lack of disclosure raises concerns about transparency.
violation consequences: Erosion of client trust; potential misunderstanding of work product provenance; violation of transparency norms under NSPE III.9
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:09:34.826300+00:00
first discovered in case: 7
match confidence: 0.88
match reasoning: This obligation is substantively the same concept as the already-extracted AI Tool Disclosure Obligation. The present class emphasizes the proactive and best-practice dimension but covers the same duty to disclose AI contribution to clients and stakeholders.
matched ontology class: AI Tool Disclosure Obligation
matched ontology label: AI Tool Disclosure Obligation
matches existing: true
source text: There are currently no universal guidelines mandating AI disclosure in engineering work, but best practices suggest informing clients when AI substantially contributes to a work product.
comment: Duty of an engineer to proactively inform clients and other stakeholders when AI tools have substantially contributed to a professional work product, so that stakeholders can assess the nature and provenance of the work and so that transparency and trust are maintained, even in the absence of universal mandatory disclosure guidelines.
subclass of: DisclosureObligation
generated at time: 2026-06-03T14:09:34.826300+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Direction and Control Obligation
type: Class
confidence: 0.91
derived from principle: Responsible Charge Integrity Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer defined solution guidelines prior to AI use, critically reviewed outputs, and documented the basis for accepting the final work product
nspe reference: II.2.b
obligation type: competence
stakeholders affected: Client
stakeholders affected: Engineer
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: By relying on AI-assisted tools without a comprehensive verification process of its output, Engineer A risked violating this requirement.
text references: Much like directing an engineering intern to solve a problem, responsible use of AI requires an engineer to outline solution guidelines and constraints. Recommendations from the program or intern should not be blindly accepted, they should be considered and challenged and the resulting outputs should be understood.
violation consequences: Violation of responsible charge requirements; potential public safety harm; disciplinary action; licensure consequences
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:09:34.826300+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Much like directing an engineering intern to solve a problem, responsible use of AI requires an engineer to outline solution guidelines and constraints. Recommendations from the program or intern should not be blindly accepted, they should be considered and challenged and the resulting outputs should be understood.
comment: Duty of an engineer who uses AI-assisted tools to generate professional work products to exercise genuine direction and control over the AI process, including outlining solution guidelines and constraints before generation, critically challenging outputs, and verifying that results conform to professional and project-specific standards before acceptance, rather than passively accepting AI-generated content.
subclass of: CompetenceObligation
generated at time: 2026-06-03T14:09:34.826300+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Licensing Board
affected stakeholders: Public
confidence: 0.88
constraint type: ethical
flexibility: hard
mitigation strategies: Consult applicable professional society guidance on AI disclosure before using AI tools
mitigation strategies: Establish office policy requiring AI use notation in all deliverables
mitigation strategies: Include explicit disclosure language in submitted work products identifying AI tool use
text references: Again, Engineer A did not cite the AI-assisted drafting tools they used to generate the engineering design documents.
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
violation impact: Misrepresentation of work product authorship, breach of client trust, potential disciplinary action by licensing board, and undermining of professional integrity standards.
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:33.588436+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
comment: Ethical and professional constraint requiring an engineer who uses AI tools to generate or substantially assist in producing a work product to disclose that use to the client and relevant parties, so that the client can accurately assess the nature and origin of the work product delivered.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-03T14:06:33.588436+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Output Verification Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Licensing Board
affected stakeholders: Public
confidence: 0.87
constraint type: competence
flexibility: hard
mitigation strategies: Cross-check AI-generated design elements against local regulatory requirements
mitigation strategies: Engage a qualified peer reviewer when personal competence to verify AI output is uncertain
mitigation strategies: Limit AI tool use to areas where the engineer has sufficient expertise to evaluate outputs
mitigation strategies: Perform line-by-line technical review of all AI-generated content against applicable standards
text references: Client W noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
violation impact: Submission of deficient or non-compliant work products, public safety risk, professional seal applied to work not meeting responsible charge standards, regulatory violations, and client harm.
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:33.588436+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
comment: Competence and safety constraint requiring an engineer who uses AI-generated outputs as the basis for professional work products to conduct a sufficiently thorough independent technical review of those outputs before submission, such that the engineer can take responsible charge and ensure accuracy, regulatory compliance, and fitness for purpose.
subclass of: CompetenceConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-03T14:06:33.588436+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Output Verification Obligation
type: Class
confidence: 0.91
derived from principle: AI Verification Competence Principle
enforcement level: mandatory
monitoring criteria: Evidence of systematic review process for AI-generated content, including cross-checking against authoritative sources and regulatory requirements
nspe reference: II.2, II.2.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Client W, however, noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
violation consequences: Submission of technically deficient work products; public safety risk; professional discipline; liability for errors in AI-generated content
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:05:12.288818+00:00
first discovered in case: 7
match confidence: 0.75
match reasoning: This obligation is a specialization of the existing Competence Obligation, applied specifically to the context of AI-generated outputs. The existing class covers the general duty to practice within competence, but does not address the specific verification duty that arises when AI tools are used to generate professional work products. A new class is warranted to capture this distinct obligation type.
matched ontology class: CompetenceObligation
matched ontology label: Competence Obligation
matches existing: true
source text: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
comment: Duty of an engineer who uses AI-assisted tools to generate technical work products to conduct a sufficiently thorough and competent review of AI-generated outputs before submitting or sealing those outputs, commensurate with the engineer's professional responsibility and the risk profile of the work.
subclass of: CompetenceObligation
scope note: [CompetenceObligation] Requirement to perform services only in areas of competence (NSPE II.2)
generated at time: 2026-06-03T14:05:12.288818+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Tool Disclosure Capability
type: Class
capability category: awareness
confidence: 0.88
domain specificity: Professional engineering practice involving AI-assisted drafting or synthesis tools
enables actions: Disclose AI tool use to clients
enables actions: Identify AI-generated content in professional deliverables
enables actions: Represent authorship accurately in submitted work products
required for obligations: AI Authorship Honesty Obligation
required for obligations: AI Tool Disclosure Obligation
skill level: intermediate
text references: Again, Engineer A did not cite the AI-assisted drafting tools they used to generate the engineering design documents.
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:21.353968+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
comment: Capability to recognize when the use of AI-assisted tools or large language models in professional work products triggers a disclosure obligation, and to communicate that use accurately and transparently to clients and other stakeholders.
subclass of: Capability
generated at time: 2026-06-03T14:06:21.353968+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Tool Disclosure Principle
type: Class
abstract nature: Open-textured obligation whose scope depends on evolving professional norms, jurisdictional rules, and the degree to which AI contribution materially shaped the work product.
confidence: 0.88
derived obligations: Disclose use of AI software in report preparation
derived obligations: Disclose use of AI-assisted drafting tools in design documents
derived obligations: Identify limitations of AI-generated content to clients
extensional examples: Academic submission of AI-generated text without attribution
extensional examples: Engineer submitting AI-drafted report without disclosure to client
extensional examples: Engineer using AI-generated design documents without noting tool provenance in submittal
operationalization: Requires engineers to identify AI tools used, note their role in the work product, and flag limitations of AI-generated content in professional submittals.
potential conflicts: Client expectations of seamless deliverables
potential conflicts: Competitive pressure to conceal novel tool use
potential conflicts: Intellectual Honesty
principle category: professional_virtue
text references: Again, Engineer A did not cite the AI-assisted drafting tools they used to generate the engineering design documents.
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
value basis: Clients, regulators, and the public are entitled to know the methods and tools used to produce professional work so they can evaluate its reliability and the engineer's independent judgment.
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:03:55.305980+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
comment: Professional principle requiring engineers to disclose their use of AI-assisted tools, large language models, or automated drafting software in the preparation of professional work products, enabling clients, reviewers, and the public to assess the provenance and reliability of the work.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-03T14:03:55.305980+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Verification Competence Principle
type: Class
abstract nature: The threshold of required understanding varies with the stakes of the work product and the maturity of the AI tool, requiring contextual judgment about when AI-generated output is sufficiently verified.
confidence: 0.91
derived obligations: Conduct substantive review of AI-generated technical content
derived obligations: Decline to seal work that cannot be independently verified
derived obligations: Understand AI tool functionality before professional use
derived obligations: Verify AI-generated design documents against applicable regulations and site conditions
extensional examples: Engineer conducting only cursory review of AI-generated design documents that omit safety features
extensional examples: Engineer relying on AI synthesis without cross-checking against domain-specific standards
extensional examples: Engineer using new AI drafting tool without understanding its accuracy limitations
operationalization: Requires engineers to understand AI tool capabilities and limitations before use, apply domain expertise to verify outputs, and refuse to seal or submit work they cannot independently validate.
potential conflicts: Availability of mentorship or supervisory review
potential conflicts: Professional Competence
potential conflicts: Time and resource pressures to deliver work products
principle category: professional_virtue
text references: Client W, however, noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
text references: The AI drafting software was new to the market and Engineer A had no previous experience with the tool.
value basis: Professional licensure places responsibility for work product on the engineer, not the tool. AI tools do not hold licenses and cannot bear professional accountability, so the engineer must be competent to evaluate what the tool produces.
discovered in case: 7
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:03:55.305980+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: The AI drafting software was new to the market and Engineer A had no previous experience with the tool.
comment: Professional competence principle requiring engineers who use AI-assisted tools to possess sufficient understanding of those tools to critically evaluate, verify, and take professional responsibility for all AI-generated outputs before incorporating them into sealed or submitted work products.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-03T14:03:55.305980+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Adversarial Data Selection Prohibition Obligation
type: Class
confidence: 0.91
derived from principle: Technical Objectivity Principle
enforcement level: mandatory
monitoring criteria: Report or findings document applies analytical methods consistently to all available data; selection criteria for included data are stated and technically justified.
nspe reference: III.2
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Courts or arbitrators
stakeholders affected: Opposing parties
stakeholders affected: Profession
stakeholders affected: Public
text references: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data. This is an egregious denial of the duties and responsibilities of a professional engineer in any setting, legal, quasi-legal or non-legal.
text references: Facts are not adversarial, even if they may be conflicting.
text references: the select language of the report precludes any interpretation that any or all 90 piles met the factor of safety requirement.
violation consequences: Constitutes an egregious denial of professional duties; undermines the integrity of the engineering profession; may expose the engineer to disciplinary action.
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:35:09.835244+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: The existing Expert Witness Neutrality Obligation and Contradictory Evidence Disclosure Obligation are related but address different duties. The Expert Witness Neutrality Obligation focuses on objectivity and not omitting contradictory evidence in the litigation expert role. The Contradictory Evidence Disclosure Obligation focuses on acknowledging contradictory evidence. This class captures a distinct and more general prohibition: the affirmative duty to refrain from selectively deploying data to serve an adversarial purpose in any professional setting, not only in expert witness roles. The case text explicitly states this applies in legal, quasi-legal, and non-legal settings, making it a broader and independently grounded obligation.
matches existing: false
source text: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data. This is an egregious denial of the duties and responsibilities of a professional engineer in any setting, legal, quasi-legal or non-legal.
comment: Duty of an engineer in any professional setting to refrain from selectively using technical data to defend a client's position, and to present technical findings on the basis of all available evidence rather than choosing data that supports a predetermined conclusion.
subclass of: EthicalObligation
generated at time: 2026-06-04T14:35:09.835244+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Adversarial Engagement Context State
type: Class
action constraints: Must not frame conclusions to impugn another professional without factual basis
action constraints: Must not omit material technical findings that favor the opposing party
activation conditions: Professional retained by one party in an active dispute against another party
activation conditions: Professional's findings are intended to serve as evidence or support in a legal or quasi-legal proceeding
confidence: 0.88
obligation activation: Duty to resist selective use of data to serve client's adversarial interest
obligation activation: Heightened duty of objectivity and completeness
obligation activation: Obligation to include all relevant technical facts regardless of which party they favor
persistence type: inertial
principle transformation: Transforms the general duty of objectivity into a heightened obligation to resist adversarial distortion of technical findings, and activates the duty to include all relevant and pertinent information in professional reports.
state category: conflict
termination conditions: Dispute resolved
termination conditions: Professional withdraws from engagement
termination conditions: Professional's engagement concluded
text references: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data
text references: It is not evident from the facts of the case that Engineer B's selective use of technical fact was inspired by the adversarial circumstance, nor does it matter
text references: an adversarial relationship is established between the municipality and Engineer A to resolve the sharing of a settlement cost
discovered in case: 71
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T14:27:40.288311+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: an adversarial relationship is established between the municipality and Engineer A to resolve the sharing of a settlement cost
comment: State in which a professional is retained to perform technical work within a dispute or litigation context where one party seeks to use the professional's findings to advance its legal or financial position against another party, creating elevated risk that adversarial pressures will distort the professional's selection, presentation, or interpretation of technical facts.
subclass of: ConflictState
generated at time: 2026-06-04T14:27:40.288311+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Adversarial Pressure Resistance Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: Professional engineering practice in litigation or quasi-legal contexts
enables actions: Identify when client interests conflict with complete technical reporting
enables actions: Maintain balanced presentation of technical facts in contested proceedings
enables actions: Refuse selective data use even when it would benefit the retaining party
required for obligations: Adversarial Data Selection Prohibition Obligation
required for obligations: Expert Witness Neutrality Obligation
required for obligations: Faithful Agent Boundary Obligation
skill level: advanced
text references: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data. This is an egregious denial of the duties and responsibilities of a professional engineer in any setting, legal, quasi-legal or non-legal.
text references: Facts are not adversarial, even if they may be conflicting. Adversarial interests, however, are polarizing to the effect that some facts may be preferred by one interest over the other.
text references: It is not evident from the facts of the case that Engineer B's selective use of technical fact was inspired by the adversarial circumstance, nor does it matter.
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:36:09.201106+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class captures the specific competency of resisting adversarial or litigation-context pressure to present findings selectively. Client Boundary Judgment Capability addresses distinguishing legitimate client service from compromising integrity, but does not specifically address the adversarial pressure dynamic and the temptation toward selective data use that arises in contested proceedings. This is a distinct and reusable concept.
matches existing: false
source text: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data. This is an egregious denial of the duties and responsibilities of a professional engineer in any setting, legal, quasi-legal or non-legal.
comment: Ability to recognize when an adversarial or litigation context is creating pressure to present technical findings selectively, and to resist that pressure by maintaining professional objectivity and completeness regardless of client interest alignment.
subclass of: Capability
generated at time: 2026-06-04T14:36:09.201106+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Advisory Conflict Disclosure Obligation
type: Class
confidence: 0.91
derived from principle: Conflict of Interest Disclosure Principle
enforcement level: mandatory
monitoring criteria: Written disclosure to client identifying the engineer's financial or competitive interest in the recommended option prior to or concurrent with the advisory recommendation
nspe reference: III.2.a
obligation type: disclosure
stakeholders affected: Funding agency
stakeholders affected: General public
stakeholders affected: Municipal client
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods.
text references: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects.
violation consequences: Client relies on biased advice without knowledge of the conflict; engineer may face disciplinary action for failure to disclose conflict of interest
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:44:38.157284+00:00
first discovered in case: 14
match confidence: 0.75
match reasoning: This is a specialization of the existing Disclosure Obligation, focused specifically on conflict-of-interest disclosure in an advisory role where the engineer stands to benefit from the recommended option. The existing Disclosure Obligation is the closest match but does not encode the advisory-role and self-interest-in-recommendation specifics. Medium confidence match to parent.
matched ontology class: DisclosureObligation
matched ontology label: Disclosure Obligation
matches existing: true
source text: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods.
comment: Duty of an engineer serving in a purely advisory capacity to disclose to the client any personal, financial, or competitive interest the engineer holds in the outcome of the advisory recommendation, including any interest in being engaged for subsequent services that would flow from the recommended option.
subclass of: DisclosureObligation
scope note: [DisclosureObligation] Requirement to inform stakeholders about conflicts, limitations, or risks (NSPE II.3.a)
generated at time: 2026-06-04T08:44:38.157284+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Advisory Objectivity Maintenance Capability
type: Class
capability category: reasoning
confidence: 0.8
domain specificity: Professional engineering advisory services where the advisor may also be a candidate to perform services under one or more recommended options
enables actions: Recognize when self-interest is influencing the framing of recommendations
enables actions: Separate advisory role from potential service provider role
enables actions: Structure comparative analysis without favoring personally beneficial options
required for obligations: Advisory Conflict Disclosure Obligation
required for obligations: Advisory Role Objectivity Obligation
skill level: advanced
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods
text references: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:39.966147+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
comment: Capability to provide professional advisory recommendations that are free from bias introduced by personal, financial, or competitive interests, including the ability to structure an analysis so that the recommendation reflects the client's interests rather than the advisor's potential benefit.
subclass of: Capability
generated at time: 2026-06-04T08:45:39.966147+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Advisory Role Integrity Principle
type: Class
abstract nature: Requires contextual judgment about when advisory and service-provider interests are sufficiently intertwined to compromise the advisory role, and what structural or disclosure measures are necessary to preserve advisory integrity.
confidence: 0.85
derived obligations: Avoid structuring advice to steer toward self-benefiting outcomes
derived obligations: Disclose anticipated follow-on work interest before or alongside advisory recommendation
derived obligations: Recommend independent review if advisory objectivity is compromised
extensional examples: Cases where a design engineer recommends a project delivery method in which they are the preferred or sole qualified provider
extensional examples: Feasibility advisors who recommend approaches that generate follow-on contracts for themselves
operationalization: Requires engineers to separate advisory and service-provider roles where feasible, disclose the relationship between the recommendation and any anticipated follow-on work, and ensure the client understands that the recommendation may not be independent.
potential conflicts: Conflict of Interest Disclosure Principle
potential conflicts: Loyalty
potential conflicts: Objectivity
principle category: relational
text references: Engineer A currently has no contractual relationship with City B.
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods
text references: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
value basis: The value of professional advisory services depends on the client's reasonable belief that the advisor is acting in the client's interest. When the advisor stands to benefit from the recommendation, the advisory relationship is structurally compromised unless the interest is disclosed and managed.
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:43:46.016802+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A currently has no contractual relationship with City B.
comment: Professional principle requiring engineers who serve in a purely advisory capacity to maintain the independence and objectivity of that role, and not to allow their interest in obtaining subsequent work to shape the content or scope of the advice they provide.
subclass of: RelationalPrinciple
generated at time: 2026-06-04T08:43:46.016802+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Advisory Role Objectivity Obligation
type: Class
confidence: 0.87
derived from principle: Advisory Role Integrity Principle
enforcement level: mandatory
monitoring criteria: Advisory work product demonstrates balanced analysis of all relevant options without promotional content favoring options in which the engineer has a financial interest
nspe reference: II.5
obligation type: ethical
stakeholders affected: General public
stakeholders affected: Municipal client
stakeholders affected: Professional community
text references: Engineer A currently has no contractual relationship with City B.
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
text references: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects.
violation consequences: Client receives biased advice; engineer undermines public trust in the profession; potential disciplinary action for conduct involving dishonesty or conflict of interest
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:44:38.157284+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A currently has no contractual relationship with City B.
comment: Duty of an engineer engaged in a purely advisory capacity to provide objective, unbiased analysis and recommendations that serve the client's interests rather than the engineer's own commercial interests, and to refrain from using the advisory engagement as a vehicle to solicit or position for subsequent work.
subclass of: EthicalObligation
generated at time: 2026-06-04T08:44:38.157284+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Advisory Scope Completeness Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Funding Agency
affected stakeholders: Public
confidence: 0.82
constraint type: ethical
flexibility: hard
mitigation strategies: Disclose any personal interest that might influence option selection
mitigation strategies: Document the basis for any option excluded from analysis
mitigation strategies: Present all approved or available options within the advisory scope
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
text references: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
violation impact: Client makes uninformed decisions based on incomplete information, engineer breaches fiduciary duty, potential disciplinary action for ethics violation
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:47.831992+00:00
first discovered in case: 14
match confidence: 0.72
match reasoning: The selective omission of options is driven by a conflict of interest and partially maps to Conflict of Interest Avoidance. However, the specific mechanism here is the completeness of advisory disclosure rather than merely the existence of a conflict, making this a variant that warrants a distinct class. The closest existing class is Conflict of Interest Avoidance but it does not capture the affirmative duty to present all options.
matched ontology class: Conflict of Interest Avoidance
matched ontology label: Conflict of Interest Avoidance (Constraint)
matches existing: true
source text: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
comment: Ethical constraint requiring that an engineer providing advisory services to a client present all materially relevant options, methods, or alternatives within the scope of the advisory request, prohibiting selective disclosure that omits options the client is entitled to consider, particularly when the omission serves the engineer's own interests.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [Conflict_of_Interest_Avoidance] Constraint established by ethics code provisions
generated at time: 2026-06-04T08:45:47.831992+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Approving Engineer Verification Obligation
type: Class
confidence: 0.83
derived from principle: Professional Competence
enforcement level: mandatory
monitoring criteria: Documented evidence of independent technical review of submitted documents prior to approval, including identification of any deficiencies communicated to the submitting engineer
nspe reference: II.2, II.5.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: Contractors
stakeholders affected: Federal funding agency
stakeholders affected: General public
text references: The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project
text references: much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes
violation consequences: Professional discipline; enabling advancement of deficient documents; potential public safety risk from reliance on approved but deficient designs
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:50:13.568162+00:00
first discovered in case: 85
match confidence: 0.74
match reasoning: Responsible Charge Verification Obligation addresses the duty of a licensed engineer in responsible charge to verify work before sealing. The present obligation applies to a reviewing or approving engineer at a funding agency rather than the originating engineer, and the verification duty runs to independent review of another's submission rather than one's own work. It is a variant of the same underlying competence principle applied to a distinct role context, warranting a separate class.
matched ontology class: Responsible Charge Verification Obligation
matched ontology label: Responsible Charge Verification Obligation
matches existing: true
source text: The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project
comment: Duty of an engineer employed by a funding or regulatory agency to review and approve design documents to conduct a sufficiently thorough and independent technical review to identify material deficiencies, incompleteness, or unbuildable elements before approving the documents, and not to rely solely on the submitting engineer's seal as a substitute for independent verification.
subclass of: CompetenceObligation
scope note: [ResponsibleChargeVerificationObligation] Duty of a licensed engineer in responsible charge to conduct a comprehensive, experience-based verification of all work products before sealing or submitting them, including active involvement in design and development rather than merely reviewing completed documents, so that the engineer can genuinely certify the work meets professional and safety standards.
generated at time: 2026-06-04T16:50:13.568162+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Attribution and Credit Principle
type: Class
abstract nature: Requires interpretation of what constitutes a substantial contribution warranting attribution, and how attribution norms developed for human contributors extend to non-human automated tools.
confidence: 0.85
derived obligations: Cite technical sources referenced or synthesized by AI tools
derived obligations: Disclose AI contributions to clients when those contributions substantially shaped the work
derived obligations: Ensure AI-generated content does not obscure the provenance of underlying technical authority
extensional examples: BER Case 98-3 requirement that engineers acknowledge significant contributions by others
extensional examples: Engineer A failing to include citations of pertinent documents of technical authority in AI-generated report
extensional examples: NSPE Code section III.9 requiring credit for engineering work to those to whom credit is due
operationalization: Requires engineers to disclose when AI tools substantially contributed to a work product, to cite authoritative sources referenced or synthesized by AI, and to ensure the work product accurately represents its intellectual origins.
potential conflicts: AI Tool Disclosure Principle
potential conflicts: Client confidentiality regarding tool selection
potential conflicts: Intellectual Honesty in Authorship Principle
principle category: professional_virtue
text references: BER Case 98-3 emphasized that engineers must acknowledge significant contributions by others. AI, while not a human contributor, fundamentally shaped the report and design documents, warranting disclosure under Code section III.9.
text references: Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
text references: The facts do not indicate the AI-generated report included citations of pertinent documents of technical authority.
value basis: Accurate attribution preserves the integrity of the professional record, enables quality assessment by clients and reviewers, and respects the intellectual contributions of others including the developers of tools that generate substantive content.
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:08:23.434917+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
comment: Professional virtue principle requiring engineers to give appropriate credit for contributions to their work products, including contributions from AI tools, automated systems, or other non-engineer sources that substantially shaped the content or design, so that recipients can accurately assess the provenance and intellectual basis of the work.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-03T14:08:23.434917+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

BER Case Precedent
type: Class
authority source: NSPE Board of Ethical Review
confidence: 0.97
extensional function: Grounds abstract ethical principles in concrete prior decisions, enabling pattern-based analogical reasoning for similar fact situations.
resource category: case_precedent
text references: In BER Case 18-10, Engineer A was the lead engineer on an independent external review
text references: In BER Case 96-8, Engineer A was a peer reviewer serving as part of an organized peer-review program.
text references: It is helpful to consider how the BER has addressed peer review issues in the past.
usage context: Conflict of interest assessment
usage context: Peer review ethics analysis
usage context: Public safety obligation determination
discovered in case: 15
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-02T19:52:49.379118+00:00
first discovered in case: 15
match confidence: 0.97
match reasoning: BER Case Precedent is a specific subtype of the canonical Case Precedent class. The BER qualifier narrows the authority source but the category is identical.
matched ontology class: CasePrecedent
matched ontology label: Case Precedent
matches existing: true
source text: It is helpful to consider how the BER has addressed peer review issues in the past.
comment: A documented case decision issued by the NSPE Board of Ethical Review that provides analogical reasoning patterns and precedential guidance for resolving professional ethics questions in engineering practice.
subclass of: CasePrecedent
scope note: [CasePrecedent] Concrete instances that exemplify principle application
generated at time: 2026-06-02T19:52:49.379118+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Bid Adequacy Reflection Constraint
type: Class
affected stakeholders: Design Engineer
affected stakeholders: Engineer-Contractor
affected stakeholders: Owner
affected stakeholders: Public
confidence: 0.85
constraint type: ethical
flexibility: hard
mitigation strategies: Decline to bid if deficiencies cannot be adequately quantified or addressed
mitigation strategies: Include bid items for additional services required to complete deficient work
mitigation strategies: Request clarification from owner or design engineer before bidding
text references: Engineer C could have requested further clarification from the owner or Engineer A in order to better understand the engineering drawings
text references: Engineer C had no one to fault but himself for the problems Engineer C encountered in attempting to build the project
text references: Engineer C submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involved
text references: If the engineering documents were incomplete or inadequate, then Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work for the benefit of the owner
violation impact: Engineer-contractor bears responsibility for losses arising from unbuildable contract; professional ethics violation for submitting bid that does not reflect known document deficiencies
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:56:15.795068+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: If the engineering documents were incomplete or inadequate, then Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work for the benefit of the owner
comment: Ethical and professional constraint requiring that an engineer-contractor who identifies deficiencies, incompleteness, or unbuildable elements in bidding documents must either include appropriate bid items reflecting the cost of additional work needed to complete the project, request clarification from the owner or design engineer before submitting a bid, or decline to bid. Submitting a low bid while knowing or having reasonable grounds to know that the documents are inadequate, without reflecting that inadequacy in the bid, constitutes a professional ethics violation.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T16:56:15.795068+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Bid Adequacy Reflection Obligation
type: Class
confidence: 0.85
derived from principle: Bid Transparency Principle
enforcement level: mandatory
monitoring criteria: Whether the bid included line items or qualifications addressing identified document deficiencies, or whether the bidder sought clarification before submitting
nspe reference: II.2, III.2
obligation type: ethical
stakeholders affected: Design engineer
stakeholders affected: Funding agency
stakeholders affected: General public
stakeholders affected: Owner
text references: Engineer C could have requested further clarification from the owner or Engineer A in order to better understand the engineering drawings.
text references: Engineer C had no one to fault but himself for the problems Engineer C encountered in attempting to build the project. Engineer C submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involved.
text references: If the engineering documents were incomplete or inadequate, then Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work for the benefit of the owner.
violation consequences: Professional discipline; financial loss from underbid contract; inability to claim relief for self-created construction difficulties
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:54:40.172403+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: If the engineering documents were incomplete or inadequate, then Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work for the benefit of the owner.
comment: Duty of an engineer-contractor who identifies deficiencies, incompleteness, or unbuildable elements in bidding documents during bid review to ensure that the submitted bid reflects those deficiencies, either by including appropriate bid items for additional services required to complete the work or by seeking clarification from the owner or design engineer before submitting, rather than submitting a low bid that ignores known inadequacies and then attributing resulting construction problems to the design documents.
subclass of: EthicalObligation
generated at time: 2026-06-04T16:54:40.172403+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Bid Document Adequacy Assessment Capability
type: Class
capability category: domain_specific
confidence: 0.88
domain specificity: Civil and structural engineering in public works construction contracting
enables actions: Identify unbuildable or underspecified design elements
enables actions: Incorporate identified deficiencies into bid pricing
enables actions: Make informed decision about whether to submit a bid
enables actions: Request clarification from owner or design engineer before bidding
enables actions: Review bidding documents for completeness and buildability
required for obligations: Bid Adequacy Reflection Obligation
required for obligations: Contractor Deficiency Notification Obligation
skill level: advanced
text references: Engineer C had an opportunity to review the bidding documents which included appropriate engineering drawings, plans, and specifications. From such a review, Engineer C should have had a sense of what would be necessary to complete the project.
text references: Engineer C had the necessary background and experience to carefully evaluate the engineering drawings as well as other aspects of the work in order to make an informed decision as to whether to bid on the project.
text references: If the engineering documents were incomplete or inadequate, then Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work for the benefit of the owner.
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:55:58.579791+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer C had an opportunity to review the bidding documents which included appropriate engineering drawings, plans, and specifications. From such a review, Engineer C should have had a sense of what would be necessary to complete the project.
comment: Technical capability of an engineer-contractor to critically evaluate bidding documents, including engineering drawings, plans, and specifications, to determine whether they are complete, buildable, and adequate to support a construction bid, and to identify deficiencies that should be reflected in bid pricing or clarification requests before submitting a bid.
subclass of: Capability
generated at time: 2026-06-04T16:55:58.579791+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Bid Transparency Principle
type: Class
abstract nature: Principle requiring engineers in contractor roles to apply their professional judgment to bidding documents and to communicate identified deficiencies through the bidding process rather than suppressing them in pursuit of a competitive advantage.
confidence: 0.85
derived obligations: Include bid items for additional services when documents are incomplete
derived obligations: Refrain from submitting bids that conceal known document inadequacies
derived obligations: Request clarification from owner or design engineer before bidding on deficient documents
extensional examples: BER case involving Engineer C who bid on an unbuildable dam project without disclosing document inadequacies in the bid
operationalization: Requires engineer-contractors to include bid items for additional services when documents are incomplete, to request clarification before bidding when documents are ambiguous, and to refrain from submitting artificially low bids that conceal known document deficiencies.
potential conflicts: Competitive bidding pressures
potential conflicts: Faithful Agent Duty Principle
principle category: professional_virtue
text references: Engineer C could have requested further clarification from the owner or Engineer A in order to better understand the engineering drawings
text references: Engineer C had no one to fault but himself for the problems Engineer C encountered in attempting to build the project. Engineer C submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involved
text references: If the engineering documents were incomplete or inadequate, then Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work for the benefit of the owner
value basis: Honesty and professional integrity in commercial transactions, protection of the owner from uninformed contract awards, and professional accountability for the consequences of knowingly accepting deficient work conditions.
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:53:07.457315+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: If the engineering documents were incomplete or inadequate, then Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work for the benefit of the owner
comment: Professional principle requiring an engineer-contractor who identifies deficiencies, ambiguities, or inadequacies in bidding documents to reflect those deficiencies in the bid submission, either by including appropriate bid items for additional services required to remedy the deficiencies or by seeking clarification from the owner or design engineer before submitting. An engineer-contractor who submits a low bid while knowingly accepting the risks of inadequate documents cannot later attribute resulting construction difficulties to others.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T16:53:07.457315+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Buildability Assessment Capability
type: Class
capability category: domain_specific
confidence: 0.87
domain specificity: Civil and structural engineering design for infrastructure construction projects
enables actions: Assess whether documents are sufficient for bidding and construction
enables actions: Determine whether design elements are constructable as specified
enables actions: Identify missing design detail in drawings and specifications
required for obligations: Approving Engineer Verification Obligation
required for obligations: Contractor Deficiency Notification Obligation
required for obligations: Engineer A Competence Dam Drawings
skill level: advanced
text references: Engineer A generally agrees with Hi-Lo's characterization
text references: Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:51:18.309339+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes.
comment: Technical capability to evaluate engineering drawings and specifications for constructability, including the ability to identify elements that are unbuildable as designed, assess whether sufficient design detail is present for construction, and determine whether the documents are adequate for contractor use.
subclass of: Capability
generated at time: 2026-06-04T16:51:18.309339+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

CADD-Assisted Document Preparation State
type: Class
action constraints: Engineer may not seal documents prepared by others without exercising genuine direction and control
action constraints: Engineer must have sufficient technical knowledge to review and verify CADD outputs
activation conditions: Documents are prepared for signing and sealing by a registered professional engineer
activation conditions: Engineer directs others who use CADD tools to prepare documents
activation conditions: Engineer uses CADD tools to prepare documents personally
confidence: 0.82
obligation activation: Duty to exercise direction and control over subordinates using CADD tools
obligation activation: Duty to maintain responsible charge over CADD-generated documents
obligation activation: Duty to verify accuracy and completeness of documents before sealing
persistence type: inertial
principle transformation: Transforms the general duty of responsible charge into specific obligations regarding oversight of technology-assisted document preparation, whether the engineer is the direct author or the supervising professional.
state category: competence
termination conditions: Documents are signed and sealed and work is complete
termination conditions: Engineer withdraws from responsible charge of the work
text references: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system
text references: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control
discovered in case: 120
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:05:02.078098+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system
comment: State in which engineering documents are prepared using computer-aided design and drafting (CADD) systems, either by the engineer of record personally or by others working under that engineer's direction and control, creating conditions in which the signing and sealing engineer must demonstrate sufficient engagement with and oversight of the work to satisfy responsible charge requirements.
subclass of: CompetenceState
generated at time: 2026-06-04T18:05:02.078098+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

CADD Authorship Verification Capability
type: Class
capability category: awareness
confidence: 0.72
domain specificity: Professional engineering practice involving CADD-assisted document production
enables actions: Confirm personal authorship of CADD-produced documents before sealing
enables actions: Decline to seal documents not personally prepared without adequate supervisory review
enables actions: Distinguish self-prepared documents from documents prepared by subordinates
required for obligations: Responsible Charge Seal Obligation
required for obligations: Technology Tool Non-Substitution Obligation
skill level: intermediate
text references: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system.
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:08:23.109387+00:00
first discovered in case: 120
match confidence: 0.75
match reasoning: AI Authorship Representation Capability covers the concept of accurately representing the intellectual origin and authorship of professional work products, including distinguishing between tool-generated content and original professional work. CADD authorship verification is a variant of this concept applied to CADD systems rather than AI, but the core capability is the same: ensuring the seal accurately reflects who actually prepared the document. Medium confidence match as a variant of the existing class.
matched ontology class: AI Authorship Representation Capability
matched ontology label: AI Authorship Representation Capability
matches existing: true
source text: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system.
comment: Capability of a licensed professional engineer to verify that documents produced using a CADD system were personally prepared by the engineer before applying a professional seal, including the ability to distinguish between documents the engineer authored directly and documents produced by others, and to ensure the seal accurately represents the engineer's personal authorship.
subclass of: Capability
scope note: [AIAuthorshipRepresentationCapability] Capability to accurately represent the intellectual origin and authorship of professional work products, including the ability to distinguish between AI-generated content and original professional work and to avoid misrepresenting AI output as one's own independent analysis.
generated at time: 2026-06-04T18:08:23.109387+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

CADD Competence Assurance State
type: Class
action constraints: Engineer must not incorporate CADD-generated solutions that the engineer does not fully understand
action constraints: Engineer must not treat CADD output as a substitute for professional competence
activation conditions: CADD system generates design solutions that the engineer has not independently derived
activation conditions: Engineer uses CADD or similar automated design systems to prepare engineering documents
confidence: 0.87
obligation activation: Obligation to ensure CADD output is understood and not merely accepted on faith
obligation activation: Obligation to exercise independent professional judgment rather than deferring to system output
obligation activation: Obligation to verify personal competence with the specific CADD system in use
persistence type: inertial
principle transformation: Transforms the general competence principle into a specific obligation to understand the tools being used and to maintain independent judgment when those tools generate design solutions.
state category: competence
termination conditions: Engineer ceases use of CADD systems on the project
termination conditions: Engineer demonstrates sufficient proficiency and understanding of system limitations
text references: CADD utilized beyond its ability to serve as a valuable tool has a propensity to be utilized as a crutch or substitute for judgement
text references: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology
discovered in case: 120
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T18:05:44.602441+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology
comment: State in which a professional engineer uses computer-aided drafting and design systems to prepare or assist in preparing engineering documents, creating an obligation to demonstrate sufficient background, education, and training to understand the capabilities and limitations of those systems, and to ensure that the systems serve as tools augmenting professional judgment rather than substitutes for it.
subclass of: CompetenceState
generated at time: 2026-06-04T18:05:44.602441+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

CADD Document Sealing Engineer
type: Class
confidence: 0.82
role category: provider_client
text references: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system
text references: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control
discovered in case: 120
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:04:45.511331+00:00
first discovered in case: 120
match confidence: 0.78
match reasoning: Responsible Charge Engineer in the ontology captures the obligation of active engagement and personal accountability over work product, which is the core obligation at issue when an engineer seals CADD-produced documents. However, the CADD-specific context and the distinction between self-prepared versus directed-others work adds a specialization not fully expressed by the existing class, so a new class is warranted while acknowledging the parent relationship.
matched ontology class: Responsible Charge Engineer
matched ontology label: Responsible Charge Engineer
matches existing: true
source text: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system
comment: A licensed professional engineering role in which the practitioner signs and seals engineering documents produced using computer-aided design and drafting (CADD) systems, bearing full professional accountability for the technical content of those documents regardless of whether the practitioner personally operated the CADD system or directed others to do so.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [ResponsibleChargeEngineer] A licensed professional engineering role in which the practitioner bears formal responsible charge over a project or work product, meaning they must be actively engaged in the engineering process from conception to completion, personally make or directly supervise all engineering decisions, and cannot satisfy this obligation by reviewing completed documents after the fact without involvement in design and development.
generated at time: 2026-06-04T18:04:45.511331+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

CADD Proficiency Competence Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.88
constraint type: competence
flexibility: hard
mitigation strategies: Engage qualified assistance when CADD capabilities exceed the engineer's understanding
mitigation strategies: Limit reliance on CADD outputs to areas within the engineer's demonstrated competence
mitigation strategies: Obtain formal training in CADD systems before use on professional projects
text references: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
text references: The key point is that the engineer must utilize such systems to assist the engineer in the performance of professional services and not employ such systems as a replacement for professional competence and expertise.
violation impact: Engineer may seal documents reflecting outputs the engineer does not understand, exposing the public to undetected design errors and exposing the engineer to professional liability and disciplinary action.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:13:02.665367+00:00
first discovered in case: 120
match confidence: 0.82
match reasoning: The existing Unfamiliar Tool Competence Constraint captures the same core concept: limiting an engineer's permissible use of a tool with which they lack sufficient experience or understanding, and requiring adequate competence before reliance on outputs. The CADD-specific framing here is a variant of that general class applied to computer-aided design systems. Medium confidence match because the existing class is general enough to subsume this, but the CADD context and the BER's specific articulation of proficiency requirements add detail not fully expressed in the existing label.
matched ontology class: Unfamiliar Tool Competence Constraint
matched ontology label: Unfamiliar Tool Competence Constraint
matches existing: true
source text: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
comment: Competence constraint requiring that a professional engineer who uses computer-aided drafting and design systems in the preparation of engineering documents possess sufficient background, education, and training to be proficient with the dynamics of those systems, including an understanding of their limitations, so that the systems serve as tools under professional direction rather than substitutes for engineering judgment.
subclass of: CompetenceConstraint
subclass of: InviolableConstraint
scope note: [UnfamiliarToolCompetenceConstraint] Competence constraint limiting an engineer's permissible use of a tool, technology, or method with which they lack sufficient experience or understanding, requiring that the engineer either acquire adequate competence before use, limit reliance on the tool's outputs, or obtain qualified assistance, so that professional work products meet required standards.
generated at time: 2026-06-04T18:13:02.665367+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

CADD Proficiency Competence Obligation
type: Class
confidence: 0.88
derived from principle: AI Verification Competence Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer has received training in the specific CADD system used and can identify and correct system-generated errors
nspe reference: II.2
obligation type: competence
stakeholders affected: Clients
stakeholders affected: Employers
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
text references: The key requirement is that an engineer possesses sufficient competence, assumes full responsibility for the work product and carefully directs, controls and reviews the material prepared under the engineer's responsible charge.
violation consequences: Potential professional liability; ethical violation under NSPE II.2; risk of sealing documents the engineer does not genuinely understand
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:11:22.208486+00:00
first discovered in case: 120
match confidence: 0.78
match reasoning: This is a specialization of the general Competence Obligation, narrowed to the specific context of CADD and computer-assisted design tool proficiency. The existing Competence Obligation covers the general duty to practice only within areas of competence, and this obligation applies that duty to the specific technological context of CADD systems and their limitations.
matched ontology class: CompetenceObligation
matched ontology label: Competence Obligation
matches existing: true
source text: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
comment: Duty of a licensed engineer who uses CADD or similar computer-assisted design systems in the preparation of professional work products to possess sufficient background, education, and training to be proficient with the dynamics of those systems, including their limitations, so that the engineer can exercise genuine professional judgment rather than relying on system outputs as a substitute for competence.
subclass of: CompetenceObligation
scope note: [CompetenceObligation] Requirement to perform services only in areas of competence (NSPE II.2)
generated at time: 2026-06-04T18:11:22.208486+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Chief Engineer Sealing Supervisor
type: Class
confidence: 0.82
role category: provider_client
text references: He was consulted about technical questions and provided answers and direction in these matters
text references: he was involved in helping to establish the concept, the design requirements, and the review elements of the design or project status as the design progressed
text references: the chief engineer within a large engineering firm affixed his seal to some of the plans prepared by registered engineers working under his general direction
discovered in case: 120
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T18:05:22.911138+00:00
first discovered in case: 120
match confidence: 0.82
match reasoning: The chief engineer sealing supervisor is a specialization of Responsible Charge Engineer: the practitioner bears formal responsible charge over work prepared by others and must be actively engaged in direction and control, which is precisely the definition of Responsible Charge Engineer. The large-firm supervisory context is case-specific detail, not a distinct role type.
matched ontology class: Responsible Charge Engineer
matched ontology label: Responsible Charge Engineer
matches existing: true
source text: the chief engineer within a large engineering firm affixed his seal to some of the plans prepared by registered engineers working under his general direction
comment: A senior licensed professional engineering role in which the practitioner holds the position of chief engineer within a large engineering firm, affixes their seal to plans prepared by registered and non-registered engineers working under their general direction, and bears professional accountability for those documents even when the volume and complexity of concurrent projects makes detailed personal review of every drawing impractical. The role requires that the practitioner be sufficiently engaged in concept development, design requirements, and progressive review to exercise meaningful direction and control, and must check and review plans in some detail before sealing.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [ResponsibleChargeEngineer] A licensed professional engineering role in which the practitioner bears formal responsible charge over a project or work product, meaning they must be actively engaged in the engineering process from conception to completion, personally make or directly supervise all engineering decisions, and cannot satisfy this obligation by reviewing completed documents after the fact without involvement in design and development.
generated at time: 2026-06-04T18:05:22.911138+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Client Budget Pressure Resistance Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: Professional engineering practice involving client-directed omission of safety measures
enables actions: Communicate the professional basis for refusing to continue work without recommended safeguards
enables actions: Decline to proceed with a project when the client insists on omitting required protective measures
enables actions: Recognize when client budget objections to safety measures cross the threshold requiring work refusal
required for obligations: Client Economic Pressure Refusal Obligation
required for obligations: Client Refusal Regulatory Reporting Obligation
skill level: advanced
text references: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations.
text references: Despite Engineer L's concerns, Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.88
match reasoning: Client Economic Pressure Resistance Capability is defined as the capability to recognize when a client's refusal to implement professionally recommended safety measures, motivated by cost or economic concerns, creates an obligation to cease work rather than continue, and to act on that obligation by declining to proceed despite client pressure. This is essentially identical to the capability required in this case. The match is high confidence.
matched ontology class: Client Economic Pressure Resistance Capability
matched ontology label: Client Economic Pressure Resistance Capability
matches existing: true
source text: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations.
comment: Capability to recognize when a client's refusal to implement professionally recommended safety or environmental protection measures, motivated by budget or financial constraints, creates an obligation to cease work rather than continue, and to act on that obligation by declining to proceed despite client pressure to continue without the recommended safeguards.
subclass of: Capability
scope note: [ClientEconomicPressureResistanceCapability] Capability to recognize when a client's refusal to implement professionally recommended safety measures, motivated by cost or economic concerns, creates an obligation to cease work rather than continue, and to act on that obligation by declining to proceed despite client pressure.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Conduct Monitoring Principle
type: Class
abstract nature: Open-textured obligation requiring judgment about what constitutes sufficient remediation and how long monitoring must continue before the engineer's obligation is discharged.
confidence: 0.87
derived obligations: Contact client upon discovery of violation
derived obligations: Escalate to regulatory authorities if client fails to remediate
derived obligations: Monitor client compliance with applicable law
derived obligations: Specify required remedial actions
extensional examples: NSPE BER Case 97-13 requiring Engineer A to follow through to see that correct follow-up action was taken by the public agency
extensional examples: NSPE BER current case requiring Engineer A to monitor wetland fill remediation until satisfied the violation is corrected
operationalization: Requires engineers to contact the client, identify the violation, specify required remedial steps, and continue oversight until compliance is verified, escalating to authorities if the client fails to act.
potential conflicts: Client Data Confidentiality Principle
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Post-Engagement Client Conduct Disclosure Principle
principle category: professional_virtue
text references: Engineer A had an obligation to follow through to see that correct follow-up action was taken by the public agency.
text references: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
value basis: An engineer's public welfare obligation is not discharged by merely notifying a client of a violation; the obligation persists until the risk to public resources or safety is actually resolved.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:32:47.556599+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
comment: Professional principle requiring an engineer who has identified a client's violation of law or regulation to monitor the client's remedial actions until the engineer is sufficiently satisfied that the violation has been corrected, rather than treating a client's promise of remediation as a substitute for actual compliance.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T17:32:47.556599+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Client Consent Independence Capability
type: Class
capability category: reasoning
confidence: 0.84
domain specificity: Public safety engineering with client relationship management
enables actions: Distinguish between obligations requiring client consent and those that do not
enables actions: Proceed with regulatory notification without client consent
enables actions: Resist client pressure to delay or condition safety reporting on client approval
required for obligations: Client Consent Independence Obligation
required for obligations: Engineers A B Client Consent Independence
skill level: advanced
text references: as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:39.466339+00:00
first discovered in case: 76
match confidence: 0.75
match reasoning: Public Safety Paramount Judgment Capability covers recognizing that the obligation to hold paramount public safety takes precedence over duties of loyalty to a client. The present capability is a specific application of that broader judgment, focused on the procedural dimension that client consent is not a prerequisite for safety reporting. It is a variant of the existing class at medium confidence.
matched ontology class: Public Safety Paramount Judgment Capability
matched ontology label: Public Safety Paramount Judgment Capability
matches existing: true
source text: as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required.
comment: Capability to recognize that the professional obligation to report a public health or safety risk to regulatory authorities does not require the client's consent or approval, and to proceed with required reporting and regulatory notification without seeking or waiting for client permission.
subclass of: Capability
scope note: [PublicSafetyParamountJudgmentCapability] Capability to recognize that the professional obligation to hold paramount the safety, health, and welfare of the public takes precedence over duties of loyalty to a client or former client, and to act on that recognition by taking affirmative steps such as regulatory reporting even when doing so is adverse to the client's interests.
generated at time: 2026-06-05T11:29:39.466339+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Client Consent Independence Obligation
type: Class
confidence: 0.87
derived from principle: Public Welfare Paramountcy Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer proceeded with regulatory notification without seeking client approval, and that the notification was not delayed pending client consent.
nspe reference: I.1, II.1.a
obligation type: safety
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: State regulatory agency
text references: As Engineers A and B are required to hold paramount the safety, health, and welfare of the public, and as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required.
violation consequences: Conditioning safety reporting on client consent allows the client to suppress mandatory disclosures and leaves the public exposed to identified health and safety risks.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:28:12.343728+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: As Engineers A and B are required to hold paramount the safety, health, and welfare of the public, and as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required.
comment: Duty of an engineer to proceed with required safety reporting and regulatory notification without seeking or waiting for the client's consent, recognizing that the paramount duty to public welfare does not depend on client authorization and that client consent is not a precondition for fulfilling mandatory safety reporting obligations.
subclass of: SafetyObligation
generated at time: 2026-06-05T11:28:12.343728+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Client Data Confidentiality Capability
type: Class
capability category: awareness
confidence: 0.82
domain specificity: Professional engineering practice involving AI and cloud-based tools
enables actions: Assess data sensitivity before uploading to external platforms
enables actions: Identify when tool use constitutes placing information in the public domain
enables actions: Obtain client consent for use of proprietary information in AI tools
required for obligations: Client Data Confidentiality Obligation
skill level: intermediate
text references: Per Code section II.1.c, confidential information can only be shared with prior consent of the Client.
text references: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:06.673267+00:00
first discovered in case: 7
match confidence: 0.72
match reasoning: The existing Confidentiality Scope Reasoning Capability addresses reasoning about limits of confidentiality obligations, but that class focuses on distinguishing between protecting review contents and procedurally improper conduct. This capability is more specifically about recognizing when tool use exposes client data to public domains and obtaining consent, which is a distinct application of confidentiality reasoning in the AI tool context. A medium-confidence match to the parent concept is appropriate, but the AI-tool-specific data upload dimension is sufficiently distinct to warrant a new class.
matched ontology class: Confidentiality Scope Reasoning Capability
matched ontology label: Confidentiality Scope Reasoning Capability
matches existing: true
source text: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
comment: Capability to recognize when professional activities involving third-party platforms or tools would expose client confidential or proprietary information to unauthorized parties, and to obtain appropriate consent or take protective measures before proceeding.
subclass of: Capability
scope note: [ConfidentialityScopeReasoningCapability] Capability to reason about the limits of confidentiality obligations, distinguishing between protecting the contents of a review and using confidentiality as a basis for procedurally improper conduct such as covert review.
generated at time: 2026-06-03T14:11:06.673267+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Client Data Confidentiality Obligation
type: Class
confidence: 0.92
derived from principle: Client Data Confidentiality Principle
enforcement level: mandatory
monitoring criteria: Documented client consent prior to any upload of proprietary data to external or public-domain tools
nspe reference: II.1.c
obligation type: confidentiality
stakeholders affected: Client
stakeholders affected: Engineer
stakeholders affected: Regulatory bodies
text references: Per Code section II.1.c, confidential information can only be shared with prior consent of the Client.
text references: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
violation consequences: Breach of client confidentiality; potential legal liability; disciplinary action by licensing board
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:09:34.826300+00:00
first discovered in case: 7
match confidence: 0.8
match reasoning: This is a specific variant of the existing Confidentiality Obligation, narrowed to the context of uploading client data into public-domain AI tools without consent. The existing class covers duty to protect confidential information generally; this specialization addresses the AI-tool transmission vector.
matched ontology class: ConfidentialityObligation
matched ontology label: Confidentiality Obligation
matches existing: true
source text: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
comment: Duty of an engineer to refrain from uploading or transmitting client-provided confidential or proprietary information into public-domain tools, platforms, or interfaces without prior written consent from the client, recognizing that such transmission is equivalent to placing the information in the public domain.
subclass of: ConfidentialityObligation
scope note: [ConfidentialityObligation] Duty to protect confidential information of clients or employers (NSPE III.4)
generated at time: 2026-06-03T14:09:34.826300+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Client Data Confidentiality Principle
type: Class
abstract nature: Open-textured obligation requiring engineers to assess not only intentional disclosure but also constructive or incidental disclosure arising from tool selection and workflow decisions.
confidence: 0.88
derived obligations: Assess data exposure risks before selecting AI or cloud-based tools
derived obligations: Inform clients of tool limitations regarding data privacy
derived obligations: Obtain client consent before uploading proprietary information to external platforms
extensional examples: Engineer A uploading Client W proprietary site data into a public-domain open-source AI interface without client consent
extensional examples: NSPE Code section II.1.c requiring prior consent before sharing confidential client information
operationalization: Requires engineers to evaluate whether any tool, platform, or workflow exposes client data to third parties or public access, and to obtain explicit client consent before using such tools with confidential information.
potential conflicts: AI Tool Disclosure Principle
potential conflicts: Professional Competence (use of best available tools)
principle category: relational
text references: Per Code section II.1.c, confidential information can only be shared with prior consent of the Client.
text references: The facts here do not indicate Engineer A obtained permission from Client W to use the private information in the public domain.
text references: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
value basis: Clients entrust engineers with sensitive project information on the assumption that it will be protected; unauthorized disclosure, even unintentional, violates that trust and may cause competitive, legal, or reputational harm.
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:08:23.434917+00:00
first discovered in case: 7
match confidence: 0.78
match reasoning: The existing Confidentiality Principle covers the general obligation to protect client information. This instance adds a domain-specific qualifier about constructive disclosure through AI tool use, which is a meaningful variant warranting a more specific class rather than a direct match. The existing Confidentiality Principle does not address the incidental-disclosure-via-tool-selection scenario, so a variant class is appropriate.
matched ontology class: ConfidentialityPrinciple
matched ontology label: Confidentiality Principle
matches existing: true
source text: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
comment: Relational principle requiring engineers to protect client-provided information from unauthorized disclosure, including disclosure that occurs incidentally through the use of third-party tools or platforms that place private data in publicly accessible domains, unless the client has given prior informed consent.
subclass of: RelationalPrinciple
scope note: [ConfidentialityPrinciple] Must be balanced against public safety obligations and legal disclosure requirements.
generated at time: 2026-06-03T14:08:23.434917+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Client Data Consent Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Third parties with access to exposed data
confidence: 0.88
constraint type: confidentiality
flexibility: hard
mitigation strategies: Anonymize or de-identify data before use in external tools
mitigation strategies: Obtain written client consent before uploading data to any external platform
mitigation strategies: Use only secure, private, client-approved systems
text references: Per Code section II.1.c, confidential information can only be shared with prior consent of the Client.
text references: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain. The facts here do not indicate Engineer A obtained permission from Client W to use the private information in the public domain.
violation impact: Breach of client confidentiality, exposure of proprietary information to public domain, loss of client trust, potential legal liability
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:08.316438+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Per Code section II.1.c, confidential information can only be shared with prior consent of the Client.
comment: Confidentiality constraint prohibiting an engineer from sharing, uploading, or otherwise transmitting confidential client information to any external system or third party without first obtaining the client's explicit prior consent, regardless of the purpose or perceived benefit of the transmission.
subclass of: ConfidentialityConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-03T14:11:08.316438+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Client Data Exposed State
type: Class
action constraints: Must not continue using the platform with client data absent consent
action constraints: Must not represent the work product as fully confidential if data was exposed
activation conditions: Confidential client data uploaded to an open or third-party platform
activation conditions: No prior client consent obtained for such use
confidence: 0.88
obligation activation: Duty to assess and mitigate downstream confidentiality risks
obligation activation: Duty to cease further uploads without consent
obligation activation: Duty to notify client of the exposure
persistence type: inertial
principle transformation: Transforms the general confidentiality principle into a concrete obligation to notify the client and obtain consent before using open-domain AI tools with private client data.
state category: information
termination conditions: Client is notified and provides retroactive consent
termination conditions: Data is confirmed removed or isolated from public access
termination conditions: Remediation agreement reached with client
text references: The facts here do not indicate Engineer A obtained permission from Client W to use the private information in the public domain.
text references: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
discovered in case: 7
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-03T14:01:36.958645+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: When Engineer A uploaded Client W's information into the AI open-source interface, this was tantamount to placing the Client's private information in the public domain.
comment: State in which a professional has uploaded or transmitted confidential client information to a third-party platform or public-domain system without obtaining prior client consent, creating a breach of confidentiality obligations and potential loss of data control regardless of whether harm has yet materialized.
subclass of: InformationState
generated at time: 2026-06-03T14:01:36.958645+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Client Defense Bias State
type: Class
action constraints: Must not structure conclusions solely to support client's litigation position
action constraints: Must not submit a report that omits material technical findings favorable to the opposing party
activation conditions: Professional selectively uses data in a manner that serves the client's adversarial interest
activation conditions: Professional's conclusions are structured to impugn an opposing party rather than to resolve a technical question
activation conditions: Professional's report omits material facts that would undermine the client's position
confidence: 0.87
obligation activation: Duty to avoid misrepresentation through omission
obligation activation: Duty to correct the incomplete or biased report
obligation activation: Obligation to include all relevant and pertinent information
persistence type: inertial
principle transformation: Transforms the general duty of honesty and objectivity into a specific prohibition on advocacy-driven omission of technical facts, and activates obligations of completeness and truthfulness in professional reports.
state category: conflict
termination conditions: Engagement concluded
termination conditions: Professional revises report to include all material facts
termination conditions: Professional withdraws from engagement
text references: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data
text references: as an engineering document the report is incomplete and does a disservice to Engineer B's client municipality by potentially misdirecting a conclusion
text references: the report appears to serve no purpose except to impugn Engineer A, or to support the original testimony of the municipality's expert witness
discovered in case: 71
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T14:27:40.288311+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data
comment: State in which a professional has oriented their technical work product toward defending or advancing the client's position in a dispute rather than providing an objective and complete professional analysis, resulting in selective presentation of data, omission of unfavorable findings, and a report that serves advocacy rather than professional truth-telling.
subclass of: ConflictState
generated at time: 2026-06-04T14:27:40.288311+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Client Deferral of Compliance State
type: Class
action constraints: Professional may not simply defer to client's business judgment when public safety is at stake
action constraints: Professional must evaluate whether continued participation without safeguards is ethically permissible
activation conditions: Client explicitly declines to implement recommended safeguards
activation conditions: Client states intention to address compliance only if later required
activation conditions: Professional has notified client of a risk and applicable regulatory requirements
confidence: 0.85
obligation activation: Duty to consider withdrawal from the engagement if safety cannot be assured
obligation activation: Duty to protect public health, safety, and welfare
obligation activation: Obligation to assess whether reporting to regulatory authorities is required
persistence type: inertial
principle transformation: Transforms the general duty to protect public safety into a specific obligation to evaluate escalation options, including regulatory reporting and withdrawal, when a client explicitly refuses to implement safety measures and defers compliance to an indefinite future.
state category: conflict
termination conditions: Client agrees to implement protective measures
termination conditions: Professional withdraws from engagement
termination conditions: Regulatory authority intervenes
termination conditions: Risk is otherwise mitigated
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed
text references: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations
discovered in case: 8
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T02:15:59.482935+00:00
first discovered in case: 8
match confidence: 0.78
match reasoning: The existing Client Override of Safety Recommendation State captures the situation where a client directs the professional to proceed without implementing a safety recommendation. The present state adds the specific element of the client explicitly deferring compliance to a future contingency rather than simply overriding the recommendation, which creates a distinct posture of deliberate regulatory non-engagement. The match is medium-confidence because the core structure is the same but the deferral-of-compliance framing is a meaningful variant.
matched ontology class: Client Override of Safety Recommendation State
matched ontology label: Client Override of Safety Recommendation State
matches existing: true
source text: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations
comment: State in which a client, having been informed of a confirmed or qualitatively assessed risk and of applicable regulatory requirements, explicitly declines to implement recommended protective measures and instead states an intention to address compliance issues only if and when required in the future, creating a condition in which the professional's safety and compliance obligations remain active while the client's posture is one of deliberate deferral.
subclass of: ConflictState
scope note: [ClientOverrideofSafetyRecommendationState] State in which a client has been informed of a professional's safety recommendation and has explicitly directed the professional to proceed without implementing that recommendation, citing cost or other business constraints, creating a direct tension between the client's authority over project scope and the professional's duty to protect public safety and comply with applicable regulatory standards.
generated at time: 2026-06-05T02:15:59.482935+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Economic Pressure Continuation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.93
constraint type: ethical
flexibility: hard
mitigation strategies: Cease participation in the project upon client refusal to implement identified safety measures
mitigation strategies: Document the client's refusal and the engineer's withdrawal
mitigation strategies: Report the risk to appropriate regulatory authorities after client override
text references: Client X's insistence on moving forward with the project without adequate safeguards creates an ethical dilemma for Engineer L.
text references: Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
text references: The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project.'
violation impact: Engineer violates paramount public safety obligation; public exposed to unmitigated risk; engineer subject to professional discipline.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:13.190895+00:00
first discovered in case: 8
match confidence: 0.95
match reasoning: The Client Economic Pressure Safety Continuation Constraint in the ontology is precisely this concept: prohibition on continuing work after a client declines safety measures on economic grounds, requiring the engineer to cease participation rather than subordinate public safety to client financial preferences. The BER Case 84-5 and Engineer L facts are direct instantiations.
matched ontology class: Client Economic Pressure Safety Continuation Constraint
matched ontology label: Client Economic Pressure Safety Continuation Constraint
matches existing: true
source text: The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project.'
comment: Ethical constraint prohibiting an engineer from continuing work on a project after a client declines to implement safety measures the engineer has identified as necessary, when the client's refusal is grounded in economic or budget concerns. Proceeding in such circumstances constitutes abandonment of the paramount public safety duty in favor of the client's financial preferences, which violates professional ethics codes.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [ClientEconomicPressureSafetyContinuationConstraint] Ethical constraint prohibiting an engineer from continuing work on a project after a client declines to implement safety measures the engineer has identified as necessary, when proceeding would require the engineer to subordinate public safety obligations to the client's economic concerns. The engineer must cease participation rather than abandon the duty to hold public safety paramount in favor of client financial preferences.
generated at time: 2026-06-05T02:27:13.190895+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Economic Pressure Refusal Obligation
type: Class
confidence: 0.88
derived from principle: Client Economic Pressure Resistance Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer ceased work or formally declined to proceed after the client refused to implement identified safety measures
nspe reference: II.1.a
obligation type: safety
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project.' The BER, in discussing BER Case 84-5, felt that 'Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.'
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
violation consequences: Violation of Code section II.1.a; potential harm to public health and safety; professional discipline
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:06:46.728956+00:00
first discovered in case: 8
match confidence: 0.78
match reasoning: The existing Client Instruction Limits Obligation covers the duty to decline client instructions that would require violating professional ethics. This class is a more specific variant focused on the scenario where the client's refusal is driven by cost or economic pressure and the engineer must refuse to continue rather than merely decline a specific instruction. The economic pressure dimension and the affirmative duty to stop work distinguish it sufficiently to warrant a separate class, though it is closely related.
matched ontology class: Client Instruction Limits Obligation
matched ontology label: Client Instruction Limits Obligation
matches existing: true
source text: Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project.' The BER, in discussing BER Case 84-5, felt that 'Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.'
comment: Duty of an engineer to refuse to continue work on a project when a client declines to implement safety measures the engineer has identified as necessary, even when the client's refusal is motivated by cost concerns, and to refrain from subordinating the paramount duty to public welfare to the client's economic interests.
subclass of: SafetyObligation
scope note: [ClientInstructionLimitsObligation] Duty of an engineer to decline client instructions that would require violating professional ethics obligations, recognizing that the faithful agent duty does not extend to complying with directives that breach professional standards.
generated at time: 2026-06-04T10:06:46.728956+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Economic Pressure Resistance Principle
type: Class
abstract nature: The principle requires engineers to distinguish between legitimate client cost management decisions and client refusals that cross the threshold of creating unacceptable public risk. This distinction requires professional judgment about the severity of the risk and the adequacy of proposed alternatives.
confidence: 0.92
derived obligations: Document the client's refusal and the engineer's response
derived obligations: Refuse to continue work when client declines necessary safety measures on cost grounds
derived obligations: Treat client refusal of safety measures as a trigger for withdrawal or escalation, not accommodation
extensional examples: BER Case 84-5: Engineer A violated Code by continuing project after client refused to hire safety representative on cost grounds, abandoning ethical duty to public
extensional examples: Present case: Engineer L cannot continue work after Client X refuses to implement protective stormwater measures
operationalization: Requires engineers to refuse to continue work when client cost objections result in removal of safety measures the engineer has identified as necessary, and to treat such refusals as triggering the obligation to withdraw or escalate rather than to proceed.
potential conflicts: Contractual obligations to complete work
potential conflicts: Faithful Agent Duty Principle
principle category: professional_virtue
text references: Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
text references: The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A abandoned the ethical duty [to the public] and proceeded to work on the project.
text references: We note a direct parallel between the 1984 case and the facts under consideration.
value basis: The integrity of the engineering profession depends on engineers maintaining their ethical obligations even under financial and relational pressure. Yielding to client economic concerns when public safety is at stake signals that professional duties are negotiable, undermining public trust in the profession.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:05:37.970804+00:00
first discovered in case: 8
match confidence: 0.78
match reasoning: The Client Economic Pressure Resistance Principle is a specific application of the Public Safety Paramount class already in the ontology, focusing on the scenario where client cost objections are the mechanism by which public safety is threatened. The existing class captures the general obligation to prioritize public safety over competing pressures. The present principle adds specificity about the economic pressure vector, making it a variant rather than an exact match. The individual record will capture the case-specific application.
matched ontology class: Public Safety Paramount
matched ontology label: Public Safety Paramount
matches existing: true
source text: The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A abandoned the ethical duty [to the public] and proceeded to work on the project.
comment: Professional virtue principle prohibiting engineers from abandoning their ethical duties to the public by yielding to client economic concerns or cost-based objections to necessary safety measures. When a client refuses to fund protective measures that the engineer has identified as necessary for public safety, the engineer must not continue work in a manner that perpetuates the identified risk, regardless of the financial consequences to the client or the professional relationship.
subclass of: ProfessionalVirtuePrinciple
scope note: [PublicSafetyParamount] Fundamental principle requiring engineers to prioritize public safety above client instructions, employer directives, or collegial relationships when significant design errors create risk to persons who will occupy or use engineered structures.
generated at time: 2026-06-04T10:05:37.970804+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Economic Priority Override State
type: Class
action constraints: Professional must not continue work on a project when client refuses safety measures and no adequate alternative safeguards exist
action constraints: Professional must not treat client cost concerns as sufficient justification to abandon safety obligations
activation conditions: Client declines the measure on cost grounds
activation conditions: Professional continues work without the measure being implemented
activation conditions: Professional recommends a safety measure
confidence: 0.87
obligation activation: Duty not to subordinate public safety to client economic interests
obligation activation: Duty to advise client when a project will not be successful from a safety standpoint
obligation activation: Duty to hold paramount public health, safety, and welfare
persistence type: inertial
principle transformation: Transforms the abstract duty to hold public safety paramount into a concrete obligation to cease or refuse work when client economic override removes necessary safety safeguards.
state category: conflict
termination conditions: Client agrees to implement the safety measure
termination conditions: Professional formally documents refusal and escalates to appropriate authority
termination conditions: Professional withdraws from the project
text references: Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project'
text references: Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T02:17:00.931476+00:00
first discovered in case: 8
match confidence: 0.87
match reasoning: The existing class Client Cost Objection to Safety Measure State captures the condition in which a client declines a safety measure on cost grounds and the professional continues work without it, which is the precise pattern described in BER Case 84-5 and applied to Engineer L's situation here.
matched ontology class: Client Cost Objection to Safety Measure State
matched ontology label: Client Cost Objection to Safety Measure State
matches existing: true
source text: Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project'
comment: State in which a professional, after being informed by a client that a recommended safety measure is too costly, continues to work on the project without the safety measure in place, creating a condition in which the professional's conduct signals that the client's economic concerns have displaced the professional's paramount obligation to public safety.
subclass of: ConflictState
scope note: [ClientCostObjectiontoSafetyMeasureState] State in which a client declines to implement a safety measure recommended by the professional engineer on the grounds that the measure is too costly, and the professional continues to work on the project without the safety measure in place, creating a condition in which the professional's primary obligation has shifted from public safety to the client's economic concerns.
generated at time: 2026-06-05T02:17:00.931476+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Funding Assumption State
type: Class
action constraints: Professional must not substitute a personal funding assumption for client-authorized scope decisions
action constraints: Professional must not withhold information about foreseeable cost impacts from the client
activation conditions: Professional assumes a specific funding source will cover costs arising from an incomplete or deficient deliverable
activation conditions: That assumption is not disclosed to the client or approving authority
activation conditions: The assumption influences the professional's decision to proceed without correcting the deficiency
confidence: 0.82
obligation activation: Duty not to use funding assumptions as justification for delivering incomplete work
obligation activation: Duty to disclose assumptions about funding that affect project scope or cost
obligation activation: Duty to obtain client authorization before relying on third-party funding to cover foreseeable cost overruns
persistence type: inertial
principle transformation: Transforms faithful-agent and honest-communication principles into an obligation to disclose and obtain authorization for any assumption about third-party funding that the professional uses to justify delivering a deficient or incomplete work product.
state category: conflict
termination conditions: Assumption is disclosed and validated by the funding authority
termination conditions: Client is informed and authorizes reliance on the assumption
termination conditions: Deficiency is corrected independent of the funding assumption
text references: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:46:12.006396+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs
comment: State in which a professional proceeds with or rationalizes a decision to deliver an incomplete or potentially cost-escalating work product on the assumption that a particular funding source, typically a third-party or government grant, will absorb any resulting cost overruns, without disclosing that assumption or obtaining client authorization to rely on it.
subclass of: ConflictState
generated at time: 2026-06-04T16:46:12.006396+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Client Instruction Boundary Judgment Capability
type: Class
capability category: reasoning
confidence: 0.8
domain specificity: Professional engineering ethics and client relations
enables actions: Communicate the basis for refusal to a client
enables actions: Decline instructions that conflict with professional ethics
enables actions: Evaluate whether client instructions are ethically permissible
required for obligations: Client Instruction Limits Obligation
required for obligations: Covert Review Refusal Obligation
skill level: advanced
text references: Engineer B objects to conducting the peer review without advising Engineer A
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:30.046199+00:00
first discovered in case: 15
match confidence: 0.72
match reasoning: The capability to identify and act on the boundary between client loyalty and professional ethics involves managing conflicting normative requirements, which aligns with Conflict Resolution as defined by Dennis et al. 2016. However, the emphasis here is on judgment about instruction limits rather than mediation between parties, making this a variant at medium confidence.
matched ontology class: ConflictResolution
matched ontology label: Conflict Resolution
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
comment: Capability to recognize when client or employer instructions exceed the limits of professional loyalty and would require violating ethical obligations, and to decline such instructions while articulating the professional basis for refusal.
subclass of: Capability
scope note: [ConflictResolution] Capability to manage and resolve conflicts between diverse and potentially conflicting normative requirements (Dennis et al. 2016)
generated at time: 2026-06-02T19:57:30.046199+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Client Interest versus Public Duty Conflict State
type: Class
action constraints: Confidentiality does not override mandatory reporting when law is violated
action constraints: Professional may not remain silent when public safety is at confirmed risk
activation conditions: Client has invoked confidentiality or instructed non-disclosure
activation conditions: Professional discovers client conduct that threatens public safety or violates law
activation conditions: Professional's duty to client and duty to public cannot both be satisfied
confidence: 0.82
obligation activation: Obligation to monitor client response
obligation activation: Obligation to notify client of violation and demand remediation
obligation activation: Obligation to report to authorities if client fails to act
persistence type: inertial
principle transformation: Transforms the abstract tension between faithful agency and public safety into a concrete sequential duty: notify client first, monitor response, then escalate to authorities if remediation is not taken.
state category: conflict
termination conditions: Client takes adequate remedial action
termination conditions: Conflict resolved through client compliance
termination conditions: Professional reports to appropriate authorities
text references: Engineering practice sometimes places the engineer in the position where the interests of a client and the interests of the public are in open and serious conflict.
text references: The obligation of the engineer to be faithful to the client and not to disclose confidential information concerning the business affairs of a client without that client's consent, and the obligation of the engineer to hold paramount the public health and safety.
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:27:19.652589+00:00
first discovered in case: 86
match confidence: 0.8
match reasoning: The Faithful Agent Duty Conflict State captures the direct conflict between the professional's obligation to act as a faithful agent for the client and the paramount duty to protect public health, safety, and welfare. The present state is the same concept applied to an environmental law violation context. A medium-confidence match is appropriate because the existing class already encodes this tension generically.
matched ontology class: Faithful Agent Duty Conflict State
matched ontology label: Faithful Agent Duty Conflict State
matches existing: true
source text: Engineering practice sometimes places the engineer in the position where the interests of a client and the interests of the public are in open and serious conflict.
comment: State in which a professional faces an open and serious conflict between obligations owed to a client, including confidentiality and faithful agency, and the paramount obligation to protect public health, safety, and welfare, requiring the professional to prioritize public duty when the two cannot be simultaneously satisfied.
subclass of: ConflictState
scope note: [FaithfulAgentDutyConflictState] State in which a professional's obligation to act as a faithful agent or trustee for a client comes into direct conflict with the professional's paramount duty to protect public health, safety, and welfare, requiring the professional to prioritize public safety over client loyalty when the two duties cannot be simultaneously satisfied.
generated at time: 2026-06-04T17:27:19.652589+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Client Loyalty Limits
type: Class
abstract nature: Requires interpretation of the scope and limits of loyalty obligations, distinguishing between legitimate client direction over the manner of professional services and impermissible client direction that overrides independent professional judgment.
confidence: 0.86
derived obligations: Advise clients when their instructions conflict with professional obligations
derived obligations: Decline client instructions that require violating professional duties to third parties
derived obligations: Follow client instructions within the bounds of professional obligations
extensional examples: Cases in which engineers declined client instructions that would require concealment from affected parties
extensional examples: NSPE BER cases establishing that client instructions do not override professional ethical obligations
operationalization: Engineer B's loyalty to the Owner does not require compliance with the instruction to conduct a covert review, because that instruction conflicts with the professional obligation to notify Engineer A. Engineer B correctly declined to follow the instruction until the Owner consented to notification.
potential conflicts: Professional Accountability
potential conflicts: Transparency
principle category: relational
text references: Engineer B objects to conducting the peer review without advising Engineer A
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
text references: When Owner reluctantly consents to notifying Engineer A
value basis: Professional loyalty to clients is instrumental to delivering quality services, but it is bounded by the engineer's independent professional obligations, which clients cannot waive by contract or instruction.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:55:30.891672+00:00
first discovered in case: 15
match confidence: 0.83
match reasoning: The principle is a specific application of the existing Loyalty class in the ontology, addressing the limits of that loyalty obligation rather than introducing a new concept. The case instantiates Loyalty by showing where Engineer B's duty to the Owner ends and independent professional obligations begin.
matched ontology class: Loyalty
matched ontology label: Loyalty
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
comment: Relational principle establishing that an engineer's duty of loyalty to a client does not extend to complying with client instructions that would require the engineer to violate other professional obligations, such as the duty to notify a colleague whose work is under review.
subclass of: RelationalPrinciple
generated at time: 2026-06-02T19:55:30.891672+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Client Override Escalation Obligation
type: Class
confidence: 0.88
derived from principle: Client Override Refusal Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that the engineer formally reported the override and associated risk to the appropriate regulatory authority
nspe reference: I.1, II.1.a, II.1.c
obligation type: reporting
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: Regulatory bodies
stakeholders affected: Water consumers
text references: Despite those recommendations, the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source.
violation consequences: Potential harm to public health; professional discipline; license revocation
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:23:42.907966+00:00
first discovered in case: 76
match confidence: 0.9
match reasoning: The obligation is substantively identical to the existing Client Override Public Safety Reporting Obligation, which covers the duty to report to a regulatory authority when a client overrides safety recommendations and proceeds without adequate safeguards.
matched ontology class: Client Override Public Safety Reporting Obligation
matched ontology label: Client Override Public Safety Reporting Obligation
matches existing: true
source text: Despite those recommendations, the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source.
comment: Duty of an engineer whose professional recommendation has been overridden by a client or governing body to escalate the matter to the appropriate regulatory authority when the override creates a risk to public health or safety, placing the paramount duty to public welfare above the faithful agent duty to the client.
subclass of: ReportingObligation
scope note: [ClientOverridePublicSafetyReportingObligation] Duty of an engineer to report identified risks to public health or safety to the appropriate regulatory or pollution control authority when the client refuses to implement recommended protective measures and insists on proceeding without adequate safeguards, placing the paramount duty to public welfare above the faithful agent duty to the client.
generated at time: 2026-06-05T11:23:42.907966+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Client Override Refusal Principle
type: Class
abstract nature: Requires judgment about the threshold of risk severity that transforms a client disagreement into a professional obligation to refuse or escalate, and about the appropriate channels for escalation.
confidence: 0.85
derived obligations: Document professional objections to client instructions in writing
derived obligations: Notify regulatory authorities when client refusal to act creates risks to public health or safety
derived obligations: Refuse to proceed with work that the engineer has determined is unsafe without adequate protective measures
extensional examples: BER Case 76-4 where a client instructed an engineer to omit adverse findings from a report submitted to a regulatory authority
extensional examples: Engineer L case where Client X insisted on proceeding without additional stormwater safeguards despite identified drinking water risk
operationalization: Requires engineers to document their professional objections, refuse to seal or submit work that incorporates client-directed omissions of known safety measures, and notify regulatory authorities when client decisions create risks to identifiable third parties.
potential conflicts: Client Loyalty
potential conflicts: Confidentiality
principle category: fundamental_ethical
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed
text references: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations
text references: Despite Engineer L's concerns, Client X insists on proceeding without added safeguards
value basis: Engineers derive their professional authority and public trust from their commitment to public welfare; allowing clients to override safety judgments would reduce engineers to mere technical instruments and undermine the social contract that justifies professional licensure.
discovered in case: 8
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:01:19.883840+00:00
first discovered in case: 8
match confidence: 0.8
match reasoning: The existing Public Safety Paramount class captures the fundamental principle that engineers must prioritize public safety above client instructions when significant risks exist. The concept extracted here is a specific operational expression of that fundamental principle in the context of a client override scenario. Rather than creating a redundant class, this is best treated as an instance of Public Safety Paramount, with the client-override context captured in the individual record. Confidence is 0.80 rather than higher because the existing class description focuses on design errors and structural risks, while this case involves environmental and public health risks from client refusal to implement protective measures, but the underlying principle is the same.
matched ontology class: Public Safety Paramount
matched ontology label: Public Safety Paramount
matches existing: true
source text: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed
comment: Professional principle establishing that when a client instructs an engineer to proceed without implementing safety or environmental protective measures that the engineer has identified as necessary, the engineer must refuse to continue work in a manner that would create or perpetuate the identified risk, and must escalate to appropriate authorities if the client's decision threatens public welfare.
subclass of: FundamentalEthicalPrinciple
subclass of: ProfessionalVirtuePrinciple
scope note: [PublicSafetyParamount] Fundamental principle requiring engineers to prioritize public safety above client instructions, employer directives, or collegial relationships when significant design errors create risk to persons who will occupy or use engineered structures.
generated at time: 2026-06-04T10:01:19.883840+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Override Safety Withdrawal Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Community Water Users
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.8
constraint type: ethical
flexibility: hard
mitigation strategies: Document the basis for withdrawal
mitigation strategies: Formally notify the client in writing that continued participation is not possible without adequate safeguards
mitigation strategies: Refer the client to another engineer who can assess the situation independently
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: Despite Engineer L's concerns, Client X insists on proceeding without added safeguards.
violation impact: Engineer participates in a project that endangers public health or safety, violating the paramount duty and exposing the engineer to professional discipline and liability.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:03:17.838512+00:00
first discovered in case: 8
match confidence: 0.78
match reasoning: The Client Instruction Override Constraint establishes that an engineer's duty of loyalty to a client does not extend to following client instructions that require violating professional ethics obligations, and that such instructions must be declined. This case instantiates that constraint in the specific context of a client overriding a safety recommendation and directing the engineer to proceed without safeguards. The existing class is broad enough to cover this scenario, though the present case adds the dimension of confirmed public safety risk and the option of withdrawal. Matching as a variant at medium confidence.
matched ontology class: Client Instruction Override Constraint
matched ontology label: Client Instruction Override Constraint
matches existing: true
source text: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
comment: Ethical constraint establishing that when a client explicitly overrides an engineer's safety recommendation in a manner that would require the engineer to continue work on a project that poses a confirmed risk to public health or safety without adequate safeguards, the engineer must decline to continue participation in that project rather than proceed in violation of the paramount public safety duty.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [ClientInstructionOverrideConstraint] Ethical constraint establishing that an engineer's duty of loyalty to a client does not extend to following client instructions that require violating professional ethics obligations, and that such instructions must be declined.
generated at time: 2026-06-04T10:03:17.838512+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Refusal Regulatory Reporting Obligation
type: Class
confidence: 0.88
derived from principle: Client Override Refusal Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that the engineer reported the client's refusal and the identified risk to the appropriate regulatory authority after the client declined to implement protective measures.
nspe reference: I.1, II.1.a, II.1.c
obligation type: reporting
stakeholders affected: Community relying on drinking water source
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations.
text references: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
violation consequences: Failure to report may result in harm to public health, professional discipline, and potential legal liability for the engineer.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:20:48.587109+00:00
first discovered in case: 8
match confidence: 0.9
match reasoning: The existing Client Override Public Safety Reporting Obligation directly covers the duty to report identified risks to public health or safety to the appropriate regulatory or pollution control authority when the client refuses to implement recommended protective measures and insists on proceeding without adequate safeguards. This case is a near-identical instantiation of that obligation. Matched with high confidence.
matched ontology class: Client Override Public Safety Reporting Obligation
matched ontology label: Client Override Public Safety Reporting Obligation
matches existing: true
source text: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations.
comment: Duty of an engineer who has notified a client of a risk to public health or safety and recommended protective measures, and whose client has refused to implement those measures while stating an intent to address compliance issues only if required later, to report the situation to the appropriate regulatory or pollution control authority, placing the paramount duty to public welfare above the faithful agent duty to the client.
subclass of: ReportingObligation
scope note: [ClientOverridePublicSafetyReportingObligation] Duty of an engineer to report identified risks to public health or safety to the appropriate regulatory or pollution control authority when the client refuses to implement recommended protective measures and insists on proceeding without adequate safeguards, placing the paramount duty to public welfare above the faithful agent duty to the client.
generated at time: 2026-06-05T02:20:48.587109+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Remediation Monitoring Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.85
constraint type: ethical
flexibility: soft
mitigation strategies: Document remediation progress
mitigation strategies: Escalate to regulatory authorities if adequate remediation does not occur within a reasonable period
mitigation strategies: Establish a monitoring schedule after receiving client assurances
text references: Engineer A had an obligation to follow through to see that correct follow-up action was taken by the public agency.
text references: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
violation impact: Ongoing environmental or safety harm resulting from unverified remediation that the engineer accepted on the client's word alone.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:35:44.662063+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
comment: Ethical constraint requiring that an engineer who has notified a client of a confirmed legal or regulatory violation and received assurances of remediation must actively monitor the client's remedial actions until the engineer is sufficiently satisfied that the violation has been corrected. The engineer may not treat the client's assurance as a substitute for actual verification of compliance.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
generated at time: 2026-06-04T17:35:44.662063+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Client Remediation Monitoring State
type: Class
action constraints: Professional may not close the matter without confirming adequate remediation
action constraints: Professional may not indefinitely defer reporting if client is unresponsive
activation conditions: Client has not yet completed remediation
activation conditions: Professional has notified client of a confirmed violation or safety risk
activation conditions: Professional is awaiting client response or corrective action
confidence: 0.83
obligation activation: Obligation to assess adequacy of corrective action taken
obligation activation: Obligation to escalate to authorities if client fails to act within a reasonable time
obligation activation: Obligation to monitor client's remediation progress
persistence type: inertial
principle transformation: Transforms the general duty to protect public safety into a time-bounded monitoring obligation that conditions the escalation duty on the client's response, while preserving the professional's ultimate obligation to report if the client does not act.
state category: risk
termination conditions: Client completes adequate remediation to professional's satisfaction
termination conditions: Professional determines client will not act and reports to authorities
termination conditions: Regulatory authority intervenes independently
text references: If appropriate steps are not taken by the client, the engineer would have an obligation to bring this matter to the attention of the appropriate authorities.
text references: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
text references: It is clear that Engineer A had an obligation to follow through to see that correct follow-up action was taken by the public agency.
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:27:19.652589+00:00
first discovered in case: 86
match confidence: 0.76
match reasoning: The Confirmed Risk Disclosure State covers the condition in which a professional has identified and documented a concrete risk and notified the client, creating an active obligation to ensure the client responds with adequate safeguards and triggering heightened duties if the client refuses to act. The present state extends that concept by focusing specifically on the monitoring phase after notification, where the professional's reporting obligation is held in conditional abeyance. The match is medium because the existing class captures the post-notification obligation structure but does not specifically name the monitoring phase as a distinct condition.
matched ontology class: Confirmed Risk Disclosure State
matched ontology label: Confirmed Risk Disclosure State
matches existing: true
source text: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
comment: State in which a professional has notified a client of a confirmed violation or safety risk and is actively monitoring whether the client takes adequate corrective action within a reasonable time, creating a conditional obligation structure in which the professional's duty to report to authorities is held in abeyance pending the outcome of the client's remediation efforts.
subclass of: RiskState
scope note: [ConfirmedRiskDisclosureState] State in which a professional has identified and documented a concrete risk as a factual finding and has notified the client of that risk, creating an active obligation to ensure the client responds with adequate safeguards and triggering heightened duties if the client refuses to act.
generated at time: 2026-06-04T17:27:19.652589+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Client Service Integrity Principle
type: Class
abstract nature: Relational principle requiring interpretation of what genuine client service means when short-term adversarial advantage conflicts with the client's long-term interest in accurate technical guidance.
confidence: 0.88
derived obligations: Advise clients when selective reporting may misdirect their decisions
derived obligations: Explain the basis for discounting adverse evidence rather than omitting it
derived obligations: Provide complete technical findings to the client
extensional examples: NSPE ethical obligations regarding honest professional service to clients
operationalization: Requires engineers to provide clients with complete technical findings even when those findings are unfavorable, to identify the rational basis for discounting adverse evidence rather than suppressing it, and to recognize that incomplete reporting forfeits the opportunity to serve the client effectively.
potential conflicts: Client Advocacy
potential conflicts: Litigation Neutrality Principle
principle category: relational
text references: As an engineering document the report is incomplete and does a disservice to Engineer B's client municipality by potentially misdirecting a conclusion.
text references: by excluding the pile driving records, Engineer B has denied himself the opportunity to present a rational for discounting their value, and thereby to serve his client.
value basis: True loyalty to a client requires honest professional judgment, not advocacy-driven selectivity. A client misled by incomplete engineering analysis may make worse decisions than one given complete but unfavorable facts.
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:34:00.918915+00:00
first discovered in case: 71
match confidence: 0.87
match reasoning: No existing principle class addresses the specific relational obligation that genuine client service requires completeness and honesty rather than selective advocacy. The existing principles address investigative diligence, scope disclosure, litigation neutrality, and methodological consistency. This principle concerns the nature of the engineer-client relationship itself and the paradox that partisan selectivity disserves the client. It is a distinct relational concept warranting its own class.
matches existing: false
source text: by excluding the pile driving records, Engineer B has denied himself the opportunity to present a rational for discounting their value, and thereby to serve his client.
comment: Professional principle holding that an engineer's duty to serve the client is fulfilled through honest, complete, and technically sound work, and that selective or incomplete reporting, even when intended to favor the client, constitutes a disservice by potentially misdirecting conclusions and exposing the client to adverse outcomes.
subclass of: RelationalPrinciple
generated at time: 2026-06-04T14:34:00.918915+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Client Violation Confrontation Capability
type: Class
capability category: communication
confidence: 0.86
domain specificity: Professional engineering contexts where a discovered client violation requires direct professional communication before regulatory reporting
enables actions: Contact a client directly upon discovering a violation
enables actions: Convey the obligation to take immediate remedial steps
enables actions: Frame the communication so as to give the client a reasonable opportunity to comply before escalation
enables actions: Identify and communicate the specific legal or regulatory violations observed
required for obligations: Client Violation Contact Obligation
required for obligations: Regulatory Escalation Obligation
skill level: intermediate
text references: Engineer A's actions appear to be obvious -- contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
text references: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:36:09.645175+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: Engineer A's actions appear to be obvious -- contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
comment: Capability to directly contact a client or former client upon discovering a legal or regulatory violation, to identify the specific violations clearly, to communicate the obligation to take immediate remedial action, and to do so in a manner that is direct and professional without being adversarial, giving the client the opportunity to remedy the situation before escalation to regulatory authorities.
subclass of: Capability
generated at time: 2026-06-04T17:36:09.645175+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Client Violation Contact Obligation
type: Class
confidence: 0.88
derived from principle: Graduated Response Proportionality Principle
enforcement level: mandatory
monitoring criteria: Documented record of direct communication with client identifying the violation and specifying required remedial actions.
nspe reference: I.1, II.1.a, III.4
obligation type: reporting
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: Engineer A's actions appear to be obvious—contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
violation consequences: Failure to contact client first may bypass an opportunity for voluntary remediation and may expose the engineer to claims of disproportionate response; failure to contact at all constitutes a breach of the duty to protect public welfare.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:34:19.889581+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: Engineer A's actions appear to be obvious—contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
comment: Duty of an engineer who discovers that a client has committed a violation of applicable law or regulation to contact the client directly, identify the violation, and require that immediate remedial steps be taken before escalating to regulatory authorities.
subclass of: ReportingObligation
generated at time: 2026-06-04T17:34:19.889581+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Code Adaptability Principle
type: Class
abstract nature: Requires ongoing interpretation of what constitutes a prevailing practice versus an unacceptable deviation from ethical standards, and how to distinguish reasonable adaptation from ethical erosion.
confidence: 0.82
derived obligations: Clarify prior opinions found to impose impossible standards
derived obligations: Distinguish adaptation from ethical compromise
derived obligations: Periodically review code interpretations against prevailing practice
extensional examples: BER Case 86-2 modification to reflect actual sealing practices in large firms
extensional examples: Revision of responsible charge standards to accommodate CADD-based practice
operationalization: Ethics boards must periodically review whether their interpretations of code provisions remain consistent with actual professional practice, and must be willing to clarify or modify prior opinions when those opinions are found to be inconsistent with reasonable prevailing practice.
potential conflicts: Risk that prevailing practice reflects widespread ethical failure rather than reasonable adaptation
potential conflicts: Stability and predictability of ethical standards
principle category: fundamental_ethical
text references: The Code must not impose an impossible or idealistic standard upon engineers, but rather must establish a bench mark of reasonable and rational methods of practice for it to maintain its credibility and adherence.
text references: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
text references: we think the Board's conclusion in BER Case 86-2 should be modified to reflect actual practices which exist within engineering and not impose a impossible standard upon practice.
value basis: A code of ethics derives its authority from its acceptance and observance by practitioners; a code that demands the impossible loses its normative force and practical relevance.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:09:59.425228+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
comment: Meta-level professional principle recognizing that a code of ethics must reflect and remain consonant with generally prevailing practices within the profession, and must not impose impossible or idealistic standards that would place a significant number of practitioners in unavoidable conflict with the code, thereby undermining the code's credibility and adherence.
subclass of: FundamentalEthicalPrinciple
generated at time: 2026-06-04T18:09:59.425228+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Code Evolution Awareness Capability
type: Class
capability category: norm_management
confidence: 0.8
domain specificity: Professional engineering ethics interpretation and code administration
enables actions: Assess whether an ethical ruling reflects actual professional practice
enables actions: Identify when a prior ruling imposes an impossible standard
enables actions: Interpret code provisions in light of prevailing professional norms
enables actions: Support clarification or modification of prior ethical decisions
required for obligations: Code Prevailing Practice Conformance Obligation
skill level: expert
text references: The Code must not impose an impossible or idealistic standard upon engineers, but rather must establish a bench mark of reasonable and rational methods of practice for it to maintain its credibility and adherence.
text references: The rendering of the Board's opinion in BER Case 86-2, raised a considerable degree of discussion within the engineering community because to many it appeared to be inconsistent with customary and generally prevailing practices within the engineering profession.
text references: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:12:59.240485+00:00
first discovered in case: 120
match confidence: 0.74
match reasoning: Ethical Learning is defined as the ability to adapt to new cases, changing standards, and novel situations while maintaining consistency. Code Evolution Awareness Capability shares the adaptation dimension but is specifically directed at institutional recognition that ethical standards must track prevailing practice rather than impose impossible ideals. The match is a medium-confidence variant: the existing class captures individual-level learning and adaptation, while this capability is more institutional and interpretive in character.
matched ontology class: EthicalLearning
matched ontology label: Ethical Learning
matches existing: true
source text: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
comment: Capability of a professional ethics body or practicing engineer to recognize that a code of professional ethics is not a static document and must be interpreted in light of generally prevailing practices within the profession, including the ability to identify when a prior ethical ruling imposes an impossible or unrealistic standard inconsistent with actual professional practice and to support revision or clarification of that ruling accordingly.
subclass of: Capability
scope note: [EthicalLearning] Ability to adapt to new cases, changing standards, and novel situations while maintaining consistency (Anderson & Anderson 2018)
generated at time: 2026-06-04T18:12:59.240485+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Code Prevailing Practice Conformance Constraint
type: Class
affected stakeholders: Engineering Profession
affected stakeholders: Ethics Review Board
affected stakeholders: Practitioners
affected stakeholders: Public
confidence: 0.8
constraint type: ethical
flexibility: soft
mitigation strategies: Consult professional practice surveys and industry standards when interpreting code provisions
mitigation strategies: Distinguish between aspirational standards and enforceable minimum requirements
mitigation strategies: Revise or clarify prior interpretations when they are shown to conflict with reasonable prevailing practice
text references: The Code must not impose an impossible or idealistic standard upon engineers, but rather must establish a bench mark of reasonable and rational methods of practice for it to maintain its credibility and adherence.
text references: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
violation impact: Ethics code interpretations that ignore prevailing practice lose credibility, reduce voluntary compliance, and may impose unjust burdens on practitioners acting in good faith.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:13:02.665367+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
comment: Ethical and institutional constraint requiring that professional ethics codes and their authoritative interpretations reflect generally prevailing practices within the profession, prohibiting the imposition of impossible or idealistic standards that would place a significant number of practitioners in unavoidable conflict with the code and thereby undermine the code's credibility and adherence.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
generated at time: 2026-06-04T18:13:02.665367+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Code Prevailing Practice Conformance Obligation
type: Class
confidence: 0.8
derived from principle: Code Adaptability Principle
enforcement level: conditional
monitoring criteria: Evidence that code interpretations are reviewed against actual prevailing professional practices and updated when significant divergence is identified
nspe reference: Preamble
obligation type: ethical
stakeholders affected: Engineering profession
stakeholders affected: Ethics boards
stakeholders affected: Licensed engineers
stakeholders affected: Regulatory bodies
text references: The Code must not impose an impossible or idealistic standard upon engineers, but rather must establish a bench mark of reasonable and rational methods of practice for it to maintain its credibility and adherence.
text references: The rendering of the Board's opinion in BER Case 86-2, raised a considerable degree of discussion within the engineering community because to many it appeared to be inconsistent with customary and generally prevailing practices within the engineering profession.
text references: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
violation consequences: Loss of credibility and adherence to the code if standards are set at levels inconsistent with actual professional practice
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:11:22.208486+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
comment: Duty of professional ethics bodies and engineers interpreting the code of ethics to ensure that ethical standards reflect and remain consonant with generally prevailing practices within the engineering profession, so that the code does not impose impossible or idealistic standards that place a significant number of practitioners in unavoidable conflict with its provisions.
subclass of: EthicalObligation
generated at time: 2026-06-04T18:11:22.208486+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Collegial Notification Principle
type: Class
abstract nature: Open-textured obligation whose precise requirements depend on contract terms, the nature of the review, and whether the original engineer's connection to the work has been formally terminated.
confidence: 0.88
derived obligations: Advise client of notification requirement before accepting review
derived obligations: Cooperate with review once notified
derived obligations: Decline peer review assignment if notification of original engineer is refused
extensional examples: NSPE BER Case 93-3 where owner refused to advise engineer of planned peer review
extensional examples: NSPE Professional Obligation III.7.a requiring knowledge of engineer whose work is reviewed
operationalization: Requires peer reviewer to decline assignment unless the engineer whose work is under review has been notified, and requires client to provide that notification as a precondition of the review.
potential conflicts: Client Loyalty Limits
potential conflicts: Confidentiality of Professional Review
principle category: relational
text references: Engineer B was completely correct in declining an assignment to conduct a peer review of Engineer A's work subject to an instruction not to disclose the peer review to Engineer A.
text references: Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated.
text references: Owner reluctantly agreed to advise Engineer A of the planned peer review.
value basis: Respect for professional dignity and collegial relationships, and recognition that concealed review undermines trust and cooperation essential to effective professional practice.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:58:41.183712+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated.
comment: Relational principle requiring that an engineer whose work is subject to peer review by another engineer for the same client must be informed of that review before or at the time it commences, protecting collegial trust and enabling meaningful cooperation while preserving the integrity of the review process.
subclass of: RelationalPrinciple
generated at time: 2026-06-02T19:58:41.183712+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Commercial Engineering Software Marketing Resource
type: Class
authority source: Commercial vendors
confidence: 0.72
extensional function: Serves as a knowledge artifact that raises ethical questions about competence, professional identity, and the limits of tool-assisted practice. Its claims about capability provide the factual predicate for ethical analysis of whether reliance on such tools satisfies professional standards.
resource category: reference_material
text references: Engineer A receives a solicitation in the mail
text references: Simply sign and return this letter today
text references: thanks to a revolutionary new CD-ROM - specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
usage context: Assessing the ethical implications of marketing claims directed at licensed professionals
usage context: Evaluating whether a commercial tool can substitute for professional experience
usage context: Identifying solicitations that may induce engineers to practice outside their competence
discovered in case: 121
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:42:45.862955+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineer A receives a solicitation in the mail
comment: A commercial solicitation, advertisement, or promotional material directed at licensed engineers offering software, databases, or automated tools purporting to enable engineering services in areas outside the engineer's existing competence or experience.
subclass of: ReferenceMaterial
generated at time: 2026-06-04T18:42:45.862955+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Commercial Inducement Resistance Principle
type: Class
abstract nature: Requires engineers to exercise independent judgment when evaluating commercial claims about the sufficiency of tools or products for professional practice, distinguishing legitimate productivity aids from substitutes for professional competence.
confidence: 0.8
derived obligations: Evaluate vendor claims about tool capabilities against independent professional judgment
derived obligations: Recognize that profit-oriented solicitations are not a reliable guide to professional competence boundaries
derived obligations: Refuse to expand service offerings solely on the basis of software acquisition
extensional examples: An engineer accepting a vendor's claim that template-based specifications can replace engineering judgment in novel project types
extensional examples: An engineer ordering a CD-ROM design tool after receiving a solicitation claiming it eliminates the need for domain experience
extensional examples: An engineer subscribing to an AI design platform marketed as enabling practice in unfamiliar engineering disciplines
operationalization: Requires engineers to evaluate vendor claims against their own honest self-assessment of competence, to treat marketing materials as inherently self-interested, and to apply professional skepticism before expanding service offerings based on tool acquisition.
potential conflicts: Client expectations for comprehensive service delivery
potential conflicts: Firm profitability and business development pressures
principle category: professional_virtue
text references: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
text references: Simply sign and return this letter today and you'll be among the first engineers to see how this full-featured interactive library of standard design can help you work faster than ever and increase your firm's profits.
text references: specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience.
value basis: The integrity of professional practice requires that engineers, not vendors or commercial interests, determine the scope of services they are competent to offer. Allowing commercial solicitations to define competence boundaries undermines public trust and safety.
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:45:01.804237+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
comment: Professional virtue principle requiring engineers to critically evaluate and resist commercial solicitations, marketing materials, or vendor claims that encourage them to expand their practice into domains where they lack competence, particularly when those solicitations explicitly frame professional competence requirements as obstacles to profit. Engineers must not allow commercial incentives or vendor-supplied tools to override their professional judgment about the boundaries of their own expertise.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T18:45:01.804237+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Commercial Solicitation Reliance Constraint
type: Class
affected stakeholders: Engineer
affected stakeholders: Licensing board
affected stakeholders: Prospective clients
affected stakeholders: Public
confidence: 0.78
constraint type: ethical
flexibility: hard
mitigation strategies: Consult professional ethics guidance before expanding service offerings
mitigation strategies: Critically evaluate commercial claims against professional competence standards
mitigation strategies: Decline solicitations that promise to substitute tools for education and experience
text references: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
text references: specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
violation impact: Engineer offers services without genuine competence, exposing clients and the public to risk of deficient work, and violates professional ethics codes governing competence and misrepresentation.
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:46:31.879113+00:00
first discovered in case: 121
match confidence: 0.75
match reasoning: The Technology Substitution Constraint prohibits using a technological tool as a replacement for independent engineering judgment and requires that tool outputs be challenged and verified. The commercial solicitation reliance scenario is a variant of this concept, where the tool is being used not merely to assist but to substitute for domain competence entirely. The existing class captures the core prohibition; this case instantiates it in the specific context of a commercial CD-ROM marketed to engineers lacking domain experience.
matched ontology class: Technology Substitution Constraint
matched ontology label: Technology Substitution Constraint
matches existing: true
source text: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
comment: Ethical and competence constraint prohibiting a licensed engineer from treating a commercial solicitation, advertisement, or marketing material as a sufficient basis for acquiring or claiming competence in an unfamiliar engineering domain, particularly when the solicitation explicitly frames professional experience requirements as obstacles to be bypassed by a commercial product.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [TechnologySubstitutionConstraint] Ethical constraint prohibiting an engineer from using a technological tool as a replacement or substitute for independent engineering judgment, requiring that the engineer's own expertise, critical evaluation, and professional standards govern all decisions and that tool outputs be challenged and verified before acceptance.
generated at time: 2026-06-04T18:46:31.879113+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Commercial Solicitation Resistance Obligation
type: Class
confidence: 0.87
derived from principle: Commercial Inducement Resistance Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer evaluated the solicitation critically and did not expand service offerings beyond documented competence in response to commercial inducements
nspe reference: II.2
obligation type: ethical
stakeholders affected: Clients
stakeholders affected: General public
stakeholders affected: Professional licensing boards
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
text references: Now - - thanks to a revolutionary new CD-ROM - specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience.
violation consequences: Professional discipline; public safety risk from incompetent services offered on the basis of commercial inducement rather than genuine competence
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:45:48.212115+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
comment: Duty of a licensed engineer to critically evaluate commercial solicitations, marketing materials, and product promotions that frame professional competence requirements as obstacles to profit or that promise to substitute a tool or product for genuine domain expertise, and to refrain from accepting such solicitations as justification for offering services outside the engineer's competence.
subclass of: EthicalObligation
generated at time: 2026-06-04T18:45:48.212115+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Boundary Obligation
type: Class
confidence: 0.92
derived from principle: Competence Boundary Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer's offered services fall within documented areas of education, training, and experience
nspe reference: II.2
obligation type: competence
stakeholders affected: Clients
stakeholders affected: Employers
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: Engineer A, a chemical engineer with no facilities design and construction experience, receives a solicitation in the mail
violation consequences: Professional discipline including license revocation; potential harm to public safety; civil liability for deficient work products
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:45:48.212115+00:00
first discovered in case: 121
match confidence: 0.9
match reasoning: This is a direct instantiation of the canonical Competence Obligation, which requires engineers to perform services only in areas of competence per NSPE II.2. The case presents a clear violation of that obligation. The existing CADD Proficiency Competence Obligation and Technology Non-Substitution Obligation are related but address tool-specific competence rather than the threshold duty to refrain from offering out-of-domain services entirely.
matched ontology class: CompetenceObligation
matched ontology label: Competence Obligation
matches existing: true
source text: Engineer A, a chemical engineer with no facilities design and construction experience, receives a solicitation in the mail
comment: Duty of a licensed engineer to refrain from offering or undertaking engineering services in technical domains outside the engineer's actual education, training, and experience, regardless of commercial solicitations, software tools, or other inducements that purport to substitute for genuine domain competence.
subclass of: CompetenceObligation
scope note: [CompetenceObligation] Requirement to perform services only in areas of competence (NSPE II.2)
generated at time: 2026-06-04T18:45:48.212115+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Boundary Principle
type: Class
abstract nature: Open-textured standard requiring case-by-case assessment of what constitutes adequate competence for a given domain, and whether available tools can bridge a competence gap or merely mask it.
confidence: 0.88
derived obligations: Decline to offer services in domains where the engineer lacks substantive training and experience
derived obligations: Disclose competence limitations to prospective clients before accepting engagements
derived obligations: Recognize that software tools do not confer professional competence
derived obligations: Seek collaboration with or referral to engineers who possess the requisite domain expertise
extensional examples: A chemical engineer using a CD-ROM design tool to offer facilities design services without relevant training
extensional examples: A structural engineer offering geotechnical design services after completing an online course
extensional examples: An electrical engineer offering civil highway design based solely on software-generated outputs
operationalization: Requires engineers to assess their own competence before accepting engagements, to decline work outside their domain, and to resist commercial incentives that encourage overreach beyond established expertise.
potential conflicts: Client demand for one-stop engineering services
potential conflicts: Commercial pressure to expand service offerings
potential conflicts: Employer directives to take on unfamiliar project types
principle category: professional_virtue
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: Engineer A, a chemical engineer with no facilities design and construction experience, receives a solicitation in the mail
text references: never designed a highway before? No problem. Just point to the 'Highways' window and click.
value basis: Public safety and trust in the profession depend on engineers practicing only within domains where they can exercise genuine, substantive professional judgment rather than nominal approval of automated outputs.
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:45:01.804237+00:00
first discovered in case: 121
match confidence: 0.75
match reasoning: The existing Competence Principle addresses balancing professional autonomy with recognition of limitations and need for collaboration. The concept extracted here is a more specific instantiation of that principle, focused on the prohibition against offering services outside one's domain and the inadequacy of software tools as a substitute for genuine competence. The existing class is the appropriate parent, but the case raises a distinct emphasis on domain-boundary overreach enabled by commercial tools that the existing class does not fully capture. Confidence is set at 0.75 as a variant rather than a direct match.
matched ontology class: CompetencePrinciple
matched ontology label: Competence Principle
matches existing: true
source text: Engineer A, a chemical engineer with no facilities design and construction experience, receives a solicitation in the mail
comment: Professional principle prohibiting engineers from offering or undertaking engineering services in technical domains for which they lack the requisite education, training, or experience, regardless of the availability of software tools, templates, or other aids that may simulate competence. The use of automated design tools does not substitute for the foundational knowledge required to exercise independent professional judgment over the outputs of those tools.
subclass of: ProfessionalVirtuePrinciple
scope note: [CompetencePrinciple] Balances professional autonomy with recognition of limitations and need for collaboration.
generated at time: 2026-06-04T18:45:01.804237+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Limit Escalation Obligation
type: Class
confidence: 0.87
derived from principle: Competence Recognition Principle
enforcement level: mandatory
monitoring criteria: Whether the engineer identified the competence gap and took affirmative action to assign or request a qualified reviewer before approving the work
nspe reference: II.2
obligation type: competence
stakeholders affected: Client
stakeholders affected: Employer
stakeholders affected: Funding agency
stakeholders affected: General public
text references: Engineers have an obligation to perform services within their area of competence. If Engineer B was not able to perform the necessary reviews of Engineer A's work, Engineer B should have provided this information to a supervisor who would have assigned an appropriate engineer to perform the review.
text references: Not possessing adequate competency to perform a task is not in and of itself a violation of the NSPE Code, but the failure to recognize the lack of competency and take appropriate action to address the situation is a violation of the NSPE Code.
violation consequences: Professional discipline for approving work beyond competence; potential public harm from inadequate review
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:54:40.172403+00:00
first discovered in case: 85
match confidence: 0.78
match reasoning: The canonical Competence Obligation covers the duty to practice within areas of competence. This class specializes that obligation by focusing on the affirmative duty to escalate when a competence gap is recognized, rather than simply declining to perform. The Mentorship Gap Competence Obligation from prior extractions addresses a related but distinct scenario. This is a variant of the canonical Competence Obligation with a specific escalation-action requirement.
matched ontology class: CompetenceObligation
matched ontology label: Competence Obligation
matches existing: true
source text: Engineers have an obligation to perform services within their area of competence. If Engineer B was not able to perform the necessary reviews of Engineer A's work, Engineer B should have provided this information to a supervisor who would have assigned an appropriate engineer to perform the review.
comment: Duty of an engineer who lacks sufficient competence to perform a required review or technical task to recognize that limitation and escalate the assignment to a supervisor or more qualified engineer, rather than proceeding with an inadequate review or approving work the engineer is not competent to evaluate.
subclass of: CompetenceObligation
scope note: [CompetenceObligation] Requirement to perform services only in areas of competence (NSPE II.2)
generated at time: 2026-06-04T16:54:40.172403+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Competence Misrepresentation Avoidance Obligation
type: Class
confidence: 0.85
derived from principle: Competence Boundary Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer accurately represented qualifications and disclosed limitations to prospective clients before accepting engagements
nspe reference: III.2.a
obligation type: disclosure
stakeholders affected: Clients
stakeholders affected: General public
stakeholders affected: Professional licensing boards
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: Engineer A, a chemical engineer with no facilities design and construction experience
violation consequences: Professional discipline; civil liability; harm to clients who rely on misrepresented qualifications
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:45:48.212115+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineer A, a chemical engineer with no facilities design and construction experience
comment: Duty of a licensed engineer to refrain from representing to prospective clients or the public that the engineer is qualified to perform services in a technical domain in which the engineer lacks the requisite education, training, and experience, including by omitting disclosure of that lack of qualification when soliciting or accepting such work.
subclass of: DisclosureObligation
generated at time: 2026-06-04T18:45:48.212115+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Misrepresentation State
type: Class
action constraints: Must not represent capability to clients based solely on automated tool availability
action constraints: Must not sign or seal work products in domains where competence is absent
activation conditions: Professional begins offering services outside their area of demonstrated competence
activation conditions: Professional holds out capability to clients without disclosing competence limitations
activation conditions: Professional relies on a commercial tool as a substitute for professional knowledge rather than as an augment to it
confidence: 0.88
obligation activation: Duty to disclose limitations to prospective clients
obligation activation: Duty to obtain supervision or associate with competent professionals before proceeding
obligation activation: Duty to refrain from offering services beyond competence
persistence type: inertial
principle transformation: Transforms the general competence principle into a concrete prohibition on holding out services and a disclosure obligation toward prospective clients who cannot independently assess the professional's actual capability.
state category: competence
termination conditions: Professional acquires sufficient education, training, or supervised experience in the domain
termination conditions: Professional discloses limitations and declines engagements beyond competence
termination conditions: Professional withdraws the offer of services in the domain
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services
text references: Engineer A, a chemical engineer with no facilities design and construction experience
discovered in case: 121
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:42:57.570207+00:00
first discovered in case: 121
match confidence: 0.8
match reasoning: Outside Area of Competence captures the core competence boundary condition. However, that class describes a state in which a professional is already engaged and recognizes a boundary, whereas this case involves a professional affirmatively beginning to offer services in a domain where competence is absent, relying on a commercial tool as a substitute. The active misrepresentation and tool-substitution dimension is not captured by the existing class, so a new class is warranted while acknowledging the close relationship.
matched ontology class: OutsideCompetence
matched ontology label: Outside Area of Competence
matches existing: true
source text: Engineer A, a chemical engineer with no facilities design and construction experience
comment: State in which a professional begins offering services in a domain where they lack the requisite education, training, or experience, relying instead on a commercial tool or shortcut that substitutes automated outputs for genuine professional competence, creating conditions in which the professional's representations of capability to prospective clients are false or misleading and in which work product carries elevated risk of harm.
subclass of: CompetenceState
scope note: [OutsideCompetence] Competence boundary preventing service provision
generated at time: 2026-06-04T18:42:57.570207+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Recognition Principle
type: Class
abstract nature: Principle requiring ongoing self-assessment of technical capability relative to assigned tasks, and affirmative escalation when a mismatch is identified, rather than passive acceptance of assignments beyond one's competence.
confidence: 0.88
derived obligations: Assess own competence before accepting or performing assigned tasks
derived obligations: Ensure appropriately qualified engineers perform tasks requiring competence the assigned engineer lacks
derived obligations: Notify supervisors when assigned tasks exceed competence
extensional examples: BER case involving Engineer B who approved incomplete dam design drawings without apparent recognition of or response to the limits of the review competence required
operationalization: Requires engineers to assess whether they possess the knowledge and skill to perform assigned tasks, to disclose limitations to supervisors when they do not, and to ensure that appropriately qualified personnel perform work that exceeds their competence.
potential conflicts: Employer loyalty
potential conflicts: Faithful Agent Duty Principle
principle category: professional_virtue
text references: Engineers have an obligation to perform services within their area of competence
text references: If Engineer B was not able to perform the necessary reviews of Engineer A's work, Engineer B should have provided this information to a supervisor who would have assigned an appropriate engineer to perform the review
text references: Not possessing adequate competency to perform a task is not in and of itself a violation of the NSPE Code, but the failure to recognize the lack of competency and take appropriate action to address the situation is a violation of the NSPE Code
value basis: Professional integrity, protection of the public from work product that has not received genuinely competent review, and honest representation of one's professional capabilities.
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:53:07.457315+00:00
first discovered in case: 85
match confidence: 0.78
match reasoning: The Competence Principle in the ontology balances professional autonomy with recognition of limitations and need for collaboration, which encompasses the self-assessment and escalation obligations described here. This is a variant that emphasizes the affirmative duty to recognize and act on competence limits rather than simply maintaining competence, but the parent class is the appropriate match. Confidence is 0.78 because the ontology class is broader and this individual instantiation has a specific emphasis on the recognition-and-escalation duty.
matched ontology class: CompetencePrinciple
matched ontology label: Competence Principle
matches existing: true
source text: Engineers have an obligation to perform services within their area of competence
comment: Professional principle requiring engineers to recognize the limits of their own competence and to take affirmative action when assigned tasks that exceed those limits, including notifying supervisors so that appropriately qualified personnel can be assigned. Lacking competence to perform a task is not itself a violation of professional standards, but failing to recognize that limitation and proceeding without remediation is a violation.
subclass of: ProfessionalVirtuePrinciple
scope note: [CompetencePrinciple] Balances professional autonomy with recognition of limitations and need for collaboration.
generated at time: 2026-06-04T16:53:07.457315+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Competence Reporting Capability
type: Class
capability category: communication
confidence: 0.8
domain specificity: General professional engineering practice
enables actions: Communicate competence concerns to the contractor or client
enables actions: Fulfill professional reporting obligations regarding peer competence
enables actions: Identify apparent competence deficiencies in another engineer's work
required for obligations: Competence Reporting Obligation
skill level: intermediate
text references: Engineer A had been unable to establish that Engineer B had any apparent subsequent training in foundation design, and Engineer A had reservations concerning the competence of Engineer B to design the structural footings and reported his concerns to the contractor
text references: the Board decided that Engineer A had an ethical responsibility to question Engineer B's competency and report his concerns to the contractor
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:50:08.208638+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineer A had been unable to establish that Engineer B had any apparent subsequent training in foundation design, and Engineer A had reservations concerning the competence of Engineer B to design the structural footings and reported his concerns to the contractor
comment: Capability of a licensed professional engineer to recognize when another engineer on the same project appears to lack the competence required to perform assigned technical work, and to report those concerns to the appropriate party such as the client, contractor, or responsible authority, in fulfillment of the professional obligation to protect public safety.
subclass of: Capability
generated at time: 2026-06-04T18:50:08.208638+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Reporting Engineer
type: Class
confidence: 0.82
role category: public_responsibility
text references: Engineer A had an ethical responsibility to question Engineer B's competency and report his concerns to the contractor
text references: Engineer A had reservations concerning the competence of Engineer B to design the structural footings and reported his concerns to the contractor
discovered in case: 121
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T18:43:21.046484+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineer A had reservations concerning the competence of Engineer B to design the structural footings and reported his concerns to the contractor
comment: A licensed professional engineering role in which the practitioner identifies and reports concerns about another engineer's lack of competence in a technical domain to the appropriate party, such as a contractor or client, fulfilling a professional obligation to protect public health and safety by ensuring that engineering work is performed only by those with adequate qualifications.
subclass of: EngineerRole
subclass of: PublicResponsibilityRole
generated at time: 2026-06-04T18:43:21.046484+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Reporting Obligation
type: Class
confidence: 0.9
derived from principle: Competence Boundary Principle
enforcement level: mandatory
monitoring criteria: Documented communication to the responsible party identifying specific competence concerns about another engineer's assigned work
nspe reference: II.2.a
obligation type: reporting
stakeholders affected: Client
stakeholders affected: Construction contractor
stakeholders affected: General public
stakeholders affected: Project owner
text references: Engineer A had reservations concerning the competence of Engineer B to design the structural footings and reported his concerns to the contractor
text references: the Board decided that it would be unethical for Engineer B to perform the design of the structural footings as part of the facility and that Engineer A had an ethical responsibility to question Engineer B's competency and report his concerns to the contractor
violation consequences: Professional discipline; public safety risk from unchallenged incompetent design
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:49:10.142160+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineer A had reservations concerning the competence of Engineer B to design the structural footings and reported his concerns to the contractor
comment: Duty of a licensed engineer who has reasonable grounds to question whether another engineer on the same project possesses the competence required to perform assigned technical work to report those concerns to the responsible party, such as the client or contractor, so that the public safety risk created by out-of-competence practice can be addressed.
subclass of: ReportingObligation
generated at time: 2026-06-04T18:49:10.142160+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Competence Scope Advisory Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.76
constraint type: competence
flexibility: soft
mitigation strategies: Disclose to the client which options fall outside the engineer's direct experience
mitigation strategies: Engage a co-advisor with complementary competence to cover all options
mitigation strategies: Limit the advisory scope to options within competence and explicitly state that limitation
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods.
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
violation impact: Client receives analysis skewed by advisor's competence gaps, options outside advisor's experience are unfairly excluded or underrepresented
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:47.831992+00:00
first discovered in case: 14
match confidence: 0.73
match reasoning: This maps to the existing Competence Constraint class as a variant applied specifically to the advisory context where uneven competence across options can distort the advice given. The existing class covers capability boundaries generally; this variant adds the advisory-distortion dimension. Matching as a variant with medium confidence.
matched ontology class: CompetenceConstraint
matched ontology label: Competence Constraint
matches existing: true
source text: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods.
comment: Competence constraint limiting an engineer providing advisory services to presenting and evaluating only those options for which the engineer possesses sufficient technical competence to give objective analysis, and requiring disclosure when the engineer's qualifications are uneven across the options being evaluated, so that the client can assess whether the advisory analysis is complete and unbiased.
subclass of: CompetenceConstraint
subclass of: DefeasibleConstraint
scope note: [CompetenceConstraint] Boundaries defined by agent capabilities and technical limitations (Hallamaa & Kalliokoski 2022)
generated at time: 2026-06-04T08:45:47.831992+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Competence Self-Assessment Capability
type: Class
capability category: awareness
confidence: 0.87
domain specificity: General professional engineering practice across all specialties
enables actions: Accurately represent qualifications to prospective clients
enables actions: Decline to offer services outside areas of established competence
enables actions: Identify domains in which the engineer lacks sufficient background to practice
enables actions: Recognize that possession of a software tool does not confer domain competence
required for obligations: Competence Boundary Obligation
required for obligations: Competence Misrepresentation Avoidance Obligation
skill level: intermediate
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: Engineer A, a chemical engineer with no facilities design and construction experience
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:46:28.378823+00:00
first discovered in case: 121
match confidence: 0.78
match reasoning: Competence Limit Recognition Capability covers recognizing the boundaries of one's own technical competence when assigned a task and taking appropriate action. This new capability is closely related but differs in emphasis: Competence Limit Recognition Capability is framed around a task assignment context where the engineer is asked to do something, whereas this capability concerns the proactive self-assessment required before offering services to the market. The holding-out and misrepresentation dimensions are not captured in the existing class. The match is a variant rather than identical, so medium confidence is appropriate.
matched ontology class: Competence Limit Recognition Capability
matched ontology label: Competence Limit Recognition Capability
matches existing: true
source text: Engineer A, a chemical engineer with no facilities design and construction experience
comment: Capability of a licensed professional engineer to accurately assess the boundaries of their own technical competence before offering or undertaking engineering services in a given domain, including the ability to recognize when a lack of education, training, or experience in a specialty area disqualifies the engineer from holding out services in that area regardless of the availability of automated tools or reference libraries.
subclass of: Capability
scope note: [CompetenceLimitRecognitionCapability] Capability to recognize the boundaries of one's own technical competence when assigned a professional task, to assess whether one possesses sufficient expertise to perform the task adequately, and to take appropriate action such as informing a supervisor or declining the assignment rather than proceeding with an inadequate review.
generated at time: 2026-06-04T18:46:28.378823+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Complete Design Delivery Obligation
type: Class
confidence: 0.88
derived from principle: Deliverable Completeness Disclosure Principle
enforcement level: mandatory
monitoring criteria: Whether the submitted drawings and specifications constitute a complete and buildable design conforming to applicable engineering standards at the time of submission
nspe reference: II.2, III.2.a
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Contractor
stakeholders affected: Funding agency
stakeholders affected: General public
text references: Engineer A was fully required to provide the complete design on the project.
text references: Engineer A's bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincing.
text references: It is clear that Engineer A had an obligation to provide a complete set of design drawings and specifications on the project in which Engineer A was engaged.
violation consequences: Professional discipline; potential fraud or misrepresentation findings; client and public harm from unbuildable or unsafe construction
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:54:40.172403+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: It is clear that Engineer A had an obligation to provide a complete set of design drawings and specifications on the project in which Engineer A was engaged.
comment: Duty of an engineer retained to produce a complete set of design drawings and specifications for a project to deliver a fully complete and buildable design conforming to applicable engineering standards, and to refrain from submitting partial or incomplete documents under seal when the scope of engagement requires full design completion, regardless of time pressures or expectations that supplemental funding will remedy deficiencies.
subclass of: EthicalObligation
generated at time: 2026-06-04T16:54:40.172403+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Complete Options Analysis Principle
type: Class
abstract nature: Requires judgment about which options are sufficiently material to require inclusion and what level of comparative analysis is adequate given the client's decision-making needs and the complexity of the choice.
confidence: 0.87
derived obligations: Disclose and justify any option excluded from analysis
derived obligations: Distinguish options the engineer can deliver from options the engineer cannot
derived obligations: Identify all approved or available project delivery methods
derived obligations: Provide comparative analysis of all material options
extensional examples: Advisory contexts where incomplete option sets lead clients to decisions they would not have made with full information
extensional examples: Cases where engineers omit viable alternatives from feasibility studies
operationalization: Requires engineers to identify all options approved or available under the applicable constraints, include each in the comparative analysis unless there is a documented and disclosed reason for exclusion, and present the analysis in a form that enables the client to understand the tradeoffs.
potential conflicts: Conflict of Interest Disclosure Principle
potential conflicts: Loyalty
principle category: professional_virtue
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
text references: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
value basis: Non-engineer clients depend on professional advisors to define the decision space accurately. Selective presentation of options distorts the client's ability to make an informed choice and transfers the engineer's judgment or interest into the client's decision without the client's awareness.
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:43:46.016802+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
comment: Professional principle requiring engineers who advise clients on selection among multiple available options to provide a reasonably complete and balanced analysis of all material options, not merely those options that favor the engineer's own interests or preferred outcome.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T08:43:46.016802+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Complete Report Inclusion Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Public Authority
confidence: 0.9
constraint type: ethical
flexibility: hard
mitigation strategies: Decline client instructions to omit material information
mitigation strategies: Include all material findings in written reports regardless of client preference
mitigation strategies: Review reports for completeness before submission
text references: Engineer L's identification of runoff risk is now 'fact.' Consistent with Code sections I.4, II.3.a, II.3.b, III.1.b, and III.3.a, Engineer L notified Client X of this risk.
text references: The BER noted that Engineer A was obligated under Code section II.3.a to be objective and truthful in professional reports, statements, or testimony and include all relevant and pertinent information in such reports.
text references: The key point of BER Case 07-6 is that information about the threat to the bird species is a 'fact' of the case.
violation impact: Report misleads relying parties; public authority makes decisions on incomplete information; engineer violates objectivity and truthfulness obligations.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:13.190895+00:00
first discovered in case: 8
match confidence: 0.92
match reasoning: The Complete Reporting Constraint in the ontology captures this concept: the requirement that an engineer preparing a technical report include all relevant and pertinent information, prohibiting selective omission of material technical facts. The BER Case 07-6 and Engineer L facts are direct instantiations.
matched ontology class: Complete Reporting Constraint
matched ontology label: Complete Reporting Constraint
matches existing: true
source text: The BER noted that Engineer A was obligated under Code section II.3.a to be objective and truthful in professional reports, statements, or testimony and include all relevant and pertinent information in such reports.
comment: Ethical and professional constraint requiring that an engineer's report, analysis, or advisory product include all relevant and pertinent information, prohibiting selective omission of material technical facts regardless of client preference, adversarial context, or the nature of the proceeding in which the report will be used.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [CompleteReportingConstraint] Requirement that an engineer preparing a technical report include all relevant and pertinent information, prohibiting selective omission of material technical facts regardless of the adversarial or client-service context in which the report is prepared.
generated at time: 2026-06-05T02:27:13.190895+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Complete Reporting Principle
type: Class
abstract nature: Open-textured obligation requiring judgment about what counts as relevant and pertinent, and how completeness is balanced against scope, but admitting no exception for adversarial convenience.
confidence: 0.95
derived obligations: Disclose equipment failures that affected test results
derived obligations: Enable independent expert interpretation by providing complete records
derived obligations: Include all material test data in reports
derived obligations: Present facts that may favor the opposing party
extensional examples: NSPE Code requirement that engineers include all relevant and pertinent information in reports, statements, or testimony
operationalization: Requires engineers to include material facts even when those facts complicate or contradict the preferred conclusion, to disclose equipment failures and anomalous conditions, and to present data that enables independent expert review.
potential conflicts: Client Advocacy
potential conflicts: Litigation Neutrality Principle
principle category: professional_virtue
text references: the Code of Ethics which requires that engineers 'shall include all relevant and pertinent information in such report, statements or testimony.'
text references: the report appears to serve no purpose except to impugn Engineer A, or to support the original testimony of the municipality's expert witness. As an engineering document the report is incomplete and does a disservice to Engineer B's client municipality by potentially misdirecting a conclusion.
text references: the select language of the report precludes any interpretation that any or all 90 piles met the factor of safety requirement. The opportunity for expert engineering review and interpretation of the pile driving test was effectively denied by Engineer B's report.
value basis: Technical reports derive their professional authority from comprehensiveness; selective reporting corrupts the epistemic function of engineering documentation and undermines trust in the profession.
discovered in case: 71
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:34:00.918915+00:00
first discovered in case: 71
match confidence: 0.92
match reasoning: The existing Scope Limitation Disclosure Principle addresses disclosure of limitations on investigation scope. This principle is distinct: it governs the completeness of reporting once facts are in hand, requiring inclusion of all pertinent data rather than merely disclosing what was not examined. The Investigative Completeness Principle governs evidence-gathering diligence. Neither captures the affirmative duty to include all relevant technical facts in the report itself, which is the core concern here.
matches existing: false
source text: the select language of the report precludes any interpretation that any or all 90 piles met the factor of safety requirement. The opportunity for expert engineering review and interpretation of the pile driving test was effectively denied by Engineer B's report.
comment: Professional principle requiring engineers to include all relevant and pertinent technical information in reports, statements, and testimony, without selective omission of facts that could alter the interpretation of findings or deny other parties the opportunity for expert review.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T14:34:00.918915+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Concern Fact Threshold Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Public Authority
confidence: 0.91
constraint type: ethical
flexibility: soft
mitigation strategies: Conduct sufficient analysis to determine whether a concern has become a fact before treating it as triggering mandatory disclosure
mitigation strategies: Disclose concerns voluntarily even when not required, with appropriate qualification
mitigation strategies: Document the basis for classifying a finding as a concern versus a fact
text references: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development.
text references: The BER's view is that, while it might be prudent for Engineer L to inform Client X of their concerns, such disclosure is not required under the Code.
text references: The key point of BER Case 07-6 is that information about the threat to the bird species is a 'fact' of the case.
text references: Thus, Engineer L's 'concern' does not rise to the technical or moral level of 'fact,' and per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts.
violation impact: Premature disclosure of unsubstantiated concerns may mislead clients and public authorities; failure to recognize when a concern has ripened into a fact may delay required disclosure.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:13.190895+00:00
first discovered in case: 8
match confidence: 0.93
match reasoning: The Concern Versus Fact Disclosure Constraint in the ontology directly captures this concept: a preliminary concern that has not been substantiated by sufficient analysis does not trigger the same mandatory disclosure obligations as a confirmed factual finding. The case text's distinction between Engineer L's early unquantified concern and the later confirmed risk finding is a direct application of that class.
matched ontology class: Concern Versus Fact Disclosure Constraint
matched ontology label: Concern Versus Fact Disclosure Constraint
matches existing: true
source text: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development.
comment: Ethical constraint establishing that mandatory public disclosure obligations attach only when an engineer's finding has reached the level of an established fact supported by sufficient technical analysis. A preliminary concern or suspicion that has not been substantiated does not trigger the same disclosure obligations as a confirmed factual finding, though prudent voluntary disclosure may be advisable.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [ConcernVersusFactDisclosureConstraint] Ethical constraint limiting an engineer's disclosure obligations to findings that have reached the level of established fact supported by technical analysis. A preliminary concern or suspicion that has not yet been substantiated by sufficient analysis does not trigger the same mandatory disclosure obligations as a confirmed factual finding, and an engineer is not required under professional ethics codes to disclose unsubstantiated concerns, though prudent disclosure may be advisable.
generated at time: 2026-06-05T02:27:13.190895+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Concurrent Engineering Action Obligation
type: Class
confidence: 0.85
derived from principle: Concurrent Safety Reporting Principle
enforcement level: mandatory
monitoring criteria: Evidence that engineers who jointly presented findings coordinated their escalation responses and that their regulatory submissions were consistent in technical content.
nspe reference: II.1.a, II.1.c
obligation type: collegial
stakeholders affected: General public
stakeholders affected: Professional peers
stakeholders affected: State regulatory agency
text references: It is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
violation consequences: Inconsistent or uncoordinated escalation actions by jointly presenting engineers may undermine the credibility and completeness of the safety report and reduce its effectiveness with regulatory authorities.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:28:12.343728+00:00
first discovered in case: 76
match confidence: 0.82
match reasoning: The Coordinated Escalation Obligation extracted from prior sections captures the duty of jointly presenting engineers to coordinate their escalation response. This class generalizes that concept for reuse across cases where multiple engineers must act in concert after a joint presentation is overruled.
matched ontology class: Coordinated Escalation Obligation
matched ontology label: Coordinated Escalation Obligation
matches existing: true
source text: It is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
comment: Duty of two or more engineers who have jointly presented findings and recommendations to a client to coordinate and act in concert when escalating safety concerns to regulatory authorities, ensuring that their subsequent actions are consistent and mutually reinforcing, even if not identical in form.
subclass of: CollegialObligation
generated at time: 2026-06-05T11:28:12.343728+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Concurrent Escalation Coordination Capability
type: Class
capability category: reasoning
confidence: 0.82
domain specificity: Public safety engineering with joint professional responsibility
enables actions: Agree on form, content, and target of regulatory notifications
enables actions: Coordinate post-override escalation steps with a co-presenting engineer
enables actions: Ensure escalation actions are consistent and not contradictory
required for obligations: Concurrent Engineering Action Obligation
required for obligations: Coordinated Escalation Obligation
required for obligations: Engineers A B Coordinated Escalation
skill level: advanced
text references: It is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:39.466339+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: It is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
comment: Capability of two or more engineers who have jointly presented professional findings to coordinate their escalation responses after a client override, ensuring that their actions are consistent, mutually reinforcing, and directed at the same authorities in a manner that accurately reflects their shared technical conclusions.
subclass of: Capability
generated at time: 2026-06-05T11:29:39.466339+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Concurrent Safety Reporting Principle
type: Class
abstract nature: Open-textured principle requiring judgment about the degree of coordination required and the appropriate division of reporting responsibilities between co-presenting engineers whose joint work has been overruled.
confidence: 0.82
derived obligations: Coordinate formal presentations to regulatory authorities
derived obligations: Jointly advise the client that the project will not be successful if safety measures are not adopted
derived obligations: Pursue further escalation in concert if formal presentations fail
extensional examples: BER Case No. 00-5 on public safety paramount obligation
extensional examples: BER Case No. 19-10 on obligation to pursue resolution through multiple channels
extensional examples: BER Case No. 89-7 on duty to report safety violations to appropriate authorities
operationalization: Requires engineers who jointly presented overruled recommendations to coordinate formal presentations to regulatory authorities, to advise the client formally and in concert, and to pursue further escalation together if initial formal presentations fail to produce remediation.
potential conflicts: Client confidentiality
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Individual professional autonomy
principle category: professional_virtue
text references: It is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
value basis: When engineers present findings jointly, the professional credibility and ethical weight of those findings derives from their joint nature, and coordinated follow-through is necessary to honor that joint commitment to the public.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:26:55.962095+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: It is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
comment: Professional principle requiring engineers who have jointly presented findings and recommendations to coordinate their safety reporting actions when those recommendations are overruled, proceeding in concert to notify clients, employers, and appropriate authorities, so that the force and credibility of the joint professional judgment is preserved and neither engineer's individual action is undermined by the silence of the other.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-05T11:26:55.962095+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Confidential Data Platform Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Licensing Board
affected stakeholders: Third Parties
confidence: 0.86
constraint type: confidentiality
flexibility: hard
mitigation strategies: Anonymize or redact confidential information before inputting into any AI platform
mitigation strategies: Obtain explicit client consent before using any third-party platform to process client data
mitigation strategies: Review AI platform terms of service for data retention and sharing policies before use
mitigation strategies: Use only secure, enterprise-grade AI tools with appropriate data handling agreements when processing confidential client data
text references: Engineer A gathered the relevant information provided by Client W and relied on the AI software to synthesize the information
text references: Engineer A input the information gathered from Client W into the AI software
text references: The AI drafting software was also open-sourced.
violation impact: Breach of client confidentiality, potential legal liability, loss of client trust, exposure of proprietary or sensitive site data to unauthorized parties, and disciplinary action.
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:33.588436+00:00
first discovered in case: 7
match confidence: 0.78
match reasoning: The Confidentiality Constraint class covers boundaries on information disclosure and privacy, which encompasses this scenario. However, the specific application to open-source AI platform data upload is a variant not explicitly addressed by the existing class. Matching as a variant of Confidentiality Constraint at medium confidence, while defining a more specific reusable subtype for AI platform contexts.
matched ontology class: ConfidentialityConstraint
matched ontology label: Confidentiality Constraint
matches existing: true
source text: Engineer A gathered the relevant information provided by Client W and relied on the AI software to synthesize the information
comment: Confidentiality constraint prohibiting an engineer from uploading or transmitting confidential client data to open-source, publicly accessible, or third-party AI platforms or software systems where the data may be exposed, retained, or used outside the confidential professional relationship.
subclass of: ConfidentialityConstraint
subclass of: InviolableConstraint
scope note: [ConfidentialityConstraint] Boundaries on information disclosure and privacy (Dennis et al. 2016)
generated at time: 2026-06-03T14:06:33.588436+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Confidential Peer Review Agreement State
type: Class
action constraints: Confidentiality does not override duty to report confirmed public safety risks
action constraints: Reviewer may not disclose findings to third parties beyond the scope of the agreement
activation conditions: Peer reviewer has signed a confidentiality agreement as a condition of the review engagement
activation conditions: Review is underway or completed under confidentiality terms
confidence: 0.85
obligation activation: Obligation to discuss safety concerns with the reviewed engineer before escalating
obligation activation: Obligation to inform authorities if safety violations cannot be resolved despite confidentiality agreement
obligation activation: Obligation to protect confidential findings from unauthorized disclosure
persistence type: inertial
principle transformation: Transforms general confidentiality principles into a structured duty that is defeasible when public safety is at risk, following the BER Case 96-8 pattern.
state category: information
termination conditions: Confidentiality agreement is released or modified
termination conditions: Public safety obligation overrides confidentiality per applicable professional standards
termination conditions: Review engagement concludes and obligations are discharged
text references: Engineer A contractually agreed not to disclose confidential information acquired in the review
text references: Such confidentiality agreements encourage the firm being reviewed to cooperate fully, build trust, and support a collegial atmosphere
discovered in case: 15
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-02T19:53:12.877625+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineer A contractually agreed not to disclose confidential information acquired in the review
comment: State in which a peer review is conducted under a contractual confidentiality agreement that restricts the reviewer from disclosing findings, creating a tension between confidentiality obligations and duties to report safety violations or inform the reviewed engineer.
subclass of: InformationState
generated at time: 2026-06-02T19:53:12.877625+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Confidential Peer Reviewer
type: Class
confidence: 0.78
role category: professional_peer
text references: Engineer A contractually agreed not to disclose confidential information acquired in the review
text references: Such confidentiality agreements encourage the firm being reviewed to cooperate fully, build trust, and support a collegial atmosphere
discovered in case: 15
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-02T19:52:44.921838+00:00
first discovered in case: 15
match confidence: 0.78
match reasoning: The confidential peer reviewer is a specialization of the Professional Peer Role, distinguished by the contractual confidentiality constraint layered onto the standard peer review relationship. The core obligation structure remains collegial review with mentoring and assessment duties.
matched ontology class: ProfessionalPeerRole
matched ontology label: Professional Peer Role
matches existing: true
source text: Engineer A contractually agreed not to disclose confidential information acquired in the review
comment: A professional engineering role in which the reviewer is bound by a contractual confidentiality agreement not to disclose information acquired during the peer review, while still retaining obligations to report safety violations to appropriate authorities if unresolved.
subclass of: ProfessionalPeerRole
scope note: [ProfessionalPeerRole] Collegial relationship with mentoring and review obligations
generated at time: 2026-06-02T19:52:44.921838+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Confidential Review Safety Disclosure Obligation
type: Class
confidence: 0.93
derived from principle: Public Safety Paramount
enforcement level: mandatory
monitoring criteria: Documented attempt to resolve concerns with reviewed engineer followed by report to appropriate authority when resolution fails
nspe reference: I.1
obligation type: safety
stakeholders affected: General public
stakeholders affected: Regulatory authorities
stakeholders affected: Reviewed engineer
text references: Engineer A had an obligation to immediately discuss these issues with Engineer B in order to seek clarification and resolution.
text references: In BER Case 96-8, Engineer A was a peer reviewer serving as part of an organized peer-review program. When selected as a reviewer for the program, Engineer A contractually agreed not to disclose confidential information acquired in the review.
text references: if Engineers A and B were unable to successfully resolve Engineer A's concerns, Engineer A had an obligation to first advise Engineer B that Engineer A had an obligation to inform the appropriate authorities, and then to so inform the appropriate authorities.
violation consequences: Potential harm to public; professional discipline for failure to report; liability exposure
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:59:48.608792+00:00
first discovered in case: 15
match confidence: 0.8
match reasoning: This is a specialization of the Reporting Obligation and Safety Obligation classes, distinguished by the condition that a confidentiality agreement is in place. It also maps closely to the Post-Termination Environmental Risk Reporting Obligation in structure, but applies to peer review contexts rather than post-termination scenarios. The safety-overrides-confidentiality logic makes it a distinct reusable type.
matched ontology class: ReportingObligation
matched ontology label: Reporting Obligation
matches existing: true
source text: In BER Case 96-8, Engineer A was a peer reviewer serving as part of an organized peer-review program. When selected as a reviewer for the program, Engineer A contractually agreed not to disclose confidential information acquired in the review.
comment: Duty of a peer reviewer bound by a contractual confidentiality agreement to nonetheless disclose safety code violations or public health risks to appropriate authorities when the reviewed engineer refuses to remedy the violations, notwithstanding the confidentiality agreement.
subclass of: SafetyObligation
scope note: [ReportingObligation] Duty to report violations or unsafe conditions to appropriate authorities
generated at time: 2026-06-02T19:59:48.608792+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Confidential Review Scope Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Design Engineer
affected stakeholders: Public
affected stakeholders: Reviewing Engineer
confidence: 0.83
constraint type: confidentiality
flexibility: soft
mitigation strategies: Clarify scope of confidentiality agreement before commencing review
mitigation strategies: Negotiate confidentiality terms that preserve safety disclosure obligations
mitigation strategies: Seek legal guidance on limits of confidentiality when safety is implicated
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
text references: When Owner reluctantly consents to notifying Engineer A, Engineer A objects and refused to consent to the peer review.
violation impact: Breach of contractual confidentiality obligations to client if findings are disclosed beyond agreed scope; however, failure to disclose safety-critical findings may create separate ethical and safety violations.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:27.688172+00:00
first discovered in case: 15
match confidence: 0.88
match reasoning: This constraint maps directly to the existing Confidentiality Constraint class, which covers boundaries on information disclosure and privacy. The specific application involves the scope and limits of a confidentiality agreement governing peer review findings. It is a variant of the existing class rather than a new concept.
matched ontology class: ConfidentialityConstraint
matched ontology label: Confidentiality Constraint
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
comment: Confidentiality constraint arising when a peer review is conducted under a confidentiality agreement with the client, limiting the reviewer's ability to disclose findings to third parties including the reviewed engineer, while not eliminating overriding safety disclosure obligations.
subclass of: ConfidentialityConstraint
subclass of: DefeasibleConstraint
scope note: [ConfidentialityConstraint] Boundaries on information disclosure and privacy (Dennis et al. 2016)
generated at time: 2026-06-02T19:57:27.688172+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Confidentiality Limit Recognition Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: Professional engineering ethics, applicable across environmental, civil, and other engineering disciplines
enables actions: Assess whether a prior engagement creates a confidentiality duty that would bar regulatory reporting
enables actions: Conclude that confidentiality does not override the obligation to report substantial legal violations
enables actions: Distinguish between protected client information and reportable violations of public law
required for obligations: Confidentiality Limits Public Law Obligation
required for obligations: Environmental Compliance Reporting Obligation
skill level: advanced
text references: Engineer A performs wetland delineation services on the client's wetland site.
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:31:02.848953+00:00
first discovered in case: 86
match confidence: 0.87
match reasoning: Confidentiality Scope Reasoning Capability is defined as the capability to reason about the limits of confidentiality obligations, distinguishing between protecting the contents of a review and using confidentiality as a basis for procedurally improper conduct. The present capability is the same concept applied to the public law reporting context rather than a peer review context. The match is high-confidence because the core reasoning structure is identical: determining when confidentiality ends and a competing obligation begins.
matched ontology class: Confidentiality Scope Reasoning Capability
matched ontology label: Confidentiality Scope Reasoning Capability
matches existing: true
source text: Engineer A performs wetland delineation services on the client's wetland site.
comment: Capability to recognize that professional confidentiality obligations owed to a client do not extend to concealing the client's violations of public law or regulation, including the ability to reason about the boundary between legitimate confidentiality and impermissible use of confidentiality as a shield against regulatory reporting obligations.
subclass of: Capability
scope note: [ConfidentialityScopeReasoningCapability] Capability to reason about the limits of confidentiality obligations, distinguishing between protecting the contents of a review and using confidentiality as a basis for procedurally improper conduct such as covert review.
generated at time: 2026-06-04T17:31:02.848953+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Confidentiality Limits Public Law Obligation
type: Class
confidence: 0.83
derived from principle: Post-Engagement Client Conduct Disclosure Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer did not allow confidentiality concerns to prevent reporting of a directly observed, substantial violation of law to the appropriate authority.
nspe reference: I.1, III.4
obligation type: ethical
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: Engineer A performs wetland delineation services on the client's wetland site.
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
text references: he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
violation consequences: Invoking confidentiality to shield a client's ongoing statutory violation from regulatory authorities constitutes a misuse of the confidentiality obligation and may result in professional discipline.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:30:01.042237+00:00
first discovered in case: 86
match confidence: 0.72
match reasoning: The existing Client Instruction Limits Obligation addresses the duty to decline client instructions that would require violating professional ethics. The present class addresses the analogous situation where a confidentiality obligation, rather than a client instruction, is invoked to shield a statutory violation. The concept is related but distinct enough to warrant a separate class. The existing Confidentiality Obligation class in the ontology is too general. The closest match is Client Instruction Limits Obligation as a structural analog, but confidence is moderate because the mechanism differs.
matched ontology class: Client Instruction Limits Obligation
matched ontology label: Client Instruction Limits Obligation
matches existing: true
source text: Engineer A performs wetland delineation services on the client's wetland site.
comment: Duty of an engineer to recognize that confidentiality obligations owed to a client do not extend to concealing the client's substantial violations of federal or state law that implicate public welfare or environmental protection, and that the duty to report such violations to appropriate authorities overrides any residual confidentiality interest in the information.
subclass of: EthicalObligation
scope note: [ClientInstructionLimitsObligation] Duty of an engineer to decline client instructions that would require violating professional ethics obligations, recognizing that the faithful agent duty does not extend to complying with directives that breach professional standards.
generated at time: 2026-06-04T17:30:01.042237+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Confidentiality Public Violation Limit Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.8
constraint type: confidentiality
flexibility: hard
mitigation strategies: Distinguish between confidential professional information and evidence of confirmed legal violations
mitigation strategies: Recognize that professional confidentiality does not protect client illegality
mitigation strategies: Report confirmed violations to regulatory authorities regardless of prior confidential relationship
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
violation impact: Treating confidentiality as a shield for a client's illegal conduct exposes the engineer to professional discipline and complicity in ongoing harm to public resources.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:30:49.666256+00:00
first discovered in case: 86
match confidence: 0.72
match reasoning: The Confidentiality Safety Override Constraint addresses the scenario where a confidentiality obligation is overridden by a safety disclosure duty. The present constraint is a variant applied to the post-engagement context where the confidentiality relationship has ended and the violation is of environmental law rather than a safety code discovered during peer review. The concept is sufficiently similar to warrant matching to the existing class at medium confidence, though the post-engagement and environmental law dimensions are distinguishing features.
matched ontology class: Confidentiality Safety Override Constraint
matched ontology label: Confidentiality Safety Override Constraint
matches existing: true
source text: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
comment: Constraint establishing that a confidentiality obligation owed to a client does not extend to concealing the client's confirmed violation of applicable federal or state law or regulation, particularly where the violation poses a risk to public health, safety, or the environment. The confidentiality duty is bounded by the engineer's overriding obligation to hold public welfare paramount and to comply with applicable law.
subclass of: ConfidentialityConstraint
subclass of: InviolableConstraint
scope note: [ConfidentialitySafetyOverrideConstraint] Constraint arising when a peer reviewer operating under a contractual confidentiality agreement discovers safety code violations. The confidentiality obligation does not eliminate the reviewer's duty to first seek resolution with the reviewed engineer and then, if unresolved, to notify appropriate authorities. The safety disclosure obligation overrides the confidentiality restriction when public health, safety, and welfare are at risk.
generated at time: 2026-06-04T17:30:49.666256+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Confidentiality of Professional Review
type: Class
abstract nature: Requires balancing the contractual and ethical duty to protect client-commissioned review information against the obligation to notify the reviewed engineer and to act on safety findings.
confidence: 0.85
derived obligations: Decline engagements that require violating notification obligations as a condition of confidentiality
derived obligations: Distinguish between confidentiality of findings and concealment of the review's existence
derived obligations: Protect review findings from unauthorized third-party disclosure
extensional examples: Cases involving the tension between client-imposed confidentiality and professional notification obligations
extensional examples: NSPE BER Case 94-7 addressing confidentiality obligations of peer reviewers
operationalization: Engineer B's contractual confidentiality obligation covers the contents and findings of the review but does not justify concealing the existence of the review from Engineer A, because that concealment would itself violate a separate professional obligation.
potential conflicts: Public Safety
potential conflicts: Transparency
principle category: relational
text references: Engineer B objects to conducting the peer review without advising Engineer A
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
value basis: Clients have legitimate interests in controlling sensitive professional review processes, but those interests do not extend to requiring reviewers to conceal the existence of a review from the engineer whose work is being reviewed.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:55:30.891672+00:00
first discovered in case: 15
match confidence: 0.82
match reasoning: The principle is a variant of the existing Confidentiality Principle, which is described as requiring balance against public safety obligations and legal disclosure requirements. The peer review context adds a specific dimension involving notification obligations to the reviewed engineer, but the underlying principle is the same Confidentiality Principle already in the ontology.
matched ontology class: ConfidentialityPrinciple
matched ontology label: Confidentiality Principle
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
comment: Relational principle governing the obligations of a peer reviewer who has entered a contractual confidentiality agreement, requiring the reviewer to protect information obtained during the review from unauthorized disclosure while still fulfilling safety obligations.
subclass of: RelationalPrinciple
scope note: [ConfidentialityPrinciple] Must be balanced against public safety obligations and legal disclosure requirements.
generated at time: 2026-06-02T19:55:30.891672+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Confirmed Environmental Law Violation State
type: Class
action constraints: Confidentiality obligations do not override reporting duties when environmental law is violated
action constraints: Professional may not remain silent once a confirmed legal violation is identified
action constraints: Remedial actions must comply with all applicable environmental laws and may require licensed engineer review
activation conditions: Professional has relevant expertise to recognize the violation
activation conditions: Professional identifies client conduct that constitutes a violation of environmental law or regulation
activation conditions: Violation is confirmed rather than speculative
confidence: 0.88
obligation activation: Obligation to advise client that immediate remedial steps are required
obligation activation: Obligation to contact client and identify the violation directly
obligation activation: Obligation to monitor situation until remediation is confirmed
obligation activation: Obligation to report to appropriate authorities if client fails to act
persistence type: inertial
principle transformation: Transforms the general duty to hold public safety paramount into a concrete sequential protocol: direct client notification, monitored remediation, and escalation to regulatory authorities upon client inaction.
state category: risk
termination conditions: Client completes remediation in full compliance with applicable environmental laws
termination conditions: Professional reports to appropriate regulatory authorities
termination conditions: Regulatory authority confirms compliance
text references: Engineer A's actions appear to be obvious: contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
text references: If appropriate steps are not taken by the client, the engineer would have an obligation to bring this matter to the attention of the appropriate authorities.
text references: The facts in the present case indicate a violation of the federal and state laws and regulations.
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:27:19.652589+00:00
first discovered in case: 86
match confidence: 0.78
match reasoning: The Confirmed Risk Without Adequate Safeguards State covers situations where a professional has confirmed a concrete public-safety or environmental risk and adequate safeguards are absent, which is the canonical activator for post-termination reporting obligations. The present state is a specific instantiation of that pattern applied to a confirmed environmental law violation. The match is medium because the existing class is framed around public-safety risk and safeguard absence, while the present state is specifically about legal violation and remediation obligation, but the ethical structure is the same.
matched ontology class: ConfirmedRiskWithoutAdequateSafeguardsState
matched ontology label: Confirmed Risk Without Adequate Safeguards State
matches existing: true
source text: The facts in the present case indicate a violation of the federal and state laws and regulations.
comment: State in which a professional has identified that a client has committed a confirmed violation of applicable federal or state environmental laws or regulations, such as unpermitted wetland filling, creating an obligation to notify the client, demand immediate remediation, monitor the client's response, and report to appropriate authorities if adequate corrective action is not taken.
subclass of: RiskState
scope note: [ConfirmedRiskWithoutAdequateSafeguardsState] State in which a professional has confirmed the existence of a concrete public-safety or environmental risk and adequate safeguards are known to be absent. Typical activator for post-termination reporting obligations and for defeating faithful-agent confidentiality (NSPE BER Case 72 pattern).
generated at time: 2026-06-04T17:27:19.652589+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Conflict of Interest Disclosure Principle
type: Class
abstract nature: Open-textured value requiring judgment about what interests are material enough to require disclosure and how disclosure should be made to preserve client trust and decision-making integrity.
confidence: 0.88
derived obligations: Disclose financial or competitive interest in recommended options
derived obligations: Distinguish advisory role from service-provider role
derived obligations: Ensure client understands the basis and potential bias of any recommendation
extensional examples: Cases where engineers recommend delivery methods in which they hold a competitive advantage
extensional examples: NSPE BER Case 76-4 on engineer recommending own services
operationalization: Requires engineers to identify any personal interest in the outcome of a recommendation, disclose that interest to the client before or alongside the recommendation, and ensure the client can make an informed independent judgment.
potential conflicts: Loyalty
potential conflicts: Professional Competence
principle category: professional_virtue
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods
text references: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
value basis: Clients, especially non-engineer clients, rely on professional advisors to provide unbiased guidance and cannot independently assess whether a recommendation serves the advisor's interests rather than their own.
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:43:46.016802+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
comment: Professional principle requiring engineers to disclose personal or financial interests that may bias their professional recommendations, particularly when the recommended course of action would benefit the recommending engineer directly.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T08:43:46.016802+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Conflict of Interest Recognition Capability
type: Class
capability category: awareness
confidence: 0.82
domain specificity: Professional engineering advisory services, particularly where the advisor is also qualified to perform services under one or more of the options being evaluated
enables actions: Disclose competitive interest to client
enables actions: Identify personal stake in advisory outcomes
enables actions: Recognize when advisory role intersects with potential service provider role
required for obligations: Advisory Conflict Disclosure Obligation
required for obligations: Advisory Role Objectivity Obligation
skill level: intermediate
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods
text references: Engineer A recommended Progressive Design Build. Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:39.966147+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods
comment: Capability to identify when a personal, financial, or competitive interest in the outcome of a professional recommendation creates a conflict with the duty to provide objective advice, and to recognize the obligation to disclose that interest to the client before or alongside the recommendation.
subclass of: Capability
generated at time: 2026-06-04T08:45:39.966147+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Consent-Independent Safety Reporting Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.87
constraint type: ethical
flexibility: hard
mitigation strategies: Coordinate with co-engineers to act consistently and without waiting for client authorization
mitigation strategies: Document the basis for proceeding independently of client approval
mitigation strategies: Proceed with regulatory notification and formal presentation without seeking client consent
text references: as Engineers A and B are required to hold paramount the safety, health, and welfare of the public, and as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required
violation impact: Engineer subordinates paramount public safety duty to client authority, confirmed public health risk goes unreported, engineer violates professional ethics code.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:35.133297+00:00
first discovered in case: 76
match confidence: 0.75
match reasoning: The Public Safety Paramount Constraint establishes that the duty to hold public safety paramount takes precedence over obligations to clients and cannot be overridden by client instructions. The present constraint is a specific application of that principle to the consent question in regulatory reporting, making it a variant. The Client Consent Independence Obligation extracted earlier captures the obligation side; this constraint captures the boundary that client consent cannot gate safety reporting. Medium-confidence variant match to the parent is appropriate.
matched ontology class: Public Safety Paramount Constraint
matched ontology label: Public Safety Paramount Constraint
matches existing: true
source text: as Engineers A and B are required to hold paramount the safety, health, and welfare of the public, and as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required
comment: Ethical constraint establishing that an engineer's duty to report a confirmed public health or safety risk to regulatory authorities does not require and cannot be conditioned on the consent or approval of the client or governing body whose decision created or perpetuated the risk. The engineer must proceed with required safety reporting regardless of whether the client consents, objects, or remains silent.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [PublicSafetyParamountConstraint] Inviolable ethical constraint establishing that an engineer's duty to hold paramount the safety, health, and welfare of the public takes precedence over obligations to clients, employers, and other parties. This constraint governs all professional decisions and cannot be overridden by client instructions, economic pressures, or contractual obligations.
generated at time: 2026-06-05T11:29:35.133297+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Construction Services Engineer
type: Class
confidence: 0.8
role category: provider_client
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods
text references: Engineer A provides construction services in the community of City B
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:41:03.751066+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A provides construction services in the community of City B
comment: A licensed professional engineering role in which the practitioner is qualified to deliver construction-phase services under specific project delivery methods such as Progressive-Design-Build or Construction-Manager-at-Risk, bearing professional accountability for both technical and advisory outputs provided to clients.
subclass of: EngineerRole
subclass of: ProviderClientRole
generated at time: 2026-06-04T08:41:03.751066+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Constructor Client
type: Class
confidence: 0.8
role category: provider_client
text references: Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes
text references: it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:46:00.156208+00:00
first discovered in case: 85
match confidence: 0.82
match reasoning: Contractor Role in the ontology covers a party contracted to carry out construction work, which matches Hi-Lo Construction's position as the awarded low bidder. Engineer C as owner of the firm also brings engineering judgment to bear, but the primary role here is the contracting party identifying design deficiencies.
matched ontology class: ContractorRole
matched ontology label: Contractor Role
matches existing: true
source text: it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications
comment: A contractor or construction firm that is awarded a construction contract and acts as a technical participant at pre-construction conferences, identifying design deficiencies or unbuildable elements in drawings and specifications provided by the design engineer.
subclass of: ClientRole
subclass of: ProviderClientRole
scope note: [ContractorRole] Party contracted to carry out construction work.
generated at time: 2026-06-04T16:46:00.156208+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Contractor Deficiency Notification Obligation
type: Class
confidence: 0.8
derived from principle: Complete Reporting Principle
enforcement level: prima_facie
monitoring criteria: Documented formal notification to client and design engineer of identified deficiencies at or before the pre-construction conference
nspe reference: II.1.a, II.5.b, III.2.b
obligation type: collegial
stakeholders affected: Client
stakeholders affected: Design engineer
stakeholders affected: General public
text references: it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes
violation consequences: Proceeding with construction on deficient documents; potential public safety risk; professional discipline for failure to report known deficiencies
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:50:13.568162+00:00
first discovered in case: 85
match confidence: 0.72
match reasoning: Observer Irregularity Reporting Obligation addresses the duty to document and report procedural irregularities during a test or investigation. The present obligation applies to a contractor-engineer who identifies design deficiencies in documents during pre-construction review rather than during a test. The underlying duty to report identified deficiencies to responsible parties is analogous but the role context and trigger conditions are sufficiently distinct to warrant a separate class.
matched ontology class: Observer Irregularity Reporting Obligation
matched ontology label: Observer Irregularity Reporting Obligation
matches existing: true
source text: it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes
comment: Duty of a licensed engineer who is also a contractor, upon identifying material deficiencies or unbuildable elements in design documents during bid review or pre-construction processes, to formally document and report those deficiencies to the client and design engineer so that the deficiencies can be remedied before construction proceeds.
subclass of: CollegialObligation
scope note: [ObserverIrregularityReportingObligation] Duty of an engineer or geotechnical consultant retained to observe a test or investigation to document and report procedural irregularities, equipment failures, or methodological deviations that could affect the validity of the results, and to communicate these findings to the retaining party promptly.
generated at time: 2026-06-04T16:50:13.568162+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Contradictory Evidence Disclosure Obligation
type: Class
confidence: 0.9
derived from principle: Investigative Completeness Principle
enforcement level: mandatory
monitoring criteria: Report explicitly addresses known contradictory data or analytical results and explains why conclusions were reached despite them
nspe reference: III.2
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: Court or mediating body
stakeholders affected: General public
stakeholders affected: Opposing party
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
text references: Engineer B's report presented conclusions about pile inadequacy without acknowledging the existence of wave equation analysis that contradicted those conclusions.
violation consequences: Professional discipline; report may be discredited; potential liability for misleading findings
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:31:15.630641+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing obligation class in the ontology corresponds to this duty. This is a new class.
matches existing: false
source text: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
comment: Duty of an engineer preparing a technical report or expert opinion to acknowledge and address evidence or accepted analytical methods that contradict or materially qualify the conclusions presented, rather than omitting such evidence from the report.
subclass of: DisclosureObligation
generated at time: 2026-06-04T14:31:15.630641+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Contradictory Evidence Omission Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Opposing parties
affected stakeholders: Public
affected stakeholders: Retained engineer
affected stakeholders: Tribunal
confidence: 0.92
constraint type: ethical
flexibility: hard
mitigation strategies: Apply analytical methods consistently to all relevant data
mitigation strategies: Decline to issue conclusions that cannot be supported without omitting contrary evidence
mitigation strategies: Include all material contradictory evidence with explanation
text references: Additionally, Engineer B did not report that the dynamic test equipment had failed.
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
violation impact: Misleading tribunal or decision-maker, professional discipline, reputational harm, unjust outcome in dispute
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology captures the hard prohibition on omitting contradictory evidence from a technical report. The obligation-side Contradictory Evidence Disclosure Obligation is a duty; this is the corresponding inviolable boundary on conduct.
matches existing: false
source text: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
comment: Prohibition on preparing a technical report or expert opinion that omits known, material evidence or accepted analytical results that contradict the report's conclusions, regardless of client preference or adversarial context.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Contradictory Evidence Recognition Capability
type: Class
capability category: awareness
confidence: 0.91
domain specificity: Technical reporting and expert opinion in geotechnical and structural engineering
enables actions: Acknowledge contradictory evidence in technical reports
enables actions: Apply accepted analytical methods such as wave equation analysis to cross-check findings
enables actions: Assess the weight of competing lines of evidence
enables actions: Recognize when available data conflicts with the primary conclusion
required for obligations: Contradictory Evidence Disclosure Obligation
skill level: advanced
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
text references: Engineer B was obligated to acknowledge in the report the wave equation analysis showing the 19 piles had driven to essential refusal.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class covers the awareness competency of identifying and incorporating contradictory evidence or alternative accepted analytical methods into a technical report.
matches existing: false
source text: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
comment: Ability to identify evidence or accepted analytical methods that contradict or qualify the primary conclusions of a technical report, and to incorporate that evidence into the analysis rather than omitting it.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Cooperative Peer Review Obligation
type: Class
abstract nature: Character-based obligation whose content varies with the severity of known defects, the legitimacy of the review process, and the degree of public risk involved, but which cannot be waived by personal discomfort or client-imposed pressure.
confidence: 0.87
derived obligations: Acknowledge and address identified errors
derived obligations: Engage constructively with reviewer concerns
derived obligations: Provide access to design documents and records
derived obligations: Refrain from obstructing or limiting the review
extensional examples: NSPE BER Case 96-8 where peer reviewer discovered safety code violations and had obligation to seek resolution with original engineer
operationalization: Requires the engineer under review to provide access to design documents, answer reviewer questions, explain design decisions, and engage constructively with identified concerns rather than refusing participation.
potential conflicts: Client Loyalty Limits
potential conflicts: Confidentiality of Professional Review
principle category: professional_virtue
text references: Each of those requirements strongly indicates that Engineer A should participate fully and cooperatively in Engineer B's peer review.
text references: Engineers must take responsibility for their actions, must acknowledge their errors, must act in the best interests of their clients, and must at all times hold paramount the health, welfare, and safety of the public.
text references: The Board concludes that it would be unethical for Engineer A to fail to cooperate.
text references: The known design defects in the first tower simply makes each of those requirements more urgent.
value basis: Professional accountability and the recognition that engineers must accept responsibility for their work product and submit to legitimate oversight, especially when public safety is implicated.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:58:41.183712+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: The Board concludes that it would be unethical for Engineer A to fail to cooperate.
comment: Professional virtue principle requiring an engineer whose work is subject to a legitimate peer review to participate fully and cooperatively in that process, particularly when known errors in the work create risks to public safety.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-02T19:58:41.183712+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Coordinated Joint Action Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Co-Engineer
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.82
constraint type: procedural
flexibility: soft
mitigation strategies: Agree on the form, content, and target of regulatory notifications before submission
mitigation strategies: Document the coordination process and any agreed division of responsibilities
mitigation strategies: Ensure that individual actions by each engineer are consistent with the jointly presented findings
mitigation strategies: Share draft formal presentations between co-engineers for review and alignment
text references: it is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical
violation impact: Inconsistent or contradictory professional positions undermine the credibility of safety findings, regulatory authorities receive a confused record, public health protection is weakened.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:35.133297+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: it is important to note that Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical
comment: Ethical and procedural constraint arising when two or more engineers have jointly presented findings and recommendations to a client or governing body, requiring that their subsequent escalation and reporting actions be coordinated and consistent, though not necessarily identical, so that the professional record presented to regulatory authorities and other parties is coherent and mutually reinforcing rather than contradictory or fragmented.
subclass of: DefeasibleConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-05T11:29:35.133297+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Corrosion Control Assessment Capability
type: Class
capability category: domain_specific
confidence: 0.88
domain specificity: Water treatment engineering and public water supply corrosion control
enables actions: Assess lead leaching risk from aging distribution infrastructure
enables actions: Evaluate corrosion risk from water source changes
enables actions: Specify required treatment improvements before source transition
required for obligations: Drinking Water Safety Obligation
required for obligations: Engineer B Drinking Water Safety
required for obligations: Public Health Risk Disclosure Obligation
skill level: expert
text references: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline for further evaluation of water quality, design, and construction of improvements.
text references: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards.
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:25:14.530972+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline for further evaluation of water quality, design, and construction of improvements.
comment: Technical capability to evaluate corrosion control requirements for a public water distribution system, including the ability to assess whether existing infrastructure such as old service pipes will leach contaminants such as lead at levels exceeding drinking water standards when water chemistry changes, and to specify the improvements required to prevent such leaching before a source change is implemented.
subclass of: Capability
generated at time: 2026-06-05T11:25:14.530972+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Cost Allocation Bias Prohibition Principle
type: Class
abstract nature: Requires engineers to maintain the same standard of completeness and adequacy in their deliverables regardless of who will ultimately pay for deficiencies, recognizing that cost-shifting reasoning corrupts professional judgment.
confidence: 0.85
derived obligations: Deliver complete and adequate drawings and specifications regardless of funding source
derived obligations: Refrain from rationalizing deficient work on the basis that a third-party funder will absorb the cost
derived obligations: Treat public grant funds with the same fiduciary care as client funds
extensional examples: Engineer delivers deficient specifications reasoning that change orders will be funded by a third party
extensional examples: Engineer submits incomplete dam design reasoning that federal grant funds will cover cost overruns, insulating the local client from financial harm
operationalization: Engineers must evaluate the adequacy of their work product against objective professional standards, not against assumptions about who will pay if the work is deficient. The source of project funding does not alter the engineer's obligation to deliver complete and adequate work.
potential conflicts: Client cost minimization interests
potential conflicts: Schedule pressure
principle category: professional_virtue
text references: While much of the information was missing from the drawings and specifications, Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs.
value basis: Professional standards of completeness and adequacy are not contingent on the identity of the party who bears remediation costs. Allowing cost-allocation assumptions to lower the standard of care undermines the integrity of the profession and misuses public funds.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:49:05.036482+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: While much of the information was missing from the drawings and specifications, Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs.
comment: Professional integrity principle prohibiting engineers from allowing assumptions about which party will bear the financial consequences of deficient work to influence the decision to submit incomplete or inadequate work product. An engineer may not rationalize delivering deficient deliverables on the basis that remediation costs will fall on a third-party funder rather than the client.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T16:49:05.036482+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Cost Allocation Neutrality Obligation
type: Class
confidence: 0.85
derived from principle: Cost Allocation Bias Prohibition Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer's submission decisions were made on the basis of professional adequacy rather than assumptions about cost absorption by federal or other third-party funds
nspe reference: II.4, II.5.a, III.2
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Federal funding agency
stakeholders affected: General public
stakeholders affected: Taxpayers
text references: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs
violation consequences: Professional discipline; breach of fiduciary duty to client; potential misuse of public funds
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:50:13.568162+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs
comment: Duty of an engineer to make professional decisions, including decisions about the completeness and quality of deliverables, without regard to assumptions about which party will bear the financial consequences of deficiencies, and to refrain from rationalizing submission of incomplete work on the basis that anticipated funding sources will absorb resulting cost overruns.
subclass of: EthicalObligation
generated at time: 2026-06-04T16:50:13.568162+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Cost Assumption Neutrality Capability
type: Class
capability category: reasoning
confidence: 0.85
domain specificity: Publicly funded engineering projects involving federal and local cost-sharing arrangements
enables actions: Identify when cost-allocation assumptions are distorting professional judgment
enables actions: Produce complete deliverables regardless of assumptions about who will bear cost overruns
enables actions: Separate funding-source considerations from completeness and quality decisions
required for obligations: Cost Allocation Neutrality Obligation
required for obligations: Deliverable Completeness Disclosure Obligation
skill level: intermediate
text references: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:51:18.309339+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs.
comment: Capability to recognize when assumptions about funding source allocation or cost responsibility are influencing professional decisions about deliverable completeness or quality, and to set aside those assumptions so that professional decisions are made on technical and ethical grounds rather than on anticipated financial benefit to the engineer.
subclass of: Capability
generated at time: 2026-06-04T16:51:18.309339+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Cost Assumption Neutrality Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Federal Agency
affected stakeholders: Public
affected stakeholders: Taxpayers
confidence: 0.8
constraint type: ethical
flexibility: hard
mitigation strategies: Disclose the funding assumption to the client and obtain confirmation before relying on it
mitigation strategies: Produce a complete deliverable regardless of assumptions about cost allocation
mitigation strategies: Seek written client authorization if proceeding with a known incomplete product
text references: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs.
violation impact: Incomplete deliverables are submitted and approved on the false premise that downstream cost consequences are acceptable, exposing public agencies and taxpayers to unplanned expenditures and project failure.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:51:16.118939+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs.
comment: Ethical constraint prohibiting an engineer from rationalizing the submission of an incomplete or potentially cost-escalating work product on the basis of an undisclosed assumption about how cost overruns will be funded, particularly when that assumption involves public funds the engineer does not control and has not verified. The engineer must make professional decisions about deliverable completeness independently of speculative funding assumptions.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T16:51:16.118939+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Covert Review Prohibition Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Original Design Engineer
affected stakeholders: Public
affected stakeholders: Reviewing Engineer
confidence: 0.88
constraint type: ethical
flexibility: hard
mitigation strategies: Decline client instructions that require covert review
mitigation strategies: Notify the original engineer before commencing review
mitigation strategies: Seek ethics guidance before proceeding
text references: Engineer B objects to conducting the peer review without advising Engineer A.
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
violation impact: Violation of professional ethics, potential disciplinary action, undermining of collegial professional relationships, and invalidation of review process integrity.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:27.688172+00:00
first discovered in case: 15
match confidence: 0.78
match reasoning: This constraint is a specific ethical boundary on permissible review conduct derived from professional ethics codes. It is a variant of the general Ethical Constraint class, with the distinguishing feature being the prohibition on covert peer review. It also has partial overlap with Non-Deception (Constraint) from the ontology, since conducting a covert review involves a form of professional deception toward the reviewed engineer. The best parent match is Ethical Constraint as the broader category, with Non-Deception (Constraint) as a closely related provision.
matched ontology class: EthicalConstraint
matched ontology label: Ethical Constraint
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
comment: Ethical constraint prohibiting a reviewing engineer from conducting a peer review of another engineer's work without first notifying and obtaining the knowledge of the engineer whose work is under review, as required by professional courtesy and ethics codes.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [EthicalConstraint] Professional ethical boundaries beyond legal requirements (Benzmüller et al. 2020)
generated at time: 2026-06-02T19:57:27.688172+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Covert Review Refusal Obligation
type: Class
confidence: 0.85
derived from principle: Professional Integrity
enforcement level: mandatory
monitoring criteria: Evidence that the reviewing engineer refused or objected to covert review instructions and insisted on proper notification
nspe reference: II.4
obligation type: ethical
stakeholders affected: Original design engineer
stakeholders affected: Professional engineering community
stakeholders affected: Project owner
text references: Engineer B objects to conducting the peer review without advising Engineer A.
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
violation consequences: Violation of professional ethics code; potential disciplinary action; harm to the reviewed engineer's professional standing
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:56:24.847658+00:00
first discovered in case: 15
match confidence: 0.75
match reasoning: This obligation is a specific instantiation of the broader Ethical Obligation class, operationalizing the duty to refuse client instructions that violate professional transparency and collegial norms. The existing Ethical Obligation class covers duties arising from professional codes and moral reasoning, which encompasses this refusal duty. Medium confidence because the existing class is more general.
matched ontology class: EthicalObligation
matched ontology label: Ethical Obligation
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
comment: Duty of a peer review engineer to decline instructions from a client or employer to conduct a review of another engineer's work without that engineer's knowledge, when such concealment would violate professional transparency norms.
subclass of: EthicalObligation
scope note: [EthicalObligation] Obligations arising from ethical principles beyond legal requirements
generated at time: 2026-06-02T19:56:24.847658+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Covert Review Request State
type: Class
action constraints: Reviewing professional should insist on notifying the subject professional
action constraints: Reviewing professional should not proceed under covert conditions
activation conditions: Client instructs reviewer to withhold engagement from subject professional
activation conditions: Peer review or evaluation is commissioned without notifying the professional whose work is under review
confidence: 0.85
obligation activation: Obligation to object to or refuse covert review conditions
obligation activation: Professional courtesy notification obligation
obligation activation: Transparency duty toward peer professional
persistence type: non_inertial
principle transformation: Transforms general professional courtesy and fairness principles into a concrete notification obligation before accepting or conducting a peer review engagement.
state category: conflict
termination conditions: Client withdraws the covert instruction
termination conditions: Reviewing professional declines the engagement
termination conditions: Subject professional is notified of the review
text references: Engineer B objects to conducting the peer review without advising Engineer A
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
discovered in case: 15
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-02T19:52:16.328615+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
comment: State in which a client or third party instructs a reviewing professional to evaluate another professional's work without the knowledge or consent of that professional, creating obligations of transparency and professional courtesy.
subclass of: ConflictState
generated at time: 2026-06-02T19:52:16.328615+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Cross-Discipline Competence Constraint
type: Class
affected stakeholders: Clients
affected stakeholders: Engineer
affected stakeholders: Licensing board
affected stakeholders: Public
confidence: 0.8
constraint type: regulatory
flexibility: hard
mitigation strategies: Collaborate with a qualified engineer in the relevant discipline
mitigation strategies: Decline engagements outside the engineer's demonstrated area of competence
mitigation strategies: Obtain additional education and supervised experience before expanding practice scope
mitigation strategies: Refer clients to engineers with appropriate domain expertise
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: Engineer A, a chemical engineer with no facilities design and construction experience
violation impact: Engineer performs work outside competence boundaries, risking deficient designs, public safety harm, license discipline, and civil liability.
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:46:31.879113+00:00
first discovered in case: 121
match confidence: 0.82
match reasoning: The Scope of Practice (Constraint) from the canonical ontology directly addresses the boundaries of permissible professional practice established by ethics code provisions. This constraint is a specific instantiation of that concept applied to cross-discipline engineering practice. The Competence Constraint class also partially overlaps, but Scope of Practice more precisely captures the prohibition on offering services outside one's credentialed and experienced domain.
matched ontology class: Scope of Practice
matched ontology label: Scope of Practice (Constraint)
matches existing: true
source text: Engineer A, a chemical engineer with no facilities design and construction experience
comment: Regulatory and ethical constraint prohibiting a licensed professional engineer from offering or performing engineering services in a technical discipline or specialty area in which the engineer lacks the requisite education, training, and experience, regardless of licensure status in another discipline. The engineer's license in one field does not confer authority or competence to practice in materially different fields.
subclass of: InviolableConstraint
subclass of: RegulatoryConstraint
scope note: [Scope_of_Practice] Constraint established by ethics code provisions
generated at time: 2026-06-04T18:46:31.879113+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Cross-Discipline Practice State
type: Class
action constraints: Must not perform out-of-discipline design without demonstrated competence
action constraints: Must not rely on general licensure as authorization to practice in an unfamiliar discipline
activation conditions: Engineer with credentials in one discipline accepts an engagement requiring a different discipline
activation conditions: No subsequent training, education, or supervised experience in the target discipline is demonstrated
activation conditions: Work product in the target discipline is produced or offered
confidence: 0.85
obligation activation: Duty to practice only within areas of competency
obligation activation: Duty to retain or recommend specialists for out-of-discipline components
obligation activation: Obligation of other engineers to question and report competence concerns
persistence type: inertial
principle transformation: Transforms the general competence principle into a discipline-specific prohibition, and activates a parallel obligation on observing engineers to report competence concerns to the responsible party.
state category: competence
termination conditions: Engineer declines the out-of-discipline work
termination conditions: Engineer obtains substantive training and experience in the target discipline
termination conditions: Engineer retains a qualified specialist for the out-of-discipline component
text references: Engineer A, a chemical engineer, has no apparent substantive background or experience in the area of facilities design and construction
text references: Engineer B's degree and background was in chemical engineering. Engineer A had been unable to establish that Engineer B had any apparent subsequent training in foundation design
text references: all engineers are implored to exercise careful professional judgment and discretion and practice solely within his or her area(s) of competency
discovered in case: 121
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T18:43:40.738200+00:00
first discovered in case: 121
match confidence: 0.8
match reasoning: Outside Area of Competence is the closest canonical class and captures the core condition. The cross-discipline framing adds specificity about the licensed-in-one-discipline-practicing-in-another pattern, but the ethical condition is a variant of the existing class rather than a genuinely new concept. Medium confidence match.
matched ontology class: OutsideCompetence
matched ontology label: Outside Area of Competence
matches existing: true
source text: Engineer B's degree and background was in chemical engineering. Engineer A had been unable to establish that Engineer B had any apparent subsequent training in foundation design
comment: State in which a licensed professional engineer, credentialed in one technical discipline, undertakes to perform engineering services in a materially different discipline for which they lack the requisite education, training, and experience, creating conditions in which the professional's general license does not confer competence to practice in the new discipline and in which the work product carries elevated risk of harm.
subclass of: CompetenceState
scope note: [OutsideCompetence] Competence boundary preventing service provision
generated at time: 2026-06-04T18:43:40.738200+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Dam Design Engineer
type: Class
confidence: 0.88
role category: provider_client
text references: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness
text references: Engineer A's firm's impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:46:00.156208+00:00
first discovered in case: 85
match confidence: 0.82
match reasoning: Design Engineer exists in the previously extracted classes and covers the core obligation of producing original plans and specifications with professional accountability. Dam Design Engineer is a specialization by infrastructure type, warranting a medium-confidence match to that parent class.
matched ontology class: Design Engineer
matched ontology label: Design Engineer
matches existing: true
source text: Engineer A's firm's impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications
comment: A licensed professional engineering role in which the practitioner is retained to produce design drawings and specifications for a dam or similar hydraulic infrastructure project, bearing full professional accountability for the completeness, accuracy, and buildability of those documents regardless of schedule pressures or funding source.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [DesignEngineer] A professional engineering role responsible for creating original plans, specifications, and designs for a project, bearing primary accountability for the technical content of those documents.
generated at time: 2026-06-04T16:46:00.156208+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Deadline Pressure Disclosure Constraint
type: Class
affected stakeholders: Approving Engineer
affected stakeholders: Client
affected stakeholders: Contractor
affected stakeholders: Public
confidence: 0.82
constraint type: ethical
flexibility: hard
mitigation strategies: Notify the client in writing that the deadline cannot be met without compromising completeness
mitigation strategies: Request a schedule extension before the deadline passes
mitigation strategies: Submit a partial deliverable with explicit written notice of what is missing
text references: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
violation impact: Client proceeds on false assumption that the deliverable is complete, leading to downstream reliance on deficient documents by approving engineers, contractors, and public agencies.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:51:16.118939+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
comment: Ethical constraint requiring that an engineer who experiences time pressure sufficient to cause or contribute to the production of an incomplete or deficient work product must communicate that pressure and its effect on deliverable quality to the client before submitting the product, so that the client can decide whether to extend the deadline, accept the incomplete product with full knowledge, or seek alternative arrangements.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T16:51:16.118939+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Deadline Pressure Resistance Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: Professional engineering practice across infrastructure and design disciplines
enables actions: Communicate schedule conflicts to clients before submission
enables actions: Decline to submit incomplete work products under deadline pressure
enables actions: Identify when a delivery schedule is incompatible with professional standards
required for obligations: Deadline Pressure Resistance Obligation
required for obligations: Deliverable Completeness Disclosure Obligation
skill level: intermediate
text references: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:51:18.309339+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
comment: Capability to recognize when externally imposed deadlines are incompatible with producing complete and professionally adequate work products, and to communicate that incompatibility to the client rather than submitting deficient work under seal to meet the deadline.
subclass of: Capability
generated at time: 2026-06-04T16:51:18.309339+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Deadline Pressure Resistance Obligation
type: Class
confidence: 0.82
derived from principle: Professional Competence
enforcement level: mandatory
monitoring criteria: Evidence that the engineer communicated schedule constraints and their impact on deliverable completeness to the client before submitting sealed documents
nspe reference: II.2, II.5.a
obligation type: ethical
stakeholders affected: Approving agency
stakeholders affected: Client
stakeholders affected: Contractors
stakeholders affected: General public
text references: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness
violation consequences: Professional discipline; submission of sealed documents that do not meet professional standards; potential public safety risk
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:50:13.568162+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness
comment: Duty of an engineer to refrain from submitting incomplete, deficient, or unbuildable work products under seal merely because of schedule pressure or a contractually specified delivery date, and to instead communicate to the client that additional time or scope is required to produce a complete and professionally adequate deliverable.
subclass of: EthicalObligation
generated at time: 2026-06-04T16:50:13.568162+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Defense Industry Engineer
type: Class
confidence: 0.78
role category: employer_relationship
text references: an engineer employed by a large defense industry firm documented and reported to his employer excessive costs and time delays by sub-contractors
text references: the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports
discovered in case: 85
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T16:46:55.513806+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: an engineer employed by a large defense industry firm documented and reported to his employer excessive costs and time delays by sub-contractors
comment: A professional engineering role in which the practitioner is employed by a large defense industry firm and bears responsibility for documenting and reporting contractor performance issues such as excessive costs and schedule delays to the employing organization, with an ethical right but not a mandatory duty to escalate concerns to external authorities when the matter does not involve public health or safety.
subclass of: EmployerRelationshipRole
subclass of: EngineerRole
generated at time: 2026-06-04T16:46:55.513806+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Delegated Work Product Sealing State
type: Class
action constraints: Delegation of preparation does not transfer the sealing engineer's professional accountability
action constraints: Engineer may not seal documents over which they did not exercise genuine responsible charge
activation conditions: Documents are prepared by persons other than the sealing engineer
activation conditions: Engineer signs and seals the resulting documents
activation conditions: Sealing engineer claims direction and control over the preparers
confidence: 0.85
obligation activation: Duty to ensure subordinates are competent to perform assigned tasks
obligation activation: Duty to exercise substantive direction and control, not merely nominal supervision
obligation activation: Duty to verify that delegated work meets professional standards before sealing
persistence type: inertial
principle transformation: Transforms the principle of professional accountability into a concrete obligation to demonstrate active oversight when sealing documents prepared by others, distinguishing legitimate delegation from improper rubber-stamping.
state category: competence
termination conditions: Engineer withdraws from the project or responsible charge role
termination conditions: Sealing is completed and work is delivered
text references: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control
discovered in case: 120
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:05:02.078098+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control
comment: State in which a professional engineer signs and seals documents that were substantially prepared by subordinates or other personnel rather than by the engineer personally, where the engineer's authority to seal depends on having exercised genuine direction and control over the preparation process rather than merely reviewing a completed product.
subclass of: CompetenceState
generated at time: 2026-06-04T18:05:02.078098+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Deliverable Completeness Disclosure Obligation
type: Class
confidence: 0.88
derived from principle: Deliverable Completeness Disclosure Principle
enforcement level: mandatory
monitoring criteria: Documented disclosure of known deficiencies to client and approving authority prior to or concurrent with submission of sealed documents
nspe reference: II.2, II.5.a, III.2.b
obligation type: disclosure
stakeholders affected: Bidding contractors
stakeholders affected: Client
stakeholders affected: Federal approving agency
stakeholders affected: General public
text references: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness
text references: much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes
violation consequences: Professional discipline; potential liability for increased project costs; risk to public safety from reliance on deficient documents
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:50:13.568162+00:00
first discovered in case: 85
match confidence: 0.78
match reasoning: The concept is a variant of Complete Technical Reporting Obligation and Report Completeness Obligation, but those address omissions within a report rather than the duty to disclose that a deliverable itself is materially incomplete at the time of submission. The present obligation is sufficiently distinct to warrant a separate class focused on the completeness of the deliverable artifact rather than the completeness of findings within a report.
matched ontology class: Complete Options Advisory Obligation
matched ontology label: Complete Technical Reporting Obligation
matches existing: true
source text: much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are 'unbuildable' without major changes
comment: Duty of an engineer to disclose to the client, approving authorities, and other relying parties any known material incompleteness, deficiency, or unbuildable element in drawings, specifications, or other deliverables before or at the time of submission, rather than concealing such deficiencies and allowing the submission to proceed as if complete.
subclass of: DisclosureObligation
scope note: [CompleteOptionsAdvisoryObligation] Duty of an engineer advising a client on selection among multiple available options to present all materially relevant options within the approved or applicable set, rather than selectively presenting only a subset, so that the client can make a fully informed decision.
generated at time: 2026-06-04T16:50:13.568162+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Deliverable Completeness Disclosure Principle
type: Class
abstract nature: Open-textured obligation requiring engineers to weigh schedule and contractual pressures against the duty to deliver complete and adequate work, and to communicate honestly when those pressures result in deficient output.
confidence: 0.88
derived obligations: Disclose incompleteness of drawings or specifications to the client at the time of submission
derived obligations: Notify the approving authority of known deficiencies before or during the approval process
derived obligations: Refrain from submitting sealed documents that the engineer knows are materially deficient without contemporaneous disclosure
extensional examples: Engineer delivers specifications knowing they are unbuildable without major changes but does not flag this to any party
extensional examples: Engineer submits incomplete dam drawings on deadline without disclosing omissions to client or federal approving agency
operationalization: Requires engineers to either complete deliverables to the required standard before submission or, when submission of incomplete work is unavoidable, to explicitly disclose the nature and extent of deficiencies to all affected parties at the time of submission.
potential conflicts: Contractual deadline obligations
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Schedule pressure from client or employer
principle category: professional_virtue
text references: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
text references: While much of the information was missing from the drawings and specifications, Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs.
value basis: Professional trust and the integrity of the engineering deliverable depend on the recipient being able to rely on submitted work as complete and adequate, or on being informed when it is not.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:49:05.036482+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
comment: Professional integrity principle requiring engineers to disclose known deficiencies, omissions, or incompleteness in drawings, specifications, or other deliverables at the time of submission, rather than submitting deficient work product while concealing its inadequacy from the client, the approving authority, and other affected parties.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T16:49:05.036482+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Design-Build Consent Waiver Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Contracting Authority
affected stakeholders: Design Engineer
affected stakeholders: Peer Reviewer
confidence: 0.8
constraint type: legal
flexibility: hard
mitigation strategies: Accompany consent provisions with confidentiality protections and opportunity to respond
mitigation strategies: Ensure all parties are aware of peer review provisions before contracting
mitigation strategies: Include peer review consent provisions in design-build bid and contract documents
text references: Frequently that disclosure is accompanied by an agreement that the client will require the peer reviewer to keep the results of the peer review confidential or, at the very least, the original designer will be provided with an opportunity to explain (and defend) the design decisions
text references: the possibility that the client will obtain a peer review is specified in design-build bid or contract documents to the effect that any party who bids or contracts with the client has, by participating, consented to the peer review
violation impact: Failure to recognize pre-established consent may lead to unnecessary procedural disputes over notification and cooperation obligations that were already resolved by contract.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:50.100159+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: the possibility that the client will obtain a peer review is specified in design-build bid or contract documents to the effect that any party who bids or contracts with the client has, by participating, consented to the peer review
comment: Constraint arising in design-build procurement contexts where bid or contract documents specify that any party who participates has, by participating, consented to peer review. This pre-established consent mechanism alters the default notification and consent requirements by incorporating them into the contractual framework at the outset.
subclass of: InviolableConstraint
subclass of: LegalConstraint
generated at time: 2026-06-02T20:00:50.100159+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Detailed Review Sealing Capability
type: Class
capability category: domain_specific
confidence: 0.88
domain specificity: Professional engineering document review and sealing practice
enables actions: Assess whether a review is adequate to support responsible charge
enables actions: Check and review engineering documents in sufficient detail before sealing
enables actions: Determine when a review is insufficient to justify sealing
enables actions: Identify deficiencies in documents prepared by subordinates
required for obligations: Detailed Review Sealing Obligation
required for obligations: Full Responsibility Assumption Obligation
required for obligations: Responsible Charge Seal Obligation
skill level: advanced
text references: The key requirement is that an engineer possesses sufficient competence, assumes full responsibility for the work product and carefully directs, controls and reviews the material prepared under the engineer's responsible charge.
text references: We concluded, based upon a review of authoritative sources that the terms 'direction' and 'control' have a meaning which, when combined, would suggest that an engineer would be required to perform all tasks related to the preparation of the drawings, plans, and specifications in order for the engineer to ethically affix his seal.
text references: Were we to decide BER Case 86-2 today, we would conclude that the it was not unethical for the engineer in that instance to seal plans that were not personally prepared by him as long as those plans were checked and reviewed by the engineer in some detail.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:12:59.240485+00:00
first discovered in case: 120
match confidence: 0.88
match reasoning: Responsible Charge Verification Capability is defined as the capability to conduct a review of professional work products sufficiently thorough to support the exercise of responsible charge, including the ability to assess whether one's review is adequate before applying a professional seal. This is precisely the capability described in the case text regarding the obligation to check and review documents in some detail before sealing. The match is high confidence.
matched ontology class: Responsible Charge Verification Capability
matched ontology label: Responsible Charge Verification Capability
matches existing: true
source text: We concluded, based upon a review of authoritative sources that the terms 'direction' and 'control' have a meaning which, when combined, would suggest that an engineer would be required to perform all tasks related to the preparation of the drawings, plans, and specifications in order for the engineer to ethically affix his seal.
comment: Capability of a licensed professional engineer to conduct a sufficiently detailed check and review of engineering documents, plans, or specifications prepared by others before affixing a professional seal, including the ability to assess whether the review performed is adequate to support responsible charge and to refrain from sealing documents that have not been reviewed in sufficient detail.
subclass of: Capability
scope note: [ResponsibleChargeVerificationCapability] Capability to conduct a review of professional work products that is sufficiently thorough to support the exercise of responsible charge, including the ability to assess whether one's review is adequate before applying a professional seal.
generated at time: 2026-06-04T18:12:59.240485+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Detailed Review Sealing Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.85
constraint type: procedural
flexibility: soft
mitigation strategies: Allocate sufficient time for detailed review proportionate to document complexity
mitigation strategies: Decline to seal documents when adequate review time is unavailable
mitigation strategies: Establish a documented review protocol for all documents before sealing
text references: In deciding that it was unethical for him to seal plans that had not been prepared by him, or which he had not checked and reviewed in detail, the Board read the language in Section II.2.b. quite literally.
text references: The key requirement is that an engineer possesses sufficient competence, assumes full responsibility for the work product and carefully directs, controls and reviews the material prepared under the engineer's responsible charge.
text references: We would conclude that it was not unethical for the engineer in that instance to seal plans that were not personally prepared by him as long as those plans were checked and reviewed by the engineer in some detail.
violation impact: Sealing without detailed review means the engineer cannot take responsible charge, exposing the public to undetected errors and the engineer to disciplinary action.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:13:02.665367+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: In deciding that it was unethical for him to seal plans that had not been prepared by him, or which he had not checked and reviewed in detail, the Board read the language in Section II.2.b. quite literally.
comment: Procedural and ethical constraint requiring that a professional engineer who seals engineering documents prepared by subordinates or technological systems must check and review those documents in some detail before affixing the seal, so that the seal reflects genuine professional oversight rather than nominal endorsement.
subclass of: DefeasibleConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-04T18:13:02.665367+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Detailed Review Sealing Obligation
type: Class
confidence: 0.9
derived from principle: Responsible Charge Integrity Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer reviewed the documents in sufficient detail to identify material errors or deficiencies before sealing
nspe reference: II.2.b
obligation type: ethical
stakeholders affected: Clients
stakeholders affected: General public
stakeholders affected: Regulatory bodies
stakeholders affected: Subordinate engineers
text references: The key requirement is that an engineer possesses sufficient competence, assumes full responsibility for the work product and carefully directs, controls and reviews the material prepared under the engineer's responsible charge.
text references: We would conclude that it was not unethical for the engineer in that instance to seal plans that were not personally prepared by him as long as those plans were checked and reviewed by the engineer in some detail.
text references: engineers must not affix their signatures to any plans or documents dealing with subject matter which they lack competence, nor to any plan or document not prepared under their direction and control.
violation consequences: Ethical violation under NSPE II.2.b; professional liability for deficiencies in sealed documents; potential license discipline
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:11:22.208486+00:00
first discovered in case: 120
match confidence: 0.87
match reasoning: This obligation is a close match to the existing Responsible Charge Seal Obligation, which requires a licensed engineer to apply their seal only to work products they have personally reviewed with sufficient depth and competence. The present obligation adds the clarification that personal preparation is not required but detailed review is, which is a refinement of the same core duty rather than a distinct new concept.
matched ontology class: Responsible Charge Seal Obligation
matched ontology label: Responsible Charge Seal Obligation
matches existing: true
source text: We would conclude that it was not unethical for the engineer in that instance to seal plans that were not personally prepared by him as long as those plans were checked and reviewed by the engineer in some detail.
comment: Duty of a licensed engineer to check and review in some detail any engineering documents, plans, or specifications prepared by others before affixing the engineer's seal, so that the seal reflects genuine professional oversight rather than mere administrative approval, even when the engineer did not personally prepare the documents.
subclass of: EthicalObligation
scope note: [ResponsibleChargeSealObligation] Duty of a licensed engineer exercising responsible charge to apply their professional seal only to work products they have personally reviewed with sufficient depth and competence to take genuine professional responsibility for the content, and not to seal work generated by tools or processes they do not adequately understand or have not adequately verified.
generated at time: 2026-06-04T18:11:22.208486+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Developer Client
type: Class
confidence: 0.82
role category: provider_client
text references: Engineer A was a principal in an environmental engineering firm and was requested by a developer client to prepare an analysis of a piece of property adjacent to a wetlands area for potential development as a residential condominium
text references: XYZ Corporation was advised by a State Pollution Control Authority
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:07.116406+00:00
first discovered in case: 8
match confidence: 0.8
match reasoning: Developer Client is a specialization of Client Role representing a private development entity commissioning engineering services. It is closely related to the previously extracted Private Development Client but is generalized here to cover developer clients in environmental and land-use contexts more broadly.
matched ontology class: ClientRole
matched ontology label: Client Role
matches existing: true
source text: Engineer A was a principal in an environmental engineering firm and was requested by a developer client to prepare an analysis of a piece of property adjacent to a wetlands area for potential development as a residential condominium
comment: A private developer or development entity that commissions professional engineering or environmental analysis services for a proposed development project, acting as the primary client and decision-maker but lacking professional engineering licensure, and whose development interests may conflict with the engineer's obligations to disclose environmental risks to public authorities.
subclass of: ClientRole
subclass of: ProviderClientRole
scope note: [ClientRole] Party that commissions the project work. This is the occupational archetype. The duty relationship is carried separately by :ProviderClientRole.
generated at time: 2026-06-04T09:59:07.116406+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Diploma Mill Equivalence Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Licensing Board
affected stakeholders: Profession
affected stakeholders: Public
confidence: 0.82
constraint type: ethical
flexibility: hard
mitigation strategies: Evaluate any credentialing or competence-building mechanism against the standard of formal engineering education and supervised practice
mitigation strategies: Reject commercial offerings that frame professional experience requirements as obstacles rather than prerequisites
mitigation strategies: Seek peer or board review of proposed competence claims before offering services in a new domain
text references: The Board considers such activities completely contrary to the basic ethical principles established in the Code of Ethics.
text references: The direct mail product described under the facts is not unlike mail order certifications offered by so called 'diploma mills' whereby individuals 'self certify' their competency based upon a perfunctory review process that rarely involves comprehensive study, examination, or practice.
violation impact: Engineer acquires and represents a credential or competence claim that lacks substantive basis, deceiving clients and the public and degrading professional standards.
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:50:05.033406+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: The direct mail product described under the facts is not unlike mail order certifications offered by so called 'diploma mills' whereby individuals 'self certify' their competency based upon a perfunctory review process that rarely involves comprehensive study, examination, or practice.
comment: Ethical constraint establishing that a licensed engineer may not rely on perfunctory, non-rigorous, or commercially motivated credentialing mechanisms as a basis for representing professional competence, because such mechanisms are functionally equivalent to diploma mill certifications and do not satisfy the profession's standards for demonstrated knowledge and experience.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T18:50:05.033406+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Disputed Driving Records State
type: Class
action constraints: Professional must not dismiss records without stated technical justification
action constraints: Professional must not issue conclusions as definitive when they rest on unresolved record disputes
activation conditions: Construction or installation records exist
activation conditions: One or more parties contest the accuracy or reliability of those records
activation conditions: Professional conclusions depend on acceptance or rejection of the records
confidence: 0.82
obligation activation: Duty to disclose that records are disputed when relying on or dismissing them
obligation activation: Duty to present the dispute as a material uncertainty in professional conclusions
obligation activation: Duty to seek independent verification of disputed records
persistence type: inertial
principle transformation: Transforms general objectivity principles into specific obligations to disclose record disputes and seek verification before issuing conclusions that depend on the acceptance or rejection of contested records.
state category: information
termination conditions: Dispute is resolved by agreed findings
termination conditions: Engagement concludes
termination conditions: Records are independently verified or refuted
text references: Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records
text references: The driving records look suspicious.
text references: We just did not believe the driving records
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:51.674939+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: We just did not believe the driving records
comment: State in which the accuracy or reliability of construction or installation records is contested between parties, creating a condition in which professional conclusions that rely on or dismiss those records carry heightened obligations of transparency, disclosure of the dispute, and independent verification before issuing findings.
subclass of: InformationState
generated at time: 2026-06-04T14:26:51.674939+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Drinking Water Quality Standard Resource
type: Class
authority source: U.S. Environmental Protection Agency and state drinking water regulatory agencies
confidence: 0.88
extensional function: Establishes binding minimum safety thresholds for public drinking water that engineers must satisfy when designing or recommending changes to water supply systems, grounding the professional duty to protect public health.
resource category: legal_resource
text references: old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards
usage context: Corrosion control design
usage context: Public health protection in water engineering
usage context: Water supply source change evaluation
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T11:17:15.547667+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards
comment: Federal or state regulations and technical standards specifying maximum contaminant levels and treatment requirements for public drinking water supplies, including lead and copper rules governing corrosion control in distribution systems to prevent leaching from service pipes.
subclass of: LegalResource
generated at time: 2026-06-05T11:17:15.547667+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Drinking Water Safety Obligation
type: Class
confidence: 0.85
derived from principle: Public Welfare Paramountcy Principle
enforcement level: mandatory
monitoring criteria: Documented verification that corrosion control and other required improvements are in place and effective before the water source change is implemented
nspe reference: I.1, II.1.a
obligation type: safety
stakeholders affected: General public
stakeholders affected: Regulatory bodies
stakeholders affected: Water consumers
text references: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards.
violation consequences: Public health harm from lead exposure; professional discipline; regulatory sanctions; potential legal liability
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:23:42.907966+00:00
first discovered in case: 76
match confidence: 0.8
match reasoning: This is a domain-specific instantiation of the existing Safety Obligation class, applied to public water supply infrastructure. The core duty to hold paramount the safety, health, and welfare of the public is already captured by the Safety Obligation and the broader Public Welfare Paramountcy Principle. No genuinely new class is required.
matched ontology class: SafetyObligation
matched ontology label: Safety Obligation
matches existing: true
source text: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards.
comment: Duty of an engineer responsible for or advising on a public water supply system to ensure that any change to the water source or treatment process does not result in drinking water that fails to meet applicable health-based standards, including standards for lead and other contaminants leached from distribution infrastructure, before the change is implemented.
subclass of: SafetyObligation
scope note: [SafetyObligation] Duty to hold paramount the safety, health, and welfare of the public (NSPE I.1)
generated at time: 2026-06-05T11:23:42.907966+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Dual Role Conflict State
type: Class
action constraints: Professional must not allow administrative loyalty to suppress required safety disclosures
action constraints: Professional must not certify compliance with standards that have not been met
activation conditions: Organization makes a decision contrary to the professional's technical recommendation
activation conditions: Professional holds both an administrative leadership role and a technical advisory role within the same organization
activation conditions: Professional must implement or oversee a decision they recommended against
confidence: 0.82
obligation activation: Duty to avoid using administrative authority to suppress technical dissent
obligation activation: Duty to clearly communicate technical objections through appropriate channels
obligation activation: Duty to consider whether continued dual role is ethically sustainable
persistence type: inertial
principle transformation: Transforms the general conflict of interest principle into a concrete obligation to manage the structural tension between organizational loyalty and independent professional judgment, with public safety as the paramount consideration.
state category: conflict
termination conditions: Organization reverses its decision
termination conditions: Professional resigns one of the roles
termination conditions: Role separation is established
text references: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed
text references: Engineer A is a professional engineer who serves as the superintendent and chief engineer for the Metropolitan Water Commission (MWC).
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T11:17:42.957900+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Engineer A is a professional engineer who serves as the superintendent and chief engineer for the Metropolitan Water Commission (MWC).
comment: State in which a professional simultaneously holds an internal administrative or managerial role within an organization and an independent technical advisory role for that same organization, creating a structural tension between the duty to carry out organizational decisions and the duty to provide objective professional advice that may conflict with those decisions.
subclass of: ConflictState
generated at time: 2026-06-05T11:17:42.957900+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Dual Role Safety Constraint
type: Class
affected stakeholders: Client Organization
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.78
constraint type: ethical
flexibility: hard
mitigation strategies: Document professional safety recommendations independently of administrative decisions
mitigation strategies: Escalate safety concerns through engineering channels even when administrative channels are blocked
mitigation strategies: Maintain clear separation between administrative and engineering functions
text references: Engineer A is a professional engineer who serves as the superintendent and chief engineer for the Metropolitan Water Commission (MWC)
violation impact: Suppression of safety findings, public health harm, professional discipline, loss of licensure
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:25:13.430491+00:00
first discovered in case: 76
match confidence: 0.72
match reasoning: The dual role situation creates a structural conflict of interest between Engineer A's administrative loyalty to the MWC and independent professional engineering judgment. The existing Conflict of Interest Avoidance constraint captures the core concept, but the specific manifestation involving simultaneous internal administrative and engineering roles is a variant that adds the dimension of role-based suppression of safety judgment. Matching as a variant at medium confidence.
matched ontology class: Conflict of Interest Avoidance
matched ontology label: Conflict of Interest Avoidance (Constraint)
matches existing: true
source text: Engineer A is a professional engineer who serves as the superintendent and chief engineer for the Metropolitan Water Commission (MWC)
comment: Ethical and professional constraint arising when an engineer simultaneously holds an internal administrative or managerial role within an organization and a professional engineering role advising that same organization, requiring the engineer to ensure that the administrative role does not suppress or subordinate the independent professional safety judgment the engineering role demands. The engineer must act on safety findings regardless of organizational pressure arising from the dual role.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [Conflict_of_Interest_Avoidance] Constraint established by ethics code provisions
generated at time: 2026-06-05T11:25:13.430491+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Engineer Contractor
type: Class
confidence: 0.82
role category: provider_client
text references: As an engineer and a contractor presumably, Engineer C had the necessary background and experience to carefully evaluate the engineering drawings
text references: Engineer C had no one to fault but himself for the problems Engineer C encountered in attempting to build the project
text references: Engineer C's actions in bidding on an unbuildable contract is also very troubling
discovered in case: 85
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T16:46:55.513806+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer C's actions in bidding on an unbuildable contract is also very troubling
comment: A licensed professional engineering role in which the practitioner is also the owner or principal of a construction firm, bids on and is awarded a construction contract, and bears professional obligations both as an engineer to evaluate the adequacy of design documents before bidding and as a contractor to perform the work, such that the practitioner cannot disclaim engineering judgment when assessing the completeness of drawings and specifications.
subclass of: ContractorRole
subclass of: ProviderClientRole
generated at time: 2026-06-04T16:46:55.513806+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Engineer Qualification and Experience Resource
type: Class
authority source: Engineering firms and licensed professionals
confidence: 0.8
extensional function: Provides evidentiary grounding for claims of competence and grounds the professional obligation to represent qualifications honestly and completely.
resource category: reference_material
text references: Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
usage context: Competence disclosure
usage context: Proposal submissions
usage context: Service recommendations
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:40:56.485170+00:00
first discovered in case: 14
match confidence: 0.8
match reasoning: This type of qualification and experience documentation fits within the existing Reference Material class as supporting documentation for professional practice. No more specific existing class covers firm experience summaries and project references.
matched ontology class: ReferenceMaterial
matched ontology label: Reference Material
matches existing: true
source text: Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
comment: Documentation of a professional engineer's or firm's qualifications, past project experience, and client references relevant to a specific service type, submitted to support a recommendation or proposal.
subclass of: ReferenceMaterial
scope note: [ReferenceMaterial] Supporting documentation for professional practice
generated at time: 2026-06-04T08:40:56.485170+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Engineering Competence Guidance Resource
type: Class
authority source: Professional engineering societies and licensing boards
confidence: 0.88
extensional function: Grounds the duty to practice within competence by providing authoritative statements of what constitutes adequate qualification for engineering services, bridging the abstract principle of competence to concrete practice decisions.
resource category: professional_code
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services
text references: Engineer A, a chemical engineer with no facilities design and construction experience
text references: specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
usage context: Assessing the adequacy of software or tool-based substitutes for professional experience
usage context: Determining ethical obligations when solicited to expand practice beyond current competence
usage context: Evaluating whether an engineer is qualified to offer a new category of services
discovered in case: 121
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:42:45.862955+00:00
first discovered in case: 121
match confidence: 0.75
match reasoning: The CADD Competency Guidance Resource class addresses professional guidance on the requisite background, education, and training engineers must have when using technical tools, and the distinction between using tools as aids versus substitutes for professional judgment. This case involves an analogous situation where a CD-ROM software product is being used as a substitute for genuine facilities design experience. The concept is a close variant but broader than CADD specifically, covering any tool-based competence substitution. A medium confidence match is appropriate.
matched ontology class: CADD Competency Guidance Resource
matched ontology label: CADD Competency Guidance Resource
matches existing: true
source text: Engineer A, a chemical engineer with no facilities design and construction experience
comment: Professional guidance addressing the requirement that engineers practice only within their areas of competence, including the obligation to undertake services only when qualified by education or experience, and the prohibition against using tools or products as substitutes for genuine professional competence.
subclass of: ProfessionalCode
scope note: [CADDCompetencyGuidanceResource] Professional guidance addressing the requisite background, education, training, and limitations engineers must understand when using Computer Aided Drafting and Design systems in professional practice, including the distinction between using such tools as aids versus substitutes for professional judgment.
generated at time: 2026-06-04T18:42:45.862955+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Engineering Design Deliverable Standard Resource
type: Class
authority source: Professional engineering societies and standard contracting practice
confidence: 0.8
extensional function: Establishes the minimum professional standard for what constitutes an acceptable set of engineering drawings and specifications, grounding the duty to deliver complete and buildable documents.
resource category: technical_standard
text references: Engineer A generally agrees with Hi-Lo's characterization
text references: certain parts of the project are unbuildable without major changes
text references: much of the design detail is lacking in the drawings and specifications
usage context: Design contract performance
usage context: Pre-construction review
usage context: Professional accountability for deliverable quality
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:45:36.674624+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: much of the design detail is lacking in the drawings and specifications
comment: Professional norms and contractual expectations governing the completeness, accuracy, and adequacy of engineering drawings and specifications delivered under a design contract, including the obligation to disclose known deficiencies before submission.
subclass of: TechnicalStandard
generated at time: 2026-06-04T16:45:36.674624+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Engineering Seal Regulation Resource
type: Class
authority source: State professional engineering licensing boards and state legislatures
confidence: 0.82
extensional function: Establishes the legal threshold for professional accountability when an engineer seals a document, grounding the duty of responsible charge in enforceable state law.
resource category: legal_resource
text references: submitted the draft report to Client W for review, including language to clearly identify that the supplied report was a draft, but applied their seal consistent with state law.
usage context: Determining conditions for responsible charge
usage context: Sealing draft reports
usage context: Sealing engineering design documents
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T13:59:19.637051+00:00
first discovered in case: 7
match confidence: 0.82
match reasoning: State laws governing professional engineering seals are legal frameworks constraining professional practice, matching the Legal Resource class in the ontology. No more specific existing class covers engineering seal statutes.
matched ontology class: LegalResource
matched ontology label: Legal Resource
matches existing: true
source text: submitted the draft report to Client W for review, including language to clearly identify that the supplied report was a draft, but applied their seal consistent with state law.
comment: State law or regulatory provision governing the conditions under which a licensed professional engineer may apply their professional seal to engineering documents, including requirements for responsible charge, review, and accuracy of sealed work.
subclass of: LegalResource
scope note: [LegalResource] Legal framework constraining professional practice
generated at time: 2026-06-03T13:59:19.637051+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Environmental Compliance Reporting Obligation
type: Class
confidence: 0.86
derived from principle: Environmental Law Compliance Principle
enforcement level: mandatory
monitoring criteria: Documented report to the appropriate federal or state environmental authority describing the observed violation, made within a reasonable time after discovery.
nspe reference: I.1, II.1.a
obligation type: reporting
stakeholders affected: Adjacent communities
stakeholders affected: General public
stakeholders affected: Regulatory authorities
stakeholders affected: Wetland ecosystems
text references: Engineer A is an environmental engineer.
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
text references: he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
violation consequences: Failure to report a known, substantial environmental law violation by a former client may result in professional discipline and ongoing harm to protected environmental resources.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:30:01.042237+00:00
first discovered in case: 86
match confidence: 0.8
match reasoning: The existing Post-Termination Environmental Risk Reporting Obligation is the closest match, covering the duty to report environmental risks to a pollution-control authority after termination of the client relationship. This class adds the dimension of specialized environmental engineering knowledge as the basis for recognizing and reporting the violation, but the core reporting duty is the same. Treated as a variant of the existing class.
matched ontology class: PostTerminationEnvironmentalRiskReportingObligation
matched ontology label: Post-Termination Environmental Risk Reporting Obligation
matches existing: true
source text: Engineer A is an environmental engineer.
comment: Duty of an engineer with specialized knowledge of environmental law and regulation who discovers a substantial violation of those laws to report the violation to the appropriate federal or state regulatory authority, drawing on that specialized knowledge to recognize the severity and legal significance of the observed conduct.
subclass of: ReportingObligation
scope note: [PostTermEnvRiskReportingObligation] Duty of an engineer to report environmental risks to a pollution-control authority after termination of the client relationship when the risk rises to a public-safety concern (NSPE Code §I.1, §II.1.a, §II.1.c). Derived from the paramount public-welfare principle.
generated at time: 2026-06-04T17:30:01.042237+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Environmental Consulting Engineer
type: Class
confidence: 0.85
role category: provider_client
text references: Engineer A was a principal in an environmental engineering firm and was requested by a developer client to prepare an analysis of a piece of property adjacent to a wetlands area
text references: Engineer Doe to perform consulting engineering services and submit a detailed report
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:07.116406+00:00
first discovered in case: 8
match confidence: 0.75
match reasoning: Environmental Consulting Engineer is a specialization of Engineer Role with a specific focus on environmental analysis and reporting obligations. The existing Environmental Engineer class from prior extractions is close but that class emphasizes contaminant analysis and groundwater monitoring infrastructure design, whereas this role centers on environmental impact analysis and disclosure obligations in a consulting context. Matching to the parent Engineer Role at medium confidence.
matched ontology class: EngineerRole
matched ontology label: Engineer Role
matches existing: true
source text: Engineer Doe to perform consulting engineering services and submit a detailed report
comment: A professional engineering role in which the practitioner is engaged by a client to perform environmental analysis, prepare technical reports on environmental conditions or risks, and provide findings to clients and public authorities, bearing professional obligations of objectivity, completeness, and truthful disclosure of all relevant facts in written reports.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [EngineerRole] A professional role involving engineering practice and responsibilities. Occupational archetype head for all engineer specializations and extracted engineer-role leaves.
generated at time: 2026-06-04T09:59:07.116406+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Environmental Discharge Consultant
type: Class
confidence: 0.87
role category: provider_client
text references: Engineer Doe had an obligation to report his findings to the Pollution Control Authority
text references: Engineer Doe verbally reported to XYZ that their discharge will lower the water quality in the receiving body of water below standards
text references: they hired Engineer Doe to perform consulting engineering services and submit a detailed report
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T02:17:07.048701+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: they hired Engineer Doe to perform consulting engineering services and submit a detailed report
comment: A licensed professional engineering role in which the practitioner is retained by a manufacturing or industrial client to perform consulting engineering services related to environmental discharge, prepare detailed technical reports on discharge impacts relative to water quality standards, and bear professional obligations to report findings truthfully to regulatory authorities even when the client instructs suppression of the written report.
subclass of: ConsultantRole
subclass of: ProviderClientRole
generated at time: 2026-06-05T02:17:07.048701+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Environmental Law Compliance Principle
type: Class
abstract nature: Open-textured value requiring interpretation of what constitutes a reportable violation, what threshold of severity triggers disclosure obligations, and how the engineer's prior service relationship affects those obligations.
confidence: 0.82
derived obligations: Assess whether observed conduct constitutes a violation of federal or state environmental law
derived obligations: Disclose the violation to appropriate regulatory authorities when public welfare requires it
derived obligations: Evaluate whether the violation poses ongoing or irreversible harm to protected resources
derived obligations: Refrain from assisting the client in concealing or perpetuating the violation
extensional examples: Engineer discovers unpermitted wetland fill by former client and must determine disclosure obligations
extensional examples: Environmental engineer observes illegal discharge by client during site visit for unrelated services
operationalization: Requires environmental engineers to assess whether observed client conduct violates applicable law, evaluate the severity and ongoing nature of the violation, and determine whether disclosure to regulatory authorities is required to protect public welfare.
potential conflicts: Client confidentiality obligations arising from the prior service relationship
potential conflicts: Confidentiality Principle
potential conflicts: Faithful Agent Duty Principle
principle category: domain_specific
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations
text references: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
value basis: Environmental laws protecting wetlands and public resources exist to safeguard ecosystems and the public interest; engineers with specialized knowledge who observe violations are positioned to prevent ongoing harm.
discovered in case: 8
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:28:58.159954+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
comment: Domain-specific principle requiring engineers engaged in environmental practice to recognize, and take appropriate action upon, client conduct that constitutes a substantial violation of federal or state environmental laws and regulations, even when that conduct is discovered incidentally after the engineer's contracted services have concluded.
subclass of: DomainSpecificPrinciple
scope note: [Case 8] Domain-specific principle requiring engineers engaged in environmental practice to recognize, and take appropriate action upon, client conduct that constitutes a substantial violation of applicable environmental laws and regulations, even when the client resists compliance or defers remediation.
generated at time: 2026-06-04T17:28:58.159954+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Environmental Risk Quantification Obligation
type: Class
confidence: 0.82
derived from principle: Environmental Stewardship Principle
enforcement level: prima_facie
monitoring criteria: Documented evidence that the engineer completed or documented the status of risk quantification work before suspending the engagement, or communicated the unquantified risk with appropriate caveats.
nspe reference: I.1, II.1.a, II.2.a
obligation type: safety
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: But before Engineer L can quantify the increased risk, Client X encounters unexpected financial setbacks and requests that Engineer L suspend work identified in the original contract.
text references: Part of Engineer L's scope of work for Client X includes ensuring that stormwater from the new development will not impact this primary drinking water source for the community.
violation consequences: Failure to quantify identified risks before suspension leaves the client and public without the information needed to make protective decisions, potentially allowing preventable harm to occur.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:02:21.757544+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: But before Engineer L can quantify the increased risk, Client X encounters unexpected financial setbacks and requests that Engineer L suspend work identified in the original contract.
comment: Duty of an engineer whose scope of work includes environmental protection to conduct sufficient analysis to quantify or adequately characterize identified environmental risks before suspending or concluding work, so that the client and relevant authorities have actionable information about the nature and magnitude of the risk.
subclass of: SafetyObligation
generated at time: 2026-06-04T10:02:21.757544+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Environmental Violation Reporting Constraint
type: Class
affected stakeholders: Adjacent Property Owners
affected stakeholders: Engineer
affected stakeholders: Environmental Resources
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.85
constraint type: regulatory
flexibility: hard
mitigation strategies: Act promptly given the ongoing nature of environmental harm from unpermitted fill
mitigation strategies: Document the observed violation with sufficient specificity to enable regulatory response
mitigation strategies: Report the violation to the appropriate federal agency such as the Army Corps of Engineers and the relevant state environmental agency
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
text references: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
violation impact: Failure to report allows ongoing destruction of protected environmental resources, exposes the engineer to professional discipline, and violates the paramount duty to protect public welfare.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:30:49.666256+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
comment: Regulatory and ethical constraint requiring an engineer with specialized knowledge of environmental law and regulation who observes or discovers a confirmed violation of federal or state environmental statutes to report that violation to the appropriate regulatory authority. The engineer's specialized competence creates a heightened duty to act because the engineer can recognize the significance of the violation and the harm it causes to protected resources.
subclass of: InviolableConstraint
subclass of: RegulatoryConstraint
generated at time: 2026-06-04T17:30:49.666256+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Equipment Failure Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Opposing parties
affected stakeholders: Retained engineer
affected stakeholders: Tribunal
confidence: 0.9
constraint type: procedural
flexibility: hard
mitigation strategies: Document all equipment failures contemporaneously during testing
mitigation strategies: Include equipment failure disclosures in the body of the report
mitigation strategies: Qualify conclusions that depend on data collected with failed equipment
text references: Additionally, Engineer B did not report that the dynamic test equipment had failed.
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test.
violation impact: Misleading report, invalid conclusions, professional discipline, unjust dispute outcomes
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology addresses the specific requirement to disclose equipment failures in a technical report. This is a distinct procedural constraint not captured by the broader scope limitation or contradictory evidence classes.
matches existing: false
source text: Additionally, Engineer B did not report that the dynamic test equipment had failed.
comment: Requirement that an engineer preparing a technical report disclose any equipment failures or malfunctions that occurred during testing or data collection and that could affect the validity or interpretation of the reported results.
subclass of: InviolableConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Error Acknowledgment Cooperation Obligation
type: Class
confidence: 0.9
derived from principle: Professional Accountability
enforcement level: mandatory
monitoring criteria: Evidence that the engineer provided access to design documents, responded to reviewer inquiries, and did not obstruct the review process
nspe reference: I.1
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Peer review engineer
stakeholders affected: Public
text references: Engineers must take responsibility for their actions, must acknowledge their errors, must act in the best interests of their clients, and must at all times hold paramount the health, welfare, and safety of the public.
text references: The known design defects in the first tower simply makes each of those requirements more urgent.
text references: Under the facts, the Board concludes that it would be unethical for Engineer A to fail to cooperate.
violation consequences: Finding of unethical conduct; potential disciplinary action; risk to public safety from uncorrected errors
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:59:48.608792+00:00
first discovered in case: 15
match confidence: 0.82
match reasoning: This obligation is a contextual extension of the Error Acknowledgment class, adding the cooperation-with-corrective-process dimension that the base class does not fully capture. It is a medium-confidence match to the existing class, with the cooperation element as the distinguishing qualifier.
matched ontology class: ErrorAcknowledgment
matched ontology label: Error Acknowledgment
matches existing: true
source text: Engineers must take responsibility for their actions, must acknowledge their errors, must act in the best interests of their clients, and must at all times hold paramount the health, welfare, and safety of the public.
comment: Duty of an engineer to acknowledge errors in their prior work and to cooperate with corrective processes, including peer review, rather than obstructing those processes to protect personal or reputational interests.
subclass of: EthicalObligation
generated at time: 2026-06-02T19:59:48.608792+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Expert Neutrality Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Opposing parties
affected stakeholders: Public
affected stakeholders: Retained expert engineer
affected stakeholders: Tribunal
confidence: 0.91
constraint type: ethical
flexibility: hard
mitigation strategies: Apply analytical methods consistently regardless of outcome
mitigation strategies: Decline engagement if client demands biased conclusions
mitigation strategies: Disclose all material evidence including evidence adverse to the retaining client
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal.
text references: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
text references: We just did not believe the driving records.
violation impact: Misleading tribunal, professional discipline, loss of credibility, unjust dispute outcome
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology captures the hard ethical prohibition on expert bias. The obligation-side Expert Witness Neutrality Obligation is a duty; this is the inviolable boundary on permissible expert conduct.
matches existing: false
source text: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
comment: Prohibition on an engineer retained as an expert witness or technical investigator orienting findings toward a client's litigation position, requiring objective presentation of all material evidence regardless of adversarial context.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Expert Witness Neutrality Obligation
type: Class
confidence: 0.94
derived from principle: Litigation Neutrality Principle
enforcement level: mandatory
monitoring criteria: Report and testimony present all material evidence, including evidence unfavorable to the retaining party, and apply methods consistently
nspe reference: III.2
obligation type: ethical
stakeholders affected: Court or mediating body
stakeholders affected: General public
stakeholders affected: Opposing party
stakeholders affected: Professional licensing board
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
text references: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
violation consequences: Professional discipline; testimony may be excluded or discredited; potential sanctions by court
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:31:15.630641+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing obligation class in the ontology corresponds to this duty. This is a new class.
matches existing: false
source text: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
comment: Duty of an engineer retained as an expert witness or technical investigator in litigation to present findings objectively, apply analytical methods consistently, and not omit material evidence that contradicts the retaining party's position.
subclass of: EthicalObligation
generated at time: 2026-06-04T14:31:15.630641+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Expert Witness Report Resource
type: Class
authority source: Retained professional engineers acting as expert witnesses
confidence: 0.83
extensional function: Provides authoritative technical findings and professional opinions that ground factual determinations in disputes, establishing the evidentiary basis on which legal and ethical judgments are made.
resource category: expert_interpretation
text references: Additionally, Engineer B did not report that the dynamic test equipment had failed.
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal
text references: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
usage context: Litigation support
usage context: Mediation proceedings
usage context: Technical dispute resolution
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:23.227248+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
comment: A formal written report prepared by a retained expert witness for use in litigation, mediation, or dispute resolution, presenting technical findings, opinions, and conclusions on matters within the expert's professional competence. Such reports carry professional accountability obligations and serve as primary evidentiary knowledge sources in legal and quasi-legal proceedings.
subclass of: ExpertInterpretation
generated at time: 2026-06-04T14:26:23.227248+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Expertise-Calibrated Disclosure Capability
type: Class
capability category: reasoning
confidence: 0.87
domain specificity: Professional engineering contexts where the engineer's level of domain expertise in the relevant technical area determines the appropriate threshold and form of disclosure
enables actions: Assess one's own level of domain expertise relative to the technical issue at hand
enables actions: Calibrate disclosure urgency and formality to the strength of the evidentiary basis
enables actions: Determine whether expertise is sufficient to treat an observation as a confirmed finding
enables actions: Distinguish between situations requiring immediate disclosure and those requiring further verification
required for obligations: Expertise-Calibrated Disclosure Obligation
required for obligations: Speculative Finding Exclusion Obligation
skill level: advanced
text references: Because Engineer A had domain expertise in wetland delineation and environmental law, Engineer A was obligated to disclose the observed wetland fill
text references: In contrast, the facts in the present case indicate a violation of the federal and state laws and regulations.
text references: the engineer in BER Case No. 89-7 did not have any particular expertise in the technical areas (mechanical, electrical) involved in the matter at issue. Taken together, it would be reasonable for an engineer under those circumstances to act in a deliberate and cautious manner before taking any action.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:36:09.645175+00:00
first discovered in case: 86
match confidence: 0.75
match reasoning: Concern Versus Fact Threshold Capability addresses calibrating disclosure obligations based on whether a concern has been substantiated. The expertise-calibrated disclosure concept is related but adds a distinct dimension: the engineer's own level of domain expertise modulates the threshold at which an observation becomes a reportable fact. This is a variant of the existing class rather than an identical match, because the existing class focuses on the evidentiary status of the finding while this capability focuses on how the engineer's expertise level affects that determination.
matched ontology class: Concern Versus Fact Threshold Capability
matched ontology label: Concern Versus Fact Threshold Capability
matches existing: true
source text: the engineer in BER Case No. 89-7 did not have any particular expertise in the technical areas (mechanical, electrical) involved in the matter at issue. Taken together, it would be reasonable for an engineer under those circumstances to act in a deliberate and cautious manner before taking any action.
comment: Capability to calibrate the form, urgency, and content of professional disclosures about potential violations or risks according to the depth of the engineer's domain expertise in the relevant technical area, recognizing that greater expertise reduces the threshold for treating an observation as an established fact warranting disclosure and that lesser expertise requires more caution before making formal assertions.
subclass of: Capability
scope note: [ConcernVersusFactThresholdCapability] Capability to distinguish between a preliminary professional concern that has not yet been substantiated by technical analysis and a finding that rises to the level of a demonstrable fact, and to calibrate disclosure obligations accordingly so that neither premature disclosure of unsubstantiated concerns nor suppression of confirmed findings occurs.
generated at time: 2026-06-04T17:36:09.645175+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Expertise-Calibrated Disclosure Obligation
type: Class
confidence: 0.82
derived from principle: Graduated Response Proportionality Principle
enforcement level: prima_facie
monitoring criteria: Disclosure content and form are consistent with the engineer's documented expertise in the relevant discipline and with the evidentiary basis for the concern.
nspe reference: I.1, II.2, II.3.b
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Other engineers
stakeholders affected: Regulatory authorities
text references: Engineer A's evaluation was based upon general surmise and speculation about the cause of the structural failure of the wall, based entirely upon a visual inspection without anything more. In addition, as in BER Case No. 89-7, there was nothing noted in the facts to indicate that Engineer A had expertise in the specific discipline involved.
text references: In addition, the engineer in BER Case No. 89-7 did not have any particular expertise in the technical areas (mechanical, electrical) involved in the matter at issue.
text references: In contrast, the facts in the present case indicate a violation of the federal and state laws and regulations.
text references: Those two cases involved a different set of factors that created a reasonable basis for an engineer to take a more measured approach to the situation.
violation consequences: Failure to calibrate disclosures to expertise level may result in either under-disclosure of known violations by domain experts or over-disclosure of speculative findings by non-experts, both of which breach professional standards.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:34:19.889581+00:00
first discovered in case: 86
match confidence: 0.75
match reasoning: This obligation overlaps substantially with the Concern Versus Fact Disclosure Threshold Obligation, which addresses the distinction between preliminary concerns and established facts as the trigger for mandatory disclosure. The expertise-calibration dimension adds a further nuance not fully captured by that class, but the core concept of calibrating disclosure to the evidentiary and competence basis is closely related, warranting a medium-confidence match.
matched ontology class: Concern Versus Fact Disclosure Threshold Obligation
matched ontology label: Concern Versus Fact Disclosure Threshold Obligation
matches existing: true
source text: In contrast, the facts in the present case indicate a violation of the federal and state laws and regulations.
comment: Duty of an engineer to calibrate the form, content, and urgency of disclosures about potential violations or risks to the engineer's actual level of expertise in the relevant technical discipline, disclosing with greater directness and specificity when the engineer has domain expertise, and with greater caution and qualification when the engineer lacks expertise in the specific discipline involved.
subclass of: DisclosureObligation
scope note: [ConcernVersusFactDisclosureThresholdObligation] Duty of an engineer to distinguish between a preliminary concern that has not yet been substantiated by technical analysis and a finding that constitutes a technical fact, and to recognize that mandatory disclosure obligations under Code section II.3.b are triggered only when the engineer's assessment rises to the level of fact rather than unverified concern, while acknowledging that prudent voluntary disclosure of concerns may nonetheless be appropriate.
generated at time: 2026-06-04T17:34:19.889581+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Expertise Calibrated Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.82
constraint type: ethical
flexibility: soft
mitigation strategies: Assess own domain expertise before characterizing a finding as speculative versus confirmed
mitigation strategies: Contact client promptly when specialized knowledge confirms a violation
mitigation strategies: Escalate to regulatory authorities if client fails to remediate
text references: In BER Case No. 89-7, for example, the facts revealed that the client had confided in the engineer and may have relied upon the engineer to maintain the information in confidence. In addition, the engineer in BER Case No. 89-7 did not have any particular expertise in the technical areas (mechanical, electrical) involved in the matter at issue.
text references: In contrast, the facts in the present case indicate a violation of the federal and state laws and regulations.
text references: Similarly, in BER Case No. 97-13, the engineer's evaluation was based upon general surmise and speculation about the cause of the structural failure of the wall, based entirely upon a visual inspection without anything more. In addition, as in BER Case No. 89-7, there was nothing noted in the facts to indicate that Engineer A had expertise in the specific discipline involved.
text references: Those two cases involved a different set of factors that created a reasonable basis for an engineer to take a more measured approach to the situation.
violation impact: Failure to disclose a confirmed violation that the engineer was competent to recognize, resulting in ongoing environmental harm and regulatory non-compliance.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:35:44.662063+00:00
first discovered in case: 86
match confidence: 0.78
match reasoning: The existing Concern Versus Fact Disclosure Constraint captures the core idea that only findings reaching the level of established fact trigger mandatory disclosure, while preliminary concerns do not. The present constraint adds the dimension that domain expertise determines whether an observation constitutes a confirmed fact or mere speculation, which is a variant of the same concept rather than a wholly new class. Medium confidence match because the expertise-calibration angle is a meaningful elaboration but the parent class is the closest existing match.
matched ontology class: Concern Versus Fact Disclosure Constraint
matched ontology label: Concern Versus Fact Disclosure Constraint
matches existing: true
source text: In contrast, the facts in the present case indicate a violation of the federal and state laws and regulations.
comment: Constraint requiring that an engineer's duty to disclose a potential violation or risk to public health, safety, or the environment is calibrated to the engineer's actual domain expertise. When an engineer possesses specialized competence in the relevant technical or regulatory area, an observation that would constitute mere speculation for a generalist rises to the level of a confirmed finding that triggers mandatory disclosure obligations. The engineer may not treat a confirmed violation as speculative simply because disclosure is inconvenient.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [ConcernVersusFactDisclosureConstraint] Ethical constraint limiting an engineer's disclosure obligations to findings that have reached the level of established fact supported by technical analysis. A preliminary concern or suspicion that has not yet been substantiated by sufficient analysis does not trigger the same mandatory disclosure obligations as a confirmed factual finding, and an engineer is not required under professional ethics codes to disclose unsubstantiated concerns, though prudent disclosure may be advisable.
generated at time: 2026-06-04T17:35:44.662063+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Fact-Based Disclosure Threshold Principle
type: Class
abstract nature: The boundary between a preliminary concern and a technical fact is inherently judgment-dependent and context-sensitive, requiring engineers to assess the state of their own analysis and the degree of confidence warranted by available evidence before characterizing findings as facts requiring mandatory disclosure.
confidence: 0.91
derived obligations: Assess the technical basis of concerns before treating them as facts requiring mandatory disclosure
derived obligations: Consider prudential disclosure of preliminary concerns even when not strictly required
derived obligations: Disclose confirmed technical findings to clients and relevant authorities
extensional examples: BER Case 07-6: information about threat to bird species constituted a fact requiring written disclosure in a public report
extensional examples: BER Case 99-8: incomplete drawings and specifications constituted facts requiring disclosure
extensional examples: Present case: Engineer L's initial concern about stormwater risk did not rise to the level of fact during the first project phase, but identification of runoff risk during the second phase did constitute fact triggering disclosure obligation
operationalization: Requires engineers to assess the technical basis of their concerns before characterizing them as facts, to disclose confirmed findings promptly, and to exercise judgment about whether prudential disclosure of preliminary concerns is appropriate even when not required.
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Proactive Risk Disclosure Principle
potential conflicts: Report Completeness Principle
principle category: professional_virtue
text references: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's concern does not rise to the technical or moral level of fact.
text references: Engineer L's identification of runoff risk is now fact.
text references: The key point of BER Case 07-6 is that information about the threat to the bird species is a fact of the case.
text references: per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts
value basis: Professional credibility and public trust depend on engineers distinguishing between verified findings and preliminary concerns, avoiding both premature alarm and suppression of confirmed risks.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:05:37.970804+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's concern does not rise to the technical or moral level of fact.
comment: Professional integrity principle establishing that an engineer's obligation to disclose concerns about project risks to clients, authorities, or the public is triggered when those concerns have reached the level of established technical fact, not merely preliminary concern or unverified suspicion. Below the threshold of fact, disclosure may be prudent but is not ethically required; at or above that threshold, disclosure becomes a professional obligation.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T10:05:37.970804+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Fact Gathering Diligence Obligation
type: Class
confidence: 0.88
derived from principle: Investigative Completeness Principle
enforcement level: mandatory
monitoring criteria: Investigation record documents contacts made with on-site personnel, contractors, and other witnesses; gaps in outreach are explained.
nspe reference: II.3
obligation type: competence
stakeholders affected: Client
stakeholders affected: Courts or arbitrators
stakeholders affected: Opposing parties
stakeholders affected: Public
text references: Engineer B's failure to inquire from the contractor, workers or others on the job is a failure of fact gathering diligence.
text references: It is clear that Engineer B may be criticized for his failure to communicate with Engineer A's on-site representative.
violation consequences: Conclusions rest on incomplete factual foundation; investigation fails professional standard of diligence; findings may be professionally indefensible.
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:35:09.835244+00:00
first discovered in case: 71
match confidence: 0.78
match reasoning: This is a variant of the existing Investigative Completeness Obligation. The existing class covers pursuing all reasonable lines of inquiry and consulting available witnesses and records. This individual instantiation emphasizes the specific sub-duty to contact on-site workers and contractors, which is a concrete application of the same parent obligation rather than a genuinely new concept. Confidence is medium because the existing class already covers witness consultation but does not foreground the contractor and worker outreach dimension as explicitly.
matched ontology label: Investigative Completeness Obligation
matches existing: true
source text: Engineer B's failure to inquire from the contractor, workers or others on the job is a failure of fact gathering diligence.
comment: Duty of an engineer conducting a technical investigation to make reasonable efforts to gather all available facts, including consulting contractors, workers, on-site personnel, and other witnesses who have direct knowledge of the work under investigation, rather than limiting inquiry to sources favorable to the retaining party.
subclass of: CompetenceObligation
generated at time: 2026-06-04T14:35:09.835244+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Failure to Consult Available Sources State
type: Class
action constraints: Professional must not dismiss available records without stated technical justification
action constraints: Professional must not issue conclusions without reasonable investigation of available sources
activation conditions: Knowledgeable parties or records are available and accessible
activation conditions: Professional declines to consult those sources
activation conditions: Professional is conducting a review or investigation
activation conditions: The unconsulted sources would be material to the professional's conclusions
confidence: 0.86
obligation activation: Duty of due diligence in investigation
obligation activation: Duty to consult available knowledgeable parties
obligation activation: Duty to seek out material information before issuing conclusions
persistence type: inertial
principle transformation: Transforms the general duty of objectivity and thoroughness into a specific obligation to actively seek out and consider available material information before issuing professional conclusions.
state category: information
termination conditions: Engagement concludes
termination conditions: Professional consults the available sources
termination conditions: Report is supplemented with findings from those sources
text references: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
text references: No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:51.674939+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
comment: State in which a professional conducting a review or investigation declines to consult available witnesses, records, or knowledgeable parties whose input would be material to the accuracy and completeness of the professional's conclusions, creating a condition of avoidable epistemic incompleteness and a breach of the duty of due diligence.
subclass of: InformationState
generated at time: 2026-06-04T14:26:51.674939+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Faithful Agent Boundary Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: Professional engineering client service and ethical boundary judgment
enables actions: Articulate the professional basis for refusing client instructions that compromise public safety obligations
enables actions: Identify when client instructions to proceed without protective measures exceed the limits of professional loyalty
enables actions: Serve the client's legitimate development interests while refusing to omit material safety findings
required for obligations: Faithful Agent Boundary Obligation
skill level: advanced
text references: Despite Engineer L's concerns, Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.88
match reasoning: Client Boundary Judgment Capability is defined as the ability to distinguish between serving a client's legitimate interests and complying with requests that would require omitting material technical evidence or compromising professional integrity, and to act accordingly. This maps closely to the faithful agent boundary capability required in this case. The match is high confidence.
matched ontology class: Client Boundary Judgment Capability
matched ontology label: Client Boundary Judgment Capability
matches existing: true
source text: Despite Engineer L's concerns, Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
comment: Capability to distinguish between serving a client's legitimate interests and complying with client instructions that would require omitting material safety findings, continuing work without required safeguards, or otherwise compromising professional integrity, and to act accordingly by refusing instructions that cross that boundary while continuing to serve legitimate client interests.
subclass of: Capability
scope note: [ClientBoundaryJudgmentCapability] Ability to distinguish between serving a client's legitimate interests and complying with requests that would require omitting material technical evidence or compromising professional integrity, and to act accordingly.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Faithful Agent Boundary Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.87
constraint type: ethical
flexibility: soft
mitigation strategies: Decline client instructions that require crossing the faithful agent boundary
mitigation strategies: Disclose the boundary to clients at the outset of engagements
mitigation strategies: Serve client interests within the boundaries set by public safety obligations
text references: The BER noted an engineer's obligation is to act for each client or employer as a faithful agent or trustee.
text references: The present case illustrates a conflict between Fundamental Canon I.1, the engineer's obligation to hold paramount the safety, health and welfare of the public; and Canon I.4, the engineer's obligation to act for each employer or client as a faithful agent or trustee.
text references: Under Fundamental Canon I.4, Engineer L has an affirmative obligation to act as the client's faithful agent or trustee. When asked in good faith to stop the design work, in the absence of facts to the contrary, there is no reason for Engineer L not to respect the client's request.
violation impact: Engineer violates paramount public safety duty while nominally fulfilling client service role; public exposed to unmitigated risk; professional ethics violation.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:13.190895+00:00
first discovered in case: 8
match confidence: 0.82
match reasoning: The Client Advocacy Boundary Constraint in the ontology captures the concept of a boundary on client service obligations, specifically the prohibition on crossing from legitimate client advocacy into suppression of material technical evidence. The faithful agent boundary concept in this case is a close variant: the faithful agent duty is bounded by the public safety paramount obligation. The match is at medium-high confidence because the ontology class is framed around expert or advocacy contexts while this case frames it as a general faithful agent limit.
matched ontology class: Client Advocacy Boundary Constraint
matched ontology label: Client Advocacy Boundary Constraint
matches existing: true
source text: The BER noted an engineer's obligation is to act for each client or employer as a faithful agent or trustee.
comment: Ethical constraint establishing that an engineer's duty to act as a faithful agent or trustee for a client is bounded by the paramount obligation to protect public health, safety, and welfare. The faithful agent duty does not extend to following client instructions that require omitting material safety findings, continuing work on projects with unmitigated public risks, or otherwise subordinating public welfare to client interests.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [ClientAdvocacyBoundaryConstraint] Prohibition on an engineer acting as a retained expert or agent crossing from legitimate advocacy of a client's position into suppression or omission of material technical evidence, marking the boundary between permissible client service and professional misconduct.
generated at time: 2026-06-05T02:27:13.190895+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Faithful Agent Boundary Judgment Capability
type: Class
capability category: reasoning
confidence: 0.95
domain specificity: Professional engineering practice across client engagement contexts
enables actions: Articulate the professional basis for refusing client instructions that exceed ethical limits
enables actions: Balance the faithful agent duty against the paramount public safety duty
enables actions: Continue serving legitimate client interests while refusing instructions that compromise public safety
enables actions: Identify when client instructions cross the boundary from legitimate direction to impermissible pressure
required for obligations: Faithful Agent Boundary Obligation
skill level: advanced
text references: The BER noted an engineer's obligation is to act for each client or employer as a faithful agent or trustee.
text references: in the absence of facts to the contrary, there is no reason for Engineer L not to respect the client's request
text references: the present case illustrates a conflict between Fundamental Canon I.1, the engineer's obligation to hold paramount the safety, health and welfare of the public; and Canon I.4, the engineer's obligation to act for each employer or client as a faithful agent or trustee.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:09.107464+00:00
first discovered in case: 8
match confidence: 0.95
match reasoning: The ontology contains Client Boundary Judgment Capability, defined as the ability to distinguish between serving a client's legitimate interests and complying with requests that would require omitting material technical evidence or compromising professional integrity. This maps directly to the faithful agent versus public safety tension analyzed throughout the case. It also appears in the prior-sections list as Faithful Agent Boundary Capability matched to this ontology class.
matched ontology class: Client Boundary Judgment Capability
matched ontology label: Client Boundary Judgment Capability
matches existing: true
source text: The BER noted an engineer's obligation is to act for each client or employer as a faithful agent or trustee.
comment: Capability to distinguish between serving a client's legitimate interests and complying with requests that would require omitting material technical evidence or compromising professional integrity, and to act accordingly.
subclass of: Capability
scope note: [ClientBoundaryJudgmentCapability] Ability to distinguish between serving a client's legitimate interests and complying with requests that would require omitting material technical evidence or compromising professional integrity, and to act accordingly.
generated at time: 2026-06-05T02:27:09.107464+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Faithful Agent Boundary Obligation
type: Class
confidence: 0.87
derived from principle: Litigation Neutrality Principle
enforcement level: mandatory
monitoring criteria: Expert reports and testimony are complete, accurate, and do not omit material evidence regardless of its effect on the retaining party's position
nspe reference: IV.1
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Court or mediating body
stakeholders affected: Opposing party
stakeholders affected: Professional licensing board
text references: Engineer B's duty as the municipality's retained expert did not extend to omitting material technical evidence from the report or declining to consult available witnesses.
text references: Engineer B, retained by the municipality in litigation against Engineer A, produced a report that relied exclusively on depth-of-penetration analysis while omitting wave equation results and pile driving record data that contradicted the report's conclusions.
violation consequences: Professional discipline; potential liability; findings discredited
discovered in case: 8
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:31:15.630641+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing obligation class in the ontology corresponds to this duty. This is a new class.
matches existing: false
source text: Engineer B, retained by the municipality in litigation against Engineer A, produced a report that relied exclusively on depth-of-penetration analysis while omitting wave equation results and pile driving record data that contradicted the report's conclusions.
comment: Duty of an engineer acting as agent or retained expert for a client to serve the client's legitimate interests while refusing to omit material technical evidence, misrepresent findings, or act in ways that violate professional ethics, even when the client's litigation position would benefit from such omissions.
subclass of: EthicalObligation
scope note: [Case 8] Duty of an engineer acting as agent or retained expert for a client to serve the client's legitimate interests while refusing to omit material technical evidence, misrepresent findings, or act in ways that violate professional ethics, even when the client's position would benefit from such omissions.
generated at time: 2026-06-04T14:31:15.630641+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Faithful Agent Duty Principle
type: Class
abstract nature: The scope of faithful agency is context-dependent and requires interpretation of what constitutes a legitimate client interest versus an instruction that crosses ethical limits. The principle gains meaning through cases that define its outer boundaries.
confidence: 0.93
derived obligations: Follow client instructions when no ethical obligation compels otherwise
derived obligations: Refuse client instructions that require suppression of safety-relevant findings
derived obligations: Respect client requests to suspend work in the absence of known safety facts
extensional examples: BER Case 76-4: Engineer Doe's duty as faithful agent to XYZ Corporation did not extend to suppressing findings about water quality degradation
extensional examples: BER Case 84-5: Engineer A's duty to client did not justify continuing a project after refusing safety measures
extensional examples: Present case: Engineer L's duty to Client X did not require continuing work without protective stormwater measures
operationalization: Requires engineers to follow client directions within ethical limits, respect client requests to pause or redirect work when no safety facts compel otherwise, and treat client information with appropriate discretion, while refusing instructions that require suppression of safety findings or creation of unmitigated public risk.
potential conflicts: Client Override Refusal Principle
potential conflicts: Proactive Risk Disclosure Principle
potential conflicts: Public Welfare Paramountcy Principle
principle category: relational
text references: Canon I.4, Engineer L has an affirmative obligation to act as the client's faithful agent or trustee.
text references: The BER noted an engineer's obligation is to act for each client or employer as a faithful agent or trustee.
text references: When asked in good faith to stop the design work, in the absence of facts to the contrary, there is no reason for Engineer L not to respect the client's request.
text references: Within this environmental framework, the present case illustrates a conflict between Fundamental Canon I.1, the engineer's obligation to hold paramount the safety, health and welfare of the public; and Canon I.4, the engineer's obligation to act for each employer or client as a faithful agent or trustee.
value basis: Professional relationships require trust and loyalty to function, and clients must be able to rely on engineers to advance their interests competently and honestly. However, this relational trust cannot be weaponized against the public.
discovered in case: 8
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:05:37.970804+00:00
first discovered in case: 8
match confidence: 0.82
match reasoning: The faithful agent or trustee duty is a specific engineering-context expression of the Loyalty principle in the ontology. The existing Loyalty class covers the general concept of professional loyalty to clients and employers. The present principle adds the engineering-specific framing of Canon I.4 and the explicit subordination to public welfare, making it a variant rather than an exact match.
matched ontology class: Loyalty
matched ontology label: Loyalty
matches existing: true
source text: The BER noted an engineer's obligation is to act for each client or employer as a faithful agent or trustee.
comment: Relational principle establishing that an engineer owes a duty of loyalty to each client or employer, acting as a faithful agent or trustee in advancing the client's legitimate interests. This duty is a genuine professional obligation but is subordinate to the engineer's paramount duty to public welfare and does not authorize compliance with client instructions that suppress safety-relevant findings or create unmitigated public risk.
subclass of: RelationalPrinciple
generated at time: 2026-06-04T10:05:37.970804+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Federal Agency Approving Engineer
type: Class
confidence: 0.85
role category: public_responsibility
text references: The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:46:00.156208+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project
comment: A licensed professional engineering role within a federal funding agency in which the practitioner reviews, approves, and seals engineering drawings and specifications submitted by a design engineer as a condition of federal project funding, bearing professional accountability for the adequacy of that approval.
subclass of: EngineerRole
subclass of: PublicResponsibilityRole
generated at time: 2026-06-04T16:46:00.156208+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Federal Grant Project Requirement Resource
type: Class
authority source: Federal grant-making agencies
confidence: 0.78
extensional function: Establishes the regulatory and procedural framework within which federally funded engineering projects must operate, including approval authority and funding constraints.
resource category: legal_resource
text references: Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs
text references: approved by Engineer B of the engineering staff of the federal agency funding the project
usage context: Cost overrun and funding adequacy determinations
usage context: Engineering document approval
usage context: Federally funded infrastructure design
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:45:36.674624+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: approved by Engineer B of the engineering staff of the federal agency funding the project
comment: Federal agency requirements and conditions attached to grant-funded public infrastructure projects, including review and approval procedures for engineering documents and constraints on the use of federal funds.
subclass of: LegalResource
generated at time: 2026-06-04T16:45:36.674624+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Federal Wetland Protection Regulation Resource
type: Class
authority source: Federal regulatory agencies including the U.S. Army Corps of Engineers and the U.S. Environmental Protection Agency
confidence: 0.87
extensional function: Establishes the legal floor defining what constitutes a violation and grounds the engineer's professional obligation to respond when a violation is observed
resource category: legal_resource
text references: installation of the fill material is a substantial violation of the federal and state laws and regulations
usage context: Professional reporting obligations
usage context: Regulatory violation identification
usage context: Wetland fill permit requirements
discovered in case: 86
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T17:25:28.729274+00:00
first discovered in case: 86
match confidence: 0.82
match reasoning: The existing Environmental Protection Regulation Resource class covers local, state, or jurisdictional regulations for safeguarding public water sources and controlling stormwater runoff. Federal wetland fill prohibition regulations are a closely related but distinct category covering a broader federal statutory framework. Matching as a variant with medium confidence, as the existing class does not explicitly address federal wetland fill permitting statutes such as Section 404 of the Clean Water Act.
matched ontology class: Environmental Protection Regulation Resource
matched ontology label: Environmental Protection Regulation Resource
matches existing: true
source text: installation of the fill material is a substantial violation of the federal and state laws and regulations
comment: Federal statutes and implementing regulations governing the protection of wetland areas, including prohibitions on the placement of fill material in jurisdictional wetlands without required permits, variances, or authorizations. These regulations establish binding legal obligations on property owners and inform the professional duties of engineers who perform services on regulated wetland sites.
subclass of: LegalResource
scope note: [EnvironmentalProtectionRegulationResource] Local, state, or jurisdictional regulations specifying mandatory environmental protection requirements, including standards for safeguarding public water sources and controlling stormwater runoff impacts on natural water bodies.
generated at time: 2026-06-04T17:25:28.729274+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Field Notes Preservation Obligation
type: Class
confidence: 0.83
derived from principle: Public Welfare Paramountcy Principle
enforcement level: mandatory
monitoring criteria: Original field notes are retained intact and unaltered; any supplemental annotations are clearly dated and distinguished from original entries.
nspe reference: III.2.a, II.3.a
obligation type: ethical
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Legal and regulatory authorities
stakeholders affected: Public agency
text references: Engineer A stated that he would retain the information from his engineering notes but not include it in the final report, as requested.
text references: However, under no circumstance would it be appropriate for Engineer A to alter his field notes.
violation consequences: Alteration or destruction of field notes constitutes a breach of professional integrity and may obstruct future investigations or corrective actions that depend on accurate contemporaneous records.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:34:19.889581+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: However, under no circumstance would it be appropriate for Engineer A to alter his field notes.
comment: Duty of an engineer to preserve and retain field notes, engineering notes, and other contemporaneous records of observations made during professional services, even when those observations are not included in a formal report, and to refrain from altering those notes.
subclass of: EthicalObligation
generated at time: 2026-06-04T17:34:19.889581+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Formal Authority Notification Required State
type: Class
action constraints: Formal presentation must be made regardless of client consent
action constraints: Informal or verbal contact with authorities does not satisfy the formal notification obligation
activation conditions: Client or governing body has overruled the engineer's safety recommendations
activation conditions: Engineer has confirmed a public safety risk
activation conditions: Informal or preliminary contact with authorities has occurred but formal presentation has not yet been made
confidence: 0.85
obligation activation: Duty to advise client formally that the project will not be successful if safety is not addressed
obligation activation: Duty to further pursue the matter if formal presentations fail to produce corrective action
obligation activation: Duty to present facts, findings, and recommendations formally in writing to regulatory agencies
persistence type: inertial
principle transformation: Transforms the general duty to report safety concerns into a specific procedural obligation requiring formal written communication to authorities, distinguishing mere contact from a complete formal presentation of professional findings.
state category: risk
termination conditions: Authorities take corrective action
termination conditions: Engineer withdraws from engagement after completing notification duties
termination conditions: Formal written presentation of findings and recommendations has been delivered to all appropriate authorities
text references: It appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations.
text references: The formal presentations satisfy Engineer A's and Engineer B's duty to report.
text references: this advisement should proceed in a formal manner
discovered in case: 76
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T11:18:53.656605+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: It appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations.
comment: State in which a professional engineer has identified a public safety risk, has had recommendations overruled by a client or governing body, and is now obligated to make a formal written presentation of findings and recommendations to one or more regulatory or governmental authorities, as distinguished from informal or verbal communication, in order to satisfy the duty to report under applicable professional codes.
subclass of: RiskState
generated at time: 2026-06-05T11:18:53.656605+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Formal Escalation Obligation Principle
type: Class
abstract nature: Requires judgment about what constitutes a sufficiently formal presentation in a given regulatory context, and about which authorities are appropriate recipients of the formal presentation.
confidence: 0.8
derived obligations: Ensure the formal presentation is sufficient to enable the authority to act
derived obligations: Identify and contact all appropriate regulatory authorities
derived obligations: Prepare a formal written presentation of facts, findings, and recommendations
extensional examples: BER Case No. 19-10 requiring Engineer A to contact supervisors, fire marshals, or agencies with jurisdiction in writing
extensional examples: BER Case No. 89-7 establishing that failure to report safety violations to appropriate public authorities is unethical
operationalization: Requires engineers to prepare and deliver a formal written presentation of facts, findings, and recommendations to the state regulatory agency or other appropriate authority, going beyond any prior informal contact.
potential conflicts: Client confidentiality
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Graduated Response Proportionality Principle
principle category: professional_virtue
text references: Again, as with the state regulatory agency, this advisement should proceed in a formal manner.
text references: It appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations.
text references: The formal presentations satisfy Engineer A's and Engineer B's duty to report.
value basis: Informal contact with authorities may fail to trigger regulatory action or create an adequate record; the public interest requires that safety concerns be communicated in a way that compels attention and preserves accountability.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:26:55.962095+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: It appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations.
comment: Professional principle requiring engineers whose safety recommendations have been overruled to present their findings, facts, and recommendations to appropriate regulatory or governmental authorities in a formal manner, not merely through informal contact, so that the presentation creates a clear record and gives the authority sufficient information to act. Informal prior contact with an authority does not satisfy this obligation; a structured formal presentation is required.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-05T11:26:55.962095+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Formal Presentation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.88
constraint type: procedural
flexibility: soft
mitigation strategies: Coordinate with co-engineers to ensure formal presentations are consistent and mutually reinforcing
mitigation strategies: Document all prior informal contacts and supplement them with formal written submissions
mitigation strategies: Prepare a formal written report of findings and recommendations for submission to the regulatory authority
text references: The formal presentations satisfy Engineer A's and Engineer B's duty to report
text references: it appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations
text references: this advisement should proceed in a formal manner
violation impact: Regulatory authorities lack the complete factual record needed to act, public health risk persists without adequate official response, engineer fails to meet professional ethics obligations.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:35.133297+00:00
first discovered in case: 76
match confidence: 0.75
match reasoning: The Verbal Only Report Constraint addresses the prohibition on treating verbal or informal communication as a substitute for a written report submitted to a public authority. The present constraint is a variant that applies specifically to regulatory escalation after a client override, requiring formal written presentation rather than informal contact. The core concept is the same but the context is escalation rather than initial reporting, so a medium-confidence variant match is appropriate.
matched ontology class: Verbal Only Report Constraint
matched ontology label: Verbal Only Report Constraint
matches existing: true
source text: it appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations
comment: Procedural and ethical constraint requiring that when an engineer has identified a public health or safety risk and has had professional recommendations overruled by a client or governing body, any notification to regulatory authorities must take the form of a formal written presentation of facts, findings, and recommendations, rather than informal contact or verbal communication alone. Informal prior contact with a regulatory agency does not satisfy this obligation.
subclass of: DefeasibleConstraint
subclass of: ProceduralConstraint
scope note: [VerbalOnlyReportConstraint] Ethical and procedural constraint prohibiting an engineer from treating a verbal communication of a material technical finding as a substitute for including that finding in a written report submitted to a public authority or other relying party. The finding must appear in the written record so that the public authority receives complete and accurate information.
generated at time: 2026-06-05T11:29:35.133297+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Formal Project Failure Notification Obligation
type: Class
confidence: 0.86
derived from principle: Project Success Notification Principle
enforcement level: mandatory
monitoring criteria: Documented written communication to the client stating that the project will not achieve safe outcomes without implementation of the recommended measures.
nspe reference: II.1.a, III.2.b
obligation type: disclosure
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: Again, as with the state regulatory agency, this advisement should proceed in a formal manner.
text references: If project success is defined as 'the public will not be endangered at all,' then Engineers A and B should advise their client that they believe the project will not be successful.
violation consequences: Failure to formally advise the client of predicted project failure deprives the client of a documented professional judgment and may leave the engineer without a record of having fulfilled the notification duty.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:28:12.343728+00:00
first discovered in case: 76
match confidence: 0.78
match reasoning: The existing Project Success Notification Obligation captures the general duty to advise a client when a project will not be successful. This class adds the specific requirement that the notification be formal and documented, which is a meaningful variant warranting a distinct class label while still being closely related to the existing concept.
matched ontology class: Project Success Notification Obligation
matched ontology label: Project Success Notification Obligation
matches existing: true
source text: If project success is defined as 'the public will not be endangered at all,' then Engineers A and B should advise their client that they believe the project will not be successful.
comment: Duty of an engineer to advise a client formally, in writing, that the project will not be successful as defined by public safety outcomes, when the client has overruled safety recommendations whose implementation is necessary to prevent public harm, so that the client has a documented formal notice of the engineer's professional judgment before proceeding.
subclass of: DisclosureObligation
scope note: [ProjectSuccessNotificationObligation] Duty of an engineer to advise a client or employer when, in the engineer's professional judgment, a project will not be successful, including when success is threatened by the absence of safety measures the client has declined to implement, so that the client has the opportunity to reconsider before the engineer is placed in a position of ethical conflict.
generated at time: 2026-06-05T11:28:12.343728+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Formal Regulatory Presentation Capability
type: Class
capability category: communication
confidence: 0.85
domain specificity: Public health and safety engineering with regulatory interface
enables actions: Distinguish between informal contact and a formal regulatory presentation
enables actions: Organize facts, findings, and recommendations in a format suitable for regulatory review
enables actions: Prepare a formal written or oral presentation of technical findings for a regulatory agency
required for obligations: Engineers A B Formal Regulatory Presentation
required for obligations: Formal Regulatory Presentation Obligation
required for obligations: Regulatory Authority Presentation Obligation
skill level: advanced
text references: Engineers A and B are required to hold paramount the safety, health, and welfare of the public, and as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required.
text references: The formal presentations satisfy Engineer A's and Engineer B's duty to report.
text references: there should be a formal presentation of the facts, findings, and recommendations
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:39.466339+00:00
first discovered in case: 76
match confidence: 0.72
match reasoning: Safety Disclosure Escalation Capability covers recognizing when internal resolution has failed and escalating to regulatory authorities. The present capability is more specific in requiring the ability to prepare and deliver a formal structured presentation to a regulatory body, which is a distinct communicative and procedural competency beyond merely deciding to escalate. It is a variant warranting medium-confidence match.
matched ontology class: Safety Disclosure Escalation Capability
matched ontology label: Safety Disclosure Escalation Capability
matches existing: true
source text: there should be a formal presentation of the facts, findings, and recommendations
comment: Capability to prepare and deliver a formal, structured presentation of professional facts, findings, and recommendations to a state or regulatory authority, as distinguished from an informal contact or preliminary notification, including the ability to determine when formality is required and to organize technical content in a manner appropriate for a regulatory audience.
subclass of: Capability
scope note: [SafetyDisclosureEscalationCapability] Capability to recognize when internal resolution of a safety concern has failed and to escalate disclosure to appropriate regulatory authorities, including the ability to sequence escalation steps correctly by first advising the responsible engineer before notifying authorities.
generated at time: 2026-06-05T11:29:39.466339+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Formal Regulatory Presentation Obligation
type: Class
confidence: 0.88
derived from principle: Formal Escalation Obligation Principle
enforcement level: mandatory
monitoring criteria: Documented evidence of a formal written or in-person presentation of technical findings and recommendations to the appropriate regulatory authority.
nspe reference: II.1.a, II.1.c
obligation type: reporting
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: State regulatory agency
text references: It appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations.
text references: The formal presentations satisfy Engineer A's and Engineer B's duty to report.
violation consequences: Failure to formally present findings leaves the regulatory authority without a complete record and may result in continued endangerment of public health and safety.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:28:12.343728+00:00
first discovered in case: 76
match confidence: 0.75
match reasoning: The existing class captures the duty to report to regulatory authorities when a client overrides safety recommendations, but this obligation adds the specific requirement that the report take the form of a formal presentation rather than informal contact, making it a meaningful variant rather than an exact match.
matched ontology class: Client Override Public Safety Reporting Obligation
matched ontology label: Client Override Public Safety Reporting Obligation
matches existing: true
source text: It appears that the state regulatory agency has been contacted; however, there should be a formal presentation of the facts, findings, and recommendations.
comment: Duty of an engineer whose professional recommendations have been overruled by a client or governing body to make a formal presentation of facts, findings, and recommendations to the appropriate state or federal regulatory authority, rather than relying on informal prior contact, so that the authority has a complete and documented basis for exercising its oversight function.
subclass of: ReportingObligation
scope note: [ClientOverridePublicSafetyReportingObligation] Duty of an engineer to report identified risks to public health or safety to the appropriate regulatory or pollution control authority when the client refuses to implement recommended protective measures and insists on proceeding without adequate safeguards, placing the paramount duty to public welfare above the faithful agent duty to the client.
generated at time: 2026-06-05T11:28:12.343728+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Free Services Solicitation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Competing Engineers
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.82
constraint type: ethical
flexibility: hard
mitigation strategies: Decline to provide free engineering services when a paid engagement is anticipated
mitigation strategies: Disclose the conflict and withdraw from the advisory role before providing any services
mitigation strategies: Provide only informal referrals to publicly available resources rather than substantive engineering analysis
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information and the extension of free services. Both aspects of the conduct were unethical in the view of the BER.
text references: not offer any gift or other valuable consideration in order to secure work
violation impact: Unfair competitive advantage, corruption of client decision-making, violation of professional ethics codes prohibiting gifts or consideration to secure work.
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:48:44.763664+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: not offer any gift or other valuable consideration in order to secure work
comment: Ethical constraint prohibiting an engineer from extending free or donated professional services to a prospective client as a mechanism to position for or secure subsequent paid work, because such conduct constitutes an improper gift or valuable consideration offered in exchange for future engagement.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T08:48:44.763664+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Full Responsibility Assumption Obligation
type: Class
confidence: 0.85
derived from principle: Professional Accountability Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer acknowledged and accepted professional responsibility for the sealed documents and did not attempt to attribute deficiencies to subordinates or tools
nspe reference: II.2.b
obligation type: ethical
stakeholders affected: Clients
stakeholders affected: General public
stakeholders affected: Regulatory bodies
stakeholders affected: Subordinate engineers
text references: In either case, we are not of the view that an engineer must personally prepare the drawings, plans and other documents involved.
text references: The key requirement is that an engineer possesses sufficient competence, assumes full responsibility for the work product and carefully directs, controls and reviews the material prepared under the engineer's responsible charge.
violation consequences: Ethical violation under NSPE II.2.b; professional liability; potential license discipline if the engineer attempts to disclaim responsibility for sealed documents
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:11:22.208486+00:00
first discovered in case: 120
match confidence: 0.76
match reasoning: The existing Responsible Charge Verification Obligation covers the duty to conduct comprehensive verification before sealing. The present obligation emphasizes the assumption of full professional responsibility as a condition of sealing, which is a related but distinct emphasis on accountability rather than verification process. Matched as a variant at medium confidence.
matched ontology class: Responsible Charge Verification Obligation
matched ontology label: Responsible Charge Verification Obligation
matches existing: true
source text: The key requirement is that an engineer possesses sufficient competence, assumes full responsibility for the work product and carefully directs, controls and reviews the material prepared under the engineer's responsible charge.
comment: Duty of a licensed engineer who seals documents prepared by others under the engineer's responsible charge to assume full professional responsibility for the work product, including accountability for any errors, deficiencies, or failures in those documents, as a condition of exercising the sealing authority.
subclass of: EthicalObligation
scope note: [ResponsibleChargeVerificationObligation] Duty of a licensed engineer in responsible charge to conduct a comprehensive, experience-based verification of all work products before sealing or submitting them, including active involvement in design and development rather than merely reviewing completed documents, so that the engineer can genuinely certify the work meets professional and safety standards.
generated at time: 2026-06-04T18:11:22.208486+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Funding Constraint Analysis Capability
type: Class
capability category: domain_specific
confidence: 0.83
domain specificity: Public infrastructure project delivery advisory services involving federally or agency-restricted funding sources
enables actions: Communicate funding constraints accurately to non-engineer clients
enables actions: Identify funding-agency-approved delivery methods
enables actions: Recognize funding-imposed restrictions such as entity separation requirements
required for obligations: Complete Options Advisory Obligation
required for obligations: Funding Constraint Disclosure Obligation
skill level: intermediate
text references: City B's City Administrator asked Engineer A for a recommendation on project delivery methods for their upcoming wastewater system improvements project using a specific funding source
text references: Under the proposed funding source, there are four approved project delivery methods
text references: if Construction Manager at Risk is selected by the owner, City B, the funding agency requires the Construction Manager at Risk firm and the Engineer of Record be two distinct entities
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:39.966147+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: City B's City Administrator asked Engineer A for a recommendation on project delivery methods for their upcoming wastewater system improvements project using a specific funding source
comment: Capability to identify, interpret, and communicate constraints imposed by a specific funding source on available project delivery or procurement options, including the ability to recognize when funding rules restrict the option set or impose conditions on particular delivery methods.
subclass of: Capability
generated at time: 2026-06-04T08:45:39.966147+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Funding Constraint Disclosure Obligation
type: Class
confidence: 0.83
derived from principle: Complete Options Analysis Principle
enforcement level: mandatory
monitoring criteria: Advisory work product identifies and accurately describes all funding-source constraints applicable to each delivery method option
nspe reference: II.5.a
obligation type: disclosure
stakeholders affected: Funding agency
stakeholders affected: General public
stakeholders affected: Municipal client
text references: Additionally, if Construction Manager at Risk is selected by the owner, City B, the funding agency requires the Construction Manager at Risk firm and the Engineer of Record be two distinct entities.
text references: City B's City Administrator asked Engineer A for a recommendation on project delivery methods for their upcoming wastewater system improvements project using a specific funding source.
text references: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
violation consequences: Client selects a delivery method without understanding funding constraints, leading to compliance failures or loss of funding
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:44:38.157284+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: City B's City Administrator asked Engineer A for a recommendation on project delivery methods for their upcoming wastewater system improvements project using a specific funding source.
comment: Duty of an engineer advising a client on project delivery or procurement options under a specific funding source to accurately and completely disclose all constraints, requirements, and conditions imposed by that funding source that affect the available options, including any requirements that restrict how certain delivery methods may be structured.
subclass of: DisclosureObligation
generated at time: 2026-06-04T08:44:38.157284+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Geotechnical Analysis Capability
type: Class
capability category: domain_specific
confidence: 0.93
domain specificity: Geotechnical and foundation engineering
enables actions: Assess skin friction and end-bearing contributions to pile capacity
enables actions: Evaluate pile set-up strength gain over time
enables actions: Interpret pile driving records and blow count data
enables actions: Perform wave equation analysis on pile driving data
required for obligations: Contradictory Evidence Disclosure Obligation
required for obligations: Investigative Completeness Obligation
required for obligations: Methodological Consistency Obligation
skill level: expert
text references: Applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
text references: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations. This opinion was based upon the fact that the nineteen piles did not reach sufficient depth to develop the full strength when applying skin friction resistance value to the square footage of pile penetration.
text references: The increase in set up strength with time was confirmed.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class covers technical geotechnical engineering competency including pile capacity analysis and wave equation methods.
matches existing: false
source text: Applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
comment: Technical competency in geotechnical engineering methods including pile capacity analysis, wave equation calculations, skin friction assessment, and interpretation of pile driving records.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Geotechnical Investigation Report Resource
type: Class
authority source: Licensed geotechnical engineering firms retained for subsurface investigation
confidence: 0.8
extensional function: Grounds foundation design decisions in documented subsurface data and professional geotechnical judgment, providing the technical basis for design parameters such as anticipated pile set-up strength.
resource category: reference_material
text references: Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements.
usage context: Construction administration
usage context: Dispute resolution technical review
usage context: Foundation design
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:23.227248+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements.
comment: A formal report produced by a geotechnical engineering firm documenting subsurface investigation findings, soil properties, and design recommendations for foundation systems. Such reports provide the technical basis for pile design parameters including expected strength gain over time and serve as primary reference documents throughout construction and dispute resolution.
subclass of: ReferenceMaterial
generated at time: 2026-06-04T14:26:23.227248+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Geotechnical Test Report Resource
type: Class
authority source: Retained geotechnical engineering consultants and testing firms
confidence: 0.82
extensional function: Provides empirical grounding for assessments of foundation design adequacy and serves as a primary evidentiary artifact in professional and legal disputes over structural performance.
resource category: technical_standard
text references: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test
usage context: Foundation design review
usage context: Litigation and mediation support
usage context: Peer technical evaluation
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:23.227248+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
comment: A formal engineering report documenting the results of geotechnical field testing, such as pile load tests or dynamic testing, including methodology, equipment performance, and conclusions about soil or foundation behavior. Such reports serve as technical evidence in disputes and as professional knowledge sources grounding design adequacy determinations.
subclass of: TechnicalStandard
generated at time: 2026-06-04T14:26:23.227248+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Graduated Escalation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.87
constraint type: procedural
flexibility: soft
mitigation strategies: Contact client first upon discovering a confirmed violation
mitigation strategies: Monitor actual remediation progress
mitigation strategies: Report to authorities only if client fails to take adequate steps
mitigation strategies: Set a reasonable timeframe for client remediation
text references: Engineer A's actions appear to be obvious: contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
text references: If appropriate steps are not taken by the client, the engineer would have an obligation to bring this matter to the attention of the appropriate authorities.
text references: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
text references: for Engineer A to have reported this information to a public authority under the circumstances as outlined in the facts, before determining whether corrective action is taken, would have been an overreaction and could easily have risked jeopardizing the professional reputations of his client and the public agency.
violation impact: Either premature regulatory escalation that damages client interests unnecessarily, or failure to escalate when the client does not remediate, leaving the public harm unaddressed.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:35:44.662063+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: Engineer A's actions appear to be obvious: contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
comment: Ethical and procedural constraint establishing that an engineer who discovers a client's confirmed violation of law or regulation must follow a graduated sequence of responses: first contacting the client directly, then monitoring remediation, and only then escalating to regulatory authorities if the client fails to act. The engineer may not skip directly to regulatory reporting without first giving the client an opportunity to remedy the violation, nor may the engineer stop at client contact without following through to verify compliance.
subclass of: DefeasibleConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-04T17:35:44.662063+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Graduated Response Proportionality Principle
type: Class
abstract nature: Requires judgment about where a given situation falls on a spectrum from mere speculation to established fact, and what level of response that position on the spectrum demands.
confidence: 0.85
derived obligations: Assess evidentiary basis before acting
derived obligations: Avoid premature public disclosure that could harm parties without adequate basis
derived obligations: Begin response at the level of client notification
derived obligations: Escalate to regulatory authorities only when client fails to act or threat is immediate
extensional examples: NSPE BER Case 97-13 holding that reporting to public authority before determining whether corrective action is taken would have been an overreaction when the engineer's basis was mere visual speculation
extensional examples: NSPE BER current case distinguishing situations of established legal violation from situations of mere surmise and requiring direct client contact as the first step
operationalization: Requires engineers to assess the certainty and severity of a concern, begin with the least disruptive adequate response, and escalate only when prior steps have failed or the severity of the threat demands immediate action.
potential conflicts: Fact-Based Disclosure Threshold Principle
potential conflicts: Proactive Risk Disclosure Principle
potential conflicts: Public Welfare Paramountcy Principle
principle category: professional_virtue
text references: Engineer A's actions appear to be obvious--contact the client and inquire directly about the actions the client has taken and point out the violations of the law and that immediate steps need to be taken to remedy the violation.
text references: Those two cases involved a different set of factors that created a reasonable basis for an engineer to take a more measured approach to the situation.
text references: for Engineer A to have reported this information to a public authority under the circumstances as outlined in the facts, before determining whether corrective action is taken, would have been an overreaction and could easily have risked jeopardizing the professional reputations of his client and the public agency.
value basis: Professional responsibility requires neither reckless inaction nor disproportionate escalation; the engineer's response must match the evidentiary and legal weight of the situation to protect both public interests and the legitimate interests of clients and colleagues.
discovered in case: 76
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:32:47.556599+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: for Engineer A to have reported this information to a public authority under the circumstances as outlined in the facts, before determining whether corrective action is taken, would have been an overreaction and could easily have risked jeopardizing the professional reputations of his client and the public agency.
comment: Professional principle requiring engineers to calibrate the urgency and directness of their response to a discovered violation or risk in proportion to the certainty, severity, and legal clarity of the threat, proceeding through escalating steps from client contact to regulatory reporting rather than immediately invoking the most drastic available response.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T17:32:47.556599+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Gratuitous Services Conflict Recognition Capability
type: Class
capability category: awareness
confidence: 0.83
domain specificity: Professional engineering practice, particularly advisory and pre-construction service contexts
enables actions: Decline to provide free services that function as a solicitation vehicle
enables actions: Identify when a free advisory service creates a competitive advantage for subsequent paid work
enables actions: Recognize that the client's awareness of the donation is irrelevant to the ethical violation
required for obligations: Advisory Conflict Disclosure Obligation
required for obligations: Gratuitous Services Solicitation Prohibition Obligation
skill level: intermediate
text references: It is not clear whether City Administrator knowingly solicited a donation of services.
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information and the extension of free services. Both aspects of the conduct were unethical
text references: not offer any gift or other valuable consideration in order to secure work
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:48:46.347963+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: It is not clear whether City Administrator knowingly solicited a donation of services.
comment: Capability to recognize when providing free or donated professional services to a prospective client creates an ethical conflict by positioning the provider to benefit from subsequent paid work, and to identify this arrangement as a prohibited form of solicitation regardless of whether the client knowingly solicited the donation.
subclass of: Capability
generated at time: 2026-06-04T08:48:46.347963+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Gratuitous Services Prohibition Principle
type: Class
abstract nature: The boundary between informal collegial assistance and a service offer intended to secure work requires contextual judgment, with the engineer's interest in subsequent work serving as a key indicator of improper motive.
confidence: 0.85
derived obligations: Decline to provide partial analysis that favors own interests
derived obligations: Disclose interest in subsequent work before providing any advisory services
derived obligations: Refer clients to neutral resources when informal advice is sought
extensional examples: BER present case where Engineer A provided free advisory memo recommending a delivery method under which Engineer A was qualified to provide subsequent paid services
operationalization: Engineers who are asked for informal advice must either refer the client to neutral resources or provide genuinely complete and unbiased analysis; they may not provide partial, self-serving analysis as a free service designed to position themselves for subsequent engagement.
potential conflicts: Advisory Role Integrity Principle
potential conflicts: Conflict of Interest Disclosure Principle
principle category: domain_specific
text references: Both aspects of the conduct were unethical in the view of the BER
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information (as in 95-5 and 99-8) and the extension of free services
text references: not offer any gift or other valuable consideration in order to secure work
value basis: Competitive fairness and client trust require that engineers be selected on merit rather than through the extension of gratuitous services that create obligation or bias in the client.
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:46:54.906706+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: not offer any gift or other valuable consideration in order to secure work
comment: Professional principle prohibiting engineers from offering free or donated professional services as a means of securing subsequent paid work, recognizing that such offers constitute a form of valuable consideration extended to influence a client's selection of the engineer for future engagements.
subclass of: DomainSpecificPrinciple
generated at time: 2026-06-04T08:46:54.906706+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Gratuitous Services Solicitation Prohibition Obligation
type: Class
confidence: 0.87
derived from principle: Gratuitous Services Prohibition Principle
enforcement level: mandatory
monitoring criteria: Evidence that free services were not provided as a vehicle to position for or solicit subsequent paid work
nspe reference: III.5.a
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Competing engineers
stakeholders affected: Public
text references: Engineer A could have referred City Administrator to resources (whether library, free, or subscription) that provided complete analyses of the various methodologies. That would be a completely ethical informal response
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information and the extension of free services
text references: not offer any gift or other valuable consideration in order to secure work
violation consequences: Professional discipline; findings of unethical conduct; potential disqualification from the subsequent engagement
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:47:48.914349+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: not offer any gift or other valuable consideration in order to secure work
comment: Duty of an engineer to refrain from offering free or donated professional services as a means of securing subsequent paid work, recognizing that the provision of complimentary engineering services to position for a follow-on engagement violates the prohibition on offering valuable consideration to secure work.
subclass of: EthicalObligation
generated at time: 2026-06-04T08:47:48.914349+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Inadequate AI Review State
type: Class
action constraints: Must not affix signature or seal to AI-generated documents reviewed only at a high level
action constraints: Must not submit design documents with undetected safety or dimensional errors
activation conditions: AI tool used to generate technical plans or documents
activation conditions: Errors or omissions remain undetected in the work product
activation conditions: Professional performs only high-level or cursory review of AI output
confidence: 0.87
obligation activation: Duty to conduct experience-based quality assurance review
obligation activation: Duty to correct identified deficiencies before submission
obligation activation: Duty to refrain from sealing or signing documents not under proper direction and control
persistence type: inertial
principle transformation: Transforms the responsible charge and public safety principles into a concrete obligation to apply at least the same level of scrutiny to AI-generated work as to human-generated work, including critical engagement with outputs rather than passive acceptance.
state category: risk
termination conditions: All errors and omissions identified and corrected
termination conditions: Comprehensive verification process completed
termination conditions: Responsible charge obligations fully satisfied
text references: By relying on AI-assisted tools without a comprehensive verification process of its output, Engineer A risked violating this requirement.
text references: Engineer A elected to only conduct a high-level review and adjusted certain elements to align with site-specific conditions.
text references: When Client W reviewed the design documents, they found misaligned dimensions and key safety features (including those necessary for compliance with local regulations) were omitted.
discovered in case: 7
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-03T14:01:36.958645+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A elected to only conduct a high-level review and adjusted certain elements to align with site-specific conditions.
comment: State in which a professional has performed only a superficial or high-level review of AI-generated technical work product rather than the comprehensive verification required for responsible charge, leaving errors, omissions, or safety deficiencies undetected and creating elevated risk of regulatory noncompliance and public harm.
subclass of: RiskState
generated at time: 2026-06-03T14:01:36.958645+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Incomplete Deliverable Disclosure Capability
type: Class
capability category: communication
confidence: 0.86
domain specificity: Professional engineering practice involving sealed design documents submitted to public agencies
enables actions: Disclose known deficiencies to clients and approving authorities
enables actions: Recognize material incompleteness in professional deliverables
enables actions: Refrain from submitting incomplete work without disclosure
required for obligations: Deliverable Completeness Disclosure Obligation
required for obligations: Engineer A Deliverable Completeness Disclosure
skill level: intermediate
text references: While much of the information was missing from the drawings and specifications
text references: did not inform anyone as to their incompleteness
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:51:18.309339+00:00
first discovered in case: 85
match confidence: 0.78
match reasoning: Incomplete Analysis Disclosure Capability addresses recognizing when a professional analysis has been suspended or left incomplete and disclosing that status to the client. The present capability is closely analogous but applies to design deliverables rather than analytical reports, and involves active concealment at submission rather than suspension of work. The match is a variant of the same concept at medium confidence.
matched ontology class: Incomplete Analysis Disclosure Capability
matched ontology label: Incomplete Analysis Disclosure Capability
matches existing: true
source text: did not inform anyone as to their incompleteness
comment: Capability to recognize when a professional deliverable such as drawings or specifications is materially incomplete, and to proactively disclose that incompleteness to the client, approving authorities, and other relying parties before or at the time of submission, rather than concealing the deficiency.
subclass of: Capability
scope note: [IncompleteAnalysisDisclosureCapability] Capability to recognize when a professional analysis has been suspended or left incomplete and to disclose the status and significance of unfinished findings to the client, including the ability to communicate identified but unquantified risks rather than remaining silent about them during a work suspension.
generated at time: 2026-06-04T16:51:18.309339+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Incomplete Deliverable Disclosure Constraint
type: Class
affected stakeholders: Approving Engineer
affected stakeholders: Client
affected stakeholders: Contractor
affected stakeholders: Public
confidence: 0.78
constraint type: ethical
flexibility: hard
mitigation strategies: Delay submission until the product meets professional standards
mitigation strategies: Disclose known deficiencies in a written transmittal accompanying the submission
mitigation strategies: Notify the client and request a schedule extension before the deadline
text references: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
violation impact: Client and approving authorities rely on a deficient product, leading to unbuildable contracts, cost overruns, and potential public safety risks.
discovered in case: 85
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T16:51:16.118939+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
comment: Ethical constraint requiring that an engineer who submits a work product known to be materially incomplete must disclose that incompleteness to the client, approving authorities, and other relying parties before or at the time of submission, so that those parties can make informed decisions about whether to accept, approve, or act upon the deliverable.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T16:51:16.118939+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Incomplete Deliverable Submitted State
type: Class
action constraints: Professional must not allow project to proceed to bid or construction on an incomplete deliverable without disclosure
action constraints: Professional must not misrepresent completeness of sealed documents
activation conditions: Incompleteness is not disclosed to client or approving authority at time of submission
activation conditions: Professional submits drawings, specifications, or other deliverable known to be incomplete
confidence: 0.88
obligation activation: Duty to correct deficiencies before project proceeds
obligation activation: Duty to disclose incompleteness to client and approving authority
obligation activation: Duty to notify affected parties of potential cost and schedule impacts
persistence type: inertial
principle transformation: Transforms general honesty and completeness principles into concrete obligations to disclose known deficiencies in sealed professional documents before those documents are relied upon by contractors, agencies, or funding bodies.
state category: information
termination conditions: Corrected and complete deliverable is submitted
termination conditions: Deficiencies are disclosed and acknowledged by all affected parties
termination conditions: Project is cancelled or scope is formally revised
text references: Engineer A generally agrees with Hi-Lo's characterization
text references: certain parts of the project are unbuildable without major changes
text references: did not inform anyone as to their incompleteness
text references: much of the design detail is lacking in the drawings and specifications
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:46:12.006396+00:00
first discovered in case: 85
match confidence: 0.78
match reasoning: Deficient Work Product Submitted State captures the concept of a submitted work product containing errors, omissions, or deficiencies failing professional standards. The present state is a variant that emphasizes the professional's contemporaneous knowledge of incompleteness and the deliberate non-disclosure, which adds a distinct epistemic and honesty dimension not fully captured by the existing class. A medium-confidence match is appropriate; the new class is warranted to capture the non-disclosure element.
matched ontology class: Deficient Work Product Submitted State
matched ontology label: Deficient Work Product Submitted State
matches existing: true
source text: much of the design detail is lacking in the drawings and specifications
comment: State in which a professional has delivered a work product that is known by the professional to be materially incomplete, lacking design detail or information necessary for the work to be constructed or implemented, and in which the professional has not disclosed the incompleteness to the client, approving authority, or other affected parties at the time of delivery.
subclass of: InformationState
scope note: [DeficientWorkProductSubmittedState] State in which a professional has submitted a work product to a client that contains errors, omissions, or deficiencies that fail to meet professional or regulatory standards, creating obligations to correct the deficiencies, notify affected parties, and assess whether safety or compliance risks have been introduced.
generated at time: 2026-06-04T16:46:12.006396+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Incomplete Expert Report State
type: Class
action constraints: Professional must not issue conclusions based on selectively presented data
action constraints: Professional must not omit findings that contradict the primary conclusion
activation conditions: Expert or reviewing professional submits a report
activation conditions: Omitted findings would materially affect the conclusions presented
activation conditions: Report omits material findings known to the professional
confidence: 0.88
obligation activation: Duty to disclose equipment failures or test anomalies
obligation activation: Duty to present complete and objective findings
obligation activation: Duty to report contradictory data that bears on conclusions
persistence type: inertial
principle transformation: Transforms general honesty and objectivity principles into specific obligations to disclose all material technical findings, including those that undercut the professional's own conclusions.
state category: information
termination conditions: Report withdrawn and replaced with complete analysis
termination conditions: Supplemental report issued correcting omissions
text references: Engineer B did not report that the dynamic test equipment had failed
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:51.674939+00:00
first discovered in case: 71
match confidence: 0.87
match reasoning: The previously extracted class Incomplete Professional Report State captures the concept of a professional report that omits material information, selectively presents data, or fails to investigate relevant factors. This case instantiates that class: Engineer B's report omitted the pile driving refusal data and the equipment failure, both of which were material to the conclusions.
matched ontology class: Incomplete Professional Report State
matched ontology label: Incomplete Professional Report State
matches existing: true
source text: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal
comment: State in which a professional retained as an expert or reviewer has produced a report that omits material technical findings, contradictory data, or equipment failures that would be necessary for the report to present a complete and accurate professional opinion, creating obligations of completeness, objectivity, and truthfulness in professional communications.
subclass of: InformationState
scope note: [IncompleteProfessionalReportState] State in which a professional has produced or submitted a report or analysis that omits material information, selectively presents data, or fails to investigate relevant factors, resulting in a misleading or incomplete professional work product that violates duties of objectivity, completeness, and truthfulness.
generated at time: 2026-06-04T14:26:51.674939+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Independent Geotechnical Observer
type: Class
confidence: 0.82
role category: provider_client
text references: An independent geotechnical consultant was retained by Engineer A to observe the test
text references: In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:11.026228+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: An independent geotechnical consultant was retained by Engineer A to observe the test
comment: A professional engineering or geotechnical consulting role in which the practitioner is retained by one party to observe and monitor testing or construction activities conducted by another party, report on procedural irregularities or equipment failures, and provide independent technical testimony on the validity of test conditions and results.
subclass of: ProviderClientRole
generated at time: 2026-06-04T14:26:11.026228+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Intellectual Honesty in Authorship Principle
type: Class
abstract nature: The boundary between permissible tool use and misrepresentation of authorship is context-dependent and evolving, requiring engineers to interpret what honest representation of AI-assisted work demands in their professional context.
confidence: 0.86
derived obligations: Acknowledge limitations of AI-generated content in professional submittals
derived obligations: Avoid presenting AI-generated text as independently authored professional writing
derived obligations: Disclose AI authorship of report sections to clients
extensional examples: Client observing that a report reads as if written by two different authors due to inconsistent AI and human writing styles
extensional examples: Engineer making minor wording adjustments to AI text and presenting the work as independently authored
extensional examples: Engineer submitting AI-drafted report without indicating AI contribution
operationalization: Requires engineers to disclose AI contributions to work products, to distinguish between AI-generated and independently authored content where material, and to avoid presenting AI-generated text as original professional writing.
potential conflicts: AI Tool Disclosure Principle
potential conflicts: Client perception of professional capability
potential conflicts: Competitive norms around tool disclosure
principle category: professional_virtue
text references: Engineer A also made minor adjustments to some of the wording to personalize the content.
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
text references: The Client commented that the report read as if written by two different authors but was otherwise satisfactory.
value basis: Professional work products carry an implicit representation that they reflect the engineer's own analysis and judgment. Concealing AI authorship misleads clients and the public about the nature and reliability of the work.
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:03:55.305980+00:00
first discovered in case: 7
match confidence: 0.75
match reasoning: Intellectual Honesty exists in the ontology as a general principle. The AI authorship context is a specific and emergent variant that the existing class does not fully address, particularly the novel question of whether presenting AI-generated text without disclosure constitutes a failure of intellectual honesty. The match is a variant rather than a direct match, warranting a new class that specializes the existing principle for AI authorship contexts.
matched ontology class: Intellectual Honesty
matched ontology label: Intellectual Honesty
matches existing: true
source text: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
comment: Integrity principle requiring engineers to accurately represent the authorship and intellectual origin of professional work products, including disclosure when substantial portions of a work were generated by AI tools or other non-engineer sources, so that recipients can assess the work's provenance.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-03T14:03:55.305980+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Investigative Completeness Obligation
type: Class
confidence: 0.93
derived from principle: Investigative Completeness Principle
enforcement level: mandatory
monitoring criteria: Documentation showing that available records, witnesses, and data sources were consulted before conclusions were drawn
nspe reference: II.2.a
obligation type: ethical
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Opposing party
stakeholders affected: Professional licensing board
text references: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
text references: No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
violation consequences: Professional discipline; findings may be discredited; potential liability for negligent investigation
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:31:15.630641+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing obligation class in the ontology corresponds to this duty. The ontology list is empty, so this is a new class.
matches existing: false
source text: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
comment: Duty of an engineer retained to investigate or evaluate technical work to pursue all reasonable lines of inquiry, consult available witnesses and records, and avoid reaching conclusions based on incomplete or selectively gathered evidence.
subclass of: EthicalObligation
generated at time: 2026-06-04T14:31:15.630641+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Investigative Completeness Principle
type: Class
abstract nature: Open-textured standard requiring judgment about what sources of evidence are reasonably available and material to the conclusions being drawn.
confidence: 0.88
derived obligations: Consult available on-site personnel before finalizing conclusions
derived obligations: Disclose in the report any material sources that were not consulted and why
derived obligations: Review existing field records relevant to the technical question
extensional examples: Engineer B's failure to consult Engineer A's on-site representatives or review pile driving records before concluding 19 piles were deficient
operationalization: Requires investigators to identify available witnesses and records, make reasonable efforts to obtain them, and disclose when material sources were not consulted.
potential conflicts: Client-defined investigation boundaries
potential conflicts: Contractual scope limitations
principle category: professional_virtue
text references: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
text references: No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
value basis: Professional conclusions that affect legal rights, public safety, and professional reputations must rest on a reasonably complete evidentiary foundation.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:30:07.628947+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
comment: Professional principle requiring engineers retained to investigate or evaluate technical work to pursue all reasonably available sources of evidence, including field records, on-site personnel, contractors, and workers, before reaching and reporting conclusions. An investigation that ignores available corroborating or contradicting evidence is professionally deficient regardless of the scope of work as contractually defined.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T14:30:07.628947+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Investigative Inquiry Capability
type: Class
capability category: reasoning
confidence: 0.92
domain specificity: Technical investigations in civil and geotechnical engineering contexts
enables actions: Consult available witnesses and on-site representatives
enables actions: Identify and pursue alternative explanations for observed data
enables actions: Review historical records relevant to the investigation
enables actions: Verify or refute working hypotheses through independent inquiry
required for obligations: Investigative Completeness Obligation
skill level: advanced
text references: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
text references: No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class covers the competency of pursuing all reasonable lines of inquiry in a technical investigation, including witness consultation and record review.
matches existing: false
source text: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
comment: Ability to identify and pursue all reasonable lines of inquiry in a technical investigation, including consulting witnesses, reviewing records, and following up on anomalies before reaching conclusions.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Investigative Scope Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Opposing parties
affected stakeholders: Public
affected stakeholders: Retained engineer
confidence: 0.9
constraint type: legal
flexibility: soft
mitigation strategies: Decline engagement if scope prevents adequate investigation
mitigation strategies: Disclose scope limitations explicitly in the report
mitigation strategies: Seek scope expansion when material evidence falls outside defined boundaries
text references: No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
text references: We didn't look at the pile driving records because it was not in our scope of work.
violation impact: Incomplete findings, misleading conclusions, professional discipline, litigation exposure
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology addresses the tension between a contractually defined scope of work and the professional duty to pursue material evidence. This is a distinct constraint type from the obligation-side Scope Limitation Disclosure Obligation already extracted.
matches existing: false
source text: We didn't look at the pile driving records because it was not in our scope of work.
comment: Limitation on the breadth of an investigation arising from a contractually defined scope of work, which may restrict but does not excuse omission of material evidence bearing on professional conclusions.
subclass of: DefeasibleConstraint
subclass of: LegalConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Joint Professional Obligation State
type: Class
action constraints: Actions need not be identical but must be coordinated
action constraints: Neither professional may unilaterally abandon the shared obligation without satisfying their individual duties
activation conditions: A client or governing body has received and acted upon the joint presentation
activation conditions: The joint presentation creates shared accountability for follow-through on those findings
activation conditions: Two or more professionals have jointly presented findings or recommendations
confidence: 0.8
obligation activation: Duty of each professional to act in concert with co-presenting colleagues on follow-up obligations
obligation activation: Duty to coordinate formal presentations to authorities
obligation activation: Individual accountability for each professional's own role-specific actions within the shared obligation
persistence type: inertial
principle transformation: Transforms individual professional duties into a coordinated shared obligation structure, requiring that professionals who have jointly committed to findings act in concert on follow-up even though their specific actions may differ.
state category: relationship
termination conditions: Both professionals have individually satisfied their reporting and notification obligations
termination conditions: The professional relationship between the co-presenting engineers concludes
termination conditions: The underlying safety concern is resolved
text references: Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
text references: It is important to note that Engineers A and B have presented the findings and recommendations jointly
discovered in case: 76
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T11:18:53.656605+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Engineers A and B have presented the findings and recommendations jointly and, as such, their actions should be in concert, although not identical.
comment: State in which two or more professionals have jointly presented findings and recommendations to a client or governing body, creating a condition in which their subsequent ethical obligations are shared and must be pursued in concert, even though the specific actions each professional takes may differ based on their individual roles and relationships.
subclass of: RelationshipState
generated at time: 2026-06-05T11:18:53.656605+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Joint Recommendation Coordination Capability
type: Class
capability category: communication
confidence: 0.82
domain specificity: Professional engineering practice in multi-engineer advisory contexts
enables actions: Coordinate technical findings between co-presenting engineers
enables actions: Document shared professional conclusions for subsequent escalation
enables actions: Present unified recommendations to a governing body
required for obligations: Coordinated Escalation Obligation
required for obligations: Engineers A B Coordinated Escalation
required for obligations: Joint Recommendation Documentation Obligation
skill level: advanced
text references: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:25:14.530972+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.
comment: Capability of two or more engineers who have independently reached convergent professional conclusions to coordinate the presentation of those conclusions to a client or governing body as a unified recommendation, ensuring that the joint presentation accurately reflects the shared technical basis, that neither engineer's findings are misrepresented, and that the coordinated position is documented so that subsequent escalation steps can be taken jointly if the recommendation is overridden.
subclass of: Capability
generated at time: 2026-06-05T11:25:14.530972+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Joint Recommendation Documentation Obligation
type: Class
confidence: 0.78
derived from principle: Complete Reporting Principle
enforcement level: prima_facie
monitoring criteria: Written record of joint recommendations including technical findings, required improvements, and timeline submitted to the client before or at the time of the client decision
nspe reference: II.3.b, III.2.b
obligation type: disclosure
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.
text references: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline.
violation consequences: Loss of evidentiary basis for regulatory escalation; weakened professional accountability record
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:23:42.907966+00:00
first discovered in case: 76
match confidence: 0.75
match reasoning: The joint documentation duty is a contextual variant of the existing Complete Technical Reporting Obligation, applied to the specific situation where two engineers jointly present findings and the documentation serves as the evidentiary basis for potential regulatory escalation. The core concept of complete and documented reporting is already captured.
matched ontology class: Complete Technical Reporting Obligation
matched ontology label: Complete Technical Reporting Obligation
matches existing: true
source text: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline.
comment: Duty of engineers who jointly develop and present professional recommendations to a client or governing body to ensure that those recommendations, including the technical basis, timeline requirements, and safety rationale, are documented in writing so that the record is available for regulatory escalation if the client overrides the recommendations.
subclass of: DisclosureObligation
scope note: [CompleteTechnicalReportingObligation] Duty of an engineer preparing a technical report to include all relevant and pertinent technical information, including facts that may complicate or contradict the primary conclusions, so that the report supports informed review and interpretation by others.
generated at time: 2026-06-05T11:23:42.907966+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Known Design Defect Present State
type: Class
action constraints: Concealment or obstruction of review is prohibited
action constraints: Non-cooperation with peer review is ethically impermissible when known defects are present
activation conditions: Design defects in prior work have been identified and confirmed
activation conditions: The professional responsible for the defective design is aware of or informed of the defects
confidence: 0.88
obligation activation: Heightened obligation to cooperate with peer review
obligation activation: Obligation to acknowledge errors and take responsibility
obligation activation: Obligation to act in the client's best interests by supporting corrective review
persistence type: inertial
principle transformation: Transforms baseline professional responsibility into urgent duties of transparency, cooperation, and correction when prior work is known to be defective.
state category: risk
termination conditions: Defects are corrected to applicable standards
termination conditions: Design is replaced or withdrawn from use
text references: The known design defects in the first tower simply makes each of those requirements more urgent
discovered in case: 15
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-02T19:53:12.877625+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: The known design defects in the first tower simply makes each of those requirements more urgent
comment: State in which a professional is aware of confirmed defects in an existing design, elevating the urgency of safety obligations, cooperation duties, and corrective action requirements beyond what would apply in a routine review context.
subclass of: RiskState
generated at time: 2026-06-02T19:53:12.877625+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Litigation Expert Engineer
type: Class
confidence: 0.88
role category: provider_client
text references: Engineer B did not report that the dynamic test equipment had failed
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal
text references: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations
text references: the municipality retained Engineer B to supervise the driving of several test piles
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:11.026228+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: the municipality retained Engineer B to supervise the driving of several test piles
comment: A licensed professional engineering role in which the practitioner is retained by one party in a legal or mediation proceeding to conduct independent technical investigations, prepare findings reports, and provide expert testimony or written opinions on engineering matters in dispute, bearing professional obligations of objectivity, completeness, and honest disclosure of all material facts including those that may be unfavorable to the retaining party.
subclass of: EngineerRole
subclass of: ProviderClientRole
generated at time: 2026-06-04T14:26:11.026228+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Litigation Neutrality Principle
type: Class
abstract nature: Requires balancing the legitimate role of advocacy in adversarial proceedings against the engineer's independent professional obligation to render technically honest opinions.
confidence: 0.86
derived obligations: Apply all relevant analytical methods, not only those supporting the retaining party's position
derived obligations: Decline to omit material technical findings because they are unhelpful to the retaining party
derived obligations: Disclose evidence that contradicts the conclusions being offered
extensional examples: Engineer B's selective reliance on one analytical method while omitting wave equation results that contradicted the conclusion favoring the retaining municipality
operationalization: Requires expert engineers to consider and disclose all material evidence, apply all relevant analytical methods, and present conclusions that reflect the full technical picture rather than only the evidence supporting the retaining party.
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Loyalty to retaining client
principle category: relational
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
text references: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
value basis: Courts, mediators, and opposing parties rely on expert engineers to provide technically honest analysis. Advocacy-shaped expert opinions corrupt the fact-finding process and undermine public trust in the profession.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:30:07.628947+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
comment: Professional principle requiring engineers retained as expert witnesses or technical investigators in litigation or mediation to render opinions based solely on technical analysis and available evidence, without shaping findings to favor the retaining party's legal position. The engineer's duty to provide objective technical analysis is not displaced by the adversarial context of the engagement.
subclass of: RelationalPrinciple
generated at time: 2026-06-04T14:30:07.628947+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Local Public Agency Client
type: Class
confidence: 0.87
role category: provider_client
text references: Engineer A responds to an RFP from a small local public agency to build a new dam
text references: The local public agency does not have the in-house technical resources to review the drawings and specifications
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:46:00.156208+00:00
first discovered in case: 85
match confidence: 0.8
match reasoning: Municipal Client from the previously extracted classes covers a government or municipal entity that commissions professional engineering services and lacks professional engineering licensure. Local Public Agency Client is a close specialization of that concept, warranting a medium-confidence match.
matched ontology class: Municipal Client
matched ontology label: Municipal Client
matches existing: true
source text: Engineer A responds to an RFP from a small local public agency to build a new dam
comment: A small local government or public agency that commissions professional engineering services for a publicly funded infrastructure project, acting as the primary client and decision-maker but lacking in-house technical resources to review or evaluate the engineering work product delivered.
subclass of: ProviderClientRole
subclass of: RegulatoryAuthorityRole
scope note: [MunicipalClient] A government or municipal entity that commissions professional engineering or construction services for public infrastructure projects, acting as the primary client and decision-maker but without professional engineering licensure.
generated at time: 2026-06-04T16:46:00.156208+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Manufacturing Client
type: Class
confidence: 0.85
role category: provider_client
text references: XYZ Corporation was advised by a State Pollution Control Authority of a need to apply for a permit to discharge manufacturing waste
text references: XYZ Corporation would present data to show their discharge meets minimum standards
text references: XYZ instructed Engineer Doe not to complete a written report and paid Engineer Doe the agreed upon fee
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T02:17:07.048701+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: XYZ Corporation was advised by a State Pollution Control Authority of a need to apply for a permit to discharge manufacturing waste
comment: A private manufacturing corporation that commissions professional engineering consulting services related to environmental discharge or compliance matters, acting as the primary client but whose instructions to suppress or withhold technical findings may conflict with the engineer's public welfare obligations.
subclass of: ClientRole
subclass of: ProviderClientRole
generated at time: 2026-06-05T02:17:07.048701+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Mentor Engineer
type: Class
confidence: 0.85
role category: professional_peer
text references: Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts
text references: Engineer B recently retired and was no longer available to Engineer A in a work capacity
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T13:59:26.869728+00:00
first discovered in case: 7
match confidence: 0.78
match reasoning: Mentor Engineer is a specialization of Professional Peer Role. The ontology lists Professional Peer Role as covering collegial relationships with mentoring and review obligations, which directly describes Engineer B's function. A distinct leaf class is warranted because the mentoring and supervisory quality-assurance dimension is more specific than generic peer review.
matched ontology class: ProfessionalPeerRole
matched ontology label: Professional Peer Role
matches existing: true
source text: Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts
comment: A senior professional engineering role in which the practitioner provides guidance, quality assurance review, and technical mentorship to a less experienced engineer, shaping that engineer's professional development and serving as a check on technical work product.
subclass of: EngineerRole
subclass of: ProfessionalPeerRole
scope note: [ProfessionalPeerRole] Collegial relationship with mentoring and review obligations
generated at time: 2026-06-03T13:59:26.869728+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Mentor Unavailable State
type: Class
action constraints: Should not proceed with work requiring mentorship support without establishing an alternative
action constraints: Should not represent work quality as equivalent to prior mentored work without adequate substitute review
activation conditions: Mentor or supervisor retires, resigns, or otherwise becomes unavailable
activation conditions: Professional had previously depended on that mentor for review or guidance
confidence: 0.85
obligation activation: Obligation to disclose competence limitations to clients if work quality may be affected
obligation activation: Obligation to identify alternative quality assurance mechanisms
obligation activation: Obligation to seek additional support before undertaking work that previously required mentorship
persistence type: inertial
principle transformation: Transforms general competence obligations into specific duties to secure alternative quality assurance before undertaking work previously dependent on mentorship.
state category: competence
termination conditions: A replacement mentor or supervisor is identified
termination conditions: Alternative quality assurance arrangement is established
termination conditions: Professional develops independent competence in the affected area
text references: Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts
text references: Engineer B recently retired and was no longer available to Engineer A in a work capacity
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T14:00:13.061399+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer B recently retired and was no longer available to Engineer A in a work capacity
comment: State in which a professional has lost access to a previously relied-upon mentor or supervisor whose guidance was integral to quality assurance and competence support, creating a gap in the professional's support structure and potentially affecting the quality and reliability of their work product.
subclass of: CompetenceState
generated at time: 2026-06-03T14:00:13.061399+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Mentorship Continuity Principle
type: Class
abstract nature: The obligation to secure alternative oversight is contextually defined by the complexity of the work, the engineer's experience level, and the availability of substitute review mechanisms.
confidence: 0.82
derived obligations: Decline work scope that exceeds independent competence without substitute review
derived obligations: Identify quality assurance gaps created by loss of mentor or supervisor
derived obligations: Seek alternative peer review when primary oversight is unavailable
extensional examples: Engineer accepting project scope beyond their independent competence without arranging substitute oversight
extensional examples: Engineer proceeding without mentor review by substituting AI tools without equivalent verification
extensional examples: Junior engineer failing to seek peer review after supervisor departure
operationalization: Requires engineers to identify when loss of mentorship creates a competence or quality gap, to seek alternative peer review or supervision, and to decline or restructure work scope when adequate oversight cannot be arranged.
potential conflicts: Client expectations and contractual commitments
potential conflicts: Professional Competence
potential conflicts: Time and resource constraints
principle category: professional_virtue
text references: Faced with the need to deliver both the report and the engineering design documents without the review by and mentorship from Engineer B, Engineer A opted to use open-sourced artificial intelligence (AI) software
text references: Previously, Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts. But Engineer B recently retired and was no longer available to Engineer A in a work capacity.
value basis: Professional quality assurance depends on review structures that catch errors individual practitioners may miss. When those structures are disrupted, the engineer bears responsibility for maintaining equivalent safeguards.
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:03:55.305980+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Previously, Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts. But Engineer B recently retired and was no longer available to Engineer A in a work capacity.
comment: Professional virtue principle requiring engineers to maintain the quality and integrity of their work when supervisory or mentorship relationships are disrupted, by seeking alternative review mechanisms rather than proceeding without adequate oversight.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-03T14:03:55.305980+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Mentorship Gap Adaptation Capability
type: Class
capability category: learning
confidence: 0.87
domain specificity: Professional engineering practice in contexts where mentorship or supervisory review has been a component of quality assurance
enables actions: Evaluate alternative review and oversight mechanisms
enables actions: Identify quality assurance gaps created by mentor unavailability
enables actions: Implement substitute quality assurance processes
enables actions: Recognize limits of one's own competence without mentorship support
required for obligations: Mentorship Gap Competence Obligation
skill level: intermediate
text references: Engineer A is known for their strong technical expertise but is, personally, less confident in their technical writing. Previously, Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts. But Engineer B recently retired and was no longer available to Engineer A in a work capacity.
text references: Faced with the need to deliver both the report and the engineering design documents without the review by and mentorship from Engineer B, Engineer A opted to use open-sourced artificial intelligence (AI) software
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:21.353968+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A is known for their strong technical expertise but is, personally, less confident in their technical writing. Previously, Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts. But Engineer B recently retired and was no longer available to Engineer A in a work capacity.
comment: Capability to recognize when the loss of a mentor or supervisor creates a quality assurance gap in one's professional practice, and to identify and implement adequate alternative mechanisms to maintain professional competence and output quality.
subclass of: Capability
generated at time: 2026-06-03T14:06:21.353968+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Mentorship Gap Competence Obligation
type: Class
confidence: 0.85
derived from principle: Mentorship Continuity Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer identified and implemented a quality assurance process adequate to substitute for lost mentorship oversight
nspe reference: II.2, II.2.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Professional licensing board
text references: Faced with the need to deliver both the report and the engineering design documents without the review by and mentorship from Engineer B, Engineer A opted to use open-sourced artificial intelligence (AI) software
text references: Previously, Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts. But Engineer B recently retired and was no longer available to Engineer A in a work capacity.
violation consequences: Submission of deficient work products; public safety risk; professional discipline for practicing beyond competence
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:05:12.288818+00:00
first discovered in case: 7
match confidence: 0.75
match reasoning: This obligation is a contextual specialization of the existing Competence Obligation, addressing the specific situation where a quality assurance mentor becomes unavailable. The existing class covers the general duty to practice within competence but does not address the specific duty to maintain quality assurance processes when supervisory support is lost. A new class is warranted to capture this distinct scenario type.
matched ontology class: CompetenceObligation
matched ontology label: Competence Obligation
matches existing: true
source text: Previously, Engineer A had relied on guidance and quality assurance reviews by their mentor and supervisor, Engineer B, to refine report drafts. But Engineer B recently retired and was no longer available to Engineer A in a work capacity.
comment: Duty of an engineer who loses access to a mentor or supervisor providing quality assurance review to identify and implement alternative means of ensuring the quality and accuracy of their professional work products before submission, rather than substituting unverified automated tools for the lost oversight function.
subclass of: CompetenceObligation
scope note: [CompetenceObligation] Requirement to perform services only in areas of competence (NSPE II.2)
generated at time: 2026-06-03T14:05:12.288818+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Methodological Consistency Obligation
type: Class
confidence: 0.91
derived from principle: Methodological Consistency Principle
enforcement level: mandatory
monitoring criteria: Test protocols document how original conditions were replicated and identify any deviations with justification
nspe reference: II.2.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: Court or mediating body
stakeholders affected: General public
stakeholders affected: Opposing party
text references: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.
violation consequences: Test results may be invalidated; professional discipline; findings may be excluded from proceedings
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:31:15.630641+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing obligation class in the ontology corresponds to this duty. This is a new class.
matches existing: false
source text: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
comment: Duty of an engineer conducting tests or investigations intended to replicate prior work to reproduce the original conditions as closely as reasonably practicable, and to disclose any deviations that could affect the comparability or validity of results.
subclass of: CompetenceObligation
generated at time: 2026-06-04T14:31:15.630641+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Methodological Consistency Principle
type: Class
abstract nature: Requires technical judgment about which conditions are material to the outcome being measured and how deviations should affect the confidence and scope of reported conclusions.
confidence: 0.85
derived obligations: Disclose all material deviations from original conditions in the test report
derived obligations: Document the conditions of the original work before designing comparison tests
derived obligations: Qualify conclusions to reflect the effect of condition differences on result validity
extensional examples: Failure to drive test piles to the same depth of penetration as original piles
extensional examples: Pre-record hammer drops that broke pile bond before blow count recording began
extensional examples: Use of a vibratory hammer in test pile driving when the original piles were not driven with a vibratory hammer
operationalization: Requires engineers to document original conditions before designing tests, replicate material conditions in the test protocol, disclose deviations in the report, and qualify conclusions where deviations may have affected results.
potential conflicts: Client timeline or cost pressures
potential conflicts: Practical constraints on test design
principle category: domain_specific
text references: After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced. In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value reported by Engineer B's tests.
text references: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
text references: The test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.
value basis: Technical conclusions about whether original work met standards are only valid if the test conditions are sufficiently similar to the original conditions to support comparison.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:30:07.628947+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
comment: Professional principle requiring engineers conducting tests or investigations to replicate, as closely as reasonably practicable, the conditions of the original work being evaluated, and to disclose and account for any material deviations from those conditions when reporting results. Conclusions drawn from tests conducted under materially different conditions must be qualified to reflect those differences.
subclass of: DomainSpecificPrinciple
generated at time: 2026-06-04T14:30:07.628947+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Methodological Replication Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Opposing parties
affected stakeholders: Retained engineer
affected stakeholders: Tribunal
confidence: 0.88
constraint type: procedural
flexibility: soft
mitigation strategies: Disclose all deviations and their potential effect on results
mitigation strategies: Document original conditions before designing the test program
mitigation strategies: Replicate hammer type, penetration depth, and setup procedures
text references: After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced.
text references: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
text references: The test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.
violation impact: Invalid test comparisons, misleading conclusions, professional discipline, unjust dispute outcomes
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology addresses the procedural requirement to replicate original test conditions. The obligation-side Methodological Consistency Obligation is a duty; this is the bounding constraint on permissible test design.
matches existing: false
source text: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
comment: Requirement that an engineer conducting tests intended to replicate prior work reproduce the original conditions as closely as practicable, and disclose any deviations that could affect the validity of comparisons drawn between the test results and the original work.
subclass of: DefeasibleConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Municipal Infrastructure Design Engineer
type: Class
confidence: 0.85
role category: provider_client
text references: Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:11.026228+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles
comment: A licensed professional engineering role in which the practitioner is retained by a municipality to design infrastructure elements such as docks, foundations, or similar civil works, bearing primary professional accountability for the technical adequacy of the design and the accuracy of supporting engineering judgments.
subclass of: EngineerRole
subclass of: ProviderClientRole
generated at time: 2026-06-04T14:26:11.026228+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

NSPE Code Provision
type: Class
authority source: National Society of Professional Engineers
confidence: 0.95
extensional function: Provides a precise, authoritative rule that directly governs engineer conduct in a defined situation, bridging the general code to specific fact patterns.
resource category: professional_code
text references: Professional Obligation III.7.a. is very clear: 'Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated.'
usage context: Ethical compliance analysis
usage context: Peer review obligation determination
discovered in case: 8
discovered in case: 15
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-02T19:52:49.379118+00:00
first discovered in case: 15
match confidence: 0.95
match reasoning: A numbered provision of the NSPE Code is a citable artifact within the Professional Code category. It is a subtype of Professional Code rather than a genuinely new class.
matched ontology class: ProfessionalCode
matched ontology label: Professional Code
matches existing: true
source text: Professional Obligation III.7.a. is very clear: 'Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated.'
comment: A numbered, individually citable provision within the NSPE Code of Ethics for Engineers, such as a specific Professional Obligation or Fundamental Canon, that states a binding rule of professional conduct.
subclass of: ProfessionalCode
scope note: [ProfessionalCode] Distillations of collective experience that guide and justify actions
generated at time: 2026-06-02T19:52:49.379118+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

No Public Safety Nexus State
type: Class
action constraints: Engineer cannot invoke mandatory safety reporting frameworks
action constraints: Engineer may disclose but is not required to do so
activation conditions: Professional misconduct or substandard work is identified
activation conditions: The identified issue does not involve a direct threat to public health or safety
activation conditions: The issue relates to financial waste, unsatisfactory plans, or contractual deficiency
confidence: 0.82
obligation activation: Discretionary right to disclose as matter of personal conscience
obligation activation: No mandatory whistleblowing obligation under the NSPE Code
obligation activation: Potential employment risk if disclosure is pursued
persistence type: inertial
principle transformation: Transforms the general duty of honesty and public welfare into a discretionary right rather than a mandatory obligation, because the absence of a public safety nexus removes the override condition that would compel disclosure.
state category: information
termination conditions: A public safety dimension is identified, elevating the state
termination conditions: The professional decides to disclose or not disclose
termination conditions: The underlying issue is resolved
text references: the case did not involve a danger to the public health or safety, but related to a claim of unsatisfactory plans and the unjustified expenditure of public funds
text references: the ethical duty or right of the engineer becomes a matter of personal conscience
text references: the issue does not allege a danger to public health or safety, but is premised upon a claim of unsatisfactory plans and the unjustified expenditure of public funds
discovered in case: 85
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T16:47:21.871867+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: the case did not involve a danger to the public health or safety, but related to a claim of unsatisfactory plans and the unjustified expenditure of public funds
comment: State in which a professional's conduct involves potential ethical violations related to public funds, unsatisfactory plans, or contractual performance, but the conduct does not rise to the level of a danger to public health or safety, placing the matter in an intermediate ethical zone where disclosure obligations are discretionary rather than mandatory and the engineer's duty to act becomes a matter of personal conscience rather than a code-mandated requirement.
subclass of: InformationState
generated at time: 2026-06-04T16:47:21.871867+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

No Safety Nexus Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Funding Agencies
affected stakeholders: Public
confidence: 0.78
constraint type: ethical
flexibility: soft
mitigation strategies: Clearly distinguish whether the concern involves public safety before determining disclosure obligations
mitigation strategies: Document the basis for concluding no safety nexus exists
mitigation strategies: Fulfill affirmative obligations of plan completeness and non-deception regardless of safety nexus
text references: The Board noted that the case did not involve a danger to the public health or safety, but related to a claim of unsatisfactory plans and the unjustified expenditure of public funds
text references: the Board indicated that it could dismiss the case on the narrow ground that the NSPE Code does not apply to a claim not involving public health and safety, but that was too narrow a reading of the ethical duties of engineers
text references: the issue does not allege a danger to public health or safety, but is premised upon a claim of unsatisfactory plans and the unjustified expenditure of public funds
violation impact: Reduced mandatory disclosure obligation; engineer retains discretion over external reporting but remains bound by affirmative obligations of completeness and non-deception
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:56:15.795068+00:00
first discovered in case: 85
match confidence: 0.72
match reasoning: The concept that disclosure obligations are reduced but not eliminated when no safety nexus exists is a form of defeasible constraint, where the default disclosure rule is relaxed under the specified condition of no public safety danger. However, the specific application to the safety-nexus threshold for mandatory reporting is not captured by any existing named class, making this a variant of Defeasible Constraint rather than a precise match.
matched ontology class: DefeasibleConstraint
matched ontology label: Defeasible Constraint
matches existing: true
source text: The Board noted that the case did not involve a danger to the public health or safety, but related to a claim of unsatisfactory plans and the unjustified expenditure of public funds
comment: Constraint arising when an engineer's ethical violation involves unsatisfactory professional work or unjustified expenditure of public funds but does not involve a danger to public health or safety. In such cases, the mandatory disclosure and escalation obligations that attach to safety-threatening conduct do not apply with the same force, and the engineer's duty to report beyond the immediate professional relationship is reduced to a matter of conscience rather than ethical requirement.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [DefeasibleConstraint] Constraints that admit justified exceptions under specified conditions (Ganascia 2007)
generated at time: 2026-06-04T16:56:15.795068+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Non-Engineer Administrator
type: Class
confidence: 0.78
role category: provider_client
text references: City Administrator is not a licensed professional engineer
text references: City B's City Administrator asked Engineer A for a recommendation
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:41:03.751066+00:00
first discovered in case: 14
match confidence: 0.75
match reasoning: The City Administrator functions as the client-side representative receiving professional engineering advice. This is a specialization of the Client Role, with the distinguishing attribute of lacking engineering licensure, which is ethically significant because it increases the engineer's duty of candor and completeness.
matched ontology class: ClientRole
matched ontology label: Client Role
matches existing: true
source text: City Administrator is not a licensed professional engineer
comment: A municipal or organizational administrator who lacks professional engineering licensure and relies on licensed engineers for technical recommendations, acting as the client-side decision-maker and primary recipient of professional engineering advice.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [ClientRole] Party that commissions the project work. This is the occupational archetype. The duty relationship is carried separately by :ProviderClientRole.
generated at time: 2026-06-04T08:41:03.751066+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Non-Engineer Client Communication Capability
type: Class
capability category: communication
confidence: 0.78
domain specificity: Engineering advisory services provided to municipal administrators or other non-engineer clients making procurement or delivery method decisions
enables actions: Ensure completeness of information provided to non-technical decision-makers
enables actions: Present technical options in accessible terms
enables actions: Recognize client's reliance on advisor due to lack of licensure
required for obligations: Advisory Role Objectivity Obligation
required for obligations: Complete Options Advisory Obligation
skill level: intermediate
text references: City Administrator is not a licensed professional engineer
text references: City B's City Administrator asked Engineer A for a recommendation on project delivery methods
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:39.966147+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: City Administrator is not a licensed professional engineer
comment: Capability to communicate technical engineering analysis and recommendations to a non-engineer client in a manner that enables informed decision-making, including the ability to recognize when the client lacks the technical background to evaluate omissions or biases in the advice received.
subclass of: Capability
generated at time: 2026-06-04T08:45:39.966147+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Norm Awareness Capability
type: Class
capability category: norm_management
confidence: 0.87
domain specificity: Professional engineering ethics across civil and geotechnical practice
enables actions: Apply professional codes of ethics to novel situations
enables actions: Distinguish permissible advocacy from prohibited omission or misrepresentation
enables actions: Identify which professional obligations apply to a given engagement
enables actions: Recognize when conduct departs from applicable ethical standards
required for obligations: Expert Witness Neutrality Obligation
required for obligations: Faithful Agent Boundary Obligation
required for obligations: Investigative Completeness Obligation
skill level: advanced
text references: Engineer B said: 'We didn't look at the pile driving records because it was not in our scope of work.'
text references: Engineer B was obligated to present findings objectively, apply analytical methods consistently, and not omit material evidence contradicting the main conclusion.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class covers the norm management competency of recognizing and applying professional ethical obligations in engineering practice.
matches existing: false
source text: Engineer B said: 'We didn't look at the pile driving records because it was not in our scope of work.'
comment: Ability to recognize applicable professional ethical norms and standards in a given situation, including duties of completeness, neutrality, and disclosure that govern professional engineering practice.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Objective Completeness in Public Reports Principle
type: Class
abstract nature: The principle requires engineers to exercise judgment about what constitutes relevant and pertinent information in a given report context, and to resist client pressure to omit inconvenient findings. The standard of completeness is context-dependent and requires assessment of what a reasonable reviewer of the report would need to know.
confidence: 0.91
derived obligations: Document in writing any material concerns communicated only verbally to clients
derived obligations: Include all relevant and pertinent information in reports submitted to public authorities
derived obligations: Refuse client instructions to omit material facts from public reports
extensional examples: BER Case 04-8: violations of federal and state laws required disclosure in report
extensional examples: BER Case 07-6: Engineer A was required to include information about threat to bird species in written report submitted to public authority, even though it was only verbally mentioned to client
extensional examples: BER Case 99-8: incomplete drawings and specifications required disclosure
operationalization: Requires engineers to include all material findings in written reports submitted to public authorities, to document verbally communicated concerns in writing when those concerns are material to the subject of a public report, and to resist client instructions to omit relevant information.
potential conflicts: Client confidentiality
potential conflicts: Faithful Agent Duty Principle
principle category: professional_virtue
text references: Engineer A was obligated under Code section II.3.a to be objective and truthful in professional reports, statements, or testimony and include all relevant and pertinent information in such reports.
text references: The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority.
text references: The key point of BER Case 07-6 is that information about the threat to the bird species is a fact of the case.
value basis: Public authorities and affected communities rely on professional reports to make decisions affecting public welfare. Selective omission of material facts from such reports corrupts the decision-making process and violates the public trust that justifies professional licensure.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:05:37.970804+00:00
first discovered in case: 8
match confidence: 0.88
match reasoning: The Report Completeness Principle already in the ontology captures the core obligation to include all relevant and pertinent information in reports and prohibit selective omission. The present principle adds the specific context of reports submitted to public authorities, but the underlying concept is the same. This is a close match to the existing class.
matched ontology class: Report Completeness Principle
matched ontology label: Report Completeness Principle
matches existing: true
source text: The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority.
comment: Professional integrity principle requiring engineers to be objective and truthful in professional reports, statements, and testimony submitted to public authorities, and to include all relevant and pertinent information in such reports. Engineers may not omit material facts from public reports even when those facts are inconvenient to the client's interests or when the client has not explicitly requested their inclusion.
subclass of: ProfessionalVirtuePrinciple
scope note: [ReportCompletenessPrinciple] Professional integrity principle requiring engineers to include all relevant and pertinent information in reports, analyses, and professional communications, prohibiting selective omission of data that would materially alter the conclusions or recommendations presented.
generated at time: 2026-06-04T10:05:37.970804+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Objective Reporting Capability
type: Class
capability category: reasoning
confidence: 0.93
domain specificity: Expert witness and litigation support roles in engineering
enables actions: Apply analytical methods consistently across all data
enables actions: Avoid selective presentation of evidence favoring one party
enables actions: Identify and report findings that cut against the retaining party's position
enables actions: Maintain neutrality when retained as an expert witness or technical investigator
required for obligations: Contradictory Evidence Disclosure Obligation
required for obligations: Expert Witness Neutrality Obligation
skill level: advanced
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
text references: Engineer B was obligated to present findings objectively, apply analytical methods consistently, and not omit material evidence contradicting the main conclusion.
discovered in case: 8
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class covers the competency of impartial, balanced technical reporting with consistent application of analytical methods in an expert witness context.
matches existing: false
source text: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
comment: Ability to present technical findings in a balanced and impartial manner, applying analytical methods consistently and refraining from selective omission of evidence that contradicts the primary conclusion.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Observed Violation Disclosure Obligation
type: Class
confidence: 0.84
derived from principle: Fact-Based Disclosure Threshold Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer communicated the observed violation to the appropriate regulatory body after confirming the observation constituted an established fact rather than a preliminary concern.
nspe reference: II.1.a, II.1.c, II.3.b
obligation type: disclosure
stakeholders affected: Environmental resources
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
text references: he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
violation consequences: Failure to disclose a directly observed, fact-level violation of law that harms public welfare may result in professional discipline and ongoing environmental harm.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:30:01.042237+00:00
first discovered in case: 86
match confidence: 0.78
match reasoning: The existing Concern Versus Fact Disclosure Threshold Obligation addresses the distinction between a preliminary concern and an established technical fact as the trigger for mandatory disclosure under Code section II.3.b. This case presents the fact-level side of that threshold: Engineer A directly observes the violation, placing it at the level of established fact. The present class is a variant that focuses on the affirmative disclosure duty once the fact threshold is crossed, rather than the threshold determination itself. The existing class is the closest match but this obligation emphasizes the resulting duty rather than the threshold analysis.
matched ontology class: Concern Versus Fact Disclosure Threshold Obligation
matched ontology label: Concern Versus Fact Disclosure Threshold Obligation
matches existing: true
source text: he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
comment: Duty of an engineer who directly observes a client's violation of applicable law or regulation during or after a professional engagement to disclose that violation to the appropriate authority, where the observation rises to the level of established fact rather than suspicion or preliminary concern, and where the violation implicates public welfare or environmental protection.
subclass of: DisclosureObligation
scope note: [ConcernVersusFactDisclosureThresholdObligation] Duty of an engineer to distinguish between a preliminary concern that has not yet been substantiated by technical analysis and a finding that constitutes a technical fact, and to recognize that mandatory disclosure obligations under Code section II.3.b are triggered only when the engineer's assessment rises to the level of fact rather than unverified concern, while acknowledging that prudent voluntary disclosure of concerns may nonetheless be appropriate.
generated at time: 2026-06-04T17:30:01.042237+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Options Completeness Assessment Capability
type: Class
capability category: reasoning
confidence: 0.85
domain specificity: Engineering advisory services involving selection among multiple regulated or funding-constrained project delivery methods
enables actions: Assess which options are foreclosed by regulatory or funding constraints
enables actions: Enumerate all funding-agency-approved delivery methods
enables actions: Present complete option set to client
required for obligations: Complete Options Advisory Obligation
required for obligations: Funding Constraint Disclosure Obligation
skill level: intermediate
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options
text references: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:39.966147+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build
comment: Capability to identify and present all materially relevant options available to a client under applicable constraints, including the ability to recognize when omitting options from an advisory analysis would deprive the client of information needed for an informed decision.
subclass of: Capability
generated at time: 2026-06-04T08:45:39.966147+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Out-of-Competence Engineer
type: Class
confidence: 0.88
role category: provider_client
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services
text references: Engineer A, a chemical engineer with no facilities design and construction experience
discovered in case: 121
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:42:28.940730+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: Engineer A, a chemical engineer with no facilities design and construction experience
comment: A licensed professional engineering role in which the practitioner offers or undertakes engineering services in a technical domain or project type outside their established education, training, and experience, thereby creating a risk of incompetent practice and potential harm to the public.
subclass of: EngineerRole
subclass of: ProviderClientRole
generated at time: 2026-06-04T18:42:28.940730+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Override Escalation Judgment Capability
type: Class
capability category: reasoning
confidence: 0.84
domain specificity: Professional engineering ethics in public health and safety contexts
enables actions: Identify the appropriate regulatory authority for escalation
enables actions: Prepare and deliver a formal presentation of facts and findings to regulators
enables actions: Recognize when a client override creates a reportable public safety condition
required for obligations: Client Override Escalation Obligation
required for obligations: Engineer A Post-Override Regulatory Reporting
required for obligations: Engineer B Post-Override Regulatory Reporting
required for obligations: Engineers A B Post-Override Regulatory Escalation
required for obligations: Regulatory Authority Presentation Obligation
skill level: advanced
text references: Despite those recommendations, the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source.
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:25:14.530972+00:00
first discovered in case: 76
match confidence: 0.75
match reasoning: Safety Disclosure Escalation Capability covers recognition of when internal resolution has failed and escalation to regulatory authorities is required. The present capability is a variant that specifically addresses the scenario where a client or governing body override, rather than internal failure, triggers the escalation obligation. The existing class is the closest match but does not fully capture the override-specific trigger or the judgment about when an override rises to the level requiring regulatory escalation. Matching as a variant with medium confidence.
matched ontology class: Safety Disclosure Escalation Capability
matched ontology label: Safety Disclosure Escalation Capability
matches existing: true
source text: Despite those recommendations, the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source.
comment: Capability to recognize when a client or governing body has overridden a professional engineering recommendation in a manner that creates a public health or safety risk, and to judge that the override triggers an obligation to escalate the matter to an appropriate regulatory authority, including the ability to identify the correct authority, determine the appropriate form and content of the escalation, and act on that judgment even when doing so is adverse to the client relationship.
subclass of: Capability
scope note: [SafetyDisclosureEscalationCapability] Capability to recognize when internal resolution of a safety concern has failed and to escalate disclosure to appropriate regulatory authorities, including the ability to sequence escalation steps correctly by first advising the responsible engineer before notifying authorities.
generated at time: 2026-06-05T11:25:14.530972+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Overruled Engineering Judgment State
type: Class
action constraints: Client consent is not required before notifying authorities when public safety is at stake
action constraints: Notification must be formal and documented rather than merely verbal
activation conditions: Client or governing body explicitly rejects engineer's safety findings or recommendations
activation conditions: Engineer believes the overruled judgment relates to a condition endangering life or property
activation conditions: Engineer's professional judgment is subordinated to an organizational decision
confidence: 0.88
obligation activation: Duty to advise client that project will not be successful if safety is not addressed
obligation activation: Duty to further pursue the matter if formal presentations fail
obligation activation: Duty to make formal written presentation of findings and recommendations
obligation activation: Duty to notify all appropriate authorities
obligation activation: Duty to notify employer or client of danger
persistence type: inertial
principle transformation: Transforms the general duty to hold public safety paramount into a concrete obligation to escalate findings through formal channels independent of client authorization, and to continue pursuing resolution even after initial formal presentations.
state category: conflict
termination conditions: Appropriate authorities intervene and impose corrective action
termination conditions: Client or governing body adopts the engineer's recommendations
termination conditions: Engineer withdraws from the engagement
text references: If Engineers A and B believe life or property is endangered, Section II.1.a. provides that not only shall the employer or client be notified, but also all other appropriate authorities.
text references: The engineering judgments of Engineer A and Engineer B were overruled by the MWC.
text references: as this duty is a fundamental canon of the NSPE Code of Ethics, the consent of the MWC is not required
discovered in case: 76
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T11:18:53.656605+00:00
first discovered in case: 76
match confidence: 0.82
match reasoning: The existing class captures the core concept of a client overriding a safety recommendation, but the present state adds the dimension of a formal governing body vote, joint professional presentation, and the escalating obligation to pursue formal written presentations to multiple authorities when the override persists. The existing class is a close match but the present state emphasizes the post-override escalation duty more specifically. Matching at medium-high confidence as a variant.
matched ontology class: Client Override of Safety Recommendation State
matched ontology label: Client Override of Safety Recommendation State
matches existing: true
source text: The engineering judgments of Engineer A and Engineer B were overruled by the MWC.
comment: State in which a professional engineer's technical findings and safety recommendations have been formally rejected or overruled by a client, employer, or governing body, creating a condition in which the engineer's professional judgment is subordinated to an organizational decision that the engineer believes endangers life or property, triggering escalating obligations to notify authorities and pursue resolution through formal channels.
subclass of: ConflictState
scope note: [ClientOverrideofSafetyRecommendationState] State in which a client has been informed of a professional's safety recommendation and has explicitly directed the professional to proceed without implementing that recommendation, citing cost or other business constraints, creating a direct tension between the client's authority over project scope and the professional's duty to protect public safety and comply with applicable regulatory standards.
generated at time: 2026-06-05T11:18:53.656605+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Partial Analysis Disclosure State
type: Class
action constraints: Professional must not omit methodologies or alternatives that would disadvantage the professional's preferred recommendation
action constraints: Professional must not present partial analysis as if it were complete
activation conditions: Omitted options or information would be material to the client's decision
activation conditions: Professional provides comparative analysis covering only a subset of relevant options or methodologies
activation conditions: The partial analysis favors an outcome beneficial to the professional
confidence: 0.85
obligation activation: Duty to avoid self-serving omissions in professional communications
obligation activation: Duty to disclose limitations in the scope of analysis provided
obligation activation: Duty to provide complete and unbiased professional advice
persistence type: inertial
principle transformation: Transforms the general duty of objectivity and completeness into a specific obligation to disclose the scope limitations of any analysis provided and to refrain from presenting partial evaluations as comprehensive professional advice.
state category: conflict
termination conditions: Client referred to comprehensive independent resources
termination conditions: Complete analysis provided to the client
termination conditions: Professional discloses the limitation and supplements the analysis
text references: Engineer A could have provided a complete analysis of the four methodologies, with all the pros and cons
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit
text references: the conduct constituted both incomplete and self-serving information
discovered in case: 14
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T08:42:02.559155+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit
comment: State in which a professional provides an analysis or evaluation that is incomplete in scope, omitting methodologies, alternatives, or considerations that would be material to the recipient's decision, and where the omission serves or appears to serve the professional's own interests rather than the client's informational needs.
subclass of: ConflictState
generated at time: 2026-06-04T08:42:02.559155+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Confidentiality Balance
type: Class
abstract nature: Requires contextual balancing between the legitimate interests served by confidentiality in peer review and the non-waivable obligations of public safety disclosure and collegial notification.
confidence: 0.83
derived obligations: Advise client of limits of confidentiality before signing
derived obligations: Disclose safety violations despite confidentiality agreement
derived obligations: Notify original engineer of review as precondition
extensional examples: NSPE BER Case 96-8 where contractual confidentiality did not override obligation to report safety code violations to authorities
operationalization: Requires that peer review confidentiality agreements be drafted to permit safety disclosures and collegial notifications, and that reviewers understand these limits before accepting confidentiality obligations.
potential conflicts: Collegial Notification Principle
potential conflicts: Public Safety Paramount
principle category: relational
text references: In BER Case 96-8, Engineer A contractually agreed not to disclose confidential information acquired in the review... Engineer A had an obligation to immediately discuss these issues with Engineer B in order to seek clarification and resolution.
text references: Such confidentiality agreements encourage the firm being reviewed to cooperate fully, build trust, and support a collegial atmosphere.
text references: if Engineers A and B were unable to successfully resolve Engineer A's concerns, Engineer A had an obligation to first advise Engineer B that Engineer A had an obligation to inform the appropriate authorities, and then to so inform the appropriate authorities.
value basis: Recognition that confidentiality in professional review serves trust and cooperation, but cannot be used as an instrument to suppress safety concerns or circumvent professional obligations.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:58:41.183712+00:00
first discovered in case: 15
match confidence: 0.78
match reasoning: The existing Confidentiality Principle states it must be balanced against public safety obligations and legal disclosure requirements, which is precisely the balancing function this principle performs in the peer review context. The prior extraction also includes Confidentiality of Professional Review as a case-level individual. This class is a variant of the existing Confidentiality Principle applied to the peer review setting, warranting a match at the variant confidence level rather than a new class.
matched ontology class: ConfidentialityPrinciple
matched ontology label: Confidentiality Principle
matches existing: true
source text: Such confidentiality agreements encourage the firm being reviewed to cooperate fully, build trust, and support a collegial atmosphere.
comment: Relational principle governing the design and enforcement of confidentiality agreements in peer review contexts, recognizing that such agreements serve legitimate purposes of encouraging cooperation and trust but must be structured to preserve safety reporting obligations and collegial notification rights.
subclass of: RelationalPrinciple
scope note: [ConfidentialityPrinciple] Must be balanced against public safety obligations and legal disclosure requirements.
generated at time: 2026-06-02T19:58:41.183712+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Confidentiality Scope Obligation
type: Class
confidence: 0.88
derived from principle: Peer Review Confidentiality Balance
enforcement level: defeasible
monitoring criteria: Review of confidentiality agreement terms against actions taken; verification that notification to reviewed engineer was not suppressed
nspe reference: III.4
obligation type: confidentiality
stakeholders affected: Client
stakeholders affected: Design engineer under review
stakeholders affected: Peer review engineer
text references: Engineer B's confidentiality obligation to the Owner covered the contents and findings of the peer review but did not extend to concealing the existence of the review
text references: Frequently that disclosure is accompanied by an agreement that the client will require the peer reviewer to keep the results of the peer review confidential or, at the very least, the original designer will be provided with an opportunity to explain (and defend) the design decisions.
text references: Such confidentiality agreements encourage the firm being reviewed to cooperate fully, build trust, and support a collegial atmosphere.
violation consequences: Breach of contract if confidentiality is violated beyond its proper scope; ethical violation if confidentiality is used to suppress required notifications
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:59:48.608792+00:00
first discovered in case: 15
match confidence: 0.76
match reasoning: This is a bounded specialization of the Confidentiality Obligation, distinguished by the specific limit that confidentiality in peer review contexts does not override the collegial notification requirement of NSPE III.7.a. It is a defeasible variant with a defined scope boundary.
matched ontology class: ConfidentialityObligation
matched ontology label: Confidentiality Obligation
matches existing: true
source text: Frequently that disclosure is accompanied by an agreement that the client will require the peer reviewer to keep the results of the peer review confidential or, at the very least, the original designer will be provided with an opportunity to explain (and defend) the design decisions.
comment: Duty of a peer reviewer operating under a confidentiality agreement to protect the contents and findings of the review, while recognizing that the confidentiality obligation does not extend to concealing the existence of the review from the engineer whose work is being reviewed.
subclass of: ConfidentialityObligation
scope note: [ConfidentialityObligation] Duty to protect confidential information of clients or employers (NSPE III.4)
generated at time: 2026-06-02T19:59:48.608792+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Consent Refused State
type: Class
action constraints: Owner must decide whether to compel, abandon, or escalate the review
action constraints: Reviewing professional must weigh proceeding against the subject professional's objection
activation conditions: Subject professional explicitly refuses consent to the review proceeding
activation conditions: Subject professional is notified of peer review
confidence: 0.82
obligation activation: Obligation to assess whether public safety or quality concerns override the refusal
obligation activation: Obligation to consider whether prior design errors create a duty to proceed regardless of consent
obligation activation: Obligation to determine whether consent is ethically required before proceeding
persistence type: inertial
principle transformation: Transforms the general principle of professional respect into a concrete tension between respecting a peer's objection and fulfilling a duty to the public and client when prior errors are known.
state category: conflict
termination conditions: Owner cancels the peer review
termination conditions: Reviewing professional or owner resolves the dispute through a third party or authority
termination conditions: Subject professional withdraws objection and consents
text references: Engineer A objects and refused to consent to the peer review
discovered in case: 15
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-02T19:52:16.328615+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineer A objects and refused to consent to the peer review
comment: State in which the professional whose work is subject to peer review has been notified of the review but actively refuses to consent to it, creating a contested review context with unresolved professional and ethical obligations.
subclass of: ConflictState
generated at time: 2026-06-02T19:52:16.328615+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Consent Sufficiency Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Design Engineer
affected stakeholders: Peer Reviewer
confidence: 0.82
constraint type: procedural
flexibility: hard
mitigation strategies: Distinguish clearly between notification obligations and consent requirements
mitigation strategies: Document the notification and the reviewed engineer's response
mitigation strategies: Proceed with review after notification even if consent is withheld
text references: While Professional Obligation III.7.a. does not require the consent of the engineer whose work is being reviewed, it will likely be a fruitless exercise to attempt to conduct a peer review without Engineer A's cooperation
violation impact: Confusion between the mandatory notification requirement and the non-mandatory consent requirement, potentially leading to improper blocking of legitimate peer reviews or to unnecessary abandonment of safety-critical review processes.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:50.100159+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: While Professional Obligation III.7.a. does not require the consent of the engineer whose work is being reviewed, it will likely be a fruitless exercise to attempt to conduct a peer review without Engineer A's cooperation
comment: Procedural constraint establishing that while notification of the engineer whose work is under review is mandatory before a peer review commences, the formal consent of that engineer is not required by professional ethics codes. The review may proceed without consent once notification has been given, though lack of cooperation may limit the review's practical effectiveness.
subclass of: InviolableConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-02T20:00:50.100159+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Cooperation Capability
type: Class
capability category: domain_specific
confidence: 0.78
domain specificity: Professional engineering peer review and quality assurance practice
enables actions: Engage constructively with review findings
enables actions: Provide documentation to peer reviewer
enables actions: Respond to reviewer questions and requests
enables actions: Support rather than obstruct quality assurance processes
required for obligations: Error Acknowledgment Cooperation Obligation
required for obligations: Peer Review Cooperation Obligation
required for obligations: Professional Accountability Cooperation Obligation
skill level: intermediate
text references: Such confidentiality agreements encourage the firm being reviewed to cooperate fully, build trust, and support a collegial atmosphere.
text references: While Professional Obligation III.7.a. does not require the consent of the engineer whose work is being reviewed, it will likely be a fruitless exercise to attempt to conduct a peer review without Engineer A's cooperation.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:55.491400+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: While Professional Obligation III.7.a. does not require the consent of the engineer whose work is being reviewed, it will likely be a fruitless exercise to attempt to conduct a peer review without Engineer A's cooperation.
comment: Technical and interpersonal capability to participate constructively in a peer review of one's own work, including providing access to relevant documentation, responding to reviewer inquiries, and engaging collegially with the review process.
subclass of: Capability
generated at time: 2026-06-02T20:00:55.491400+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Cooperation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Design Engineer
affected stakeholders: Peer Reviewer
affected stakeholders: Public
confidence: 0.88
constraint type: ethical
flexibility: soft
mitigation strategies: Acknowledge prior errors and support corrective processes
mitigation strategies: Engage constructively with review findings
mitigation strategies: Provide full documentation and access to the reviewing engineer
text references: Engineers must take responsibility for their actions, must acknowledge their errors, must act in the best interests of their clients, and must at all times hold paramount the health, welfare, and safety of the public
text references: it will likely be a fruitless exercise to attempt to conduct a peer review without Engineer A's cooperation
text references: the Board concludes that it would be unethical for Engineer A to fail to cooperate
violation impact: Obstruction of safety-critical quality assurance, potential harm to public health and welfare, professional ethics violation, and possible disciplinary action.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:50.100159+00:00
first discovered in case: 15
match confidence: 0.75
match reasoning: This is a variant of the general Ethical Constraint class. It is more specific than the base class but does not map precisely to any of the already-extracted constraint classes, which address notification, covert review prohibition, client instruction override, safety review consent, and confidential review scope. The cooperation duty under known-defect conditions is a distinct ethical boundary not yet captured.
matched ontology class: EthicalConstraint
matched ontology label: Ethical Constraint
matches existing: true
source text: the Board concludes that it would be unethical for Engineer A to fail to cooperate
comment: Ethical constraint requiring that a design engineer whose work is subject to a legitimately initiated peer review must cooperate fully with that review, particularly when known errors in prior work elevate public safety concerns. Refusal to cooperate constitutes an ethical violation because engineers must take responsibility for their actions, acknowledge errors, act in client interests, and hold public safety paramount.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [EthicalConstraint] Professional ethical boundaries beyond legal requirements (Benzmüller et al. 2020)
generated at time: 2026-06-02T20:00:50.100159+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Cooperation Obligation
type: Class
confidence: 0.92
derived from principle: Professional Accountability
enforcement level: mandatory
monitoring criteria: Evidence of active participation, provision of design documents, and responsiveness to reviewer inquiries
nspe reference: I.1
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Peer review engineer
stakeholders affected: Public
text references: Engineers must take responsibility for their actions, must acknowledge their errors, must act in the best interests of their clients, and must at all times hold paramount the health, welfare, and safety of the public.
text references: Under the facts, the Board concludes that it would be unethical for Engineer A to fail to cooperate.
text references: it will likely be a fruitless exercise to attempt to conduct a peer review without Engineer A's cooperation
violation consequences: Finding of unethical conduct; potential loss of client relationship; risk to public safety
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:59:48.608792+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Under the facts, the Board concludes that it would be unethical for Engineer A to fail to cooperate.
comment: Duty of a design engineer to cooperate fully with a legitimate peer review of their work when the review has been properly initiated with their knowledge, particularly when prior errors in their work have been identified and public safety may be at risk.
subclass of: EthicalObligation
generated at time: 2026-06-02T19:59:48.608792+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Cooperation Refused State
type: Class
action constraints: Non-cooperation is ethically impermissible when known design defects are present
action constraints: Owner must choose between proceeding under difficult conditions, abandoning the review, or replacing the original engineer
activation conditions: Engineer whose work is under review refuses to cooperate with the reviewing engineer
activation conditions: Peer review is properly initiated with required notification given
confidence: 0.87
obligation activation: Obligation on the non-cooperating engineer to act in the client's best interests
obligation activation: Obligation to hold public health, safety, and welfare paramount
obligation activation: Obligation to take responsibility for one's own design decisions
persistence type: inertial
principle transformation: Transforms general professional responsibility principles into a concrete duty to cooperate, especially when known defects elevate public safety concerns.
state category: conflict
termination conditions: Engineer agrees to cooperate with the peer review
termination conditions: Owner proceeds without the engineer or without the peer review
termination conditions: Review is formally cancelled
text references: If Engineer A refused to consent and cooperate, Owner would be then face with three options
text references: the Board concludes that it would be unethical for Engineer A to fail to cooperate
discovered in case: 15
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-02T19:53:12.877625+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: If Engineer A refused to consent and cooperate, Owner would be then face with three options
comment: State in which the engineer whose work is subject to a peer review declines to participate or cooperate with the review process, creating conditions under which the review may be impeded or rendered ineffective and triggering ethical obligations on the non-cooperating party.
subclass of: ConflictState
generated at time: 2026-06-02T19:53:12.877625+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Engineer
type: Class
confidence: 0.9
role category: professional_peer
text references: Engineer B objects to conducting the peer review without advising Engineer A
text references: Owner decides to obtain a peer review of the plans and design of Engineer A for the second tower and retains Engineer B
text references: Owner instructs Engineer B to conduct the peer review
discovered in case: 15
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-02T19:52:08.471399+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Owner decides to obtain a peer review of the plans and design of Engineer A for the second tower and retains Engineer B
comment: A professional engineering role engaged to independently evaluate and assess the plans, designs, or work product of another engineer, typically to identify errors, omissions, or deficiencies before or during construction.
subclass of: EngineerRole
subclass of: ProfessionalPeerRole
generated at time: 2026-06-02T19:52:08.471399+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Knowledge Obligation
type: Class
confidence: 0.95
derived from principle: Collegial Notification Principle
enforcement level: mandatory
monitoring criteria: Documented notification to the reviewed engineer prior to commencement of peer review
nspe reference: III.7.a
obligation type: collegial
stakeholders affected: Client
stakeholders affected: Design engineer under review
stakeholders affected: Public
text references: Engineer B was completely correct in declining an assignment to conduct a peer review of Engineer A's work subject to an instruction not to disclose the peer review to Engineer A.
text references: Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated.
violation consequences: Violation of NSPE III.7.a; potential disciplinary action; invalidation of review process
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T19:59:48.608792+00:00
first discovered in case: 15
match confidence: 0.78
match reasoning: This obligation is a specific mandatory instantiation of the collegial duty toward professional peers, grounded in NSPE III.7.a. The prior extraction captured a related concept as Peer Review Notification Obligation, and this class generalizes that concept into a reusable canonical form tied directly to the code provision.
matched ontology class: CollegialObligation
matched ontology label: Collegial Obligation
matches existing: true
source text: Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated.
comment: Duty of an engineer conducting a peer review to ensure that the engineer whose work is being reviewed has knowledge of the review before it commences, as required by NSPE III.7.a, unless the reviewed engineer's connection with the work has been terminated.
subclass of: CollegialObligation
scope note: [CollegialObligation] Duties toward professional peers including respect, fairness, and credit for work
generated at time: 2026-06-02T19:59:48.608792+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Notification Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Original Design Engineer
affected stakeholders: Reviewing Engineer
confidence: 0.9
constraint type: procedural
flexibility: hard
mitigation strategies: Document notification attempts and responses
mitigation strategies: Provide written notification to the original engineer prior to review
mitigation strategies: Refuse client instructions that conflict with notification requirements
text references: Engineer B objects to conducting the peer review without advising Engineer A.
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
text references: When Owner reluctantly consents to notifying Engineer A, Engineer A objects and refused to consent to the peer review.
violation impact: Breach of professional ethics, violation of NSPE Code provisions, potential disciplinary consequences, and compromise of the legitimacy of the review process.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:27.688172+00:00
first discovered in case: 15
match confidence: 0.82
match reasoning: This constraint maps well to the existing Procedural Constraint class, which covers requirements for following specific processes or protocols. The notification requirement before commencing peer review is a defined procedural step mandated by professional ethics codes, specifically NSPE Code III.7.a. It is a variant of Procedural Constraint with the distinguishing feature of the pre-review notification step.
matched ontology class: ProceduralConstraint
matched ontology label: Procedural Constraint
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
comment: Procedural constraint requiring that an engineer whose work is subject to peer review must be notified before the review commences, establishing a mandatory step in the peer review process that cannot be bypassed by client instruction.
subclass of: InviolableConstraint
subclass of: ProceduralConstraint
scope note: [ProceduralConstraint] Requirements for following specific processes or protocols (Furbach et al. 2014)
generated at time: 2026-06-02T19:57:27.688172+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Notification Obligation
type: Class
confidence: 0.88
derived from principle: Professional Transparency
enforcement level: prima_facie
monitoring criteria: Documented evidence that the original engineer was notified prior to commencement of peer review
nspe reference: III.7
obligation type: collegial
stakeholders affected: General public
stakeholders affected: Original design engineer
stakeholders affected: Project owner
text references: Engineer B objects to conducting the peer review without advising Engineer A.
text references: When Owner reluctantly consents to notifying Engineer A, Engineer A objects and refused to consent to the peer review.
violation consequences: Breach of collegial duty; potential disciplinary action; invalidation of review process integrity
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:56:24.847658+00:00
first discovered in case: 15
match confidence: 0.78
match reasoning: This is a specialization of the existing Collegial Obligation class, adding the specific context of peer review notification. The existing class covers duties toward professional peers including respect and fairness, which encompasses the duty to notify a peer before reviewing their work. Confidence is medium because the existing class is more general.
matched ontology class: CollegialObligation
matched ontology label: Collegial Obligation
matches existing: true
source text: Engineer B objects to conducting the peer review without advising Engineer A.
comment: Duty of a peer review engineer to notify the original design engineer before commencing an independent review of that engineer's work, ensuring the reviewed party has knowledge of and opportunity to respond to the review process.
subclass of: CollegialObligation
scope note: [CollegialObligation] Duties toward professional peers including respect, fairness, and credit for work
generated at time: 2026-06-02T19:56:24.847658+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Practice Standard
type: Class
authority source: Professional engineering societies and ethics boards
confidence: 0.78
extensional function: Grounds the duty to notify the original engineer before conducting a peer review and establishes acceptable peer review procedures within the profession.
resource category: professional_code
text references: Engineer B objects to conducting the peer review without advising Engineer A
usage context: Ethical conduct between engineers
usage context: Peer review engagements
usage context: Quality assurance on engineering designs
discovered in case: 15
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-02T19:51:55.286875+00:00
first discovered in case: 15
match confidence: 0.75
match reasoning: Peer review practice standards are a subtype of professional codes in that they distill collective professional experience into guidance for conduct. No more specific existing class covers peer review procedural norms, so matching to the Professional Code parent at medium confidence.
matched ontology class: ProfessionalCode
matched ontology label: Professional Code
matches existing: true
source text: Engineer B objects to conducting the peer review without advising Engineer A
comment: Professional norms and documented guidance governing the conduct of engineering peer reviews, including notification requirements, scope, and the rights and obligations of reviewing and reviewed engineers.
subclass of: ProfessionalCode
scope note: [ProfessionalCode] Distillations of collective experience that guide and justify actions
generated at time: 2026-06-02T19:51:55.286875+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Peer Review Protocol Competence
type: Class
capability category: domain_specific
confidence: 0.82
domain specificity: Professional engineering practice and peer review procedures
enables actions: Assess whether review conditions meet professional standards
enables actions: Decline improperly structured review assignments
enables actions: Identify when peer review notification is required
required for obligations: Covert Review Refusal Obligation
required for obligations: Peer Review Notification Obligation
skill level: advanced
text references: Engineer B objects to conducting the peer review without advising Engineer A
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:30.046199+00:00
first discovered in case: 15
match confidence: 0.75
match reasoning: Peer review protocol knowledge is a technical competency specific to professional engineering roles, fitting Professional Competence as defined by Kong et al. 2020 and Stenseke 2024. However, the procedural and ethical dimensions of peer review notification go beyond generic professional competence, warranting a more specific class. Matched as a variant at medium confidence.
matched ontology class: ProfessionalCompetence
matched ontology label: Professional Competence
matches existing: true
source text: Engineer B objects to conducting the peer review without advising Engineer A
comment: Technical and procedural knowledge of the standards governing independent peer review in professional engineering, including notification requirements, scope boundaries, and the conditions under which review is ethically permissible.
subclass of: Capability
scope note: [ProfessionalCompetence] Technical competencies specific to professional roles and activities (Kong et al. 2020, Stenseke 2024)
generated at time: 2026-06-02T19:57:30.046199+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Persistent Safety Pursuit Obligation State
type: Class
action constraints: Gravity of danger is a factor in determining how far the pursuit obligation extends
action constraints: Satisfaction of initial reporting duty does not extinguish the obligation to pursue further when formal presentations fail
activation conditions: Formal presentations have failed to produce corrective action or change in client plans
activation conditions: Professional has made formal written presentations to client and appropriate authorities
activation conditions: The gravity of the danger is sufficient to require continued pursuit
activation conditions: The underlying public safety risk remains unmitigated
confidence: 0.86
obligation activation: Duty to continue advocacy for public safety even after initial reporting obligations are technically satisfied
obligation activation: Duty to further pursue the matter beyond initial formal presentations
obligation activation: Duty to identify and engage additional authorities or channels
persistence type: inertial
principle transformation: Transforms the general duty to hold public safety paramount into a continuing and escalating obligation that survives initial formal reporting, requiring the professional to pursue additional remedies when those reports fail to produce corrective action.
state category: risk
termination conditions: Client or governing body adopts corrective measures
termination conditions: Engineer withdraws from the project after exhausting available escalation options
termination conditions: Regulatory authority intervenes and imposes compliance
termination conditions: The safety risk is otherwise resolved
text references: Engineers A and B have an obligation to further pursue the matter.
text references: in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter
discovered in case: 76
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T11:18:53.656605+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Engineers A and B have an obligation to further pursue the matter.
comment: State in which a professional engineer has made formal presentations to a client and to regulatory authorities regarding a confirmed public safety risk, those presentations have not produced corrective action, and the professional is therefore obligated to continue pursuing resolution through additional channels or escalation, given the gravity of the danger to public health and safety.
subclass of: RiskState
generated at time: 2026-06-05T11:18:53.656605+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Pile Driving Record Resource
type: Class
authority source: On-site construction records maintained by contractors and resident engineers
confidence: 0.8
extensional function: Provides primary field data grounding assessments of pile capacity and design compliance, enabling engineers and reviewers to evaluate whether construction met design intent.
resource category: reference_material
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal
text references: One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirements of the design calculations.
text references: We didn't look at the pile driving records because it was not in our scope of work.
text references: We just did not believe the driving records
usage context: Foundation performance evaluation
usage context: Litigation and mediation support
usage context: Peer technical review
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:23.227248+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirements of the design calculations.
comment: A contemporaneous field record documenting blow counts, penetration depth, and driving resistance data collected during pile installation. These records serve as primary technical evidence for evaluating whether driven piles achieved design load-carrying capacity and are used in post-construction review, dispute resolution, and engineering analysis.
subclass of: ReferenceMaterial
generated at time: 2026-06-04T14:26:23.227248+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Pollution Control Authority
type: Class
confidence: 0.85
role category: public_responsibility
text references: XYZ Corporation was advised by a State Pollution Control Authority of a need to apply for a permit to discharge manufacturing waste into a receiving body of water
text references: the BER concluded that Doe had an obligation to report his findings to the Pollution Control Authority
text references: the Pollution Control Authority would be holding a public hearing
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:07.116406+00:00
first discovered in case: 8
match confidence: 0.9
match reasoning: The Pollution Control Authority is a government oversight body with code-enforcement and permitting functions, matching the Regulatory Authority Role definition directly.
matched ontology class: RegulatoryAuthorityRole
matched ontology label: Regulatory Authority Role
matches existing: true
source text: XYZ Corporation was advised by a State Pollution Control Authority of a need to apply for a permit to discharge manufacturing waste into a receiving body of water
comment: A government regulatory body responsible for overseeing environmental discharge standards, issuing permits, and holding public hearings on matters affecting water quality and environmental compliance. Engineers who identify violations or risks have an obligation to report findings to this authority when client interests conflict with public welfare.
subclass of: PublicResponsibilityRole
subclass of: RegulatoryAuthorityRole
scope note: [RegulatoryAuthorityRole] Code-enforcement officials, inspectors, boards, and government agencies acting in an oversight capacity. No IFC equivalent (IFC has no regulator role).
generated at time: 2026-06-04T09:59:07.116406+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Post-Engagement Client Conduct Disclosure Principle
type: Class
abstract nature: Requires interpretation of whether the temporal gap between service completion and discovery of the violation affects the engineer's duty, and how the engineer's specialized knowledge creates responsibilities that persist beyond the engagement.
confidence: 0.78
derived obligations: Evaluate the severity and ongoing nature of discovered violations
derived obligations: Recognize that professional obligations to the public persist after an engagement concludes
derived obligations: Report substantial ongoing violations of environmental law to appropriate authorities when public welfare requires it
extensional examples: Engineer who completed site assessment discovers client has since implemented prohibited disposal practices
extensional examples: Engineer who completed wetland delineation later observes unpermitted fill and must determine whether prior engagement creates or limits reporting duty
operationalization: Requires engineers to evaluate whether discovered post-engagement client conduct causes ongoing harm, whether the engineer's specialized knowledge uniquely positions them to recognize and report the harm, and whether disclosure to authorities is required to prevent continuation of the violation.
potential conflicts: Client confidentiality obligations from the prior engagement
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Whistleblower Conscience Principle
principle category: professional_virtue
text references: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations
value basis: Professional responsibility derives from specialized knowledge and the public trust placed in licensed engineers, not solely from the existence of an active contractual relationship. Knowledge of ongoing illegal harm to public resources carries ethical weight independent of engagement status.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:28:58.159954+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material
comment: Professional principle establishing that an engineer's disclosure obligations to regulatory authorities or the public are not extinguished by the conclusion of the contractual engagement, and that conduct by a former client that constitutes a substantial violation of law and poses ongoing harm to public resources may trigger an affirmative obligation to report, notwithstanding the absence of a current service relationship.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T17:28:58.159954+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Post-Engagement Disclosure Constraint
type: Class
affected stakeholders: Engineer
affected stakeholders: Environmental Resources
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.82
constraint type: ethical
flexibility: hard
mitigation strategies: Consult applicable professional ethics codes and legal counsel regarding reporting obligations
mitigation strategies: Document the observation and the basis for concluding a violation has occurred before reporting
mitigation strategies: Report the confirmed violation to the appropriate federal and state regulatory authorities promptly upon discovery
text references: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
violation impact: Failure to report allows ongoing environmental harm, exposes the engineer to professional discipline, and undermines the public interest the engineer is obligated to protect.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:30:49.666256+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
comment: Ethical and legal constraint requiring an engineer who discovers, after the conclusion of a professional engagement, that a former client has committed a confirmed violation of applicable law or regulation to report that violation to the appropriate regulatory authority, notwithstanding the absence of an ongoing professional relationship. The termination of the engagement does not extinguish the engineer's duty to hold public welfare paramount when a confirmed violation poses a risk to public health, safety, or the environment.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T17:30:49.666256+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Post-Engagement Violation Detection Capability
type: Class
capability category: awareness
confidence: 0.78
domain specificity: Environmental engineering, wetland regulation, and post-engagement professional responsibility
enables actions: Assess whether observed conditions constitute a substantial violation
enables actions: Connect observed site conditions to prior professional knowledge of the site
enables actions: Recognize unpermitted fill activity as a legal violation
required for obligations: Observed Violation Disclosure Obligation
required for obligations: Post-Engagement Violation Reporting Obligation
skill level: advanced
text references: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:31:02.848953+00:00
first discovered in case: 86
match confidence: 0.72
match reasoning: Ethical Perception covers the capability to recognize ethically salient features and dynamically assess environment. The post-engagement incidental observation of a violation is a variant of that general perceptual capability applied in a specific post-engagement context. The existing class is the closest match but does not fully capture the post-engagement and domain-specific legal recognition dimension, so this is treated as a variant warranting a new specialized class.
matched ontology class: EthicalPerception
matched ontology label: Ethical Perception
matches existing: true
source text: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
comment: Capability to recognize, after the conclusion of a professional engagement, that a former client has committed a violation of applicable law or regulation related to the subject matter of the prior engagement, including the ability to identify the legal significance of observed conditions encountered incidentally rather than through active monitoring.
subclass of: Capability
scope note: [EthicalPerception] Capability to recognize ethically salient features and dynamically assess environment (Anderson et al. 2006, Berreby et al. 2017)
generated at time: 2026-06-04T17:31:02.848953+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Post-Engagement Violation Discovery State
type: Class
action constraints: Professional may not ignore a substantial known violation simply because the engagement has ended
action constraints: Professional must not certify or endorse the altered site condition without disclosing the violation
activation conditions: Professional independently observes or learns of client conduct constituting a violation
activation conditions: Professional's engagement with client has formally concluded
activation conditions: Violation relates to the subject matter of the prior professional engagement
confidence: 0.85
obligation activation: Duty to avoid using prior professional work to facilitate or conceal the violation
obligation activation: Duty to evaluate whether post-engagement reporting obligations are triggered
obligation activation: Obligation to assess whether the violation creates a public safety or environmental risk
persistence type: inertial
principle transformation: Transforms the general principle that professional obligations do not automatically terminate with a contract into a concrete duty to evaluate reporting and disclosure obligations when a post-engagement discovery reveals client misconduct related to the prior engagement.
state category: information
termination conditions: Client remedies the violation
termination conditions: Professional determines no reporting obligation applies and documents that determination
termination conditions: Professional reports violation to appropriate authority
text references: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material
discovered in case: 86
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T17:25:48.580472+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material
comment: State in which a professional, after completing services for a client, independently discovers that the client has taken actions on the subject site or matter that constitute a legal or regulatory violation, creating an obligation to evaluate whether post-engagement duties, including reporting to authorities, apply even though the professional's contractual relationship has concluded.
subclass of: InformationState
generated at time: 2026-06-04T17:25:48.580472+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Post-Engagement Violation Reporting Obligation
type: Class
confidence: 0.88
derived from principle: Post-Engagement Client Conduct Disclosure Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that the engineer reported the observed violation to the appropriate federal or state environmental or pollution control authority within a reasonable time after discovery.
nspe reference: I.1, II.1.a, II.1.c
obligation type: reporting
stakeholders affected: Adjacent landowners
stakeholders affected: General public
stakeholders affected: Regulatory authorities
stakeholders affected: Wetland ecosystems
text references: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
text references: Engineer A performs wetland delineation services on the client's wetland site.
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
violation consequences: Failure to report a known substantial environmental violation may constitute complicity in ongoing harm to public welfare and may expose the engineer to professional discipline.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:30:01.042237+00:00
first discovered in case: 86
match confidence: 0.82
match reasoning: The existing Post-Termination Environmental Risk Reporting Obligation covers the duty to report environmental risks to a pollution-control authority after termination of the client relationship when the risk rises to a public-safety concern. This case instantiates that class: Engineer A's engagement has concluded and the discovered violation is a substantial breach of federal and state law. The present class is a close variant emphasizing the active violation of law rather than a prospective risk, but the core concept is the same and the existing class is the correct match.
matched ontology class: PostTerminationEnvironmentalRiskReportingObligation
matched ontology label: Post-Termination Environmental Risk Reporting Obligation
matches existing: true
source text: Engineer A performs wetland delineation services on the client's wetland site.
comment: Duty of an engineer who discovers, after the conclusion of a professional engagement, that a former client has committed a substantial violation of federal or state environmental law on a site the engineer previously worked on, to report that violation to the appropriate regulatory authority, placing the paramount duty to public welfare above any residual loyalty to the former client.
subclass of: ReportingObligation
scope note: [PostTermEnvRiskReportingObligation] Duty of an engineer to report environmental risks to a pollution-control authority after termination of the client relationship when the risk rises to a public-safety concern (NSPE Code §I.1, §II.1.a, §II.1.c). Derived from the paramount public-welfare principle.
generated at time: 2026-06-04T17:30:01.042237+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Post-Formal-Presentation Persistence Principle
type: Class
abstract nature: Open-textured principle requiring judgment about what additional channels are available and appropriate, and about when the gravity of the danger is sufficient to trigger the obligation to persist beyond formal presentations.
confidence: 0.78
derived obligations: Continue pursuit of remediation in proportion to the gravity of the danger
derived obligations: Identify additional escalation channels when formal presentations fail
derived obligations: Not treat completion of formal presentations as discharge of all professional responsibility
extensional examples: BER Case No. 19-10 requiring Engineer A to continue pursuing resolution by working with client and contacting supervisors, fire marshals, or any other agency with jurisdiction
extensional examples: BER Case No. 89-7 establishing that engineers could have taken other steps beyond the structural report
operationalization: Requires engineers to identify additional channels for escalation when formal presentations fail, including contacting additional regulatory bodies, professional societies, or other authorities with jurisdiction, calibrated to the severity of the identified risk.
potential conflicts: Client confidentiality
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Whistleblower Conscience Principle
principle category: fundamental_ethical
text references: However, in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter.
value basis: The public cannot protect itself from engineering decisions it does not know about; when formal channels fail, the engineer remains the last line of defense and cannot treat procedural compliance as a substitute for actual protection of the public.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:26:55.962095+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: However, in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter.
comment: Professional principle establishing that when formal presentations to clients and regulatory authorities fail to produce remediation of a serious public health or safety risk, engineers have an obligation to further pursue the matter through additional available channels, and may not treat the completion of formal presentations as the end of their professional responsibility. The gravity of the danger determines the extent of the obligation to persist.
subclass of: FundamentalEthicalPrinciple
generated at time: 2026-06-05T11:26:55.962095+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Post-Override Persistence Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.85
constraint type: ethical
flexibility: soft
mitigation strategies: Coordinate with co-engineers to pursue additional channels consistently
mitigation strategies: Document all escalation steps and their outcomes
mitigation strategies: Escalate to higher levels within the regulatory hierarchy if initial contacts are unresponsive
mitigation strategies: Identify and engage additional regulatory or governmental authorities with jurisdiction
text references: in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter
violation impact: Confirmed public health risk persists without adequate professional advocacy, engineer abandons paramount safety duty after initial steps, public remains endangered.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:35.133297+00:00
first discovered in case: 76
match confidence: 0.75
match reasoning: The Regulatory Escalation Constraint requires an engineer whose client has overridden a safety recommendation to report the risk to appropriate regulatory authorities. The present constraint extends that concept to require continued pursuit beyond the initial formal presentation if that presentation fails to produce a change in the client's plans. It is a variant that adds the persistence dimension to the escalation obligation. Medium-confidence variant match is appropriate.
matched ontology class: Regulatory Escalation Constraint
matched ontology label: Regulatory Escalation Constraint
matches existing: true
source text: in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter
comment: Ethical constraint requiring that an engineer who has made formal presentations to a client and to regulatory authorities regarding a confirmed public health or safety risk, and whose recommendations have not been adopted, must continue to pursue resolution through additional available channels rather than treating the formal presentations as the end of the professional obligation. The gravity of the danger determines the extent of the continuing pursuit required.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [RegulatoryEscalationConstraint] Safety and ethical constraint requiring an engineer who has identified a confirmed risk to public health or safety, and whose client has overridden the engineer's recommendation to address that risk, to report the risk to the appropriate regulatory or pollution control authority when the client's override creates a condition that endangers public welfare and cannot be resolved within the professional relationship.
generated at time: 2026-06-05T11:29:35.133297+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Post-Presentation Persistence Capability
type: Class
capability category: reasoning
confidence: 0.83
domain specificity: Public safety engineering with multi-step regulatory escalation
enables actions: Assess whether formal presentations have resolved the public safety risk
enables actions: Continue pursuing resolution through available means after initial escalation
enables actions: Identify additional channels for escalation when formal presentations fail
required for obligations: Engineers A B Post-Presentation Persistence
required for obligations: Post-Presentation Persistence Obligation
skill level: advanced
text references: in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:29:39.466339+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter.
comment: Capability to recognize that a formal presentation to a client and to regulatory authorities does not exhaust the professional obligation when a serious public health or safety risk remains unaddressed, and to identify and pursue additional available channels or escalation steps beyond the initial formal presentation.
subclass of: Capability
generated at time: 2026-06-05T11:29:39.466339+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Post-Presentation Persistence Obligation
type: Class
confidence: 0.87
derived from principle: Post-Formal-Presentation Persistence Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer pursued additional escalation steps or channels after formal presentations failed to change the client's course of action.
nspe reference: I.1, II.1.a, II.1.c
obligation type: safety
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: State regulatory agency
text references: However, in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter.
violation consequences: Abandonment of the matter after failed formal presentations leaves the public exposed to identified health and safety risks without further professional advocacy.
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T11:28:12.343728+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: However, in the event that these formal presentations fail to sway the MWC to change its plans, given the gravity of the danger to public health and safety, Engineers A and B have an obligation to further pursue the matter.
comment: Duty of an engineer who has made formal presentations to a client and to regulatory authorities regarding a public health or safety risk, and whose presentations have failed to produce a change in the client's plans, to further pursue the matter through additional available channels, given the gravity of the danger to public health and safety.
subclass of: SafetyObligation
generated at time: 2026-06-05T11:28:12.343728+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Precedent Modification Reasoning Capability
type: Class
capability category: reasoning
confidence: 0.83
domain specificity: Professional engineering ethics adjudication and precedent management
enables actions: Articulate a reasoned basis for departing from or refining prior decisions
enables actions: Assess whether a prior ruling is consistent with current professional practice
enables actions: Distinguish clarification from reversal in ethical precedent
enables actions: Identify factual or normative grounds for modifying a prior ruling
required for obligations: Code Prevailing Practice Conformance Obligation
skill level: expert
text references: For that reason, we think the Board's conclusion in BER Case 86-2 should be modified to reflect actual practices which exist within engineering and not impose a impossible standard upon practice.
text references: This Board has long noted that the Code of Ethics is not a static document and must reflect and be in consonance with generally prevailing practices within the engineering profession.
text references: We do not believe this represents a reversal of the Board's decision in BER Case 86-2, but rather a clarification, particularly for those who were troubled by the Board's discussion and conclusion in that case.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:12:59.240485+00:00
first discovered in case: 120
match confidence: 0.75
match reasoning: Precedent Analogical Reasoning Capability addresses identifying prior rulings, analyzing factual distinctions, and reasoning from those distinctions to determine whether the precedent applies. Precedent Modification Reasoning Capability is a related but distinct concept: it concerns the ability to reason about when and how a prior ruling should be modified or clarified rather than simply applied or distinguished. The match is medium confidence as a variant of the existing class, with the modification and clarification dimension being the distinguishing feature.
matched ontology class: Precedent Analogical Reasoning Capability
matched ontology label: Precedent Analogical Reasoning Capability
matches existing: true
source text: For that reason, we think the Board's conclusion in BER Case 86-2 should be modified to reflect actual practices which exist within engineering and not impose a impossible standard upon practice.
comment: Capability to identify when a prior ethical ruling or precedent should be modified or clarified in light of new information, changed professional practices, or demonstrated inconsistency with prevailing norms, and to articulate a reasoned basis for the modification that distinguishes it from a reversal while preserving doctrinal continuity.
subclass of: Capability
scope note: [PrecedentAnalogicalReasoningCapability] Capability to identify prior professional ethics rulings or case precedents that are factually similar to a current situation, to analyze the factual distinctions between the precedent and the current case, and to reason from those distinctions to determine whether the precedent's conclusion applies, is modified, or is inapplicable in the current context.
generated at time: 2026-06-04T18:12:59.240485+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Preliminary Risk Disclosure Capability
type: Class
capability category: awareness
confidence: 0.8
domain specificity: Environmental and stormwater engineering risk communication
enables actions: Communicate a preliminary risk concern to a client without overstating or understating the level of certainty
enables actions: Distinguish between concerns that are too speculative to disclose and those that warrant preliminary notification
enables actions: Recognize when a preliminary stormwater risk concern is sufficiently developed to require client notification
required for obligations: Preliminary Risk Disclosure Obligation
skill level: advanced
text references: But before Engineer L can quantify the increased risk, Client X encounters unexpected financial setbacks and requests that Engineer L suspend work.
text references: During the preliminary design phase, Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase, as the likelihood of heavy stormwater flows will increase over time.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.8
match reasoning: Concern Versus Fact Threshold Capability is defined as the capability to distinguish between a preliminary professional concern that has not yet been substantiated by technical analysis and a finding that rises to the level of a demonstrable fact, and to calibrate disclosure obligations accordingly so that neither premature disclosure of unsubstantiated concerns nor suppression of confirmed findings occurs. This maps to the capability required for Engineer L to determine whether the preliminary stormwater risk concern warranted disclosure at the time of suspension. The match is medium-high confidence because the existing class captures the core calibration judgment, though the present case emphasizes the disclosure side rather than the suppression side.
matched ontology class: Concern Versus Fact Threshold Capability
matched ontology label: Concern Versus Fact Threshold Capability
matches existing: true
source text: During the preliminary design phase, Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase, as the likelihood of heavy stormwater flows will increase over time.
comment: Capability to recognize when a preliminary professional concern about a risk to public health or safety, even before it has been fully quantified, is sufficiently developed to warrant disclosure to the client, and to communicate that concern in a manner that is appropriately calibrated to the level of certainty available at the time.
subclass of: Capability
scope note: [ConcernVersusFactThresholdCapability] Capability to distinguish between a preliminary professional concern that has not yet been substantiated by technical analysis and a finding that rises to the level of a demonstrable fact, and to calibrate disclosure obligations accordingly so that neither premature disclosure of unsubstantiated concerns nor suppression of confirmed findings occurs.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Premature Source Transition State
type: Class
action constraints: Professional must not certify the transition as safe without adequate safeguards
action constraints: Professional must not remain silent when public health is at imminent risk
activation conditions: Authority votes to change supply source before required improvements are complete
activation conditions: Corrosion control or treatment capacity is insufficient for the new source
activation conditions: Professional engineers have identified that improvements are necessary prior to transition
confidence: 0.85
obligation activation: Duty to assess whether continued participation is ethically permissible
obligation activation: Duty to document professional objection
obligation activation: Duty to notify regulatory authorities of public health risk
persistence type: inertial
principle transformation: Transforms the general duty to protect public health and safety into a concrete obligation to object, document, and report when a utility proceeds with a supply change that creates foreseeable lead leaching risk in the distribution system.
state category: risk
termination conditions: Regulatory authority halts the transition
termination conditions: Required treatment improvements are completed and validated
termination conditions: Source change is reversed
text references: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards.
text references: the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T11:17:42.957900+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards.
comment: State in which a water or utility authority proceeds with a change in supply source before required treatment infrastructure, corrosion control measures, or quality safeguards have been designed, evaluated, or constructed, creating an active public health risk because the new source may deliver water through distribution infrastructure that is incompatible with the new source chemistry.
subclass of: RiskState
generated at time: 2026-06-05T11:17:42.957900+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Prime Consultant Engineer
type: Class
confidence: 0.8
role category: provider_client
text references: the prime consultant, which has overall responsibility for the project, was in a far better position than Engineer A to understand the interrelationships between various elements of the projects
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:26:36.428475+00:00
first discovered in case: 86
match confidence: 0.72
match reasoning: Prime Consultant Engineer is a specialization of Consultant Role with added coordination and integration responsibilities over sub-consultants. It is not identical to the generic Consultant Role but maps to it as a parent.
matched ontology class: ConsultantRole
matched ontology label: Consultant Role
matches existing: true
source text: the prime consultant, which has overall responsibility for the project, was in a far better position than Engineer A to understand the interrelationships between various elements of the projects
comment: A professional engineering role in which the practitioner or firm holds overall responsibility for a project as the primary contracted consultant, coordinates sub-consultants, and bears accountability for integrating technical findings from all sub-consultants into a coherent project-level evaluation and response.
subclass of: ConsultantRole
subclass of: ProviderClientRole
scope note: [ConsultantRole] Professional engaged for expert advice on a specific aspect of a project. Engineering consultants are classified under EngineerRole. This head covers non-engineering advisory roles.
generated at time: 2026-06-04T17:26:36.428475+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Private Development Client
type: Class
confidence: 0.85
role category: provider_client
text references: Client X encounters unexpected financial setbacks and requests that Engineer L suspend work
text references: Client X insists on proceeding without added safeguards
text references: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations
text references: Client X, a private development entity
discovered in case: 8
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T09:57:38.749817+00:00
first discovered in case: 8
match confidence: 0.8
match reasoning: Client Role exists in the ontology as the party that commissions project work. Private Development Client is a specialization of Client Role distinguished by its private commercial nature and the tension between financial constraints and public safety obligations. Matching to Client Role as parent with medium confidence.
matched ontology class: ClientRole
matched ontology label: Client Role
matches existing: true
source text: Client X, a private development entity
comment: A private commercial entity that commissions professional engineering services for a development project, acting as the primary client and decision-maker but lacking professional engineering licensure, and whose financial and business interests may conflict with the engineer's professional obligations to protect public welfare.
subclass of: ClientRole
subclass of: ProviderClientRole
scope note: [ClientRole] Party that commissions the project work. This is the occupational archetype. The duty relationship is carried separately by :ProviderClientRole.
generated at time: 2026-06-04T09:57:38.749817+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Proactive Risk Disclosure Principle
type: Class
abstract nature: Open-textured value requiring judgment about when a risk is sufficiently identified to trigger disclosure, and to whom disclosure must be made beyond the immediate client.
confidence: 0.88
derived obligations: Disclose identified risks to the client at the time of identification, not deferred to a later phase
derived obligations: Document risk communications in writing
derived obligations: Escalate to appropriate authorities when client declines to act on disclosed risks affecting third parties
extensional examples: BER Case 76-4 where an engineer failed to disclose pollution risk to a regulatory authority
extensional examples: Engineer L case where work suspension did not relieve the obligation to communicate identified drinking water risks
operationalization: Requires engineers to communicate identified risks to clients at the time of identification, regardless of project status, and to escalate to regulatory authorities or the public when client action is insufficient to protect third parties.
potential conflicts: Client Loyalty
potential conflicts: Confidentiality
principle category: professional_virtue
text references: Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase, as the likelihood of heavy stormwater flows will increase over time
text references: Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source
value basis: Engineers possess specialized knowledge that affected parties lack; withholding identified risks deprives those parties of the ability to protect themselves or seek alternative measures.
discovered in case: 8
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:01:19.883840+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source
comment: Professional principle requiring engineers to disclose known or reasonably anticipated risks to affected parties, including clients and the public, as soon as those risks are identified, without waiting for the risks to materialize or for a convenient moment in the project lifecycle. The obligation to disclose is not suspended by project interruptions, financial pressures, or client reluctance.
subclass of: FundamentalEthicalPrinciple
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T10:01:19.883840+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Procedural Irregularity Reporting Capability
type: Class
capability category: awareness
confidence: 0.89
domain specificity: Geotechnical observation and testing in foundation engineering
enables actions: Assess the potential effect of irregularities on test validity
enables actions: Identify procedural deviations from standard or agreed methods
enables actions: Observe and document equipment failures during testing
enables actions: Report irregularities to the retaining party and in formal findings
required for obligations: Observer Irregularity Reporting Obligation
skill level: intermediate
text references: After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced.
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class addresses the competency of observing, documenting, and reporting procedural irregularities during a supervised test or investigation.
matches existing: false
source text: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration.
comment: Ability to observe, document, and report procedural irregularities or equipment failures encountered during a test or investigation, including deviations from standard practice that may affect the validity of results.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Procedural Irregularity Reporting Constraint
type: Class
affected stakeholders: Observer engineer
affected stakeholders: Opposing parties
affected stakeholders: Retaining party
affected stakeholders: Tribunal
confidence: 0.86
constraint type: procedural
flexibility: hard
mitigation strategies: Include irregularity documentation in the observer report
mitigation strategies: Maintain contemporaneous field notes of all observed irregularities
mitigation strategies: Raise irregularities with the supervising engineer at the time of occurrence
text references: After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced.
text references: An independent geotechnical consultant was retained by Engineer A to observe the test.
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration.
violation impact: Invalid test record, misleading findings, professional discipline, unjust dispute outcomes
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology addresses the procedural requirement for an observer to document and report irregularities. This is the bounding constraint corresponding to the obligation-side Observer Irregularity Reporting Obligation.
matches existing: false
source text: An independent geotechnical consultant was retained by Engineer A to observe the test.
comment: Requirement that an engineer or observer retained to witness a test or investigation document and report all procedural irregularities observed, regardless of which party the irregularities may favor or disfavor.
subclass of: InviolableConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Professional Accountability Acceptance Capability
type: Class
capability category: awareness
confidence: 0.8
domain specificity: Professional engineering practice involving design error discovery and quality assurance
enables actions: Acknowledge prior errors without evasion
enables actions: Consent to independent review of prior work
enables actions: Cooperate fully with peer review processes
enables actions: Prioritize public safety over personal professional interest
required for obligations: Error Acknowledgment Cooperation Obligation
required for obligations: Peer Review Cooperation Obligation
required for obligations: Professional Accountability Cooperation Obligation
required for obligations: Safety Review Consent Obligation
skill level: intermediate
text references: Engineers must take responsibility for their actions, must acknowledge their errors, must act in the best interests of their clients, and must at all times hold paramount the health, welfare, and safety of the public.
text references: The known design defects in the first tower simply makes each of those requirements more urgent.
text references: Under the facts, the Board concludes that it would be unethical for Engineer A to fail to cooperate.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:55.491400+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineers must take responsibility for their actions, must acknowledge their errors, must act in the best interests of their clients, and must at all times hold paramount the health, welfare, and safety of the public.
comment: Capability to recognize that professional responsibility for prior errors requires active cooperation with corrective and quality assurance processes, including peer review, and to act accordingly rather than obstructing such processes.
subclass of: Capability
generated at time: 2026-06-02T20:00:55.491400+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Professional Accountability Cooperation Obligation
type: Class
confidence: 0.82
derived from principle: Professional Accountability
enforcement level: prima_facie
monitoring criteria: Evidence that the design engineer cooperated with or at minimum did not obstruct the peer review process
nspe reference: II.2
obligation type: ethical
stakeholders affected: General public
stakeholders affected: Professional engineering community
stakeholders affected: Project owner
text references: Engineer A objects and refused to consent to the peer review.
text references: Several significant design errors are discovered in the plans and design of Engineer A.
violation consequences: Failure of professional accountability; potential disciplinary action; obstruction of safety-motivated oversight
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:56:24.847658+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineer A objects and refused to consent to the peer review.
comment: Duty of a design engineer to cooperate with legitimate quality assurance and review processes, including peer review, particularly when prior errors in their work have been identified, as an expression of professional accountability.
subclass of: EthicalObligation
generated at time: 2026-06-02T19:56:24.847658+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Professional Accountability Principle
type: Class
abstract nature: The principle requires interpretation of the scope and depth of accountability that attaches to the act of sealing, and how that accountability differs depending on whether the engineer personally prepared the work or supervised its preparation.
confidence: 0.9
derived obligations: Accept personal responsibility for all sealed documents
derived obligations: Ensure adequate basis exists for sealing, whether through personal preparation or substantive supervision
derived obligations: Respond to challenges to sealed work products
extensional examples: Engineer A bears full accountability for CADD documents personally prepared and sealed
extensional examples: Engineer B bears full accountability for CADD documents sealed after directing and controlling the work of others
operationalization: Requires engineers to understand that sealing a document is not a ministerial act but an acceptance of professional responsibility, and to ensure they have the basis to stand behind every document they seal.
potential conflicts: Efficiency pressures in document production
potential conflicts: Employer Loyalty
principle category: professional_virtue
text references: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system.
text references: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control.
value basis: The professional seal is a public representation that the engineer accepts personal responsibility for the work, protecting the public who rely on the documents.
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:07:04.619436+00:00
first discovered in case: 120
match confidence: 0.92
match reasoning: The existing ontology class 'Professional Accountability' is defined as a professional virtue principle requiring engineers to accept responsibility for their work product and to submit to legitimate oversight and review processes. This matches the accountability dimension of sealing engineering documents, where the act of signing and sealing constitutes a public acceptance of professional responsibility. The concept is the same; no new class is needed.
matched ontology class: Professional Accountability
matched ontology label: Professional Accountability
matches existing: true
source text: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system.
comment: Professional virtue principle requiring engineers to accept responsibility for their work product and to submit to legitimate oversight and review processes, particularly when the engineer's seal is affixed to documents, making the engineer personally accountable for the technical adequacy and accuracy of those documents.
subclass of: ProfessionalVirtuePrinciple
scope note: [ProfessionalAccountability] Professional virtue principle requiring engineers to accept responsibility for their work product and to submit to legitimate oversight and review processes, particularly when errors in that work product have been identified.
generated at time: 2026-06-04T18:07:04.619436+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Professional Competence
type: Class
abstract nature: Requires ongoing self-assessment and acceptance of external validation mechanisms as legitimate checks on whether competence standards are being met in practice.
confidence: 0.87
derived obligations: Accept peer review as a legitimate competence-verification mechanism
derived obligations: Acknowledge when prior work contained significant deficiencies
derived obligations: Correct identified errors in existing designs
extensional examples: NSPE BER cases involving engineers who produced deficient designs and the profession's response
extensional examples: NSPE Code Section II.2 requiring engineers to perform services only in areas of their competence
operationalization: The discovery of significant errors in the first tower plans provides grounds for peer review of the second tower plans as a competence-verification mechanism, and Engineer A's resistance to that review conflicts with the accountability dimension of professional competence.
potential conflicts: Loyalty
potential conflicts: Professional Dignity
principle category: professional_virtue
text references: Owner decides to obtain a peer review of the plans and design of Engineer A for the second tower
text references: several significant design errors are discovered in the plans and design of Engineer A
value basis: Public safety depends on engineers producing technically sound work, and the discovery of significant errors in completed designs raises legitimate questions about whether competence standards were met.
discovered in case: 15
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:55:30.891672+00:00
first discovered in case: 15
match confidence: 0.9
match reasoning: Direct match to the existing Professional Competence class in the ontology. The case raises this principle through the discovery of significant design errors in the first tower, which motivates the peer review of the second tower as a mechanism for verifying that competence standards are being met.
matched ontology class: Professional Competence
matched ontology label: Professional Competence
matches existing: true
source text: several significant design errors are discovered in the plans and design of Engineer A
comment: Professional virtue principle requiring engineers to maintain and demonstrate the technical knowledge and skill necessary to produce work that meets applicable standards, and to acknowledge the limits of their competence.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-02T19:55:30.891672+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Professional Integrity
type: Class
abstract nature: Character-based principle that shapes how engineers respond when client instructions or self-interest conflict with professional obligations, requiring internal moral consistency rather than mere rule compliance.
confidence: 0.88
derived obligations: Accept peer review as a legitimate professional process
derived obligations: Place professional obligations above personal reputational concerns
derived obligations: Resist client pressure to conduct covert review
extensional examples: NSPE BER cases involving engineers who refused client instructions that would compromise professional standards
extensional examples: Oakley and Cocking virtue ethics framework applied to engineering professional character
operationalization: Requires Engineer B to insist on notifying Engineer A despite client pressure to proceed covertly, and requires Engineer A to accept legitimate oversight rather than obstruct it for self-protective reasons.
potential conflicts: Loyalty
potential conflicts: Professional Dignity
principle category: professional_virtue
text references: Engineer A objects and refused to consent to the peer review
text references: Engineer B objects to conducting the peer review without advising Engineer A
value basis: Professional trustworthiness depends on engineers acting from internalized values rather than external compulsion, so that their conduct is reliable even when oversight is absent.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:55:30.891672+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineer B objects to conducting the peer review without advising Engineer A
comment: Professional virtue principle requiring engineers to maintain consistency between their ethical obligations and their conduct, refusing to allow client pressure, personal interest, or collegial discomfort to cause them to act contrary to their professional duties.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-02T19:55:30.891672+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Professional Transparency
type: Class
abstract nature: Requires contextual judgment about what information must be disclosed to whom, and at what stage of a professional process, to preserve trust and fairness in collegial relationships.
confidence: 0.91
derived obligations: Decline to conduct covert review of a colleague's work
derived obligations: Inform the original engineer of the scope and purpose of the review
derived obligations: Notify the original engineer before commencing peer review
extensional examples: NSPE BER Case 94-7 on notification obligations when reviewing another engineer's work
extensional examples: NSPE Code Section III.8 requiring engineers to notify the other party when asked to review another engineer's work
operationalization: Requires the reviewing engineer to notify the original design engineer before or at the outset of a peer review, and requires the client to permit such notification as a condition of the engagement.
potential conflicts: Confidentiality
potential conflicts: Loyalty
principle category: relational
text references: Engineer B objects to conducting the peer review without advising Engineer A
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
text references: When Owner reluctantly consents to notifying Engineer A
value basis: Engineers whose work is subject to review have a legitimate professional interest in knowing that review is occurring, so they may respond, correct errors, or provide context.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:55:30.891672+00:00
first discovered in case: 15
match confidence: 0.88
match reasoning: The principle maps closely to the existing Transparency class in the ontology. The case instantiates transparency as the obligation to disclose to Engineer A that a peer review is being conducted, which is a direct application of the Transparency principle governing openness in professional conduct.
matched ontology class: Transparency
matched ontology label: Transparency
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
comment: Relational principle requiring engineers to conduct professional activities openly and without concealment from affected colleagues, particularly when those activities involve evaluating or overseeing another engineer's work.
subclass of: RelationalPrinciple
generated at time: 2026-06-02T19:55:30.891672+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Project Delivery Advisor
type: Class
confidence: 0.83
role category: provider_client
text references: City B's City Administrator asked Engineer A for a recommendation on project delivery methods
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:41:03.751066+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: City B's City Administrator asked Engineer A for a recommendation on project delivery methods
comment: A professional engineering role in which the practitioner provides advisory recommendations to a client on the selection of project delivery methods for a capital project, bearing professional obligations of objectivity, completeness, and avoidance of self-interest in the advice rendered.
subclass of: ProviderClientRole
generated at time: 2026-06-04T08:41:03.751066+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Project Delivery Method Guidance Resource
type: Class
authority source: Funding agencies, government programs, or regulatory bodies administering infrastructure financing
confidence: 0.82
extensional function: Establishes the bounded set of permissible delivery options an engineer must consider and disclose when advising an owner, grounding the duty of completeness and objectivity in professional recommendations.
resource category: legal_resource
text references: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
usage context: Funding compliance
usage context: Owner advisory services
usage context: Project delivery method selection
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:40:56.485170+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
comment: Official documentation or regulatory guidance specifying approved project delivery methods available under a particular funding source or program, including conditions and constraints attached to each method such as entity separation requirements.
subclass of: LegalResource
generated at time: 2026-06-04T08:40:56.485170+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Project Owner
type: Class
confidence: 0.85
role category: provider_client
text references: Owner decides to obtain a peer review
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know
text references: Owner is developing a site with two mirror-image towers
text references: Owner retains Engineer B
text references: When Owner reluctantly consents to notifying Engineer A
discovered in case: 15
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-02T19:52:08.471399+00:00
first discovered in case: 15
match confidence: 0.92
match reasoning: Project Owner maps directly to Owner Role in the ontology, which is defined as the party that owns the asset, project, or building. High confidence match.
matched ontology class: OwnerRole
matched ontology label: Owner Role
matches existing: true
source text: Owner is developing a site with two mirror-image towers
comment: A party that owns or is developing an asset and commissions professional engineering and construction services for that asset, acting as the primary client and decision-maker for the project.
subclass of: OwnerRole
subclass of: ProviderClientRole
scope note: [OwnerRole] Party that owns the asset, project, or building.
generated at time: 2026-06-02T19:52:08.471399+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Project Safety Advisor
type: Class
confidence: 0.83
role category: provider_client
text references: Engineer A abandoned the ethical duty and proceeded to work on the project
text references: Engineer A did notify the client of the need to hire a full-time, on-site project representative
text references: Engineer A recommended the client hire a full-time, on-site project representative for the project because of the potentially dangerous nature of implementing the design during the construction phase
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T02:17:07.048701+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer A recommended the client hire a full-time, on-site project representative for the project because of the potentially dangerous nature of implementing the design during the construction phase
comment: A licensed professional engineering role in which the practitioner recommends specific safety measures or personnel to a client as a condition of project success, notifies the client when omission of those measures creates unacceptable risk, and bears an obligation not to continue work when the client refuses to implement the identified safeguards, because proceeding would subordinate public safety to the client's economic concerns.
subclass of: ProviderClientRole
generated at time: 2026-06-05T02:17:07.048701+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Project Success Notification Capability
type: Class
capability category: reasoning
confidence: 0.93
domain specificity: Professional engineering project advisory in stormwater and environmental contexts
enables actions: Advise the client that the project as currently scoped will not meet regulatory or public safety requirements
enables actions: Assess whether proceeding without recommended protective measures constitutes a compliant or successful project outcome
enables actions: Communicate the professional judgment that proceeding without safeguards is not a viable path to project success
required for obligations: Project Success Notification Obligation
skill level: advanced
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: local environmental standards require steps to safeguard public water sources
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.93
match reasoning: Project Success Assessment Capability is defined as the capability to evaluate whether a project can be completed successfully in terms of safety, structural adequacy, and public welfare, and to advise the client or employer when the engineer's professional judgment is that the project will not be successful without specific measures, including the ability to define success beyond mere economic or structural completion. This matches the capability required for Engineer L's obligation to advise Client X that proceeding without protective measures would not constitute a compliant or successful project. The match is high confidence.
matched ontology class: Project Success Assessment Capability
matched ontology label: Project Success Assessment Capability
matches existing: true
source text: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
comment: Capability to evaluate whether a project can be completed successfully in terms of safety, regulatory compliance, and public welfare, and to advise the client or employer when the engineer's professional judgment is that the project will not be successful without specific measures, including the ability to define success beyond mere economic or structural completion.
subclass of: Capability
scope note: [ProjectSuccessAssessmentCapability] Capability to evaluate whether a project can be completed successfully in terms of safety, structural adequacy, and public welfare, and to advise the client or employer when the engineer's professional judgment is that the project will not be successful without specific measures, including the ability to define success beyond mere economic or structural completion.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Project Success Notification Principle
type: Class
abstract nature: The concept of project success requires interpretation across technical, economic, and safety dimensions. The principle requires engineers to exercise judgment about when a project has crossed the threshold of likely failure or unacceptable risk, and to communicate that judgment clearly to clients even when unwelcome.
confidence: 0.9
derived obligations: Define project success to include safety outcomes, not only structural and economic outcomes
derived obligations: Document notifications to clients about project viability concerns
derived obligations: Notify clients when project success is threatened by identified deficiencies or refused protective measures
extensional examples: BER Case 84-5: Engineer A was required to notify client that project would not be successful without a full-time on-site safety representative during construction
extensional examples: Present case: Engineer L was required to notify Client X that the project would not be successful without implementation of protective stormwater measures
operationalization: Requires engineers to communicate clearly when identified deficiencies or client refusals to implement protective measures will result in project failure or unsafe conditions, and to document that communication.
potential conflicts: Client confidentiality
potential conflicts: Faithful Agent Duty Principle
principle category: professional_virtue
text references: Client X's insistence on moving forward with the project without adequate safeguards creates an ethical dilemma for Engineer L.
text references: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
text references: Engineer L notified Client X of this risk.
text references: section III.1.b. clearly requires the engineer to inform a client when the engineer believes that a project will not be successful. The term successful includes not merely the structural and economic success of a project but also the success of the project from a safety standpoint.
value basis: Clients rely on engineers for honest professional assessments of project viability and risk. Withholding a judgment that a project will fail or create safety risks deprives the client of information needed to make informed decisions and exposes the public to preventable harm.
discovered in case: 8
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:05:37.970804+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
comment: Professional principle requiring engineers to advise clients or employers when, in the engineer's professional judgment, a project will not be successful, where success encompasses not only structural and economic outcomes but also safety outcomes. This obligation applies when the engineer has identified conditions or deficiencies that, if unaddressed, will result in project failure or unsafe outcomes.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T10:05:37.970804+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Protective Measure Recommendation Capability
type: Class
capability category: domain_specific
confidence: 0.85
domain specificity: Stormwater management and environmental engineering
enables actions: Assess adequacy of proposed protective measures against identified risk
enables actions: Communicate the technical basis for protective measure recommendations
enables actions: Identify safeguards required by local environmental standards
enables actions: Recommend specific stormwater protective measures to client
required for obligations: Protective Measure Recommendation Obligation
skill level: advanced
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:03:17.498340+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
comment: Capability to identify and recommend specific protective measures commensurate with an identified risk to public health or safety, including the ability to specify what safeguards are technically appropriate and to communicate those recommendations clearly to a client even when the client is reluctant to invest in them.
subclass of: Capability
generated at time: 2026-06-04T10:03:17.498340+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Protective Measure Recommendation Obligation
type: Class
confidence: 0.84
derived from principle: Proactive Risk Disclosure Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that the engineer provided specific protective measure recommendations to the client in writing, with reference to applicable regulatory requirements.
nspe reference: I.1, II.1.a, II.1.c
obligation type: safety
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
violation consequences: Failure to recommend protective measures leaves the client without professional guidance needed to protect public welfare and may expose the engineer to liability for resulting harm.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:02:21.757544+00:00
first discovered in case: 8
match confidence: 0.75
match reasoning: This obligation is a variant of the existing Safety Obligation, specialized to the duty to affirmatively recommend protective measures rather than merely identify risks. The existing Safety Obligation covers the general duty to hold paramount public safety, but does not specifically address the affirmative duty to recommend concrete protective measures to the client. A new class is warranted to capture this action-specific dimension.
matched ontology class: SafetyObligation
matched ontology label: Safety Obligation
matches existing: true
source text: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
comment: Duty of an engineer who identifies a risk to public health or safety to recommend specific protective measures to the client that are commensurate with the identified risk, including measures required by applicable local, state, or federal environmental or safety standards, and to document those recommendations.
subclass of: SafetyObligation
scope note: [SafetyObligation] Duty to hold paramount the safety, health, and welfare of the public (NSPE I.1)
generated at time: 2026-06-04T10:02:21.757544+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Public Agency Client
type: Class
confidence: 0.83
role category: provider_client
text references: The public agency contacted VWX Architects and Engineers which then contacted Engineer A
text references: a public agency retained the services of VWX Architects and Engineers to perform a major scheduled overhaul of a bridge
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:26:36.428475+00:00
first discovered in case: 86
match confidence: 0.75
match reasoning: Public Agency Client is a specialization of Client Role representing a government body commissioning infrastructure services. It is closely related to Municipal Client already extracted in prior cases but is referenced here in the context of bridge overhaul and is treated as the same general concept.
matched ontology class: ClientRole
matched ontology label: Client Role
matches existing: true
source text: a public agency retained the services of VWX Architects and Engineers to perform a major scheduled overhaul of a bridge
comment: A government or public agency that commissions professional engineering or architectural services for public infrastructure, acting as the primary client and decision-maker, and as the party responsible for authorizing or directing corrective action when safety-relevant findings are reported through the consultant chain.
subclass of: ProviderClientRole
subclass of: RegulatoryAuthorityRole
scope note: [ClientRole] Party that commissions the project work. This is the occupational archetype. The duty relationship is carried separately by :ProviderClientRole.
generated at time: 2026-06-04T17:26:36.428475+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Public Funds Misrepresentation Avoidance Capability
type: Class
capability category: reasoning
confidence: 0.85
domain specificity: Professional engineering on publicly funded infrastructure projects
enables actions: Assess accuracy of representations about deliverable completeness
enables actions: Identify when funding-contingent assertions are misleading
enables actions: Recognize when a justification for incomplete work borders on fraud
enables actions: Refrain from misrepresenting incomplete documents as adequate
required for obligations: Deliverable Completeness Disclosure Obligation
required for obligations: Public Funds Misrepresentation Avoidance Obligation
skill level: intermediate
text references: Engineer A's bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincing.
text references: Engineer A's comment about Federal funds borders on fraud and misrepresentation and is a clear violation of the NSPE Code.
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:55:58.579791+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A's bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincing.
comment: Capability to recognize when representations made to a client or funding authority about the completeness or adequacy of professional work products would be false or misleading, particularly in the context of publicly funded projects, and to refrain from making such representations even when doing so might secure continued funding or avoid disclosure of deficiencies.
subclass of: Capability
generated at time: 2026-06-04T16:55:58.579791+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Public Funds Misrepresentation Avoidance Obligation
type: Class
confidence: 0.86
derived from principle: Public Funds Stewardship Principle
enforcement level: mandatory
monitoring criteria: Whether the engineer made representations about funding remediation of deficiencies that were unsupported and served to conceal incomplete deliverables
nspe reference: III.2.a, II.5.a
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Funding agency
stakeholders affected: General public
stakeholders affected: Taxpayers
text references: Engineer A's bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincing.
text references: Engineer A's comment about Federal funds borders on fraud and misrepresentation and is a clear violation of the NSPE Code.
violation consequences: Professional discipline for deceptive acts; potential fraud findings; misuse of public funds
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:54:40.172403+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer A's comment about Federal funds borders on fraud and misrepresentation and is a clear violation of the NSPE Code.
comment: Duty of an engineer engaged on a publicly funded project to refrain from representations to the client, funding agency, or approving authority that incomplete or deficient work is acceptable or will be remedied by anticipated public funding, when such representations are unsupported and serve to conceal the engineer's failure to deliver a complete and conforming work product.
subclass of: EthicalObligation
generated at time: 2026-06-04T16:54:40.172403+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Public Funds Misrepresentation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Federal Funding Agency
affected stakeholders: Public
confidence: 0.88
constraint type: ethical
flexibility: hard
mitigation strategies: Deliver complete work products before representing them as adequate
mitigation strategies: Disclose incompleteness explicitly rather than relying on anticipated funding
mitigation strategies: Obtain verified funding commitments before making representations about project adequacy
text references: Engineer A's bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincing
text references: Engineer A's comment about Federal funds borders on fraud and misrepresentation and is a clear violation of the NSPE Code
violation impact: Professional ethics violation; potential fraud and misrepresentation liability; loss of public trust; project cost overruns borne by public
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:56:15.795068+00:00
first discovered in case: 85
match confidence: 0.75
match reasoning: The prohibition on misrepresenting incomplete work as adequate by relying on unverified public funding assumptions is a specific application of the general non-deception constraint. The Cost Assumption Neutrality Constraint extracted from prior sections addresses the rationalization aspect, while this constraint addresses the affirmative misrepresentation to the client and funding agency. It is a variant of Non-Deception rather than a fully new class, but the public-funds-specific framing and fraud-border characterization give it enough specificity to warrant a distinct class.
matched ontology class: Non Deception
matched ontology label: Non-Deception (Constraint)
matches existing: true
source text: Engineer A's bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincing
comment: Ethical and legal constraint prohibiting an engineer from representing to a client or funding agency that incomplete or inadequate work products are acceptable or sufficient on the basis of an assumption that public funds will be awarded to remedy the deficiency. Such representations border on fraud and misrepresentation and violate professional ethics codes regardless of the engineer's subjective belief that funding will materialize.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [Non_Deception] Constraint established by ethics code provisions
generated at time: 2026-06-04T16:56:15.795068+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Public Funds Stewardship Principle
type: Class
abstract nature: Principle requiring contextual interpretation of what constitutes unjustified expenditure and deceptive conduct in the public funding context, and recognition that the public interest in fiscal integrity is a professional concern even absent a safety dimension.
confidence: 0.83
derived obligations: Avoid misrepresentations about project completeness to public funding authorities
derived obligations: Complete work to applicable standards without deferring deficiencies to future public funding
derived obligations: Report unjustified expenditure of public funds as a matter of professional right and potentially of duty
extensional examples: BER Case No. 82-5 involving excessive subcontractor costs on a defense contract
extensional examples: BER dam design case involving Engineer A's assertion that federal funds would remedy incomplete design work
operationalization: Requires engineers on publicly funded projects to avoid misrepresentations about project status, to complete work to applicable standards without relying on anticipated future public funding to remedy known deficiencies, and to report unjustified expenditures of public funds even when not required by safety obligations.
potential conflicts: Client Loyalty Limits
potential conflicts: Confidentiality Principle
potential conflicts: Faithful Agent Duty Principle
principle category: domain_specific
text references: Engineer A's comment about Federal funds borders on fraud and misrepresentation and is a clear violation of the NSPE Code
text references: the case did not involve a danger to the public health or safety, but related to a claim of unsatisfactory plans and the unjustified expenditure of public funds
text references: the issue does not allege a danger to public health or safety, but is premised upon a claim of unsatisfactory plans and the unjustified expenditure of public funds
value basis: Public trust in the integrity of publicly funded infrastructure projects, accountability to taxpayers and public funding authorities, and the special obligations that attach to work performed with public resources.
discovered in case: 76
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:53:07.457315+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: the case did not involve a danger to the public health or safety, but related to a claim of unsatisfactory plans and the unjustified expenditure of public funds
comment: Professional principle establishing that engineers engaged on publicly funded projects bear a heightened responsibility to avoid deceptive acts, misrepresentations, and conduct that results in the unjustified expenditure of public funds, even when the conduct does not rise to the level of a direct public health or safety threat. The use of public funds imposes an affirmative obligation of honesty and completeness that goes beyond the minimum duties owed to a private client.
subclass of: DomainSpecificPrinciple
generated at time: 2026-06-04T16:53:07.457315+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Public Health Risk Disclosure Obligation
type: Class
confidence: 0.87
derived from principle: Proactive Risk Disclosure Principle
enforcement level: mandatory
monitoring criteria: Documented disclosure of the specific risk, its technical basis, and the conditions triggering it, communicated to the client and relevant authorities before the risk-creating action is taken
nspe reference: I.1, II.1.a, II.3.b
obligation type: disclosure
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: Regulatory bodies
stakeholders affected: Water consumers
text references: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards.
violation consequences: Public health harm; professional discipline; potential legal liability
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:23:42.907966+00:00
first discovered in case: 76
match confidence: 0.83
match reasoning: The obligation closely matches the existing Preliminary Risk Disclosure Obligation, which covers the duty to disclose identified risks to public health or safety to the client and relevant stakeholders promptly. The present case involves a fully characterized rather than merely preliminary risk, but the core disclosure duty is the same concept.
matched ontology class: Preliminary Risk Disclosure Obligation
matched ontology label: Preliminary Risk Disclosure Obligation
matches existing: true
source text: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards.
comment: Duty of an engineer who identifies a specific, quantified risk to public health, such as lead leaching from service pipes exceeding drinking water standards, to disclose that risk clearly and completely to the client and to the public or regulatory authority, including the technical basis for the risk assessment and the conditions under which the risk will materialize.
subclass of: DisclosureObligation
scope note: [PreliminaryRiskDisclosureObligation] Duty of an engineer who identifies a potential risk to public health or safety during a preliminary phase of work to disclose that risk to the client and relevant stakeholders promptly, even before the risk has been fully quantified, so that the client can make informed decisions about project scope, suspension, or protective measures.
generated at time: 2026-06-05T11:23:42.907966+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Public Safety Reporting Capability
type: Class
capability category: reasoning
confidence: 0.93
domain specificity: Environmental and stormwater engineering regulatory reporting
enables actions: Act on the public safety paramount obligation despite client instructions to the contrary
enables actions: Recognize when a client's refusal to implement safety measures triggers a public safety reporting obligation
enables actions: Report identified stormwater risks to the appropriate regulatory or pollution control authority
required for obligations: Client Refusal Regulatory Reporting Obligation
skill level: advanced
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: local environmental standards require steps to safeguard public water sources
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.93
match reasoning: Public Safety Paramount Judgment Capability is defined as the capability to recognize that the professional obligation to hold paramount the safety, health, and welfare of the public takes precedence over duties of loyalty to a client or former client, and to act on that recognition by taking affirmative steps such as regulatory reporting even when doing so is adverse to the client's interests. This is a direct match at high confidence.
matched ontology class: Public Safety Paramount Judgment Capability
matched ontology label: Public Safety Paramount Judgment Capability
matches existing: true
source text: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
comment: Capability to recognize that the professional obligation to hold paramount the safety, health, and welfare of the public takes precedence over duties of loyalty to a client, and to act on that recognition by taking affirmative steps such as regulatory reporting even when doing so is adverse to the client's interests.
subclass of: Capability
scope note: [PublicSafetyParamountJudgmentCapability] Capability to recognize that the professional obligation to hold paramount the safety, health, and welfare of the public takes precedence over duties of loyalty to a client or former client, and to act on that recognition by taking affirmative steps such as regulatory reporting even when doing so is adverse to the client's interests.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Public Water Commission
type: Class
confidence: 0.82
role category: provider_client
text references: the MWC has been considering changing its water supply source
text references: the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T11:17:25.675106+00:00
first discovered in case: 76
match confidence: 0.78
match reasoning: The MWC is a municipal or quasi-governmental body commissioning engineering services and acting as the primary decision-maker, which aligns with Municipal Client. The commission structure with voting authority over technical recommendations is a specialization of that existing class.
matched ontology class: Municipal Client
matched ontology label: Municipal Client
matches existing: true
source text: the MWC has been considering changing its water supply source
comment: A public governing body responsible for overseeing a municipal water utility, making policy and infrastructure decisions on water supply sources and capital expenditures, and acting as the client and decision-making authority for professional engineering services retained by the utility, with the power to override technical recommendations made by its own engineers.
subclass of: ProviderClientRole
subclass of: PublicRole
scope note: [MunicipalClient] A government or municipal entity that commissions professional engineering or construction services for public infrastructure projects, acting as the primary client and decision-maker but without professional engineering licensure.
generated at time: 2026-06-05T11:17:25.675106+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Public Water Supply Protection Standard Resource
type: Class
authority source: Environmental protection agencies and professional engineering bodies
confidence: 0.8
extensional function: Provides collective professional and regulatory agreement on acceptable practices for preventing contamination of community drinking water supplies, grounding engineering design obligations in documented technical criteria.
resource category: technical_standard
text references: ensuring that stormwater from the new development will not impact this primary drinking water source for the community
text references: local environmental standards require steps to safeguard public water sources
usage context: Public health risk assessment
usage context: Stormwater management design near drinking water sources
usage context: Watershed protection engineering
discovered in case: 8
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T09:57:35.025217+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: local environmental standards require steps to safeguard public water sources
comment: Technical or regulatory standards specifying design and operational requirements for protecting public drinking water sources from contamination, including stormwater runoff controls and watershed management criteria.
subclass of: TechnicalStandard
generated at time: 2026-06-04T09:57:35.025217+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Public Welfare Paramountcy Principle
type: Class
abstract nature: Open-textured value requiring case-by-case interpretation of what constitutes a sufficient threat to public welfare to trigger disclosure or refusal obligations, and how to balance against competing duties of loyalty and confidentiality.
confidence: 0.97
derived obligations: Disclose identified safety and environmental risks to affected parties and authorities
derived obligations: Prioritize public health over client economic concerns when the two conflict
derived obligations: Refuse to continue work when client declines to implement necessary protective measures
extensional examples: BER Case 22-5 and BER Case 20-4: emphasis on safe drinking water as public welfare concern
extensional examples: BER Case 76-4: Engineer Doe obligated to report discharge findings to Pollution Control Authority despite client instruction to suppress written report
extensional examples: BER Case 84-5: Engineer A violated Code by continuing project after client refused safety representative, subordinating public welfare to client economic concerns
operationalization: Requires engineers to disclose known safety risks to appropriate authorities, refuse to continue work that creates unmitigated public risk, and resist client pressure to suppress or ignore safety findings.
potential conflicts: Client Loyalty Limits
potential conflicts: Confidentiality Principle
potential conflicts: Faithful Agent Duty Principle
principle category: fundamental_ethical
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
text references: Section 2(a) requires that his duty to the public be paramount.
text references: a code of ethics is of course a statement of commitment from a particular profession to assist its members in the protection of the public health and safety
text references: it is basic to the entire concept of a profession that its members will devote their interests to the public welfare
value basis: The foundational justification for professional licensure and regulation is protection of the public, who cannot independently assess the safety of engineered works and must rely on professional integrity.
discovered in case: 8
discovered in case: 76
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:05:37.970804+00:00
first discovered in case: 8
match confidence: 0.93
match reasoning: This principle maps directly to the existing Public Welfare Principle and Public Welfare Paramount classes in the ontology. The case text explicitly invokes NSPE Canon I.1 and the paramountcy formulation. The existing Public Welfare Principle class covers this concept; the individual record captures the case-specific application.
matched ontology class: PublicWelfarePrinciple
matched ontology label: Public Welfare Principle
matches existing: true
source text: Section 2(a) requires that his duty to the public be paramount.
comment: Fundamental principle requiring engineers to hold paramount the safety, health, and welfare of the public above all competing professional obligations, including duties of loyalty to clients and employers. This principle is the highest-order canon in engineering ethics and cannot be overridden by client economic concerns, contractual relationships, or instructions to suppress findings.
subclass of: FundamentalEthicalPrinciple
scope note: [PublicWelfarePrinciple] Requires contextual interpretation to balance against client confidentiality and employer loyalty when public safety is at risk.
generated at time: 2026-06-04T10:05:37.970804+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Public Works Director
type: Class
confidence: 0.8
role category: participant
text references: BER Case No. 00-5 centered on the reopening of a dangerous, closed bridge by a nonengineer public works director
discovered in case: 76
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T11:18:16.149700+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: BER Case No. 00-5 centered on the reopening of a dangerous, closed bridge by a nonengineer public works director
comment: A non-engineer public official who holds administrative authority over public works infrastructure and may make operational decisions affecting public safety, including decisions that override professional engineering recommendations.
subclass of: PublicRole
subclass of: RelationalRole
generated at time: 2026-06-05T11:18:16.149700+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Qualitative Risk Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.78
constraint type: ethical
flexibility: soft
mitigation strategies: Disclose the qualitative risk estimate with explicit notation of its preliminary or unquantified character
mitigation strategies: Document the basis for the qualitative estimate and the limitations of the analysis
mitigation strategies: Recommend further study to quantify the risk while simultaneously disclosing the qualitative finding
text references: Engineer L conducts additional studies and qualitatively estimates the risk that heavy rainfall could lead to stormwater runoff from the development reaching the nearby watershed and community drinking water source.
text references: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
violation impact: Client and regulatory authorities are deprived of material safety information, potentially allowing a known risk to persist without protective action while the engineer awaits a level of certainty that may not be achievable within the project timeline.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:06.761320+00:00
first discovered in case: 8
match confidence: 0.75
match reasoning: The existing Concern Versus Fact Disclosure Constraint addresses the boundary between preliminary concerns and established facts for disclosure purposes. The qualitative risk scenario here is closely related: Engineer L has moved beyond a mere concern to a qualitative estimate, which sits between a preliminary concern and a fully quantified finding. The existing class addresses this spectrum and its disclosure implications. This is a variant match at medium confidence, as the existing class covers the conceptual territory though the qualitative-estimate framing is a specific application.
matched ontology class: Concern Versus Fact Disclosure Constraint
matched ontology label: Concern Versus Fact Disclosure Constraint
matches existing: true
source text: Engineer L conducts additional studies and qualitatively estimates the risk that heavy rainfall could lead to stormwater runoff from the development reaching the nearby watershed and community drinking water source.
comment: Ethical and professional constraint establishing that an engineer who has conducted sufficient analysis to form a qualitative estimate of a risk to public health or safety is obligated to disclose that estimate to the client and, where applicable, to relevant regulatory authorities, even when a full quantitative characterization of the risk has not yet been completed. A qualitative finding that a risk exists and is material triggers disclosure obligations equivalent to those arising from a quantified finding.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [ConcernVersusFactDisclosureConstraint] Ethical constraint limiting an engineer's disclosure obligations to findings that have reached the level of established fact supported by technical analysis. A preliminary concern or suspicion that has not yet been substantiated by sufficient analysis does not trigger the same mandatory disclosure obligations as a confirmed factual finding, and an engineer is not required under professional ethics codes to disclose unsubstantiated concerns, though prudent disclosure may be advisable.
generated at time: 2026-06-05T02:22:06.761320+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Qualitative Risk Estimation Capability
type: Class
capability category: domain_specific
confidence: 0.72
domain specificity: Environmental and stormwater engineering risk assessment
enables actions: Communicate the basis and limitations of a qualitative risk estimate to a client
enables actions: Estimate stormwater runoff risk to a watershed using qualitative methods
enables actions: Identify when qualitative findings are sufficient to trigger disclosure or protective measure recommendations
required for obligations: Environmental Risk Quantification Obligation
required for obligations: Protective Measure Recommendation Obligation
skill level: advanced
text references: Engineer L conducts additional studies and qualitatively estimates the risk that heavy rainfall could lead to stormwater runoff from the development reaching the nearby watershed and community drinking water source.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.72
match reasoning: Environmental Risk Quantification Capability covers the technical capability to conduct sufficient analysis to quantify environmental risks, assess magnitude and likelihood of stormwater or discharge impacts on public water sources, and document the status of quantification work when full analysis cannot be completed. The present case involves a qualitative rather than fully quantitative estimate, which is a variant of the same core competency. The match is medium confidence because the existing class emphasizes quantification while the case involves a qualitative estimate, but both concern the same domain and the same obligation to characterize risk sufficiently to support disclosure and protective measure recommendations.
matched ontology class: Environmental Risk Quantification Capability
matched ontology label: Environmental Risk Quantification Capability
matches existing: true
source text: Engineer L conducts additional studies and qualitatively estimates the risk that heavy rainfall could lead to stormwater runoff from the development reaching the nearby watershed and community drinking water source.
comment: Technical capability to conduct and communicate a qualitative or semi-quantitative estimate of an environmental or public safety risk when full quantitative analysis is not yet feasible, including the ability to characterize the nature, direction, and approximate magnitude of a risk based on available evidence and professional judgment, and to recognize the limits of such an estimate.
subclass of: Capability
scope note: [EnvironmentalRiskQuantificationCapability] Technical capability to conduct sufficient analysis to quantify environmental risks identified during professional work, including the ability to assess the magnitude and likelihood of stormwater or discharge impacts on public water sources and to document the status of quantification work when full analysis cannot be completed.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Referral Alternative Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.78
constraint type: ethical
flexibility: soft
mitigation strategies: Disclose inability to provide complete objective analysis and withdraw from advisory role
mitigation strategies: Recommend a neutral third-party advisor
mitigation strategies: Refer client to publicly available or subscription resources covering all options
text references: Engineer A could have referred City Administrator to resources (whether library, free, or subscription) that provided complete analyses of the various methodologies. That would be a completely ethical informal response to an informal solicitation, involving no provision of engineering services.
violation impact: Client receives incomplete or biased guidance, professional gains unfair advantage, trust in advisory relationship is undermined.
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:48:44.763664+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A could have referred City Administrator to resources (whether library, free, or subscription) that provided complete analyses of the various methodologies. That would be a completely ethical informal response to an informal solicitation, involving no provision of engineering services.
comment: Ethical constraint establishing that when a professional cannot or should not provide a complete advisory service without incurring conflicts of interest or other ethical violations, the professional must offer the client a referral to independent resources or qualified third parties rather than providing a partial or self-serving substitute for that service.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
generated at time: 2026-06-04T08:48:44.763664+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Referral Resource Identification Capability
type: Class
capability category: awareness
confidence: 0.82
domain specificity: Professional engineering advisory practice, particularly project delivery method selection
enables actions: Decline partial advisory engagement in favor of neutral referral
enables actions: Identify publicly available resources relevant to client inquiry
enables actions: Refer client to complete third-party analyses
required for obligations: Advisory Role Objectivity Obligation
required for obligations: Complete Options Advisory Obligation
required for obligations: Self-Serving Advisory Avoidance Obligation
skill level: intermediate
text references: Engineer A could have referred City Administrator to resources (whether library, free, or subscription) that provided complete analyses of the various methodologies. That would be a completely ethical informal response to an informal solicitation, involving no provision of engineering services.
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:48:46.347963+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A could have referred City Administrator to resources (whether library, free, or subscription) that provided complete analyses of the various methodologies. That would be a completely ethical informal response to an informal solicitation, involving no provision of engineering services.
comment: Capability to identify and direct clients to appropriate external resources, such as publicly available analyses, library materials, or subscription references, as an ethical alternative to providing partial or self-serving professional advisory services, particularly when a full engagement would create a conflict of interest.
subclass of: Capability
generated at time: 2026-06-04T08:48:46.347963+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Authority
type: Class
confidence: 0.9
role category: public_responsibility
text references: Engineer A had an obligation to first advise Engineer B that Engineer A had an obligation to inform the appropriate authorities, and then to so inform the appropriate authorities
discovered in case: 15
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-02T19:52:44.921838+00:00
first discovered in case: 15
match confidence: 0.9
match reasoning: The appropriate authorities referenced in the text are precisely the code-enforcement officials and government oversight bodies described by the Regulatory Authority Role in the ontology.
matched ontology class: RegulatoryAuthorityRole
matched ontology label: Regulatory Authority Role
matches existing: true
source text: Engineer A had an obligation to first advise Engineer B that Engineer A had an obligation to inform the appropriate authorities, and then to so inform the appropriate authorities
comment: A government body, code-enforcement official, or oversight authority to whom engineers must report safety violations that cannot be resolved through direct professional dialogue, overriding confidentiality obligations when public health, safety, and welfare are at risk.
subclass of: PublicResponsibilityRole
subclass of: RegulatoryAuthorityRole
scope note: [RegulatoryAuthorityRole] Code-enforcement officials, inspectors, boards, and government agencies acting in an oversight capacity. No IFC equivalent (IFC has no regulator role).
generated at time: 2026-06-02T19:52:44.921838+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Authority Presentation Obligation
type: Class
confidence: 0.85
derived from principle: Public Welfare Paramountcy Principle
enforcement level: mandatory
monitoring criteria: Documented formal submission or presentation of findings and recommendations to the state regulatory agency
nspe reference: I.1, II.1.a, II.1.c
obligation type: reporting
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: State regulatory agency
stakeholders affected: Water consumers
text references: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.
text references: Despite those recommendations, the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source.
violation consequences: Continued public health risk; professional discipline; potential legal liability
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:23:42.907966+00:00
first discovered in case: 76
match confidence: 0.82
match reasoning: This obligation is a contextual variant of the existing Client Override Public Safety Reporting Obligation, with the distinguishing feature that the escalation target is specifically a state regulatory agency and the mechanism is a formal presentation of facts and findings. The core duty is the same: report to appropriate authority when client overrides safety recommendations.
matched ontology class: Client Override Public Safety Reporting Obligation
matched ontology label: Client Override Public Safety Reporting Obligation
matches existing: true
source text: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.
comment: Duty of an engineer who has identified a public health or safety risk and whose client has overridden protective recommendations to formally present the facts, findings, and recommendations to the appropriate state or federal regulatory authority, so that the authority can exercise its oversight function and protect the public.
subclass of: ReportingObligation
scope note: [ClientOverridePublicSafetyReportingObligation] Duty of an engineer to report identified risks to public health or safety to the appropriate regulatory or pollution control authority when the client refuses to implement recommended protective measures and insists on proceeding without adequate safeguards, placing the paramount duty to public welfare above the faithful agent duty to the client.
generated at time: 2026-06-05T11:23:42.907966+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Escalation Obligation
type: Class
confidence: 0.9
derived from principle: Graduated Response Proportionality Principle
enforcement level: conditional
monitoring criteria: Documented evidence that the engineer reported the unresolved violation to the appropriate federal or state authority after the client failed to remediate within a reasonable period.
nspe reference: I.1, II.1.a, II.1.c
obligation type: reporting
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: If appropriate steps are not taken by the client, the engineer would have an obligation to bring this matter to the attention of the appropriate authorities.
violation consequences: Failure to escalate to regulatory authorities after client inaction leaves a known public welfare risk unaddressed and constitutes a breach of the paramount duty under NSPE I.1.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:34:19.889581+00:00
first discovered in case: 86
match confidence: 0.8
match reasoning: This obligation is a close variant of the Post-Termination Environmental Risk Reporting Obligation and the Client Override Public Safety Reporting Obligation. It differs in that it is triggered not by client override of a recommendation but by client failure to remediate after being contacted, and it follows a graduated response sequence. The conditional trigger and the graduated-response framing distinguish it sufficiently to warrant a medium-confidence match rather than a full identity match.
matched ontology class: PostTermEnvRiskReportingObligation
matched ontology label: Post-Termination Environmental Risk Reporting Obligation
matches existing: true
source text: If appropriate steps are not taken by the client, the engineer would have an obligation to bring this matter to the attention of the appropriate authorities.
comment: Duty of an engineer who has contacted a client about a legal or regulatory violation and monitored the situation to report the violation to the appropriate regulatory authority when the client fails to take adequate remedial steps within a reasonable time, placing the paramount duty to public welfare above any residual loyalty to the client.
subclass of: ReportingObligation
scope note: [PostTermEnvRiskReportingObligation] Duty of an engineer to report environmental risks to a pollution-control authority after termination of the client relationship when the risk rises to a public-safety concern (NSPE Code §I.1, §II.1.a, §II.1.c). Derived from the paramount public-welfare principle.
generated at time: 2026-06-04T17:34:19.889581+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Option Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Funding Agency
affected stakeholders: Public
confidence: 0.8
constraint type: regulatory
flexibility: hard
mitigation strategies: Advise client to verify approved methods directly with the funding agency
mitigation strategies: Cite the governing funding source documentation when presenting options
mitigation strategies: Review and accurately convey all funding-agency-approved options to the client
text references: City B's City Administrator asked Engineer A for a recommendation on project delivery methods for their upcoming wastewater system improvements project using a specific funding source.
text references: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
violation impact: Client may select a non-compliant delivery method, jeopardizing funding eligibility and project viability
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:47.831992+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
comment: Constraint arising when a specific funding source or regulatory authority limits the set of permissible project delivery methods, procurement approaches, or procedural options available to an owner, requiring that any professional advisor accurately represent those regulatory boundaries to the client rather than substituting the advisor's own narrower selection.
subclass of: InviolableConstraint
subclass of: RegulatoryConstraint
generated at time: 2026-06-04T08:45:47.831992+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Reporting Authority Identification Capability
type: Class
capability category: norm_management
confidence: 0.8
domain specificity: Environmental engineering and regulatory compliance, particularly wetland and water resource regulation
enables actions: Determine whether concurrent reporting to multiple agencies is required
enables actions: Identify the appropriate federal authority for wetland fill violations
enables actions: Identify the appropriate state authority for wetland fill violations
required for obligations: Environmental Compliance Reporting Obligation
required for obligations: Observed Violation Disclosure Obligation
required for obligations: Post-Engagement Violation Reporting Obligation
skill level: advanced
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:31:02.848953+00:00
first discovered in case: 86
match confidence: 0.76
match reasoning: Regulatory Reporting Trigger Recognition Capability covers recognizing when findings must be reported to a regulatory or pollution control authority and identifying the appropriate authority. The present capability focuses specifically on the authority identification and jurisdictional selection dimension rather than the trigger recognition dimension. It is a closely related variant of the existing class, warranting a new class to capture the distinct authority-identification competency that is required once the reporting trigger has been recognized.
matched ontology class: Regulatory Reporting Trigger Recognition Capability
matched ontology label: Regulatory Reporting Trigger Recognition Capability
matches existing: true
source text: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
comment: Capability to identify the specific federal and state regulatory authorities to whom a discovered violation of environmental law must be reported, including the ability to determine jurisdictional scope and select the appropriate reporting channel when multiple authorities may have concurrent jurisdiction.
subclass of: Capability
scope note: [RegulatoryReportingTriggerRecognitionCapability] Capability to recognize when identified professional findings about public health or safety risks must be reported to a regulatory or pollution control authority, including the ability to identify the appropriate authority and to act on that obligation even when the client has instructed the engineer not to complete or submit a report.
generated at time: 2026-06-04T17:31:02.848953+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Reporting Trigger Capability
type: Class
capability category: norm_management
confidence: 0.92
domain specificity: Environmental and stormwater engineering regulatory compliance
enables actions: Act on the reporting obligation despite client instructions to the contrary
enables actions: Determine the appropriate pollution control or regulatory authority to notify
enables actions: Identify when stormwater or environmental risk findings trigger a mandatory regulatory reporting obligation
required for obligations: Client Refusal Regulatory Reporting Obligation
skill level: advanced
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: local environmental standards require steps to safeguard public water sources
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.92
match reasoning: Regulatory Reporting Trigger Recognition Capability is defined as the capability to recognize when identified professional findings about public health or safety risks must be reported to a regulatory or pollution control authority, including the ability to identify the appropriate authority and to act on that obligation even when the client has instructed the engineer not to complete or submit a report. This matches the capability required in this case at high confidence.
matched ontology class: Regulatory Reporting Trigger Recognition Capability
matched ontology label: Regulatory Reporting Trigger Recognition Capability
matches existing: true
source text: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
comment: Capability to recognize when identified professional findings about public health or safety risks must be reported to a regulatory or pollution control authority, including the ability to identify the appropriate authority and to act on that reporting obligation even when the client has instructed the engineer to proceed without implementing recommended safeguards or has declined to authorize a report.
subclass of: Capability
scope note: [RegulatoryReportingTriggerRecognitionCapability] Capability to recognize when identified professional findings about public health or safety risks must be reported to a regulatory or pollution control authority, including the ability to identify the appropriate authority and to act on that obligation even when the client has instructed the engineer not to complete or submit a report.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Safety Compliance Obligation
type: Class
confidence: 0.88
derived from principle: Public Safety Paramount
enforcement level: mandatory
monitoring criteria: Verification that submitted design documents include all safety features required by applicable regulations, confirmed by systematic regulatory checklist review
nspe reference: I.1, II.1.a, II.1.c
obligation type: safety
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Client W raised concerns about the accuracy and reliability of the engineering design and instructed Engineer A to revise the plans, ensuring that all elements satisfied the necessary professional and regulatory standards.
text references: Client W, however, noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
violation consequences: Public safety risk; regulatory non-compliance; professional discipline; client harm; potential liability for injuries or regulatory penalties
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:05:12.288818+00:00
first discovered in case: 7
match confidence: 0.8
match reasoning: This obligation is a specialization of the existing Safety Obligation, focused specifically on regulatory compliance in design documents. The existing Safety Obligation covers the general duty to hold paramount public safety, and the external reference standard 'Comply with Applicable Safety Standards' is closely related. A distinct class is warranted because this obligation specifically addresses regulatory compliance verification in submitted design documents rather than the broader public welfare principle.
matched ontology class: SafetyObligation
matched ontology label: Safety Obligation
matches existing: true
source text: Client W, however, noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
comment: Duty of an engineer preparing engineering design documents to ensure that all plans and specifications comply with applicable local, state, and federal regulatory safety requirements before submission, regardless of the method used to generate the documents.
subclass of: SafetyObligation
scope note: [SafetyObligation] Duty to hold paramount the safety, health, and welfare of the public (NSPE I.1)
generated at time: 2026-06-03T14:05:12.288818+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Remediation Monitoring Capability
type: Class
capability category: awareness
confidence: 0.88
domain specificity: Environmental and regulatory compliance contexts where a professional has notified a client of a violation and must track follow-through
enables actions: Assess adequacy of corrective steps against regulatory requirements
enables actions: Determine when remediation is sufficient to close the reporting loop
enables actions: Identify when promised remediation has not materialized
enables actions: Monitor client remedial actions after violation notification
required for obligations: Regulatory Escalation Obligation
required for obligations: Remediation Monitoring Obligation
skill level: intermediate
text references: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
text references: the engineer should advise that the all remedial actions should be in full compliance with all applicable environmental laws and regulations, which may include the review of a licensed engineer
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:36:09.645175+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
comment: Capability to monitor a client's or former client's remedial actions following notification of a legal or regulatory violation, including the ability to assess whether promised corrective steps are actually being taken, to evaluate whether those steps are adequate and compliant with applicable law, and to determine when the situation has been sufficiently remedied to satisfy the engineer's professional obligations.
subclass of: Capability
generated at time: 2026-06-04T17:36:09.645175+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Remediation Monitoring Obligation
type: Class
confidence: 0.87
derived from principle: Client Conduct Monitoring Principle
enforcement level: conditional
monitoring criteria: Engineer maintains documented follow-up records confirming that remedial actions were completed and comply with all applicable environmental laws and regulations.
nspe reference: I.1, II.1.a
obligation type: reporting
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
text references: In this connection, the engineer should advise that the all remedial actions should be in full compliance with all applicable environmental laws and regulations, which may include the review of a licensed engineer.
violation consequences: Failure to monitor allows a client's unfulfilled remediation promise to stand unchallenged, leaving the public welfare risk unresolved and the engineer in constructive breach of the paramount duty.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:34:19.889581+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: If the client indicates that those steps will be taken, the engineer should monitor the situation until the engineer is sufficiently satisfied that the situation has been remedied.
comment: Duty of an engineer who has notified a client of a legal or regulatory violation and received assurances of remediation to monitor the client's actual remedial actions until the engineer is sufficiently satisfied that the violation has been fully corrected in compliance with applicable law.
subclass of: ReportingObligation
generated at time: 2026-06-04T17:34:19.889581+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Report Completeness Integrity Capability
type: Class
capability category: reasoning
confidence: 0.85
domain specificity: Professional engineering reporting and advisory practice across domains
enables actions: Audit a draft report for omitted or selectively excluded information
enables actions: Ensure advisory memos include all relevant methodologies, pros, and cons
enables actions: Identify when partial presentation of options or data would mislead the recipient
required for obligations: Complete Options Advisory Obligation
required for obligations: Report Completeness Obligation
required for obligations: Self-Serving Advisory Avoidance Obligation
skill level: advanced
text references: BER Case 95-5 addressed integrity and completeness in preparing reports. The engineer in question rendered an opinion that... failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal (intentional disregard of other information); that the test equipment had failed (selective use of information).
text references: BER Case 99-8 was relatively analogous. Engineer A submitted plans that were lacking much of the design detail in both drawings and specifications.
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information (as in 95-5 and 99-8)
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:48:46.347963+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: BER Case 95-5 addressed integrity and completeness in preparing reports. The engineer in question rendered an opinion that... failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal (intentional disregard of other information); that the test equipment had failed (selective use of information).
comment: Capability to recognize when a professional report, memo, or advisory product omits material information, selectively presents data, or disregards contrary evidence, and to ensure that all relevant and pertinent information is included so that the product is not misleading or self-serving.
subclass of: Capability
generated at time: 2026-06-04T08:48:46.347963+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Deficit State
type: Class
action constraints: Must not affix signature to plans reviewed only after preparation without involvement in development
action constraints: Must not delegate engineering judgment entirely to AI tools
activation conditions: Professional signs or seals documents without active involvement in design and development
activation conditions: Reliance on AI or other tools substitutes for engineering judgment
activation conditions: Review limited to post-preparation checking without supervisory direction during preparation
confidence: 0.89
obligation activation: Duty to engage actively in the engineering process from conception to completion
obligation activation: Duty to make engineering decisions personally or through supervised subordinates
obligation activation: Duty to refrain from sealing documents not under genuine direction and control
persistence type: inertial
principle transformation: Transforms the responsible charge and public safety principles into a concrete prohibition on passive post-hoc review as a substitute for active supervisory engagement throughout the engineering process.
state category: competence
termination conditions: Comprehensive verification process established
termination conditions: Professional re-engages with active supervisory direction and control
termination conditions: Responsible charge obligations demonstrably satisfied
text references: Engineer A did not maintain responsible charge in violation of licensure law which violates Code section III.8.a.
text references: Engineer A, as the engineer in Responsible Charge of the project, is required to provide an experienced-based quality assurance review, engaging in critical discussions, mentorship, and professional development.
text references: Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.
discovered in case: 7
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-03T14:01:36.958645+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A did not maintain responsible charge in violation of licensure law which violates Code section III.8.a.
comment: State in which a professional engineer has failed to maintain the active engagement, supervisory direction, and control authority required by responsible charge standards, whether due to over-reliance on automated tools, absence of mentorship support, or insufficient involvement in the design and development process, such that the professional's seal or signature does not reflect genuine oversight.
subclass of: CompetenceState
generated at time: 2026-06-03T14:01:36.958645+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Definition Resource
type: Class
authority source: National Society of Professional Engineers
confidence: 0.88
extensional function: Grounds the abstract obligation of responsible charge in concrete behavioral criteria, enabling engineers and reviewers to assess whether adequate oversight was exercised over engineering work including AI-generated outputs.
resource category: reference_material
text references: NSPE defines 'Responsible Charge' in NSPE Position Statement No. 10-1778 as 'being actively engaged in the engineering process, from conception to completion.'
usage context: Assessing direction and control of engineering deliverables
usage context: Determining licensure compliance
usage context: Evaluating adequacy of engineer oversight
discovered in case: 7
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-03T14:00:46.675889+00:00
first discovered in case: 7
match confidence: 0.78
match reasoning: NSPE Position Statement No. 10-1778 is a supporting policy document that defines a professional practice concept. It functions as reference material rather than a professional code provision, technical standard, or case precedent. No existing class captures position statements defining responsible charge specifically, so matching to the Reference Material base class at medium confidence.
matched ontology class: ReferenceM
matched ontology label: Reference Material
matches existing: true
source text: NSPE defines 'Responsible Charge' in NSPE Position Statement No. 10-1778 as 'being actively engaged in the engineering process, from conception to completion.'
comment: An official position statement or policy document issued by a professional engineering society that defines the concept of responsible charge, specifying what constitutes active engagement, supervisory direction, and control authority in engineering practice.
subclass of: ReferenceMaterial
scope note: [ReferenceMaterial] Supporting documentation for professional practice
generated at time: 2026-06-03T14:00:46.675889+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Direction Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory bodies
confidence: 0.87
constraint type: regulatory
flexibility: hard
mitigation strategies: Conduct comprehensive verification of all AI-generated outputs
mitigation strategies: Establish solution guidelines and constraints before initiating AI-assisted drafting
mitigation strategies: Maintain documented evidence of active involvement throughout design process
mitigation strategies: Obtain qualified assistance when mentor or supervisor is unavailable
text references: Code section II.2.b states that, '[e]ngineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control.'
text references: Much like directing an engineering intern to solve a problem, responsible use of AI requires an engineer to outline solution guidelines and constraints.
text references: NSPE defines 'Responsible Charge' in NSPE Position Statement No. 10-1778 as 'being actively engaged in the engineering process, from conception to completion. Engineering decisions must be personally made by the professional engineer or by others over which the professional engineer provides supervisory direction and control authority. Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.'
violation impact: Violation of licensure law, submission of deficient or unsafe work products, regulatory noncompliance, public safety hazard, professional discipline
discovered in case: 7
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:08.316438+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Code section II.2.b states that, '[e]ngineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control.'
comment: Regulatory and ethical constraint requiring that an engineer in responsible charge actively direct and control the preparation of engineering work products from conception through completion, including outlining solution guidelines and constraints before delegating to any tool or subordinate, and critically evaluating outputs rather than accepting them without independent judgment. Reviewing completed documents after preparation without involvement in the design process does not satisfy this requirement.
subclass of: InviolableConstraint
subclass of: RegulatoryConstraint
generated at time: 2026-06-03T14:11:08.316438+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Integrity Principle
type: Class
abstract nature: The meaning of substantive oversight depends on the complexity of the work, the tools used, and the applicable regulatory framework, requiring engineers to interpret what genuine responsible charge demands in each context.
confidence: 0.87
derived obligations: Ensure AI-generated content meets professional and regulatory standards before sealing
derived obligations: Identify errors and omissions before submitting sealed documents
derived obligations: Perform substantive technical review of all sealed work products
derived obligations: Seek additional review when personal competence or capacity is insufficient
extensional examples: Engineer applying seal to work prepared by others without independent verification
extensional examples: Engineer of record delegating substantive technical judgment to automated tools
extensional examples: Engineer sealing AI-generated design documents after only cursory review
operationalization: Requires engineers to perform independent technical review proportionate to the complexity and risk of the work, to identify and correct errors before sealing, and to refuse to seal work they have not genuinely reviewed.
potential conflicts: Client expectations for timely delivery
potential conflicts: Loss of mentorship or supervisory support
potential conflicts: Time pressure and project deadlines
principle category: professional_virtue
text references: Client W, however, noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
text references: submitted the draft report to Client W for review, including language to clearly identify that the supplied report was a draft, but applied their seal consistent with state law.
value basis: The professional seal is a public representation that the engineer has exercised independent professional judgment over the work. Nominal or superficial review undermines the trust that licensure is designed to protect.
discovered in case: 7
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:03:55.305980+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
comment: Professional virtue principle requiring the engineer of record to exercise genuine, substantive oversight of all work performed under their seal, including work generated by automated or AI-assisted tools, ensuring that the seal represents authentic professional judgment rather than nominal approval.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-03T14:03:55.305980+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Review Adequacy State
type: Class
action constraints: Engineer must not seal documents based solely on confidence in an automated system without independent verification
action constraints: Engineer must not seal documents based solely on general confidence in subordinates without detailed review
activation conditions: Documents were prepared by subordinates, registered engineers, or automated systems under the engineer's direction
activation conditions: Engineer seals documents not personally prepared by the engineer
activation conditions: Question arises whether the engineer's review was sufficiently detailed to satisfy responsible charge
confidence: 0.88
obligation activation: Obligation to assume full responsibility for the work product
obligation activation: Obligation to carefully direct, control, and review material prepared under responsible charge
obligation activation: Obligation to check and review documents in sufficient detail before sealing
persistence type: inertial
principle transformation: Transforms the sealing and responsible charge principle into a concrete obligation to perform detailed review, distinguishing between the impermissible practice of sealing without review and the permissible practice of sealing after sufficient direction, control, and review even without personal preparation.
state category: competence
termination conditions: Engineer completes a sufficiently detailed check and review of the documents
termination conditions: Engineer declines to seal the documents
text references: The key requirement is that an engineer possesses sufficient competence, assumes full responsibility for the work product and carefully directs, controls and reviews the material prepared under the engineer's responsible charge
text references: it would not be unethical for an engineer to sign and seal the drawings in question as long as those plans were checked and reviewed by the engineer in some detail
discovered in case: 120
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T18:05:44.602441+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: it would not be unethical for an engineer to sign and seal the drawings in question as long as those plans were checked and reviewed by the engineer in some detail
comment: State in which a professional engineer has sealed or is considering sealing engineering documents prepared by others, and the ethical permissibility of that sealing depends on whether the engineer has performed a sufficiently detailed check and review of the documents to satisfy responsible charge obligations, as distinguished from either personally preparing the documents or merely providing general supervisory oversight without detailed review.
subclass of: CompetenceState
generated at time: 2026-06-04T18:05:44.602441+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Seal Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Licensing Board
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.85
constraint type: regulatory
flexibility: hard
mitigation strategies: Consult state engineering seal law and professional society responsible charge definitions before sealing AI-assisted work
mitigation strategies: Decline to seal work products prepared by others or by AI tools without sufficient personal oversight
mitigation strategies: Document the nature and extent of supervisory direction exercised over each sealed work product
mitigation strategies: Maintain active involvement in the preparation of all work products bearing the engineer's seal
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
text references: submitted the draft report to Client W for review, including language to clearly identify that the supplied report was a draft, but applied their seal consistent with state law
violation impact: Invalid or fraudulent seal application, regulatory violation, license revocation, legal liability for deficient sealed documents, and public safety risk from reliance on improperly certified work.
discovered in case: 7
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:33.588436+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: submitted the draft report to Client W for review, including language to clearly identify that the supplied report was a draft, but applied their seal consistent with state law
comment: Regulatory and legal constraint requiring that a licensed professional engineer apply their professional seal only to work products over which they have exercised genuine responsible charge, meaning active supervisory direction and control throughout preparation, not merely a post-preparation review of a completed product.
subclass of: InviolableConstraint
subclass of: RegulatoryConstraint
generated at time: 2026-06-03T14:06:33.588436+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Safety Accountability Judgment Capability
type: Class
capability category: awareness
confidence: 0.8
domain specificity: Professional engineering accountability and quality assurance
enables actions: Assess the professional duty to consent to peer review
enables actions: Distinguish personal reluctance from professional obligation
enables actions: Recognize when prior errors trigger review obligations
required for obligations: Professional Accountability Cooperation Obligation
required for obligations: Safety Review Consent Obligation
skill level: advanced
text references: Engineer A objects and refused to consent to the peer review
text references: several significant design errors are discovered in the plans and design of Engineer A
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:30.046199+00:00
first discovered in case: 15
match confidence: 0.76
match reasoning: Recognizing that prior errors create an accountability obligation and that personal resistance to review is ethically impermissible is a form of ethical perception, specifically the ability to recognize ethically salient features of a situation as described by Anderson et al. 2006 and Berreby et al. 2017. This is a variant focused on accountability contexts, matched at medium confidence.
matched ontology class: EthicalPerception
matched ontology label: Ethical Perception
matches existing: true
source text: several significant design errors are discovered in the plans and design of Engineer A
comment: Capability to recognize that prior discovery of significant professional errors creates an obligation to support quality assurance processes, and to assess when consent to independent review is required as an expression of professional accountability.
subclass of: Capability
scope note: [EthicalPerception] Capability to recognize ethically salient features and dynamically assess environment (Anderson et al. 2006, Berreby et al. 2017)
generated at time: 2026-06-02T19:57:30.046199+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Safety Feature Compliance Obligation
type: Class
confidence: 0.9
derived from principle: Public Safety Paramount
enforcement level: mandatory
monitoring criteria: Design documents reviewed against applicable regulatory safety checklists prior to submission; no required safety features omitted
nspe reference: I.1
obligation type: safety
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Client W reviewed the design documents, they found misaligned dimensions and key safety features (including those necessary for compliance with local regulations) were omitted.
text references: The errors in the AI-generated design documents could have led to regulatory noncompliance and safety hazards, conflicting with the Fundamental Canon I.1, 'hold paramount the safety, health, and welfare of the public'.
violation consequences: Regulatory noncompliance; public safety hazard; disciplinary action; potential legal liability
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:09:34.826300+00:00
first discovered in case: 7
match confidence: 0.84
match reasoning: This obligation is a variant of the already-extracted Regulatory Safety Compliance Obligation, with specific emphasis on verifying that safety features required by local regulations are not omitted from AI-generated design documents.
matched ontology class: RegulatoryComplianceObligation
matched ontology label: Regulatory Safety Compliance Obligation
matches existing: true
source text: Client W reviewed the design documents, they found misaligned dimensions and key safety features (including those necessary for compliance with local regulations) were omitted.
comment: Duty of an engineer to ensure that engineering design documents include all safety features required by applicable local, state, and federal regulations, and to verify that AI-generated or otherwise automated design outputs have not omitted required safety elements before submission to a client or regulatory authority.
subclass of: SafetyObligation
generated at time: 2026-06-03T14:09:34.826300+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Safety Feature Recognition Capability
type: Class
capability category: domain_specific
confidence: 0.83
domain specificity: Engineering design review for regulatory and public safety compliance
enables actions: Assess regulatory compliance status of engineering design documents
enables actions: Flag safety deficiencies before document submission or sealing
enables actions: Identify safety features required by local regulations in design documents
enables actions: Recognize omissions of mandatory safety elements in AI-generated plans
required for obligations: Regulatory Safety Compliance Obligation
required for obligations: Safety Feature Compliance Obligation
skill level: advanced
text references: When Client W reviewed the design documents, they found misaligned dimensions and key safety features (including those necessary for compliance with local regulations) were omitted.
text references: failure to detect misaligned dimensions and omitted safety features further indicates that Engineer A did not exercise sufficient diligence. The errors in the AI-generated design documents could have led to regulatory noncompliance and safety hazards, conflicting with the Fundamental Canon I.1, 'hold paramount the safety, health, and welfare of the public'.
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:06.673267+00:00
first discovered in case: 7
match confidence: 0.74
match reasoning: The existing Engineering Design Error Recognition Capability covers identifying errors, omissions, and deficiencies in engineering plans including safety implications. The present capability is a more specific instantiation focused on safety feature recognition and regulatory compliance checking. A medium-confidence match to the existing class is appropriate, but the regulatory compliance and safety feature identification dimension is sufficiently distinct to warrant a separate class for precision.
matched ontology class: Engineering Design Error Recognition Capability
matched ontology label: Engineering Design Error Recognition Capability
matches existing: true
source text: When Client W reviewed the design documents, they found misaligned dimensions and key safety features (including those necessary for compliance with local regulations) were omitted.
comment: Technical capability to identify required safety features in engineering design documents, including the ability to recognize when AI-generated or otherwise prepared plans omit safety elements mandated by applicable regulations, and to assess the public safety implications of such omissions.
subclass of: Capability
scope note: [EngineeringDesignErrorRecognitionCapability] Technical capability to identify significant errors, omissions, or deficiencies in engineering plans and designs through independent review, including the ability to assess the severity and safety implications of discovered errors.
generated at time: 2026-06-03T14:11:06.673267+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Safety Reporting Engineer
type: Class
confidence: 0.87
role category: public_responsibility
text references: Engineers A and B have an obligation to further pursue the matter.
text references: If Engineers A and B believe life or property is endangered, Section II.1.a. provides that not only shall the employer or client be notified, but also all other appropriate authorities.
text references: it was unethical for Engineer A not to report the safety violations to the appropriate public authorities
discovered in case: 76
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T11:18:16.149700+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: If Engineers A and B believe life or property is endangered, Section II.1.a. provides that not only shall the employer or client be notified, but also all other appropriate authorities.
comment: A licensed professional engineering role in which the practitioner identifies a safety hazard affecting the public, exhausts direct channels with the client or employer, and bears an obligation to formally report findings and recommendations to all appropriate regulatory or governmental authorities when the client overrules the engineering judgment and public safety remains endangered.
subclass of: EngineerRole
subclass of: PublicResponsibilityRole
generated at time: 2026-06-05T11:18:16.149700+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Safety Review Consent Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Design Engineer
affected stakeholders: Public
affected stakeholders: Reviewing Engineer
confidence: 0.85
constraint type: safety
flexibility: soft
mitigation strategies: Document the refusal and the safety rationale for proceeding
mitigation strategies: Escalate to professional licensing board if consent is withheld
mitigation strategies: Proceed with peer review under client authorization even absent consent
text references: As the first tower is built, several significant design errors are discovered in the plans and design of Engineer A.
text references: Engineer A objects and refused to consent to the peer review.
text references: Owner decides to obtain a peer review of the plans and design of Engineer A for the second tower.
violation impact: Continued public safety risk from unreviewed designs with known defect history, potential liability for harm, and professional accountability failure.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:27.688172+00:00
first discovered in case: 15
match confidence: 0.82
match reasoning: This constraint maps to the existing Safety Constraint class, which covers constraints ensuring safety requirements are met. The specific application here is that known prior design defects create a safety imperative that limits the original engineer's ability to block independent review. It is a variant of Safety Constraint with the distinguishing feature of the consent limitation arising from confirmed prior defects.
matched ontology class: SafetyConstraint
matched ontology label: Safety Constraint
matches existing: true
source text: As the first tower is built, several significant design errors are discovered in the plans and design of Engineer A.
comment: Safety constraint establishing that when significant design defects have been confirmed in a professional's prior work, that professional cannot reasonably withhold consent to an independent peer review of related subsequent work, because public safety interests override individual professional prerogative.
subclass of: DefeasibleConstraint
subclass of: SafetyConstraint
scope note: [SafetyConstraint] Constraints ensuring safety requirements are met (Arkin 2008)
generated at time: 2026-06-02T19:57:27.688172+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Safety Review Consent Obligation
type: Class
confidence: 0.87
derived from principle: Public Safety Paramount
enforcement level: mandatory
monitoring criteria: Evidence that the design engineer consented to or cooperated with the peer review process when prior errors were established
nspe reference: I.1
obligation type: safety
stakeholders affected: Future occupants of the structure
stakeholders affected: General public
stakeholders affected: Project owner
stakeholders affected: Regulatory authorities
text references: As the first tower is built, several significant design errors are discovered in the plans and design of Engineer A.
text references: Engineer A objects and refused to consent to the peer review.
violation consequences: Potential endangerment of public safety; professional disciplinary action; liability for harm resulting from unreviewed defective designs
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:56:24.847658+00:00
first discovered in case: 15
match confidence: 0.8
match reasoning: This is a contextual specialization of the existing Safety Obligation class, applying the paramount public safety duty to the specific situation where a design engineer must cooperate with safety-motivated peer review. The existing Safety Obligation class directly covers the duty to hold paramount the safety, health, and welfare of the public.
matched ontology class: SafetyObligation
matched ontology label: Safety Obligation
matches existing: true
source text: As the first tower is built, several significant design errors are discovered in the plans and design of Engineer A.
comment: Duty of a design engineer to consent to independent peer review of their work when significant errors have been discovered in prior related work and public safety may be at risk, placing public welfare above personal reputational interests.
subclass of: SafetyObligation
scope note: [SafetyObligation] Duty to hold paramount the safety, health, and welfare of the public (NSPE I.1)
generated at time: 2026-06-02T19:56:24.847658+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Scope Exclusion Observation State
type: Class
action constraints: Professional may not alter or destroy field notes documenting the out-of-scope observation
action constraints: Scope limitation does not extinguish the duty to document and verbally report material safety observations
activation conditions: Client or prime consultant instructs professional to exclude the observation from the formal report
activation conditions: Professional observes a condition outside the contractual scope of services
activation conditions: The out-of-scope condition is material to safety, legal compliance, or professional accuracy
confidence: 0.84
obligation activation: Obligation to document observation in field notes regardless of scope
obligation activation: Obligation to follow up to confirm corrective action
obligation activation: Obligation to verbally report observation to client or prime consultant
persistence type: inertial
principle transformation: Transforms the contractual scope limitation into a bounded constraint that governs formal report content but does not eliminate the professional's independent duty to document and communicate material safety observations through appropriate channels.
state category: conflict
termination conditions: Observation is formally documented and communicated to responsible party
termination conditions: Professional escalates to authorities if corrective action is not taken
termination conditions: Responsible party takes corrective action
text references: Engineer A stated that he would retain the information from his engineering notes but not include it in the final report, as requested.
text references: Engineer A's scope of work was solely to identify any pavement damage on the bridge and report the damage to VWX for further review and repair.
text references: The public agency contacted VWX Architects and Engineers which then contacted Engineer A and asked Engineer A not to include this additional information in his final report since it was not part of his scope of work.
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:27:19.652589+00:00
first discovered in case: 86
match confidence: 0.8
match reasoning: The Scope Limitation Justification State is defined as a state in which a professional invokes a contractually defined scope of work as justification for failing to investigate or report on material technical findings that bear on safety or accuracy. The present state is the same concept but framed from the perspective of the professional who has made an out-of-scope observation and must decide how to handle it, rather than from the perspective of a professional who uses scope as a shield. The match is medium-high because the underlying tension between contractual scope and independent professional duty is the same.
matched ontology class: Scope Limitation Justification State
matched ontology label: Scope Limitation Justification State
matches existing: true
source text: Engineer A's scope of work was solely to identify any pavement damage on the bridge and report the damage to VWX for further review and repair.
comment: State in which a professional, while performing services within a defined contractual scope, observes a condition or deficiency that falls outside that scope but is material to safety, legal compliance, or the accuracy of the professional's overall assessment, creating a tension between scope compliance and the independent duty to document, report, and follow up on the out-of-scope observation.
subclass of: ConflictState
scope note: [ScopeLimitationJustificationState] State in which a professional invokes a contractually defined scope of work as justification for failing to investigate or report on material technical findings that bear on safety or accuracy, creating a tension between contractual scope compliance and the professional's independent duty of completeness and objectivity.
generated at time: 2026-06-04T17:27:19.652589+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Scope Limitation Disclosure Capability
type: Class
capability category: communication
confidence: 0.91
domain specificity: Technical reporting in engineering investigations and expert witness contexts
enables actions: Disclose omitted data sources or unavailable records
enables actions: Document scope constraints in technical reports
enables actions: Identify equipment failures or procedural gaps that limit findings
enables actions: Qualify conclusions appropriately given investigative limitations
required for obligations: Scope Limitation Disclosure Obligation
skill level: intermediate
text references: Engineer B did not report that the dynamic test equipment had failed.
text references: Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class addresses the competency of recognizing and disclosing material scope limitations in technical reports.
matches existing: false
source text: Engineer B did not report that the dynamic test equipment had failed.
comment: Ability to recognize when material limitations exist on the scope of an investigation and to communicate those limitations clearly and completely in any resulting report or findings document.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Scope Limitation Disclosure Obligation
type: Class
confidence: 0.92
derived from principle: Scope Limitation Disclosure Principle
enforcement level: mandatory
monitoring criteria: Report contains explicit statement of any limitations, equipment failures, or data sources excluded from the analysis
nspe reference: III.2
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: Court or mediating body
stakeholders affected: General public
stakeholders affected: Opposing party
text references: Engineer B did not report that the dynamic test equipment had failed.
text references: Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'
violation consequences: Professional discipline; report conclusions may be invalidated; reputational harm
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:31:15.630641+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing obligation class in the ontology corresponds to this duty. This is a new class.
matches existing: false
source text: Engineer B did not report that the dynamic test equipment had failed.
comment: Duty of an engineer to disclose in any report or findings document any material limitations on the scope of the investigation, including equipment failures, records not reviewed, or methodological constraints that could affect the reliability or completeness of the conclusions.
subclass of: DisclosureObligation
generated at time: 2026-06-04T14:31:15.630641+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Scope Limitation Disclosure Principle
type: Class
abstract nature: Requires judgment about which scope limitations are material to the conclusions and would affect a reasonable reader's assessment of the report's reliability.
confidence: 0.87
derived obligations: Disclose equipment failures that affected test results
derived obligations: Disclose evidence sources that were available but not consulted
derived obligations: Qualify conclusions to reflect the actual scope of investigation performed
extensional examples: Engineer B's failure to disclose that dynamic test equipment had failed during the test pile driving
extensional examples: Engineer B's failure to disclose that pile driving records were not reviewed
operationalization: Requires engineers to identify scope limitations that are material to conclusions, disclose them explicitly in the report, and avoid presenting conclusions with a degree of confidence that the underlying investigation does not support.
potential conflicts: Client interest in a clean, unqualified report
potential conflicts: Retaining party's litigation strategy
principle category: professional_virtue
text references: Additionally, Engineer B did not report that the dynamic test equipment had failed.
text references: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
value basis: Recipients of professional reports, including courts, clients, and affected parties, must be able to assess the evidentiary basis and limitations of the conclusions presented to them.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:30:07.628947+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
comment: Professional principle requiring engineers to disclose in their reports and findings any material limitations on the scope of their investigation that could affect the reliability or completeness of their conclusions, including evidence sources that were available but not consulted, tests that failed or were not properly replicated, and methodological constraints imposed by the engagement terms.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T14:30:07.628947+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Selective Data Use Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Dispute Resolution Body
affected stakeholders: Engineer
affected stakeholders: Opposing Party
affected stakeholders: Public
confidence: 0.8
constraint type: ethical
flexibility: hard
mitigation strategies: Apply analytical methods consistently across all data sets
mitigation strategies: Distinguish legitimate client advocacy from suppression of material evidence
mitigation strategies: Present all available technical data regardless of which party it favors
text references: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data. This is an egregious denial of the duties and responsibilities of a professional engineer in any setting, legal, quasi-legal or non-legal.
text references: It is not evident from the facts of the case that Engineer B's selective use of technical fact was inspired by the adversarial circumstance, nor does it matter.
violation impact: Corruption of technical findings, professional misconduct, potential harm to client through misdirected conclusions, undermining of dispute resolution integrity
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:36:05.125890+00:00
first discovered in case: 71
match confidence: 0.8
match reasoning: The Selective Data Use Constraint maps closely onto the Client Advocacy Boundary Constraint already in the ontology, which marks the boundary between permissible client service and professional misconduct through suppression or omission of material technical evidence. The case text's characterization of selective data use as an egregious denial of professional duties in any setting is the same concept. The present framing adds emphasis on the data-selection mechanism specifically, but the core prohibition is the same.
matched ontology label: Client Advocacy Boundary Constraint
matches existing: true
source text: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data. This is an egregious denial of the duties and responsibilities of a professional engineer in any setting, legal, quasi-legal or non-legal.
comment: Prohibition on an engineer assuming a defensive or advocacy posture toward a client by selectively using technical data to support a predetermined conclusion, which constitutes a denial of professional duties in any setting, legal, quasi-legal, or non-legal.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T14:36:05.125890+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Selective Option Disclosure State
type: Class
action constraints: Professional must disclose basis for excluding options
action constraints: Professional must not limit option presentation to self-serving alternatives
activation conditions: Client lacks independent knowledge to detect the omission
activation conditions: Omitted options are known to the professional
activation conditions: Professional omits one or more approved or viable options from advice or recommendation
confidence: 0.88
obligation activation: Duty to avoid misleading clients through omission
obligation activation: Duty to disclose material information affecting client decisions
obligation activation: Duty to provide complete and objective professional advice
persistence type: inertial
principle transformation: Transforms the general duty of honesty and objectivity into a concrete obligation to present all materially relevant options and disclose the basis for any exclusions.
state category: conflict
termination conditions: Client independently learns of omitted options
termination conditions: Engagement concluded
termination conditions: Full disclosure of all available options provided to client
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:41:16.710298+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options
comment: State in which a professional presents only a subset of available or approved options to a client, omitting alternatives that the professional is not positioned to provide or that would disadvantage the professional's business interests, creating a transparency deficit and potential breach of the duty to provide complete and unbiased advice.
subclass of: ConflictState
generated at time: 2026-06-04T08:41:16.710298+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Self-Certification Avoidance Capability
type: Class
capability category: awareness
confidence: 0.85
domain specificity: General professional engineering practice
enables actions: Distinguish legitimate competence from tool-based self-certification
enables actions: Evaluate whether a product purchase confers genuine professional qualification
enables actions: Refrain from holding out services based solely on tool acquisition
required for obligations: Competence Misrepresentation Avoidance Obligation
required for obligations: Self-Certification Avoidance Obligation
required for obligations: Tool Substitution Refusal Obligation
skill level: intermediate
text references: By ordering and using the CD-ROM, Engineer A in a sense was 'self-certifying' his competency to perform facilities design and construction services without obtaining the substantive education, experience, and qualifications to perform those services in a competent and professional manner
text references: The Board considers such activities completely contrary to the basic ethical principles established in the Code of Ethics
text references: the direct mail product described under the facts is not unlike mail order certifications offered by so called 'diploma mills' whereby individuals 'self certify' their competency based upon a perfunctory review process that rarely involves comprehensive study, examination, or practice
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:50:08.208638+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: By ordering and using the CD-ROM, Engineer A in a sense was 'self-certifying' his competency to perform facilities design and construction services without obtaining the substantive education, experience, and qualifications to perform those services in a competent and professional manner
comment: Capability of a licensed professional engineer to recognize when the acquisition or use of a commercial tool, template, reference library, or similar product does not constitute a legitimate basis for representing competence in a technical domain, and to refrain from treating such acquisition as a substitute for the substantive education, examination, and professional experience required to practice competently in that domain.
subclass of: Capability
generated at time: 2026-06-04T18:50:08.208638+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Self-Certification Avoidance Obligation
type: Class
confidence: 0.92
derived from principle: Self-Certification Prohibition Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer did not represent competence in a domain solely on the basis of a commercial tool or product acquisition
nspe reference: II.2.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Prospective clients
stakeholders affected: Regulatory bodies
text references: A CD-ROM that permits virtually anyone to specify, design and cost out a project clearly is not an appropriate basis upon which an individual can obtain professional competency to perform facilities design and construction services
text references: By ordering and using the CD-ROM, Engineer A in a sense was self-certifying his competency to perform facilities design and construction services without obtaining the substantive education, experience, and qualifications to perform those services in a competent and professional manner
text references: The Board considers such activities completely contrary to the basic ethical principles established in the Code of Ethics
text references: not unlike mail order certifications offered by so called diploma mills whereby individuals self certify their competency based upon a perfunctory review process that rarely involves comprehensive study, examination, or practice
violation consequences: Professional discipline; public safety risk; reputational harm to the profession
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:49:10.142160+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: A CD-ROM that permits virtually anyone to specify, design and cost out a project clearly is not an appropriate basis upon which an individual can obtain professional competency to perform facilities design and construction services
comment: Duty of a licensed engineer to refrain from treating the acquisition or use of a commercial tool, template, CD-ROM library, or similar product as a basis for representing competence in a technical domain in which the engineer lacks substantive education, training, and experience, recognizing that such self-certification is contrary to the foundational ethical principles of the profession.
subclass of: CompetenceObligation
generated at time: 2026-06-04T18:49:10.142160+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Self-Certification Competence Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Licensing Board
affected stakeholders: Public
confidence: 0.88
constraint type: ethical
flexibility: hard
mitigation strategies: Decline engagements that require competencies not yet established through recognized means
mitigation strategies: Obtain formal education and supervised experience in the target domain before offering services
mitigation strategies: Retain qualified specialists for work outside demonstrated competence
text references: A CD-ROM that permits virtually anyone to 'specify, design and cost out' a project clearly is not an appropriate basis upon which an individual can obtain professional competency to perform facilities design and construction services.
text references: By ordering and using the CD-ROM, Engineer A in a sense was 'self-certifying' his competency to perform facilities design and construction services without obtaining the substantive education, experience, and qualifications to perform those services in a competent and professional manner.
text references: The Board considers such activities completely contrary to the basic ethical principles established in the Code of Ethics.
violation impact: Engineer misrepresents qualifications to clients and the public, exposes the public to work performed without adequate knowledge, and undermines the professional standards that protect public health and safety.
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:50:05.033406+00:00
first discovered in case: 121
match confidence: 0.72
match reasoning: The Unfamiliar Tool Competence Constraint addresses limits on using tools the engineer lacks sufficient experience with, which partially overlaps. However, the present constraint is more specifically about the prohibition on treating tool acquisition as a substitute for domain competence certification, which is a distinct concept closer to self-certification and misrepresentation than to mere unfamiliarity with a tool. The match is a variant rather than an exact match; the existing class does not fully capture the self-certification dimension.
matched ontology class: Unfamiliar Tool Competence Constraint
matched ontology label: Unfamiliar Tool Competence Constraint
matches existing: true
source text: A CD-ROM that permits virtually anyone to 'specify, design and cost out' a project clearly is not an appropriate basis upon which an individual can obtain professional competency to perform facilities design and construction services.
comment: Ethical and regulatory constraint prohibiting a licensed engineer from treating self-directed acquisition of a commercial tool, template, or automated system as a sufficient basis for claiming or representing competence in a technical domain, in lieu of obtaining the substantive education, examination, and professional experience that genuine competence requires.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [UnfamiliarToolCompetenceConstraint] Competence constraint limiting an engineer's permissible use of a tool, technology, or method with which they lack sufficient experience or understanding, requiring that the engineer either acquire adequate competence before use, limit reliance on the tool's outputs, or obtain qualified assistance, so that professional work products meet required standards.
generated at time: 2026-06-04T18:50:05.033406+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Self-Certification Prohibition Principle
type: Class
abstract nature: Open-textured principle requiring judgment about what constitutes genuine competence acquisition versus superficial credentialing, and about the threshold at which tool-assisted practice crosses into unqualified practice.
confidence: 0.87
derived obligations: Accurately represent the basis of one's qualifications when soliciting or accepting work
derived obligations: Refrain from offering services in domains where competence rests solely on a commercial tool or template
derived obligations: Seek formal education or supervised experience before expanding into a new technical domain
extensional examples: Analogy to diploma mill self-certification noted by the Board of Ethical Review
extensional examples: BER Case current: Engineer A orders a CD-ROM and begins offering facilities design services without any substantive background in civil, structural, mechanical, or electrical engineering
operationalization: Requires engineers to obtain substantive education, experience, and demonstrated qualifications before offering services in a new domain, and to refrain from representing tool-assisted familiarity as professional competence.
potential conflicts: Commercial Inducement Resistance Principle
potential conflicts: Competence Boundary Principle
principle category: professional_virtue
text references: A CD-ROM that permits virtually anyone to 'specify, design and cost out' a project clearly is not an appropriate basis upon which an individual can obtain professional competency to perform facilities design and construction services.
text references: By ordering and using the CD-ROM, Engineer A in a sense was 'self-certifying' his competency to perform facilities design and construction services without obtaining the substantive education, experience, and qualifications to perform those services in a competent and professional manner.
text references: The direct mail product described under the facts is not unlike mail order certifications offered by so called 'diploma mills' whereby individuals 'self certify' their competency based upon a perfunctory review process that rarely involves comprehensive study, examination, or practice.
value basis: The public relies on licensure and professional representation as a signal that the engineer possesses genuine knowledge and skill. Self-certification through tool acquisition undermines that signal and exposes the public to undetected incompetence.
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:48:00.517540+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: A CD-ROM that permits virtually anyone to 'specify, design and cost out' a project clearly is not an appropriate basis upon which an individual can obtain professional competency to perform facilities design and construction services.
comment: Professional integrity principle prohibiting engineers from treating the acquisition of a commercial tool, template, software package, or other shortcut resource as a substitute for genuine education, examination, and supervised experience in a technical domain. An engineer who orders a tool and declares themselves competent to practice in a new domain on that basis alone is engaged in a form of self-certification that is incompatible with the professional obligation to demonstrate substantive qualifications before offering services.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T18:48:00.517540+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Self-Certified Competence State
type: Class
action constraints: Must not perform services in the domain without genuine competence
action constraints: Must not represent tool-assisted output as product of professional judgment
action constraints: Must not submit work product to clients or authorities as if produced by a qualified practitioner
activation conditions: Professional acquires a tool, software, or reference material and treats it as conferring domain competence
activation conditions: Professional begins offering services in a domain without verifiable education or experience credentials
activation conditions: Professional self-assesses as qualified without external validation
confidence: 0.88
obligation activation: Duty to decline work outside genuine competence
obligation activation: Duty to disclose competence limitations to clients
obligation activation: Duty to retain or recommend qualified specialists
obligation activation: Obligation to protect public health and safety by not performing unqualified work
persistence type: inertial
principle transformation: Transforms the general competence principle into a concrete prohibition on performing services and a positive duty to refer or disclose, activated by the gap between claimed and actual capability.
state category: competence
termination conditions: Professional declines the work or refers it to a qualified practitioner
termination conditions: Professional discloses limitation and retains a qualified specialist
termination conditions: Professional obtains substantive education and supervised experience in the domain
text references: A CD-ROM that permits virtually anyone to specify, design and cost out a project clearly is not an appropriate basis upon which an individual can obtain professional competency
text references: Engineer A in a sense was self-certifying his competency to perform facilities design and construction services without obtaining the substantive education, experience, and qualifications
text references: not unlike mail order certifications offered by so called diploma mills whereby individuals self certify their competency based upon a perfunctory review process
discovered in case: 121
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T18:43:40.738200+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: A CD-ROM that permits virtually anyone to specify, design and cost out a project clearly is not an appropriate basis upon which an individual can obtain professional competency
comment: State in which a professional declares or implies competence in a domain based solely on self-assessment or use of a commercial shortcut tool, without having obtained the substantive education, training, examination, or supervised experience that the domain requires, creating conditions in which the professional's representations of capability are false or misleading and in which work product carries elevated risk of harm to the public.
subclass of: CompetenceState
generated at time: 2026-06-04T18:43:40.738200+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Self-Interested Recommendation State
type: Class
action constraints: Professional must disclose any financial interest in the recommended option before or at the time of recommendation
action constraints: Professional must not recommend options solely or primarily on the basis of personal gain
activation conditions: Interest is not disclosed to the client
activation conditions: Professional has a financial or business interest in the recommended option
activation conditions: Professional recommends a specific option or course of action
confidence: 0.87
obligation activation: Duty to act in the client's best interest
obligation activation: Duty to disclose personal or business interest in recommended option
obligation activation: Duty to provide objective and unbiased professional advice
persistence type: inertial
principle transformation: Transforms the general conflict-of-interest principle into a concrete obligation to disclose business interest in a recommended project delivery method and to ensure the recommendation is grounded in the client's needs rather than the professional's commercial advantage.
state category: conflict
termination conditions: Conflict of interest disclosed to client
termination conditions: Engagement concluded
termination conditions: Recommendation withdrawn or revised
text references: Engineer A is qualified to provide construction services under Progressive-Design-Build and Construction-Manager-at-Risk delivery methods
text references: Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects
text references: Engineer A recommended Progressive Design Build
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:41:16.710298+00:00
first discovered in case: 14
match confidence: 0.75
match reasoning: Conflict of Interest State captures the general condition of competing personal and professional interests. This new class is a more specific variant focused on the act of making a recommendation while holding an undisclosed business interest in the recommended option, which adds the disclosure and advice-objectivity dimensions not fully expressed by the general class.
matched ontology class: ConflictOfInterest
matched ontology label: Conflict of Interest State
matches existing: true
source text: Engineer A recommended Progressive Design Build
comment: State in which a professional makes a recommendation to a client that favors an option under which the professional stands to benefit commercially, without disclosing that interest, creating a conflict between the duty of objective advice and the professional's financial or business interests.
subclass of: ConflictState
scope note: [ConflictOfInterest] Professional situation where personal and professional interests compete
generated at time: 2026-06-04T08:41:16.710298+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Self-Promotion Advisory Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.78
constraint type: ethical
flexibility: hard
mitigation strategies: Obtain client informed consent before combining advisory and promotional functions
mitigation strategies: Refrain from submitting qualifications materials alongside advisory recommendations
mitigation strategies: Separate advisory and service-provider roles or disclose the dual interest explicitly
text references: Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects.
text references: Engineer A recommended Progressive Design Build.
violation impact: Breach of fiduciary duty, conflict of interest violation, client harm from biased advice, potential disciplinary action
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:45:47.831992+00:00
first discovered in case: 14
match confidence: 0.75
match reasoning: The conduct maps to Conflict of Interest Avoidance because the engineer is using an advisory role to advance personal business interests. However, the specific prohibition on embedding self-promotional materials within an advisory product is a variant not fully captured by the existing class. Matching as a variant with medium confidence.
matched ontology class: Conflict of Interest Avoidance
matched ontology label: Conflict of Interest Avoidance (Constraint)
matches existing: true
source text: Accompanying the recommendation, Engineer A provided a summary of the firm's experience with Progressive-Design-Build projects and references from past projects.
comment: Ethical constraint prohibiting an engineer who is providing advisory services from using the advisory engagement as a vehicle to promote the engineer's own services or qualifications, particularly when doing so involves presenting a biased or incomplete analysis that steers the client toward an option under which the engineer stands to benefit.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [Conflict_of_Interest_Avoidance] Constraint established by ethics code provisions
generated at time: 2026-06-04T08:45:47.831992+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Self-Serving Advisory Avoidance Obligation
type: Class
confidence: 0.85
derived from principle: Advisory Role Integrity Principle
enforcement level: mandatory
monitoring criteria: Evidence that the advisory recommendation was based on objective analysis of all available options rather than on the engineer's commercial interest in the outcome
nspe reference: II.3.a
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Competing engineers
stakeholders affected: Public
text references: Engineer A could have provided a complete analysis of the four methodologies, with all the pros and cons by compiling properly referenced resources from others
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information
text references: objective and truthful
violation consequences: Professional discipline; findings of unethical conduct; loss of client trust; potential disqualification
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:47:48.914349+00:00
first discovered in case: 14
match confidence: 0.72
match reasoning: The Advisory Role Objectivity Obligation extracted in prior sections is the closest existing extracted class, but it is listed under previously extracted classes rather than the canonical ontology. Among the canonical ontology classes, Disclosure Obligation is the closest parent because the self-serving advisory avoidance duty is partly grounded in the requirement to inform stakeholders about conflicts and limitations. However, this class is a distinct specialization emphasizing the prohibition on structuring advisory content to serve the engineer's own interests, which goes beyond mere disclosure. Matched as a variant with medium confidence.
matched ontology class: DisclosureObligation
matched ontology label: Disclosure Obligation
matches existing: true
source text: objective and truthful
comment: Duty of an engineer providing advisory services to refrain from structuring the advisory product in a manner that serves the engineer's own commercial interests, including recommending options under which the engineer is positioned to receive subsequent paid work while omitting or underanalyzing competing options, so that the advisory product reflects the client's interests rather than the engineer's.
subclass of: EthicalObligation
scope note: [DisclosureObligation] Requirement to inform stakeholders about conflicts, limitations, or risks (NSPE II.3.a)
generated at time: 2026-06-04T08:47:48.914349+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Simultaneous Transition Safety Constraint
type: Class
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
affected stakeholders: Water Commission
confidence: 0.8
constraint type: safety
flexibility: hard
mitigation strategies: Document the safety basis for the sequential requirement in writing
mitigation strategies: Escalate to regulatory authority when client proceeds simultaneously over professional objection
mitigation strategies: Refuse to endorse simultaneous transition and improvement schedules when sequential completion is required for safety
text references: The improvements are needed prior to the change in water source to ensure that sufficient corrosion control is provided so that old service pipes in the MWC service area don't leach lead at levels in excess of drinking water standards
text references: the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source
violation impact: Confirmed risk of lead or other contaminant leaching above regulatory standards, public health harm, regulatory violation, professional discipline
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:25:13.430491+00:00
first discovered in case: 76
match confidence: 0.74
match reasoning: The simultaneous transition scenario is a specific instance of a client overriding safety recommendations for economic reasons and the engineer being prohibited from continuing to facilitate that unsafe course. The existing Client Budget Override Safety Continuation Constraint captures the core prohibition on continuing work after a client declines safety measures for budget reasons. The simultaneous transition framing is a variant of that concept applied to the specific sequencing question. Matching as a variant at medium confidence.
matched ontology class: Client Budget Override Safety Continuation Constraint
matched ontology label: Client Budget Override Safety Continuation Constraint
matches existing: true
source text: the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source
comment: Safety constraint prohibiting a water or utility authority, and the engineers advising it, from proceeding with a change in supply source or infrastructure simultaneously with the evaluation and design of required safety improvements, when the professional engineering assessment has established that the safety improvements must be completed before the transition to protect public health. Proceeding simultaneously rather than sequentially creates a confirmed public health risk that engineers must not endorse or facilitate.
subclass of: InviolableConstraint
subclass of: SafetyConstraint
scope note: [ClientBudgetOverrideSafetyContinuationConstraint] Ethical constraint prohibiting an engineer from continuing work on a project after a client declines to implement safety measures the engineer has identified as necessary to protect public health or safety, when the client's refusal is grounded in budget or economic considerations. The engineer must cease participation rather than subordinate the paramount public safety duty to the client's financial preferences.
generated at time: 2026-06-05T11:25:13.430491+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Solicitation Critical Evaluation Capability
type: Class
capability category: awareness
confidence: 0.82
domain specificity: General professional engineering practice
enables actions: Assess whether a promoted tool can legitimately substitute for domain expertise
enables actions: Decline to act on solicitations that would lead to ethical violations
enables actions: Identify misleading claims in commercial solicitations
enables actions: Recognize when a solicitation frames professional standards as obstacles
required for obligations: Commercial Solicitation Resistance Obligation
skill level: intermediate
text references: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
text references: specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:46:28.378823+00:00
first discovered in case: 121
match confidence: 0.55
match reasoning: CADD Proficiency Capability addresses recognizing when a technological tool is being used as a substitute for professional judgment, which partially overlaps. However, that class is scoped to CADD systems and proficiency within a known tool context, whereas this capability concerns critically evaluating an external commercial solicitation that misrepresents what a tool can do before the engineer even acquires it. The awareness dimension and the solicitation-evaluation context are sufficiently distinct to warrant a new class. No existing class captures the front-end critical evaluation of marketing claims directed at engineers.
matched ontology class: CADD Proficiency Capability
matched ontology label: CADD Proficiency Capability
matches existing: true
source text: Engineers today cannot afford to pass up a single job that comes by - including construction projects that may be new or unfamiliar.
comment: Capability to critically evaluate commercial solicitations, marketing materials, and product promotions directed at licensed engineers, including the ability to recognize when a solicitation misrepresents professional competence requirements, frames ethical obligations as obstacles to profit, or implies that a software tool can substitute for domain knowledge and professional experience.
subclass of: Capability
scope note: [CADDProficiencyCapability] Technical capability of a licensed professional engineer to possess sufficient background, education, and training to be proficient with CADD systems, including understanding the limitations of the technology, recognizing when the system is being used as a substitute for professional judgment rather than as a production tool, and ensuring that outputs reflect genuine engineering competence rather than uncritical reliance on system-generated solutions.
generated at time: 2026-06-04T18:46:28.378823+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Source Consultation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Opposing parties
affected stakeholders: Retained engineer
affected stakeholders: Tribunal
confidence: 0.89
constraint type: procedural
flexibility: soft
mitigation strategies: Disclose any sources not consulted and the reason for non-consultation
mitigation strategies: Identify and contact all available witnesses before finalizing conclusions
mitigation strategies: Review all available primary records relevant to the investigation
text references: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
text references: No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
violation impact: Incomplete investigation, unsupported conclusions, professional discipline, unjust outcomes
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology addresses the procedural requirement to consult available sources before reaching conclusions. This is the bounding constraint corresponding to the obligation-side Investigative Completeness Obligation.
matches existing: false
source text: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.
comment: Requirement that an engineer conducting an investigation consult available witnesses, records, and other primary sources before reaching conclusions, and disclose any failure to do so in the resulting report.
subclass of: DefeasibleConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Specialist Retention Judgment Capability
type: Class
capability category: reasoning
confidence: 0.82
domain specificity: General professional engineering practice across multi-discipline projects
enables actions: Ensure multi-discipline project coverage by competent engineers
enables actions: Identify technical domains outside own competence
enables actions: Retain or recommend qualified specialists
required for obligations: Competence Boundary Obligation
required for obligations: Specialist Retention Obligation
skill level: advanced
text references: a prime professional will be expected to retain or recommend the retention of experts and specialists in situations in which the prime professional is performing substantial services on the project
text references: engineers have an ethical obligation to seek work only in areas where they possess educational background and experience or to retain individuals who possess the necessary educational background and experience to perform the work
text references: the Board recognized the propriety and value of the prime professional or client retaining the services of experts and specialists in the interests of the project
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:50:08.208638+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: the Board recognized the propriety and value of the prime professional or client retaining the services of experts and specialists in the interests of the project
comment: Capability of a licensed professional engineer to recognize when a project involves technical domains outside the engineer's own competence and to identify, retain, or recommend the retention of qualified specialists or experts in those domains, ensuring that all project disciplines are covered by engineers with appropriate education and experience.
subclass of: Capability
generated at time: 2026-06-04T18:50:08.208638+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Specialist Retention Obligation
type: Class
confidence: 0.88
derived from principle: Specialist Retention Obligation Principle
enforcement level: mandatory
monitoring criteria: Evidence that qualified specialists were retained or recommended for technical domains outside the engineer's competence
nspe reference: II.2.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: Construction contractor
stakeholders affected: General public
stakeholders affected: Project owner
text references: a prime professional will be expected to retain or recommend the retention of experts and specialists in situations in which the prime professional is performing substantial services on the project
text references: engineers have an ethical obligation to seek work only in areas where they possess educational background and experience or to retain individuals who possess the necessary educational background and experience to perform the work
text references: the Board recognized the propriety and value of the prime professional or client retaining the services of experts and specialists in the interests of the project
violation consequences: Professional discipline; public safety risk; potential liability for deficient design
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:49:10.142160+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: the Board recognized the propriety and value of the prime professional or client retaining the services of experts and specialists in the interests of the project
comment: Duty of an engineer who undertakes or is retained for a project involving technical domains outside the engineer's own competence to retain or recommend the retention of qualified specialists or experts in those domains, rather than attempting to perform the out-of-competence work personally or with inadequate tools.
subclass of: CompetenceObligation
generated at time: 2026-06-04T18:49:10.142160+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Specialist Retention Obligation Principle
type: Class
abstract nature: Requires judgment about when a technical domain is sufficiently distinct from the engineer's background to trigger the obligation, and about what constitutes adequate specialist qualifications.
confidence: 0.83
derived obligations: Identify technical domains in a project that exceed the engineer's own qualifications
derived obligations: Refrain from performing work in domains where the engineer lacks competence and no qualified specialist has been engaged
derived obligations: Retain or recommend retention of qualified specialists for those domains
extensional examples: BER Case 71-2: prime professional expected to retain experts and specialists when performing substantial services on a project
extensional examples: BER Case 78-5: consulting firm obligated to seek work only in areas of competence or to retain individuals with the necessary background
operationalization: Requires engineers to identify technical domains in a project that fall outside their competence, to seek or recommend qualified specialists for those domains, and to refrain from proceeding without such specialists when the work is safety-relevant.
potential conflicts: Competence Boundary Principle
potential conflicts: Faithful Agent Duty Principle
principle category: professional_virtue
text references: BER Case 71-2, a case involving the brokerage of engineering services by two firms competing for government work and the question of professional competence, the Board recognized 'the propriety and value of the prime professional or client retaining the services of experts and specialists in the interests of the project'
text references: engineers have an ethical obligation to seek work only in areas where they possess educational background and experience or to retain individuals who possess the necessary educational background and experience to perform the work
value basis: Public safety and project integrity depend on work in each technical domain being performed by someone with genuine qualifications in that domain. The prime professional or retaining engineer is the gatekeeper who ensures that qualified personnel are engaged.
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:48:00.517540+00:00
first discovered in case: 121
match confidence: 0.0
matches existing: false
source text: BER Case 71-2, a case involving the brokerage of engineering services by two firms competing for government work and the question of professional competence, the Board recognized 'the propriety and value of the prime professional or client retaining the services of experts and specialists in the interests of the project'
comment: Professional principle requiring engineers who undertake or are retained for projects involving technical domains outside their own competence to affirmatively retain, or recommend the retention of, qualified specialists or experts in those domains, rather than attempting to perform the work themselves or leaving the gap unaddressed. The obligation applies both to prime professionals managing multi-discipline projects and to engineers who recognize mid-project that a required task exceeds their qualifications.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T18:48:00.517540+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Speculative Finding Exclusion Capability
type: Class
capability category: reasoning
confidence: 0.87
domain specificity: Professional engineering inspection and investigation contexts where scope limitations or competence boundaries constrain what can be formally reported
enables actions: Assess whether an observation is supported by sufficient analysis to appear in a formal report
enables actions: Communicate the distinction between speculation and confirmed findings to clients
enables actions: Exclude speculative findings from final written deliverables
enables actions: Retain speculative observations in field notes for possible future reference
required for obligations: Field Notes Preservation Obligation
required for obligations: Speculative Finding Exclusion Obligation
skill level: intermediate
text references: Engineer A stated that he would retain the information from his engineering notes but not include it in the final report, as requested
text references: Engineer A surmised that the defective condition may have been a contributing factor in the wall failure and noted this in his engineering notes.
text references: there was nothing under the facts to indicate anything more than Engineer A's general surmise and speculation about the cause of the structural failure of the wall
text references: to place this information in a final report would not be responsible and could unnecessarily inflame the situation
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:36:09.645175+00:00
first discovered in case: 86
match confidence: 0.82
match reasoning: Concern Versus Fact Threshold Capability captures the ability to distinguish between a preliminary professional concern not yet substantiated by technical analysis and a finding that rises to the level of demonstrable fact, and to calibrate disclosure obligations accordingly. The speculative finding exclusion concept is a direct application of that threshold judgment to the question of what belongs in a formal report versus field notes. The match is strong but not identical because the existing class frames the distinction in terms of disclosure obligations broadly, while this capability is specifically about report content decisions.
matched ontology class: Concern Versus Fact Threshold Capability
matched ontology label: Concern Versus Fact Threshold Capability
matches existing: true
source text: Engineer A surmised that the defective condition may have been a contributing factor in the wall failure and noted this in his engineering notes.
comment: Capability to distinguish between observations that rise to the level of a professionally supportable finding and observations that remain speculative or unverified, and to exclude speculative observations from formal written reports while preserving them in field notes, so that professional work products do not assert conclusions beyond what the evidence and the engineer's competence support.
subclass of: Capability
scope note: [ConcernVersusFactThresholdCapability] Capability to distinguish between a preliminary professional concern that has not yet been substantiated by technical analysis and a finding that rises to the level of a demonstrable fact, and to calibrate disclosure obligations accordingly so that neither premature disclosure of unsubstantiated concerns nor suppression of confirmed findings occurs.
generated at time: 2026-06-04T17:36:09.645175+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Speculative Finding Exclusion Obligation
type: Class
confidence: 0.85
derived from principle: Competence Recognition Principle
enforcement level: defeasible
monitoring criteria: Final report contains only findings supported by competent analysis within the engineer's area of expertise; speculative observations are retained in field notes only.
nspe reference: II.2, III.2.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: Other engineers
stakeholders affected: Prime consultant
stakeholders affected: Public agency
text references: Under the circumstances, the Board concluded that it would have been improper for Engineer A to include reference to the information in his final report, particularly since it would have been based upon mere speculation and not careful testing or evaluation by a competent individual or firm.
text references: While it might have been appropriate for Engineer A to note such information in his field notes, to place this information in a final report would not be responsible and could unnecessarily inflame the situation.
violation consequences: Including speculative findings in a formal report may unjustifiably damage the reputations of other professionals and parties, and may constitute a breach of the duty to practice only within areas of competence.
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:34:19.889581+00:00
first discovered in case: 86
match confidence: 0.72
match reasoning: This is a partial inverse of Complete Technical Reporting Obligation: where that class requires inclusion of all relevant findings, this class addresses the competing duty to exclude findings that are not professionally substantiated. It is a variant that qualifies the completeness duty by competence limits, warranting a medium-confidence match to the parent concept rather than a new independent class, but the specific exclusion framing is not captured by any existing class.
matched ontology class: Complete Technical Reporting Obligation
matched ontology label: Complete Technical Reporting Obligation
matches existing: true
source text: While it might have been appropriate for Engineer A to note such information in his field notes, to place this information in a final report would not be responsible and could unnecessarily inflame the situation.
comment: Duty of an engineer to refrain from including observations or conclusions in a formal written report when those observations are based solely on visual inspection without supporting analysis, when the engineer lacks expertise in the relevant discipline, and when inclusion would constitute speculation rather than a professionally substantiated finding.
subclass of: CompetenceObligation
scope note: [CompleteTechnicalReportingObligation] Duty of an engineer preparing a technical report to include all relevant and pertinent technical information, including facts that may complicate or contradict the primary conclusions, so that the report supports informed review and interpretation by others.
generated at time: 2026-06-04T17:34:19.889581+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Speculative Risk Finding State
type: Class
action constraints: Professional should not alter or destroy field notes documenting the observation
action constraints: Professional should not include speculative findings in formal written reports
action constraints: Professional should not report to public authorities before determining whether corrective action is taken
activation conditions: No testing or formal analysis has been performed to confirm the risk
activation conditions: Professional lacks specific expertise in the relevant technical discipline
activation conditions: Professional observes a potentially hazardous condition through visual inspection only
confidence: 0.85
obligation activation: Obligation to document observation in field notes
obligation activation: Obligation to follow up to confirm corrective action is taken
obligation activation: Obligation to verbally report concern to client or prime consultant
persistence type: inertial
principle transformation: Transforms the general duty of completeness and public safety into a calibrated set of obligations scaled to the epistemic quality of the finding: document, report verbally, monitor, and escalate only if corrective action is not taken.
state category: risk
termination conditions: Competent analysis confirms or refutes the risk
termination conditions: Professional obtains expertise or retains qualified specialist
termination conditions: Responsible party takes corrective action
text references: Engineer A's evaluation was based upon general surmise and speculation about the cause of the structural failure of the wall, based entirely upon a visual inspection without anything more.
text references: There was nothing noted in the facts to indicate that Engineer A had expertise in the specific discipline involved.
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:27:19.652589+00:00
first discovered in case: 86
match confidence: 0.82
match reasoning: The Unverified Risk Concern State is defined as a state in which a professional has a concern or suspicion about a potential risk but has not yet developed the analysis to a point where the concern constitutes a technical or factual finding. This matches the speculative-observation scenario from BER Case 97-13 discussed in the text. The match is medium-high because the existing class already captures the intermediate epistemic condition and its calibrated obligations.
matched ontology class: Unverified Risk Concern State
matched ontology label: Unverified Risk Concern State
matches existing: true
source text: Engineer A's evaluation was based upon general surmise and speculation about the cause of the structural failure of the wall, based entirely upon a visual inspection without anything more.
comment: State in which a professional has observed a condition that may indicate a risk or defect but has formed no more than a general surmise or speculation about causation, lacking the technical expertise, testing, or analysis needed to convert the observation into a confirmed professional finding, creating an intermediate epistemic condition that limits but does not eliminate the professional's disclosure and follow-up obligations.
subclass of: RiskState
scope note: [UnverifiedRiskConcernState] State in which a professional has a concern or suspicion about a potential risk but has not yet developed the analysis to a point where the concern constitutes a technical or factual finding. The concern is real but unquantified, creating an intermediate epistemic condition that does not yet trigger mandatory disclosure obligations but may support prudent voluntary disclosure.
generated at time: 2026-06-04T17:27:19.652589+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

State Wetland Protection Regulation Resource
type: Class
authority source: State environmental regulatory agencies
confidence: 0.85
extensional function: Establishes state-level legal obligations that complement federal wetland protections and inform the professional duties of engineers observing violations
resource category: legal_resource
text references: installation of the fill material is a substantial violation of the federal and state laws and regulations
usage context: Professional reporting obligations
usage context: Regulatory violation identification
usage context: State wetland fill permit requirements
discovered in case: 86
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T17:25:28.729274+00:00
first discovered in case: 86
match confidence: 0.8
match reasoning: The existing Environmental Protection Regulation Resource class covers local, state, or jurisdictional regulations for environmental protection. State wetland protection statutes are a variant of this class. Matching with medium confidence as the existing class definition references stormwater and water source protection specifically, while state wetland fill regulations are a related but broader category.
matched ontology class: Environmental Protection Regulation Resource
matched ontology label: Environmental Protection Regulation Resource
matches existing: true
source text: installation of the fill material is a substantial violation of the federal and state laws and regulations
comment: State statutes and regulations governing the protection of wetland areas within a jurisdiction, including requirements for permits or approvals before placing fill material in regulated wetlands. These regulations operate alongside federal requirements and may impose additional or parallel obligations on property owners and professionals.
subclass of: LegalResource
scope note: [EnvironmentalProtectionRegulationResource] Local, state, or jurisdictional regulations specifying mandatory environmental protection requirements, including standards for safeguarding public water sources and controlling stormwater runoff impacts on natural water bodies.
generated at time: 2026-06-04T17:25:28.729274+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Stormwater Design Engineer
type: Class
confidence: 0.88
role category: provider_client
text references: Engineer L conducts additional studies and qualitatively estimates the risk that heavy rainfall could lead to stormwater runoff
text references: Engineer L is contracted by Client X, a private development entity, to design a stormwater management system
text references: Engineer L, a licensed professional engineer, has many years of experience in stormwater control design
discovered in case: 8
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T09:57:38.749817+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L, a licensed professional engineer, has many years of experience in stormwater control design
comment: A licensed professional engineering role specializing in stormwater management system design, bearing professional accountability for assessing and communicating risks to public water sources and ensuring designs comply with applicable environmental standards.
subclass of: EngineerRole
subclass of: ProviderClientRole
generated at time: 2026-06-04T09:57:38.749817+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Structural Inspection Engineer
type: Class
confidence: 0.82
role category: provider_client
text references: Engineer A noticed an apparent pre-existing defective condition in the wall close to where the accident involving Police Officer B occurred
text references: Engineer A, a civil engineer, as its sub-consultant to perform bridge inspection services on the bridge
discovered in case: 86
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T17:26:36.428475+00:00
first discovered in case: 86
match confidence: 0.72
match reasoning: The bridge inspection sub-consultant role is a specialization of Civil Engineer Role, focused on structural inspection and out-of-scope safety observation reporting. It is distinct enough in its obligation structure to warrant a separate extracted class, but maps to Civil Engineer Role as its parent.
matched ontology class: CivilEngineerRole
matched ontology label: Civil Engineer Role
matches existing: true
source text: Engineer A, a civil engineer, as its sub-consultant to perform bridge inspection services on the bridge
comment: A licensed professional engineering role in which the practitioner is retained to perform inspection services on existing structures, identify deficiencies or defective conditions observed during inspection, and report findings through appropriate channels, bearing professional obligations to disclose safety-relevant observations even when they fall outside the contracted scope of work.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [CivilEngineerRole] Engineer specializing in infrastructure and the built environment.
generated at time: 2026-06-04T17:26:36.428475+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Supervisory Direction Adequacy Capability
type: Class
capability category: domain_specific
confidence: 0.78
domain specificity: Professional engineering supervision involving CADD-assisted document production by subordinates
enables actions: Critically evaluate work products produced by supervised personnel
enables actions: Determine whether the level of direction exercised is sufficient to support sealing
enables actions: Identify when subordinate work requires additional review before a seal can be applied
enables actions: Set technical guidelines and constraints for subordinates using CADD or other production tools
required for obligations: Responsible Charge Seal Obligation
required for obligations: Supervisory Direction Control Obligation
required for obligations: Technology Tool Non-Substitution Obligation
skill level: advanced
text references: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control.
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:08:23.109387+00:00
first discovered in case: 120
match confidence: 0.78
match reasoning: AI Direction and Control Capability covers the capability to exercise genuine professional direction and control over AI-assisted tools used to generate engineering work products, including outlining solution guidelines, critically evaluating outputs, and ensuring final work reflects independent professional judgment. The supervisory direction adequacy concept in this case is a variant applied to CADD systems and subordinate personnel rather than AI tools directly, but the core capability structure is the same. Medium confidence match as a variant.
matched ontology class: AI Direction and Control Capability
matched ontology label: AI Direction and Control Capability
matches existing: true
source text: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control.
comment: Capability of a licensed professional engineer in a supervisory role to exercise genuine, substantive direction and control over subordinates producing engineering documents, including the ability to set technical requirements, review outputs critically, and ensure that the supervisory relationship is sufficient to support responsible charge before applying a professional seal to work produced by others.
subclass of: Capability
scope note: [AIDirectionandControlCapability] Capability to exercise genuine professional direction and control over AI-assisted tools used to generate engineering work products, including the ability to outline solution guidelines and constraints, critically evaluate AI outputs, and ensure that final work products reflect independent professional judgment rather than uncritical acceptance of AI-generated content.
generated at time: 2026-06-04T18:08:23.109387+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Supervisory Direction Control Obligation
type: Class
confidence: 0.88
derived from principle: Responsible Charge Integrity Principle
enforcement level: mandatory
monitoring criteria: Documented evidence of active involvement in design decisions, technical review, and correction of subordinate work prior to sealing
nspe reference: II.2, III.2.b
obligation type: ethical
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
stakeholders affected: Subordinate staff
text references: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control.
violation consequences: Professional discipline; invalidation of sealed documents; civil liability for deficient work
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:07:43.735405+00:00
first discovered in case: 120
match confidence: 0.82
match reasoning: The existing Responsible Charge Verification Obligation captures the duty to conduct comprehensive, experience-based verification of all work products before sealing, including active involvement in design and development. The supervisory direction and control concept is a close variant of that obligation applied to the context of subordinate-produced CADD documents, warranting a medium-confidence match to the parent class.
matched ontology class: Responsible Charge Verification Obligation
matched ontology label: Responsible Charge Verification Obligation
matches existing: true
source text: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control.
comment: Duty of a licensed engineer who seals documents produced by subordinates to exercise genuine, substantive direction and control over the work throughout its preparation, including setting technical parameters, reviewing outputs, and verifying conformance with professional standards, so that the seal reflects real professional oversight rather than mere administrative approval.
subclass of: EthicalObligation
scope note: [ResponsibleChargeVerificationObligation] Duty of a licensed engineer in responsible charge to conduct a comprehensive, experience-based verification of all work products before sealing or submitting them, including active involvement in design and development rather than merely reviewing completed documents, so that the engineer can genuinely certify the work meets professional and safety standards.
generated at time: 2026-06-04T18:07:43.735405+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Suspension Period Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.82
constraint type: ethical
flexibility: soft
mitigation strategies: Disclose the preliminary concern in suspension communications with appropriate qualification as unquantified
mitigation strategies: Document the concern in writing before suspending work
mitigation strategies: Request client acknowledgment of the disclosed risk before finalizing suspension
text references: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
violation impact: Client proceeds through suspension period without knowledge of a material safety risk, delaying protective action and potentially allowing conditions to worsen before work resumes.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:06.761320+00:00
first discovered in case: 8
match confidence: 0.8
match reasoning: The existing Preliminary Risk Disclosure Constraint addresses the duty to disclose a potential risk to public health or safety during a preliminary phase of work before suspending or transitioning work. The suspension-period scenario here is a specific application of that same concept: the engineer identifies a preliminary risk and then suspends work without disclosing it. The existing class covers this scenario adequately, though the suspension-period framing adds a temporal specificity not fully captured in the existing label. Matching as a variant with medium-high confidence.
matched ontology class: Preliminary Risk Disclosure Constraint
matched ontology label: Preliminary Risk Disclosure Constraint
matches existing: true
source text: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
comment: Ethical constraint requiring that an engineer who has identified a preliminary concern about a risk to public health or safety must disclose that concern to the client at the time of a work suspension, even when the risk has not yet been fully quantified, so that the client is not left uninformed of a material safety issue during the period when work is paused and no further investigation will occur.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [PreliminaryRiskDisclosureConstraint] Ethical and professional constraint requiring an engineer who identifies a potential risk to public health or safety during a preliminary phase of work to disclose that concern to the client before suspending, pausing, or transitioning work, even when the risk has not yet been fully quantified, so that the client can make informed decisions about how to proceed.
generated at time: 2026-06-05T02:22:06.761320+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Suspension Period Risk Disclosure Capability
type: Class
capability category: awareness
confidence: 0.78
domain specificity: Professional engineering practice involving project suspensions and incomplete risk analyses
enables actions: Communicate preliminary risk findings to a client at the time of suspension
enables actions: Distinguish between risks requiring immediate disclosure and those requiring further analysis
enables actions: Identify risks discovered before a work suspension
required for obligations: Preliminary Risk Disclosure Obligation
required for obligations: Suspension Period Risk Disclosure Obligation
skill level: advanced
text references: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:28.927578+00:00
first discovered in case: 8
match confidence: 0.78
match reasoning: Incomplete Analysis Disclosure Capability covers the obligation to recognize when a professional analysis has been suspended or left incomplete and to disclose the status and significance of unfinished findings to the client, including communicating identified but unquantified risks rather than remaining silent during a work suspension. This maps closely to Engineer L's failure to disclose the preliminary stormwater risk concern at the time of suspension. The match is medium confidence because the existing class emphasizes the suspension of analysis rather than the suspension of the engagement itself, but the core concept is the same.
matched ontology class: Incomplete Analysis Disclosure Capability
matched ontology label: Incomplete Analysis Disclosure Capability
matches existing: true
source text: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
comment: Capability to recognize when a work suspension creates an obligation to disclose identified but unquantified risks to a client before or during the suspension, including the ability to distinguish between risks that are sufficiently developed to warrant disclosure and those that remain too preliminary, and to communicate identified concerns even when the analysis is incomplete.
subclass of: Capability
scope note: [IncompleteAnalysisDisclosureCapability] Capability to recognize when a professional analysis has been suspended or left incomplete and to disclose the status and significance of unfinished findings to the client, including the ability to communicate identified but unquantified risks rather than remaining silent about them during a work suspension.
generated at time: 2026-06-05T02:22:28.927578+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Suspension Period Risk Disclosure Obligation
type: Class
confidence: 0.82
derived from principle: Proactive Risk Disclosure Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that the engineer communicated the identified risk to the client at or before the time of the suspension agreement.
nspe reference: II.1.a, II.3.b
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: During the preliminary design phase, Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase, as the likelihood of heavy stormwater flows will increase over time.
text references: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
violation consequences: Failure to disclose may allow a known risk to persist unaddressed during the suspension period, potentially resulting in harm to public welfare and professional discipline for the engineer.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:20:48.587109+00:00
first discovered in case: 8
match confidence: 0.78
match reasoning: The existing Preliminary Risk Disclosure Obligation covers the duty to disclose potential risks to public health or safety during a preliminary phase of work before the risk is fully quantified. This case instantiates that obligation in the specific context of a work suspension, where the engineer failed to disclose a preliminary concern during suspension communications. The suspension context adds a temporal qualifier but the core obligation is the same: disclose identified preliminary risks promptly so the client can make informed decisions. Matched as a variant with medium-high confidence.
matched ontology class: Preliminary Risk Disclosure Obligation
matched ontology label: Preliminary Risk Disclosure Obligation
matches existing: true
source text: During the preliminary design phase, Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase, as the likelihood of heavy stormwater flows will increase over time.
comment: Duty of an engineer who has identified a potential risk to public health or safety during an active engagement to disclose that risk to the client before or at the time of a work suspension, rather than remaining silent about the risk during communications about the suspension, so that the client has the opportunity to make informed decisions about the project during the suspension period.
subclass of: DisclosureObligation
scope note: [PreliminaryRiskDisclosureObligation] Duty of an engineer who identifies a potential risk to public health or safety during a preliminary phase of work to disclose that risk to the client and relevant stakeholders promptly, even before the risk has been fully quantified, so that the client can make informed decisions about project scope, suspension, or protective measures.
generated at time: 2026-06-05T02:20:48.587109+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Technical Citation Capability
type: Class
capability category: domain_specific
confidence: 0.8
domain specificity: Professional engineering report preparation and documentation
enables actions: Identify authoritative technical sources relevant to a work product
enables actions: Incorporate citations into AI-generated or AI-assisted reports
enables actions: Recognize absence of citations as an ethical deficiency in professional documents
required for obligations: Technical Citation Obligation
skill level: intermediate
text references: Absent this professional level of care, diligence, and documentation, Engineer A's use of the AI language processing software would be less than ethical.
text references: the facts do not indicate the AI-generated report included citations of pertinent documents of technical authority. Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:06.673267+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: the facts do not indicate the AI-generated report included citations of pertinent documents of technical authority. Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
comment: Capability to identify and include appropriate citations to pertinent documents of technical authority in professional work products, including the ability to recognize when AI-generated content lacks proper attribution and to supply required references.
subclass of: Capability
generated at time: 2026-06-03T14:11:06.673267+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Technical Citation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Peer reviewers
affected stakeholders: Regulatory bodies
confidence: 0.85
constraint type: procedural
flexibility: soft
mitigation strategies: Establish a citation checklist as part of document review process
mitigation strategies: Include citations to all referenced standards, codes, and technical documents
mitigation strategies: Review AI-generated content specifically for missing citations
text references: the facts do not indicate the AI-generated report included citations of pertinent documents of technical authority. Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
violation impact: Failure to give proper credit, inability to verify technical basis of work product, potential misrepresentation of the work's intellectual foundation, ethics code violation
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:08.316438+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: the facts do not indicate the AI-generated report included citations of pertinent documents of technical authority. Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
comment: Procedural and ethical constraint requiring that an engineer's professional work products include appropriate citations to pertinent documents of technical authority, ensuring proper attribution of sources and enabling verification of technical claims by clients and reviewers.
subclass of: DefeasibleConstraint
subclass of: ProceduralConstraint
generated at time: 2026-06-03T14:11:08.316438+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Technical Citation Obligation
type: Class
confidence: 0.88
derived from principle: Attribution and Credit Principle
enforcement level: mandatory
monitoring criteria: Work products contain citations to pertinent technical authority documents commensurate with the scope and risk of the work
nspe reference: III.9
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Professional community
stakeholders affected: Regulatory bodies
text references: Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
text references: the facts do not indicate the AI-generated report included citations of pertinent documents of technical authority
violation consequences: Violation of professional attribution standards; potential disciplinary action; erosion of client and public trust
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:09:34.826300+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Per Code section III.9, engineers are required to 'give credit for engineering work to those to whom credit is due,' so Engineer A's ethical use of the AI software would need to include appropriate citations.
comment: Duty of an engineer to include appropriate citations to pertinent documents of technical authority in professional work products, including those substantially generated or assisted by AI tools, so that the intellectual and technical basis of the work is transparent and properly attributed.
subclass of: EthicalObligation
generated at time: 2026-06-03T14:09:34.826300+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Technical Objectivity Principle
type: Class
abstract nature: High-level value requiring engineers to maintain the epistemic integrity of technical analysis even under institutional pressures that reward partisan advocacy, with the scope of the obligation requiring case-by-case interpretation.
confidence: 0.93
derived obligations: Distinguish technical findings from advocacy
derived obligations: Present all material technical facts regardless of their effect on the client's legal position
derived obligations: Refrain from structuring report language to deny alternative interpretations
extensional examples: NSPE Code provisions on objectivity and truthfulness in professional reports and testimony
operationalization: Requires engineers to present facts that cut against the client's position, to refrain from structuring reports to foreclose alternative interpretations, and to treat the adversarial context as irrelevant to the technical content of findings.
potential conflicts: Client Loyalty
potential conflicts: Litigation Neutrality Principle
principle category: fundamental_ethical
text references: Engineer B appears to have assumed a responsibility to defend the client municipality by the selective use of data. This is an egregious denial of the duties and responsibilities of a professional engineer in any setting, legal, quasi-legal or non-legal.
text references: Facts are not adversarial, even if they may be conflicting. Adversarial interests, however, are polarizing to the effect that some facts may be preferred by one interest over the other.
text references: It is not evident from the facts of the case that Engineer B's selective use of technical fact was inspired by the adversarial circumstance, nor does it matter.
value basis: Engineering analysis serves a truth-seeking function that is corrupted when technical authority is weaponized for adversarial ends. The public and the legal system rely on engineering reports as honest technical assessments, not advocacy documents.
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:34:00.918915+00:00
first discovered in case: 71
match confidence: 0.88
match reasoning: The Litigation Neutrality Principle addresses the obligation to render opinions based solely on technical analysis without shaping findings to favor the retaining party. This principle is closely related but operates at a higher level of abstraction, covering all professional engineering contexts, not only litigation, and emphasizing the epistemic character of engineering analysis as inherently non-adversarial. The case text explicitly generalizes the obligation beyond litigation settings. A new class is warranted to capture this broader, more fundamental value, with the Litigation Neutrality Principle as a domain-specific instantiation.
matches existing: false
source text: Facts are not adversarial, even if they may be conflicting. Adversarial interests, however, are polarizing to the effect that some facts may be preferred by one interest over the other.
comment: Professional principle requiring engineers to base reports, findings, and testimony on objective technical analysis of all available facts, refusing to selectively deploy evidence in service of a client's adversarial position, regardless of the legal or quasi-legal context of the engagement.
subclass of: FundamentalEthicalPrinciple
generated at time: 2026-06-04T14:34:00.918915+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Technical Record Review Capability
type: Class
capability category: domain_specific
confidence: 0.82
domain specificity: Geotechnical and civil engineering investigations involving field test records
enables actions: Assess the significance of available records to investigation conclusions
enables actions: Identify relevant field documentation for inclusion in analysis
enables actions: Obtain and review pile driving records
required for obligations: Complete Technical Reporting Obligation
required for obligations: Fact Gathering Diligence Obligation
required for obligations: Investigative Completeness Obligation
skill level: intermediate
text references: Engineer B's failure to inquire from the contractor, workers or others on the job is a failure of fact gathering diligence.
text references: Further, by excluding the pile driving records, Engineer B has denied himself the opportunity to present a rational for discounting their value, and thereby to serve his client.
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:36:09.201106+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: Geotechnical Analysis Capability covers technical competency in geotechnical methods but does not specifically address the procedural competency of identifying, obtaining, and reviewing available field records as part of an investigation. Investigative Inquiry Capability addresses pursuing lines of inquiry broadly but is framed around witness consultation and anomaly follow-up rather than the specific technical record review process. This is a distinct domain-specific competency.
matches existing: false
source text: Further, by excluding the pile driving records, Engineer B has denied himself the opportunity to present a rational for discounting their value, and thereby to serve his client.
comment: Ability to identify, obtain, and systematically review available technical records such as pile driving logs, test data, and field documentation as part of a technical investigation or evaluation, and to incorporate those records into the analysis.
subclass of: Capability
generated at time: 2026-06-04T14:36:09.201106+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Technology Role Limitation Obligation
type: Class
confidence: 0.87
derived from principle: Commercial Inducement Resistance Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer exercised independent professional judgment and did not rely solely on technological tool outputs as the basis for professional work products
nspe reference: II.2.a
obligation type: competence
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Professional engineering cannot be reduced to an activity whereby practitioners rely upon computers and technical information instead of time-tested professional experience and engineering judgment
text references: Relying on a how to CD-ROM appears to show a general disregard for the fundamental role that professional engineers play in protecting the public health and safety and minimizes the high level of knowledge and expertise necessary to perform these critical responsibilities
text references: it is the Board's position that technology has an important place in the practice of engineering, but it must never be a replacement of a substitute for engineering judgment
violation consequences: Professional discipline; public safety risk from engineering work performed without genuine professional judgment
discovered in case: 121
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:49:10.142160+00:00
first discovered in case: 121
match confidence: 0.88
match reasoning: The Technology Non-Substitution Obligation in the ontology captures the duty to ensure technological tools serve as instruments under the engineer's direction rather than substitutes for professional judgment. The present obligation is the same concept applied to the CD-ROM context. A medium-high match is appropriate because the ontology class is stated in terms of CADD systems but the definition is general enough to encompass any technological tool including CD-ROMs.
matched ontology class: Technology Non-Substitution Obligation
matched ontology label: Technology Non-Substitution Obligation
matches existing: true
source text: it is the Board's position that technology has an important place in the practice of engineering, but it must never be a replacement of a substitute for engineering judgment
comment: Duty of a licensed engineer to ensure that computers, software, CD-ROMs, and other technological tools serve as instruments supporting professional practice under the engineer's direction rather than as replacements for engineering judgment, and to recognize that technology has an important place in engineering practice only when it supplements rather than substitutes for genuine professional competence.
subclass of: CompetenceObligation
scope note: [TechnologyNon-SubstitutionObligation] Duty of a licensed engineer to ensure that technological tools, including CADD systems and similar computer-assisted platforms, serve as instruments of professional production under the engineer's direction rather than as substitutes for the engineer's own professional judgment, so that the engineer retains genuine intellectual and technical responsibility for the work product and does not incorporate system-generated solutions the engineer has not prepared or fully understands.
generated at time: 2026-06-04T18:49:10.142160+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Technology Substitution Prohibition Principle
type: Class
abstract nature: Requires ongoing interpretation of the boundary between legitimate tool use and impermissible substitution of tool output for professional judgment, particularly as tool capabilities evolve.
confidence: 0.9
derived obligations: Conduct comprehensive rather than high-level review of AI-generated technical work
derived obligations: Critically evaluate and challenge AI-generated outputs rather than accepting them
derived obligations: Define problem constraints and guidelines before delegating to AI tools
derived obligations: Verify that AI outputs meet independent professional standards before incorporation
extensional examples: BER Case 90-6 warning that CADD used beyond its ability has a propensity to be used as a crutch or substitute for judgment
extensional examples: BER Case 98-3 conclusion that technology must not replace or be used as a substitute for engineering judgment
extensional examples: Engineer A conducting only a high-level review of AI-generated design documents rather than substantive independent evaluation
operationalization: Requires engineers to outline solution guidelines and constraints before using AI tools, to critically evaluate and challenge tool outputs, to understand the reasoning behind outputs, and to accept only those outputs that satisfy independent professional standards.
potential conflicts: Professional Competence (efficient use of available tools)
potential conflicts: Responsible Charge Integrity Principle
principle category: fundamental_ethical
text references: As night follows day one can be assured that CADD utilized beyond its ability to serve as a valuable tool has a propensity to be utilized as a crutch or substitute for judgement.
text references: By relying on AI-assisted tools without a comprehensive verification process of its output, Engineer A risked violating this requirement.
text references: It is the [BER]'s position that technology has an important place in the practice of engineering, but it must never be a replacement of a substitute for engineering judgement.
text references: Much like directing an engineering intern to solve a problem, responsible use of AI requires an engineer to outline solution guidelines and constraints. Recommendations from the program or intern should not be blindly accepted, they should be considered and challenged and the resulting outputs should be understood.
value basis: Engineering judgment is the core professional contribution that licenses and professional obligations protect; allowing tools to replace rather than assist that judgment undermines the entire basis for professional licensure and public trust.
discovered in case: 7
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:08:23.434917+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: It is the [BER]'s position that technology has an important place in the practice of engineering, but it must never be a replacement of a substitute for engineering judgement.
comment: Fundamental professional principle prohibiting engineers from using technological tools, including AI-assisted drafting or automated design systems, as a substitute for independent engineering judgment, requiring instead that such tools serve only as aids subject to substantive professional evaluation and oversight.
subclass of: FundamentalEthicalPrinciple
generated at time: 2026-06-03T14:08:23.434917+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Technology Tool Non-Substitution Obligation
type: Class
confidence: 0.85
derived from principle: Technology Substitution Prohibition Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer directed the tool's use, set technical parameters, and critically reviewed outputs rather than passively accepting tool-generated content
nspe reference: II.2, III.2.b
obligation type: ethical
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system.
text references: Engineer B, a registered professional engineer signs and seals documents which are the results of the efforts of others using a CADD system working under Engineer B's direction and control.
violation consequences: Professional discipline; invalidation of sealed documents; reputational harm
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:07:43.735405+00:00
first discovered in case: 120
match confidence: 0.0
matches existing: false
source text: Engineer A, a registered professional engineer signs and seals documents he prepared using a CADD system.
comment: Duty of a licensed engineer to ensure that technological tools, including CADD systems and AI-assisted drafting platforms, serve as instruments of professional production under the engineer's direction rather than as substitutes for the engineer's own professional judgment, authorship, or oversight, so that the engineer retains genuine intellectual and technical responsibility for the work product.
subclass of: EthicalObligation
generated at time: 2026-06-04T18:07:43.735405+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Test Condition Replication Capability
type: Class
capability category: domain_specific
confidence: 0.9
domain specificity: Geotechnical and foundation engineering test programs
enables actions: Design test programs that replicate prior conditions as closely as practicable
enables actions: Disclose methodological differences and their potential effect on results
enables actions: Identify original test or construction conditions from records
enables actions: Recognize when deviations from original conditions have occurred
required for obligations: Methodological Consistency Obligation
skill level: advanced
text references: After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced.
text references: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
text references: The test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class addresses the technical competency of replicating prior test or construction conditions in a comparative investigation.
matches existing: false
source text: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving.
comment: Technical ability to reproduce the conditions of prior work when conducting comparative tests or investigations, and to recognize and disclose deviations that may affect the validity of results.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Test Methodology Deficiency State
type: Class
action constraints: Professional must not omit equipment failures from reports that rely on data from those tests
action constraints: Professional must not present conclusions as reliable when known test deficiencies undermine the data
activation conditions: Conclusions in the report rely on the deficient test data
activation conditions: Equipment fails or procedural deviations occur during testing
activation conditions: Testing or investigation is conducted to generate data for a professional report
activation conditions: The deficiencies are known to the professional issuing the report
confidence: 0.87
obligation activation: Duty to disclose equipment failures and procedural deviations in the report
obligation activation: Duty to qualify conclusions that rest on deficient test data
obligation activation: Duty to recommend retesting when deficiencies are material
persistence type: inertial
principle transformation: Transforms the general duty of truthfulness and objectivity into a specific obligation to disclose known test deficiencies and qualify any conclusions that depend on data generated under those deficient conditions.
state category: risk
termination conditions: Engagement concludes
termination conditions: Report is amended to disclose deficiencies and qualify conclusions accordingly
termination conditions: Testing is repeated under corrected conditions
text references: After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced
text references: Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving
text references: Engineer B did not report that the dynamic test equipment had failed
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:51.674939+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Engineer B did not report that the dynamic test equipment had failed
comment: State in which the testing or investigative methodology used to generate data for a professional report contains known deficiencies, including equipment failures, non-representative conditions, or procedural deviations, that materially affect the reliability of the data and the validity of conclusions drawn from it, creating obligations to disclose those deficiencies in any report relying on the data.
subclass of: RiskState
generated at time: 2026-06-04T14:26:51.674939+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Tool Substitution Recognition Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: General professional engineering practice
enables actions: Distinguish between a tool that aids a competent practitioner and one marketed as a replacement for competence
enables actions: Identify when a solicitation conflates tool access with professional qualification
enables actions: Recognize that a CD-ROM design library does not supply the judgment required for facilities design
enables actions: Refuse to offer services on the basis of tool possession alone
required for obligations: Tool Substitution Refusal Obligation
skill level: intermediate
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:46:28.378823+00:00
first discovered in case: 121
match confidence: 0.88
match reasoning: Technology Non-Substitution Judgment Capability directly addresses recognizing when a technological tool is being used as a substitute for professional judgment rather than as an aid to it, and resisting the temptation to incorporate system-generated solutions the engineer has not prepared or fully understands. This is the same core concept applied to a CD-ROM design library rather than a CADD system or AI platform. The match is high confidence as a variant of the same reusable class.
matched ontology class: Technology Non-Substitution Judgment Capability
matched ontology label: Technology Non-Substitution Judgment Capability
matches existing: true
source text: specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
comment: Capability of a licensed professional engineer to recognize when a software tool, automated design library, or similar product is being positioned as a substitute for the domain knowledge, training, and professional experience required to practice competently in a specialty area, and to resist treating the tool as conferring competence the engineer does not independently possess.
subclass of: Capability
scope note: [TechnologyNon-SubstitutionJudgmentCapability] Capability of a licensed professional engineer to recognize when a technological tool such as a CADD system or AI-assisted platform is being used as a substitute for professional judgment rather than as an aid to it, and to resist the temptation to incorporate system-generated solutions that the engineer has neither prepared nor fully understands, ensuring that the tool remains subordinate to the engineer's independent professional competence.
generated at time: 2026-06-04T18:46:28.378823+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Tool Substitution Refusal Obligation
type: Class
confidence: 0.88
derived from principle: Competence Boundary Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer did not expand service offerings into new technical domains solely on the basis of acquiring a software tool or automated design library
nspe reference: II.2
obligation type: competence
stakeholders affected: Clients
stakeholders affected: General public
stakeholders affected: Professional licensing boards
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services.
text references: Now - - thanks to a revolutionary new CD-ROM - specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience.
violation consequences: Professional discipline; public safety risk from deficient work products generated without genuine domain competence
discovered in case: 121
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T18:45:48.212115+00:00
first discovered in case: 121
match confidence: 0.82
match reasoning: The Technology Non-Substitution Obligation captures the duty to ensure technological tools serve as instruments under the engineer's direction rather than substitutes for professional judgment. This case instantiates that concept specifically in the context of a CD-ROM design library being used to enter an entirely new domain of practice, which is a variant of the same principle. Medium confidence because the existing class focuses on tools within an established practice area, while this case involves using a tool to enter a domain where no competence exists at all.
matched ontology class: TechnologyNonSubstitutionObligation
matched ontology label: Technology Non-Substitution Obligation
matches existing: true
source text: Now - - thanks to a revolutionary new CD-ROM - specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience.
comment: Duty of a licensed engineer to refrain from treating a software tool, CD-ROM library, or similar automated system as a substitute for the domain knowledge, education, and professional experience required to competently practice in a technical field, and to recognize that access to such a tool does not confer competence to offer professional services in that field.
subclass of: CompetenceObligation
scope note: [TechnologyNon-SubstitutionObligation] Duty of a licensed engineer to ensure that technological tools, including CADD systems and similar computer-assisted platforms, serve as instruments of professional production under the engineer's direction rather than as substitutes for the engineer's own professional judgment, so that the engineer retains genuine intellectual and technical responsibility for the work product and does not incorporate system-generated solutions the engineer has not prepared or fully understands.
generated at time: 2026-06-04T18:45:48.212115+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Tool Substitution for Competence State
type: Class
action constraints: Must not market services as competent practice when competence rests solely on tool availability
action constraints: Must not seal or certify work product generated by a tool the professional cannot independently evaluate
activation conditions: Professional acquires or deploys a tool marketed as enabling practice in an unfamiliar domain
activation conditions: Professional has no independent basis for evaluating the tool's outputs
activation conditions: Professional proceeds to offer or deliver services based on tool outputs without supervision
confidence: 0.87
obligation activation: Duty to disclose reliance on automated tools to clients
obligation activation: Duty to obtain competent supervision before delivering work product
obligation activation: Duty to verify that tool outputs meet applicable professional standards
persistence type: inertial
principle transformation: Transforms the general principle that engineers shall practice only in areas of competence into a specific prohibition on treating automated tools as competence proxies and a requirement to maintain independent professional judgment over tool outputs.
state category: competence
termination conditions: Professional acquires independent competence in the domain
termination conditions: Professional associates with a competent engineer who provides genuine oversight
termination conditions: Professional discontinues use of the tool as a competence substitute
text references: Engineer A orders the CD-ROM and begins to offer facilities design and construction services
text references: never designed a highway before? No problem. Just point to the 'Highways' window and click
text references: thanks to a revolutionary new CD-ROM - specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
discovered in case: 121
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T18:42:57.570207+00:00
first discovered in case: 121
match confidence: 0.75
match reasoning: Unfamiliar Tool Deployment State captures the use of a tool without prior experience. This case adds the distinct dimension that the tool is being used as a wholesale substitute for domain competence rather than merely as an unfamiliar instrument within an area where the professional otherwise has expertise. The substitution-for-competence aspect is materially different and ethically more serious, warranting a distinct class, though the existing class is the closest match.
matched ontology class: Unfamiliar Tool Deployment State
matched ontology label: Unfamiliar Tool Deployment State
matches existing: true
source text: thanks to a revolutionary new CD-ROM - specifying, designing and costing out any construction project is as easy as pointing and clicking your mouse - no matter your design experience
comment: State in which a professional treats a commercial software tool, database, or automated system as a functional substitute for the domain knowledge, training, and experience required to practice competently in a given area, rather than as an instrument augmenting existing professional judgment, creating conditions in which the professional lacks the background necessary to evaluate, correct, or take responsibility for the tool's outputs.
subclass of: CompetenceState
scope note: [UnfamiliarToolDeploymentState] State in which a professional uses a tool, technology, or method with which they have no prior experience, creating elevated risk of undetected errors and triggering heightened obligations of verification, disclosure, and caution before relying on outputs for professional work products.
generated at time: 2026-06-04T18:42:57.570207+00:00
was attributed to: Case 121 Extraction
was attributed to: claude-sonnet-4-6

Unbuildable Contract Bid State
type: Class
action constraints: Contractor-engineer may not later claim ignorance of deficiencies apparent from document review
action constraints: Contractor-engineer must not submit a bid that ignores known inadequacies without disclosure
activation conditions: A contractor-engineer reviews bidding documents prior to submitting a bid
activation conditions: The contractor-engineer submits a bid without reflecting the deficiency or seeking clarification
activation conditions: The documents are materially incomplete or inadequate for construction
confidence: 0.78
obligation activation: Obligation to disclose known inadequacies to the owner
obligation activation: Obligation to reflect known deficiencies in bid pricing
obligation activation: Obligation to seek clarification when documents appear incomplete
persistence type: inertial
principle transformation: Transforms the general duty of honesty and competence into a specific obligation to disclose known document deficiencies at the bid stage rather than proceeding silently and later attributing construction failures to the design engineer.
state category: risk
termination conditions: Contract is withdrawn or rebid with complete documents
termination conditions: Contractor adjusts bid to include items for additional services
termination conditions: Contractor seeks clarification and receives adequate design information
text references: Engineer C had no one to fault but himself for the problems Engineer C encountered in attempting to build the project
text references: Engineer C submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involved
text references: Engineer C's actions in bidding on an 'unbuildable' contract is also very troubling
text references: Engineer C's bid should have reflected that fact and contained appropriate bid items for additional services required to complete the work
discovered in case: 85
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T16:47:21.871867+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer C's actions in bidding on an 'unbuildable' contract is also very troubling
comment: State in which a contractor-engineer bids on a contract knowing or having reasonable grounds to know that the engineering documents are incomplete or inadequate to support construction, without adjusting the bid to reflect the additional work required or seeking clarification from the owner or design engineer, thereby assuming known risks without disclosure and forfeiting the ability to claim ignorance of resulting construction problems.
subclass of: RiskState
generated at time: 2026-06-04T16:47:21.871867+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Undisclosed AI Contribution State
type: Class
action constraints: Must include citations and attribution consistent with professional standards
action constraints: Must not represent AI-generated content as solely the product of the professional's own analysis without disclosure
activation conditions: AI tools substantially contributed to the work product
activation conditions: No disclosure of AI contribution made to client or relevant parties
confidence: 0.86
obligation activation: Duty to avoid creating false impressions about the origin of work
obligation activation: Duty to disclose substantial AI contributions to clients
obligation activation: Duty to provide appropriate attribution in work products
persistence type: inertial
principle transformation: Transforms the general honesty and attribution principles into a concrete obligation to proactively disclose when AI has substantially shaped a work product, even absent a universal regulatory mandate to do so.
state category: information
termination conditions: Appropriate attribution included in the work product
termination conditions: Client acknowledges and accepts the AI contribution
termination conditions: Disclosure of AI use made to client
text references: AI, while not a human contributor, fundamentally shaped the report and design documents, warranting disclosure under Code section III.9.
text references: There are currently no universal guidelines mandating AI disclosure in engineering work, but best practices suggest informing clients when AI substantially contributes to a work product.
text references: While Engineer A reviewed the content, the lack of disclosure raises concerns about transparency.
discovered in case: 7
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-03T14:01:36.958645+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: While Engineer A reviewed the content, the lack of disclosure raises concerns about transparency.
comment: State in which artificial intelligence tools have made a substantial contribution to a professional work product but that contribution has not been disclosed to the client or relevant parties, creating a transparency deficit that implicates attribution obligations, client trust, and professional honesty standards.
subclass of: InformationState
generated at time: 2026-06-03T14:01:36.958645+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Undisclosed AI Use State
type: Class
action constraints: Should not represent AI-generated content as entirely self-authored without disclosure
action constraints: Should not seal or certify work without disclosing the role of AI in its production where standards require
activation conditions: AI tools are used to generate or substantially draft a professional work product
activation conditions: The professional omits disclosure of AI use when submitting the work product
confidence: 0.88
obligation activation: Obligation to comply with professional standards governing attribution and transparency
obligation activation: Obligation to correct any false impression created by non-disclosure
obligation activation: Obligation to disclose AI use to clients and relevant parties
persistence type: inertial
principle transformation: Transforms honesty and transparency principles into specific disclosure obligations when AI tools have played a material role in producing a professional work product.
state category: information
termination conditions: Disclosure of AI use is made to the client or relevant parties
termination conditions: Work product is resubmitted with appropriate attribution and disclosure
text references: Engineer A did not cite the AI-assisted drafting tools they used to generate the engineering design documents
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T14:00:13.061399+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
comment: State in which a professional has used AI tools to generate or substantially assist in producing a work product but has not disclosed that use to the client, employer, or relevant professional body, creating a transparency deficit that may implicate honesty obligations, professional standards, and client trust.
subclass of: InformationState
generated at time: 2026-06-03T14:00:13.061399+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Undisclosed Deadline Pressure State
type: Class
action constraints: Professional must not allow client or approving authority to rely on a deliverable without knowing its limitations
action constraints: Professional must not seal and submit documents known to be incomplete without disclosing the reason and the incompleteness
activation conditions: Professional does not disclose the pressure or its effect to affected parties at time of delivery
activation conditions: Professional experiences deadline pressure that affects completeness or quality of deliverable
confidence: 0.85
obligation activation: Duty to disclose factors that materially affected the quality of the professional's work product
obligation activation: Duty to notify client when deadline constraints prevent delivery of a complete and adequate product
obligation activation: Duty to seek deadline extension rather than deliver a known-incomplete product
persistence type: inertial
principle transformation: Transforms general honesty and faithful-agent principles into a specific obligation to disclose when external pressures have compromised the professional's ability to deliver a complete and adequate work product.
state category: information
termination conditions: Affected parties are informed and given opportunity to respond
termination conditions: Corrected deliverable is provided
termination conditions: Professional discloses the deadline pressure and its effect on the work product
text references: did not inform anyone as to their incompleteness
text references: he felt pressured to deliver the drawings and specifications on a specified date
discovered in case: 85
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T16:46:12.006396+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: he felt pressured to deliver the drawings and specifications on a specified date
comment: State in which a professional has experienced time pressure that caused or contributed to the production of an incomplete or substandard work product, but has not disclosed that pressure or its effect on deliverable quality to the client, approving authority, or other affected parties, leaving those parties unable to assess the reliability of the work product.
subclass of: InformationState
generated at time: 2026-06-04T16:46:12.006396+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Undisclosed Preliminary Risk State
type: Class
action constraints: Professional should communicate preliminary concerns even when unquantified
action constraints: Professional should not allow work suspension to serve as a reason to defer disclosure of a known risk concern
activation conditions: Client is not informed of the concern at the time of suspension
activation conditions: Professional identifies a preliminary risk concern during contracted work
activation conditions: Work is suspended or interrupted before the concern is disclosed
confidence: 0.82
obligation activation: Duty to disclose material risk concerns to the client
obligation activation: Duty to protect public health and safety
obligation activation: Obligation not to withhold information material to the client's decisions
persistence type: inertial
principle transformation: Transforms the general duty of honest communication into a specific obligation to disclose preliminary risk findings before or at the time of any work suspension, so that the client can make informed decisions during the interruption.
state category: information
termination conditions: Professional discloses the concern to the client
termination conditions: Risk is formally assessed and communicated
termination conditions: Work resumes and disclosure is made
text references: Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase
text references: Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source
discovered in case: 8
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T02:15:59.482935+00:00
first discovered in case: 8
match confidence: 0.72
match reasoning: The existing Unverified Risk Concern State captures the intermediate epistemic condition where a professional has a concern but not yet a confirmed finding. However, the distinctive feature here is that the concern was not disclosed at the time of work suspension, creating a transparency deficit that persists through the interruption. The existing class does not specifically capture the non-disclosure dimension during a work suspension. A medium-confidence match is appropriate, but the non-disclosure aspect during suspension is a meaningful additional element.
matched ontology class: Unverified Risk Concern State
matched ontology label: Unverified Risk Concern State
matches existing: true
source text: Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase
comment: State in which a professional has identified a preliminary concern about a potential risk to public safety or welfare during the course of contracted work, but has not disclosed that concern to the client or affected parties before a work suspension or other interruption occurs, leaving the client without information needed to make informed decisions during the intervening period.
subclass of: InformationState
scope note: [UnverifiedRiskConcernState] State in which a professional has a concern or suspicion about a potential risk but has not yet developed the analysis to a point where the concern constitutes a technical or factual finding. The concern is real but unquantified, creating an intermediate epistemic condition that does not yet trigger mandatory disclosure obligations but may support prudent voluntary disclosure.
generated at time: 2026-06-05T02:15:59.482935+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Unpermitted Environmental Alteration State
type: Class
action constraints: Professional may not assist client in concealing or perpetuating the violation
action constraints: Professional must not misrepresent the site condition in any subsequent professional work
activation conditions: Alteration constitutes a violation of applicable federal or state environmental law
activation conditions: Client installs fill material or otherwise alters regulated environmental feature without permits
activation conditions: Professional observes or becomes aware of the unpermitted alteration
confidence: 0.88
obligation activation: Duty to assess whether the violation creates a public safety or environmental risk requiring mandatory reporting
obligation activation: Duty to consider whether continued professional silence constitutes complicity in ongoing violation
obligation activation: Obligation to evaluate post-engagement reporting duties triggered by confirmed regulatory violation
persistence type: inertial
principle transformation: Transforms general environmental stewardship principles and post-engagement duties into concrete obligations to evaluate mandatory disclosure to regulatory authorities when a client has committed a substantial unpermitted alteration of a regulated environmental feature.
state category: risk
termination conditions: Client obtains required permits or regulatory authorization retroactively
termination conditions: Fill or alteration is removed and site restored to compliant condition
termination conditions: Regulatory authority issues enforcement action resolving the violation
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations
text references: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
discovered in case: 86
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T17:25:48.580472+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
comment: State in which a client or property owner has made a substantial physical alteration to an environmentally regulated site, such as filling wetlands, without obtaining required permits, variances, or regulatory approvals, creating a condition of active legal violation and triggering the professional's obligations to assess reporting duties to regulatory authorities.
subclass of: RiskState
generated at time: 2026-06-04T17:25:48.580472+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Unquantified Risk Awareness State
type: Class
action constraints: Professional should not suspend work without communicating identified concerns
action constraints: Professional should not treat unquantified risk as equivalent to no risk
activation conditions: Professional identifies a potential risk during preliminary work
activation conditions: Risk assessment is incomplete or suspended before quantification is achieved
confidence: 0.85
obligation activation: Duty to disclose known concerns to client even before full quantification
obligation activation: Duty to resume and complete risk assessment when work resumes
obligation activation: Precautionary duty to flag potential third-party harm
persistence type: inertial
principle transformation: Transforms general honesty and public safety principles into a concrete obligation to communicate preliminary risk findings to the client before or at the time work is suspended, rather than waiting for full quantification.
state category: risk
termination conditions: Risk is eliminated by design change
termination conditions: Risk is fully quantified and characterized
termination conditions: Work is permanently abandoned
text references: Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase
text references: Engineer L does not mention to Client X the potential increased risk
text references: before Engineer L can quantify the increased risk, Client X encounters unexpected financial setbacks
discovered in case: 8
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T09:58:09.658057+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase
comment: State in which a professional has identified a potential risk to third parties or the public but has not yet completed the analysis needed to quantify or confirm that risk, creating an intermediate epistemic condition that still triggers preliminary disclosure and precautionary obligations even though the full scope of harm remains uncertain.
subclass of: RiskState
generated at time: 2026-06-04T09:58:09.658057+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Unreviewed Incomplete Design State
type: Class
action constraints: Reviewer must not allow incomplete work to advance without disclosure
action constraints: Reviewer must not approve work beyond their competence
activation conditions: A reviewing engineer approves a design submission
activation conditions: The reviewer either lacked competence or failed to apply adequate review
activation conditions: The submission is materially incomplete or deficient
confidence: 0.8
obligation activation: Obligation to notify supervisors when unable to perform adequate review
obligation activation: Obligation to recognize competence limits and escalate to a qualified reviewer
obligation activation: Obligation to refuse approval of incomplete submissions
persistence type: inertial
principle transformation: Transforms the general duty of competence and professional review into a specific obligation to escalate or refuse approval when the reviewer cannot adequately evaluate the submission.
state category: risk
termination conditions: A competent reviewer re-examines and properly evaluates the submission
termination conditions: Deficiencies are identified and corrected
termination conditions: The project is halted pending correction
text references: Engineer B's approval of Engineer A's incomplete plans is troubling
text references: If Engineer B was not able to perform the necessary reviews of Engineer A's work, Engineer B should have provided this information to a supervisor who would have assigned an appropriate engineer to perform the review
text references: the failure to recognize the lack of competency and take appropriate action to address the situation is a violation of the NSPE Code
discovered in case: 85
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T16:47:21.871867+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineer B's approval of Engineer A's incomplete plans is troubling
comment: State in which a reviewing engineer has approved or accepted a design submission that is materially incomplete, either because the reviewer lacked the competence to detect the deficiencies or failed to apply adequate scrutiny, resulting in an incomplete work product advancing through the approval process without correction.
subclass of: RiskState
generated at time: 2026-06-04T16:47:21.871867+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Unsuccessful Project Advisory Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.91
constraint type: ethical
flexibility: soft
mitigation strategies: Cease participation if the client overrides a safety-critical recommendation
mitigation strategies: Document the advisory and the client's response
mitigation strategies: Formally advise the client in writing when the engineer believes a project will not succeed without specific measures
text references: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
text references: Engineer L notified Client X of this risk. Consistent with Code sections I.4, II.3.a, II.3.b, III.1.b, and III.3.a.
text references: Section III.1.b. clearly requires the engineer to inform a client when the engineer believes that a project will not be successful. The term 'successful' includes not merely the structural and economic success of a project but also the success of the project from a safety standpoint.
violation impact: Client proceeds without informed understanding of project risks; engineer fails professional duty to advise; public safety may be compromised.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:13.190895+00:00
first discovered in case: 8
match confidence: 0.93
match reasoning: The Project Success Advisory Constraint in the ontology captures exactly this concept: the requirement to advise a client when the engineer believes a project will not be successful, with success defined to include safety outcomes. The BER Case 84-5 and Engineer L facts are direct instantiations of that class.
matched ontology class: Project Success Advisory Constraint
matched ontology label: Project Success Advisory Constraint
matches existing: true
source text: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
comment: Ethical constraint requiring an engineer to advise a client or employer when the engineer believes a project will not be successful, where success encompasses structural, economic, and safety outcomes. This obligation must be fulfilled before the engineer can be said to have met professional ethics requirements, and it applies whenever the engineer's professional judgment indicates that proceeding without specific measures will result in project failure in any of these dimensions.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
scope note: [ProjectSuccessAdvisoryConstraint] Ethical constraint requiring an engineer to advise a client or employer when the engineer believes a project will not be successful, where success encompasses not only structural and economic outcomes but also safety outcomes. This obligation must be fulfilled before the engineer can be said to have met professional ethics requirements, and it applies whenever the engineer's professional judgment indicates that proceeding without specific measures will result in project failure in any of these dimensions.
generated at time: 2026-06-05T02:27:13.190895+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Verbal Only Disclosure State
type: Class
action constraints: Professional must not allow a public hearing or decision to proceed on incomplete written record
action constraints: Professional must not submit a written report that omits material findings already communicated verbally
activation conditions: Professional communicates the finding verbally to client
activation conditions: Professional identifies a material technical finding
activation conditions: Professional omits the finding from a written report submitted to a public authority or decision-making body
confidence: 0.88
obligation activation: Duty to be objective and truthful in professional reports
obligation activation: Duty to ensure public authorities have complete information
obligation activation: Duty to include all relevant and pertinent information in written reports
persistence type: inertial
principle transformation: Transforms the general duty of truthfulness and completeness into a specific obligation to document and submit material findings in writing whenever a report is submitted to a public authority.
state category: information
termination conditions: Finding is documented in a written report
termination conditions: Written disclosure is submitted to all relevant parties
text references: Engineer A verbally mentioned the concern, but Engineer A did not include the information in a written report that will be submitted to a public authority
text references: Engineer Doe verbally reported to XYZ that their discharge will lower the water quality in the receiving body of water below standards. XYZ instructed Engineer Doe not to complete a written report
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-05T02:17:00.931476+00:00
first discovered in case: 8
match confidence: 0.88
match reasoning: The existing class Incomplete Written Disclosure State directly captures the condition in which a professional has verbally communicated a material finding but omitted it from a written report submitted to a public authority, which is precisely the pattern in both BER Case 76-4 and BER Case 07-6 analyzed here.
matched ontology class: Incomplete Written Disclosure State
matched ontology label: Incomplete Written Disclosure State
matches existing: true
source text: Engineer Doe verbally reported to XYZ that their discharge will lower the water quality in the receiving body of water below standards. XYZ instructed Engineer Doe not to complete a written report
comment: State in which a professional has communicated a material technical finding or concern to a client verbally but has not reduced that finding to writing, creating a condition in which the professional's disclosure obligations under codes requiring objective and truthful written reports remain unfulfilled, and in which the client or a public authority may act on incomplete or unrecorded information.
subclass of: InformationState
scope note: [IncompleteWrittenDisclosureState] State in which a professional has verbally communicated a material finding or concern to a client but has omitted that finding from a written report submitted to a public authority or other decision-making body, creating a transparency deficit and a breach of the duty to be objective and truthful in professional reports.
generated at time: 2026-06-05T02:17:00.931476+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Water Commission Chief Engineer
type: Class
confidence: 0.85
role category: employer_relationship
text references: Engineer A is a professional engineer who serves as the superintendent and chief engineer for the Metropolitan Water Commission (MWC)
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T11:17:25.675106+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Engineer A is a professional engineer who serves as the superintendent and chief engineer for the Metropolitan Water Commission (MWC)
comment: A licensed professional engineering role in which the practitioner serves simultaneously as superintendent and chief engineer for a public water utility, bearing professional accountability for technical recommendations on water supply, treatment adequacy, and public health protection, while operating within a governance structure where elected or appointed commissioners hold final decision-making authority.
subclass of: EmployerRelationshipRole
subclass of: EngineerRole
generated at time: 2026-06-05T11:17:25.675106+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Water Treatment Consulting Engineer
type: Class
confidence: 0.87
role category: provider_client
text references: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T11:17:25.675106+00:00
first discovered in case: 76
match confidence: 0.72
match reasoning: Engineer B is a consulting engineer, which is a specialization of Consultant Role. However, the role is specifically an engineering consulting role focused on water treatment evaluation, making it more precisely a specialization of Engineer Role or Consultant Role. Matched as a specialization of Consultant Role at medium confidence because the engineering specialty and public health protection obligations distinguish it from the generic consultant archetype.
matched ontology class: ConsultantRole
matched ontology label: Consultant Role
matches existing: true
source text: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline
comment: A licensed professional engineering role in which the practitioner is retained by a public water utility to evaluate water treatment requirements associated with a change in water supply source, prepare technical reports recommending capital improvements and timelines, and advise the utility on risks to public health such as lead leaching from aging service infrastructure.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [ConsultantRole] Professional engaged for expert advice on a specific aspect of a project. Engineering consultants are classified under EngineerRole. This head covers non-engineering advisory roles.
generated at time: 2026-06-05T11:17:25.675106+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Water Treatment Engineering Report Resource
type: Class
authority source: Retained consulting engineer
confidence: 0.85
extensional function: Provides the technical grounding for engineering recommendations on water supply changes, establishing the factual and analytical basis for professional advice to a public authority.
resource category: reference_material
text references: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline for further evaluation of water quality, design, and construction of improvements
usage context: Capital planning for water utilities
usage context: Public health risk assessment in water engineering
usage context: Water source change evaluation
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-05T11:17:15.547667+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline for further evaluation of water quality, design, and construction of improvements
comment: A formal technical report produced by a consulting engineer evaluating water treatment requirements, capital investment needs, and implementation timelines associated with a change in water supply source or treatment process. Such reports provide the technical basis for infrastructure decisions and serve as primary professional knowledge sources in water utility planning.
subclass of: ReferenceMaterial
generated at time: 2026-06-05T11:17:15.547667+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Water Treatment Evaluation Capability
type: Class
capability category: domain_specific
confidence: 0.85
domain specificity: Water treatment engineering and public water supply management
enables actions: Assess water quality implications of source change
enables actions: Develop capital investment and timeline recommendations for treatment upgrades
enables actions: Identify required treatment infrastructure improvements
required for obligations: Drinking Water Safety Obligation
required for obligations: Engineer B Drinking Water Safety
required for obligations: Engineers A B Project Success Notification
skill level: expert
text references: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline for further evaluation of water quality, design, and construction of improvements.
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:25:14.530972+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline for further evaluation of water quality, design, and construction of improvements.
comment: Technical capability to evaluate the water treatment requirements associated with a change in public water supply source, including the ability to assess water quality parameters, identify required treatment processes, estimate capital investment needs, and develop a realistic timeline for design, evaluation, and construction of treatment improvements sufficient to protect public health.
subclass of: Capability
generated at time: 2026-06-05T11:25:14.530972+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Wave Equation Analysis Resource
type: Class
authority source: Geotechnical engineering professional consensus and published analytical methods
confidence: 0.78
extensional function: Provides an accepted analytical framework for translating field driving records into pile capacity estimates, grounding professional judgments about whether piles meet design requirements.
resource category: technical_standard
text references: applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements
usage context: Dispute resolution technical analysis
usage context: Foundation design review
usage context: Pile capacity evaluation
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:23.227248+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements
comment: A documented analytical method or calculation applying wave equation principles to pile driving data to estimate pile capacity from blow count and driving resistance records. This method is an accepted engineering technique for evaluating driven pile performance and serves as a technical knowledge source in foundation engineering practice.
subclass of: TechnicalStandard
generated at time: 2026-06-04T14:26:23.227248+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Wetland Delineation Engineer
type: Class
confidence: 0.82
role category: provider_client
text references: Engineer A is an environmental engineer. Engineer A performs wetland delineation services on the client's wetland site.
discovered in case: 86
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T17:25:19.255251+00:00
first discovered in case: 86
match confidence: 0.78
match reasoning: Wetland delineation is a specialization of environmental engineering practice. The existing Environmental Engineer class covers environmental analysis and technical reports bearing licensure-based accountability, which encompasses this role. Matching as a specialization at medium confidence.
matched ontology class: Environmental Engineer
matched ontology label: Environmental Engineer
matches existing: true
source text: Engineer A is an environmental engineer. Engineer A performs wetland delineation services on the client's wetland site.
comment: A licensed professional engineering role in which the practitioner is retained to perform wetland delineation services, assess wetland boundaries, and produce technical findings for a client site, bearing professional obligations of accuracy, completeness, and disclosure of violations of federal and state environmental laws discovered in connection with the engagement.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [EnvironmentalEngineer] A professional engineering role specializing in environmental systems, contaminant analysis, groundwater monitoring, and related infrastructure design, bearing licensure-based accountability for technical reports and engineering documents delivered to clients.
generated at time: 2026-06-04T17:25:19.255251+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Wetland Delineation Report Resource
type: Class
authority source: Licensed environmental engineering professionals
confidence: 0.88
extensional function: Provides the technical baseline that defines the scope of regulated wetland area and grounds professional accountability for subsequent site changes
resource category: reference_material
text references: Engineer A performs wetland delineation services on the client's wetland site
usage context: Professional accountability
usage context: Regulatory compliance baseline
usage context: Wetland boundary determination
discovered in case: 86
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T17:25:28.729274+00:00
first discovered in case: 86
match confidence: 0.0
matches existing: false
source text: Engineer A performs wetland delineation services on the client's wetland site
comment: A formal technical report produced by a qualified environmental engineer documenting the boundaries, extent, and characteristics of wetland areas on a subject property. Such reports establish the baseline conditions for regulatory compliance and serve as primary reference documents for subsequent permitting, enforcement, and professional accountability determinations.
subclass of: ReferenceMaterial
generated at time: 2026-06-04T17:25:28.729274+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Wetland Fill Violator Client
type: Class
confidence: 0.8
role category: provider_client
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
text references: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
discovered in case: 86
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T17:25:19.255251+00:00
first discovered in case: 86
match confidence: 0.75
match reasoning: The client here is the party that commissioned wetland delineation services and is the subject of the violation. The existing Client Role covers the party that commissions project work. This is a specialization adding the violation context, so matching to Client Role at medium confidence.
matched ontology class: ClientRole
matched ontology label: Client Role
matches existing: true
source text: the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions
comment: A client who has commissioned professional environmental engineering services for a wetland site and subsequently installs fill material on that site without required permits, variances, or permissions, thereby committing a substantial violation of federal and state environmental laws and placing the engineer in a conflict between client confidentiality and public welfare obligations.
subclass of: ClientRole
subclass of: ProviderClientRole
scope note: [ClientRole] Party that commissions the project work. This is the occupational archetype. The duty relationship is carried separately by :ProviderClientRole.
generated at time: 2026-06-04T17:25:19.255251+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Wetland Regulatory Knowledge Capability
type: Class
capability category: domain_specific
confidence: 0.82
domain specificity: Environmental engineering with specialization in wetland delineation and wetland regulatory compliance
enables actions: Assess the magnitude of the violation in terms of acreage and regulatory thresholds
enables actions: Identify that fill material placed without permits violates federal and state wetland laws
enables actions: Identify the appropriate federal and state regulatory authorities to notify
required for obligations: Environmental Compliance Reporting Obligation
required for obligations: Observed Violation Disclosure Obligation
required for obligations: Post-Engagement Violation Reporting Obligation
skill level: expert
text references: Engineer A is an environmental engineer.
text references: Engineer A performs wetland delineation services on the client's wetland site.
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:31:02.848953+00:00
first discovered in case: 86
match confidence: 0.75
match reasoning: Domain Expertise covers professional domain-specific knowledge and competencies. Wetland regulatory knowledge is a specialized instance of domain expertise. The existing class is a reasonable parent match, but the wetland regulatory dimension is sufficiently specific and recurrent in environmental engineering ethics cases to warrant a distinct subclass capturing both the technical delineation competency and the regulatory compliance knowledge dimension.
matched ontology class: DomainExpertise
matched ontology label: Domain Expertise
matches existing: true
source text: Engineer A is an environmental engineer.
comment: Domain-specific technical and legal competency in federal and state wetland regulations, including the ability to identify permit requirements, recognize unpermitted fill activity, assess the substantiality of a violation, and determine which regulatory authorities have jurisdiction over wetland fill violations.
subclass of: Capability
scope note: [DomainExpertise] Professional domain-specific knowledge and competencies (Hallamaa & Kalliokoski 2022, Doernberg & Truog 2023)
generated at time: 2026-06-04T17:31:02.848953+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Whistleblower Conscience Constraint
type: Class
affected stakeholders: Employer
affected stakeholders: Engineer
affected stakeholders: Funding Agencies
affected stakeholders: Public
confidence: 0.82
constraint type: ethical
flexibility: soft
mitigation strategies: Distinguish cases involving public safety from those involving only fiscal or quality concerns
mitigation strategies: Document concerns thoroughly before deciding whether to escalate
mitigation strategies: Seek legal counsel regarding whistleblower protections
text references: if an engineer feels strongly that an employer's course of conduct is improper when related to public concerns, and if the engineer feels compelled to blow the whistle to expose facts as he sees them, he may well have to pay the price of loss of employment
text references: the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience
text references: the ethical duty or right of the engineer becomes a matter of personal conscience, but the Board was unwilling to make a blanket statement that there is an ethical duty in these kinds of situations
violation impact: No professional ethics violation for declining to escalate; personal consequences such as employment loss may follow voluntary escalation
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:56:15.795068+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience
comment: Ethical constraint establishing that when an engineer identifies employer or organizational conduct that is improper in relation to public concerns but does not involve a danger to public health or safety, the engineer has an ethical right but not a mandatory ethical duty to report or escalate that conduct beyond the employer's rejection of the engineer's reports. Pursuing such disclosure is a matter of personal conscience, and the engineer may bear personal consequences such as loss of employment for doing so.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
generated at time: 2026-06-04T16:56:15.795068+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Whistleblower Conscience Judgment Capability
type: Class
capability category: reasoning
confidence: 0.82
domain specificity: Professional engineering practice in defense, public works, and other contexts involving public funds or public interest
enables actions: Assess whether improper conduct involves public health or safety
enables actions: Decide whether to escalate concerns beyond internal channels
enables actions: Distinguish ethical right from ethical duty in disclosure decisions
enables actions: Weigh personal conscience against professional risk
required for obligations: Whistleblower Conscience Obligation
skill level: advanced
text references: if an engineer feels strongly that an employer's course of conduct is improper when related to public concerns, and if the engineer feels compelled to blow the whistle to expose facts as he sees them, he may well have to pay the price of loss of employment
text references: the ethical duty or right of the engineer becomes a matter of personal conscience, but the Board was unwilling to make a blanket statement that there is an ethical duty in these kinds of situations
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:55:58.579791+00:00
first discovered in case: 85
match confidence: 0.62
match reasoning: Safety Disclosure Escalation Capability addresses escalation to regulatory authorities when internal resolution fails, but the present capability is distinct in that it concerns the threshold judgment between ethical right and ethical duty in non-safety public interest contexts, and the personal conscience dimension of that judgment. The match is weak enough that a new class is warranted, though there is partial conceptual overlap.
matched ontology class: Safety Disclosure Escalation Capability
matched ontology label: Safety Disclosure Escalation Capability
matches existing: true
source text: if an engineer feels strongly that an employer's course of conduct is improper when related to public concerns, and if the engineer feels compelled to blow the whistle to expose facts as he sees them, he may well have to pay the price of loss of employment
comment: Capability to recognize when employer or organizational conduct that is improper in relation to public concerns rises to the level where personal conscience compels disclosure beyond internal reporting, including the ability to assess whether the situation involves public health and safety or a lesser public interest, and to weigh the personal and professional costs of external disclosure against the ethical right to pursue the matter.
subclass of: Capability
scope note: [SafetyDisclosureEscalationCapability] Capability to recognize when internal resolution of a safety concern has failed and to escalate disclosure to appropriate regulatory authorities, including the ability to sequence escalation steps correctly by first advising the responsible engineer before notifying authorities.
generated at time: 2026-06-04T16:55:58.579791+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Whistleblower Conscience Obligation
type: Class
confidence: 0.82
derived from principle: Whistleblower Conscience Principle
enforcement level: conditional
monitoring criteria: Whether the engineer recognized the distinction between a matter of personal conscience and a mandatory reporting duty, and acted accordingly
nspe reference: I.1
obligation type: ethical
stakeholders affected: Employer
stakeholders affected: Engineer
stakeholders affected: Public
text references: the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience
text references: the ethical duty or right of the engineer becomes a matter of personal conscience, but the Board was unwilling to make a blanket statement that there is an ethical duty in these kinds of situations
violation consequences: No mandatory professional sanction for declining to escalate; personal consequences such as employment loss may follow if the engineer chooses to escalate
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:54:40.172403+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience
comment: Duty of an engineer who identifies employer or organizational conduct that is improper in relation to public concerns, such as unjustified expenditure of public funds or unsatisfactory plans, to recognize that further disclosure or whistleblowing is a matter of personal conscience and ethical right rather than a mandatory professional duty, absent a direct danger to public health or safety, and to understand that exercising that right may carry personal professional consequences.
subclass of: EthicalObligation
generated at time: 2026-06-04T16:54:40.172403+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Whistleblower Conscience Principle
type: Class
abstract nature: Open-textured principle requiring case-by-case determination of whether the conduct at issue crosses the threshold from a matter of personal conscience into a mandatory disclosure obligation, based on the presence or absence of public health and safety risk.
confidence: 0.87
derived obligations: Accept professional consequences of voluntary disclosure decisions
derived obligations: Distinguish safety threats from financial impropriety before determining disclosure duty
derived obligations: Exhaust internal channels before public disclosure when safety is not at stake
extensional examples: BER Case No. 82-5 where an engineer reported excessive subcontractor costs and delays but the Board declined to impose a duty of continued disclosure
operationalization: Requires distinguishing between conduct that threatens public safety, which triggers mandatory disclosure, and conduct that is merely improper or wasteful, which triggers only a right of disclosure. Engineers must accept employment consequences if they choose to exercise that right.
potential conflicts: Confidentiality Principle
potential conflicts: Faithful Agent Duty Principle
potential conflicts: Public Welfare Paramountcy Principle
principle category: professional_virtue
text references: if an engineer feels strongly that an employer's course of conduct is improper when related to public concerns, and if the engineer feels compelled to blow the whistle to expose facts as he sees them, he may well have to pay the price of loss of employment
text references: the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience
text references: the ethical duty or right of the engineer becomes a matter of personal conscience, but the Board was unwilling to make a blanket statement that there is an ethical duty in these kinds of situations
value basis: Respect for professional autonomy and personal conscience, balanced against the recognition that not every organizational impropriety rises to the level requiring mandatory professional action.
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:53:07.457315+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience
comment: Professional principle recognizing that when an engineer identifies employer or organizational conduct that is improper with respect to public concerns but does not rise to the level of a direct public safety threat, the engineer has an ethical right but not an ethical duty to pursue disclosure beyond internal channels or to escalate to public reporting. The decision to continue the campaign or blow the whistle becomes a matter of personal conscience, and the engineer must accept the professional consequences of that choice.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T16:53:07.457315+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Written Report Completeness Obligation
type: Class
confidence: 0.85
derived from principle: Objective Completeness in Public Reports Principle
enforcement level: mandatory
monitoring criteria: Comparison of the written report against all findings documented in the engineer's work product to verify that no material finding was omitted
nspe reference: II.3.a
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Public authority
text references: The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority. The BER noted that Engineer A was obligated under Code section II.3.a to be objective and truthful in professional reports, statements, or testimony and include all relevant and pertinent information in such reports.
text references: The key point of BER Case 07-6 is that information about the threat to the bird species is a 'fact' of the case.
violation consequences: Violation of Code section II.3.a; submission of a materially incomplete report to a public authority; potential harm to public welfare
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:06:46.728956+00:00
first discovered in case: 8
match confidence: 0.9
match reasoning: The existing Report Completeness Obligation directly captures the duty to include all relevant and pertinent information and to refrain from selectively omitting data. This class is a close match, with the additional specificity that the report is submitted to a public authority. The match is high confidence.
matched ontology class: Report Completeness Obligation
matched ontology label: Report Completeness Obligation
matches existing: true
source text: The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority. The BER noted that Engineer A was obligated under Code section II.3.a to be objective and truthful in professional reports, statements, or testimony and include all relevant and pertinent information in such reports.
comment: Duty of an engineer preparing a written report to be submitted to a public authority to include all relevant and pertinent information, including findings that may be unfavorable to the client's interests or that concern risks to protected species, environmental quality, or public welfare, and to refrain from omitting such information even when it has been communicated verbally to the client.
subclass of: DisclosureObligation
scope note: [ReportCompletenessObligation] Duty of an engineer preparing a professional report, analysis, or advisory memo to include all relevant and pertinent information, and to refrain from selectively omitting data, findings, or options that would materially affect the recipient's understanding or decision, regardless of whether the omitted information is unfavorable to the engineer's interests.
generated at time: 2026-06-04T10:06:46.728956+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

AI Authorship Representation Capability
type: Class
capability category: communication
confidence: 0.86
domain specificity: Professional engineering and technical writing practice involving AI-assisted content generation
enables actions: Accurately attribute authorship in professional submissions
enables actions: Communicate the nature and extent of AI contribution to clients
enables actions: Identify AI-generated content within a work product
enables actions: Refrain from presenting AI-generated text as original professional writing
required for obligations: AI Authorship Honesty Obligation
required for obligations: AI Tool Disclosure Obligation
skill level: intermediate
text references: Client W noted that the introduction discussing the contaminant's manufacture, use, and characteristics to be exceptionally polished. The Client commented that the report read as if written by two different authors
text references: Engineer A also made minor adjustments to some of the wording to personalize the content.
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:21.353968+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
comment: Capability to accurately represent the intellectual origin and authorship of professional work products, including the ability to distinguish between AI-generated content and original professional work and to avoid misrepresenting AI output as one's own independent analysis.
subclass of: Capability
generated at time: 2026-06-03T14:06:21.353968+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Output Verification Capability
type: Class
capability category: domain_specific
confidence: 0.9
domain specificity: Professional engineering practice using AI-assisted drafting or synthesis tools across technical domains
enables actions: Assess completeness and reliability of AI-synthesized technical content
enables actions: Determine whether AI output meets professional and regulatory standards
enables actions: Identify regulatory omissions in AI-generated design documents
enables actions: Review AI-generated reports for factual accuracy
required for obligations: AI Output Verification Obligation
required for obligations: Regulatory Safety Compliance Obligation
required for obligations: Responsible Charge Seal Obligation
skill level: advanced
text references: Client W, however, noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
text references: Not being familiar with the full functionality of the AI software, including the accuracy and originality of AI-generated text, Engineer A conducted a thorough review of the report
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:21.353968+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
comment: Technical capability to critically evaluate AI-generated work products for accuracy, completeness, regulatory compliance, and professional adequacy, sufficient to take responsible charge over the output and identify deficiencies before submission.
subclass of: Capability
generated at time: 2026-06-03T14:06:21.353968+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Tool Disclosure Obligation
type: Class
confidence: 0.92
derived from principle: AI Tool Disclosure Principle
enforcement level: mandatory
monitoring criteria: Documented disclosure of AI tool use in submitted work products or accompanying transmittal communications
nspe reference: III.2, II.3.a
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Professional licensing board
stakeholders affected: Regulatory bodies
text references: Again, Engineer A did not cite the AI-assisted drafting tools they used to generate the engineering design documents.
text references: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
violation consequences: Misrepresentation of authorship and methodology; potential disciplinary action; erosion of client trust; professional license sanctions
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:05:12.288818+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A did not cite their use of AI-software or its large language models, and submitted the draft report to Client W for review
comment: Duty of an engineer who uses AI-assisted tools or large language models in the preparation of professional work products to disclose that use to clients, employers, and other stakeholders who rely on those work products, so that they can assess the nature and provenance of the work.
subclass of: DisclosureObligation
generated at time: 2026-06-03T14:05:12.288818+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

AI Tool Use Guidance Resource
type: Class
authority source: Professional engineering societies, ethics boards, and regulatory bodies issuing guidance on emerging technology in practice
confidence: 0.78
extensional function: Bridges abstract professional responsibility principles to the novel context of AI-assisted engineering work, providing concrete guidance on when and how AI tools may be used and what obligations attach to their use.
resource category: expert_interpretation
text references: Engineer A did not cite the AI-assisted drafting tools they used to generate the engineering design documents.
text references: Engineer A did not cite their use of AI-software or its large language models
text references: Engineer A opted to use open-sourced artificial intelligence (AI) software to create an initial draft of the necessary report and to use AI-assisted drafting tools to generate preliminary design documents.
usage context: AI-assisted design document generation
usage context: AI-assisted report drafting
usage context: Disclosure of AI tool use to clients
usage context: Verification of AI-generated content
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T13:59:19.637051+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A opted to use open-sourced artificial intelligence (AI) software to create an initial draft of the necessary report and to use AI-assisted drafting tools to generate preliminary design documents.
comment: Professional guidance, policy statements, or documented norms addressing the appropriate use of artificial intelligence tools in engineering practice, including disclosure obligations, accuracy verification requirements, and professional responsibility when AI-generated content is incorporated into deliverables.
subclass of: ExpertInterpretation
generated at time: 2026-06-03T13:59:19.637051+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

CADD Competency Guidance Resource
type: Class
authority source: NSPE Board of Ethical Review and professional engineering community consensus
confidence: 0.78
extensional function: Grounds the professional duty to maintain competence when adopting new computational design technologies, bridging abstract competence obligations to specific CADD and AI tool contexts.
resource category: expert_interpretation
text references: It is critical for engineers to fully understand the role that new technologies such as CADD will play in the performance of professional services.
text references: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
usage context: Professional competence assessment
usage context: Seal and signature obligations
usage context: Technology adoption in engineering practice
discovered in case: 120
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T18:05:30.148012+00:00
first discovered in case: 120
match confidence: 0.78
match reasoning: CADD competency guidance is a variant of the existing AI Tool Use Guidance Resource class, which covers professional guidance on appropriate use of computational and AI tools including disclosure obligations, accuracy verification, and professional responsibility. CADD predates modern AI but the class definition is broad enough to encompass it as a subtype.
matched ontology class: AI Tool Use Guidance Resource
matched ontology label: AI Tool Use Guidance Resource
matches existing: true
source text: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
comment: Professional guidance addressing the requisite background, education, training, and limitations engineers must understand when using Computer Aided Drafting and Design systems in professional practice, including the distinction between using such tools as aids versus substitutes for professional judgment.
subclass of: ExpertInterpretation
scope note: [AIToolUseGuidanceResource] Professional guidance, policy statements, or documented norms addressing the appropriate use of artificial intelligence tools in engineering practice, including disclosure obligations, accuracy verification requirements, and professional responsibility when AI-generated content is incorporated into deliverables.
generated at time: 2026-06-04T18:05:30.148012+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

CADD Proficiency Capability
type: Class
capability category: domain_specific
confidence: 0.82
domain specificity: Computer-assisted design and drafting in professional engineering practice
enables actions: Avoid incorporating system-generated solutions the engineer has not prepared or fully understands
enables actions: Maintain professional authorship over CADD-produced documents
enables actions: Recognize when CADD output exceeds the engineer's understanding
enables actions: Use CADD systems as a production tool under professional direction
required for obligations: CADD Proficiency Competence Obligation
required for obligations: Responsible Charge Seal Obligation
required for obligations: Technology Tool Non-Substitution Obligation
skill level: intermediate
text references: CADD utilized beyond its ability to serve as a valuable tool has a propensity to be utilized as a crutch or substitute for judgement.
text references: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
text references: The key point is that the engineer must utilize such systems to assist the engineer in the performance of professional services and not employ such systems as a replacement for professional competence and expertise.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:12:59.240485+00:00
first discovered in case: 120
match confidence: 0.72
match reasoning: The concept partially overlaps with AI Output Verification Capability in that both concern the engineer's ability to critically evaluate technology-generated outputs and avoid uncritical reliance on them. However, CADD Proficiency Capability is broader, encompassing the foundational technical training and background needed to use the system competently as a tool, not merely the verification of outputs. The existing class focuses on post-generation evaluation; this class includes the upstream competence to direct and understand the system. A medium-confidence variant match is appropriate, but the concept is sufficiently distinct in scope to warrant a separate class.
matched ontology class: AI Output Verification Capability
matched ontology label: AI Output Verification Capability
matches existing: true
source text: The change to CADD provides the BER with concerns that require assurance that the professional engineer has the requisite background, education and training to be proficient with the dynamics of CADD including the limitations of current technology.
comment: Technical capability of a licensed professional engineer to possess sufficient background, education, and training to be proficient with CADD systems, including understanding the limitations of the technology, recognizing when the system is being used as a substitute for professional judgment rather than as a production tool, and ensuring that outputs reflect genuine engineering competence rather than uncritical reliance on system-generated solutions.
subclass of: Capability
scope note: [AIOutputVerificationCapability] Technical capability to critically evaluate AI-generated work products for accuracy, completeness, regulatory compliance, and professional adequacy, sufficient to take responsible charge over the output and identify deficiencies before submission.
generated at time: 2026-06-04T18:12:59.240485+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Client Advocacy Boundary Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Opposing parties
affected stakeholders: Public
affected stakeholders: Retained engineer
affected stakeholders: Tribunal
confidence: 0.87
constraint type: ethical
flexibility: hard
mitigation strategies: Distinguish between presenting favorable evidence and omitting contrary evidence
mitigation strategies: Refuse client instructions to omit material findings
mitigation strategies: Withdraw from engagement if client demands suppression of evidence
text references: Engineer B was obligated to serve the municipality's legitimate interests while refusing to omit material technical evidence from the report.
text references: We just did not believe the driving records and there was also the issue of whether the pile was vented to allow air to escape.
violation impact: Professional discipline, harm to opposing parties, unjust outcomes, public safety risk
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:37.486481+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing constraint class in the ontology captures the hard ethical boundary between permissible client advocacy and impermissible suppression of evidence. The obligation-side Faithful Agent Boundary Obligation is a duty; this is the inviolable constraint on conduct.
matches existing: false
source text: Engineer B was obligated to serve the municipality's legitimate interests while refusing to omit material technical evidence from the report.
comment: Prohibition on an engineer acting as a retained expert or agent crossing from legitimate advocacy of a client's position into suppression or omission of material technical evidence, marking the boundary between permissible client service and professional misconduct.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T14:32:37.486481+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Client Budget Override Safety Continuation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.88
constraint type: ethical
flexibility: hard
mitigation strategies: Document the refusal and the engineer's recommendation in writing before withdrawal
mitigation strategies: Report the risk to appropriate regulatory authorities after withdrawal
mitigation strategies: Withdraw from the project upon client refusal to implement identified safety measures
text references: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations.
text references: Despite Engineer L's concerns, Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
violation impact: Engineer continues work on a project that poses a confirmed risk to public health or safety without adequate safeguards, directly violating the paramount duty to hold public welfare above client economic interests.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T02:22:06.761320+00:00
first discovered in case: 8
match confidence: 0.92
match reasoning: The existing Client Economic Pressure Safety Continuation Constraint directly addresses the prohibition on an engineer continuing work after a client declines to implement safety measures on economic grounds. The case facts map precisely onto this existing class: Client X refuses additional protective measures citing budget limitations, and Engineer L faces the constraint of whether to continue. This is a high-confidence match to the existing class.
matched ontology class: Client Economic Pressure Safety Continuation Constraint
matched ontology label: Client Economic Pressure Safety Continuation Constraint
matches existing: true
source text: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations.
comment: Ethical constraint prohibiting an engineer from continuing work on a project after a client declines to implement safety measures the engineer has identified as necessary to protect public health or safety, when the client's refusal is grounded in budget or economic considerations. The engineer must cease participation rather than subordinate the paramount public safety duty to the client's financial preferences.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [ClientEconomicPressureSafetyContinuationConstraint] Ethical constraint prohibiting an engineer from continuing work on a project after a client declines to implement safety measures the engineer has identified as necessary, when proceeding would require the engineer to subordinate public safety obligations to the client's economic concerns. The engineer must cease participation rather than abandon the duty to hold public safety paramount in favor of client financial preferences.
generated at time: 2026-06-05T02:22:06.761320+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Cost Objection to Safety Measure State
type: Class
action constraints: Continuing work after client refuses a necessary safety measure constitutes a violation of the public safety paramount duty
action constraints: Professional may not abandon the ethical duty to the public in response to client cost concerns
activation conditions: Client declines the recommendation citing cost
activation conditions: Professional continues work without the safety measure
activation conditions: Professional recommends a safety measure as necessary for project success
confidence: 0.84
obligation activation: Obligation not to continue work that poses unmitigated public safety risk
obligation activation: Obligation to advise client that the project will not be successful without the measure
obligation activation: Obligation to prioritize public safety over client economic preferences
persistence type: inertial
principle transformation: Transforms the abstract duty to hold public safety paramount into a concrete prohibition on continuing professional services when a client refuses a safety measure that the professional has identified as necessary, regardless of the client's economic rationale.
state category: conflict
termination conditions: Client agrees to implement the safety measure
termination conditions: Professional withdraws from the project
termination conditions: Project is redesigned to eliminate the safety concern
text references: Client X's insistence on moving forward with the project without adequate safeguards creates an ethical dilemma for Engineer L
text references: Engineer A abandoned the ethical duty and proceeded to work on the project
text references: Engineer A recommended the client hire a full-time, on-site project representative for the project because of the potentially dangerous nature of implementing the design during the construction phase. The client indicated that hiring the representative would be too costly, and Engineer A continues to work on the project.
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:35.891200+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer A recommended the client hire a full-time, on-site project representative for the project because of the potentially dangerous nature of implementing the design during the construction phase. The client indicated that hiring the representative would be too costly, and Engineer A continues to work on the project.
comment: State in which a client declines to implement a safety measure recommended by the professional engineer on the grounds that the measure is too costly, and the professional continues to work on the project without the safety measure in place, creating a condition in which the professional's primary obligation has shifted from public safety to the client's economic concerns.
subclass of: ConflictState
generated at time: 2026-06-04T09:59:35.891200+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Economic Pressure Resistance Capability
type: Class
capability category: reasoning
confidence: 0.87
domain specificity: Professional engineering practice where client cost concerns conflict with public safety obligations
enables actions: Advise the client that the project cannot proceed successfully without the recommended measures
enables actions: Identify when client cost objections cross the threshold from legitimate scope negotiation to ethically impermissible pressure
enables actions: Refuse to continue professional work when safety measures the engineer has identified as necessary are rejected by the client
required for obligations: Client Economic Pressure Refusal Obligation
required for obligations: Client Override Public Safety Reporting Obligation
required for obligations: Project Success Notification Obligation
skill level: advanced
text references: Client X's insistence on moving forward with the project without adequate safeguards creates an ethical dilemma for Engineer L.
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
text references: The problematic behavior in BER Case 84-5 was that, when cost concerns were raised by the client, Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project.'
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:30.219581+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
comment: Capability to recognize when a client's refusal to implement professionally recommended safety measures, motivated by cost or economic concerns, creates an obligation to cease work rather than continue, and to act on that obligation by declining to proceed despite client pressure.
subclass of: Capability
generated at time: 2026-06-04T10:08:30.219581+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Instruction Override Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Third-Party Professionals
confidence: 0.87
constraint type: ethical
flexibility: hard
mitigation strategies: Advise client of the ethical limitation and propose compliant alternatives
mitigation strategies: Decline instructions that conflict with ethics code requirements
mitigation strategies: Document refusal and reasoning
text references: Engineer B objects to conducting the peer review without advising Engineer A.
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
violation impact: Violation of professional ethics, potential disciplinary action, and complicity in unethical conduct if client instructions are followed over ethical obligations.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:27.688172+00:00
first discovered in case: 15
match confidence: 0.8
match reasoning: This constraint is a specific application of the general Ethical Constraint class. It captures the boundary that client loyalty does not override professional ethics obligations. It is closely related to the existing Non-Deception (Constraint) and Conflict of Interest Avoidance (Constraint) ontology entries but is more precisely characterized as an Ethical Constraint governing the limits of client authority over professional conduct.
matched ontology class: EthicalConstraint
matched ontology label: Ethical Constraint
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
comment: Ethical constraint establishing that an engineer's duty of loyalty to a client does not extend to following client instructions that require violating professional ethics obligations, and that such instructions must be declined.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [EthicalConstraint] Professional ethical boundaries beyond legal requirements (Benzmüller et al. 2020)
generated at time: 2026-06-02T19:57:27.688172+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Competence Limit Recognition Capability
type: Class
capability category: awareness
confidence: 0.87
domain specificity: Professional engineering review and approval functions across engineering disciplines
enables actions: Assess whether assigned review task falls within personal competence
enables actions: Inform supervisor of competence limitations
enables actions: Recognize when a review is beyond one's technical expertise
enables actions: Request reassignment of task to a qualified engineer
required for obligations: Approving Engineer Verification Obligation
required for obligations: Competence Limit Escalation Obligation
skill level: intermediate
text references: Engineers have an obligation to perform services within their area of competence. If Engineer B was not able to perform the necessary reviews of Engineer A's work, Engineer B should have provided this information to a supervisor who would have assigned an appropriate engineer to perform the review.
text references: Not possessing adequate competency to perform a task is not in and of itself a violation of the NSPE Code, but the failure to recognize the lack of competency and take appropriate action to address the situation is a violation of the NSPE Code.
discovered in case: 85
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T16:55:58.579791+00:00
first discovered in case: 85
match confidence: 0.0
matches existing: false
source text: Engineers have an obligation to perform services within their area of competence. If Engineer B was not able to perform the necessary reviews of Engineer A's work, Engineer B should have provided this information to a supervisor who would have assigned an appropriate engineer to perform the review.
comment: Capability to recognize the boundaries of one's own technical competence when assigned a professional task, to assess whether one possesses sufficient expertise to perform the task adequately, and to take appropriate action such as informing a supervisor or declining the assignment rather than proceeding with an inadequate review.
subclass of: Capability
generated at time: 2026-06-04T16:55:58.579791+00:00
was attributed to: Case 85 Extraction
was attributed to: claude-sonnet-4-6

Complete Options Advisory Obligation
type: Class
confidence: 0.88
derived from principle: Complete Options Analysis Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that all approved or applicable options were identified and analyzed in the advisory work product
nspe reference: II.5.a
obligation type: disclosure
stakeholders affected: Funding agency
stakeholders affected: General public
stakeholders affected: Municipal client
text references: Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.
text references: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
violation consequences: Client makes uninformed decision based on incomplete analysis; engineer may face disciplinary action for dishonest or misleading professional conduct
discovered in case: 14
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T08:44:38.157284+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build.
comment: Duty of an engineer advising a client on selection among multiple available options to present all materially relevant options within the approved or applicable set, rather than selectively presenting only a subset, so that the client can make a fully informed decision.
subclass of: DisclosureObligation
generated at time: 2026-06-04T08:44:38.157284+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Complete Reporting Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Opposing Party
affected stakeholders: Public
affected stakeholders: Tribunal or Dispute Resolution Body
confidence: 0.78
constraint type: ethical
flexibility: hard
mitigation strategies: Address contradictory evidence explicitly rather than omitting it
mitigation strategies: Disclose equipment failures and procedural anomalies
mitigation strategies: Include all material test results and field data in the report
text references: as an engineering document the report is incomplete and does a disservice to Engineer B's client municipality by potentially misdirecting a conclusion
text references: the Code of Ethics which requires that engineers 'shall include all relevant and pertinent information in such report, statements or testimony'
violation impact: Misdirection of technical conclusions, disservice to client, impairment of opposing party's ability to obtain expert review, professional discipline
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:36:05.125890+00:00
first discovered in case: 71
match confidence: 0.78
match reasoning: The Complete Reporting Constraint overlaps substantially with the Contradictory Evidence Omission Constraint already in the ontology, which prohibits preparing a technical report that omits known material evidence contradicting the report's conclusions. The present case text emphasizes the same code requirement to include all relevant and pertinent information. However, the existing class is framed specifically around contradictory evidence, while the case text also addresses omission of non-contradictory material facts such as equipment failure and driven-to-refusal status. The match is strong but not identical, so medium-high confidence is appropriate.
matched ontology label: Contradictory Evidence Omission Constraint
matches existing: true
source text: the Code of Ethics which requires that engineers 'shall include all relevant and pertinent information in such report, statements or testimony'
comment: Requirement that an engineer preparing a technical report include all relevant and pertinent information, prohibiting selective omission of material technical facts regardless of the adversarial or client-service context in which the report is prepared.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T14:36:05.125890+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Confidentiality Safety Override Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Design Engineer
affected stakeholders: Peer Reviewer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.87
constraint type: confidentiality
flexibility: soft
mitigation strategies: Advise the reviewed engineer of the intent to notify authorities if resolution is not reached
mitigation strategies: Discuss safety concerns directly with the reviewed engineer before escalating
mitigation strategies: Notify appropriate authorities when safety violations remain unresolved
text references: Engineer A contractually agreed not to disclose confidential information acquired in the review
text references: Engineer A had an obligation to immediately discuss these issues with Engineer B in order to seek clarification and resolution
text references: if Engineers A and B were unable to successfully resolve Engineer A's concerns, Engineer A had an obligation to first advise Engineer B that Engineer A had an obligation to inform the appropriate authorities, and then to so inform the appropriate authorities
violation impact: Suppression of safety-critical information, risk to public health and welfare, and potential professional liability for the reviewer who fails to escalate unresolved safety violations.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:50.100159+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineer A had an obligation to immediately discuss these issues with Engineer B in order to seek clarification and resolution
comment: Constraint arising when a peer reviewer operating under a contractual confidentiality agreement discovers safety code violations. The confidentiality obligation does not eliminate the reviewer's duty to first seek resolution with the reviewed engineer and then, if unresolved, to notify appropriate authorities. The safety disclosure obligation overrides the confidentiality restriction when public health, safety, and welfare are at risk.
subclass of: ConfidentialityConstraint
subclass of: DefeasibleConstraint
generated at time: 2026-06-02T20:00:50.100159+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Confirmed Risk Disclosure State
type: Class
action constraints: Professional may not ethically acquiesce to client pressure to proceed without adequate safeguards
action constraints: Professional may not suppress or omit the factual finding from written reports
activation conditions: Client has been informed but has not yet responded with adequate safeguards
activation conditions: Professional completes sufficient analysis to characterize a risk as a factual finding
activation conditions: Professional notifies the client of the identified risk
confidence: 0.85
obligation activation: Obligation to advise client that the project will not be successful without safeguards
obligation activation: Obligation to refuse to continue work if client insists on proceeding without safeguards
obligation activation: Potential obligation to report to relevant authorities if client refuses to act
persistence type: inertial
principle transformation: Transforms the general duty to hold public safety paramount into a concrete obligation to withhold professional services when a client refuses to implement identified safeguards, overriding the faithful-agent duty to the client.
state category: risk
termination conditions: Client implements adequate protective measures
termination conditions: Project is terminated
termination conditions: Regulatory authority takes over management of the risk
text references: Client X's insistence on moving forward with the project without adequate safeguards creates an ethical dilemma for Engineer L
text references: Engineer L notified Client X of this risk
text references: Engineer L's identification of runoff risk is now fact
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:35.891200+00:00
first discovered in case: 8
match confidence: 0.88
match reasoning: The existing Confirmed Risk Without Adequate Safeguards State directly captures this condition: a professional has confirmed a concrete risk and adequate safeguards are absent. Engineer L has confirmed the stormwater runoff risk as a factual finding, notified the client, and the client refuses to implement protective measures. This matches the existing class at high confidence.
matched ontology class: ConfirmedRiskWithoutAdequateSafeguardsState
matched ontology label: Confirmed Risk Without Adequate Safeguards State
matches existing: true
source text: Engineer L's identification of runoff risk is now fact
comment: State in which a professional has identified and documented a concrete risk as a factual finding and has notified the client of that risk, creating an active obligation to ensure the client responds with adequate safeguards and triggering heightened duties if the client refuses to act.
subclass of: RiskState
scope note: [ConfirmedRiskWithoutAdequateSafeguardsState] State in which a professional has confirmed the existence of a concrete public-safety or environmental risk and adequate safeguards are known to be absent. Typical activator for post-termination reporting obligations and for defeating faithful-agent confidentiality (NSPE BER Case 72 pattern).
generated at time: 2026-06-04T09:59:35.891200+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Coordinated Escalation Obligation
type: Class
confidence: 0.75
derived from principle: Graduated Response Proportionality Principle
enforcement level: prima_facie
monitoring criteria: Evidence that both engineers agreed on and jointly executed or separately but consistently executed the regulatory escalation
nspe reference: I.1, II.1.a, II.1.c
obligation type: reporting
stakeholders affected: Client governing body
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.
text references: Despite those recommendations, the MWC voted to proceed simultaneously with the accelerated evaluation and design of needed water treatment improvements and the change in water source.
violation consequences: Inconsistent or incomplete regulatory reporting; weakened public protection; professional accountability gap
discovered in case: 76
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-05T11:23:42.907966+00:00
first discovered in case: 76
match confidence: 0.0
matches existing: false
source text: Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.
comment: Duty of two or more engineers who have jointly identified a public health or safety risk and jointly presented recommendations that were overridden by a client to coordinate their escalation response, including agreeing on the form, content, and target of any regulatory report or presentation, so that the escalation is consistent, complete, and effective.
subclass of: ReportingObligation
generated at time: 2026-06-05T11:23:42.907966+00:00
was attributed to: Case 76 Extraction
was attributed to: claude-sonnet-4-6

Design Engineer
type: Class
confidence: 0.88
role category: provider_client
text references: plans and design of Engineer A for the second tower
text references: several significant design errors are discovered in the plans and design of Engineer A
discovered in case: 15
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-02T19:52:08.471399+00:00
first discovered in case: 15
match confidence: 0.75
match reasoning: Design Engineer is a specialization of Engineer Role focused on original design authorship. The ontology has Engineer Role as the occupational archetype head, making this a medium-confidence specialization match rather than a new concept.
matched ontology class: EngineerRole
matched ontology label: Engineer Role
matches existing: true
source text: several significant design errors are discovered in the plans and design of Engineer A
comment: A professional engineering role responsible for creating original plans, specifications, and designs for a project, bearing primary accountability for the technical content of those documents.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [EngineerRole] A professional role involving engineering practice and responsibilities. Occupational archetype head for all engineer specializations and extracted engineer-role leaves.
generated at time: 2026-06-02T19:52:08.471399+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Engineering Design Error Recognition Capability
type: Class
capability category: domain_specific
confidence: 0.83
domain specificity: Structural and civil engineering design review
enables actions: Assess severity and safety implications of errors
enables actions: Document findings for accountability purposes
enables actions: Identify design errors in engineering plans
required for obligations: Professional Accountability Cooperation Obligation
required for obligations: Safety Review Consent Obligation
skill level: advanced
text references: Owner decides to obtain a peer review of the plans and design of Engineer A for the second tower
text references: several significant design errors are discovered in the plans and design of Engineer A
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:30.046199+00:00
first discovered in case: 15
match confidence: 0.78
match reasoning: The ability to identify significant design errors through independent review is a domain-specific professional competency fitting Domain Expertise as defined by Hallamaa and Kalliokoski 2022 and Doernberg and Truog 2023. The focus on error recognition in peer review is a variant of the broader class, matched at medium confidence.
matched ontology class: DomainExpertise
matched ontology label: Domain Expertise
matches existing: true
source text: several significant design errors are discovered in the plans and design of Engineer A
comment: Technical capability to identify significant errors, omissions, or deficiencies in engineering plans and designs through independent review, including the ability to assess the severity and safety implications of discovered errors.
subclass of: Capability
scope note: [DomainExpertise] Professional domain-specific knowledge and competencies (Hallamaa & Kalliokoski 2022, Doernberg & Truog 2023)
generated at time: 2026-06-02T19:57:30.046199+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Environmental Engineer
type: Class
confidence: 0.88
role category: provider_client
text references: Engineer A was tasked to develop engineering design documents (plans and specifications) for modifications to groundwater infrastructure
text references: Engineer A, an environmental engineer with several years of experience and holding a professional engineering license, was retained by Client W
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T13:59:26.869728+00:00
first discovered in case: 7
match confidence: 0.75
match reasoning: Environmental Engineer is a specialization of Engineer Role in the ontology. The ontology has Engineer Role as the occupational archetype head for all engineer specializations, so this is a medium-confidence match to the parent. A distinct leaf class is warranted because environmental engineering carries domain-specific obligations around contaminant reporting and groundwater infrastructure not captured by the generic Engineer Role.
matched ontology class: EngineerRole
matched ontology label: Engineer Role
matches existing: true
source text: Engineer A, an environmental engineer with several years of experience and holding a professional engineering license, was retained by Client W
comment: A professional engineering role specializing in environmental systems, contaminant analysis, groundwater monitoring, and related infrastructure design, bearing licensure-based accountability for technical reports and engineering documents delivered to clients.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [EngineerRole] A professional role involving engineering practice and responsibilities. Occupational archetype head for all engineer specializations and extracted engineer-role leaves.
generated at time: 2026-06-03T13:59:26.869728+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Environmental Risk Quantification Capability
type: Class
capability category: domain_specific
confidence: 0.88
domain specificity: Environmental and stormwater engineering, hydrological risk assessment
enables actions: Conduct hydrological and environmental impact studies
enables actions: Document the status of incomplete risk quantification
enables actions: Estimate qualitative and quantitative risk levels from heavy rainfall events
enables actions: Quantify risk of stormwater runoff reaching a drinking water source
required for obligations: Environmental Risk Quantification Obligation
skill level: advanced
text references: But before Engineer L can quantify the increased risk, Client X encounters unexpected financial setbacks and requests that Engineer L suspend work.
text references: Engineer L conducts additional studies and qualitatively estimates the risk that heavy rainfall could lead to stormwater runoff from the development reaching the nearby watershed and community drinking water source.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:03:17.498340+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L conducts additional studies and qualitatively estimates the risk that heavy rainfall could lead to stormwater runoff from the development reaching the nearby watershed and community drinking water source.
comment: Technical capability to conduct sufficient analysis to quantify environmental risks identified during professional work, including the ability to assess the magnitude and likelihood of stormwater or discharge impacts on public water sources and to document the status of quantification work when full analysis cannot be completed.
subclass of: Capability
generated at time: 2026-06-04T10:03:17.498340+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Faithful Agent Duty Conflict State
type: Class
action constraints: Professional may not abandon public safety duty in response to client cost concerns
action constraints: Professional may not continue work that poses unmitigated public risk simply to preserve the client relationship
activation conditions: Client instructs professional to take an action or refrain from an action
activation conditions: Following the client's instruction would compromise public safety or welfare
activation conditions: Professional has identified a factual basis for the safety concern
confidence: 0.87
obligation activation: Obligation to advise client that the project will not be successful
obligation activation: Obligation to prioritize public safety over client economic interests
obligation activation: Obligation to refuse to continue work that endangers the public
persistence type: inertial
principle transformation: Transforms the abstract tension between Fundamental Canon I.1 (public safety paramount) and Canon I.4 (faithful agent duty) into a concrete obligation to withhold services when the two duties cannot be reconciled in favor of public safety.
state category: conflict
termination conditions: Client agrees to implement adequate safeguards
termination conditions: Professional withdraws from the engagement
termination conditions: Regulatory authority resolves the conflict externally
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L
text references: the present case illustrates a conflict between Fundamental Canon I.1, the engineer's obligation to hold paramount the safety, health and welfare of the public; and Canon I.4, the engineer's obligation to act for each employer or client as a faithful agent or trustee
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:35.891200+00:00
first discovered in case: 8
match confidence: 0.85
match reasoning: The existing Competing Duties State captures the general condition of conflicting professional obligations requiring ethical prioritization. The faithful-agent versus public-safety conflict is a canonical instance of competing duties. Matching to the existing class at high confidence rather than creating a new class.
matched ontology class: CompetingDuties
matched ontology label: Competing Duties State
matches existing: true
source text: the present case illustrates a conflict between Fundamental Canon I.1, the engineer's obligation to hold paramount the safety, health and welfare of the public; and Canon I.4, the engineer's obligation to act for each employer or client as a faithful agent or trustee
comment: State in which a professional's obligation to act as a faithful agent or trustee for a client comes into direct conflict with the professional's paramount duty to protect public health, safety, and welfare, requiring the professional to prioritize public safety over client loyalty when the two duties cannot be simultaneously satisfied.
subclass of: ConflictState
scope note: [CompetingDuties] State requiring ethical prioritization between conflicting obligations
generated at time: 2026-06-04T09:59:35.891200+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Incomplete Written Disclosure State
type: Class
action constraints: Professional may not submit a written report to a public authority that omits material facts known to the professional
action constraints: Verbal disclosure to the client does not satisfy the obligation to disclose in writing to a public authority
activation conditions: Professional identifies a material fact relevant to a public authority's decision
activation conditions: Professional omits the finding from a written report submitted to a public authority
activation conditions: Professional verbally communicates the finding to the client
confidence: 0.83
obligation activation: Obligation to be objective and truthful in written professional communications
obligation activation: Obligation to correct the omission before the report is acted upon
obligation activation: Obligation to include all relevant and pertinent information in professional reports
persistence type: inertial
principle transformation: Transforms the general duty of truthfulness and objectivity into a specific obligation to include material findings in written reports submitted to public authorities, even when the client prefers the information be omitted.
state category: information
termination conditions: Public authority independently obtains the information
termination conditions: Supplemental written disclosure is submitted to the public authority
termination conditions: Written report is amended to include the omitted finding
text references: Engineer A verbally mentioned the concern, but Engineer A did not include the information in a written report that will be submitted to a public authority
text references: The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:35.891200+00:00
first discovered in case: 8
match confidence: 0.84
match reasoning: The existing Incomplete Professional Report State captures the condition of a professional report that omits material information, resulting in a misleading or incomplete work product. The BER Case 07-6 pattern of verbal disclosure without written inclusion in a public report is a direct instance of that state. Matching to the existing class at high confidence.
matched ontology class: Incomplete Professional Report State
matched ontology label: Incomplete Professional Report State
matches existing: true
source text: Engineer A verbally mentioned the concern, but Engineer A did not include the information in a written report that will be submitted to a public authority
comment: State in which a professional has verbally communicated a material finding or concern to a client but has omitted that finding from a written report submitted to a public authority or other decision-making body, creating a transparency deficit and a breach of the duty to be objective and truthful in professional reports.
subclass of: InformationState
scope note: [IncompleteProfessionalReportState] State in which a professional has produced or submitted a report or analysis that omits material information, selectively presents data, or fails to investigate relevant factors, resulting in a misleading or incomplete professional work product that violates duties of objectivity, completeness, and truthfulness.
generated at time: 2026-06-04T09:59:35.891200+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Local Regulatory Safety Requirement Resource
type: Class
authority source: Local regulatory authorities and jurisdictional bodies
confidence: 0.8
extensional function: Provides the concrete regulatory baseline against which engineering design documents are evaluated for compliance, grounding the professional obligation to meet safety and regulatory standards.
resource category: legal_resource
text references: Client W noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: ensuring that all elements satisfied the necessary professional and regulatory standards.
usage context: Identification of omitted safety features in AI-generated plans
usage context: Review of engineering design documents for regulatory compliance
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T13:59:19.637051+00:00
first discovered in case: 7
match confidence: 0.8
match reasoning: Local regulatory requirements for safety features in engineering design are legal frameworks constraining professional practice, matching the Legal Resource class. No more specific existing class covers local safety regulations for engineering design.
matched ontology class: LegalResource
matched ontology label: Legal Resource
matches existing: true
source text: Client W noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
comment: Local or jurisdictional regulations specifying mandatory safety features and design requirements that engineering documents must satisfy, serving as a binding technical and legal floor for professional engineering deliverables.
subclass of: LegalResource
scope note: [LegalResource] Legal framework constraining professional practice
generated at time: 2026-06-03T13:59:19.637051+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Observer Irregularity Reporting Obligation
type: Class
confidence: 0.88
derived from principle: Investigative Completeness Principle
enforcement level: mandatory
monitoring criteria: Observer's report or testimony documents all identified irregularities with supporting evidence
nspe reference: II.2.a
obligation type: reporting
stakeholders affected: Court or mediating body
stakeholders affected: Opposing party
stakeholders affected: Retaining party
text references: In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value reported by Engineer B's tests.
text references: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.
violation consequences: Failure to report may result in reliance on invalid test data; professional discipline
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:31:15.630641+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing obligation class in the ontology corresponds to this duty. This is a new class.
matches existing: false
source text: The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration that apparently was required for the plug to form in the original piles.
comment: Duty of an engineer or geotechnical consultant retained to observe a test or investigation to document and report procedural irregularities, equipment failures, or methodological deviations that could affect the validity of the results, and to communicate these findings to the retaining party promptly.
subclass of: ReportingObligation
generated at time: 2026-06-04T14:31:15.630641+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Precedent Analogical Reasoning Capability
type: Class
capability category: reasoning
confidence: 0.85
domain specificity: Professional ethics analysis across engineering disciplines where prior board rulings or case law inform current obligations
enables actions: Analyze factual similarities and differences between a precedent and the current case
enables actions: Articulate why a prior ruling does or does not govern the current situation
enables actions: Determine whether a precedent's reasoning extends to a new fact pattern
enables actions: Identify prior ethics rulings relevant to a current professional dilemma
required for obligations: Expertise-Calibrated Disclosure Obligation
required for obligations: Post-Engagement Violation Reporting Obligation
skill level: advanced
text references: In BER Case No. 89-7, for example, the facts revealed that the client had confided in the engineer and may have relied upon the engineer to maintain the information in confidence. In addition, the engineer in BER Case No. 89-7 did not have any particular expertise in the technical areas
text references: Similarly, in BER Case No. 97-13, the engineer's evaluation was based upon general surmise and speculation
text references: Those two cases involved a different set of factors that created a reasonable basis for an engineer to take a more measured approach to the situation
text references: the Board can easily distinguish BER Case Nos. 89-7 and 97-13 from the present case
discovered in case: 86
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T17:36:09.645175+00:00
first discovered in case: 86
match confidence: 0.8
match reasoning: Precedent Application Capability covers identifying and applying prior professional ethics rulings and case precedents to novel situations, including reasoning by analogy from established decisions. The present capability adds emphasis on distinguishing precedents by factual differences rather than simply applying them, but the core concept is the same. The match is strong at the intermediate-to-high confidence level.
matched ontology class: Precedent Application Capability
matched ontology label: Precedent Application Capability
matches existing: true
source text: the Board can easily distinguish BER Case Nos. 89-7 and 97-13 from the present case
comment: Capability to identify prior professional ethics rulings or case precedents that are factually similar to a current situation, to analyze the factual distinctions between the precedent and the current case, and to reason from those distinctions to determine whether the precedent's conclusion applies, is modified, or is inapplicable in the current context.
subclass of: Capability
scope note: [PrecedentApplicationCapability] Capability to identify and apply prior professional ethics rulings and case precedents to novel situations, including the ability to reason by analogy from established decisions to determine appropriate conduct in related circumstances.
generated at time: 2026-06-04T17:36:09.645175+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Precedent Application Capability
type: Class
capability category: retrieval
confidence: 0.82
domain specificity: Professional engineering ethics adjudication and peer review practice
enables actions: Apply precedent reasoning to current facts
enables actions: Distinguish applicable from inapplicable precedents
enables actions: Identify relevant prior rulings
required for obligations: Confidential Review Safety Disclosure Obligation
required for obligations: Covert Review Refusal Obligation
required for obligations: Peer Review Knowledge Obligation
skill level: advanced
text references: In BER Case 96-8, Engineer A was a peer reviewer serving as part of an organized peer-review program.
text references: It is helpful to consider how the BER has addressed peer review issues in the past. For example, in BER Case 18-10...
discovered in case: 8
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:55.491400+00:00
first discovered in case: 15
match confidence: 0.82
match reasoning: The capability to identify and apply prior BER rulings and case-based reasoning to current peer review situations maps closely to Precedent Retrieval, defined as the capability to identify relevant precedents and apply case-based reasoning. The present use is domain-specific to engineering ethics adjudication but the core concept is the same.
matched ontology class: PrecedentRetrieval
matched ontology label: Precedent Retrieval
matches existing: true
source text: It is helpful to consider how the BER has addressed peer review issues in the past. For example, in BER Case 18-10...
comment: Capability to identify and apply prior professional ethics rulings and case precedents to novel situations, including the ability to reason by analogy from established decisions to determine appropriate conduct in related circumstances.
subclass of: Capability
scope note: [PrecedentRetrieval] Capability to identify relevant precedents and apply case-based reasoning (McLaren 2003, SIROCCO system)
generated at time: 2026-06-02T20:00:55.491400+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Preliminary Risk Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.82
constraint type: ethical
flexibility: soft
mitigation strategies: Document and communicate preliminary risk concerns in writing at the time of suspension or transition
mitigation strategies: Include a caveat in suspension communications noting unresolved risk items
mitigation strategies: Recommend that the client retain another engineer to continue risk assessment if work is suspended
text references: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
violation impact: Client proceeds without awareness of material risk, potentially causing harm to third parties or the public and exposing the engineer to professional liability.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:03:17.838512+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
comment: Ethical and professional constraint requiring an engineer who identifies a potential risk to public health or safety during a preliminary phase of work to disclose that concern to the client before suspending, pausing, or transitioning work, even when the risk has not yet been fully quantified, so that the client can make informed decisions about how to proceed.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
generated at time: 2026-06-04T10:03:17.838512+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Professional Accountability
type: Class
abstract nature: Requires interpretation of what forms of oversight are legitimate and what degree of professional resistance to review is permissible when an engineer believes the review process is unfair or unnecessary.
confidence: 0.9
derived obligations: Consent to peer review when prior errors give reasonable grounds for review
derived obligations: Cooperate with reviewing engineers
derived obligations: Refrain from obstructing safety-motivated oversight
extensional examples: NSPE BER cases in which engineers were found to have an obligation not to obstruct legitimate review of their work
extensional examples: Professional licensing board disciplinary cases involving failure to cooperate with peer review
operationalization: Requires Engineer A to consent to peer review of the second tower plans given that significant errors were already found in the first tower plans, rather than refusing on grounds of professional autonomy or reputational concern.
potential conflicts: Loyalty
potential conflicts: Professional Dignity
principle category: professional_virtue
text references: Engineer A objects and refused to consent to the peer review
text references: several significant design errors are discovered in the plans and design of Engineer A
value basis: Engineers who produce work that affects public safety must be answerable for that work, and the profession's credibility depends on engineers not placing self-protection above accountability.
discovered in case: 15
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:55:30.891672+00:00
first discovered in case: 15
match confidence: 0.92
match reasoning: Direct match to the existing Professional Accountability class in the ontology. The case instantiates this principle through Engineer A's refusal to consent to peer review after significant errors were found in the first tower, which is a paradigm case of failing to accept accountability for one's professional work product.
matched ontology class: Professional Accountability
matched ontology label: Professional Accountability
matches existing: true
source text: several significant design errors are discovered in the plans and design of Engineer A
comment: Professional virtue principle requiring engineers to accept responsibility for their work product and to submit to legitimate oversight and review processes, particularly when errors in that work product have been identified.
subclass of: ProfessionalVirtuePrinciple
scope note: [Case 120] Professional virtue principle requiring engineers to accept responsibility for their work product and to submit to legitimate oversight and review processes, particularly when the engineer's seal is affixed to documents, making the engineer personally accountable for the technical adequacy and accuracy of those documents.
generated at time: 2026-06-02T19:55:30.891672+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Project Success Advisory Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.86
constraint type: ethical
flexibility: hard
mitigation strategies: Communicate in writing the specific conditions under which the project will not be successful
mitigation strategies: Document the advisory communication and the client's response
mitigation strategies: Identify the measures required to achieve success across structural, economic, and safety dimensions
text references: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
text references: Consistent with Code sections I.4, II.3.a, II.3.b, III.1.b, and III.3.a, Engineer L notified Client X of this risk.
text references: section III.1.b. clearly requires the engineer to inform a client when the engineer believes that a project will not be successful. The term 'successful' includes not merely the structural and economic success of a project but also the success of the project from a safety standpoint.
violation impact: Client proceeds without material information needed to make an informed decision about the project, engineer fails to fulfill advisory duty, and public safety may be compromised if the safety dimension of project success is not communicated.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:14.702097+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
comment: Ethical constraint requiring an engineer to advise a client or employer when the engineer believes a project will not be successful, where success encompasses not only structural and economic outcomes but also safety outcomes. This obligation must be fulfilled before the engineer can be said to have met professional ethics requirements, and it applies whenever the engineer's professional judgment indicates that proceeding without specific measures will result in project failure in any of these dimensions.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T10:08:14.702097+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Project Success Assessment Capability
type: Class
capability category: domain_specific
confidence: 0.85
domain specificity: Professional engineering practice requiring integrated safety and feasibility judgment
enables actions: Assess whether a project can be completed safely given current scope and resources
enables actions: Communicate a professional judgment that a project will not succeed to the client
enables actions: Identify conditions whose absence would render a project unsuccessful from a safety standpoint
required for obligations: Client Economic Pressure Refusal Obligation
required for obligations: Project Success Notification Obligation
skill level: advanced
text references: BER Case 84-5 noted that, 'section III.1.b. clearly requires the engineer to inform a client when the engineer believes that a project will not be successful. The term "successful" includes not merely the structural and economic success of a project but also the success of the project from a safety standpoint.'
text references: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:30.219581+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
comment: Capability to evaluate whether a project can be completed successfully in terms of safety, structural adequacy, and public welfare, and to advise the client or employer when the engineer's professional judgment is that the project will not be successful without specific measures, including the ability to define success beyond mere economic or structural completion.
subclass of: Capability
generated at time: 2026-06-04T10:08:30.219581+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Project Success Notification Obligation
type: Class
confidence: 0.87
derived from principle: Project Success Notification Principle
enforcement level: mandatory
monitoring criteria: Documented communication to the client stating that the project will not be successful without the identified measures, prior to any decision to withdraw or continue
nspe reference: III.1.b
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: Employer
stakeholders affected: General public
text references: BER Case 84-5 noted that, 'section III.1.b. clearly requires the engineer to inform a client when the engineer believes that a project will not be successful. The term "successful" includes not merely the structural and economic success of a project but also the success of the project from a safety standpoint.'
text references: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
text references: Consistent with Code sections I.4, II.3.a, II.3.b, III.1.b, and III.3.a, Engineer L notified Client X of this risk.
violation consequences: Violation of Code section III.1.b; failure to give the client the opportunity to remedy the deficiency before the engineer must withdraw
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:06:46.728956+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Code section III.1.b requires that engineers advise their clients or employers when they believe a project will be unsuccessful.
comment: Duty of an engineer to advise a client or employer when, in the engineer's professional judgment, a project will not be successful, including when success is threatened by the absence of safety measures the client has declined to implement, so that the client has the opportunity to reconsider before the engineer is placed in a position of ethical conflict.
subclass of: DisclosureObligation
generated at time: 2026-06-04T10:06:46.728956+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Public Safety Paramount Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authority
confidence: 0.88
constraint type: ethical
flexibility: hard
mitigation strategies: Cease participation in projects where public safety cannot be adequately protected
mitigation strategies: Refuse client instructions that require subordinating public safety
mitigation strategies: Report confirmed risks to regulatory authorities when client override creates public danger
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
text references: It is basic to the entire concept of a profession that its members will devote their interests to the public welfare.
text references: Section 2(a) requires that his duty to the public be paramount.
text references: The present case illustrates a conflict between Fundamental Canon I.1, the engineer's obligation to hold paramount the safety, health and welfare of the public; and Canon I.4, the engineer's obligation to act for each employer or client as a faithful agent or trustee.
violation impact: Public exposed to preventable harm; engineer violates the foundational obligation of the profession; subject to professional discipline and potential legal liability.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:13.190895+00:00
first discovered in case: 8
match confidence: 0.8
match reasoning: The public safety paramount obligation is best captured as an Inviolable Constraint in the ontology, as it is an absolute constraint that cannot be overridden under any circumstances. However, the Safety Constraint class is also a close match. The Inviolable Constraint class is the better fit because the case text repeatedly frames the public safety duty as paramount and non-negotiable, not merely a safety boundary.
matched ontology class: InviolableConstraint
matched ontology label: Inviolable Constraint
matches existing: true
source text: The present case illustrates a conflict between Fundamental Canon I.1, the engineer's obligation to hold paramount the safety, health and welfare of the public; and Canon I.4, the engineer's obligation to act for each employer or client as a faithful agent or trustee.
comment: Inviolable ethical constraint establishing that an engineer's duty to hold paramount the safety, health, and welfare of the public takes precedence over obligations to clients, employers, and other parties. This constraint governs all professional decisions and cannot be overridden by client instructions, economic pressures, or contractual obligations.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [InviolableConstraint] Absolute constraints that cannot be overridden under any circumstances (Dennis et al. 2016)
generated at time: 2026-06-05T02:27:13.190895+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Escalation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Community Water Users
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.88
constraint type: safety
flexibility: hard
mitigation strategies: Document all communications with client regarding the risk and the client's refusal
mitigation strategies: Notify the appropriate regulatory or pollution control authority of the identified risk
mitigation strategies: Withdraw from the engagement if the client continues to override safety recommendations
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
violation impact: Public health or safety harmed by unaddressed risk; engineer in violation of paramount public safety duty and potentially subject to professional discipline.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:03:17.838512+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
comment: Safety and ethical constraint requiring an engineer who has identified a confirmed risk to public health or safety, and whose client has overridden the engineer's recommendation to address that risk, to report the risk to the appropriate regulatory or pollution control authority when the client's override creates a condition that endangers public welfare and cannot be resolved within the professional relationship.
subclass of: InviolableConstraint
subclass of: SafetyConstraint
generated at time: 2026-06-04T10:03:17.838512+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Report Completeness Obligation
type: Class
confidence: 0.88
derived from principle: Report Completeness Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that all materially relevant information was included in the report or advisory product
nspe reference: III.2.b
obligation type: ethical
stakeholders affected: Client
stakeholders affected: Public
stakeholders affected: Regulatory bodies
text references: Engineer A submitted plans that were lacking much of the design detail in both drawings and specifications
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information
text references: include all relevant and pertinent information
text references: the engineer in question rendered an opinion that, based upon test pile, the project's installed piles did not meet the design safety factor. However, the engineer failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal
violation consequences: Professional discipline; findings of unethical conduct by the Board of Ethical Review; reputational harm
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:47:48.914349+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: include all relevant and pertinent information
comment: Duty of an engineer preparing a professional report, analysis, or advisory memo to include all relevant and pertinent information, and to refrain from selectively omitting data, findings, or options that would materially affect the recipient's understanding or decision, regardless of whether the omitted information is unfavorable to the engineer's interests.
subclass of: EthicalObligation
generated at time: 2026-06-04T08:47:48.914349+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Report Completeness Principle
type: Class
abstract nature: Open-textured obligation requiring judgment about what counts as relevant and pertinent in any given professional context, with meaning accumulated through case precedents such as BER 95-5 and 99-8.
confidence: 0.88
derived obligations: Disclose all material data bearing on conclusions
derived obligations: Identify limitations of analysis
derived obligations: Notify recipients of known incompleteness at time of submission
extensional examples: BER Case 95-5 where engineer omitted pile refusal data and equipment failure from safety report
extensional examples: BER Case 99-8 where engineer submitted incomplete design drawings without disclosing their incompleteness
operationalization: Requires engineers to include all material data, disclose known limitations, and refrain from intentional or negligent omission of information that would change the recipient's understanding of the professional findings.
potential conflicts: Client Loyalty Limits
potential conflicts: Conflict of Interest Disclosure Principle
principle category: professional_virtue
text references: Engineer A did not inform anyone as to the incompleteness at the time of submission
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information
text references: the engineer failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal (intentional disregard of other information)
text references: the test equipment had failed (selective use of information)
value basis: Clients and the public rely on professional reports as complete representations of the engineer's findings; selective omission corrupts the epistemic foundation of professional advice.
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:46:54.906706+00:00
first discovered in case: 14
match confidence: 0.0
matches existing: false
source text: the engineer failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal (intentional disregard of other information)
comment: Professional integrity principle requiring engineers to include all relevant and pertinent information in reports, analyses, and professional communications, prohibiting selective omission of data that would materially alter the conclusions or recommendations presented.
subclass of: ProfessionalVirtuePrinciple
generated at time: 2026-06-04T08:46:54.906706+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Report Integrity Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Reviewing Authorities
confidence: 0.8
constraint type: ethical
flexibility: hard
mitigation strategies: Cite sources and document the basis for conclusions
mitigation strategies: Conduct thorough investigation before rendering professional opinions
mitigation strategies: Disclose limitations in available data or scope of analysis
mitigation strategies: Include all materially relevant data and contrary evidence in reports
text references: BER Case 95-5 addressed integrity and completeness in preparing reports. The engineer in question rendered an opinion that, based upon test pile, the project's installed piles did not meet the design safety factor. However, the engineer failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal (intentional disregard of other information); that the test equipment had failed (selective use of information)
text references: by providing only a partial, comparative engineering evaluation with no analysis and a recommendation to Engineer A's benefit, the conduct constituted both incomplete and self-serving information
text references: include all relevant and pertinent information
text references: objective and truthful
violation impact: Client or public reliance on incomplete or misleading professional work product, potential safety consequences, professional discipline, and reputational harm.
discovered in case: 14
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T08:48:44.763664+00:00
first discovered in case: 14
match confidence: 0.75
match reasoning: The Report Integrity Constraint is closely related to Non-Deception in that selective omission and intentional disregard of contrary evidence are forms of deception. However, the constraint here is broader, encompassing affirmative completeness duties and investigative thoroughness beyond mere non-deception. It also overlaps with the previously extracted Advisory Scope Completeness Constraint and Report Completeness Obligation. A medium-confidence match to Non-Deception is appropriate, but the completeness and investigation dimensions make this a variant rather than an exact match.
matched ontology class: Non Deception
matched ontology label: Non-Deception (Constraint)
matches existing: true
source text: objective and truthful
comment: Ethical and professional constraint requiring that an engineer's report, analysis, or advisory product be objective and truthful and include all relevant and pertinent information, prohibiting selective omission, intentional disregard of contrary evidence, or incomplete investigation that would render the product misleading.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [Non_Deception] Constraint established by ethics code provisions
generated at time: 2026-06-04T08:48:44.763664+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Verification Capability
type: Class
capability category: reasoning
confidence: 0.85
domain specificity: Licensed professional engineering practice across technical domains
enables actions: Assess adequacy of one's own review process
enables actions: Determine whether review depth supports responsible charge
enables actions: Identify gaps between cursory review and the standard required for sealing
required for obligations: AI Output Verification Obligation
required for obligations: Responsible Charge Seal Obligation
skill level: advanced
text references: Client W noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
text references: Engineer A was obligated to apply their professional seal to the engineering design documents only after conducting a review sufficient to take general responsibility for the work
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:21.353968+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A was obligated to apply their professional seal to the engineering design documents only after conducting a review sufficient to take general responsibility for the work
comment: Capability to conduct a review of professional work products that is sufficiently thorough to support the exercise of responsible charge, including the ability to assess whether one's review is adequate before applying a professional seal.
subclass of: Capability
generated at time: 2026-06-03T14:06:21.353968+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Scope Limitation Justification State
type: Class
action constraints: Professional must not present conclusions as complete when scope prevented full investigation
action constraints: Professional must not use scope limitation as a shield against reporting known material findings
activation conditions: Material information exists outside the literal scope
activation conditions: Professional declines to investigate or report that information citing scope limitations
activation conditions: Professional is retained under a defined scope of work
confidence: 0.85
obligation activation: Duty to assess whether scope limitations prevent fulfillment of independent professional obligations
obligation activation: Duty to disclose scope limitations that affect completeness of conclusions
obligation activation: Duty to seek scope expansion when material safety or accuracy issues are identified
persistence type: inertial
principle transformation: Transforms the contractual faithful-agent duty into a bounded obligation that cannot override the independent professional duty of objectivity and completeness when material findings are at stake.
state category: conflict
termination conditions: Engagement concludes
termination conditions: Professional voluntarily addresses the material information despite scope limitation
termination conditions: Scope is expanded to cover the material information
text references: Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'
discovered in case: 71
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T14:26:51.674939+00:00
first discovered in case: 71
match confidence: 0.0
matches existing: false
source text: Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'
comment: State in which a professional invokes a contractually defined scope of work as justification for failing to investigate or report on material technical findings that bear on safety or accuracy, creating a tension between contractual scope compliance and the professional's independent duty of completeness and objectivity.
subclass of: ConflictState
generated at time: 2026-06-04T14:26:51.674939+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Technology Non-Substitution Judgment Capability
type: Class
capability category: awareness
confidence: 0.85
domain specificity: Professional engineering practice involving computer-assisted or AI-assisted design tools
enables actions: Decline to incorporate CADD or AI outputs the engineer does not fully understand
enables actions: Distinguish between tool-assisted professional work and tool-substituted professional judgment
enables actions: Maintain independent professional judgment when using automated design systems
enables actions: Recognize liability exposure created by uncritical reliance on system outputs
required for obligations: Responsible Charge Seal Obligation
required for obligations: Technology Non-Substitution Obligation
required for obligations: Technology Tool Non-Substitution Obligation
skill level: advanced
text references: CADD utilized beyond its ability to serve as a valuable tool has a propensity to be utilized as a crutch or substitute for judgement. That translates to a scenario for potential liability.
text references: In some instances, there may be a temptation for the engineer to incorporate a solution provided by the system which the engineer has neither prepared nor fully understands because the engineer believes, based upon engineer's confidence in the system and upon prior experience, that the system will provide a quality solution on a project.
text references: The key point is that the engineer must utilize such systems to assist the engineer in the performance of professional services and not employ such systems as a replacement for professional competence and expertise.
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:12:59.240485+00:00
first discovered in case: 120
match confidence: 0.78
match reasoning: AI Direction and Control Capability addresses the engineer's ability to exercise genuine professional direction over AI-assisted tools and ensure final work reflects independent judgment rather than uncritical acceptance of AI output. Technology Non-Substitution Judgment Capability is the same concept applied to CADD systems, with emphasis on the recognition dimension: identifying when the tool is crossing from aid to substitute. The match is a medium-confidence variant because the existing class emphasizes direction and control actions while this class emphasizes the perceptual and judgment dimension of recognizing the substitution risk.
matched ontology class: AI Direction and Control Capability
matched ontology label: AI Direction and Control Capability
matches existing: true
source text: In some instances, there may be a temptation for the engineer to incorporate a solution provided by the system which the engineer has neither prepared nor fully understands because the engineer believes, based upon engineer's confidence in the system and upon prior experience, that the system will provide a quality solution on a project.
comment: Capability of a licensed professional engineer to recognize when a technological tool such as a CADD system or AI-assisted platform is being used as a substitute for professional judgment rather than as an aid to it, and to resist the temptation to incorporate system-generated solutions that the engineer has neither prepared nor fully understands, ensuring that the tool remains subordinate to the engineer's independent professional competence.
subclass of: Capability
scope note: [AIDirectionandControlCapability] Capability to exercise genuine professional direction and control over AI-assisted tools used to generate engineering work products, including the ability to outline solution guidelines and constraints, critically evaluate AI outputs, and ensure that final work products reflect independent professional judgment rather than uncritical acceptance of AI-generated content.
generated at time: 2026-06-04T18:12:59.240485+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Technology Non-Substitution Obligation
type: Class
confidence: 0.91
derived from principle: Technology Substitution Prohibition Principle
enforcement level: mandatory
monitoring criteria: Evidence that the engineer actively directed the use of the tool, reviewed outputs critically, and did not passively accept system-generated solutions without independent verification
nspe reference: II.2.b
obligation type: ethical
stakeholders affected: Clients
stakeholders affected: Employers
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: CADD utilized beyond its ability to serve as a valuable tool has a propensity to be utilized as a crutch or substitute for judgement.
text references: In some instances, there may be a temptation for the engineer to incorporate a solution provided by the system which the engineer has neither prepared nor fully understands because the engineer believes, based upon engineer's confidence in the system and upon prior experience, that the system will provide a quality solution on a project.
text references: The key point is that the engineer must utilize such systems to assist the engineer in the performance of professional services and not employ such systems as a replacement for professional competence and expertise.
violation consequences: Ethical violation under NSPE II.2.b; potential professional liability; risk of sealing documents not genuinely under the engineer's direction and control
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T18:11:22.208486+00:00
first discovered in case: 120
match confidence: 0.92
match reasoning: This obligation is substantively identical to the Technology Tool Non-Substitution Obligation already extracted from prior sections of this case. The concept is the same: engineers must not allow CADD or similar tools to substitute for professional judgment. Matched at high confidence as the same class.
matched ontology class: TechnologyToolNonSubstitutionObligation
matched ontology label: Technology Tool Non-Substitution Obligation
matches existing: true
source text: CADD utilized beyond its ability to serve as a valuable tool has a propensity to be utilized as a crutch or substitute for judgement.
comment: Duty of a licensed engineer to ensure that technological tools, including CADD systems and similar computer-assisted platforms, serve as instruments of professional production under the engineer's direction rather than as substitutes for the engineer's own professional judgment, so that the engineer retains genuine intellectual and technical responsibility for the work product and does not incorporate system-generated solutions the engineer has not prepared or fully understands.
subclass of: EthicalObligation
generated at time: 2026-06-04T18:11:22.208486+00:00
was attributed to: Case 120 Extraction
was attributed to: claude-sonnet-4-6

Technology Substitution Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Professional licensing board
affected stakeholders: Public
confidence: 0.84
constraint type: ethical
flexibility: hard
mitigation strategies: Apply independent engineering judgment to all tool-generated recommendations
mitigation strategies: Document the basis for accepting or modifying tool outputs
mitigation strategies: Treat AI and software outputs as preliminary inputs requiring critical review
text references: Engineer A relied on the AI-generated plans and specifications without proper oversight.
text references: Recommendations from the program or intern should not be blindly accepted, they should be considered and challenged and the resulting outputs should be understood.
text references: it is the [BER]'s position that technology has an important place in the practice of engineering, but it must never be a replacement of a substitute for engineering judgment.
violation impact: Abdication of professional judgment, submission of work products that do not reflect genuine engineering analysis, public safety risk, ethics code violation
discovered in case: 7
discovered in case: 120
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:08.316438+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: it is the [BER]'s position that technology has an important place in the practice of engineering, but it must never be a replacement of a substitute for engineering judgment.
comment: Ethical constraint prohibiting an engineer from using a technological tool as a replacement or substitute for independent engineering judgment, requiring that the engineer's own expertise, critical evaluation, and professional standards govern all decisions and that tool outputs be challenged and verified before acceptance.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-03T14:11:08.316438+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Unfamiliar Tool Deployment State
type: Class
action constraints: Should not rely on tool outputs without independent verification when tool behavior is not fully understood
action constraints: Should not represent outputs as professionally validated without adequate review
activation conditions: Professional adopts a tool or technology for the first time without prior training or experience
activation conditions: Tool is new to the market or otherwise untested in the professional's practice context
confidence: 0.87
obligation activation: Obligation to conduct thorough verification of tool outputs before relying on them
obligation activation: Obligation to disclose use of unfamiliar tools to clients or supervisors where output reliability is uncertain
obligation activation: Obligation to seek guidance or training before deploying the tool on consequential work
persistence type: inertial
principle transformation: Transforms general competence and due care principles into specific verification and disclosure duties when deploying tools whose accuracy and limitations are not yet understood by the professional.
state category: competence
termination conditions: Professional completes formal training on the tool
termination conditions: Professional gains sufficient experience and familiarity with the tool
termination conditions: Use of the tool is discontinued
text references: Not being familiar with the full functionality of the AI software, including the accuracy and originality of AI-generated text
text references: The AI drafting software was new to the market and Engineer A had no previous experience with the tool
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T14:00:13.061399+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: The AI drafting software was new to the market and Engineer A had no previous experience with the tool
comment: State in which a professional uses a tool, technology, or method with which they have no prior experience, creating elevated risk of undetected errors and triggering heightened obligations of verification, disclosure, and caution before relying on outputs for professional work products.
subclass of: CompetenceState
generated at time: 2026-06-03T14:00:13.061399+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Verbal Disclosure Written Report Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Public Authority
confidence: 0.88
constraint type: ethical
flexibility: hard
mitigation strategies: Document all findings in writing before submission to any public authority
mitigation strategies: Include all material factual findings in written reports regardless of prior verbal disclosure
mitigation strategies: Treat verbal communication as supplementary to, not a substitute for, written disclosure
text references: Engineer A verbally mentioned the concern, but Engineer A did not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal. The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority.
text references: The BER noted that Engineer A was obligated under Code section II.3.a to be objective and truthful in professional reports, statements, or testimony and include all relevant and pertinent information in such reports.
violation impact: Public authority acts on incomplete information, engineer violates objectivity and truthfulness obligations under professional ethics codes, potential harm to public welfare.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:14.702097+00:00
first discovered in case: 8
match confidence: 0.82
match reasoning: The concept is a variant of the Report Integrity Constraint, which requires that an engineer's report be objective and truthful and include all relevant and pertinent information, prohibiting selective omission. The present constraint adds the specific dimension that verbal disclosure to a client does not substitute for written inclusion in a report to a public authority, making it a more specific procedural application of the same underlying principle. Medium confidence match to parent.
matched ontology class: Report Integrity Constraint
matched ontology label: Report Integrity Constraint
matches existing: true
source text: Engineer A verbally mentioned the concern, but Engineer A did not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal. The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority.
comment: Ethical and procedural constraint requiring that when an engineer has identified a material factual finding relevant to a public authority's decision, verbal communication of that finding to a client does not satisfy the engineer's obligation to include it in a written report submitted to that authority. The finding must appear in the written record so that the public authority receives complete and accurate information.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [ReportIntegrityConstraint] Ethical and professional constraint requiring that an engineer's report, analysis, or advisory product be objective and truthful and include all relevant and pertinent information, prohibiting selective omission, intentional disregard of contrary evidence, or incomplete investigation that would render the product misleading.
generated at time: 2026-06-04T10:08:14.702097+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Verbal Only Report Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Public Authority
confidence: 0.92
constraint type: ethical
flexibility: hard
mitigation strategies: Document verbal disclosures and follow up with written confirmation
mitigation strategies: Include all material findings in written reports regardless of client preference
mitigation strategies: Refuse client instructions to omit material findings from written reports
text references: Engineer A verbally mentioned the concern, but Engineer A did not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal.
text references: The BER concluded that it was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority.
text references: The BER noted that Engineer A was obligated under Code section II.3.a to be objective and truthful in professional reports, statements, or testimony and include all relevant and pertinent information in such reports.
violation impact: Public authority makes decisions without complete written record; engineer violates objectivity and truthfulness obligations under professional ethics codes.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-05T02:27:13.190895+00:00
first discovered in case: 8
match confidence: 0.93
match reasoning: The Verbal Disclosure Written Report Constraint in the ontology captures exactly this concept: verbal communication of a material factual finding to a client does not satisfy the engineer's obligation to include it in a written report submitted to a public authority. The BER Case 07-6 facts about Engineer A and the bird species are a direct instantiation of that class.
matched ontology class: Verbal Disclosure Written Report Constraint
matched ontology label: Verbal Disclosure Written Report Constraint
matches existing: true
source text: Engineer A verbally mentioned the concern, but Engineer A did not include the information in a written report that will be submitted to a public authority that is considering the developer's proposal.
comment: Ethical and procedural constraint prohibiting an engineer from treating a verbal communication of a material technical finding as a substitute for including that finding in a written report submitted to a public authority or other relying party. The finding must appear in the written record so that the public authority receives complete and accurate information.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
scope note: [VerbalDisclosureWrittenReportConstraint] Ethical and procedural constraint requiring that when an engineer has identified a material factual finding relevant to a public authority's decision, verbal communication of that finding to a client does not satisfy the engineer's obligation to include it in a written report submitted to that authority. The finding must appear in the written record so that the public authority receives complete and accurate information.
generated at time: 2026-06-05T02:27:13.190895+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

AI Direction and Control Capability
type: Class
capability category: domain_specific
confidence: 0.88
domain specificity: Professional engineering practice using AI-assisted drafting and language processing tools
enables actions: Critically challenge and evaluate AI-generated recommendations
enables actions: Define solution parameters and constraints before engaging AI tools
enables actions: Distinguish between acceptable AI assistance and inappropriate substitution of AI for professional judgment
enables actions: Ensure final work products reflect the engineer's own professional standards
required for obligations: AI Direction and Control Obligation
skill level: advanced
text references: Because Engineer A performed a thorough review, cross-checked key facts against professional sources, and made adjustments to the text, the final document remained under Engineer A's direction and control
text references: Code section II.2.b states that, '[e]ngineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control.'
text references: Much like directing an engineering intern to solve a problem, responsible use of AI requires an engineer to outline solution guidelines and constraints. Recommendations from the program or intern should not be blindly accepted, they should be considered and challenged and the resulting outputs should be understood.
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:11:06.673267+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Much like directing an engineering intern to solve a problem, responsible use of AI requires an engineer to outline solution guidelines and constraints. Recommendations from the program or intern should not be blindly accepted, they should be considered and challenged and the resulting outputs should be understood.
comment: Capability to exercise genuine professional direction and control over AI-assisted tools used to generate engineering work products, including the ability to outline solution guidelines and constraints, critically evaluate AI outputs, and ensure that final work products reflect independent professional judgment rather than uncritical acceptance of AI-generated content.
subclass of: Capability
generated at time: 2026-06-03T14:11:06.673267+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Client Boundary Judgment Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: Expert witness and retained engineering roles in litigation or dispute resolution
enables actions: Communicate the limits of permissible client advocacy to the retaining party
enables actions: Decline to omit material evidence from a technical report even under client pressure
enables actions: Identify when a client's instructions conflict with professional obligations
enables actions: Serve client interests within the bounds of professional ethics
required for obligations: Faithful Agent Boundary Obligation
skill level: advanced
text references: Engineer B said: 'We just did not believe the driving records and there was also the issue of whether the pile was vented to allow air to escape.'
text references: Engineer B was obligated to serve the municipality's legitimate interests while refusing to omit material technical evidence from the report, even under pressure from the retaining client.
discovered in case: 71
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T14:32:46.344874+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: No existing capability class covers the judgment competency of distinguishing legitimate client service from impermissible omission of material evidence.
matches existing: false
source text: Engineer B was obligated to serve the municipality's legitimate interests while refusing to omit material technical evidence from the report, even under pressure from the retaining client.
comment: Ability to distinguish between serving a client's legitimate interests and complying with requests that would require omitting material technical evidence or compromising professional integrity, and to act accordingly.
subclass of: Capability
generated at time: 2026-06-04T14:32:46.344874+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Client Economic Pressure Safety Continuation Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.85
constraint type: ethical
flexibility: hard
mitigation strategies: Advise the client in writing that the project cannot proceed safely without the recommended measures
mitigation strategies: Decline to continue work when the client refuses necessary safety measures
mitigation strategies: Document the safety recommendation and the client's refusal before withdrawing
mitigation strategies: Notify appropriate regulatory authorities if the client proceeds without safeguards
text references: Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project.' The BER, in discussing BER Case 84-5, felt that 'Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.'
text references: Engineer L cannot ethically acquiesce to Client X's insistence to continue work on the project when Client X refuses to invest in the protective measures identified by Engineer L.
text references: The client indicated that hiring the representative would be too costly, and Engineer A continues to work on the project.
violation impact: Engineer violates the paramount duty to public safety, exposes the public to confirmed risk, and acts in violation of professional ethics codes by prioritizing client economic concerns over safety obligations.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:14.702097+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer A 'abandoned the ethical duty [to the public] and proceeded to work on the project.' The BER, in discussing BER Case 84-5, felt that 'Engineer A acted in a manner that suggests the primary obligation was not the public, but the client's economic concerns. For that reason, Engineer A was in violation of Code section II.1.a.'
comment: Ethical constraint prohibiting an engineer from continuing work on a project after a client declines to implement safety measures the engineer has identified as necessary, when proceeding would require the engineer to subordinate public safety obligations to the client's economic concerns. The engineer must cease participation rather than abandon the duty to hold public safety paramount in favor of client financial preferences.
subclass of: EthicalConstraint
subclass of: InviolableConstraint
generated at time: 2026-06-04T10:08:14.702097+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Client Instruction Limits Obligation
type: Class
confidence: 0.83
derived from principle: Client Loyalty Limits
enforcement level: mandatory
monitoring criteria: Evidence that the engineer declined or objected to the client instruction and articulated the professional ethics basis for refusal
nspe reference: II.4
obligation type: ethical
stakeholders affected: Client or employer
stakeholders affected: Professional engineering community
stakeholders affected: Third-party engineers
text references: Engineer B objects to conducting the peer review without advising Engineer A.
text references: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
violation consequences: Complicity in ethics violation; professional disciplinary action; harm to third-party engineers
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:56:24.847658+00:00
first discovered in case: 15
match confidence: 0.76
match reasoning: This obligation is the defeasible counterpart to the Faithful Agent Obligation. The existing Faithful Agent Obligation is explicitly noted as defeasible under states that confirm public-safety risk or ethics violations, and this class captures the duty that defeats it when client instructions cross ethical lines. Medium confidence because the existing class addresses the same role-relationship from the complementary direction.
matched ontology class: FaithfulAgentObligation
matched ontology label: Faithful Agent Obligation
matches existing: true
source text: Owner instructs Engineer B to conduct the peer review without letting Engineer A know.
comment: Duty of an engineer to decline client instructions that would require violating professional ethics obligations, recognizing that the faithful agent duty does not extend to complying with directives that breach professional standards.
subclass of: EthicalObligation
scope note: [FaithfulAgentObligation] Duty of an engineer to act as a faithful agent or trustee of an employer or client (NSPE Code of Ethics, Section 1 / §II.4). Defeasible under states that confirm public-safety risk.
generated at time: 2026-06-02T19:56:24.847658+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Client Override of Safety Recommendation State
type: Class
action constraints: Professional may not simply defer to client preference when public safety obligations are active
action constraints: Professional should not proceed as if the safety concern has been resolved
activation conditions: Client has explicitly rejected or deferred the recommendation
activation conditions: Professional has communicated a safety recommendation to the client
activation conditions: Project proceeds without the recommended safeguards
confidence: 0.87
obligation activation: Duty to assess whether continued participation is ethically permissible
obligation activation: Duty to consider reporting to regulatory authorities if public safety is at risk
obligation activation: Duty to document the recommendation and client's rejection
obligation activation: Duty to refuse to seal or certify work that does not meet safety standards
persistence type: inertial
principle transformation: Transforms the general duty to hold public safety paramount into a concrete obligation to escalate beyond client communication, potentially including regulatory notification or withdrawal, when the client has overridden a safety recommendation.
state category: conflict
termination conditions: Client accepts and implements the recommendation
termination conditions: Professional withdraws from the engagement
termination conditions: Regulatory authority intervenes
termination conditions: Risk is otherwise mitigated
text references: Client X insists on proceeding without added safeguards
text references: Client X is hesitant to invest in additional protective measures, citing continuing budget limitations
text references: Client X will address any compliance issues later, if needed
discovered in case: 8
discovered in case: 76
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T09:58:09.658057+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Client X insists on proceeding without added safeguards
comment: State in which a client has been informed of a professional's safety recommendation and has explicitly directed the professional to proceed without implementing that recommendation, citing cost or other business constraints, creating a direct tension between the client's authority over project scope and the professional's duty to protect public safety and comply with applicable regulatory standards.
subclass of: ConflictState
scope note: [Case 76] State in which a governing body or client has been informed of professional safety recommendations and has explicitly voted or directed to proceed without implementing those recommendations, creating a direct tension between the client's authority over project scope and the professional's duty to protect public safety and comply with applicable regulatory standards.
generated at time: 2026-06-04T09:58:09.658057+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Complete Technical Reporting Obligation
type: Class
confidence: 0.92
derived from principle: Complete Reporting Principle
enforcement level: mandatory
monitoring criteria: Report includes all material test data, equipment status, and methodological facts; omissions are documented with stated rationale.
nspe reference: III.2
obligation type: reporting
stakeholders affected: Client
stakeholders affected: Courts or arbitrators
stakeholders affected: General public
stakeholders affected: Opposing parties
stakeholders affected: Reviewing engineers
text references: As an engineering document the report is incomplete and does a disservice to Engineer B's client municipality by potentially misdirecting a conclusion.
text references: Material facts, however, were not addressed in Engineer B's report. Among them, that dynamic test equipment failed during the test, and that all 19 test piles reported as failing the test were driven to refusal.
text references: the Code of Ethics which requires that engineers 'shall include all relevant and pertinent information in such report, statements or testimony.'
violation consequences: Report serves only an adversarial purpose rather than a technical one; client may be misdirected; professional credibility is undermined; potential NSPE Code violation.
discovered in case: 71
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T14:35:09.835244+00:00
first discovered in case: 71
match confidence: 0.0
match reasoning: The existing Contradictory Evidence Disclosure Obligation addresses acknowledging contradictory evidence, and the Scope Limitation Disclosure Obligation addresses disclosing methodological constraints. This obligation is distinct in that it captures the affirmative duty to include all relevant and pertinent technical facts in a report, not merely to disclose limitations or contradictions, grounded directly in the NSPE Code provision requiring complete reporting. It is broader and independently grounded.
matches existing: false
source text: the Code of Ethics which requires that engineers 'shall include all relevant and pertinent information in such report, statements or testimony.'
comment: Duty of an engineer preparing a technical report to include all relevant and pertinent technical information, including facts that may complicate or contradict the primary conclusions, so that the report supports informed review and interpretation by others.
subclass of: ReportingObligation
generated at time: 2026-06-04T14:35:09.835244+00:00
was attributed to: Case 71 Extraction
was attributed to: claude-sonnet-4-6

Concern Versus Fact Disclosure Threshold Obligation
type: Class
confidence: 0.82
derived from principle: Fact-Based Disclosure Threshold Principle
enforcement level: conditional
monitoring criteria: Documentation showing whether the engineer's finding was supported by completed technical analysis before disclosure was characterized as mandatory
nspe reference: II.3.b
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory authorities
text references: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's 'concern' does not rise to the technical or moral level of 'fact,' and per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts.
text references: The BER's view is that, while it might be prudent for Engineer L to inform Client X of their concerns, such disclosure is not required under the Code.
violation consequences: Premature mandatory disclosure claims may misrepresent the state of technical knowledge; failure to recognize the threshold may lead to either over-disclosure of unverified concerns or under-disclosure of confirmed facts
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:06:46.728956+00:00
first discovered in case: 8
match confidence: 0.72
match reasoning: This is a variant of the general Disclosure Obligation that specifically addresses the threshold condition distinguishing a preliminary concern from a technical fact for purposes of mandatory disclosure. The Fact-Based Disclosure Threshold Principle was identified in prior extraction, and this obligation operationalizes that principle. No existing class captures the concern-versus-fact distinction as a conditional trigger for disclosure duties.
matched ontology class: DisclosureObligation
matched ontology label: Disclosure Obligation
matches existing: true
source text: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's 'concern' does not rise to the technical or moral level of 'fact,' and per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts.
comment: Duty of an engineer to distinguish between a preliminary concern that has not yet been substantiated by technical analysis and a finding that constitutes a technical fact, and to recognize that mandatory disclosure obligations under Code section II.3.b are triggered only when the engineer's assessment rises to the level of fact rather than unverified concern, while acknowledging that prudent voluntary disclosure of concerns may nonetheless be appropriate.
subclass of: DisclosureObligation
scope note: [DisclosureObligation] Requirement to inform stakeholders about conflicts, limitations, or risks (NSPE II.3.a)
generated at time: 2026-06-04T10:06:46.728956+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Confidentiality Scope Reasoning Capability
type: Class
capability category: reasoning
confidence: 0.78
domain specificity: Professional engineering ethics and confidentiality in peer review
enables actions: Distinguish procedural propriety from confidentiality of findings
enables actions: Identify the proper scope of a confidentiality obligation
enables actions: Recognize when confidentiality cannot override notification duties
required for obligations: Covert Review Refusal Obligation
required for obligations: Peer Review Notification Obligation
skill level: intermediate
text references: Engineer B was obligated to protect the contents and findings of the peer review as confidential to the Owner, but this confidentiality obligation did not extend to conducting the review covertly
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:57:30.046199+00:00
first discovered in case: 15
match confidence: 0.76
match reasoning: Reasoning about the scope and limits of a confidentiality obligation in order to distinguish permissible from impermissible conduct is a form of ethical reasoning as described by Wallach and Allen 2009 and Belle 2023. This is a variant focused on confidentiality boundary analysis, matched at medium confidence.
matched ontology class: EthicalReasoning
matched ontology label: Ethical Reasoning
matches existing: true
source text: Engineer B was obligated to protect the contents and findings of the peer review as confidential to the Owner, but this confidentiality obligation did not extend to conducting the review covertly
comment: Capability to reason about the limits of confidentiality obligations, distinguishing between protecting the contents of a review and using confidentiality as a basis for procedurally improper conduct such as covert review.
subclass of: Capability
scope note: [EthicalReasoning] Capability to process ethical information, deliberate on choices, and exercise moral judgment (Wallach & Allen 2009, Belle 2023)
generated at time: 2026-06-02T19:57:30.046199+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Deficient Work Product Submitted State
type: Class
action constraints: Should not allow deficient work product to remain in use without correction
action constraints: Should not minimize or conceal the nature or extent of identified deficiencies
activation conditions: Client or reviewer identifies errors, omissions, or regulatory non-compliance in a submitted work product
activation conditions: Work product is found to be inaccurate or incomplete after submission
confidence: 0.88
obligation activation: Obligation to assess whether deficiencies create safety or regulatory compliance risks
obligation activation: Obligation to investigate the root cause of deficiencies to prevent recurrence
obligation activation: Obligation to notify affected parties if deficiencies pose safety risks
obligation activation: Obligation to revise and correct the deficient work product promptly
persistence type: inertial
principle transformation: Transforms general professional responsibility and public safety principles into specific corrective action and notification duties once deficiencies in a submitted work product are confirmed.
state category: risk
termination conditions: Client accepts a corrected version and any safety or compliance risks are resolved
termination conditions: Deficiencies are corrected and a revised work product meeting applicable standards is submitted
text references: Client W noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations
text references: Client W raised concerns about the accuracy and reliability of the engineering design and instructed Engineer A to revise the plans
discovered in case: 7
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-03T14:00:13.061399+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Client W noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations
comment: State in which a professional has submitted a work product to a client that contains errors, omissions, or deficiencies that fail to meet professional or regulatory standards, creating obligations to correct the deficiencies, notify affected parties, and assess whether safety or compliance risks have been introduced.
subclass of: RiskState
generated at time: 2026-06-03T14:00:13.061399+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Environmental Protection Regulation Resource
type: Class
authority source: Local and state environmental regulatory agencies
confidence: 0.85
extensional function: Establishes binding legal floor for engineering design decisions affecting environmental quality and public water supply, grounding professional obligations in enforceable regulatory requirements.
resource category: legal_resource
text references: local environmental standards require steps to safeguard public water sources
usage context: Environmental compliance assessment
usage context: Public water source protection
usage context: Stormwater management design
discovered in case: 8
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T09:57:35.025217+00:00
first discovered in case: 8
match confidence: 0.75
match reasoning: The local environmental standards requiring steps to safeguard public water sources are a variant of the existing Local Regulatory Safety Requirement Resource class. The existing class covers local or jurisdictional regulations specifying mandatory safety features and design requirements. Environmental protection of drinking water sources is a closely related but distinct domain, focused on environmental compliance rather than structural safety, warranting a medium-confidence match as a subtype.
matched ontology class: Local Regulatory Safety Requirement Resource
matched ontology label: Local Regulatory Safety Requirement Resource
matches existing: true
source text: local environmental standards require steps to safeguard public water sources
comment: Local, state, or jurisdictional regulations specifying mandatory environmental protection requirements, including standards for safeguarding public water sources and controlling stormwater runoff impacts on natural water bodies.
subclass of: LegalResource
scope note: [LocalRegulatorySafetyRequirementResource] Local or jurisdictional regulations specifying mandatory safety features and design requirements that engineering documents must satisfy, serving as a binding technical and legal floor for professional engineering deliverables.
generated at time: 2026-06-04T09:57:35.025217+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Incomplete Analysis Disclosure Capability
type: Class
capability category: communication
confidence: 0.82
domain specificity: Professional engineering practice involving phased or suspended work scopes
enables actions: Communicate the significance of incomplete analysis to client
enables actions: Disclose preliminary risk findings to client during work suspension
enables actions: Flag unresolved safety concerns when pausing professional work
required for obligations: Preliminary Risk Disclosure Obligation
required for obligations: Report Completeness Obligation
skill level: intermediate
text references: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:03:17.498340+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
comment: Capability to recognize when a professional analysis has been suspended or left incomplete and to disclose the status and significance of unfinished findings to the client, including the ability to communicate identified but unquantified risks rather than remaining silent about them during a work suspension.
subclass of: Capability
generated at time: 2026-06-04T10:03:17.498340+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Incomplete Professional Report State
type: Class
action constraints: Professional must not omit information that would materially affect conclusions
action constraints: Professional must not render opinions based on selectively presented data
activation conditions: Professional fails to investigate relevant factors before rendering an opinion
activation conditions: Professional selectively uses data to support a predetermined conclusion
activation conditions: Professional submits report omitting known material information
confidence: 0.88
obligation activation: Duty to correct or supplement the deficient report
obligation activation: Duty to include all relevant and pertinent information
obligation activation: Duty to provide objective and truthful analysis
persistence type: inertial
principle transformation: Transforms general honesty and completeness principles into concrete obligations to investigate fully, disclose all material information, and refrain from rendering opinions based on incomplete or selectively assembled data.
state category: information
termination conditions: Corrected and complete report issued
termination conditions: Omitted information disclosed to affected parties
termination conditions: Professional retracts or supplements the incomplete submission
text references: failure to investigate
text references: integrity and completeness in preparing reports
text references: that the test equipment had failed (selective use of information)
text references: the engineer failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal
discovered in case: 14
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T08:42:02.559155+00:00
first discovered in case: 14
match confidence: 0.72
match reasoning: Deficient Work Product Submitted State covers errors and omissions in submitted work products, which overlaps substantially. However, the present concept is more specifically focused on the epistemic dimension of selective omission and failure to investigate in a report or opinion context, rather than the broader category of technical deficiencies. A medium-confidence match is appropriate; the existing class is the closest available but does not fully capture the deliberate or negligent omission of material information as the defining feature.
matched ontology class: Deficient Work Product Submitted State
matched ontology label: Deficient Work Product Submitted State
matches existing: true
source text: the engineer failed to include in the report that the initial log indicated that several of the piles were driven to essential refusal
comment: State in which a professional has produced or submitted a report or analysis that omits material information, selectively presents data, or fails to investigate relevant factors, resulting in a misleading or incomplete professional work product that violates duties of objectivity, completeness, and truthfulness.
subclass of: InformationState
scope note: [DeficientWorkProductSubmittedState] State in which a professional has submitted a work product to a client that contains errors, omissions, or deficiencies that fail to meet professional or regulatory standards, creating obligations to correct the deficiencies, notify affected parties, and assess whether safety or compliance risks have been introduced.
generated at time: 2026-06-04T08:42:02.559155+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Municipal Client
type: Class
confidence: 0.82
role category: provider_client
text references: City B's City Administrator asked Engineer A for a recommendation on project delivery methods
text references: Engineer A currently has no contractual relationship with City B
discovered in case: 14
discovered in pass: 1
discovered in section: facts
first discovered at: 2026-06-04T08:41:03.751066+00:00
first discovered in case: 14
match confidence: 0.78
match reasoning: City B functions as the commissioning client for the wastewater project. The municipal government context is a specialization of the general Client Role, warranting a medium-confidence match to that parent class.
matched ontology class: ClientRole
matched ontology label: Client Role
matches existing: true
source text: City B's City Administrator asked Engineer A for a recommendation on project delivery methods
comment: A government or municipal entity that commissions professional engineering or construction services for public infrastructure projects, acting as the primary client and decision-maker but without professional engineering licensure.
subclass of: ClientRole
subclass of: ProviderClientRole
scope note: [ClientRole] Party that commissions the project work. This is the occupational archetype. The duty relationship is carried separately by :ProviderClientRole.
generated at time: 2026-06-04T08:41:03.751066+00:00
was attributed to: Case 14 Extraction
was attributed to: claude-sonnet-4-6

Preliminary Risk Disclosure Obligation
type: Class
confidence: 0.88
derived from principle: Proactive Risk Disclosure Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that the engineer communicated identified risks to the client at the time of discovery, including during work suspension communications.
nspe reference: I.1, II.1.a, III.2.b
obligation type: disclosure
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase
text references: In their communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source.
violation consequences: Failure to disclose allows the client to make uninformed decisions about project suspension or resumption, potentially increasing public health risk and exposing the engineer to professional discipline.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:02:21.757544+00:00
first discovered in case: 8
match confidence: 0.75
match reasoning: This is a variant of the existing Disclosure Obligation, specialized to the context of preliminary or unquantified risk identification during a work suspension phase. The existing Disclosure Obligation covers the general duty to inform stakeholders about risks, but does not specifically address the obligation to disclose risks that have been identified but not yet fully quantified, particularly at a project suspension juncture. A new class is warranted to capture this temporal and epistemic specificity.
matched ontology class: DisclosureObligation
matched ontology label: Disclosure Obligation
matches existing: true
source text: Engineer L becomes concerned that the risk of impact to the community drinking water source will potentially increase
comment: Duty of an engineer who identifies a potential risk to public health or safety during a preliminary phase of work to disclose that risk to the client and relevant stakeholders promptly, even before the risk has been fully quantified, so that the client can make informed decisions about project scope, suspension, or protective measures.
subclass of: DisclosureObligation
scope note: [DisclosureObligation] Requirement to inform stakeholders about conflicts, limitations, or risks (NSPE II.3.a)
generated at time: 2026-06-04T10:02:21.757544+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Public Safety Paramount
type: Class
abstract nature: Open-textured value requiring interpretation of what constitutes sufficient risk to trigger override of ordinary professional deference to client and colleague relationships.
confidence: 0.93
derived obligations: Consent to peer review when significant design errors are known
derived obligations: Disclose known design deficiencies to reviewing engineers
derived obligations: Refrain from blocking safety-motivated oversight
extensional examples: NSPE BER Case 76-6 on obligation to report safety hazards discovered during construction
extensional examples: NSPE Canon 1 requiring engineers to hold paramount the safety, health, and welfare of the public
operationalization: Requires engineers to support independent review of designs containing known errors, refuse to obstruct safety-motivated peer review, and accept oversight even when it is professionally uncomfortable.
potential conflicts: Loyalty
potential conflicts: Professional Dignity
principle category: fundamental_ethical
text references: Engineer A objects and refused to consent to the peer review
text references: several significant design errors are discovered in the plans and design of Engineer A
value basis: Members of the public who occupy buildings cannot evaluate engineering design quality and depend entirely on professional integrity to protect them from latent structural risks.
discovered in case: 15
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-02T19:55:30.891672+00:00
first discovered in case: 15
match confidence: 0.9
match reasoning: The principle directly maps to the existing Public Safety class in the ontology, which covers the obligation to prioritize public safety in engineering decisions. The case instantiates this principle through the known design errors and the need for peer review to protect future occupants of the second tower.
matched ontology class: Public Safety
matched ontology label: Public Safety
matches existing: true
source text: several significant design errors are discovered in the plans and design of Engineer A
comment: Fundamental principle requiring engineers to prioritize public safety above client instructions, employer directives, or collegial relationships when significant design errors create risk to persons who will occupy or use engineered structures.
subclass of: FundamentalEthicalPrinciple
generated at time: 2026-06-02T19:55:30.891672+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6

Public Safety Paramount Judgment Capability
type: Class
capability category: reasoning
confidence: 0.82
domain specificity: Professional engineering ethics, applicable across all engineering disciplines
enables actions: Conclude that public welfare obligations override confidentiality or loyalty in cases of substantial legal violation
enables actions: Decide to report a violation to regulatory authorities despite adverse consequences for the client
enables actions: Weigh public safety obligations against client loyalty duties
required for obligations: Environmental Compliance Reporting Obligation
required for obligations: Observed Violation Disclosure Obligation
required for obligations: Post-Engagement Violation Reporting Obligation
skill level: advanced
text references: A few months after Engineer A completes the services, he drives by his client's property and notices that the client has installed a substantial amount of fill material on more than 1/2 an acre across a portion of the wetlands without any permits, variances, or permissions.
text references: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
discovered in case: 8
discovered in case: 86
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T17:31:02.848953+00:00
first discovered in case: 86
match confidence: 0.74
match reasoning: Ethical Reasoning covers the capability to process ethical information, deliberate on choices, and exercise moral judgment. The public safety paramount judgment is a specific application of ethical reasoning in which the engineer must weigh competing duties and conclude that public welfare prevails. The existing class is the closest match but is more general. The present capability is a distinct and recurrent type of ethical reasoning in engineering ethics cases involving the paramount public safety duty, warranting a new specialized class.
matched ontology class: EthicalReasoning
matched ontology label: Ethical Reasoning
matches existing: true
source text: The installation of the fill material is a substantial violation of the federal and state laws and regulations.
comment: Capability to recognize that the professional obligation to hold paramount the safety, health, and welfare of the public takes precedence over duties of loyalty to a client or former client, and to act on that recognition by taking affirmative steps such as regulatory reporting even when doing so is adverse to the client's interests.
subclass of: Capability
scope note: [EthicalReasoning] Capability to process ethical information, deliberate on choices, and exercise moral judgment (Wallach & Allen 2009, Belle 2023)
generated at time: 2026-06-04T17:31:02.848953+00:00
was attributed to: Case 86 Extraction
was attributed to: claude-sonnet-4-6

Regulatory Reporting Trigger Recognition Capability
type: Class
capability category: norm_management
confidence: 0.86
domain specificity: Environmental and public safety engineering with regulatory reporting dimensions
enables actions: Determine the appropriate regulatory authority to receive a report
enables actions: Identify when findings about environmental or safety risks trigger mandatory reporting to regulatory bodies
enables actions: Proceed with regulatory notification despite client instructions to the contrary
required for obligations: Client Override Public Safety Reporting Obligation
skill level: advanced
text references: BER Case 76-4 concluded that Doe had an obligation to report his findings to the Pollution Control Authority.
text references: Engineer L was obligated to report the identified risk to the community drinking water source to the appropriate pollution control or regulatory authority.
text references: Upon learning of the hearing, he is squarely confronted with his obligations to the public concerning its safety, health, and welfare. Section 2(a) requires that his duty to the public be paramount.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:30.219581+00:00
first discovered in case: 8
match confidence: 0.72
match reasoning: Safety Disclosure Escalation Capability addresses recognizing when internal resolution has failed and escalating to regulatory authorities, which partially overlaps. However, the present capability is more specifically about recognizing the initial trigger for regulatory reporting when a client has suppressed a report, rather than about sequencing escalation steps after internal failure. The match is a variant rather than an exact match, so medium confidence is appropriate.
matched ontology class: Safety Disclosure Escalation Capability
matched ontology label: Safety Disclosure Escalation Capability
matches existing: true
source text: BER Case 76-4 concluded that Doe had an obligation to report his findings to the Pollution Control Authority.
comment: Capability to recognize when identified professional findings about public health or safety risks must be reported to a regulatory or pollution control authority, including the ability to identify the appropriate authority and to act on that obligation even when the client has instructed the engineer not to complete or submit a report.
subclass of: Capability
scope note: [SafetyDisclosureEscalationCapability] Capability to recognize when internal resolution of a safety concern has failed and to escalate disclosure to appropriate regulatory authorities, including the ability to sequence escalation steps correctly by first advising the responsible engineer before notifying authorities.
generated at time: 2026-06-04T10:08:30.219581+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Engineer
type: Class
confidence: 0.88
role category: provider_client
text references: Engineer A did not maintain responsible charge in violation of licensure law
text references: Engineer A, as the engineer in Responsible Charge of the project, is required to provide an experienced-based quality assurance review
text references: NSPE defines 'Responsible Charge' in NSPE Position Statement No. 10-1778 as 'being actively engaged in the engineering process, from conception to completion.'
discovered in case: 7
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-03T14:00:40.742585+00:00
first discovered in case: 7
match confidence: 0.72
match reasoning: Responsible Charge Engineer is a specialization of Engineer Role, distinguished by the formal licensure-law concept of responsible charge, which imposes active engagement and supervisory control obligations beyond general engineering practice. No existing extracted class captures this specific licensure-based accountability framing.
matched ontology class: EngineerRole
matched ontology label: Engineer Role
matches existing: true
source text: Engineer A did not maintain responsible charge in violation of licensure law
comment: A licensed professional engineering role in which the practitioner bears formal responsible charge over a project or work product, meaning they must be actively engaged in the engineering process from conception to completion, personally make or directly supervise all engineering decisions, and cannot satisfy this obligation by reviewing completed documents after the fact without involvement in design and development.
subclass of: EngineerRole
subclass of: ProviderClientRole
scope note: [EngineerRole] A professional role involving engineering practice and responsibilities. Occupational archetype head for all engineer specializations and extracted engineer-role leaves.
generated at time: 2026-06-03T14:00:40.742585+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Seal Obligation
type: Class
confidence: 0.9
derived from principle: Responsible Charge Integrity Principle
enforcement level: mandatory
monitoring criteria: Documentation of review process prior to sealing; evidence that the engineer understood the content and methodology of the sealed work product
nspe reference: II.2, III.2.b
obligation type: ethical
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Professional licensing board
stakeholders affected: Regulatory bodies
text references: Client W, however, noticed several issues with the AI-generated design documents, including misaligned dimensions and an omission of key safety features required by local regulations.
text references: Engineer A applied their seal consistent with state law.
text references: Engineer A completed a cursory review of the AI-generated plans and adjusted certain elements to align with site-specific conditions.
violation consequences: Misrepresentation of professional oversight; regulatory violation; professional license sanctions; liability for deficient sealed documents
discovered in case: 7
discovered in case: 120
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:05:12.288818+00:00
first discovered in case: 7
match confidence: 0.0
matches existing: false
source text: Engineer A applied their seal consistent with state law.
comment: Duty of a licensed engineer exercising responsible charge to apply their professional seal only to work products they have personally reviewed with sufficient depth and competence to take genuine professional responsibility for the content, and not to seal work generated by tools or processes they do not adequately understand or have not adequately verified.
subclass of: EthicalObligation
generated at time: 2026-06-03T14:05:12.288818+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Unfamiliar Tool Competence Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
confidence: 0.84
constraint type: competence
flexibility: soft
mitigation strategies: Disclose tool limitations and unfamiliarity to the client and seek consent before proceeding
mitigation strategies: Engage a colleague with relevant tool expertise to review outputs
mitigation strategies: Limit use of unfamiliar tools to non-critical or supplementary tasks until competence is established
mitigation strategies: Obtain training or experience with a new tool before using it for client deliverables
text references: Not being familiar with the full functionality of the AI software, including the accuracy and originality of AI-generated text
text references: The AI drafting software was new to the market and Engineer A had no previous experience with the tool.
violation impact: Deficient work products, public safety risk, regulatory non-compliance, and professional liability arising from reliance on tool outputs the engineer cannot adequately evaluate.
discovered in case: 7
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-03T14:06:33.588436+00:00
first discovered in case: 7
match confidence: 0.78
match reasoning: The existing Competence Constraint class covers boundaries defined by agent capabilities and technical limitations, which encompasses this scenario. The unfamiliar tool variant is a specific application of that general class. Matching as a variant at medium confidence while defining a more specific reusable subtype for unfamiliar tool deployment contexts.
matched ontology class: CompetenceConstraint
matched ontology label: Competence Constraint
matches existing: true
source text: The AI drafting software was new to the market and Engineer A had no previous experience with the tool.
comment: Competence constraint limiting an engineer's permissible use of a tool, technology, or method with which they lack sufficient experience or understanding, requiring that the engineer either acquire adequate competence before use, limit reliance on the tool's outputs, or obtain qualified assistance, so that professional work products meet required standards.
subclass of: CompetenceConstraint
subclass of: DefeasibleConstraint
scope note: [CompetenceConstraint] Boundaries defined by agent capabilities and technical limitations (Hallamaa & Kalliokoski 2022)
generated at time: 2026-06-03T14:06:33.588436+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Unverified Risk Concern State
type: Class
action constraints: Professional may not publicly assert the concern as a technical fact
action constraints: Professional should not suppress the concern entirely without further investigation
activation conditions: Insufficient analysis has been completed to characterize the risk as a factual finding
activation conditions: Professional identifies a potential risk through preliminary observation or intuition
activation conditions: Professional work has been paused or is incomplete
confidence: 0.82
obligation activation: Obligation to complete analysis before making public technical statements
obligation activation: Prudential disclosure to client as a matter of good practice
persistence type: non_inertial
principle transformation: Transforms general precautionary principles into a limited duty of prudent voluntary disclosure rather than mandatory reporting, because the concern has not yet risen to the level of a factual finding.
state category: risk
termination conditions: Additional analysis confirms or refutes the risk as a factual finding
termination conditions: Project is abandoned
termination conditions: Risk is quantified and documented in a professional report
text references: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development
text references: Engineer L's concern does not rise to the technical or moral level of fact
discovered in case: 8
discovered in pass: 1
discovered in section: discussion
first discovered at: 2026-06-04T09:59:35.891200+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development
comment: State in which a professional has a concern or suspicion about a potential risk but has not yet developed the analysis to a point where the concern constitutes a technical or factual finding. The concern is real but unquantified, creating an intermediate epistemic condition that does not yet trigger mandatory disclosure obligations but may support prudent voluntary disclosure.
subclass of: RiskState
generated at time: 2026-06-04T09:59:35.891200+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Concern Versus Fact Disclosure Constraint
type: Class
affected stakeholders: Client
affected stakeholders: Engineer
affected stakeholders: Public
affected stakeholders: Regulatory Authorities
confidence: 0.87
constraint type: ethical
flexibility: soft
mitigation strategies: Complete sufficient technical analysis before characterizing a concern as a factual finding
mitigation strategies: Disclose concerns as concerns rather than facts when prudent communication is warranted
mitigation strategies: Document the distinction between preliminary concerns and confirmed findings
mitigation strategies: Proceed to quantification promptly when a concern is identified
text references: The BER's view is that, while it might be prudent for Engineer L to inform Client X of their concerns, such disclosure is not required under the Code.
text references: the present case states that Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's 'concern' does not rise to the technical or moral level of 'fact,' and per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts.
violation impact: Premature disclosure of unsubstantiated concerns may mislead clients or public authorities, undermine the engineer's credibility, and violate the requirement that technical opinions be founded on knowledge of the facts.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:14.702097+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: the present case states that Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's 'concern' does not rise to the technical or moral level of 'fact,' and per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts.
comment: Ethical constraint limiting an engineer's disclosure obligations to findings that have reached the level of established fact supported by technical analysis. A preliminary concern or suspicion that has not yet been substantiated by sufficient analysis does not trigger the same mandatory disclosure obligations as a confirmed factual finding, and an engineer is not required under professional ethics codes to disclose unsubstantiated concerns, though prudent disclosure may be advisable.
subclass of: DefeasibleConstraint
subclass of: EthicalConstraint
generated at time: 2026-06-04T10:08:14.702097+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Concern Versus Fact Threshold Capability
type: Class
capability category: reasoning
confidence: 0.88
domain specificity: Environmental and public safety engineering contexts requiring graduated disclosure judgments
enables actions: Assess whether identified risks have been sufficiently analyzed to constitute facts
enables actions: Communicate the epistemic status of findings accurately to clients and authorities
enables actions: Determine when disclosure obligations are triggered versus when concerns remain preliminary
required for obligations: Concern Versus Fact Disclosure Threshold Obligation
required for obligations: Preliminary Risk Disclosure Obligation
required for obligations: Written Report Completeness Obligation
skill level: advanced
text references: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's 'concern' does not rise to the technical or moral level of 'fact,' and per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts.
text references: The key point of BER Case 07-6 is that information about the threat to the bird species is a 'fact' of the case.
discovered in case: 8
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-04T10:08:30.219581+00:00
first discovered in case: 8
match confidence: 0.0
matches existing: false
source text: Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks of potential stormwater runoff resulting from the new development. Thus, Engineer L's 'concern' does not rise to the technical or moral level of 'fact,' and per Code section II.3.b, engineers may express publicly technical opinions that are founded upon knowledge of the facts.
comment: Capability to distinguish between a preliminary professional concern that has not yet been substantiated by technical analysis and a finding that rises to the level of a demonstrable fact, and to calibrate disclosure obligations accordingly so that neither premature disclosure of unsubstantiated concerns nor suppression of confirmed findings occurs.
subclass of: Capability
generated at time: 2026-06-04T10:08:30.219581+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Responsible Charge Verification Obligation
type: Class
confidence: 0.91
derived from principle: Responsible Charge Integrity Principle
enforcement level: mandatory
monitoring criteria: Evidence of active engineer involvement in design and development process, not merely post-preparation document review
nspe reference: II.2.b
obligation type: competence
stakeholders affected: Client
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Engineer A did not maintain responsible charge in violation of licensure law which violates Code section III.8.a.
text references: Engineer A's oversight of engineering plans was inadequate, raising ethical concerns. AI-generated technical work requires at least the same level of scrutiny as human-created work.
text references: Reviewing drawings or documents after preparation without involvement in the design and development process does not satisfy the definition of Responsible Charge.
violation consequences: Violation of licensure law; potential public safety harm; disciplinary action; license revocation
discovered in case: 7
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-03T14:09:34.826300+00:00
first discovered in case: 7
match confidence: 0.82
match reasoning: This obligation is closely related to the already-extracted Responsible Charge Seal Obligation but emphasizes the verification and active-involvement dimension rather than the sealing act itself. It is a variant of that class focusing on the process of responsible charge rather than the sealing act.
matched ontology class: Responsible Charge Seal Obligation
matched ontology label: Responsible Charge Seal Obligation
matches existing: true
source text: Engineer A did not maintain responsible charge in violation of licensure law which violates Code section III.8.a.
comment: Duty of a licensed engineer in responsible charge to conduct a comprehensive, experience-based verification of all work products before sealing or submitting them, including active involvement in design and development rather than merely reviewing completed documents, so that the engineer can genuinely certify the work meets professional and safety standards.
subclass of: CompetenceObligation
generated at time: 2026-06-03T14:09:34.826300+00:00
was attributed to: Case 7 Extraction
was attributed to: claude-sonnet-4-6

Client Override Public Safety Reporting Obligation
type: Class
confidence: 0.91
derived from principle: Client Override Refusal Principle
enforcement level: mandatory
monitoring criteria: Documented evidence that the engineer notified the appropriate regulatory authority of the identified risk after the client refused to implement protective measures.
nspe reference: I.1, II.1.a, II.1.c, III.2.b
obligation type: reporting
stakeholders affected: Community relying on drinking water source
stakeholders affected: General public
stakeholders affected: Regulatory bodies
text references: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
text references: Engineer L notifies Client X of this risk, advising that additional protective measures should be considered, especially as local environmental standards require steps to safeguard public water sources.
violation consequences: Failure to report allows preventable public health harm to proceed, exposes the engineer to professional discipline and potential legal liability, and undermines the public trust in the engineering profession.
discovered in case: 8
discovered in pass: 2
discovered in section: facts
first discovered at: 2026-06-04T10:02:21.757544+00:00
first discovered in case: 8
match confidence: 0.72
match reasoning: The existing Post-Termination Environmental Risk Reporting Obligation addresses reporting after termination of the client relationship. This obligation arises while the client relationship is still active but the client has refused to act on identified risks. The concept is closely related but the triggering condition differs: here the obligation is activated by client refusal during an ongoing engagement rather than post-termination. A new class is warranted to capture the active-engagement client-override trigger.
matched ontology class: PostTerminationEnvironmentalRiskReportingObligation
matched ontology label: Post-Termination Environmental Risk Reporting Obligation
matches existing: true
source text: Client X insists on proceeding without added safeguards, stating that Client X will address any compliance issues later, if needed.
comment: Duty of an engineer to report identified risks to public health or safety to the appropriate regulatory or pollution control authority when the client refuses to implement recommended protective measures and insists on proceeding without adequate safeguards, placing the paramount duty to public welfare above the faithful agent duty to the client.
subclass of: ReportingObligation
scope note: [PostTermEnvRiskReportingObligation] Duty of an engineer to report environmental risks to a pollution-control authority after termination of the client relationship when the risk rises to a public-safety concern (NSPE Code §I.1, §II.1.a, §II.1.c). Derived from the paramount public-welfare principle.
generated at time: 2026-06-04T10:02:21.757544+00:00
was attributed to: Case 8 Extraction
was attributed to: claude-sonnet-4-6

Safety Disclosure Escalation Capability
type: Class
capability category: reasoning
confidence: 0.83
domain specificity: Engineering peer review under confidentiality agreements with safety code violation discovery
enables actions: Advise the responsible engineer of impending disclosure
enables actions: Determine when internal resolution has been exhausted
enables actions: Report safety code violations to appropriate authorities
enables actions: Sequence escalation steps in the correct order
required for obligations: Confidential Review Safety Disclosure Obligation
skill level: advanced
text references: Engineer A had an obligation to immediately discuss these issues with Engineer B in order to seek clarification and resolution.
text references: if Engineers A and B were unable to successfully resolve Engineer A's concerns, Engineer A had an obligation to first advise Engineer B that Engineer A had an obligation to inform the appropriate authorities, and then to so inform the appropriate authorities.
discovered in case: 15
discovered in pass: 2
discovered in section: discussion
first discovered at: 2026-06-02T20:00:55.491400+00:00
first discovered in case: 15
match confidence: 0.0
matches existing: false
source text: Engineer A had an obligation to immediately discuss these issues with Engineer B in order to seek clarification and resolution.
comment: Capability to recognize when internal resolution of a safety concern has failed and to escalate disclosure to appropriate regulatory authorities, including the ability to sequence escalation steps correctly by first advising the responsible engineer before notifying authorities.
subclass of: Capability
generated at time: 2026-06-02T20:00:55.491400+00:00
was attributed to: Case 15 Extraction
was attributed to: claude-sonnet-4-6