This page shows the pre-commit working store (the raw extraction under review). This case was committed to OntServe on 2026-07-13 00:01; the committed record differs by design (deduplication, typing, and agent binding are applied at commit). View the committed record
37 entities 8 actions 4 events 10 causal chains 14 temporal relations
Timeline Overview
Action Event 12 sequenced markers
Engineer Retention Beginning of the project, before the planning phase
Public Engagement Scheduling During the planning phase
Outreach Method Directive Prior to or during the public outreach effort
Concern Expression After the public outreach sessions were held
Concern Dismissal Immediately after Engineer M expresses concern
Misleading Report Submission After the public engagement sessions and after dismissing Engineer M's concerns
Ethics Conference With Firm Prospective, recommended as the immediate next step
Escalation to Client Prospective, conditional on Firm DBA choosing not to correct the discrepancies
Licensure Board Reporting Decision Prospective, conditional on the City deciding to do nothing after the escalation meeting
Low Community Participation During the public engagement sessions in the planning phase
Displacement Concerns Voiced During the public engagement sessions
Supportive Comments Reception During the public outreach sessions held in Community Q
OWL-Time Temporal Structure 14 relations time: = w3.org/2006/time
meeting with the City time:intervalBefore Engineer M deciding whether to report to the state licensure board
retention of Engineer M by the City time:intervalBefore planning phase public engagement sessions
public engagement sessions time:intervalDuring planning phase
partnership with Firm DBA time:intervalBefore conduct of public engagement sessions
City instructions to Firm DBA time:intervalBefore public engagement sessions held by Firm DBA
public engagement sessions in Community Q time:intervalBefore Engineer M expressing concern to Firm DBA
Engineer M expressing concern time:intervalBefore Firm DBA preparing and submitting the carefully-framed report
prior projects undertaken for the City time:intervalBefore current public outreach practices
earlier version of the NSPE Code time:intervalBefore revised NSPE Code
report submission time:intervalBefore Engineer M conferring with Firm DBA (recommended)
Engineer M confronting Firm DBA time:intervalBefore Firm DBA acknowledging ethical obligations and correcting discrepancies (conditional)
Firm DBA refusing to correct discrepancies time:intervalBefore Engineer M conferring with the City
reporting Firm DBA to the state licensure board time:intervalBefore prevention of similar future situations
proceeding with the project time:intervalBefore hypothetical later disclosure of omitted information
Extracted Actions (8)
Volitional professional decisions with intentions and ethical context

Description: City leaders, citing economic, political, and social considerations, specifically instruct Firm DBA to perform the public engagement sessions in the manner Firm DBA carried out.

Temporal Marker: Prior to or during the public outreach effort instant

Fluent Transitions:
Initiates (1)
  • Client Pressure State

Mental State: deliberate

Intended Outcome: Shape public engagement according to economic, political, and social considerations

Foreseen Unintended Effects:

  • Suppressed participation from Community P
Required Capabilities:
Municipal project direction
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • requiresCapability: Municipal project direction
  • initiates: Client Pressure State
Literal extractions (kept for synthesis)
  • description content: City leaders, citing economic, political, and social considerations, specifically instruct Firm DBA to perform the public engagement sessions in the manner Firm DBA carried out.
  • hasAgent content: City leaders
  • temporalMarker content: Prior to or during the public outreach effort
  • eventRoleContext content: client
  • hasMentalState content: deliberate
  • intendedOutcome content: Shape public engagement according to economic, political, and social considerations
  • foreseenUnintendedEffects content: Suppressed participation from Community P
  • textReferences content: City leaders, citing economic, political, and social considerations, specifically instructed Firm DBA to perform the public engagement sessions in the way that Firm DBA completed them
  • temporalExtent content: instant
  • temporalSequence content: 2
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Outreach_Method_Directive",
  "@type": "proeth:Action",
  "proeth:description": "City leaders, citing economic, political, and social considerations, specifically instruct Firm DBA to perform the public engagement sessions in the manner Firm DBA carried out.",
  "proeth:eventRoleContext": "client",
  "proeth:foreseenUnintendedEffects": [
    "Suppressed participation from Community P"
  ],
  "proeth:hasAgent": "City leaders",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Client Pressure State"
  ],
  "proeth:intendedOutcome": "Shape public engagement according to economic, political, and social considerations",
  "proeth:requiresCapability": [
    "Municipal project direction"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Prior to or during the public outreach effort",
  "proeth:temporalSequence": 2,
  "proeth:textReferences": [
    "City leaders, citing economic, political, and social considerations, specifically instructed Firm DBA to perform the public engagement sessions in the way that Firm DBA completed them"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Outreach Method Directive"
}

Description: Firm DBA organizes public engagement sessions at times and locations difficult for Community P residents to attend, in Community Q, with no written comment mechanism and no virtual meetings.

Temporal Marker: During the planning phase interval

Fluent Transitions:
Initiates (2)
  • Inaccessible Public Engagement State
  • Community P Exclusion State

Mental State: deliberate

Intended Outcome: Conduct the City-required public engagement sessions in the manner directed by City leaders

Foreseen Unintended Effects:

  • Exclusion of Community P residents from meaningful participation
Obligation Engagement:
Violates (1)
  • Hold Paramount Public Safety, Health, and Welfare
Required Capabilities:
Public outreach coordination Communications and public relations
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • violatesObligation: Hold Paramount Public Safety, Health, and Welfare
  • requiresCapability: Public outreach coordination; Communications and public relations
  • initiates: Inaccessible Public Engagement State; Community P Exclusion State
Literal extractions (kept for synthesis)
  • description content: Firm DBA organizes public engagement sessions at times and locations difficult for Community P residents to attend, in Community Q, with no written comment mechanism and no virtual meetings.
  • hasAgent content: Firm DBA
  • temporalMarker content: During the planning phase
  • eventRoleContext content: engineering consultant with communications and public relations department
  • hasMentalState content: deliberate
  • intendedOutcome content: Conduct the City-required public engagement sessions in the manner directed by City leaders
  • foreseenUnintendedEffects content: Exclusion of Community P residents from meaningful participation
  • textReferences content: Firm DBA organizes meetings at times and locations that are difficult for Community P residents to attend, such as during work hours at venues far from the area and not easily accessible via public transit.; Firm DBA’s outreach and notices do not provide for a method for community members to submit written comments. Finally, no virtual meetings are held to gather feedback from interested persons.
  • temporalExtent content: interval
  • temporalSequence content: 3
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Public_Engagement_Scheduling",
  "@type": "proeth:Action",
  "proeth:description": "Firm DBA organizes public engagement sessions at times and locations difficult for Community P residents to attend, in Community Q, with no written comment mechanism and no virtual meetings.",
  "proeth:eventRoleContext": "engineering consultant with communications and public relations department",
  "proeth:foreseenUnintendedEffects": [
    "Exclusion of Community P residents from meaningful participation"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:hasAgent": "Firm DBA",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Inaccessible Public Engagement State",
    "Community P Exclusion State"
  ],
  "proeth:intendedOutcome": "Conduct the City-required public engagement sessions in the manner directed by City leaders",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Public outreach coordination",
    "Communications and public relations"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During the planning phase",
  "proeth:temporalSequence": 3,
  "proeth:textReferences": [
    "Firm DBA organizes meetings at times and locations that are difficult for Community P residents to attend, such as during work hours at venues far from the area and not easily accessible via public transit.",
    "Firm DBA\u2019s outreach and notices do not provide for a method for community members to submit written comments. Finally, no virtual meetings are held to gather feedback from interested persons."
  ],
  "proeth:violatesObligation": [
    "Hold Paramount Public Safety, Health, and Welfare"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Public Engagement Scheduling"
}

Description: Engineer M expresses concern to Firm DBA about the public outreach and the session locations after observing the flawed engagement process.

Temporal Marker: After the public outreach sessions were held instant

Fluent Transitions:
Initiates (1)
  • Ethical Concerns Raised State

Mental State: deliberate

Intended Outcome: Prompt Firm DBA to address deficiencies in the public outreach process

Foreseen Unintended Effects:

  • Friction with project partner Firm DBA
Obligation Engagement:
Fulfills (1)
  • Hold Paramount Public Safety, Health, and Welfare
Guided By Principles:
  • Hold Paramount the Safety, Health, and Welfare of the Public
Required Capabilities:
Professional judgment Communication
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Hold Paramount Public Safety, Health, and Welfare
  • guidedByPrinciple: Hold Paramount the Safety, Health, and Welfare of the Public
  • requiresCapability: Professional judgment; Communication
  • initiates: Ethical Concerns Raised State
Literal extractions (kept for synthesis)
  • description content: Engineer M expresses concern to Firm DBA about the public outreach and the session locations after observing the flawed engagement process.
  • hasAgent content: Engineer M
  • temporalMarker content: After the public outreach sessions were held
  • eventRoleContext content: lead engineer retained by the City
  • hasMentalState content: deliberate
  • intendedOutcome content: Prompt Firm DBA to address deficiencies in the public outreach process
  • foreseenUnintendedEffects content: Friction with project partner Firm DBA
  • textReferences content: Engineer M expresses concern to Firm DBA about the public outreach and session locations
  • temporalExtent content: instant
  • temporalSequence content: 7
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Concern_Expression",
  "@type": "proeth:Action",
  "proeth:description": "Engineer M expresses concern to Firm DBA about the public outreach and the session locations after observing the flawed engagement process.",
  "proeth:eventRoleContext": "lead engineer retained by the City",
  "proeth:foreseenUnintendedEffects": [
    "Friction with project partner Firm DBA"
  ],
  "proeth:fulfillsObligation": [
    "Hold Paramount Public Safety, Health, and Welfare"
  ],
  "proeth:guidedByPrinciple": [
    "Hold Paramount the Safety, Health, and Welfare of the Public"
  ],
  "proeth:hasAgent": "Engineer M",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Ethical Concerns Raised State"
  ],
  "proeth:intendedOutcome": "Prompt Firm DBA to address deficiencies in the public outreach process",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Professional judgment",
    "Communication"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "After the public outreach sessions were held",
  "proeth:temporalSequence": 7,
  "proeth:textReferences": [
    "Engineer M expresses concern to Firm DBA about the public outreach and session locations"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Concern Expression"
}

