PASS 3: Temporal Dynamics
Case 139: Public Health and Safety—Observing Off-Site Safety Issues
Timeline Overview
OWL-Time Temporal Structure 8 relations time: = w3.org/2006/time
Extracted Actions (2)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A, on behalf of ES Consulting, performs ongoing construction observation services on a project for Client X, during which the adjacent-site safety issues are noticed.
Temporal Marker: Ongoing during the Client X project engagement interval
Fluent Transitions:
- Active Construction Observation Engagement
Mental State: deliberate professional performance
Intended Outcome: Provide contracted construction observation services for Client X
Obligation Engagement:
- Duty to Perform Contracted Professional Services for Client X
Guided By Principles:
- Paramount Public Health, Safety, and Welfare
Required Capabilities:
Field classification (triples vs literals)
fulfillsObligation: Duty to Perform Contracted Professional Services for Client XguidedByPrinciple: Paramount Public Health, Safety, and WelfarerequiresCapability: Construction observation expertise; Safety hazard recognitioninitiates: Active Construction Observation Engagement
descriptioncontent: Engineer A, on behalf of ES Consulting, performs ongoing construction observation services on a project for Client X, during which the adjacent-site safety issues are noticed.hasAgentcontent: Engineer AtemporalMarkercontent: Ongoing during the Client X project engagementeventRoleContextcontent: Consulting Engineer, ES ConsultinghasMentalStatecontent: deliberate professional performanceintendedOutcomecontent: Provide contracted construction observation services for Client XtextReferencescontent: Engineer A performs construction observation services on a project for Client XtemporalExtentcontent: intervaltemporalSequencecontent: 1withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#Action_Construction_Observation_Services",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-14T01:10:36.520247+00:00",
"proeth:description": "Engineer A, on behalf of ES Consulting, performs ongoing construction observation services on a project for Client X, during which the adjacent-site safety issues are noticed.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Consulting Engineer, ES Consulting",
"proeth:fulfillsObligation": [
"Duty to Perform Contracted Professional Services for Client X"
],
"proeth:guidedByPrinciple": [
"Paramount Public Health, Safety, and Welfare"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate professional performance",
"proeth:initiates": [
"Active Construction Observation Engagement"
],
"proeth:intendedOutcome": "Provide contracted construction observation services for Client X",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Construction observation expertise",
"Safety hazard recognition"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "Ongoing during the Client X project engagement",
"proeth:temporalSequence": 1,
"proeth:textReferences": [
"Engineer A performs construction observation services on a project for Client X"
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Construction Observation Services"
}
Description: The Board identifies a potential response Engineer A may choose, bringing the observed adjacent-site safety issues to the attention of ES Consulting superiors and Client X to explore informing responsible parties on the adjacent site, such as the project superintendent. The Board frames this as a personal judgment, not an ethical obligation.
Temporal Marker: Prospective, following observation of the adjacent-site safety issues instant
Fluent Transitions:
- Safety Concern Escalated to Superiors and Client
Mental State: discretionary deliberation, a matter of personal judgment
Intended Outcome: Have appropriate responsible parties on the adjacent site informed of the potential safety issues, particularly if those issues could affect the progress of work on Client X's property
Foreseen Unintended Effects:
- Possible disruption bearing on the progress of the work on Client X's property
Guided By Principles:
- Paramount Public Health, Safety, and Welfare
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Paramount Public Health, Safety, and WelfarerequiresCapability: Safety hazard recognition; Professional communication with superiors and clientinitiates: Safety Concern Escalated to Superiors and Client
descriptioncontent: The Board identifies a potential response Engineer A may choose, bringing the observed adjacent-site safety issues to the attention of ES Consulting superiors and Client X to explore informing responsible parties on the adjacent site, such as the project superintendent. The Board frames this as a personal judgment, not an ethical obligation.hasAgentcontent: Engineer AtemporalMarkercontent: Prospective, following observation of the adjacent-site safety issueseventRoleContextcontent: Consulting Engineer, ES ConsultinghasMentalStatecontent: discretionary deliberation, a matter of personal judgmentintendedOutcomecontent: Have appropriate responsible parties on the adjacent site informed of the potential safety issues, particularly if those issues could affect the progress of work on Client X's propertyforeseenUnintendedEffectscontent: Possible disruption bearing on the progress of the work on Client X's propertytextReferencescontent: One potential response could include bringing the matter to the attention of Engineer A’s superiors in ES Consulting and Client X to explore informing appropriate responsible parties on the adjacent site (e.g., project superintendent); this is a personal judgment and does not constitute an ethical obligation that can be imposed on Engineer A to take immediate or direct actiontemporalExtentcontent: instanttemporalSequencecontent: 3withinCompetenceassessment: False
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#Action_Prospective_Safety_Escalation",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-14T01:10:36.520402+00:00",
"proeth:description": "The Board identifies a potential response Engineer A may choose, bringing the observed adjacent-site safety issues to the attention of ES Consulting superiors and Client X to explore informing responsible parties on the adjacent site, such as the project superintendent. The Board frames this as a personal judgment, not an ethical obligation.",
"proeth:discoveredInSection": "discussion",
"proeth:eventRoleContext": "Consulting Engineer, ES Consulting",
"proeth:foreseenUnintendedEffects": [
"Possible disruption bearing on the progress of the work on Client X\u0027s property"
],
"proeth:guidedByPrinciple": [
"Paramount Public Health, Safety, and Welfare"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "discretionary deliberation, a matter of personal judgment",
"proeth:initiates": [
"Safety Concern Escalated to Superiors and Client"
],
"proeth:intendedOutcome": "Have appropriate responsible parties on the adjacent site informed of the potential safety issues, particularly if those issues could affect the progress of work on Client X\u0027s property",
"proeth:requiresCapability": [
"Safety hazard recognition",
"Professional communication with superiors and client"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Prospective, following observation of the adjacent-site safety issues",
"proeth:temporalSequence": 3,
"proeth:textReferences": [
"One potential response could include bringing the matter to the attention of Engineer A\u2019s superiors in ES Consulting and Client X to explore informing appropriate responsible parties on the adjacent site (e.g., project superintendent)",
"this is a personal judgment and does not constitute an ethical obligation that can be imposed on Engineer A to take immediate or direct action"
],
"proeth:withinCompetence": false,
"rdfs:label": "Prospective Safety Escalation"
}
Extracted Events (1)
Occurrences that trigger ethical considerations and state changesDescription: While performing construction observation services for Client X, Engineer A observes potential safety issues in a subcontractor's work on an adjacent property owned by Owner Y, a party with no relationship to Engineer A, ES Consulting, or Client X. The observed hazard falls outside Engineer A's professional scope of responsibility.
Temporal Marker: During performance of construction observation services for Client X instant
Fluent Transitions:
- Adjacent Property Safety Risk
- Out-of-Scope Hazard Awareness
Caused By Action: Action_Construction_Observation_Services
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/139#Action_Construction_Observation_Servicesinitiates: Adjacent Property Safety Risk; Out-of-Scope Hazard Awareness
descriptioncontent: While performing construction observation services for Client X, Engineer A observes potential safety issues in a subcontractor's work on an adjacent property owned by Owner Y, a party with no relationship to Engineer A, ES Consulting, or Client X. The observed hazard falls outside Engineer A's professional scope of responsibility.temporalMarkercontent: During performance of construction observation services for Client XtextReferencescontent: Engineer A observes potential safety issues relating to the performance of work by a subcontractor on a project being constructed on an adjacent piece of property for Owner Y, a party with whom neither Engineer A, ES Consulting, or Client X has any direct relationship; the unsafe condition observed by Engineer A is not within the professional scope of responsibility of Engineer AeventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 2confidenceassessment: 0.95
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#Event_Safety_Hazard_Observation",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-14T01:10:36.520501+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/139#Action_Construction_Observation_Services",
"proeth:confidence": "0.95",
"proeth:description": "While performing construction observation services for Client X, Engineer A observes potential safety issues in a subcontractor\u0027s work on an adjacent property owned by Owner Y, a party with no relationship to Engineer A, ES Consulting, or Client X. The observed hazard falls outside Engineer A\u0027s professional scope of responsibility.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Adjacent Property Safety Risk",
"Out-of-Scope Hazard Awareness"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During performance of construction observation services for Client X",
"proeth:temporalSequence": 2,
"proeth:textReferences": [
"Engineer A observes potential safety issues relating to the performance of work by a subcontractor on a project being constructed on an adjacent piece of property for Owner Y, a party with whom neither Engineer A, ES Consulting, or Client X has any direct relationship",
"the unsafe condition observed by Engineer A is not within the professional scope of responsibility of Engineer A"
],
"rdfs:label": "Safety Hazard Observation"
}
Causal Chains (7)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: During the performance of the construction observation services for Client X, Engineer A observes potential safety issues relating to the performance of work by a subcontractor on a project being constructed on an adjacent piece of property for Owner Y
Necessary Factors (NESS):
- Engineer A's physical presence on Client X's project site
- Engineer A's professional training enabling recognition of safety risks
- Existence of unsafe subcontractor work on the adjacent property
Sufficient Factors:
- Combination of on-site observation duties + proximity of the adjacent project + Engineer A's engineering expertise
Responsibility Attribution:
Agent: Engineer A (acting for ES Consulting)
Type: indirect
Within Agent Control:
Yes
Causal Sequence:
-
Construction Observation Services
Engineer A performs construction observation services for Client X on behalf of ES Consulting -
Adjacent-Site Exposure
Engineer A's presence on site places the adjacent Owner Y project within Engineer A's field of observation -
Safety Hazard Observation
Engineer A observes potential safety issues relating to a subcontractor's work on the adjacent property
Field classification (triples vs literals)
cause: Construction Observation Serviceseffect: Safety Hazard ObservationresponsibleAgent: Engineer A (acting for ES Consulting)
causalLanguagecontent: During the performance of the construction observation services for Client X, Engineer A observes potential safety issues relating to the performance of work by a subcontractor on a project being constructed on an adjacent piece of property for Owner YnecessaryFactorscontent: Engineer A's physical presence on Client X's project site; Engineer A's professional training enabling recognition of safety risks; Existence of unsafe subcontractor work on the adjacent propertysufficientFactorscontent: Combination of on-site observation duties + proximity of the adjacent project + Engineer A's engineering expertisecounterfactualcontent: Had Engineer A not been performing construction observation services at that location, the adjacent-site safety issues would not have been observed by Engineer AagentKnowledgecontent: Engineer A knew the scope of the engagement was Client X's project; the adjacent-site hazard was outside that professional scopeinterveningFactorscontent: Unsafe practices of the subcontractor on Owner Y's project; Physical adjacency of the two construction sitescausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Construction Observation Services', 'proeth:description': 'Engineer A performs construction observation services for Client X on behalf of ES Consulting'}; {'proeth:step': 2, 'proeth:element': 'Adjacent-Site Exposure', 'proeth:description': "Engineer A's presence on site places the adjacent Owner Y project within Engineer A's field of observation"}; {'proeth:step': 3, 'proeth:element': 'Safety Hazard Observation', 'proeth:description': "Engineer A observes potential safety issues relating to a subcontractor's work on the adjacent property"}responsibilityTypeassessment: indirectwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#CausalChain_1",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-14T01:10:36.520570+00:00",
"proeth:agentKnowledge": "Engineer A knew the scope of the engagement was Client X\u0027s project; the adjacent-site hazard was outside that professional scope",
"proeth:causalLanguage": "During the performance of the construction observation services for Client X, Engineer A observes potential safety issues relating to the performance of work by a subcontractor on a project being constructed on an adjacent piece of property for Owner Y",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A performs construction observation services for Client X on behalf of ES Consulting",
"proeth:element": "Construction Observation Services",
"proeth:step": 1
},
{
"proeth:description": "Engineer A\u0027s presence on site places the adjacent Owner Y project within Engineer A\u0027s field of observation",
"proeth:element": "Adjacent-Site Exposure",
"proeth:step": 2
},
{
"proeth:description": "Engineer A observes potential safety issues relating to a subcontractor\u0027s work on the adjacent property",
"proeth:element": "Safety Hazard Observation",
"proeth:step": 3
}
],
"proeth:cause": "Construction Observation Services",
"proeth:counterfactual": "Had Engineer A not been performing construction observation services at that location, the adjacent-site safety issues would not have been observed by Engineer A",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Safety Hazard Observation",
"proeth:interveningFactors": [
"Unsafe practices of the subcontractor on Owner Y\u0027s project",
"Physical adjacency of the two construction sites"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s physical presence on Client X\u0027s project site",
"Engineer A\u0027s professional training enabling recognition of safety risks",
"Existence of unsafe subcontractor work on the adjacent property"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "Engineer A (acting for ES Consulting)",
"proeth:sufficientFactors": [
"Combination of on-site observation duties + proximity of the adjacent project + Engineer A\u0027s engineering expertise"
],
"proeth:withinAgentControl": true
}
Causal Language: the facts in the present case suggest that Engineer A’s recognition of potential safety issues in connection with the adjacent construction project might cause Engineer A to decide that the matter requires some level of response on Engineer A’s part
Necessary Factors (NESS):
- Engineer A's actual observation and recognition of the potential safety issues
- Engineer A's professional judgment that the matter may warrant a response
- Potential bearing of the safety issue on the progress of work on Client X's property
Sufficient Factors:
- Recognition of the hazard + Engineer A's personal judgment that a response is warranted
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Safety Hazard Observation
Engineer A observes potential safety issues on the adjacent Owner Y project -
Recognition and Judgment
Engineer A's recognition might cause Engineer A to decide the matter requires some level of response -
Prospective Safety Escalation
Potential response of bringing the matter to superiors in ES Consulting and Client X to explore informing responsible parties on the adjacent site
Field classification (triples vs literals)
cause: Safety Hazard Observationeffect: Prospective Safety EscalationresponsibleAgent: Engineer A
causalLanguagecontent: the facts in the present case suggest that Engineer A’s recognition of potential safety issues in connection with the adjacent construction project might cause Engineer A to decide that the matter requires some level of response on Engineer A’s partnecessaryFactorscontent: Engineer A's actual observation and recognition of the potential safety issues; Engineer A's professional judgment that the matter may warrant a response; Potential bearing of the safety issue on the progress of work on Client X's propertysufficientFactorscontent: Recognition of the hazard + Engineer A's personal judgment that a response is warrantedcounterfactualcontent: Without observing the safety issues, Engineer A would have no basis to consider bringing the matter to superiors, Client X, or responsible parties on the adjacent siteagentKnowledgecontent: Engineer A knows of potential safety issues but the matter is not within Engineer A's professional scope of responsibilityinterveningFactorscontent: Board's determination that this is a personal judgment, not an imposed ethical obligation; Absence of any direct relationship with Owner YcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Safety Hazard Observation', 'proeth:description': 'Engineer A observes potential safety issues on the adjacent Owner Y project'}; {'proeth:step': 2, 'proeth:element': 'Recognition and Judgment', 'proeth:description': "Engineer A's recognition might cause Engineer A to decide the matter requires some level of response"}; {'proeth:step': 3, 'proeth:element': 'Prospective Safety Escalation', 'proeth:description': 'Potential response of bringing the matter to superiors in ES Consulting and Client X to explore informing responsible parties on the adjacent site'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#CausalChain_2",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-14T01:10:36.520604+00:00",
"proeth:agentKnowledge": "Engineer A knows of potential safety issues but the matter is not within Engineer A\u0027s professional scope of responsibility",
"proeth:causalLanguage": "the facts in the present case suggest that Engineer A\u2019s recognition of potential safety issues in connection with the adjacent construction project might cause Engineer A to decide that the matter requires some level of response on Engineer A\u2019s part",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A observes potential safety issues on the adjacent Owner Y project",
"proeth:element": "Safety Hazard Observation",
"proeth:step": 1
},
{
"proeth:description": "Engineer A\u0027s recognition might cause Engineer A to decide the matter requires some level of response",
"proeth:element": "Recognition and Judgment",
"proeth:step": 2
},
{
"proeth:description": "Potential response of bringing the matter to superiors in ES Consulting and Client X to explore informing responsible parties on the adjacent site",
"proeth:element": "Prospective Safety Escalation",
"proeth:step": 3
}
],
"proeth:cause": "Safety Hazard Observation",
"proeth:counterfactual": "Without observing the safety issues, Engineer A would have no basis to consider bringing the matter to superiors, Client X, or responsible parties on the adjacent site",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Prospective Safety Escalation",
"proeth:interveningFactors": [
"Board\u0027s determination that this is a personal judgment, not an imposed ethical obligation",
"Absence of any direct relationship with Owner Y"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s actual observation and recognition of the potential safety issues",
"Engineer A\u0027s professional judgment that the matter may warrant a response",
"Potential bearing of the safety issue on the progress of work on Client X\u0027s property"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Recognition of the hazard + Engineer A\u0027s personal judgment that a response is warranted"
],
"proeth:withinAgentControl": true
}
Causal Language: where an engineer employed by a large defense industry firm documented and reported to his employer excessive costs and time delays by subcontractors, the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports
Necessary Factors (NESS):
- Engineer's documentation of excessive costs and time delays
- Submission of the reports to the employer
- Employer's unwillingness to change its course of conduct
Sufficient Factors:
- Reports presented to an employer disposed to reject them
Responsibility Attribution:
Agent: Employer (defense industry firm)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Internal Reporting to Employer
Engineer documents and reports excessive costs and time delays by subcontractors to his employer -
Report Rejection
The employer rejects the engineer's reports -
Ethical Right Determination
Board rules the engineer had no obligation to continue efforts or report to authorities, but had an ethical right to do so as a matter of personal conscience
Field classification (triples vs literals)
cause: Internal Reporting to Employereffect: Report RejectionresponsibleAgent: Employer (defense industry firm)
causalLanguagecontent: where an engineer employed by a large defense industry firm documented and reported to his employer excessive costs and time delays by subcontractors, the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reportsnecessaryFactorscontent: Engineer's documentation of excessive costs and time delays; Submission of the reports to the employer; Employer's unwillingness to change its course of conductsufficientFactorscontent: Reports presented to an employer disposed to reject themcounterfactualcontent: Had the engineer not documented and reported the concerns, there would have been no reports for the employer to rejectagentKnowledgecontent: Employer received documented reports of excessive costs and time delays by subcontractorsinterveningFactorscontent: The matter did not involve a danger to public health or safety; Claim concerned unsatisfactory plans and unjustified expenditure of public fundscausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Internal Reporting to Employer', 'proeth:description': 'Engineer documents and reports excessive costs and time delays by subcontractors to his employer'}; {'proeth:step': 2, 'proeth:element': 'Report Rejection', 'proeth:description': "The employer rejects the engineer's reports"}; {'proeth:step': 3, 'proeth:element': 'Ethical Right Determination', 'proeth:description': 'Board rules the engineer had no obligation to continue efforts or report to authorities, but had an ethical right to do so as a matter of personal conscience'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#CausalChain_3",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-14T01:10:36.520632+00:00",
"proeth:agentKnowledge": "Employer received documented reports of excessive costs and time delays by subcontractors",
"proeth:causalLanguage": "where an engineer employed by a large defense industry firm documented and reported to his employer excessive costs and time delays by subcontractors, the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports",
"proeth:causalSequence": [
{
"proeth:description": "Engineer documents and reports excessive costs and time delays by subcontractors to his employer",
"proeth:element": "Internal Reporting to Employer",
"proeth:step": 1
},
{
"proeth:description": "The employer rejects the engineer\u0027s reports",
"proeth:element": "Report Rejection",
"proeth:step": 2
},
{
"proeth:description": "Board rules the engineer had no obligation to continue efforts or report to authorities, but had an ethical right to do so as a matter of personal conscience",
"proeth:element": "Ethical Right Determination",
"proeth:step": 3
}
],
"proeth:cause": "Internal Reporting to Employer",
"proeth:counterfactual": "Had the engineer not documented and reported the concerns, there would have been no reports for the employer to reject",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Report Rejection",
"proeth:interveningFactors": [
"The matter did not involve a danger to public health or safety",
"Claim concerned unsatisfactory plans and unjustified expenditure of public funds"
],
"proeth:necessaryFactors": [
"Engineer\u0027s documentation of excessive costs and time delays",
"Submission of the reports to the employer",
"Employer\u0027s unwillingness to change its course of conduct"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Employer (defense industry firm)",
"proeth:sufficientFactors": [
"Reports presented to an employer disposed to reject them"
],
"proeth:withinAgentControl": true
}
Causal Language: After (1) noticing problems with overflow capacity, which are required to be reported to the state water pollution control authorities, (2) discussing the problem privately with members of the city council
Necessary Factors (NESS):
- Engineer's responsibility for disposal of plants and beds associated with poultry processing facilities
- Existence of overflow capacity problems
- Engineer's awareness that the problems required reporting to state authorities
Sufficient Factors:
- Discovery of the overflow problem + engineer's decision to raise it with city council members
Responsibility Attribution:
Agent: City engineer/director of public works
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Overflow Problem Discovery
City engineer notices problems with overflow capacity required to be reported to state authorities -
Informal Council Disclosure
Engineer discusses the problem privately with members of the city council -
Reporting Restriction Directive
City administrator warns the engineer to report the problem only to him
Field classification (triples vs literals)
cause: Overflow Problem Discoveryeffect: Informal Council DisclosureresponsibleAgent: City engineer/director of public works
causalLanguagecontent: After (1) noticing problems with overflow capacity, which are required to be reported to the state water pollution control authorities, (2) discussing the problem privately with members of the city councilnecessaryFactorscontent: Engineer's responsibility for disposal of plants and beds associated with poultry processing facilities; Existence of overflow capacity problems; Engineer's awareness that the problems required reporting to state authoritiessufficientFactorscontent: Discovery of the overflow problem + engineer's decision to raise it with city council memberscounterfactualcontent: Without discovering the overflow capacity problems, the engineer would have had nothing to disclose to the city councilagentKnowledgecontent: Knew overflow capacity problems are required to be reported to the state water pollution control authoritiesinterveningFactorscontent: Reporting hierarchy through the city administratorcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Overflow Problem Discovery', 'proeth:description': 'City engineer notices problems with overflow capacity required to be reported to state authorities'}; {'proeth:step': 2, 'proeth:element': 'Informal Council Disclosure', 'proeth:description': 'Engineer discusses the problem privately with members of the city council'}; {'proeth:step': 3, 'proeth:element': 'Reporting Restriction Directive', 'proeth:description': 'City administrator warns the engineer to report the problem only to him'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#CausalChain_4",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-14T01:10:36.520656+00:00",
"proeth:agentKnowledge": "Knew overflow capacity problems are required to be reported to the state water pollution control authorities",
"proeth:causalLanguage": "After (1) noticing problems with overflow capacity, which are required to be reported to the state water pollution control authorities, (2) discussing the problem privately with members of the city council",
"proeth:causalSequence": [
{
"proeth:description": "City engineer notices problems with overflow capacity required to be reported to state authorities",
"proeth:element": "Overflow Problem Discovery",
"proeth:step": 1
},
{
"proeth:description": "Engineer discusses the problem privately with members of the city council",
"proeth:element": "Informal Council Disclosure",
"proeth:step": 2
},
{
"proeth:description": "City administrator warns the engineer to report the problem only to him",
"proeth:element": "Reporting Restriction Directive",
"proeth:step": 3
}
],
"proeth:cause": "Overflow Problem Discovery",
"proeth:counterfactual": "Without discovering the overflow capacity problems, the engineer would have had nothing to disclose to the city council",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Informal Council Disclosure",
"proeth:interveningFactors": [
"Reporting hierarchy through the city administrator"
],
"proeth:necessaryFactors": [
"Engineer\u0027s responsibility for disposal of plants and beds associated with poultry processing facilities",
"Existence of overflow capacity problems",
"Engineer\u0027s awareness that the problems required reporting to state authorities"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "City engineer/director of public works",
"proeth:sufficientFactors": [
"Discovery of the overflow problem + engineer\u0027s decision to raise it with city council members"
],
"proeth:withinAgentControl": true
}
Causal Language: (4) discussing the problem again informally with the city council, and (5) being relieved by the city administrator of responsibility for the disposal of plants and beds
Necessary Factors (NESS):
- Engineer's repeated informal discussions with the city council
- City administrator's prior warning to report the problem only to him
- City administrator's authority over the engineer's assigned responsibilities
Sufficient Factors:
- Engineer's defiance of the administrator's directive + administrator's authority to reassign duties
Responsibility Attribution:
Agent: City administrator
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Reporting Restriction Directive
City administrator warns the engineer to report the problem only to him -
Informal Council Disclosure
Engineer discusses the problem again informally with the city council -
Responsibility Removal
City administrator relieves the engineer of responsibility for the disposal of plants and beds
Field classification (triples vs literals)
cause: Informal Council Disclosureeffect: Responsibility RemovalresponsibleAgent: City administrator
causalLanguagecontent: (4) discussing the problem again informally with the city council, and (5) being relieved by the city administrator of responsibility for the disposal of plants and bedsnecessaryFactorscontent: Engineer's repeated informal discussions with the city council; City administrator's prior warning to report the problem only to him; City administrator's authority over the engineer's assigned responsibilitiessufficientFactorscontent: Engineer's defiance of the administrator's directive + administrator's authority to reassign dutiescounterfactualcontent: Had the engineer not gone to the city council after the administrator's warning, the administrator likely would not have relieved her of the disposal responsibility at that timeagentKnowledgecontent: Administrator knew of the overflow problem and had directed the engineer to report only to himinterveningFactorscontent: Pattern of ongoing disregard for the law by the administrator and city council memberscausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Reporting Restriction Directive', 'proeth:description': 'City administrator warns the engineer to report the problem only to him'}; {'proeth:step': 2, 'proeth:element': 'Informal Council Disclosure', 'proeth:description': 'Engineer discusses the problem again informally with the city council'}; {'proeth:step': 3, 'proeth:element': 'Responsibility Removal', 'proeth:description': 'City administrator relieves the engineer of responsibility for the disposal of plants and beds'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#CausalChain_5",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-14T01:10:36.520677+00:00",
"proeth:agentKnowledge": "Administrator knew of the overflow problem and had directed the engineer to report only to him",
"proeth:causalLanguage": "(4) discussing the problem again informally with the city council, and (5) being relieved by the city administrator of responsibility for the disposal of plants and beds",
"proeth:causalSequence": [
{
"proeth:description": "City administrator warns the engineer to report the problem only to him",
"proeth:element": "Reporting Restriction Directive",
"proeth:step": 1
},
{
"proeth:description": "Engineer discusses the problem again informally with the city council",
"proeth:element": "Informal Council Disclosure",
"proeth:step": 2
},
{
"proeth:description": "City administrator relieves the engineer of responsibility for the disposal of plants and beds",
"proeth:element": "Responsibility Removal",
"proeth:step": 3
}
],
"proeth:cause": "Informal Council Disclosure",
"proeth:counterfactual": "Had the engineer not gone to the city council after the administrator\u0027s warning, the administrator likely would not have relieved her of the disposal responsibility at that time",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Responsibility Removal",
"proeth:interveningFactors": [
"Pattern of ongoing disregard for the law by the administrator and city council members"
],
"proeth:necessaryFactors": [
"Engineer\u0027s repeated informal discussions with the city council",
"City administrator\u0027s prior warning to report the problem only to him",
"City administrator\u0027s authority over the engineer\u0027s assigned responsibilities"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "City administrator",
"proeth:sufficientFactors": [
"Engineer\u0027s defiance of the administrator\u0027s directive + administrator\u0027s authority to reassign duties"
],
"proeth:withinAgentControl": true
}
Causal Language: The Board said that the engineer's inaction permitted a serious violation of the law to continue and made the engineer an "accessory" to the actions of the city administrator and others.
Necessary Factors (NESS):
- Engineer's knowledge of the overflow problem and its legal reporting requirement
- Engineer's continued employment as city engineer/director of public works after being relieved of the disposal duty
- Engineer's failure to notify state officials, the proper authorities
Sufficient Factors:
- Engineer's inaction combined with the city officials' ongoing disregard for the law
Responsibility Attribution:
Agent: City engineer/director of public works
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Responsibility Removal
Engineer is relieved by the city administrator of responsibility for the disposal of plants and beds -
Failure to Report Authorities
Engineer continues working as city engineer/director of public works without reporting to state officials -
Legal Violation Continuation
The engineer's inaction permits a serious violation of the law to continue -
Accessory Finding
Board finds the engineer failed her ethical obligations and became an 'accessory' to the actions of the city administrator and others
Field classification (triples vs literals)
cause: Failure to Report Authoritieseffect: Legal Violation ContinuationresponsibleAgent: City engineer/director of public works
causalLanguagecontent: The Board said that the engineer's inaction permitted a serious violation of the law to continue and made the engineer an "accessory" to the actions of the city administrator and others.necessaryFactorscontent: Engineer's knowledge of the overflow problem and its legal reporting requirement; Engineer's continued employment as city engineer/director of public works after being relieved of the disposal duty; Engineer's failure to notify state officials, the proper authoritiessufficientFactorscontent: Engineer's inaction combined with the city officials' ongoing disregard for the lawcounterfactualcontent: Had the engineer reported to state officials, the serious violation of the law would likely not have been permitted to continueagentKnowledgecontent: The engineer knew, or should have known, that 'proper authorities' were not the city officials, but more probably, state officialsinterveningFactorscontent: City administrator's directive restricting reporting; Pattern of ongoing disregard for the law by supervisor and city council memberscausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Responsibility Removal', 'proeth:description': 'Engineer is relieved by the city administrator of responsibility for the disposal of plants and beds'}; {'proeth:step': 2, 'proeth:element': 'Failure to Report Authorities', 'proeth:description': 'Engineer continues working as city engineer/director of public works without reporting to state officials'}; {'proeth:step': 3, 'proeth:element': 'Legal Violation Continuation', 'proeth:description': "The engineer's inaction permits a serious violation of the law to continue"}; {'proeth:step': 4, 'proeth:element': 'Accessory Finding', 'proeth:description': "Board finds the engineer failed her ethical obligations and became an 'accessory' to the actions of the city administrator and others"}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#CausalChain_6",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-14T01:10:36.520698+00:00",
"proeth:agentKnowledge": "The engineer knew, or should have known, that \u0027proper authorities\u0027 were not the city officials, but more probably, state officials",
"proeth:causalLanguage": "The Board said that the engineer\u0027s inaction permitted a serious violation of the law to continue and made the engineer an \"accessory\" to the actions of the city administrator and others.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer is relieved by the city administrator of responsibility for the disposal of plants and beds",
"proeth:element": "Responsibility Removal",
"proeth:step": 1
},
{
"proeth:description": "Engineer continues working as city engineer/director of public works without reporting to state officials",
"proeth:element": "Failure to Report Authorities",
"proeth:step": 2
},
{
"proeth:description": "The engineer\u0027s inaction permits a serious violation of the law to continue",
"proeth:element": "Legal Violation Continuation",
"proeth:step": 3
},
{
"proeth:description": "Board finds the engineer failed her ethical obligations and became an \u0027accessory\u0027 to the actions of the city administrator and others",
"proeth:element": "Accessory Finding",
"proeth:step": 4
}
],
"proeth:cause": "Failure to Report Authorities",
"proeth:counterfactual": "Had the engineer reported to state officials, the serious violation of the law would likely not have been permitted to continue",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Legal Violation Continuation",
"proeth:interveningFactors": [
"City administrator\u0027s directive restricting reporting",
"Pattern of ongoing disregard for the law by supervisor and city council members"
],
"proeth:necessaryFactors": [
"Engineer\u0027s knowledge of the overflow problem and its legal reporting requirement",
"Engineer\u0027s continued employment as city engineer/director of public works after being relieved of the disposal duty",
"Engineer\u0027s failure to notify state officials, the proper authorities"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "City engineer/director of public works",
"proeth:sufficientFactors": [
"Engineer\u0027s inaction combined with the city officials\u0027 ongoing disregard for the law"
],
"proeth:withinAgentControl": true
}
Causal Language: (3) being warned by the city administrator to report the problem only to him, (4) discussing the problem again informally with the city council, and (5) being relieved by the city administrator of responsibility for the disposal of plants and beds, the engineer continued to work in the capacity as city engineer/director of public works.
Necessary Factors (NESS):
- City administrator's warning restricting the engineer's reporting channel
- Engineer's acquiescence to remaining silent toward state officials
- Engineer's continued employment under the administrator's authority
Sufficient Factors:
- Administrator's directive + engineer's decision not to escalate beyond city officials
Responsibility Attribution:
Agent: City administrator and city engineer (jointly)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Overflow Problem Discovery
Engineer notices overflow capacity problems requiring state reporting -
Reporting Restriction Directive
City administrator warns the engineer to report the problem only to him -
Failure to Report Authorities
Engineer continues in her role without reporting to state officials -
Legal Violation Continuation
Serious violation of the law is permitted to continue
Field classification (triples vs literals)
cause: Reporting Restriction Directiveeffect: Failure to Report AuthoritiesresponsibleAgent: City administrator and city engineer (jointly)
causalLanguagecontent: (3) being warned by the city administrator to report the problem only to him, (4) discussing the problem again informally with the city council, and (5) being relieved by the city administrator of responsibility for the disposal of plants and beds, the engineer continued to work in the capacity as city engineer/director of public works.necessaryFactorscontent: City administrator's warning restricting the engineer's reporting channel; Engineer's acquiescence to remaining silent toward state officials; Engineer's continued employment under the administrator's authoritysufficientFactorscontent: Administrator's directive + engineer's decision not to escalate beyond city officialscounterfactualcontent: The directive alone did not compel silence; the engineer knew, or should have known, the proper authorities were state officials, so the failure would not have occurred without the engineer's own acquiescenceagentKnowledgecontent: Administrator knew of the overflow problem; engineer was aware of a pattern of ongoing disregard for the law by her immediate supervisor and city council membersinterveningFactorscontent: Employment pressure and hierarchical reporting structure; City council members' complicity in disregarding the lawcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Overflow Problem Discovery', 'proeth:description': 'Engineer notices overflow capacity problems requiring state reporting'}; {'proeth:step': 2, 'proeth:element': 'Reporting Restriction Directive', 'proeth:description': 'City administrator warns the engineer to report the problem only to him'}; {'proeth:step': 3, 'proeth:element': 'Failure to Report Authorities', 'proeth:description': 'Engineer continues in her role without reporting to state officials'}; {'proeth:step': 4, 'proeth:element': 'Legal Violation Continuation', 'proeth:description': 'Serious violation of the law is permitted to continue'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/139#",
"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/139#CausalChain_7",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-14T01:10:36.520718+00:00",
"proeth:agentKnowledge": "Administrator knew of the overflow problem; engineer was aware of a pattern of ongoing disregard for the law by her immediate supervisor and city council members",
"proeth:causalLanguage": "(3) being warned by the city administrator to report the problem only to him, (4) discussing the problem again informally with the city council, and (5) being relieved by the city administrator of responsibility for the disposal of plants and beds, the engineer continued to work in the capacity as city engineer/director of public works.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer notices overflow capacity problems requiring state reporting",
"proeth:element": "Overflow Problem Discovery",
"proeth:step": 1
},
{
"proeth:description": "City administrator warns the engineer to report the problem only to him",
"proeth:element": "Reporting Restriction Directive",
"proeth:step": 2
},
{
"proeth:description": "Engineer continues in her role without reporting to state officials",
"proeth:element": "Failure to Report Authorities",
"proeth:step": 3
},
{
"proeth:description": "Serious violation of the law is permitted to continue",
"proeth:element": "Legal Violation Continuation",
"proeth:step": 4
}
],
"proeth:cause": "Reporting Restriction Directive",
"proeth:counterfactual": "The directive alone did not compel silence; the engineer knew, or should have known, the proper authorities were state officials, so the failure would not have occurred without the engineer\u0027s own acquiescence",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Failure to Report Authorities",
"proeth:interveningFactors": [
"Employment pressure and hierarchical reporting structure",
"City council members\u0027 complicity in disregarding the law"
],
"proeth:necessaryFactors": [
"City administrator\u0027s warning restricting the engineer\u0027s reporting channel",
"Engineer\u0027s acquiescence to remaining silent toward state officials",
"Engineer\u0027s continued employment under the administrator\u0027s authority"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "City administrator and city engineer (jointly)",
"proeth:sufficientFactors": [
"Administrator\u0027s directive + engineer\u0027s decision not to escalate beyond city officials"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (8)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineer A's observation of potential safety issues on the adjacent property |
during
Entity1 occurs entirely within the duration of Entity2 |
Engineer A's construction observation services for Client X |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
During the performance of the construction observation services for Client X, Engineer A observes po... [more] |
| subcontractor's work on Owner Y's adjacent project |
overlaps
Entity1 starts before Entity2 and ends during Entity2 |
Engineer A's construction observation services for Client X |
time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps |
Engineer A observes potential safety issues relating to the performance of work by a subcontractor o... [more] |
| BER precedent cases (65-12, 82-5, 88-6) |
before
Entity1 is before Entity2 |
the present case involving Engineer A |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
The NSPE Board of Ethical Review has reviewed a variety of cases over the years... The facts in the ... [more] |
| discussing the problem privately with city council members (step 2) |
before
Entity1 is before Entity2 |
being warned by the city administrator to report the problem only to him (step 3) |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
(2) discussing the problem privately with members of the city council, (3) being warned by the city ... [more] |
| being warned by the city administrator (step 3) |
before
Entity1 is before Entity2 |
discussing the problem again informally with the city council (step 4) |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
(3) being warned by the city administrator to report the problem only to him, (4) discussing the pro... [more] |
| second informal discussion with the city council (step 4) |
before
Entity1 is before Entity2 |
being relieved of responsibility for disposal of plants and beds (step 5) |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
(4) discussing the problem again informally with the city council, and (5) being relieved by the cit... [more] |
| being relieved of responsibility (step 5) |
before
Entity1 is before Entity2 |
engineer continuing to work as city engineer/director of public works |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
After (1)... (5) being relieved by the city administrator of responsibility for the disposal of plan... [more] |
| Engineer A's potential response (notifying superiors, Client X, or site superintendent) |
after
Entity1 is after Entity2 |
Engineer A's observation of the potential safety issues |
time:intervalAfter
http://www.w3.org/2006/time#intervalAfter |
Engineer A's recognition of potential safety issues in connection with the adjacent construction pro... [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.