PASS 3: Temporal Dynamics
Case 94: Failure to Disclose Full Impact of Development
Timeline Overview
OWL-Time Temporal Structure 9 relations time: = w3.org/2006/time
Extracted Actions (4)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A agrees to be retained by Developer F for the major waterfront development project in City X, establishing a client relationship that will frame all subsequent professional obligations and potential conflicts of interest.
Temporal Marker: Pre-hearing; project initiation phase
Mental State: deliberate
Intended Outcome: Establish professional engagement to provide engineering services for the waterfront development project
Fulfills Obligations:
- Legitimate professional engagement within scope of engineering practice
- Providing technical expertise to support a development project through a lawful approval process
Guided By Principles:
- Engineers may be retained by private clients for projects requiring public approval
- Professional competence in accepting assignments within one's area of expertise
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A seeks professional engagement and revenue by accepting a prominent waterfront development project, likely viewing it as a career-enhancing opportunity while assuming standard client-advocate professional norms apply, without yet fully reckoning with the public-interest obligations that will later come into conflict.
Ethical Tension: Loyalty to a paying client and the legitimate pursuit of professional work versus the engineer's foundational obligation to protect public health, safety, and welfare — a tension embedded from the moment the retainer is accepted, since the client's interests may not fully align with the public's.
Learning Significance: Illustrates that ethical obligations do not begin at the moment of misconduct but are established at contract formation; students learn to identify how the structure of a client relationship can create downstream conflicts of interest and to ask 'what am I implicitly agreeing to disclose or withhold?' before accepting an engagement.
Stakes: Engineer A's professional independence and impartiality are immediately placed at risk; the public's right to complete information about a major land-use decision is indirectly at stake from the outset; Engineer A's license and reputation could ultimately be jeopardized if client loyalty overrides public-interest duties.
Decision Point: Yes - Story can branch here
- Accept the retainer but negotiate explicit terms requiring full disclosure of both positive and negative project impacts in any public testimony.
- Decline the retainer on the grounds that acting as both project designer and public hearing presenter creates an inherent advocacy conflict incompatible with objective engineering testimony.
- Accept the retainer for design services only and recommend that Developer F retain a separate, independent engineer to present findings to the Planning Board.
Narrative Role: inciting_incident
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Action_Accept_Developer_Retention",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Accept the retainer but negotiate explicit terms requiring full disclosure of both positive and negative project impacts in any public testimony.",
"Decline the retainer on the grounds that acting as both project designer and public hearing presenter creates an inherent advocacy conflict incompatible with objective engineering testimony.",
"Accept the retainer for design services only and recommend that Developer F retain a separate, independent engineer to present findings to the Planning Board."
],
"proeth-scenario:characterMotivation": "Engineer A seeks professional engagement and revenue by accepting a prominent waterfront development project, likely viewing it as a career-enhancing opportunity while assuming standard client-advocate professional norms apply, without yet fully reckoning with the public-interest obligations that will later come into conflict.",
"proeth-scenario:consequencesIfAlternative": [
"Negotiating disclosure terms upfront would align the client relationship with NSPE Code obligations from the start, likely preventing the later omission entirely, though Developer F might seek a more compliant engineer.",
"Declining the retainer eliminates the conflict entirely but costs Engineer A the project; it signals strong professional integrity and could attract clients who value ethical practice.",
"Separating design from public testimony roles would preserve objectivity at the hearing, protect public interest, and reduce Engineer A\u0027s personal ethical exposure, though it adds project cost and complexity for Developer F."
],
"proeth-scenario:decisionSignificance": "Illustrates that ethical obligations do not begin at the moment of misconduct but are established at contract formation; students learn to identify how the structure of a client relationship can create downstream conflicts of interest and to ask \u0027what am I implicitly agreeing to disclose or withhold?\u0027 before accepting an engagement.",
"proeth-scenario:ethicalTension": "Loyalty to a paying client and the legitimate pursuit of professional work versus the engineer\u0027s foundational obligation to protect public health, safety, and welfare \u2014 a tension embedded from the moment the retainer is accepted, since the client\u0027s interests may not fully align with the public\u0027s.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "inciting_incident",
"proeth-scenario:stakes": "Engineer A\u0027s professional independence and impartiality are immediately placed at risk; the public\u0027s right to complete information about a major land-use decision is indirectly at stake from the outset; Engineer A\u0027s license and reputation could ultimately be jeopardized if client loyalty overrides public-interest duties.",
"proeth:description": "Engineer A agrees to be retained by Developer F for the major waterfront development project in City X, establishing a client relationship that will frame all subsequent professional obligations and potential conflicts of interest.",
"proeth:foreseenUnintendedEffects": [
"Client relationship may create pressure to frame public presentations favorably toward developer interests",
"Retention by a private developer may create tension with obligations to public bodies and the general public"
],
"proeth:fulfillsObligation": [
"Legitimate professional engagement within scope of engineering practice",
"Providing technical expertise to support a development project through a lawful approval process"
],
"proeth:guidedByPrinciple": [
"Engineers may be retained by private clients for projects requiring public approval",
"Professional competence in accepting assignments within one\u0027s area of expertise"
],
"proeth:hasAgent": "Engineer A (Consulting Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client advocacy vs. public interest obligations",
"proeth:resolutionReasoning": "Engineer A accepted retention, implicitly agreeing to advocate for the project while remaining bound by independent ethical obligations to the public and the Planning Board"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Establish professional engagement to provide engineering services for the waterfront development project",
"proeth:requiresCapability": [
"Waterfront development engineering expertise",
"Environmental impact assessment",
"Public hearing presentation skills",
"Knowledge of planning and regulatory approval processes"
],
"proeth:temporalMarker": "Pre-hearing; project initiation phase",
"proeth:withinCompetence": true,
"rdfs:label": "Accept Developer Retention"
}
Description: During the public hearing, Engineer A deliberately chooses to structure the presentation to highlight the environmental benefits of converting the waterfront from an industrial facility to parkland, affirmatively selecting a positive framing for the project's environmental profile.
Temporal Marker: During public hearing before City Planning Board; presentation phase
Mental State: deliberate
Intended Outcome: Persuade the City Planning Board of the environmental merits of the waterfront development project to support approval
Fulfills Obligations:
- Provided accurate information about the environmental benefits of parkland conversion
- Responded to the client's interest in presenting the project favorably
Guided By Principles:
- Engineers shall be objective and truthful in professional reports and public statements
- Engineers shall not suppress or distort technical data to favor a client
- Public bodies rely on engineers for complete technical information to make sound policy decisions
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A, acting as an advocate for Developer F's project, consciously or habitually defaults to a persuasion frame — presenting the project in its most favorable light to maximize approval chances — conflating the role of engineering expert with the role of project advocate, and rationalizing that emphasizing genuine environmental benefits is not dishonest.
Ethical Tension: The legitimate value of effective, organized communication (choosing what to lead with) conflicts with the engineer's duty to provide objective, balanced, and complete information to a public regulatory body; the line between strategic emphasis and material omission is central to the tension.
Learning Significance: Teaches students that selective truthfulness — presenting only accurate but incomplete information — can be as ethically problematic as outright falsehood, particularly when an engineer testifies before a public body; highlights the distinction between an attorney's advocacy role and an engineer's duty of candor to public institutions.
Stakes: The Planning Board's ability to make a fully informed land-use decision is compromised; Engineer A begins constructing a misleading narrative that, even if each individual claim is true, produces a false overall impression; public trust in engineering expertise at civic proceedings is at risk.
Decision Point: Yes - Story can branch here
- Structure the presentation as a balanced environmental impact summary, leading with benefits but explicitly flagging known negative impacts and proposed mitigations in the same presentation.
- Present only the design and engineering specifications within Engineer A's direct expertise, explicitly deferring environmental trade-off judgments to independent environmental review.
- Disclose to the Planning Board at the outset of testimony that Engineer A is retained by the developer, framing all subsequent information within that disclosed advocacy context so the Board can calibrate accordingly.
Narrative Role: rising_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Action_Frame_Presentation_Around_Benefits",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Structure the presentation as a balanced environmental impact summary, leading with benefits but explicitly flagging known negative impacts and proposed mitigations in the same presentation.",
"Present only the design and engineering specifications within Engineer A\u0027s direct expertise, explicitly deferring environmental trade-off judgments to independent environmental review.",
"Disclose to the Planning Board at the outset of testimony that Engineer A is retained by the developer, framing all subsequent information within that disclosed advocacy context so the Board can calibrate accordingly."
],
"proeth-scenario:characterMotivation": "Engineer A, acting as an advocate for Developer F\u0027s project, consciously or habitually defaults to a persuasion frame \u2014 presenting the project in its most favorable light to maximize approval chances \u2014 conflating the role of engineering expert with the role of project advocate, and rationalizing that emphasizing genuine environmental benefits is not dishonest.",
"proeth-scenario:consequencesIfAlternative": [
"A balanced presentation would fulfill Engineer A\u0027s public-interest obligations, likely strengthen long-term credibility with the Board, and reduce ethical and legal exposure, though it might displease Developer F if negative impacts receive prominent attention.",
"Limiting testimony to design specifications keeps Engineer A within a defensible scope of expertise and avoids the selective-emphasis problem, but may leave the Board without needed engineering context on environmental trade-offs.",
"Proactive disclosure of the client relationship, while not resolving the omission problem, at least ensures the Board can weigh testimony appropriately and demonstrates a baseline of transparency that partially mitigates the advocacy-versus-objectivity tension."
],
"proeth-scenario:decisionSignificance": "Teaches students that selective truthfulness \u2014 presenting only accurate but incomplete information \u2014 can be as ethically problematic as outright falsehood, particularly when an engineer testifies before a public body; highlights the distinction between an attorney\u0027s advocacy role and an engineer\u0027s duty of candor to public institutions.",
"proeth-scenario:ethicalTension": "The legitimate value of effective, organized communication (choosing what to lead with) conflicts with the engineer\u0027s duty to provide objective, balanced, and complete information to a public regulatory body; the line between strategic emphasis and material omission is central to the tension.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "rising_action",
"proeth-scenario:stakes": "The Planning Board\u0027s ability to make a fully informed land-use decision is compromised; Engineer A begins constructing a misleading narrative that, even if each individual claim is true, produces a false overall impression; public trust in engineering expertise at civic proceedings is at risk.",
"proeth:description": "During the public hearing, Engineer A deliberately chooses to structure the presentation to highlight the environmental benefits of converting the waterfront from an industrial facility to parkland, affirmatively selecting a positive framing for the project\u0027s environmental profile.",
"proeth:foreseenUnintendedEffects": [
"Selective emphasis on benefits creates an incomplete picture for the Planning Board",
"Board members may form decisions without full awareness of negative environmental tradeoffs",
"Other witnesses may need to supply omitted information, potentially undermining project credibility"
],
"proeth:fulfillsObligation": [
"Provided accurate information about the environmental benefits of parkland conversion",
"Responded to the client\u0027s interest in presenting the project favorably"
],
"proeth:guidedByPrinciple": [
"Engineers shall be objective and truthful in professional reports and public statements",
"Engineers shall not suppress or distort technical data to favor a client",
"Public bodies rely on engineers for complete technical information to make sound policy decisions"
],
"proeth:hasAgent": "Engineer A (Consulting Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Client advocacy vs. complete objective disclosure",
"proeth:resolutionReasoning": "Engineer A resolved the conflict in favor of client framing, relying implicitly on the absence of a direct question and the subsequent testimony of other witnesses as justification, but the Discussion section raises whether this satisfies the \u0027relevant and pertinent information\u0027 disclosure standard"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Persuade the City Planning Board of the environmental merits of the waterfront development project to support approval",
"proeth:requiresCapability": [
"Environmental impact analysis and communication",
"Public hearing presentation and testimony",
"Technical judgment about project impacts"
],
"proeth:temporalMarker": "During public hearing before City Planning Board; presentation phase",
"proeth:violatesObligation": [
"Obligation to issue public statements in an objective and truthful manner",
"Obligation to disclose all relevant and pertinent information to a public body",
"Obligation to hold public health, safety, and welfare paramount over client interests"
],
"proeth:withinCompetence": true,
"rdfs:label": "Frame Presentation Around Benefits"
}
Description: Engineer A, fully aware that the anticipated commercial development would increase traffic, air pollution, and noise pollution, makes a conscious decision not to volunteer this information to the City Planning Board during the presentation or Q&A, despite its direct relevance to the project's environmental profile.
Temporal Marker: During public hearing; throughout presentation and Q&A phase
Mental State: deliberate
Intended Outcome: Avoid introducing negative information that could jeopardize project approval, while remaining technically truthful about what was stated
Fulfills Obligations:
- Did not make affirmatively false statements
- Maintained conditional willingness to answer honestly if directly questioned
Guided By Principles:
- Engineers testifying before public bodies bear heightened obligations to completeness given their effect on public policy
- Silence on material facts known to the engineer may constitute a form of misrepresentation in a public hearing context
- The public and public bodies rely on engineers for technical information they cannot independently assess
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A consciously withholds known negative impact data, motivated by a combination of client loyalty (Developer F's project approval depends on a favorable hearing), possible rationalization that the Board can ask if they want to know, and perhaps a self-serving avoidance of information that would complicate Engineer A's own professional position as the project's designer — illustrating how conflicts of interest distort judgment.
Ethical Tension: The duty to serve the client's immediate interests conflicts directly with NSPE Code Canon obligations to hold public health, safety, and welfare paramount and to be objective and truthful in professional reports and public statements; the omission also implicates duties of honesty and non-deception that apply regardless of whether a question is asked.
Learning Significance: This is the ethical core of the case and the primary teaching moment: engineers testifying before public bodies bear an affirmative duty of disclosure for material information — not merely a duty to answer questions honestly — because the public and regulatory bodies depend on engineering expertise precisely to surface information they do not know to ask about; silence on known material facts is an ethical violation even absent a direct lie.
Stakes: Immediate stakes include the Planning Board making a flawed land-use decision affecting City X residents' quality of life; longer-term stakes include Engineer A's professional license, reputation, and potential liability; systemic stakes involve erosion of public trust in engineers as honest brokers of technical information at civic proceedings.
Decision Point: Yes - Story can branch here
- Voluntarily disclose all known negative impacts — traffic, air, and noise pollution increases — during the presentation, accompanied by proposed mitigation strategies, fulfilling the affirmative duty of candor.
- Pause the presentation and inform the Board that a complete environmental impact analysis including negative factors is available and offer to provide it, even if not originally planned for the hearing.
- Withdraw from presenting at the public hearing and advise Developer F to commission an independent environmental impact assessment before proceeding, citing Engineer A's inability to provide objective testimony as the retained designer.
Narrative Role: climax
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Action_Omit_Known_Negative_Impacts",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Voluntarily disclose all known negative impacts \u2014 traffic, air, and noise pollution increases \u2014 during the presentation, accompanied by proposed mitigation strategies, fulfilling the affirmative duty of candor.",
"Pause the presentation and inform the Board that a complete environmental impact analysis including negative factors is available and offer to provide it, even if not originally planned for the hearing.",
"Withdraw from presenting at the public hearing and advise Developer F to commission an independent environmental impact assessment before proceeding, citing Engineer A\u0027s inability to provide objective testimony as the retained designer."
],
"proeth-scenario:characterMotivation": "Engineer A consciously withholds known negative impact data, motivated by a combination of client loyalty (Developer F\u0027s project approval depends on a favorable hearing), possible rationalization that the Board can ask if they want to know, and perhaps a self-serving avoidance of information that would complicate Engineer A\u0027s own professional position as the project\u0027s designer \u2014 illustrating how conflicts of interest distort judgment.",
"proeth-scenario:consequencesIfAlternative": [
"Voluntary disclosure satisfies Engineer A\u0027s ethical obligations under the NSPE Code, enables informed Board deliberation, and \u2014 as the BER cases suggest \u2014 likely would not have doomed the project since other witnesses raised the same concerns anyway, while protecting Engineer A\u0027s professional standing.",
"Offering to provide complete impact data mid-hearing is a partial remedy that demonstrates good faith and could correct the omission in real time, though it may raise questions about why the information was not included originally.",
"Withdrawing from testimony is the most protective action for Engineer A\u0027s integrity but effectively abandons Developer F and may not be practically feasible mid-process; it would, however, prevent Engineer A from being the source of misleading incomplete testimony."
],
"proeth-scenario:decisionSignificance": "This is the ethical core of the case and the primary teaching moment: engineers testifying before public bodies bear an affirmative duty of disclosure for material information \u2014 not merely a duty to answer questions honestly \u2014 because the public and regulatory bodies depend on engineering expertise precisely to surface information they do not know to ask about; silence on known material facts is an ethical violation even absent a direct lie.",
"proeth-scenario:ethicalTension": "The duty to serve the client\u0027s immediate interests conflicts directly with NSPE Code Canon obligations to hold public health, safety, and welfare paramount and to be objective and truthful in professional reports and public statements; the omission also implicates duties of honesty and non-deception that apply regardless of whether a question is asked.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "climax",
"proeth-scenario:stakes": "Immediate stakes include the Planning Board making a flawed land-use decision affecting City X residents\u0027 quality of life; longer-term stakes include Engineer A\u0027s professional license, reputation, and potential liability; systemic stakes involve erosion of public trust in engineers as honest brokers of technical information at civic proceedings.",
"proeth:description": "Engineer A, fully aware that the anticipated commercial development would increase traffic, air pollution, and noise pollution, makes a conscious decision not to volunteer this information to the City Planning Board during the presentation or Q\u0026A, despite its direct relevance to the project\u0027s environmental profile.",
"proeth:foreseenUnintendedEffects": [
"Planning Board makes decisions without complete environmental impact information from the primary project engineer",
"Public interest may be harmed if the Board approves a project without understanding its full environmental tradeoffs",
"Other engineers subsequently testify about omitted impacts, potentially signaling Engineer A\u0027s selective disclosure"
],
"proeth:fulfillsObligation": [
"Did not make affirmatively false statements",
"Maintained conditional willingness to answer honestly if directly questioned"
],
"proeth:guidedByPrinciple": [
"Engineers testifying before public bodies bear heightened obligations to completeness given their effect on public policy",
"Silence on material facts known to the engineer may constitute a form of misrepresentation in a public hearing context",
"The public and public bodies rely on engineers for technical information they cannot independently assess"
],
"proeth:hasAgent": "Engineer A (Consulting Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Non-disclosure to protect client vs. complete disclosure to serve public interest",
"proeth:resolutionReasoning": "Engineer A resolved the conflict by treating the absence of a direct question as sufficient justification for non-disclosure, but the Discussion section frames the central ethical question as whether the omitted information constitutes \u0027relevant and pertinent\u0027 information that required proactive disclosure regardless of whether it was solicited"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Avoid introducing negative information that could jeopardize project approval, while remaining technically truthful about what was stated",
"proeth:requiresCapability": [
"Environmental impact assessment",
"Professional judgment about materiality and relevance of technical information",
"Public hearing testimony ethics"
],
"proeth:temporalMarker": "During public hearing; throughout presentation and Q\u0026A phase",
"proeth:violatesObligation": [
"Obligation to disclose all relevant and pertinent information to a public body",
"Obligation to be objective and complete in public technical testimony",
"Obligation to hold public health, safety, and welfare paramount",
"Obligation not to suppress or withhold technical data that affects public policy decisions"
],
"proeth:withinCompetence": true,
"rdfs:label": "Omit Known Negative Impacts"
}
Description: Engineer A internally resolves that, if directly questioned by the City Planning Board about traffic, air, or noise pollution impacts, honest and complete testimony would be provided, but does not translate this conditional commitment into proactive disclosure.
Temporal Marker: During public hearing Q&A phase
Mental State: deliberate
Intended Outcome: Preserve personal ethical integrity by committing to truthful answers if asked, while avoiding proactive disclosure that could harm the client's approval prospects
Fulfills Obligations:
- Maintained commitment to truthful testimony if directly questioned
- Did not prepare or intend to give false answers
Guided By Principles:
- Honesty in engineering testimony encompasses both reactive truthfulness and proactive completeness
- A public body's inability to ask the right question does not relieve the engineer of the obligation to supply material technical information
Required Capabilities:
Scenario Metadata
Pedagogical context for interactive teaching scenariosCharacter Motivation: Engineer A constructs a conditional ethical commitment — 'I will be honest if asked' — as a psychological mechanism to preserve a self-image of integrity while avoiding the discomfort and client-relations risk of proactive disclosure; this rationalization allows Engineer A to feel compliant with honesty norms without actually fulfilling the affirmative disclosure duty that engineering ethics requires.
Ethical Tension: A reactive honesty norm (answering questions truthfully when asked) conflicts with a proactive candor norm (volunteering material information relevant to public welfare without waiting to be asked); the tension exposes a common but flawed mental model in which engineers treat public testimony like cross-examination rather than like a professional report with affirmative disclosure obligations.
Learning Significance: Teaches students to recognize the 'conditional honesty' rationalization as an insufficient ethical standard for engineers in public-interest contexts; draws a critical distinction between passive non-deception and active candor, and illustrates how the structure of public hearings — where Board members cannot ask about what they do not know they should ask — places the disclosure burden squarely on the expert witness.
Stakes: Engineer A's internal ethical reasoning is revealed as inadequate, setting up the case's analytical conclusion; the gap between Engineer A's self-assessed compliance and actual ethical obligation is the gap that causes harm — the Board proceeds without full information not because they refused it but because they did not know to request it.
Decision Point: Yes - Story can branch here
- Translate the conditional commitment into an unconditional one by proactively raising the pollution impacts before leaving the podium, without waiting for questions that may never come.
- After the hearing, submit a written supplement to the Planning Board's record disclosing the known negative impacts, acknowledging they were not addressed in oral testimony.
- Consult with a professional ethics advisor or NSPE Board of Ethical Review guidance before the hearing to determine whether the planned presentation structure meets disclosure obligations, and adjust accordingly.
Narrative Role: falling_action
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Action_Conditionally_Commit_to_Honest_Answers",
"@type": "proeth:Action",
"proeth-scenario:alternativeActions": [
"Translate the conditional commitment into an unconditional one by proactively raising the pollution impacts before leaving the podium, without waiting for questions that may never come.",
"After the hearing, submit a written supplement to the Planning Board\u0027s record disclosing the known negative impacts, acknowledging they were not addressed in oral testimony.",
"Consult with a professional ethics advisor or NSPE Board of Ethical Review guidance before the hearing to determine whether the planned presentation structure meets disclosure obligations, and adjust accordingly."
],
"proeth-scenario:characterMotivation": "Engineer A constructs a conditional ethical commitment \u2014 \u0027I will be honest if asked\u0027 \u2014 as a psychological mechanism to preserve a self-image of integrity while avoiding the discomfort and client-relations risk of proactive disclosure; this rationalization allows Engineer A to feel compliant with honesty norms without actually fulfilling the affirmative disclosure duty that engineering ethics requires.",
"proeth-scenario:consequencesIfAlternative": [
"Proactive disclosure at the podium fully resolves the ethical violation in real time; it may create friction with Developer F but fulfills Engineer A\u0027s paramount public-welfare duty and is consistent with the BER\u0027s eventual conclusion about what was required.",
"A post-hearing written supplement partially remedies the omission and creates a record of good faith correction, though the Board\u0027s initial deliberations may already have been influenced by incomplete information.",
"Pre-hearing ethics consultation would have surfaced the disclosure obligation before any violation occurred, representing the ideal preventive approach and modeling the professional habit of seeking guidance on ambiguous ethical situations before acting."
],
"proeth-scenario:decisionSignificance": "Teaches students to recognize the \u0027conditional honesty\u0027 rationalization as an insufficient ethical standard for engineers in public-interest contexts; draws a critical distinction between passive non-deception and active candor, and illustrates how the structure of public hearings \u2014 where Board members cannot ask about what they do not know they should ask \u2014 places the disclosure burden squarely on the expert witness.",
"proeth-scenario:ethicalTension": "A reactive honesty norm (answering questions truthfully when asked) conflicts with a proactive candor norm (volunteering material information relevant to public welfare without waiting to be asked); the tension exposes a common but flawed mental model in which engineers treat public testimony like cross-examination rather than like a professional report with affirmative disclosure obligations.",
"proeth-scenario:isDecisionPoint": true,
"proeth-scenario:narrativeRole": "falling_action",
"proeth-scenario:stakes": "Engineer A\u0027s internal ethical reasoning is revealed as inadequate, setting up the case\u0027s analytical conclusion; the gap between Engineer A\u0027s self-assessed compliance and actual ethical obligation is the gap that causes harm \u2014 the Board proceeds without full information not because they refused it but because they did not know to request it.",
"proeth:description": "Engineer A internally resolves that, if directly questioned by the City Planning Board about traffic, air, or noise pollution impacts, honest and complete testimony would be provided, but does not translate this conditional commitment into proactive disclosure.",
"proeth:foreseenUnintendedEffects": [
"The conditional commitment provides Engineer A with a subjective ethical justification for non-disclosure that may not satisfy objective professional standards",
"The Board, not knowing what questions to ask, may never trigger the disclosure Engineer A is prepared to make"
],
"proeth:fulfillsObligation": [
"Maintained commitment to truthful testimony if directly questioned",
"Did not prepare or intend to give false answers"
],
"proeth:guidedByPrinciple": [
"Honesty in engineering testimony encompasses both reactive truthfulness and proactive completeness",
"A public body\u0027s inability to ask the right question does not relieve the engineer of the obligation to supply material technical information"
],
"proeth:hasAgent": "Engineer A (Consulting Engineer)",
"proeth:hasCompetingPriorities": {
"@type": "proeth:CompetingPriorities",
"proeth:priorityConflict": "Reactive honesty vs. proactive completeness",
"proeth:resolutionReasoning": "Engineer A drew the boundary of the disclosure obligation at direct questioning, treating reactive honesty as sufficient; the Discussion section challenges this by asking whether the omitted information was \u0027relevant and pertinent\u0027 such that proactive disclosure was required"
},
"proeth:hasMentalState": "deliberate",
"proeth:intendedOutcome": "Preserve personal ethical integrity by committing to truthful answers if asked, while avoiding proactive disclosure that could harm the client\u0027s approval prospects",
"proeth:requiresCapability": [
"Professional judgment about disclosure obligations",
"Technical knowledge of project impacts",
"Public hearing testimony ethics"
],
"proeth:temporalMarker": "During public hearing Q\u0026A phase",
"proeth:violatesObligation": [
"Obligation to proactively disclose relevant and pertinent information to a public body",
"Obligation to ensure the public body has the information needed to make sound decisions, not merely to answer questions honestly when asked"
],
"proeth:withinCompetence": true,
"rdfs:label": "Conditionally Commit to Honest Answers"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changesDescription: Engineer A is formally retained by Developer F for the waterfront development project in City X, establishing a professional-client relationship with attendant duties and obligations.
Temporal Marker: Project initiation, prior to public hearing
Activates Constraints:
- Client_Loyalty_Constraint
- Professional_Competence_Constraint
- Conflict_Of_Interest_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A likely feels professional confidence and perhaps commercial satisfaction; Developer F feels reassured by securing technical expertise; the public is as yet unaware and unaffected emotionally
- engineer_a: Assumes professional obligations that constrain future conduct; reputation now tied to project outcomes
- developer_f: Gains technical credibility and advocacy for the project; implicitly expects Engineer A to advance project interests
- city_planning_board: Will rely on Engineer A's professional judgment as a credentialed expert
- public: Indirectly affected as the retained engineer will shape what information reaches decision-makers
Learning Moment: The moment of retention is not ethically neutral — it activates a full suite of professional obligations, including duties that may conflict with the client's preferences. Students should understand that accepting a commission means accepting responsibilities to third parties and the public, not just the paying client.
Ethical Implications: Reveals the foundational tension in engineering practice between serving a paying client and upholding broader public welfare obligations; establishes that professional ethics are not suspended by contractual relationships
- When an engineer accepts a client engagement, to whom does the engineer owe primary loyalty — the client, the public, or both?
- Should Engineer A have negotiated explicit terms about disclosure obligations before accepting the retention?
- Does the source of payment (Developer F) inherently compromise Engineer A's objectivity, and if so, how should this be managed?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Event_Engineer_Retention_Established",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"When an engineer accepts a client engagement, to whom does the engineer owe primary loyalty \u2014 the client, the public, or both?",
"Should Engineer A have negotiated explicit terms about disclosure obligations before accepting the retention?",
"Does the source of payment (Developer F) inherently compromise Engineer A\u0027s objectivity, and if so, how should this be managed?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "Engineer A likely feels professional confidence and perhaps commercial satisfaction; Developer F feels reassured by securing technical expertise; the public is as yet unaware and unaffected emotionally",
"proeth-scenario:ethicalImplications": "Reveals the foundational tension in engineering practice between serving a paying client and upholding broader public welfare obligations; establishes that professional ethics are not suspended by contractual relationships",
"proeth-scenario:learningMoment": "The moment of retention is not ethically neutral \u2014 it activates a full suite of professional obligations, including duties that may conflict with the client\u0027s preferences. Students should understand that accepting a commission means accepting responsibilities to third parties and the public, not just the paying client.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"city_planning_board": "Will rely on Engineer A\u0027s professional judgment as a credentialed expert",
"developer_f": "Gains technical credibility and advocacy for the project; implicitly expects Engineer A to advance project interests",
"engineer_a": "Assumes professional obligations that constrain future conduct; reputation now tied to project outcomes",
"public": "Indirectly affected as the retained engineer will shape what information reaches decision-makers"
},
"proeth:activatesConstraint": [
"Client_Loyalty_Constraint",
"Professional_Competence_Constraint",
"Conflict_Of_Interest_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/94#Action_Accept_Developer_Retention",
"proeth:causesStateChange": "Engineer A transitions from uninvolved party to retained professional with fiduciary and ethical duties to both Developer F and the broader public",
"proeth:createsObligation": [
"Duty_To_Serve_Client_Competently",
"Duty_To_Prioritize_Public_Safety_Over_Client_Interest",
"Duty_To_Disclose_Pertinent_Information",
"Duty_To_Avoid_Misleading_Representations"
],
"proeth:description": "Engineer A is formally retained by Developer F for the waterfront development project in City X, establishing a professional-client relationship with attendant duties and obligations.",
"proeth:emergencyStatus": "routine",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Project initiation, prior to public hearing",
"proeth:urgencyLevel": "low",
"rdfs:label": "Engineer Retention Established"
}
Description: The City Planning Board convenes a public hearing at which Engineer A is scheduled to present the proposed waterfront development design, creating a formal civic forum for expert testimony.
Temporal Marker: After project design phase; before Engineer A's presentation
Activates Constraints:
- Public_Forum_Honesty_Constraint
- Expert_Witness_Integrity_Constraint
- Duty_To_Inform_Public_Deliberation_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel the pressure of a public stage; Developer F anticipates a favorable outcome; board members approach the hearing with civic duty; community members may feel curiosity, hope, or apprehension about waterfront changes
- engineer_a: Now operates in a public forum where statements are on record and subject to scrutiny; ethical obligations are heightened
- developer_f: Project fate now subject to public deliberation; outcome uncertain
- city_planning_board: Assumes responsibility for fair evaluation of all testimony including expert claims
- public_community: Gains formal opportunity to participate in decisions affecting their environment
Learning Moment: Public hearings elevate the ethical stakes for engineers: testimony before a regulatory body carries special weight because decision-makers and the public rely on expert candor to make informed choices. The public forum transforms professional obligations from private to civic.
Ethical Implications: Highlights that engineers functioning as expert witnesses in public proceedings serve a quasi-public role; their selective presentation of facts can distort democratic deliberation and undermine informed consent of governing bodies
- Does testifying at a public hearing impose different or stronger disclosure obligations than advising a client privately?
- How does the presence of a civic audience change what 'complete' information means for an engineer's presentation?
- Who bears responsibility for ensuring the Planning Board receives all material information — the engineer, the board members, or both?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Event_Public_Hearing_Convened",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Does testifying at a public hearing impose different or stronger disclosure obligations than advising a client privately?",
"How does the presence of a civic audience change what \u0027complete\u0027 information means for an engineer\u0027s presentation?",
"Who bears responsibility for ensuring the Planning Board receives all material information \u2014 the engineer, the board members, or both?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer A may feel the pressure of a public stage; Developer F anticipates a favorable outcome; board members approach the hearing with civic duty; community members may feel curiosity, hope, or apprehension about waterfront changes",
"proeth-scenario:ethicalImplications": "Highlights that engineers functioning as expert witnesses in public proceedings serve a quasi-public role; their selective presentation of facts can distort democratic deliberation and undermine informed consent of governing bodies",
"proeth-scenario:learningMoment": "Public hearings elevate the ethical stakes for engineers: testimony before a regulatory body carries special weight because decision-makers and the public rely on expert candor to make informed choices. The public forum transforms professional obligations from private to civic.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"city_planning_board": "Assumes responsibility for fair evaluation of all testimony including expert claims",
"developer_f": "Project fate now subject to public deliberation; outcome uncertain",
"engineer_a": "Now operates in a public forum where statements are on record and subject to scrutiny; ethical obligations are heightened",
"public_community": "Gains formal opportunity to participate in decisions affecting their environment"
},
"proeth:activatesConstraint": [
"Public_Forum_Honesty_Constraint",
"Expert_Witness_Integrity_Constraint",
"Duty_To_Inform_Public_Deliberation_Constraint"
],
"proeth:causesStateChange": "The project moves from private planning into public regulatory scrutiny; Engineer A\u0027s professional conduct becomes subject to civic accountability and public record",
"proeth:createsObligation": [
"Duty_To_Present_Complete_And_Accurate_Information_To_Board",
"Duty_To_Volunteer_Material_Information_Affecting_Public_Interest",
"Duty_To_Represent_Engineering_Profession_With_Integrity"
],
"proeth:description": "The City Planning Board convenes a public hearing at which Engineer A is scheduled to present the proposed waterfront development design, creating a formal civic forum for expert testimony.",
"proeth:emergencyStatus": "routine",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "After project design phase; before Engineer A\u0027s presentation",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Public Hearing Convened"
}
Description: No members of the City Planning Board specifically question Engineer A about traffic, air, or noise pollution impacts during or after the presentation, leaving the omissions unchallenged from the board's side.
Temporal Marker: During public hearing, immediately following Engineer A's presentation
Activates Constraints:
- Proactive_Disclosure_Constraint
- Non_Deception_By_Omission_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel relief or false validation that the omissions went unnoticed; board members are unaware of their own informational deficit; the public present may sense something is missing but lack standing to intervene
- engineer_a: Silence creates a false sense that omission was acceptable; moral responsibility deepens
- city_planning_board: Proceeds under a materially incomplete factual record, compromising quality of deliberation
- developer_f: Benefits from unchallenged favorable presentation
- public_community: Interests are unrepresented in the expert testimony phase; decisions may be made without full awareness of environmental tradeoffs
Learning Moment: The absence of a question does not create permission for an engineer to withhold material information. Engineers cannot treat silence as implicit consent to incomplete disclosure. The proactive duty to inform is not contingent on being asked.
Ethical Implications: Exposes the ethical asymmetry between expert knowledge and lay reliance: the more a decision-maker depends on an expert, the stronger the expert's affirmative duty to disclose; silence by the uninformed cannot waive the expert's obligation
- Is an engineer ethically absolved of a disclosure obligation simply because no one asked the right question?
- What does 'reliance' by a regulatory body on expert testimony imply about the expert's disclosure duties?
- How does the board's silence change — if at all — Engineer A's moral responsibility for the omission?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Event_Board_Members_Silent_On_Impacts",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"Is an engineer ethically absolved of a disclosure obligation simply because no one asked the right question?",
"What does \u0027reliance\u0027 by a regulatory body on expert testimony imply about the expert\u0027s disclosure duties?",
"How does the board\u0027s silence change \u2014 if at all \u2014 Engineer A\u0027s moral responsibility for the omission?"
],
"proeth-scenario:dramaticTension": "medium",
"proeth-scenario:emotionalImpact": "Engineer A may feel relief or false validation that the omissions went unnoticed; board members are unaware of their own informational deficit; the public present may sense something is missing but lack standing to intervene",
"proeth-scenario:ethicalImplications": "Exposes the ethical asymmetry between expert knowledge and lay reliance: the more a decision-maker depends on an expert, the stronger the expert\u0027s affirmative duty to disclose; silence by the uninformed cannot waive the expert\u0027s obligation",
"proeth-scenario:learningMoment": "The absence of a question does not create permission for an engineer to withhold material information. Engineers cannot treat silence as implicit consent to incomplete disclosure. The proactive duty to inform is not contingent on being asked.",
"proeth-scenario:narrativePacing": "slow_burn",
"proeth-scenario:stakeholderConsequences": {
"city_planning_board": "Proceeds under a materially incomplete factual record, compromising quality of deliberation",
"developer_f": "Benefits from unchallenged favorable presentation",
"engineer_a": "Silence creates a false sense that omission was acceptable; moral responsibility deepens",
"public_community": "Interests are unrepresented in the expert testimony phase; decisions may be made without full awareness of environmental tradeoffs"
},
"proeth:activatesConstraint": [
"Proactive_Disclosure_Constraint",
"Non_Deception_By_Omission_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/94#Action_Omit_Known_Negative_Impacts",
"proeth:causesStateChange": "The absence of board questioning does not relieve Engineer A of disclosure duty; the information gap widens and the board proceeds toward deliberation with an incomplete factual record",
"proeth:createsObligation": [
"Heightened_Duty_To_Volunteer_Omitted_Information",
"Duty_Not_To_Exploit_Board_Silence_As_License_For_Continued_Omission"
],
"proeth:description": "No members of the City Planning Board specifically question Engineer A about traffic, air, or noise pollution impacts during or after the presentation, leaving the omissions unchallenged from the board\u0027s side.",
"proeth:emergencyStatus": "medium",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "During public hearing, immediately following Engineer A\u0027s presentation",
"proeth:urgencyLevel": "medium",
"rdfs:label": "Board Members Silent On Impacts"
}
Description: After Engineer A's testimony, other witnesses including other engineers testify before the Planning Board specifically about traffic, noise, and air pollution concerns associated with the development project.
Temporal Marker: Later in the same public hearing, after Engineer A's presentation
Activates Constraints:
- Retroactive_Correction_Obligation_Constraint
- Professional_Integrity_Under_Scrutiny_Constraint
- Duty_Not_To_Allow_Misleading_Record_To_Stand
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Engineer A may feel exposed, defensive, or embarrassed as omissions are implicitly highlighted; board members may feel confused or misled; other engineers may feel a sense of professional duty fulfilled; public may feel vindicated or alarmed
- engineer_a: Professional credibility called into question; the contrast between selective presentation and subsequent fuller testimony is now on the public record
- developer_f: Project narrative is complicated; board now has a more complete and less favorable picture
- city_planning_board: Now receives material information but must reconcile conflicting completeness of expert testimonies
- public_community: Interests are belatedly represented; but the sequencing may have already shaped board impressions
- other_engineers: Fulfill professional and civic duty by disclosing material information Engineer A omitted
Learning Moment: The fact that other engineers voluntarily disclosed what Engineer A withheld starkly illustrates that the information was both available and material — undermining any claim that omission was justified by uncertainty or irrelevance. Peer disclosure creates an implicit standard of professional conduct.
Ethical Implications: Demonstrates that professional ethics are partly defined by community standards — when peers disclose what one engineer withheld, it reveals a breach of the expected standard of candor; also raises questions about whether strategic sequencing of favorable information constitutes a form of deception even without explicit falsehood
- Does the fact that other engineers voluntarily disclosed the pollution concerns indicate that Engineer A had a clear professional obligation to do so as well?
- At the moment other witnesses raise the omitted concerns, does Engineer A acquire a new obligation to respond, correct, or supplement prior testimony?
- How does the sequence of disclosure — benefits first, harms later by others — affect the integrity of the public hearing process?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Event_Subsequent_Witnesses_Raise_Concerns",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Does the fact that other engineers voluntarily disclosed the pollution concerns indicate that Engineer A had a clear professional obligation to do so as well?",
"At the moment other witnesses raise the omitted concerns, does Engineer A acquire a new obligation to respond, correct, or supplement prior testimony?",
"How does the sequence of disclosure \u2014 benefits first, harms later by others \u2014 affect the integrity of the public hearing process?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Engineer A may feel exposed, defensive, or embarrassed as omissions are implicitly highlighted; board members may feel confused or misled; other engineers may feel a sense of professional duty fulfilled; public may feel vindicated or alarmed",
"proeth-scenario:ethicalImplications": "Demonstrates that professional ethics are partly defined by community standards \u2014 when peers disclose what one engineer withheld, it reveals a breach of the expected standard of candor; also raises questions about whether strategic sequencing of favorable information constitutes a form of deception even without explicit falsehood",
"proeth-scenario:learningMoment": "The fact that other engineers voluntarily disclosed what Engineer A withheld starkly illustrates that the information was both available and material \u2014 undermining any claim that omission was justified by uncertainty or irrelevance. Peer disclosure creates an implicit standard of professional conduct.",
"proeth-scenario:narrativePacing": "escalation",
"proeth-scenario:stakeholderConsequences": {
"city_planning_board": "Now receives material information but must reconcile conflicting completeness of expert testimonies",
"developer_f": "Project narrative is complicated; board now has a more complete and less favorable picture",
"engineer_a": "Professional credibility called into question; the contrast between selective presentation and subsequent fuller testimony is now on the public record",
"other_engineers": "Fulfill professional and civic duty by disclosing material information Engineer A omitted",
"public_community": "Interests are belatedly represented; but the sequencing may have already shaped board impressions"
},
"proeth:activatesConstraint": [
"Retroactive_Correction_Obligation_Constraint",
"Professional_Integrity_Under_Scrutiny_Constraint",
"Duty_Not_To_Allow_Misleading_Record_To_Stand"
],
"proeth:causedByAction": "http://proethica.org/cases/94#Action_Omit_Known_Negative_Impacts",
"proeth:causesStateChange": "The information gap created by Engineer A\u0027s omission is partially filled by other witnesses; Engineer A\u0027s selective presentation is now implicitly contradicted by the public record, raising questions about the completeness and integrity of the original testimony",
"proeth:createsObligation": [
"Duty_To_Correct_Or_Supplement_Prior_Incomplete_Testimony",
"Duty_To_Acknowledge_Known_Negative_Impacts_If_Given_Opportunity",
"Obligation_Not_To_Remain_Silent_When_Omission_Is_Exposed"
],
"proeth:description": "After Engineer A\u0027s testimony, other witnesses including other engineers testify before the Planning Board specifically about traffic, noise, and air pollution concerns associated with the development project.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "Later in the same public hearing, after Engineer A\u0027s presentation",
"proeth:urgencyLevel": "high",
"rdfs:label": "Subsequent Witnesses Raise Concerns"
}
Description: As a result of Engineer A's selective presentation, the Planning Board's deliberative record contains a material informational asymmetry: environmental benefits are presented by the project's own engineer while negative impacts are introduced only by third-party witnesses, potentially skewing the board's initial impressions.
Temporal Marker: Throughout and following the public hearing
Activates Constraints:
- Integrity_Of_Public_Record_Constraint
- Informed_Decision_Making_Constraint
- Public_Welfare_Primacy_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: Board members may feel manipulated upon reflection; the public may feel their interests were subordinated to developer interests; Engineer A may experience cognitive dissonance between professional identity and conduct; Developer F may feel the strategy backfired
- engineer_a: Professional reputation damaged; conduct subject to ethical review; may face disciplinary proceedings
- developer_f: Project approval process complicated; credibility of development proposal tainted by association with incomplete expert testimony
- city_planning_board: Institutional integrity of the hearing process is compromised; decisions made on this record may be legally or politically vulnerable
- public_community: Risk of approvals being granted on a skewed evidentiary basis; long-term environmental and quality-of-life harms may materialize if the project proceeds without adequate mitigation
- engineering_profession: Public trust in engineers as honest brokers of technical information is eroded
Learning Moment: Selective disclosure — presenting only favorable information while knowingly withholding unfavorable but material facts — is a form of deception even when no explicit false statement is made. Engineers have an affirmative duty of candor that goes beyond literal truthfulness to encompass completeness of material information.
Ethical Implications: Reveals the core tension between the engineer-as-advocate (serving client interests) and the engineer-as-public-servant (ensuring informed democratic deliberation); demonstrates that deception by omission is ethically equivalent to deception by commission when the omitter knows the information is material and decision-makers are relying on completeness
- Is there a meaningful ethical distinction between lying and strategically omitting material information in a public proceeding?
- What systemic reforms to public hearing processes might reduce the risk of selective expert disclosure distorting regulatory decisions?
- How should the engineering profession balance the legitimate role of advocate-engineer with the obligation of honest expert?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Event_Information_Gap_In_Record",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": true,
"proeth-scenario:discussionPrompts": [
"Is there a meaningful ethical distinction between lying and strategically omitting material information in a public proceeding?",
"What systemic reforms to public hearing processes might reduce the risk of selective expert disclosure distorting regulatory decisions?",
"How should the engineering profession balance the legitimate role of advocate-engineer with the obligation of honest expert?"
],
"proeth-scenario:dramaticTension": "high",
"proeth-scenario:emotionalImpact": "Board members may feel manipulated upon reflection; the public may feel their interests were subordinated to developer interests; Engineer A may experience cognitive dissonance between professional identity and conduct; Developer F may feel the strategy backfired",
"proeth-scenario:ethicalImplications": "Reveals the core tension between the engineer-as-advocate (serving client interests) and the engineer-as-public-servant (ensuring informed democratic deliberation); demonstrates that deception by omission is ethically equivalent to deception by commission when the omitter knows the information is material and decision-makers are relying on completeness",
"proeth-scenario:learningMoment": "Selective disclosure \u2014 presenting only favorable information while knowingly withholding unfavorable but material facts \u2014 is a form of deception even when no explicit false statement is made. Engineers have an affirmative duty of candor that goes beyond literal truthfulness to encompass completeness of material information.",
"proeth-scenario:narrativePacing": "crisis",
"proeth-scenario:stakeholderConsequences": {
"city_planning_board": "Institutional integrity of the hearing process is compromised; decisions made on this record may be legally or politically vulnerable",
"developer_f": "Project approval process complicated; credibility of development proposal tainted by association with incomplete expert testimony",
"engineer_a": "Professional reputation damaged; conduct subject to ethical review; may face disciplinary proceedings",
"engineering_profession": "Public trust in engineers as honest brokers of technical information is eroded",
"public_community": "Risk of approvals being granted on a skewed evidentiary basis; long-term environmental and quality-of-life harms may materialize if the project proceeds without adequate mitigation"
},
"proeth:activatesConstraint": [
"Integrity_Of_Public_Record_Constraint",
"Informed_Decision_Making_Constraint",
"Public_Welfare_Primacy_Constraint"
],
"proeth:causedByAction": "http://proethica.org/cases/94#Action_Omit_Known_Negative_Impacts",
"proeth:causesStateChange": "The public record is materially incomplete as presented by the project engineer; the board must now reconstruct a balanced picture from disparate sources rather than receiving integrated expert analysis; public trust in the engineering expert role is potentially undermined",
"proeth:createsObligation": [
"Board_Obligation_To_Weigh_Full_Record_Including_Third_Party_Testimony",
"Engineer_A_Obligation_To_Correct_Record_If_Opportunity_Arises",
"Professional_Community_Obligation_To_Maintain_Standards_Of_Disclosure"
],
"proeth:description": "As a result of Engineer A\u0027s selective presentation, the Planning Board\u0027s deliberative record contains a material informational asymmetry: environmental benefits are presented by the project\u0027s own engineer while negative impacts are introduced only by third-party witnesses, potentially skewing the board\u0027s initial impressions.",
"proeth:emergencyStatus": "high",
"proeth:eventType": "outcome",
"proeth:temporalMarker": "Throughout and following the public hearing",
"proeth:urgencyLevel": "high",
"rdfs:label": "Information Gap In Record"
}
Description: The Discussion section of the case analysis invokes two prior Board of Ethical Review decisions (Case 65-9 from 1965 and Case 79-2 from 1979) as precedent to contextualize and evaluate Engineer A's disclosure obligations, establishing that the ethical standard at issue has prior authoritative grounding.
Temporal Marker: Discussion/analysis phase, after factual events
Activates Constraints:
- Precedent_Consistency_Constraint
- Established_Ethical_Standard_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenariosEmotional Impact: For students and practitioners, the invocation of precedent may produce a sense of clarity (the standard is settled) or gravity (Engineer A cannot claim ignorance of expectations); for Engineer A, the precedent removes any defense of ambiguity
- engineer_a: Cannot claim the disclosure obligation was unclear or unprecedented; precedent establishes that the standard was knowable and known
- engineering_profession: Demonstrates institutional capacity for self-regulation and normative continuity
- students_and_practitioners: Gain access to a body of reasoned ethical precedent that clarifies professional obligations
- city_planning_board_and_public: Indirectly benefit from a profession that has articulated and enforced disclosure standards over time
Learning Moment: Professional ethical standards are not invented anew for each case — they are built through accumulated decisions. Engineers are expected to know and apply established standards. The existence of prior BER cases on analogous facts means Engineer A's obligations were clearly defined, not ambiguous.
Ethical Implications: Illustrates that professional ethics is a cumulative, precedent-informed practice — not merely a set of abstract principles — and that engineers bear responsibility for knowing the established standards of their profession; also highlights the profession's self-regulatory function as a mechanism of public accountability
- How does the existence of prior BER precedent affect your assessment of Engineer A's culpability — does it make the conduct more or less defensible?
- What is the role of professional self-regulation (like BER case decisions) in shaping engineer conduct, and how effective is it?
- Should engineering ethics education place greater emphasis on case law and precedent, similar to legal education?
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"proeth-scenario": "http://proethica.org/ontology/scenario#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/cases/94#Event_Prior_BER_Cases_Referenced",
"@type": "proeth:Event",
"proeth-scenario:crisisIdentification": false,
"proeth-scenario:discussionPrompts": [
"How does the existence of prior BER precedent affect your assessment of Engineer A\u0027s culpability \u2014 does it make the conduct more or less defensible?",
"What is the role of professional self-regulation (like BER case decisions) in shaping engineer conduct, and how effective is it?",
"Should engineering ethics education place greater emphasis on case law and precedent, similar to legal education?"
],
"proeth-scenario:dramaticTension": "low",
"proeth-scenario:emotionalImpact": "For students and practitioners, the invocation of precedent may produce a sense of clarity (the standard is settled) or gravity (Engineer A cannot claim ignorance of expectations); for Engineer A, the precedent removes any defense of ambiguity",
"proeth-scenario:ethicalImplications": "Illustrates that professional ethics is a cumulative, precedent-informed practice \u2014 not merely a set of abstract principles \u2014 and that engineers bear responsibility for knowing the established standards of their profession; also highlights the profession\u0027s self-regulatory function as a mechanism of public accountability",
"proeth-scenario:learningMoment": "Professional ethical standards are not invented anew for each case \u2014 they are built through accumulated decisions. Engineers are expected to know and apply established standards. The existence of prior BER cases on analogous facts means Engineer A\u0027s obligations were clearly defined, not ambiguous.",
"proeth-scenario:narrativePacing": "aftermath",
"proeth-scenario:stakeholderConsequences": {
"city_planning_board_and_public": "Indirectly benefit from a profession that has articulated and enforced disclosure standards over time",
"engineer_a": "Cannot claim the disclosure obligation was unclear or unprecedented; precedent establishes that the standard was knowable and known",
"engineering_profession": "Demonstrates institutional capacity for self-regulation and normative continuity",
"students_and_practitioners": "Gain access to a body of reasoned ethical precedent that clarifies professional obligations"
},
"proeth:activatesConstraint": [
"Precedent_Consistency_Constraint",
"Established_Ethical_Standard_Constraint"
],
"proeth:causesStateChange": "The ethical analysis moves from fact-specific inquiry to normative evaluation against established professional standards; Engineer A\u0027s conduct is now measured against a known and documented baseline of expected professional behavior",
"proeth:createsObligation": [
"Obligation_To_Apply_Consistent_Ethical_Standards_Across_Cases",
"Obligation_To_Recognize_That_Disclosure_Duty_Is_Not_Novel_But_Established"
],
"proeth:description": "The Discussion section of the case analysis invokes two prior Board of Ethical Review decisions (Case 65-9 from 1965 and Case 79-2 from 1979) as precedent to contextualize and evaluate Engineer A\u0027s disclosure obligations, establishing that the ethical standard at issue has prior authoritative grounding.",
"proeth:emergencyStatus": "low",
"proeth:eventType": "exogenous",
"proeth:temporalMarker": "Discussion/analysis phase, after factual events",
"proeth:urgencyLevel": "low",
"rdfs:label": "Prior BER Cases Referenced"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: Engineer A deliberately chooses to structure the presentation to highlight benefits while, as a direct consequence of that framing choice combined with the omission of known negative impacts, the Planning Board's deliberative record contains a materially incomplete picture of the project's consequences
Necessary Factors (NESS):
- Engineer A's deliberate decision to frame testimony around benefits only
- Engineer A's possession of knowledge about negative impacts (traffic, air pollution, noise)
- The absence of Board members specifically questioning Engineer A about those impacts (Event 3)
- Engineer A's conditional commitment to honesty only if directly questioned (Action 4)
Sufficient Factors:
- Benefit-only framing + omission of known negatives + Board silence on impacts = sufficient to produce a one-sided record without any single factor alone being sufficient
- The conditional honesty commitment (Action 4) ensured that Board silence (Event 3) would not trigger voluntary disclosure, completing the sufficient set
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Frame Presentation Around Benefits (Action 2)
Engineer A deliberately structures testimony to emphasize project benefits, establishing a one-sided evidentiary frame -
Omit Known Negative Impacts (Action 3)
Engineer A, knowing of traffic, air, and noise impacts, excludes them from the presentation, compounding the framing decision with active omission -
Board Members Silent On Impacts (Event 3)
No Planning Board member specifically questions Engineer A about the omitted impacts, removing the only trigger Engineer A had conditioned honest disclosure upon -
Conditionally Commit to Honest Answers (Action 4)
Because no direct question is asked, Engineer A's conditional commitment to honesty is never activated, and voluntary disclosure does not occur -
Information Gap In Record (Event 5)
The Planning Board's deliberative record is left materially incomplete, impairing the Board's ability to make a fully informed regulatory decision in the public interest
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/94#CausalChain_8252a6cd",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A deliberately chooses to structure the presentation to highlight benefits while, as a direct consequence of that framing choice combined with the omission of known negative impacts, the Planning Board\u0027s deliberative record contains a materially incomplete picture of the project\u0027s consequences",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A deliberately structures testimony to emphasize project benefits, establishing a one-sided evidentiary frame",
"proeth:element": "Frame Presentation Around Benefits (Action 2)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A, knowing of traffic, air, and noise impacts, excludes them from the presentation, compounding the framing decision with active omission",
"proeth:element": "Omit Known Negative Impacts (Action 3)",
"proeth:step": 2
},
{
"proeth:description": "No Planning Board member specifically questions Engineer A about the omitted impacts, removing the only trigger Engineer A had conditioned honest disclosure upon",
"proeth:element": "Board Members Silent On Impacts (Event 3)",
"proeth:step": 3
},
{
"proeth:description": "Because no direct question is asked, Engineer A\u0027s conditional commitment to honesty is never activated, and voluntary disclosure does not occur",
"proeth:element": "Conditionally Commit to Honest Answers (Action 4)",
"proeth:step": 4
},
{
"proeth:description": "The Planning Board\u0027s deliberative record is left materially incomplete, impairing the Board\u0027s ability to make a fully informed regulatory decision in the public interest",
"proeth:element": "Information Gap In Record (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Frame Presentation Around Benefits (Action 2)",
"proeth:counterfactual": "Had Engineer A framed the presentation to include known negative impacts, the information gap would not have arisen regardless of whether Board members asked follow-up questions",
"proeth:effect": "Information Gap In Record (Event 5)",
"proeth:necessaryFactors": [
"Engineer A\u0027s deliberate decision to frame testimony around benefits only",
"Engineer A\u0027s possession of knowledge about negative impacts (traffic, air pollution, noise)",
"The absence of Board members specifically questioning Engineer A about those impacts (Event 3)",
"Engineer A\u0027s conditional commitment to honesty only if directly questioned (Action 4)"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Benefit-only framing + omission of known negatives + Board silence on impacts = sufficient to produce a one-sided record without any single factor alone being sufficient",
"The conditional honesty commitment (Action 4) ensured that Board silence (Event 3) would not trigger voluntary disclosure, completing the sufficient set"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A, fully aware that the anticipated commercial development would increase traffic, air pollution, and noise, omits these known impacts from testimony; because the Board receives no signal that these issues exist as concerns, members have no basis upon which to formulate targeted questions, contributing causally to their silence and the resulting record gap
Necessary Factors (NESS):
- Engineer A's actual knowledge of the negative impacts
- Engineer A's decision not to disclose those impacts voluntarily
- Board members' reliance on Engineer A's expert presentation as a basis for identifying what questions to ask
- Absence of other information sources alerting the Board to the omitted issues prior to Engineer A's testimony
Sufficient Factors:
- Expert omission of material facts + Board reliance on expert framing for question formulation = sufficient to produce uninformed Board silence on those specific issues during Engineer A's testimony
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Omit Known Negative Impacts (Action 3)
Engineer A deliberately excludes known adverse impact information from the expert presentation to the Planning Board -
Public Hearing Convened (Event 2) — Testimony Phase
Engineer A delivers the benefit-framed, impact-omitting testimony to the Board without any disclosure of the known negatives -
Board Members Silent On Impacts (Event 3)
Board members, having received no signal from the expert that negative impacts are a relevant concern, do not ask about them -
Subsequent Witnesses Raise Concerns (Event 4)
Other engineers and witnesses raise the omitted concerns after Engineer A's testimony, partially filling the gap but outside Engineer A's testimony record -
Information Gap In Record (Event 5)
Despite subsequent witness testimony, Engineer A's portion of the record remains selectively incomplete, and the overall record reflects the distortion introduced by Engineer A's omission
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/94#CausalChain_3e3277a1",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A, fully aware that the anticipated commercial development would increase traffic, air pollution, and noise, omits these known impacts from testimony; because the Board receives no signal that these issues exist as concerns, members have no basis upon which to formulate targeted questions, contributing causally to their silence and the resulting record gap",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A deliberately excludes known adverse impact information from the expert presentation to the Planning Board",
"proeth:element": "Omit Known Negative Impacts (Action 3)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A delivers the benefit-framed, impact-omitting testimony to the Board without any disclosure of the known negatives",
"proeth:element": "Public Hearing Convened (Event 2) \u2014 Testimony Phase",
"proeth:step": 2
},
{
"proeth:description": "Board members, having received no signal from the expert that negative impacts are a relevant concern, do not ask about them",
"proeth:element": "Board Members Silent On Impacts (Event 3)",
"proeth:step": 3
},
{
"proeth:description": "Other engineers and witnesses raise the omitted concerns after Engineer A\u0027s testimony, partially filling the gap but outside Engineer A\u0027s testimony record",
"proeth:element": "Subsequent Witnesses Raise Concerns (Event 4)",
"proeth:step": 4
},
{
"proeth:description": "Despite subsequent witness testimony, Engineer A\u0027s portion of the record remains selectively incomplete, and the overall record reflects the distortion introduced by Engineer A\u0027s omission",
"proeth:element": "Information Gap In Record (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Omit Known Negative Impacts (Action 3)",
"proeth:counterfactual": "Had Engineer A disclosed the negative impacts, Board members would have had a concrete basis to ask follow-up questions, and the record gap would not have formed in the same way; alternatively, had the Board possessed independent pre-hearing research identifying these impacts, member silence might not have occurred",
"proeth:effect": "Board Members Silent On Impacts (Event 3) enabling Information Gap In Record (Event 5)",
"proeth:necessaryFactors": [
"Engineer A\u0027s actual knowledge of the negative impacts",
"Engineer A\u0027s decision not to disclose those impacts voluntarily",
"Board members\u0027 reliance on Engineer A\u0027s expert presentation as a basis for identifying what questions to ask",
"Absence of other information sources alerting the Board to the omitted issues prior to Engineer A\u0027s testimony"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Expert omission of material facts + Board reliance on expert framing for question formulation = sufficient to produce uninformed Board silence on those specific issues during Engineer A\u0027s testimony"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A agrees to be retained by Developer F, formally establishing a financial and professional relationship that creates the foundational conflict of interest underlying all subsequent ethical failures
Necessary Factors (NESS):
- Engineer A's volitional decision to accept the retainer
- Developer F's offer of engagement for the waterfront project
- Absence of Engineer A declining or disclosing conflict to the Planning Board
Sufficient Factors:
- Acceptance of retainer + formal engagement agreement = establishment of retained relationship with all attendant loyalty obligations to Developer F
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Accept Developer Retention (Action 1)
Engineer A voluntarily agrees to be retained by Developer F, creating a financial relationship and implicit loyalty obligation -
Engineer Retention Established (Event 1)
Formal retention is established, embedding Engineer A in a role where Developer F's interests become Engineer A's professional incentive -
Public Hearing Convened (Event 2)
Engineer A is scheduled to present the project to the City Planning Board, now acting as a retained advocate rather than an independent technical expert -
Frame Presentation Around Benefits (Action 2) + Omit Known Negative Impacts (Action 3)
The retained relationship motivates Engineer A to structure testimony favorably for Developer F, omitting known adverse impacts -
Information Gap In Record (Event 5)
The Planning Board's deliberative record is materially incomplete due to Engineer A's advocacy-driven omissions, compromising public interest protection
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/94#CausalChain_45fbb419",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A agrees to be retained by Developer F, formally establishing a financial and professional relationship that creates the foundational conflict of interest underlying all subsequent ethical failures",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A voluntarily agrees to be retained by Developer F, creating a financial relationship and implicit loyalty obligation",
"proeth:element": "Accept Developer Retention (Action 1)",
"proeth:step": 1
},
{
"proeth:description": "Formal retention is established, embedding Engineer A in a role where Developer F\u0027s interests become Engineer A\u0027s professional incentive",
"proeth:element": "Engineer Retention Established (Event 1)",
"proeth:step": 2
},
{
"proeth:description": "Engineer A is scheduled to present the project to the City Planning Board, now acting as a retained advocate rather than an independent technical expert",
"proeth:element": "Public Hearing Convened (Event 2)",
"proeth:step": 3
},
{
"proeth:description": "The retained relationship motivates Engineer A to structure testimony favorably for Developer F, omitting known adverse impacts",
"proeth:element": "Frame Presentation Around Benefits (Action 2) + Omit Known Negative Impacts (Action 3)",
"proeth:step": 4
},
{
"proeth:description": "The Planning Board\u0027s deliberative record is materially incomplete due to Engineer A\u0027s advocacy-driven omissions, compromising public interest protection",
"proeth:element": "Information Gap In Record (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Accept Developer Retention (Action 1)",
"proeth:counterfactual": "Had Engineer A declined the retention or disclosed the financial relationship fully to the Planning Board, the structural conflict of interest would not have existed or would have been neutralized by transparency",
"proeth:effect": "Engineer Retention Established (Event 1)",
"proeth:necessaryFactors": [
"Engineer A\u0027s volitional decision to accept the retainer",
"Developer F\u0027s offer of engagement for the waterfront project",
"Absence of Engineer A declining or disclosing conflict to the Planning Board"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Acceptance of retainer + formal engagement agreement = establishment of retained relationship with all attendant loyalty obligations to Developer F"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A internally resolves that only if directly questioned will honest answers about impacts be provided; because Board members do not ask (Event 3), this conditional standard ensures that Engineer A's knowledge of negative impacts is never disclosed, directly producing the information gap in the record
Necessary Factors (NESS):
- Engineer A's adoption of a conditional rather than proactive honesty standard
- Board members' failure to ask direct questions about impacts (Event 3)
- Engineer A's possession of material knowledge that would otherwise require disclosure under a proactive standard
Sufficient Factors:
- Conditional honesty standard + Board silence = sufficient to guarantee non-disclosure of known material negative impacts, regardless of Engineer A's underlying knowledge
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Conditionally Commit to Honest Answers (Action 4)
Engineer A internally adopts a standard of honesty contingent on being directly questioned, rather than a proactive full-disclosure standard -
Frame Presentation Around Benefits (Action 2)
The benefit-only framing ensures Board members receive no signal prompting them to ask about negative impacts -
Board Members Silent On Impacts (Event 3)
Board members do not ask about traffic, air, or noise impacts, satisfying the condition under which Engineer A would remain silent -
Non-Disclosure of Known Impacts
Engineer A's conditional commitment is never triggered; known negative impacts are never voluntarily disclosed during testimony -
Information Gap In Record (Event 5)
The Planning Board's record is left without Engineer A's expert assessment of negative impacts, impairing the integrity of the regulatory deliberation
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/94#CausalChain_6047d007",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "Engineer A internally resolves that only if directly questioned will honest answers about impacts be provided; because Board members do not ask (Event 3), this conditional standard ensures that Engineer A\u0027s knowledge of negative impacts is never disclosed, directly producing the information gap in the record",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A internally adopts a standard of honesty contingent on being directly questioned, rather than a proactive full-disclosure standard",
"proeth:element": "Conditionally Commit to Honest Answers (Action 4)",
"proeth:step": 1
},
{
"proeth:description": "The benefit-only framing ensures Board members receive no signal prompting them to ask about negative impacts",
"proeth:element": "Frame Presentation Around Benefits (Action 2)",
"proeth:step": 2
},
{
"proeth:description": "Board members do not ask about traffic, air, or noise impacts, satisfying the condition under which Engineer A would remain silent",
"proeth:element": "Board Members Silent On Impacts (Event 3)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A\u0027s conditional commitment is never triggered; known negative impacts are never voluntarily disclosed during testimony",
"proeth:element": "Non-Disclosure of Known Impacts",
"proeth:step": 4
},
{
"proeth:description": "The Planning Board\u0027s record is left without Engineer A\u0027s expert assessment of negative impacts, impairing the integrity of the regulatory deliberation",
"proeth:element": "Information Gap In Record (Event 5)",
"proeth:step": 5
}
],
"proeth:cause": "Conditionally Commit to Honest Answers (Action 4)",
"proeth:counterfactual": "Had Engineer A adopted an unconditional proactive disclosure standard \u2014 consistent with engineering ethics obligations to the public \u2014 the Board\u0027s silence would have been irrelevant and the information gap would not have formed",
"proeth:effect": "Information Gap In Record (Event 5) \u2014 via non-disclosure when Board is silent",
"proeth:necessaryFactors": [
"Engineer A\u0027s adoption of a conditional rather than proactive honesty standard",
"Board members\u0027 failure to ask direct questions about impacts (Event 3)",
"Engineer A\u0027s possession of material knowledge that would otherwise require disclosure under a proactive standard"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Conditional honesty standard + Board silence = sufficient to guarantee non-disclosure of known material negative impacts, regardless of Engineer A\u0027s underlying knowledge"
],
"proeth:withinAgentControl": true
}
Causal Language: As a result of Engineer A's selective presentation producing an information gap in the Planning Board's deliberative record, the case analysis invokes prior Board of Ethical Review decisions to evaluate and confirm that Engineer A's conduct constitutes a violation of engineering ethics obligations, particularly the duty to be objective and truthful in public statements and to act in the public interest
Necessary Factors (NESS):
- The existence of a demonstrable information gap in the record attributable to Engineer A's conduct
- The existence of prior BER precedents addressing analogous selective disclosure and public testimony ethics scenarios
- The ethical review process examining Engineer A's conduct against established professional standards
Sufficient Factors:
- Documented information gap + applicable BER precedents + ethical review process = sufficient to produce a finding that Engineer A's conduct violated professional engineering ethics obligations
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Accept Developer Retention (Action 1) + Omit Known Negative Impacts (Action 3)
The foundational ethical failures — conflicted retention and deliberate omission — set the conditions for the information gap -
Information Gap In Record (Event 5)
Engineer A's selective presentation leaves the Planning Board's record materially incomplete regarding known negative project impacts -
Subsequent Witnesses Raise Concerns (Event 4)
Other engineers and witnesses identify the concerns Engineer A omitted, making the gap visible and documentable in the hearing record -
Ethical Review Initiated
Engineer A's conduct is submitted for ethical review, with the information gap and its causes forming the factual basis of the analysis -
Prior BER Cases Referenced (Event 6)
The BER analysis invokes prior decisions to confirm that Engineer A's conduct — selective presentation in service of a retaining developer before a public regulatory body — constitutes a violation of professional engineering ethics
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/cases/94#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/cases/94#CausalChain_cca8194d",
"@type": "proeth:CausalChain",
"proeth:causalLanguage": "As a result of Engineer A\u0027s selective presentation producing an information gap in the Planning Board\u0027s deliberative record, the case analysis invokes prior Board of Ethical Review decisions to evaluate and confirm that Engineer A\u0027s conduct constitutes a violation of engineering ethics obligations, particularly the duty to be objective and truthful in public statements and to act in the public interest",
"proeth:causalSequence": [
{
"proeth:description": "The foundational ethical failures \u2014 conflicted retention and deliberate omission \u2014 set the conditions for the information gap",
"proeth:element": "Accept Developer Retention (Action 1) + Omit Known Negative Impacts (Action 3)",
"proeth:step": 1
},
{
"proeth:description": "Engineer A\u0027s selective presentation leaves the Planning Board\u0027s record materially incomplete regarding known negative project impacts",
"proeth:element": "Information Gap In Record (Event 5)",
"proeth:step": 2
},
{
"proeth:description": "Other engineers and witnesses identify the concerns Engineer A omitted, making the gap visible and documentable in the hearing record",
"proeth:element": "Subsequent Witnesses Raise Concerns (Event 4)",
"proeth:step": 3
},
{
"proeth:description": "Engineer A\u0027s conduct is submitted for ethical review, with the information gap and its causes forming the factual basis of the analysis",
"proeth:element": "Ethical Review Initiated",
"proeth:step": 4
},
{
"proeth:description": "The BER analysis invokes prior decisions to confirm that Engineer A\u0027s conduct \u2014 selective presentation in service of a retaining developer before a public regulatory body \u2014 constitutes a violation of professional engineering ethics",
"proeth:element": "Prior BER Cases Referenced (Event 6)",
"proeth:step": 5
}
],
"proeth:cause": "Information Gap In Record (Event 5)",
"proeth:counterfactual": "Had Engineer A\u0027s presentation been complete and balanced, there would have been no information gap to analyze, and the BER precedents would have been referenced only to confirm compliant conduct rather than to establish a violation",
"proeth:effect": "Prior BER Cases Referenced (Event 6) \u2014 ethical violation confirmed by precedent analysis",
"proeth:necessaryFactors": [
"The existence of a demonstrable information gap in the record attributable to Engineer A\u0027s conduct",
"The existence of prior BER precedents addressing analogous selective disclosure and public testimony ethics scenarios",
"The ethical review process examining Engineer A\u0027s conduct against established professional standards"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Documented information gap + applicable BER precedents + ethical review process = sufficient to produce a finding that Engineer A\u0027s conduct violated professional engineering ethics obligations"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (9)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineers A and B study of landfill contours (BER Case No. 79-2) |
before
Entity1 is before Entity2 |
Engineer C publicly contending the higher level design would be environmentally unsound (BER Case No. 79-2) |
time:before
http://www.w3.org/2006/time#before |
Engineer C, a resident of the town, publicly contended that the higher level design concept would be... [more] |
| Engineer A's presentation and Q&A before City Planning Board |
before
Entity1 is before Entity2 |
other witnesses testifying about traffic, noise, and air pollution |
time:before
http://www.w3.org/2006/time#before |
Later, other witnesses attending the public hearing (including other engineers) testify about the in... [more] |
| Engineer A's awareness of traffic, air, and noise pollution factors |
during
Entity1 occurs entirely within the duration of Entity2 |
Engineer A's presentation to the City Planning Board |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
Engineer A is aware of these factors, but was not specifically questioned on these factors and does ... [more] |
| BER Case No. 65-9 |
before
Entity1 is before Entity2 |
BER Case No. 79-2 |
time:before
http://www.w3.org/2006/time#before |
Later in BER Case No. 79-2, the Board considered a case... [following discussion of BER Case No. 65-... [more] |
| BER Case No. 79-2 |
before
Entity1 is before Entity2 |
present case (Engineer A and Developer F waterfront project) |
time:before
http://www.w3.org/2006/time#before |
Turning to the facts in the present case, the Board used the two earlier cases to show that engineer... [more] |
| BER Case No. 65-9 |
before
Entity1 is before Entity2 |
present case (Engineer A and Developer F waterfront project) |
time:before
http://www.w3.org/2006/time#before |
Although the facts in Case Nos. 65-9 and 79-2 are different than those in the present case, the Boar... [more] |
| City Planning Board members questioning Engineer A |
during
Entity1 occurs entirely within the duration of Entity2 |
Engineer A's public hearing presentation |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
Engineer A makes a presentation and responds to questions by members of the City Planning Board. |
| Engineer A's retention by Developer F |
before
Entity1 is before Entity2 |
public hearing before the City Planning Board |
time:before
http://www.w3.org/2006/time#before |
Engineer A is retained by Developer F for a major waterfront development project in City X. As part ... [more] |
| several redesigns not accepted by town council (BER Case No. 79-2) |
before
Entity1 is before Entity2 |
town council requesting new design resulting in acceptable solution (BER Case No. 79-2) |
time:before
http://www.w3.org/2006/time#before |
After several redesigns were not accepted, the town council requested Engineers A and B to prepare a... [more] |
About Allen Relations & OWL-Time
Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.
Each relation includes both a ProEthica custom property and a
time:* OWL-Time property for maximum compatibility.