Description: Firm DBA rejects Engineer M's concerns, stating the practices are consistent with prior projects for the City and were performed under specific City instruction.

Temporal Marker: Immediately after Engineer M expresses concern instant

Fluent Transitions:
Initiates (1)
  • Unresolved Ethical Dispute State

Mental State: deliberate

Intended Outcome: Defend and continue its outreach approach without changes

Foreseen Unintended Effects:

  • Perpetuation of a flawed engagement record
Obligation Engagement:
Violates (1)
  • Hold Paramount Public Safety, Health, and Welfare
Required Capabilities:
Client relations
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • violatesObligation: Hold Paramount Public Safety, Health, and Welfare
  • requiresCapability: Client relations
  • initiates: Unresolved Ethical Dispute State
Literal extractions (kept for synthesis)
  • description content: Firm DBA rejects Engineer M's concerns, stating the practices are consistent with prior projects for the City and were performed under specific City instruction.
  • hasAgent content: Firm DBA
  • temporalMarker content: Immediately after Engineer M expresses concern
  • eventRoleContext content: engineering consultant
  • hasMentalState content: deliberate
  • intendedOutcome content: Defend and continue its outreach approach without changes
  • foreseenUnintendedEffects content: Perpetuation of a flawed engagement record
  • textReferences content: Firm DBA states that these practices are consistent with prior projects undertaken for the City
  • temporalExtent content: instant
  • temporalSequence content: 8
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Concern_Dismissal",
  "@type": "proeth:Action",
  "proeth:description": "Firm DBA rejects Engineer M\u0027s concerns, stating the practices are consistent with prior projects for the City and were performed under specific City instruction.",
  "proeth:eventRoleContext": "engineering consultant",
  "proeth:foreseenUnintendedEffects": [
    "Perpetuation of a flawed engagement record"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:hasAgent": "Firm DBA",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Unresolved Ethical Dispute State"
  ],
  "proeth:intendedOutcome": "Defend and continue its outreach approach without changes",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Client relations"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Immediately after Engineer M expresses concern",
  "proeth:temporalSequence": 8,
  "proeth:textReferences": [
    "Firm DBA states that these practices are consistent with prior projects undertaken for the City"
  ],
  "proeth:violatesObligation": [
    "Hold Paramount Public Safety, Health, and Welfare"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Concern Dismissal"
}

Description: Firm DBA prepares and submits a carefully-framed report that omits where and when sessions were held and that written comments were not accepted, and claims Community P supports the project.

Temporal Marker: After the public engagement sessions and after dismissing Engineer M's concerns instant

Fluent Transitions:
Initiates (2)
  • Misrepresented Community Support State
  • Fraudulent or Dishonest Enterprise State

Mental State: deliberate

Intended Outcome: Present the project as having community support and satisfy the City's engagement requirement

Foreseen Unintended Effects:

  • Misrepresentation of Community P's position
  • Negative impact if the omissions are later disclosed
Obligation Engagement:
Violates (3)
  • Issue Statements in an Objective and Truthful Manner
  • Avoid Deceptive Acts
  • Not Omit a Material Fact
Required Capabilities:
Report preparation Communications
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • violatesObligation: Issue Statements in an Objective and Truthful Manner; Avoid Deceptive Acts; Not Omit a Material Fact
  • requiresCapability: Report preparation; Communications
  • initiates: Misrepresented Community Support State; Fraudulent or Dishonest Enterprise State
Literal extractions (kept for synthesis)
  • description content: Firm DBA prepares and submits a carefully-framed report that omits where and when sessions were held and that written comments were not accepted, and claims Community P supports the project.
  • hasAgent content: Firm DBA
  • temporalMarker content: After the public engagement sessions and after dismissing Engineer M's concerns
  • eventRoleContext content: engineering consultant
  • hasMentalState content: deliberate
  • intendedOutcome content: Present the project as having community support and satisfy the City's engagement requirement
  • foreseenUnintendedEffects content: Misrepresentation of Community P's position; Negative impact if the omissions are later disclosed
  • textReferences content: Firm DBA prepares a carefully-framed report, omitting details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted.; Firm DBA submits a report claiming Community P’s support for the project, citing a lack of significant opposition and comments in support of the project.
  • temporalExtent content: instant
  • temporalSequence content: 9
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Misleading_Report_Submission",
  "@type": "proeth:Action",
  "proeth:description": "Firm DBA prepares and submits a carefully-framed report that omits where and when sessions were held and that written comments were not accepted, and claims Community P supports the project.",
  "proeth:eventRoleContext": "engineering consultant",
  "proeth:foreseenUnintendedEffects": [
    "Misrepresentation of Community P\u0027s position",
    "Negative impact if the omissions are later disclosed"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:hasAgent": "Firm DBA",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Misrepresented Community Support State",
    "Fraudulent or Dishonest Enterprise State"
  ],
  "proeth:intendedOutcome": "Present the project as having community support and satisfy the City\u0027s engagement requirement",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Report preparation",
    "Communications"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "After the public engagement sessions and after dismissing Engineer M\u0027s concerns",
  "proeth:temporalSequence": 9,
  "proeth:textReferences": [
    "Firm DBA prepares a carefully-framed report, omitting details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted.",
    "Firm DBA submits a report claiming Community P\u2019s support for the project, citing a lack of significant opposition and comments in support of the project."
  ],
  "proeth:violatesObligation": [
    "Issue Statements in an Objective and Truthful Manner",
    "Avoid Deceptive Acts",
    "Not Omit a Material Fact"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Misleading Report Submission"
}

Description: Recommended prospective action in which Engineer M confers immediately with Firm DBA, states objections, and expresses all ethical obligations under the Code, with Firm DBA's supervising licensed engineers involved.

Temporal Marker: Prospective, recommended as the immediate next step instant

Fluent Transitions:
Initiates (1)
  • Correction Opportunity State
Terminates (1)
  • Unresolved Ethical Dispute State

Mental State: deliberate

Intended Outcome: Achieve an immediate resolution with Firm DBA correcting the report discrepancies

Foreseen Unintended Effects:

  • Firm DBA may refuse, citing City direction
Obligation Engagement:
Fulfills (2)
  • Not Associate With Fraudulent or Dishonest Enterprise
  • Advise Clients or Employers When a Project Will Not Be Successful
Guided By Principles:
  • Hold Paramount the Safety, Health, and Welfare of the Public
  • Adherence to the Highest Principles of Ethical Conduct
Required Capabilities:
Ethical reasoning Professional communication
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Not Associate With Fraudulent or Dishonest Enterprise; Advise Clients or Employers When a Project Will Not Be Successful
  • guidedByPrinciple: Hold Paramount the Safety, Health, and Welfare of the Public; Adherence to the Highest Principles of Ethical Conduct
  • requiresCapability: Ethical reasoning; Professional communication
  • initiates: Correction Opportunity State
  • terminates: Unresolved Ethical Dispute State
Literal extractions (kept for synthesis)
  • description content: Recommended prospective action in which Engineer M confers immediately with Firm DBA, states objections, and expresses all ethical obligations under the Code, with Firm DBA's supervising licensed engineers involved.
  • hasAgent content: Engineer M
  • temporalMarker content: Prospective, recommended as the immediate next step
  • eventRoleContext content: lead engineer retained by the City
  • hasMentalState content: deliberate
  • intendedOutcome content: Achieve an immediate resolution with Firm DBA correcting the report discrepancies
  • foreseenUnintendedEffects content: Firm DBA may refuse, citing City direction
  • textReferences content: the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code.; The licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved in these discussions
  • temporalExtent content: instant
  • temporalSequence content: 10
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Ethics_Conference_With_Firm",
  "@type": "proeth:Action",
  "proeth:description": "Recommended prospective action in which Engineer M confers immediately with Firm DBA, states objections, and expresses all ethical obligations under the Code, with Firm DBA\u0027s supervising licensed engineers involved.",
  "proeth:eventRoleContext": "lead engineer retained by the City",
  "proeth:foreseenUnintendedEffects": [
    "Firm DBA may refuse, citing City direction"
  ],
  "proeth:fulfillsObligation": [
    "Not Associate With Fraudulent or Dishonest Enterprise",
    "Advise Clients or Employers When a Project Will Not Be Successful"
  ],
  "proeth:guidedByPrinciple": [
    "Hold Paramount the Safety, Health, and Welfare of the Public",
    "Adherence to the Highest Principles of Ethical Conduct"
  ],
  "proeth:hasAgent": "Engineer M",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Correction Opportunity State"
  ],
  "proeth:intendedOutcome": "Achieve an immediate resolution with Firm DBA correcting the report discrepancies",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Ethical reasoning",
    "Professional communication"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Prospective, recommended as the immediate next step",
  "proeth:temporalSequence": 10,
  "proeth:terminates": [
    "Unresolved Ethical Dispute State"
  ],
  "proeth:textReferences": [
    "the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code.",
    "The licensed professional engineers of Firm DBA, because of their supervisory and ownership roles, should be involved in these discussions"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Ethics Conference With Firm"
}

Description: Prospective action in which Engineer M, if Firm DBA does not correct the discrepancies, confers with the City with the knowledge and potential presence of Firm DBA to discuss the ethical obligations of all involved.

Temporal Marker: Prospective, conditional on Firm DBA choosing not to correct the discrepancies instant

Fluent Transitions:
Initiates (1)
  • City Notified of Discrepancies State

Mental State: deliberate

Intended Outcome: Have the City address the flawed report and the ethical obligations of all parties

Foreseen Unintended Effects:

  • The City may decide to do nothing
Obligation Engagement:
At stake (2)
  • Advise Clients or Employers When a Project Will Not Be Successful
  • Hold Paramount Public Safety, Health, and Welfare
Guided By Principles:
  • Hold Paramount the Safety, Health, and Welfare of the Public
Required Capabilities:
Client communication Ethical reasoning
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Hold Paramount the Safety, Health, and Welfare of the Public
  • requiresCapability: Client communication; Ethical reasoning
  • initiates: City Notified of Discrepancies State
  • raisesObligation: Advise Clients or Employers When a Project Will Not Be Successful; Hold Paramount Public Safety, Health, and Welfare
Literal extractions (kept for synthesis)
  • description content: Prospective action in which Engineer M, if Firm DBA does not correct the discrepancies, confers with the City with the knowledge and potential presence of Firm DBA to discuss the ethical obligations of all involved.
  • hasAgent content: Engineer M
  • temporalMarker content: Prospective, conditional on Firm DBA choosing not to correct the discrepancies
  • eventRoleContext content: lead engineer retained by the City
  • hasMentalState content: deliberate
  • intendedOutcome content: Have the City address the flawed report and the ethical obligations of all parties
  • foreseenUnintendedEffects content: The City may decide to do nothing
  • textReferences content: Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved
  • temporalExtent content: instant
  • temporalSequence content: 11
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Escalation_to_Client",
  "@type": "proeth:Action",
  "proeth:description": "Prospective action in which Engineer M, if Firm DBA does not correct the discrepancies, confers with the City with the knowledge and potential presence of Firm DBA to discuss the ethical obligations of all involved.",
  "proeth:eventRoleContext": "lead engineer retained by the City",
  "proeth:foreseenUnintendedEffects": [
    "The City may decide to do nothing"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:guidedByPrinciple": [
    "Hold Paramount the Safety, Health, and Welfare of the Public"
  ],
  "proeth:hasAgent": "Engineer M",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "City Notified of Discrepancies State"
  ],
  "proeth:intendedOutcome": "Have the City address the flawed report and the ethical obligations of all parties",
  "proeth:raisesObligation": [
    "Advise Clients or Employers When a Project Will Not Be Successful",
    "Hold Paramount Public Safety, Health, and Welfare"
  ],
  "proeth:requiresCapability": [
    "Client communication",
    "Ethical reasoning"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Prospective, conditional on Firm DBA choosing not to correct the discrepancies",
  "proeth:temporalSequence": 11,
  "proeth:textReferences": [
    "Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Escalation to Client"
}

Description: Prospective decision in which Engineer M, if the City decides to do nothing, must decide whether to report Firm DBA's actions to the state's engineering licensure board.

Temporal Marker: Prospective, conditional on the City deciding to do nothing after the escalation meeting instant

Fluent Transitions:
Initiates (1)
  • Regulatory Reporting Consideration State

Mental State: deliberate

Intended Outcome: Prevent similar situations from happening in the future

Foreseen Unintended Effects:

  • The step may appear extreme and strain professional relationships
Obligation Engagement:
At stake (1)
  • Hold Paramount Public Safety, Health, and Welfare
Guided By Principles:
  • Hold Paramount the Safety, Health, and Welfare of the Public
Required Capabilities:
Ethical judgment Knowledge of licensure board processes
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Hold Paramount the Safety, Health, and Welfare of the Public
  • requiresCapability: Ethical judgment; Knowledge of licensure board processes
  • initiates: Regulatory Reporting Consideration State
  • raisesObligation: Hold Paramount Public Safety, Health, and Welfare
Literal extractions (kept for synthesis)
  • description content: Prospective decision in which Engineer M, if the City decides to do nothing, must decide whether to report Firm DBA's actions to the state's engineering licensure board.
  • hasAgent content: Engineer M
  • temporalMarker content: Prospective, conditional on the City deciding to do nothing after the escalation meeting
  • eventRoleContext content: lead engineer retained by the City
  • hasMentalState content: deliberate
  • intendedOutcome content: Prevent similar situations from happening in the future
  • foreseenUnintendedEffects content: The step may appear extreme and strain professional relationships
  • textReferences content: if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board; Although seemingly extreme, reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future.
  • temporalExtent content: instant
  • temporalSequence content: 12
  • withinCompetence assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Action_Licensure_Board_Reporting_Decision",
  "@type": "proeth:Action",
  "proeth:description": "Prospective decision in which Engineer M, if the City decides to do nothing, must decide whether to report Firm DBA\u0027s actions to the state\u0027s engineering licensure board.",
  "proeth:eventRoleContext": "lead engineer retained by the City",
  "proeth:foreseenUnintendedEffects": [
    "The step may appear extreme and strain professional relationships"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:guidedByPrinciple": [
    "Hold Paramount the Safety, Health, and Welfare of the Public"
  ],
  "proeth:hasAgent": "Engineer M",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Regulatory Reporting Consideration State"
  ],
  "proeth:intendedOutcome": "Prevent similar situations from happening in the future",
  "proeth:raisesObligation": [
    "Hold Paramount Public Safety, Health, and Welfare"
  ],
  "proeth:requiresCapability": [
    "Ethical judgment",
    "Knowledge of licensure board processes"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Prospective, conditional on the City deciding to do nothing after the escalation meeting",
  "proeth:temporalSequence": 12,
  "proeth:textReferences": [
    "if the City decided to do nothing, Engineer M must decide whether to report Firm DBA\u2019s actions to the state\u2019s engineering licensure board",
    "Although seemingly extreme, reporting Firm DBA to the state\u2019s engineering licensure board may be necessary to prevent similar situations from happening in the future."
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Licensure Board Reporting Decision"
}
Extracted Events (4)
Occurrences that trigger ethical considerations and state changes

Description: Engineer M is retained by the City as the lead engineer on the major public infrastructure project to upgrade the highway through Community P.

Temporal Marker: Beginning of the project, before the planning phase instant

Fluent Transitions:
Initiates (1)
  • Engineer M Lead Engineer Engagement
Field classification (triples vs literals)
Relations (structural triples)
  • initiates: Engineer M Lead Engineer Engagement
Literal extractions (kept for synthesis)
  • description content: Engineer M is retained by the City as the lead engineer on the major public infrastructure project to upgrade the highway through Community P.
  • temporalMarker content: Beginning of the project, before the planning phase
  • textReferences content: Engineer M is retained by the City as the lead engineer on a major public infrastructure project to upgrade a highway system that runs through Community P
  • eventType content: outcome
  • temporalExtent content: instant
  • temporalSequence content: 1
  • confidence assessment: 0.8
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Event_Engineer_Retention",
  "@type": "proeth:Event",
  "proeth:confidence": "0.8",
  "proeth:description": "Engineer M is retained by the City as the lead engineer on the major public infrastructure project to upgrade the highway through Community P.",
  "proeth:eventType": "outcome",
  "proeth:initiates": [
    "Engineer M Lead Engineer Engagement"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Beginning of the project, before the planning phase",
  "proeth:temporalSequence": 1,
  "proeth:textReferences": [
    "Engineer M is retained by the City as the lead engineer on a major public infrastructure project to upgrade a highway system that runs through Community P"
  ],
  "rdfs:label": "Engineer Retention"
}

Description: Few residents of Community P attend the public engagement sessions because the sessions are scheduled at inaccessible times and held in Community Q, far from the affected area.

Temporal Marker: During the public engagement sessions in the planning phase interval

Fluent Transitions:
Initiates (1)
  • Inadequate Community P Representation

Caused By Action: Action_Public_Engagement_Scheduling

Field classification (triples vs literals)
Relations (structural triples)
  • causedByAction: http://proethica.org/ontology/case/5#Action_Public_Engagement_Scheduling
  • initiates: Inadequate Community P Representation
Literal extractions (kept for synthesis)
  • description content: Few residents of Community P attend the public engagement sessions because the sessions are scheduled at inaccessible times and held in Community Q, far from the affected area.
  • temporalMarker content: During the public engagement sessions in the planning phase
  • textReferences content: Few Community P members participate
  • eventType content: outcome
  • temporalExtent content: interval
  • temporalSequence content: 4
  • confidence assessment: 0.95
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Event_Low_Community_Participation",
  "@type": "proeth:Event",
  "proeth:causedByAction": "http://proethica.org/ontology/case/5#Action_Public_Engagement_Scheduling",
  "proeth:confidence": "0.95",
  "proeth:description": "Few residents of Community P attend the public engagement sessions because the sessions are scheduled at inaccessible times and held in Community Q, far from the affected area.",
  "proeth:eventType": "outcome",
  "proeth:initiates": [
    "Inadequate Community P Representation"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During the public engagement sessions in the planning phase",
  "proeth:temporalSequence": 4,
  "proeth:textReferences": [
    "Few Community P members participate"
  ],
  "rdfs:label": "Low Community Participation"
}

Description: The few Community P attendees who do participate express concerns that the project could displace residents and disrupt local businesses.

Temporal Marker: During the public engagement sessions interval

Fluent Transitions:
Initiates (1)
  • Known Community P Opposition

Caused By Action: Action_Public_Engagement_Scheduling

Field classification (triples vs literals)
Relations (structural triples)
  • causedByAction: http://proethica.org/ontology/case/5#Action_Public_Engagement_Scheduling
  • initiates: Known Community P Opposition
Literal extractions (kept for synthesis)
  • description content: The few Community P attendees who do participate express concerns that the project could displace residents and disrupt local businesses.
  • temporalMarker content: During the public engagement sessions
  • textReferences content: those who do express concerns about the project’s potential to displace residents and disrupt local businesses
  • eventType content: outcome
  • temporalExtent content: interval
  • temporalSequence content: 5
  • confidence assessment: 0.9
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Event_Displacement_Concerns_Voiced",
  "@type": "proeth:Event",
  "proeth:causedByAction": "http://proethica.org/ontology/case/5#Action_Public_Engagement_Scheduling",
  "proeth:confidence": "0.9",
  "proeth:description": "The few Community P attendees who do participate express concerns that the project could displace residents and disrupt local businesses.",
  "proeth:eventType": "outcome",
  "proeth:initiates": [
    "Known Community P Opposition"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During the public engagement sessions",
  "proeth:temporalSequence": 5,
  "proeth:textReferences": [
    "those who do express concerns about the project\u2019s potential to displace residents and disrupt local businesses"
  ],
  "rdfs:label": "Displacement Concerns Voiced"
}

Description: Because the sessions are held in Community Q, an alternate route area, many comments are received favoring routing the upgrade through Community P rather than Community Q, producing a skewed public input record.

Temporal Marker: During the public outreach sessions held in Community Q interval

Fluent Transitions:
Initiates (1)
  • Skewed Public Input Record

Caused By Action: Action_Public_Engagement_Scheduling

Field classification (triples vs literals)
Relations (structural triples)
  • causedByAction: http://proethica.org/ontology/case/5#Action_Public_Engagement_Scheduling
  • initiates: Skewed Public Input Record
Literal extractions (kept for synthesis)
  • description content: Because the sessions are held in Community Q, an alternate route area, many comments are received favoring routing the upgrade through Community P rather than Community Q, producing a skewed public input record.
  • temporalMarker content: During the public outreach sessions held in Community Q
  • textReferences content: Many comments are received that support the upgrade through the historically underserved, underrepresented, and overburdened neighborhood (Community P) and not through Community Q.
  • eventType content: outcome
  • temporalExtent content: interval
  • temporalSequence content: 6
  • confidence assessment: 0.92
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "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/ontology/case/5#Event_Supportive_Comments_Reception",
  "@type": "proeth:Event",
  "proeth:causedByAction": "http://proethica.org/ontology/case/5#Action_Public_Engagement_Scheduling",
  "proeth:confidence": "0.92",
  "proeth:description": "Because the sessions are held in Community Q, an alternate route area, many comments are received favoring routing the upgrade through Community P rather than Community Q, producing a skewed public input record.",
  "proeth:eventType": "outcome",
  "proeth:initiates": [
    "Skewed Public Input Record"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During the public outreach sessions held in Community Q",
  "proeth:temporalSequence": 6,
  "proeth:textReferences": [
    "Many comments are received that support the upgrade through the historically underserved, underrepresented, and overburdened neighborhood (Community P) and not through Community Q."
  ],
  "rdfs:label": "Supportive Comments Reception"
}
Causal Chains (10)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: Firm DBA organizes meetings at times and locations that are difficult for Community P residents to attend, such as during work hours at venues far from the area and not easily accessible via public transit.

Necessary Factors (NESS):
  • Sessions scheduled during work hours
  • Venues far from Community P and not accessible by public transit
  • No written comment mechanism
  • No virtual meetings offered
Sufficient Factors:
  • Combination of inaccessible timing + inaccessible location + absence of alternative participation channels (written or virtual)
Counterfactual Test: With accessible times/locations or alternative channels (written comments, virtual meetings), Community P residents would likely have participated in meaningful numbers
Responsibility Attribution:

Agent: Firm DBA (its communications/PR department under licensed PE supervision)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Public Engagement Scheduling
    Sessions set during work hours at distant, transit-inaccessible venues in Community Q
  2. Access Barriers Materialize
    Community P residents face practical barriers to attendance with no written or virtual alternatives
  3. Low Community Participation
    Few Community P members participate in the engagement sessions
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Public Engagement Scheduling
  • effect: Low Community Participation
  • responsibleAgent: Firm DBA (its communications/PR department under licensed PE supervision)
Literal extractions (kept for synthesis)
  • causalLanguage content: Firm DBA organizes meetings at times and locations that are difficult for Community P residents to attend, such as during work hours at venues far from the area and not easily accessible via public transit.
  • necessaryFactors content: Sessions scheduled during work hours; Venues far from Community P and not accessible by public transit; No written comment mechanism; No virtual meetings offered
  • sufficientFactors content: Combination of inaccessible timing + inaccessible location + absence of alternative participation channels (written or virtual)
  • counterfactual content: With accessible times/locations or alternative channels (written comments, virtual meetings), Community P residents would likely have participated in meaningful numbers
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Public Engagement Scheduling', 'proeth:description': 'Sessions set during work hours at distant, transit-inaccessible venues in Community Q'}; {'proeth:step': 2, 'proeth:element': 'Access Barriers Materialize', 'proeth:description': 'Community P residents face practical barriers to attendance with no written or virtual alternatives'}; {'proeth:step': 3, 'proeth:element': 'Low Community Participation', 'proeth:description': 'Few Community P members participate in the engagement sessions'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_2",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm DBA organizes meetings at times and locations that are difficult for Community P residents to attend, such as during work hours at venues far from the area and not easily accessible via public transit.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Sessions set during work hours at distant, transit-inaccessible venues in Community Q",
      "proeth:element": "Public Engagement Scheduling",
      "proeth:step": 1
    },
    {
      "proeth:description": "Community P residents face practical barriers to attendance with no written or virtual alternatives",
      "proeth:element": "Access Barriers Materialize",
      "proeth:step": 2
    },
    {
      "proeth:description": "Few Community P members participate in the engagement sessions",
      "proeth:element": "Low Community Participation",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Public Engagement Scheduling",
  "proeth:counterfactual": "With accessible times/locations or alternative channels (written comments, virtual meetings), Community P residents would likely have participated in meaningful numbers",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Low Community Participation",
  "proeth:necessaryFactors": [
    "Sessions scheduled during work hours",
    "Venues far from Community P and not accessible by public transit",
    "No written comment mechanism",
    "No virtual meetings offered"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Firm DBA (its communications/PR department under licensed PE supervision)",
  "proeth:sufficientFactors": [
    "Combination of inaccessible timing + inaccessible location + absence of alternative participation channels (written or virtual)"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Firm DBA states that City leaders, citing economic, political, and social considerations, specifically instructed Firm DBA to perform the public engagement sessions in the way that Firm DBA completed them.

Necessary Factors (NESS):
  • City leaders' specific instruction on how sessions were to be conducted
  • Firm DBA's willingness to follow the instruction rather than exercise independent professional judgment
  • City's economic, political, and social motivations favoring Community Q
Sufficient Factors:
  • City directive + Firm DBA's compliance + absence of pushback from licensed PEs in supervisory roles at Firm DBA
Counterfactual Test: Without the City's directive, Firm DBA might still have followed its prior practice ('consistent with prior projects'), so the directive was a contributing but possibly not strictly necessary cause; however, the directive was part of a set sufficient to produce the exclusionary scheduling
Responsibility Attribution:

Agent: City leaders (with Firm DBA as complying agent)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Outreach Method Directive
    City leaders, citing economic, political, and social considerations, specifically instruct Firm DBA on how to conduct engagement sessions
  2. Firm DBA Compliance
    Firm DBA accepts the directive, noting the practices are consistent with prior City projects
  3. Public Engagement Scheduling
    Firm DBA organizes meetings at times and locations difficult for Community P residents, with no written comments or virtual meetings
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Outreach Method Directive
  • effect: Public Engagement Scheduling
  • responsibleAgent: City leaders (with Firm DBA as complying agent)
Literal extractions (kept for synthesis)
  • causalLanguage content: Firm DBA states that City leaders, citing economic, political, and social considerations, specifically instructed Firm DBA to perform the public engagement sessions in the way that Firm DBA completed them.
  • necessaryFactors content: City leaders' specific instruction on how sessions were to be conducted; Firm DBA's willingness to follow the instruction rather than exercise independent professional judgment; City's economic, political, and social motivations favoring Community Q
  • sufficientFactors content: City directive + Firm DBA's compliance + absence of pushback from licensed PEs in supervisory roles at Firm DBA
  • counterfactual content: Without the City's directive, Firm DBA might still have followed its prior practice ('consistent with prior projects'), so the directive was a contributing but possibly not strictly necessary cause; however, the directive was part of a set sufficient to produce the exclusionary scheduling
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Outreach Method Directive', 'proeth:description': 'City leaders, citing economic, political, and social considerations, specifically instruct Firm DBA on how to conduct engagement sessions'}; {'proeth:step': 2, 'proeth:element': 'Firm DBA Compliance', 'proeth:description': 'Firm DBA accepts the directive, noting the practices are consistent with prior City projects'}; {'proeth:step': 3, 'proeth:element': 'Public Engagement Scheduling', 'proeth:description': 'Firm DBA organizes meetings at times and locations difficult for Community P residents, with no written comments or virtual meetings'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm DBA states that City leaders, citing economic, political, and social considerations, specifically instructed Firm DBA to perform the public engagement sessions in the way that Firm DBA completed them.",
  "proeth:causalSequence": [
    {
      "proeth:description": "City leaders, citing economic, political, and social considerations, specifically instruct Firm DBA on how to conduct engagement sessions",
      "proeth:element": "Outreach Method Directive",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA accepts the directive, noting the practices are consistent with prior City projects",
      "proeth:element": "Firm DBA Compliance",
      "proeth:step": 2
    },
    {
      "proeth:description": "Firm DBA organizes meetings at times and locations difficult for Community P residents, with no written comments or virtual meetings",
      "proeth:element": "Public Engagement Scheduling",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Outreach Method Directive",
  "proeth:counterfactual": "Without the City\u0027s directive, Firm DBA might still have followed its prior practice (\u0027consistent with prior projects\u0027), so the directive was a contributing but possibly not strictly necessary cause; however, the directive was part of a set sufficient to produce the exclusionary scheduling",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Public Engagement Scheduling",
  "proeth:necessaryFactors": [
    "City leaders\u0027 specific instruction on how sessions were to be conducted",
    "Firm DBA\u0027s willingness to follow the instruction rather than exercise independent professional judgment",
    "City\u0027s economic, political, and social motivations favoring Community Q"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "City leaders (with Firm DBA as complying agent)",
  "proeth:sufficientFactors": [
    "City directive + Firm DBA\u0027s compliance + absence of pushback from licensed PEs in supervisory roles at Firm DBA"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: The area in which Firm DBA holds the public outreach sessions, Community Q, is an alternate route for the major public infrastructure project. ... Many comments are received that support the upgrade through the historically underserved, underrepresented, and overburdened neighborhood (Community P) and not through Community Q.

Necessary Factors (NESS):
  • Sessions held in Community Q, the alternate route area
  • Community Q attendees' self-interest in routing the project away from their own area
  • Exclusion of Community P voices from the sessions
Sufficient Factors:
  • Holding sessions in the alternate-route community + suppressed Community P attendance was sufficient to skew comments toward routing through Community P
Counterfactual Test: If sessions had been held in or accessible to Community P, the comment record would likely have reflected Community P's displacement and business-disruption concerns rather than predominant support
Responsibility Attribution:

Agent: Firm DBA
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Public Engagement Scheduling
    Sessions held in Community Q, the alternate route area
  2. Skewed Audience Composition
    Attendees are predominantly from Community Q rather than the affected Community P
  3. Supportive Comments Reception
    Many comments support routing the upgrade through Community P and not through Community Q
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Public Engagement Scheduling
  • effect: Supportive Comments Reception
  • responsibleAgent: Firm DBA
Literal extractions (kept for synthesis)
  • causalLanguage content: The area in which Firm DBA holds the public outreach sessions, Community Q, is an alternate route for the major public infrastructure project. ... Many comments are received that support the upgrade through the historically underserved, underrepresented, and overburdened neighborhood (Community P) and not through Community Q.
  • necessaryFactors content: Sessions held in Community Q, the alternate route area; Community Q attendees' self-interest in routing the project away from their own area; Exclusion of Community P voices from the sessions
  • sufficientFactors content: Holding sessions in the alternate-route community + suppressed Community P attendance was sufficient to skew comments toward routing through Community P
  • counterfactual content: If sessions had been held in or accessible to Community P, the comment record would likely have reflected Community P's displacement and business-disruption concerns rather than predominant support
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Public Engagement Scheduling', 'proeth:description': 'Sessions held in Community Q, the alternate route area'}; {'proeth:step': 2, 'proeth:element': 'Skewed Audience Composition', 'proeth:description': 'Attendees are predominantly from Community Q rather than the affected Community P'}; {'proeth:step': 3, 'proeth:element': 'Supportive Comments Reception', 'proeth:description': 'Many comments support routing the upgrade through Community P and not through Community Q'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The area in which Firm DBA holds the public outreach sessions, Community Q, is an alternate route for the major public infrastructure project. ... Many comments are received that support the upgrade through the historically underserved, underrepresented, and overburdened neighborhood (Community P) and not through Community Q.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Sessions held in Community Q, the alternate route area",
      "proeth:element": "Public Engagement Scheduling",
      "proeth:step": 1
    },
    {
      "proeth:description": "Attendees are predominantly from Community Q rather than the affected Community P",
      "proeth:element": "Skewed Audience Composition",
      "proeth:step": 2
    },
    {
      "proeth:description": "Many comments support routing the upgrade through Community P and not through Community Q",
      "proeth:element": "Supportive Comments Reception",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Public Engagement Scheduling",
  "proeth:counterfactual": "If sessions had been held in or accessible to Community P, the comment record would likely have reflected Community P\u0027s displacement and business-disruption concerns rather than predominant support",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Supportive Comments Reception",
  "proeth:necessaryFactors": [
    "Sessions held in Community Q, the alternate route area",
    "Community Q attendees\u0027 self-interest in routing the project away from their own area",
    "Exclusion of Community P voices from the sessions"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Firm DBA",
  "proeth:sufficientFactors": [
    "Holding sessions in the alternate-route community + suppressed Community P attendance was sufficient to skew comments toward routing through Community P"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Few Community P members participate, and those who do express concerns about the project’s potential to displace residents and disrupt local businesses.

Necessary Factors (NESS):
  • At least some Community P members overcoming access barriers to attend
  • Genuine underlying concerns about displacement and business disruption in Community P
Sufficient Factors:
  • Attendance by even a few affected residents + real project impacts was sufficient for concerns to be voiced on the record
Counterfactual Test: Had participation been broader, displacement concerns would likely have been voiced more extensively; had no Community P member attended, the concerns would not have entered the record at all
Responsibility Attribution:

Agent: Community P attendees (voicing concerns); Firm DBA (creating conditions limiting how widely concerns were heard)
Type: indirect
Within Agent Control: No

Causal Sequence:
  1. Low Community Participation
    Few Community P members are able to attend the sessions
  2. Displacement Concerns Voiced
    The few attendees express concerns about displacement of residents and disruption of local businesses
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Low Community Participation
  • effect: Displacement Concerns Voiced
  • responsibleAgent: Community P attendees (voicing concerns); Firm DBA (creating conditions limiting how widely concerns were heard)
Literal extractions (kept for synthesis)
  • causalLanguage content: Few Community P members participate, and those who do express concerns about the project’s potential to displace residents and disrupt local businesses.
  • necessaryFactors content: At least some Community P members overcoming access barriers to attend; Genuine underlying concerns about displacement and business disruption in Community P
  • sufficientFactors content: Attendance by even a few affected residents + real project impacts was sufficient for concerns to be voiced on the record
  • counterfactual content: Had participation been broader, displacement concerns would likely have been voiced more extensively; had no Community P member attended, the concerns would not have entered the record at all
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Low Community Participation', 'proeth:description': 'Few Community P members are able to attend the sessions'}; {'proeth:step': 2, 'proeth:element': 'Displacement Concerns Voiced', 'proeth:description': 'The few attendees express concerns about displacement of residents and disruption of local businesses'}
  • responsibilityType assessment: indirect
  • withinAgentControl assessment: False
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_4",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Few Community P members participate, and those who do express concerns about the project\u2019s potential to displace residents and disrupt local businesses.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Few Community P members are able to attend the sessions",
      "proeth:element": "Low Community Participation",
      "proeth:step": 1
    },
    {
      "proeth:description": "The few attendees express concerns about displacement of residents and disruption of local businesses",
      "proeth:element": "Displacement Concerns Voiced",
      "proeth:step": 2
    }
  ],
  "proeth:cause": "Low Community Participation",
  "proeth:counterfactual": "Had participation been broader, displacement concerns would likely have been voiced more extensively; had no Community P member attended, the concerns would not have entered the record at all",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Displacement Concerns Voiced",
  "proeth:necessaryFactors": [
    "At least some Community P members overcoming access barriers to attend",
    "Genuine underlying concerns about displacement and business disruption in Community P"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Community P attendees (voicing concerns); Firm DBA (creating conditions limiting how widely concerns were heard)",
  "proeth:sufficientFactors": [
    "Attendance by even a few affected residents + real project impacts was sufficient for concerns to be voiced on the record"
  ],
  "proeth:withinAgentControl": false
}

Causal Language: Engineer M expresses concern to Firm DBA about the public outreach and session locations, but Firm DBA states that these practices are consistent with prior projects undertaken for the City.

Necessary Factors (NESS):
  • Engineer M raising concerns to Firm DBA
  • Firm DBA's institutional commitment to its prior practices
  • The City directive Firm DBA could cite as justification
Sufficient Factors:
  • Concerns being raised + Firm DBA's reliance on prior practice and City instruction was sufficient to produce a dismissive response
Counterfactual Test: Without Engineer M's expression of concern, there would have been no dismissal event; the dismissal is a direct response to the concern
Responsibility Attribution:

Agent: Firm DBA
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Concern Expression
    Engineer M raises concerns about outreach methods and session locations
  2. Concern Dismissal
    Firm DBA rejects the concerns, citing consistency with prior City projects and the City's specific instructions
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Concern Expression
  • effect: Concern Dismissal
  • responsibleAgent: Firm DBA
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer M expresses concern to Firm DBA about the public outreach and session locations, but Firm DBA states that these practices are consistent with prior projects undertaken for the City.
  • necessaryFactors content: Engineer M raising concerns to Firm DBA; Firm DBA's institutional commitment to its prior practices; The City directive Firm DBA could cite as justification
  • sufficientFactors content: Concerns being raised + Firm DBA's reliance on prior practice and City instruction was sufficient to produce a dismissive response
  • counterfactual content: Without Engineer M's expression of concern, there would have been no dismissal event; the dismissal is a direct response to the concern
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Concern Expression', 'proeth:description': 'Engineer M raises concerns about outreach methods and session locations'}; {'proeth:step': 2, 'proeth:element': 'Concern Dismissal', 'proeth:description': "Firm DBA rejects the concerns, citing consistency with prior City projects and the City's specific instructions"}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_5",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer M expresses concern to Firm DBA about the public outreach and session locations, but Firm DBA states that these practices are consistent with prior projects undertaken for the City.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer M raises concerns about outreach methods and session locations",
      "proeth:element": "Concern Expression",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA rejects the concerns, citing consistency with prior City projects and the City\u0027s specific instructions",
      "proeth:element": "Concern Dismissal",
      "proeth:step": 2
    }
  ],
  "proeth:cause": "Concern Expression",
  "proeth:counterfactual": "Without Engineer M\u0027s expression of concern, there would have been no dismissal event; the dismissal is a direct response to the concern",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Concern Dismissal",
  "proeth:necessaryFactors": [
    "Engineer M raising concerns to Firm DBA",
    "Firm DBA\u0027s institutional commitment to its prior practices",
    "The City directive Firm DBA could cite as justification"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm DBA",
  "proeth:sufficientFactors": [
    "Concerns being raised + Firm DBA\u0027s reliance on prior practice and City instruction was sufficient to produce a dismissive response"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Despite Engineer M’s concerns, Firm DBA prepares a carefully-framed report, omitting details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted.

Necessary Factors (NESS):
  • Firm DBA's decision to disregard Engineer M's objections
  • Firm DBA's control over the report's contents
  • A skewed engagement record needing concealment to appear legitimate
Sufficient Factors:
  • Dismissal of concerns + deliberate omission of material facts + a comment record skewed toward Community Q was sufficient to produce a deceptive report claiming Community P support
Counterfactual Test: Had Firm DBA heeded Engineer M's concerns and corrected the discrepancies, a truthful report disclosing the sessions' locations, timing, and comment limitations would have been produced instead
Responsibility Attribution:

Agent: Firm DBA (including its licensed professional engineers in supervisory and ownership roles)
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Concern Dismissal
    Firm DBA rejects Engineer M's objections, citing prior practice and City instructions
  2. Report Framing Decision
    Firm DBA prepares a carefully-framed report omitting session locations, times, and the absence of written comments
  3. Misleading Report Submission
    Firm DBA submits a report claiming Community P's support, citing a lack of significant opposition
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Concern Dismissal
  • effect: Misleading Report Submission
  • responsibleAgent: Firm DBA (including its licensed professional engineers in supervisory and ownership roles)
Literal extractions (kept for synthesis)
  • causalLanguage content: Despite Engineer M’s concerns, Firm DBA prepares a carefully-framed report, omitting details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted.
  • necessaryFactors content: Firm DBA's decision to disregard Engineer M's objections; Firm DBA's control over the report's contents; A skewed engagement record needing concealment to appear legitimate
  • sufficientFactors content: Dismissal of concerns + deliberate omission of material facts + a comment record skewed toward Community Q was sufficient to produce a deceptive report claiming Community P support
  • counterfactual content: Had Firm DBA heeded Engineer M's concerns and corrected the discrepancies, a truthful report disclosing the sessions' locations, timing, and comment limitations would have been produced instead
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Concern Dismissal', 'proeth:description': "Firm DBA rejects Engineer M's objections, citing prior practice and City instructions"}; {'proeth:step': 2, 'proeth:element': 'Report Framing Decision', 'proeth:description': 'Firm DBA prepares a carefully-framed report omitting session locations, times, and the absence of written comments'}; {'proeth:step': 3, 'proeth:element': 'Misleading Report Submission', 'proeth:description': "Firm DBA submits a report claiming Community P's support, citing a lack of significant opposition"}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_6",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Despite Engineer M\u2019s concerns, Firm DBA prepares a carefully-framed report, omitting details about where the sessions were held and at what time of day the sessions were held, including not identifying that written comments were not accepted.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm DBA rejects Engineer M\u0027s objections, citing prior practice and City instructions",
      "proeth:element": "Concern Dismissal",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA prepares a carefully-framed report omitting session locations, times, and the absence of written comments",
      "proeth:element": "Report Framing Decision",
      "proeth:step": 2
    },
    {
      "proeth:description": "Firm DBA submits a report claiming Community P\u0027s support, citing a lack of significant opposition",
      "proeth:element": "Misleading Report Submission",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Concern Dismissal",
  "proeth:counterfactual": "Had Firm DBA heeded Engineer M\u0027s concerns and corrected the discrepancies, a truthful report disclosing the sessions\u0027 locations, timing, and comment limitations would have been produced instead",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Misleading Report Submission",
  "proeth:necessaryFactors": [
    "Firm DBA\u0027s decision to disregard Engineer M\u0027s objections",
    "Firm DBA\u0027s control over the report\u0027s contents",
    "A skewed engagement record needing concealment to appear legitimate"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm DBA (including its licensed professional engineers in supervisory and ownership roles)",
  "proeth:sufficientFactors": [
    "Dismissal of concerns + deliberate omission of material facts + a comment record skewed toward Community Q was sufficient to produce a deceptive report claiming Community P support"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Firm DBA submits a report claiming Community P’s support for the project, citing a lack of significant opposition and comments in support of the project.

Necessary Factors (NESS):
  • Existence of supportive comments (from Community Q attendees) to cite
  • Suppressed opposition record due to low Community P participation
  • Firm DBA's decision to attribute the support to Community P
Sufficient Factors:
  • The skewed comment record + Firm DBA's misattribution and omissions was sufficient to enable the false claim of Community P support
Counterfactual Test: Without the supportive comments generated by holding sessions in Community Q, Firm DBA would have lacked any evidentiary basis, however misattributed, for claiming support; 'Firm DBA’s report claimed Community P supported the project, without any evidence to support that claim'
Responsibility Attribution:

Agent: Firm DBA
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Supportive Comments Reception
    Many comments received supporting the upgrade through Community P rather than Community Q
  2. Misattribution of Support
    Firm DBA characterizes the record as showing Community P support and a lack of significant opposition
  3. Misleading Report Submission
    Firm DBA submits the carefully-framed report to the City
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Supportive Comments Reception
  • effect: Misleading Report Submission
  • responsibleAgent: Firm DBA
Literal extractions (kept for synthesis)
  • causalLanguage content: Firm DBA submits a report claiming Community P’s support for the project, citing a lack of significant opposition and comments in support of the project.
  • necessaryFactors content: Existence of supportive comments (from Community Q attendees) to cite; Suppressed opposition record due to low Community P participation; Firm DBA's decision to attribute the support to Community P
  • sufficientFactors content: The skewed comment record + Firm DBA's misattribution and omissions was sufficient to enable the false claim of Community P support
  • counterfactual content: Without the supportive comments generated by holding sessions in Community Q, Firm DBA would have lacked any evidentiary basis, however misattributed, for claiming support; 'Firm DBA’s report claimed Community P supported the project, without any evidence to support that claim'
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Supportive Comments Reception', 'proeth:description': 'Many comments received supporting the upgrade through Community P rather than Community Q'}; {'proeth:step': 2, 'proeth:element': 'Misattribution of Support', 'proeth:description': 'Firm DBA characterizes the record as showing Community P support and a lack of significant opposition'}; {'proeth:step': 3, 'proeth:element': 'Misleading Report Submission', 'proeth:description': 'Firm DBA submits the carefully-framed report to the City'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_7",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm DBA submits a report claiming Community P\u2019s support for the project, citing a lack of significant opposition and comments in support of the project.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Many comments received supporting the upgrade through Community P rather than Community Q",
      "proeth:element": "Supportive Comments Reception",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA characterizes the record as showing Community P support and a lack of significant opposition",
      "proeth:element": "Misattribution of Support",
      "proeth:step": 2
    },
    {
      "proeth:description": "Firm DBA submits the carefully-framed report to the City",
      "proeth:element": "Misleading Report Submission",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Supportive Comments Reception",
  "proeth:counterfactual": "Without the supportive comments generated by holding sessions in Community Q, Firm DBA would have lacked any evidentiary basis, however misattributed, for claiming support; \u0027Firm DBA\u2019s report claimed Community P supported the project, without any evidence to support that claim\u0027",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Misleading Report Submission",
  "proeth:necessaryFactors": [
    "Existence of supportive comments (from Community Q attendees) to cite",
    "Suppressed opposition record due to low Community P participation",
    "Firm DBA\u0027s decision to attribute the support to Community P"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm DBA",
  "proeth:sufficientFactors": [
    "The skewed comment record + Firm DBA\u0027s misattribution and omissions was sufficient to enable the false claim of Community P support"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code.

Necessary Factors (NESS):
  • Existence of the deceptive report violating the Code (objective and truthful statements, deceptive acts, misrepresentation, omission of material fact)
  • Engineer M's obligation not to associate with fraudulent or dishonest enterprise (Code II.1.d)
  • Engineer M's knowledge of the report's deficiencies
Sufficient Factors:
  • The deceptive report + Engineer M's Code obligations was sufficient to require Engineer M to confer immediately with Firm DBA
Counterfactual Test: Had Firm DBA submitted an honest report, no ethics confrontation over the report's contents would be required
Responsibility Attribution:

Agent: Engineer M
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Misleading Report Submission
    Firm DBA submits the report claiming Community P support while omitting material facts
  2. Ethical Obligation Triggered
    Engineer M must not permit association with a firm believed to be engaged in fraudulent or dishonest enterprise (Code II.1.d)
  3. Ethics Conference With Firm
    Engineer M confers immediately with Firm DBA, stating objections and ethical obligations, involving Firm DBA's licensed PE supervisors and owners
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Misleading Report Submission
  • effect: Ethics Conference With Firm
  • responsibleAgent: Engineer M
Literal extractions (kept for synthesis)
  • causalLanguage content: As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code.
  • necessaryFactors content: Existence of the deceptive report violating the Code (objective and truthful statements, deceptive acts, misrepresentation, omission of material fact); Engineer M's obligation not to associate with fraudulent or dishonest enterprise (Code II.1.d); Engineer M's knowledge of the report's deficiencies
  • sufficientFactors content: The deceptive report + Engineer M's Code obligations was sufficient to require Engineer M to confer immediately with Firm DBA
  • counterfactual content: Had Firm DBA submitted an honest report, no ethics confrontation over the report's contents would be required
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Misleading Report Submission', 'proeth:description': 'Firm DBA submits the report claiming Community P support while omitting material facts'}; {'proeth:step': 2, 'proeth:element': 'Ethical Obligation Triggered', 'proeth:description': 'Engineer M must not permit association with a firm believed to be engaged in fraudulent or dishonest enterprise (Code II.1.d)'}; {'proeth:step': 3, 'proeth:element': 'Ethics Conference With Firm', 'proeth:description': "Engineer M confers immediately with Firm DBA, stating objections and ethical obligations, involving Firm DBA's licensed PE supervisors and owners"}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_8",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As to a course of action, the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their objections with Firm DBA and express all ethical obligations under the Code.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm DBA submits the report claiming Community P support while omitting material facts",
      "proeth:element": "Misleading Report Submission",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer M must not permit association with a firm believed to be engaged in fraudulent or dishonest enterprise (Code II.1.d)",
      "proeth:element": "Ethical Obligation Triggered",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer M confers immediately with Firm DBA, stating objections and ethical obligations, involving Firm DBA\u0027s licensed PE supervisors and owners",
      "proeth:element": "Ethics Conference With Firm",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Misleading Report Submission",
  "proeth:counterfactual": "Had Firm DBA submitted an honest report, no ethics confrontation over the report\u0027s contents would be required",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Ethics Conference With Firm",
  "proeth:necessaryFactors": [
    "Existence of the deceptive report violating the Code (objective and truthful statements, deceptive acts, misrepresentation, omission of material fact)",
    "Engineer M\u0027s obligation not to associate with fraudulent or dishonest enterprise (Code II.1.d)",
    "Engineer M\u0027s knowledge of the report\u0027s deficiencies"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer M",
  "proeth:sufficientFactors": [
    "The deceptive report + Engineer M\u0027s Code obligations was sufficient to require Engineer M to confer immediately with Firm DBA"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved.

Necessary Factors (NESS):
  • Ethics conference having occurred and failed to produce correction
  • Firm DBA's refusal to correct the discrepancies
  • Engineer M's continuing Code obligations to the public and client
Sufficient Factors:
  • Failed conference + Firm DBA's refusal + Engineer M's paramount duty to public welfare was sufficient to require escalation to the City
Counterfactual Test: If Firm DBA acknowledged its ethical obligations after being confronted, 'a more immediate resolution to the issues may be realized' and escalation to the City would be unnecessary
Responsibility Attribution:

Agent: Engineer M (escalating); Firm DBA (necessitating escalation by refusal)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Ethics Conference With Firm
    Engineer M states objections and ethical obligations to Firm DBA's supervisors and owners
  2. Firm DBA Refusal
    Firm DBA takes the position it performed the work under City direction and is unwilling to make corrections
  3. Escalation to Client
    Engineer M confers with the City, with Firm DBA's knowledge and potential presence, on the ethical obligations of all involved
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Ethics Conference With Firm
  • effect: Escalation to Client
  • responsibleAgent: Engineer M (escalating); Firm DBA (necessitating escalation by refusal)
Literal extractions (kept for synthesis)
  • causalLanguage content: Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved.
  • necessaryFactors content: Ethics conference having occurred and failed to produce correction; Firm DBA's refusal to correct the discrepancies; Engineer M's continuing Code obligations to the public and client
  • sufficientFactors content: Failed conference + Firm DBA's refusal + Engineer M's paramount duty to public welfare was sufficient to require escalation to the City
  • counterfactual content: If Firm DBA acknowledged its ethical obligations after being confronted, 'a more immediate resolution to the issues may be realized' and escalation to the City would be unnecessary
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Ethics Conference With Firm', 'proeth:description': "Engineer M states objections and ethical obligations to Firm DBA's supervisors and owners"}; {'proeth:step': 2, 'proeth:element': 'Firm DBA Refusal', 'proeth:description': 'Firm DBA takes the position it performed the work under City direction and is unwilling to make corrections'}; {'proeth:step': 3, 'proeth:element': 'Escalation to Client', 'proeth:description': "Engineer M confers with the City, with Firm DBA's knowledge and potential presence, on the ethical obligations of all involved"}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_9",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with the City (with the knowledge and potential presence of Firm DBA) and have a discussion of the ethical obligations of all involved.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer M states objections and ethical obligations to Firm DBA\u0027s supervisors and owners",
      "proeth:element": "Ethics Conference With Firm",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm DBA takes the position it performed the work under City direction and is unwilling to make corrections",
      "proeth:element": "Firm DBA Refusal",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer M confers with the City, with Firm DBA\u0027s knowledge and potential presence, on the ethical obligations of all involved",
      "proeth:element": "Escalation to Client",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Ethics Conference With Firm",
  "proeth:counterfactual": "If Firm DBA acknowledged its ethical obligations after being confronted, \u0027a more immediate resolution to the issues may be realized\u0027 and escalation to the City would be unnecessary",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Escalation to Client",
  "proeth:necessaryFactors": [
    "Ethics conference having occurred and failed to produce correction",
    "Firm DBA\u0027s refusal to correct the discrepancies",
    "Engineer M\u0027s continuing Code obligations to the public and client"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer M (escalating); Firm DBA (necessitating escalation by refusal)",
  "proeth:sufficientFactors": [
    "Failed conference + Firm DBA\u0027s refusal + Engineer M\u0027s paramount duty to public welfare was sufficient to require escalation to the City"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board.

Necessary Factors (NESS):
  • The City-level meeting having occurred
  • The City deciding to do nothing
  • Engineer M's exhausted internal remedies and remaining Code obligations
Sufficient Factors:
  • City inaction after escalation + uncorrected deceptive report was sufficient to force the reporting decision on Engineer M
Counterfactual Test: If the City acted to correct the engagement process and the report, the licensure board reporting decision would not arise; 'reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future'
Responsibility Attribution:

Agent: Engineer M (deciding); City (creating necessity through inaction)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Escalation to Client
    Engineer M confers with the City about the ethical obligations of all involved
  2. City Inaction
    The City decides to do nothing to correct the discrepancies
  3. Licensure Board Reporting Decision
    Engineer M must decide whether to report Firm DBA's actions to the state's engineering licensure board to prevent similar situations in the future
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Escalation to Client
  • effect: Licensure Board Reporting Decision
  • responsibleAgent: Engineer M (deciding); City (creating necessity through inaction)
Literal extractions (kept for synthesis)
  • causalLanguage content: After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA’s actions to the state’s engineering licensure board.
  • necessaryFactors content: The City-level meeting having occurred; The City deciding to do nothing; Engineer M's exhausted internal remedies and remaining Code obligations
  • sufficientFactors content: City inaction after escalation + uncorrected deceptive report was sufficient to force the reporting decision on Engineer M
  • counterfactual content: If the City acted to correct the engagement process and the report, the licensure board reporting decision would not arise; 'reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar situations from happening in the future'
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Escalation to Client', 'proeth:description': 'Engineer M confers with the City about the ethical obligations of all involved'}; {'proeth:step': 2, 'proeth:element': 'City Inaction', 'proeth:description': 'The City decides to do nothing to correct the discrepancies'}; {'proeth:step': 3, 'proeth:element': 'Licensure Board Reporting Decision', 'proeth:description': "Engineer M must decide whether to report Firm DBA's actions to the state's engineering licensure board to prevent similar situations in the future"}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/5#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/ontology/case/5#CausalChain_10",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm DBA\u2019s actions to the state\u2019s engineering licensure board.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer M confers with the City about the ethical obligations of all involved",
      "proeth:element": "Escalation to Client",
      "proeth:step": 1
    },
    {
      "proeth:description": "The City decides to do nothing to correct the discrepancies",
      "proeth:element": "City Inaction",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer M must decide whether to report Firm DBA\u0027s actions to the state\u0027s engineering licensure board to prevent similar situations in the future",
      "proeth:element": "Licensure Board Reporting Decision",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Escalation to Client",
  "proeth:counterfactual": "If the City acted to correct the engagement process and the report, the licensure board reporting decision would not arise; \u0027reporting Firm DBA to the state\u2019s engineering licensure board may be necessary to prevent similar situations from happening in the future\u0027",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Licensure Board Reporting Decision",
  "proeth:necessaryFactors": [
    "The City-level meeting having occurred",
    "The City deciding to do nothing",
    "Engineer M\u0027s exhausted internal remedies and remaining Code obligations"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer M (deciding); City (creating necessity through inaction)",
  "proeth:sufficientFactors": [
    "City inaction after escalation + uncorrected deceptive report was sufficient to force the reporting decision on Engineer M"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (14)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
meeting with the City before
Entity1 is before Entity2
Engineer M deciding whether to report to the state licensure board time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
After this meeting, if the City decided to do nothing, Engineer M must decide whether to report Firm... [more]
retention of Engineer M by the City before
Entity1 is before Entity2
planning phase public engagement sessions time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
Engineer M is retained by the City as the lead engineer... During the planning phase, the City requi... [more]
public engagement sessions during
Entity1 occurs entirely within the duration of Entity2
planning phase time:intervalDuring
http://www.w3.org/2006/time#intervalDuring
During the planning phase, the City requires a series of public engagement sessions to gather input ... [more]
partnership with Firm DBA before
Entity1 is before Entity2
conduct of public engagement sessions time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
Engineer M’s firm partners with an engineering consultant, Firm DBA, to coordinate public outreach a... [more]
City instructions to Firm DBA before
Entity1 is before Entity2
public engagement sessions held by Firm DBA time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
City leaders... specifically instructed Firm DBA to perform the public engagement sessions in the wa... [more]
public engagement sessions in Community Q before
Entity1 is before Entity2
Engineer M expressing concern to Firm DBA time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
Engineer M expresses concern to Firm DBA about the public outreach and session locations
Engineer M expressing concern before
Entity1 is before Entity2
Firm DBA preparing and submitting the carefully-framed report time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
Despite Engineer M’s concerns, Firm DBA prepares a carefully-framed report... Firm DBA submits a rep... [more]
prior projects undertaken for the City before
Entity1 is before Entity2
current public outreach practices time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
Firm DBA states that these practices are consistent with prior projects undertaken for the City
earlier version of the NSPE Code before
Entity1 is before Entity2
revised NSPE Code time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
However, the Code has been revised since that time
report submission before
Entity1 is before Entity2
Engineer M conferring with Firm DBA (recommended) time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
the BER recommends Engineer M to confer immediately with Firm DBA. Engineer M should state their obj... [more]
Engineer M confronting Firm DBA before
Entity1 is before Entity2
Firm DBA acknowledging ethical obligations and correcting discrepancies (conditional) time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
Should Firm DBA acknowledge their ethical obligations after being confronted by Engineer M, a more i... [more]
Firm DBA refusing to correct discrepancies before
Entity1 is before Entity2
Engineer M conferring with the City time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
Should Firm DBA choose not to correct the discrepancies, Engineer M would need to also confer with t... [more]
reporting Firm DBA to the state licensure board before
Entity1 is before Entity2
prevention of similar future situations time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
reporting Firm DBA to the state’s engineering licensure board may be necessary to prevent similar si... [more]
proceeding with the project before
Entity1 is before Entity2
hypothetical later disclosure of omitted information time:intervalBefore
http://www.w3.org/2006/time#intervalBefore
If the facts come out later that relevant information was not disclosed in the report, the impact of... [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.