PASS 3: Temporal Dynamics
Case 85: Incomplete Plans and Specifications – Engineer, Government, and Contractor Responsibilities
Timeline Overview
OWL-Time Temporal Structure 13 relations time: = w3.org/2006/time
Extracted Actions (7)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A's firm responds to the RFP from the small local public agency and secures the design contract through its brochure and personal interview.
Temporal Marker: Project outset, RFP and selection phase interval
Fluent Transitions:
- Design Contract In Force
Mental State: deliberate
Intended Outcome: Win the design contract for the dam project
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Dam design expertise; Proposal preparationinitiates: Design Contract In Force
descriptioncontent: Engineer A's firm responds to the RFP from the small local public agency and secures the design contract through its brochure and personal interview.hasAgentcontent: Engineer AtemporalMarkercontent: Project outset, RFP and selection phaseeventRoleContextcontent: Principal, design firmhasMentalStatecontent: deliberateintendedOutcomecontent: Win the design contract for the dam projecttextReferencescontent: Engineer A responds to an RFP from a small local public agency to build a new dam to be financed in part by a federal grant. Engineer A’s firm’s impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications.temporalExtentcontent: intervaltemporalSequencecontent: 2withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Action_Contract_Pursuit",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T13:31:41.449612+00:00",
"proeth:description": "Engineer A\u0027s firm responds to the RFP from the small local public agency and secures the design contract through its brochure and personal interview.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Principal, design firm",
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Design Contract In Force"
],
"proeth:intendedOutcome": "Win the design contract for the dam project",
"proeth:requiresCapability": [
"Dam design expertise",
"Proposal preparation"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "Project outset, RFP and selection phase",
"proeth:temporalSequence": 2,
"proeth:textReferences": [
"Engineer A responds to an RFP from a small local public agency to build a new dam to be financed in part by a federal grant. Engineer A\u2019s firm\u2019s impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications."
],
"proeth:withinCompetence": true,
"rdfs:label": "Contract Pursuit"
}
Description: Engineer A, under deadline pressure, delivers signed and sealed drawings and specifications that lack much design detail, choosing to meet the specified date rather than complete the design or request more time.
Temporal Marker: During design phase, at the specified delivery date instant
Fluent Transitions:
- Incomplete Design Documents State
Mental State: deliberate, pressured by deadline
Intended Outcome: Meet the specified delivery date for the drawings and specifications
Foreseen Unintended Effects:
- Incomplete design detail in the delivered documents
- Potential increased costs to be covered by federal funds
Obligation Engagement:
- Obligation to provide a complete set of design drawings and specifications
- Responsibility to complete plans in conformity with applicable engineering standards
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Obligation to provide a complete set of design drawings and specifications; Responsibility to complete plans in conformity with applicable engineering standardsrequiresCapability: Dam design competence; Preparation of drawings and specificationsinitiates: Incomplete Design Documents State
descriptioncontent: Engineer A, under deadline pressure, delivers signed and sealed drawings and specifications that lack much design detail, choosing to meet the specified date rather than complete the design or request more time.hasAgentcontent: Engineer AtemporalMarkercontent: During design phase, at the specified delivery dateeventRoleContextcontent: Design EngineerhasMentalStatecontent: deliberate, pressured by deadlineintendedOutcomecontent: Meet the specified delivery date for the drawings and specificationsforeseenUnintendedEffectscontent: Incomplete design detail in the delivered documents; Potential increased costs to be covered by federal fundstextReferencescontent: he felt pressured to deliver the drawings and specifications on a specified date; Engineer A had an obligation to provide a complete set of design drawings and specifications on the project in which Engineer A was engagedtemporalExtentcontent: instanttemporalSequencecontent: 4withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Action_Incomplete_Design_Delivery",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T13:31:41.450105+00:00",
"proeth:description": "Engineer A, under deadline pressure, delivers signed and sealed drawings and specifications that lack much design detail, choosing to meet the specified date rather than complete the design or request more time.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Design Engineer",
"proeth:foreseenUnintendedEffects": [
"Incomplete design detail in the delivered documents",
"Potential increased costs to be covered by federal funds"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate, pressured by deadline",
"proeth:initiates": [
"Incomplete Design Documents State"
],
"proeth:intendedOutcome": "Meet the specified delivery date for the drawings and specifications",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Dam design competence",
"Preparation of drawings and specifications"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During design phase, at the specified delivery date",
"proeth:temporalSequence": 4,
"proeth:textReferences": [
"he felt pressured to deliver the drawings and specifications on a specified date",
"Engineer A had an obligation to provide a complete set of design drawings and specifications on the project in which Engineer A was engaged"
],
"proeth:violatesObligation": [
"Obligation to provide a complete set of design drawings and specifications",
"Responsibility to complete plans in conformity with applicable engineering standards"
],
"proeth:withinCompetence": true,
"rdfs:label": "Incomplete Design Delivery"
}
Description: Engineer A does not inform anyone that the drawings and specifications are incomplete, relying on his confidence that federal funds would cover any increased costs. The case treats this omission as his conduct.
Temporal Marker: At delivery of the design documents and thereafter until the pre-construction conference interval
Fluent Transitions:
- Deceptive Concealment State
- Unjustified Public Expenditure Risk
Mental State: deliberate concealment through silence
Intended Outcome: Avoid consequences of missing the deadline while expecting federal funds to absorb increased costs
Foreseen Unintended Effects:
- Increased project costs to be covered by federal funds rather than local funding
- Bidders relying on incomplete documents
Obligation Engagement:
- Duty to avoid deceptive acts
- Responsibility to complete plans in conformity with applicable engineering standards
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Duty to avoid deceptive acts; Responsibility to complete plans in conformity with applicable engineering standardsrequiresCapability: Professional candor and disclosureinitiates: Deceptive Concealment State; Unjustified Public Expenditure Risk
descriptioncontent: Engineer A does not inform anyone that the drawings and specifications are incomplete, relying on his confidence that federal funds would cover any increased costs. The case treats this omission as his conduct.hasAgentcontent: Engineer AtemporalMarkercontent: At delivery of the design documents and thereafter until the pre-construction conferenceeventRoleContextcontent: Design EngineerhasMentalStatecontent: deliberate concealment through silenceintendedOutcomecontent: Avoid consequences of missing the deadline while expecting federal funds to absorb increased costsforeseenUnintendedEffectscontent: Increased project costs to be covered by federal funds rather than local funding; Bidders relying on incomplete documentstextReferencescontent: did not inform anyone as to their incompleteness; Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs; Engineer A’s comment about Federal funds borders on fraud and misrepresentation and is a clear violation of the NSPE CodetemporalExtentcontent: intervaltemporalSequencecontent: 5withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Action_Nondisclosure_of_Incompleteness",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T13:31:41.450161+00:00",
"proeth:description": "Engineer A does not inform anyone that the drawings and specifications are incomplete, relying on his confidence that federal funds would cover any increased costs. The case treats this omission as his conduct.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Design Engineer",
"proeth:foreseenUnintendedEffects": [
"Increased project costs to be covered by federal funds rather than local funding",
"Bidders relying on incomplete documents"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate concealment through silence",
"proeth:initiates": [
"Deceptive Concealment State",
"Unjustified Public Expenditure Risk"
],
"proeth:intendedOutcome": "Avoid consequences of missing the deadline while expecting federal funds to absorb increased costs",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Professional candor and disclosure"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "At delivery of the design documents and thereafter until the pre-construction conference",
"proeth:temporalSequence": 5,
"proeth:textReferences": [
"did not inform anyone as to their incompleteness",
"Engineer A was confident that sufficient federal funds (and not local funding) would cover any potential increased costs",
"Engineer A\u2019s comment about Federal funds borders on fraud and misrepresentation and is a clear violation of the NSPE Code"
],
"proeth:violatesObligation": [
"Duty to avoid deceptive acts",
"Responsibility to complete plans in conformity with applicable engineering standards"
],
"proeth:withinCompetence": true,
"rdfs:label": "Nondisclosure of Incompleteness"
}
Description: Engineer B of the federal funding agency approves Engineer A's signed and sealed drawings and specifications despite their incompleteness, with the local agency lacking in-house resources to review them.
Temporal Marker: Federal review phase, before advertisement for bids instant
Fluent Transitions:
- Approved Incomplete Plans State
Mental State: deliberate approval, full circumstances unknown to the Board
Intended Outcome: Approve the project documents so the project could proceed to bidding
Obligation Engagement:
- Obligation to perform services within their area of competence
- Duty to recognize lack of competency and take appropriate action, such as informing a supervisor
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Duty to recognize lack of competency and take appropriate action, such as informing a supervisorrequiresCapability: Competent review of dam design drawings and specificationsinitiates: Approved Incomplete Plans StateraisesObligation: Obligation to perform services within their area of competence
descriptioncontent: Engineer B of the federal funding agency approves Engineer A's signed and sealed drawings and specifications despite their incompleteness, with the local agency lacking in-house resources to review them.hasAgentcontent: Engineer BtemporalMarkercontent: Federal review phase, before advertisement for bidseventRoleContextcontent: Engineering staff, federal funding agencyhasMentalStatecontent: deliberate approval, full circumstances unknown to the BoardintendedOutcomecontent: Approve the project documents so the project could proceed to biddingtextReferencescontent: The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project; Engineer B’s approval of Engineer A’s incomplete plans is troubling, although we do not know all of the facts and circumstances relating to the decision to approvetemporalExtentcontent: instanttemporalSequencecontent: 6withinCompetenceassessment: False
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Action_Plan_Approval",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T13:31:41.450192+00:00",
"proeth:description": "Engineer B of the federal funding agency approves Engineer A\u0027s signed and sealed drawings and specifications despite their incompleteness, with the local agency lacking in-house resources to review them.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Engineering staff, federal funding agency",
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate approval, full circumstances unknown to the Board",
"proeth:initiates": [
"Approved Incomplete Plans State"
],
"proeth:intendedOutcome": "Approve the project documents so the project could proceed to bidding",
"proeth:raisesObligation": [
"Obligation to perform services within their area of competence"
],
"proeth:requiresCapability": [
"Competent review of dam design drawings and specifications"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Federal review phase, before advertisement for bids",
"proeth:temporalSequence": 6,
"proeth:textReferences": [
"The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project",
"Engineer B\u2019s approval of Engineer A\u2019s incomplete plans is troubling, although we do not know all of the facts and circumstances relating to the decision to approve"
],
"proeth:violatesObligation": [
"Duty to recognize lack of competency and take appropriate action, such as informing a supervisor"
],
"proeth:withinCompetence": false,
"rdfs:label": "Plan Approval"
}
Description: Engineer C, owner of Hi-Lo Construction, submits the low bid on the project after having the opportunity to review the bidding documents, presumably knowing the inadequacies of the documents and the risks involved.
Temporal Marker: Bidding phase, after advertisement for bids instant
Fluent Transitions:
- Construction Contract Awarded On Inadequate Documents
Mental State: deliberate, presumably informed of document inadequacies
Intended Outcome: Win the construction contract with the low bid
Foreseen Unintended Effects:
- Problems in attempting to build the project from inadequate documents
Obligation Engagement:
- Responsibility to reflect document inadequacies in the bid or seek clarification before bidding
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Responsibility to reflect document inadequacies in the bid or seek clarification before biddingrequiresCapability: Evaluation of engineering drawings, plans, and specifications; Construction cost estimatinginitiates: Construction Contract Awarded On Inadequate Documents
descriptioncontent: Engineer C, owner of Hi-Lo Construction, submits the low bid on the project after having the opportunity to review the bidding documents, presumably knowing the inadequacies of the documents and the risks involved.hasAgentcontent: Engineer CtemporalMarkercontent: Bidding phase, after advertisement for bidseventRoleContextcontent: Owner, Hi-Lo ConstructionhasMentalStatecontent: deliberate, presumably informed of document inadequaciesintendedOutcomecontent: Win the construction contract with the low bidforeseenUnintendedEffectscontent: Problems in attempting to build the project from inadequate documentstextReferencescontent: a contract is awarded to the low bidder, Hi-Lo Construction; Engineer C submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involvedtemporalExtentcontent: instanttemporalSequencecontent: 8withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Action_Low_Bid_Submission",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T13:31:41.450217+00:00",
"proeth:description": "Engineer C, owner of Hi-Lo Construction, submits the low bid on the project after having the opportunity to review the bidding documents, presumably knowing the inadequacies of the documents and the risks involved.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Owner, Hi-Lo Construction",
"proeth:foreseenUnintendedEffects": [
"Problems in attempting to build the project from inadequate documents"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer C",
"proeth:hasMentalState": "deliberate, presumably informed of document inadequacies",
"proeth:initiates": [
"Construction Contract Awarded On Inadequate Documents"
],
"proeth:intendedOutcome": "Win the construction contract with the low bid",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Evaluation of engineering drawings, plans, and specifications",
"Construction cost estimating"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Bidding phase, after advertisement for bids",
"proeth:temporalSequence": 8,
"proeth:textReferences": [
"a contract is awarded to the low bidder, Hi-Lo Construction",
"Engineer C submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involved"
],
"proeth:violatesObligation": [
"Responsibility to reflect document inadequacies in the bid or seek clarification before bidding"
],
"proeth:withinCompetence": true,
"rdfs:label": "Low Bid Submission"
}
Description: At the pre-construction conference, Engineer C points out that much of the design detail is lacking and declares that certain parts of the project are unbuildable without major changes, rather than having raised the issues during bidding.
Temporal Marker: Pre-construction conference instant
Fluent Transitions:
- Design Deficiencies Disclosed State
- Deceptive Concealment State
Mental State: deliberate
Intended Outcome: Put the parties on notice that major changes are needed before construction can proceed
Foreseen Unintended Effects:
- Project delay and cost increase claims
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Evaluation of engineering drawings, plans, and specificationsinitiates: Design Deficiencies Disclosed Stateterminates: Deceptive Concealment State
descriptioncontent: At the pre-construction conference, Engineer C points out that much of the design detail is lacking and declares that certain parts of the project are unbuildable without major changes, rather than having raised the issues during bidding.hasAgentcontent: Engineer CtemporalMarkercontent: Pre-construction conferenceeventRoleContextcontent: Owner, Hi-Lo ConstructionhasMentalStatecontent: deliberateintendedOutcomecontent: Put the parties on notice that major changes are needed before construction can proceedforeseenUnintendedEffectscontent: Project delay and cost increase claimstextReferencescontent: it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are “unbuildable” without major changestemporalExtentcontent: instanttemporalSequencecontent: 11withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Action_Deficiency_Disclosure",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T13:31:41.450244+00:00",
"proeth:description": "At the pre-construction conference, Engineer C points out that much of the design detail is lacking and declares that certain parts of the project are unbuildable without major changes, rather than having raised the issues during bidding.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Owner, Hi-Lo Construction",
"proeth:foreseenUnintendedEffects": [
"Project delay and cost increase claims"
],
"proeth:hasAgent": "Engineer C",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Design Deficiencies Disclosed State"
],
"proeth:intendedOutcome": "Put the parties on notice that major changes are needed before construction can proceed",
"proeth:requiresCapability": [
"Evaluation of engineering drawings, plans, and specifications"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Pre-construction conference",
"proeth:temporalSequence": 11,
"proeth:terminates": [
"Deceptive Concealment State"
],
"proeth:textReferences": [
"it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are \u201cunbuildable\u201d without major changes"
],
"proeth:withinCompetence": true,
"rdfs:label": "Deficiency Disclosure"
}
Description: Engineer A generally agrees with Hi-Lo's characterization of the documents at the pre-construction conference, but defends his conduct by citing deadline pressure and his confidence that federal funds would cover increased costs.
Temporal Marker: Pre-construction conference instant
Fluent Transitions:
- Design Incompleteness Acknowledged State
Mental State: deliberate, defensive
Intended Outcome: Acknowledge the incompleteness while deflecting blame to time pressure and expected federal funding
Obligation Engagement:
- Duty to avoid deceptive acts
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Duty to avoid deceptive actsrequiresCapability: Professional candor and disclosureinitiates: Design Incompleteness Acknowledged State
descriptioncontent: Engineer A generally agrees with Hi-Lo's characterization of the documents at the pre-construction conference, but defends his conduct by citing deadline pressure and his confidence that federal funds would cover increased costs.hasAgentcontent: Engineer AtemporalMarkercontent: Pre-construction conferenceeventRoleContextcontent: Design EngineerhasMentalStatecontent: deliberate, defensiveintendedOutcomecontent: Acknowledge the incompleteness while deflecting blame to time pressure and expected federal fundingtextReferencescontent: Engineer A generally agrees with Hi-Lo’s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date; Engineer A’s bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincingtemporalExtentcontent: instanttemporalSequencecontent: 12withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Action_Admission_With_Justification",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T13:31:41.450269+00:00",
"proeth:description": "Engineer A generally agrees with Hi-Lo\u0027s characterization of the documents at the pre-construction conference, but defends his conduct by citing deadline pressure and his confidence that federal funds would cover increased costs.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "Design Engineer",
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate, defensive",
"proeth:initiates": [
"Design Incompleteness Acknowledged State"
],
"proeth:intendedOutcome": "Acknowledge the incompleteness while deflecting blame to time pressure and expected federal funding",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Professional candor and disclosure"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Pre-construction conference",
"proeth:temporalSequence": 12,
"proeth:textReferences": [
"Engineer A generally agrees with Hi-Lo\u2019s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date",
"Engineer A\u2019s bold assertion that the work was incomplete, but that this was due to time pressures and his expectation that Federal funds would be awarded to complete the work is wholly unconvincing"
],
"proeth:violatesObligation": [
"Duty to avoid deceptive acts"
],
"proeth:withinCompetence": true,
"rdfs:label": "Admission With Justification"
}
Extracted Events (6)
Occurrences that trigger ethical considerations and state changesDescription: A small local public agency issues a request for proposals for a new dam project financed in part by a federal grant.
Temporal Marker: Beginning of the case timeline instant
Fluent Transitions:
- Project Solicitation Open
- Federal Grant Funding In Place
Field classification (triples vs literals)
initiates: Project Solicitation Open; Federal Grant Funding In Place
descriptioncontent: A small local public agency issues a request for proposals for a new dam project financed in part by a federal grant.temporalMarkercontent: Beginning of the case timelinetextReferencescontent: Engineer A responds to an RFP from a small local public agency to build a new dam to be financed in part by a federal grant.eventTypecontent: exogenoustemporalExtentcontent: instanttemporalSequencecontent: 1confidenceassessment: 0.9
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Event_RFP_Issuance",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T13:31:41.450349+00:00",
"proeth:confidence": "0.9",
"proeth:description": "A small local public agency issues a request for proposals for a new dam project financed in part by a federal grant.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "exogenous",
"proeth:initiates": [
"Project Solicitation Open",
"Federal Grant Funding In Place"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Beginning of the case timeline",
"proeth:temporalSequence": 1,
"proeth:textReferences": [
"Engineer A responds to an RFP from a small local public agency to build a new dam to be financed in part by a federal grant."
],
"rdfs:label": "RFP Issuance"
}
Description: Engineer A's firm is awarded the contract for the design, drawings, and specifications following its impressive brochure and personal interview.
Temporal Marker: After the firm's proposal and interview instant
Fluent Transitions:
- Design Contract In Force
- Engineer A Design Responsibility
- Project Solicitation Open
Caused By Action: Action_Contract_Pursuit
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/85#Action_Contract_Pursuitinitiates: Design Contract In Force; Engineer A Design Responsibilityterminates: Project Solicitation Open
descriptioncontent: Engineer A's firm is awarded the contract for the design, drawings, and specifications following its impressive brochure and personal interview.temporalMarkercontent: After the firm's proposal and interviewtextReferencescontent: Engineer A’s firm’s impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications.eventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 3confidenceassessment: 0.95
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Event_Design_Contract_Award",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T13:31:41.450383+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/85#Action_Contract_Pursuit",
"proeth:confidence": "0.95",
"proeth:description": "Engineer A\u0027s firm is awarded the contract for the design, drawings, and specifications following its impressive brochure and personal interview.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Design Contract In Force",
"Engineer A Design Responsibility"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After the firm\u0027s proposal and interview",
"proeth:temporalSequence": 3,
"proeth:terminates": [
"Project Solicitation Open"
],
"proeth:textReferences": [
"Engineer A\u2019s firm\u2019s impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications."
],
"rdfs:label": "Design Contract Award"
}
Description: Following federal approval of the signed and sealed drawings and specifications, the project is duly advertised for bids under standard procurement procedure.
Temporal Marker: After Engineer B's approval of the plans interval
Fluent Transitions:
- Bidding Open
Caused By Action: Action_Plan_Approval
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/85#Action_Plan_Approvalinitiates: Bidding Open
descriptioncontent: Following federal approval of the signed and sealed drawings and specifications, the project is duly advertised for bids under standard procurement procedure.temporalMarkercontent: After Engineer B's approval of the planstextReferencescontent: the project is thereafter duly advertised for bidseventTypecontent: automatictemporalExtentcontent: intervaltemporalSequencecontent: 7confidenceassessment: 0.88
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Event_Bid_Advertisement",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T13:31:41.450407+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/85#Action_Plan_Approval",
"proeth:confidence": "0.88",
"proeth:description": "Following federal approval of the signed and sealed drawings and specifications, the project is duly advertised for bids under standard procurement procedure.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "automatic",
"proeth:initiates": [
"Bidding Open"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "After Engineer B\u0027s approval of the plans",
"proeth:temporalSequence": 7,
"proeth:textReferences": [
"the project is thereafter duly advertised for bids"
],
"rdfs:label": "Bid Advertisement"
}
Description: The construction contract is awarded to Hi-Lo Construction as the low bidder under the low-bid selection rule.
Temporal Marker: After bidding closes instant
Fluent Transitions:
- Construction Contract In Force
- Hi-Lo Construction Obligated To Build
- Bidding Open
Caused By Action: Action_Low_Bid_Submission
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/85#Action_Low_Bid_Submissioninitiates: Construction Contract In Force; Hi-Lo Construction Obligated To Buildterminates: Bidding Open
descriptioncontent: The construction contract is awarded to Hi-Lo Construction as the low bidder under the low-bid selection rule.temporalMarkercontent: After bidding closestextReferencescontent: a contract is awarded to the low bidder, Hi-Lo ConstructioneventTypecontent: automatictemporalExtentcontent: instanttemporalSequencecontent: 9confidenceassessment: 0.9
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Event_Construction_Contract_Award",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T13:31:41.450430+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/85#Action_Low_Bid_Submission",
"proeth:confidence": "0.9",
"proeth:description": "The construction contract is awarded to Hi-Lo Construction as the low bidder under the low-bid selection rule.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "automatic",
"proeth:initiates": [
"Construction Contract In Force",
"Hi-Lo Construction Obligated To Build"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After bidding closes",
"proeth:temporalSequence": 9,
"proeth:terminates": [
"Bidding Open"
],
"proeth:textReferences": [
"a contract is awarded to the low bidder, Hi-Lo Construction"
],
"rdfs:label": "Construction Contract Award"
}
Description: The scheduled pre-construction conference convenes, providing the setting in which Engineer C discloses the design deficiencies and Engineer A admits the incompleteness.
Temporal Marker: After contract award, before construction begins interval
Fluent Transitions:
- Parties Convened For Construction Coordination
Field classification (triples vs literals)
initiates: Parties Convened For Construction Coordination
descriptioncontent: The scheduled pre-construction conference convenes, providing the setting in which Engineer C discloses the design deficiencies and Engineer A admits the incompleteness.temporalMarkercontent: After contract award, before construction beginstextReferencescontent: At the pre-construction conference, it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specificationseventTypecontent: automatictemporalExtentcontent: intervaltemporalSequencecontent: 10confidenceassessment: 0.8
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Event_Pre-Construction_Conference",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T13:31:41.450451+00:00",
"proeth:confidence": "0.8",
"proeth:description": "The scheduled pre-construction conference convenes, providing the setting in which Engineer C discloses the design deficiencies and Engineer A admits the incompleteness.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "automatic",
"proeth:initiates": [
"Parties Convened For Construction Coordination"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "After contract award, before construction begins",
"proeth:temporalSequence": 10,
"proeth:textReferences": [
"At the pre-construction conference, it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications"
],
"rdfs:label": "Pre-Construction Conference"
}
Description: The incompleteness of the drawings and specifications becomes known to the project parties, with certain parts of the project declared unbuildable without major changes, ending the concealment of the deficiencies.
Temporal Marker: At the pre-construction conference instant
Fluent Transitions:
- Design Incompleteness Known
- Project Buildability In Question
- Design Incompleteness Concealed
Caused By Action: Action_Deficiency_Disclosure
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/85#Action_Deficiency_Disclosureinitiates: Design Incompleteness Known; Project Buildability In Questionterminates: Design Incompleteness Concealed
descriptioncontent: The incompleteness of the drawings and specifications becomes known to the project parties, with certain parts of the project declared unbuildable without major changes, ending the concealment of the deficiencies.temporalMarkercontent: At the pre-construction conferencetextReferencescontent: Hi-Lo Construction declares that certain parts of the project are “unbuildable” without major changeseventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 13confidenceassessment: 0.87
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#Event_Design_Deficiency_Revealed",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T13:31:41.450476+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/85#Action_Deficiency_Disclosure",
"proeth:confidence": "0.87",
"proeth:description": "The incompleteness of the drawings and specifications becomes known to the project parties, with certain parts of the project declared unbuildable without major changes, ending the concealment of the deficiencies.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Design Incompleteness Known",
"Project Buildability In Question"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "At the pre-construction conference",
"proeth:temporalSequence": 13,
"proeth:terminates": [
"Design Incompleteness Concealed"
],
"proeth:textReferences": [
"Hi-Lo Construction declares that certain parts of the project are \u201cunbuildable\u201d without major changes"
],
"rdfs:label": "Design Deficiency Revealed"
}
Causal Chains (9)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: Engineer A’s firm’s impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications.
Necessary Factors (NESS):
- Engineer A's firm responding to the RFP
- Impressive brochure and personal interview presentation
- Agency's selection process based on qualifications presentation
Sufficient Factors:
- Combination of RFP response + persuasive brochure + successful interview was enough to win the award
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
RFP Issuance
Small local public agency issues RFP for a federally funded dam project -
Contract Pursuit
Engineer A's firm responds with impressive brochure and personal interview -
Design Contract Award
Firm is awarded the contract for design, drawings, and specifications
Field classification (triples vs literals)
cause: Contract Pursuiteffect: Design Contract AwardresponsibleAgent: Engineer A
causalLanguagecontent: Engineer A’s firm’s impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications.necessaryFactorscontent: Engineer A's firm responding to the RFP; Impressive brochure and personal interview presentation; Agency's selection process based on qualifications presentationsufficientFactorscontent: Combination of RFP response + persuasive brochure + successful interview was enough to win the awardcounterfactualcontent: Without Engineer A's pursuit and impressive presentation, the contract would have gone to another firm and Engineer A would not have been in a position to produce deficient plansagentKnowledgecontent: Engineer A knew the firm was presenting itself as capable of performing the full design within project time parametersinterveningFactorscontent: Local agency lacked in-house technical resources to independently vet the firm's capabilitycausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'RFP Issuance', 'proeth:description': 'Small local public agency issues RFP for a federally funded dam project'}; {'proeth:step': 2, 'proeth:element': 'Contract Pursuit', 'proeth:description': "Engineer A's firm responds with impressive brochure and personal interview"}; {'proeth:step': 3, 'proeth:element': 'Design Contract Award', 'proeth:description': 'Firm is awarded the contract for design, drawings, and specifications'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_1",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450532+00:00",
"proeth:agentKnowledge": "Engineer A knew the firm was presenting itself as capable of performing the full design within project time parameters",
"proeth:causalLanguage": "Engineer A\u2019s firm\u2019s impressive brochure and personal interview results in the award of a contract for the design, drawings, and specifications.",
"proeth:causalSequence": [
{
"proeth:description": "Small local public agency issues RFP for a federally funded dam project",
"proeth:element": "RFP Issuance",
"proeth:step": 1
},
{
"proeth:description": "Engineer A\u0027s firm responds with impressive brochure and personal interview",
"proeth:element": "Contract Pursuit",
"proeth:step": 2
},
{
"proeth:description": "Firm is awarded the contract for design, drawings, and specifications",
"proeth:element": "Design Contract Award",
"proeth:step": 3
}
],
"proeth:cause": "Contract Pursuit",
"proeth:counterfactual": "Without Engineer A\u0027s pursuit and impressive presentation, the contract would have gone to another firm and Engineer A would not have been in a position to produce deficient plans",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Design Contract Award",
"proeth:interveningFactors": [
"Local agency lacked in-house technical resources to independently vet the firm\u0027s capability"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s firm responding to the RFP",
"Impressive brochure and personal interview presentation",
"Agency\u0027s selection process based on qualifications presentation"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Combination of RFP response + persuasive brochure + successful interview was enough to win the award"
],
"proeth:withinAgentControl": true
}
Causal Language: he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness
Necessary Factors (NESS):
- Contract obligating Engineer A to deliver complete design by a specified date
- Time/deadline pressure
- Engineer A's decision to seal and deliver despite incompleteness
Sufficient Factors:
- Deadline pressure + Engineer A's willingness to submit incomplete work + reliance on anticipated federal funds
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Design Contract Award
Engineer A's firm assumes obligation to provide the complete design -
Deadline Pressure
Engineer A feels pressured to deliver drawings and specifications on a specified date -
Incomplete Design Delivery
Engineer A signs and seals drawings and specifications lacking major design detail
Field classification (triples vs literals)
cause: Design Contract Awardeffect: Incomplete Design DeliveryresponsibleAgent: Engineer A
causalLanguagecontent: he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompletenessnecessaryFactorscontent: Contract obligating Engineer A to deliver complete design by a specified date; Time/deadline pressure; Engineer A's decision to seal and deliver despite incompletenesssufficientFactorscontent: Deadline pressure + Engineer A's willingness to submit incomplete work + reliance on anticipated federal fundscounterfactualcontent: Had Engineer A managed the schedule competently or requested more time, complete drawings and specifications would likely have been delivered; the award itself did not compel incomplete delivery, so Engineer A's choice was the operative element within the sufficient setagentKnowledgecontent: Engineer A knew the drawings and specifications were incomplete at the time of deliveryinterveningFactorscontent: Specified delivery date creating schedule pressurecausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Design Contract Award', 'proeth:description': "Engineer A's firm assumes obligation to provide the complete design"}; {'proeth:step': 2, 'proeth:element': 'Deadline Pressure', 'proeth:description': 'Engineer A feels pressured to deliver drawings and specifications on a specified date'}; {'proeth:step': 3, 'proeth:element': 'Incomplete Design Delivery', 'proeth:description': 'Engineer A signs and seals drawings and specifications lacking major design detail'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_2",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450561+00:00",
"proeth:agentKnowledge": "Engineer A knew the drawings and specifications were incomplete at the time of delivery",
"proeth:causalLanguage": "he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A\u0027s firm assumes obligation to provide the complete design",
"proeth:element": "Design Contract Award",
"proeth:step": 1
},
{
"proeth:description": "Engineer A feels pressured to deliver drawings and specifications on a specified date",
"proeth:element": "Deadline Pressure",
"proeth:step": 2
},
{
"proeth:description": "Engineer A signs and seals drawings and specifications lacking major design detail",
"proeth:element": "Incomplete Design Delivery",
"proeth:step": 3
}
],
"proeth:cause": "Design Contract Award",
"proeth:counterfactual": "Had Engineer A managed the schedule competently or requested more time, complete drawings and specifications would likely have been delivered; the award itself did not compel incomplete delivery, so Engineer A\u0027s choice was the operative element within the sufficient set",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Incomplete Design Delivery",
"proeth:interveningFactors": [
"Specified delivery date creating schedule pressure"
],
"proeth:necessaryFactors": [
"Contract obligating Engineer A to deliver complete design by a specified date",
"Time/deadline pressure",
"Engineer A\u0027s decision to seal and deliver despite incompleteness"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Deadline pressure + Engineer A\u0027s willingness to submit incomplete work + reliance on anticipated federal funds"
],
"proeth:withinAgentControl": true
}
Causal Language: The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project
Necessary Factors (NESS):
- Submission of signed and sealed documents that appeared to be a final deliverable
- Engineer B's review failing to detect or act on the incompleteness
- Absence of any disclosure of incompleteness by Engineer A
Sufficient Factors:
- Sealed submission presented as complete + inadequate federal review + no local agency technical review capacity
Responsibility Attribution:
Agent: Engineer B (with Engineer A as contributing agent)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Incomplete Design Delivery
Engineer A submits signed and sealed but incomplete drawings and specifications -
Federal Agency Review
Engineer B reviews the documents despite possible lack of competency for the review -
Plan Approval
Engineer B approves the incomplete plans
Field classification (triples vs literals)
cause: Incomplete Design Deliveryeffect: Plan ApprovalresponsibleAgent: Engineer B (with Engineer A as contributing agent)
causalLanguagecontent: The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the projectnecessaryFactorscontent: Submission of signed and sealed documents that appeared to be a final deliverable; Engineer B's review failing to detect or act on the incompleteness; Absence of any disclosure of incompleteness by Engineer AsufficientFactorscontent: Sealed submission presented as complete + inadequate federal review + no local agency technical review capacitycounterfactualcontent: Had the documents not been delivered as ostensibly complete sealed plans, there would have been nothing for Engineer B to approve; a competent review could still have blocked approval, making Engineer B's failure a co-contributoragentKnowledgecontent: Engineer B may have lacked competence to perform the review; per the Board, 'the failure to recognize the lack of competency and take appropriate action to address the situation is a violation of the NSPE Code'interveningFactorscontent: The local public agency does not have the in-house technical resources to review the drawings and specificationscausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Incomplete Design Delivery', 'proeth:description': 'Engineer A submits signed and sealed but incomplete drawings and specifications'}; {'proeth:step': 2, 'proeth:element': 'Federal Agency Review', 'proeth:description': 'Engineer B reviews the documents despite possible lack of competency for the review'}; {'proeth:step': 3, 'proeth:element': 'Plan Approval', 'proeth:description': 'Engineer B approves the incomplete plans'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_3",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450583+00:00",
"proeth:agentKnowledge": "Engineer B may have lacked competence to perform the review; per the Board, \u0027the failure to recognize the lack of competency and take appropriate action to address the situation is a violation of the NSPE Code\u0027",
"proeth:causalLanguage": "The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engineering staff of the federal agency funding the project",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A submits signed and sealed but incomplete drawings and specifications",
"proeth:element": "Incomplete Design Delivery",
"proeth:step": 1
},
{
"proeth:description": "Engineer B reviews the documents despite possible lack of competency for the review",
"proeth:element": "Federal Agency Review",
"proeth:step": 2
},
{
"proeth:description": "Engineer B approves the incomplete plans",
"proeth:element": "Plan Approval",
"proeth:step": 3
}
],
"proeth:cause": "Incomplete Design Delivery",
"proeth:counterfactual": "Had the documents not been delivered as ostensibly complete sealed plans, there would have been nothing for Engineer B to approve; a competent review could still have blocked approval, making Engineer B\u0027s failure a co-contributor",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Plan Approval",
"proeth:interveningFactors": [
"The local public agency does not have the in-house technical resources to review the drawings and specifications"
],
"proeth:necessaryFactors": [
"Submission of signed and sealed documents that appeared to be a final deliverable",
"Engineer B\u0027s review failing to detect or act on the incompleteness",
"Absence of any disclosure of incompleteness by Engineer A"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer B (with Engineer A as contributing agent)",
"proeth:sufficientFactors": [
"Sealed submission presented as complete + inadequate federal review + no local agency technical review capacity"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A generally agrees with Hi-Lo’s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.
Necessary Factors (NESS):
- Engineer A's silence about the missing design detail
- No party with knowledge of the deficiencies until the contractor's review
- Progression of the project to construction phase before discovery
Sufficient Factors:
- Concealment by Engineer A + approval by Engineer B + award to a contractor who examined the documents ensured the deficiencies would surface only at the pre-construction stage
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Nondisclosure of Incompleteness
Engineer A informs no one that the sealed documents are incomplete -
Plan Approval
Engineer B approves the plans without detecting deficiencies -
Construction Contract Award
Contract awarded to Hi-Lo based on the deficient documents -
Pre-Construction Conference
Parties convene before construction begins -
Design Deficiency Revealed
Incompleteness and 'unbuildable' portions become known to all parties
Field classification (triples vs literals)
cause: Nondisclosure of Incompletenesseffect: Design Deficiency RevealedresponsibleAgent: Engineer A
causalLanguagecontent: Engineer A generally agrees with Hi-Lo’s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.necessaryFactorscontent: Engineer A's silence about the missing design detail; No party with knowledge of the deficiencies until the contractor's review; Progression of the project to construction phase before discoverysufficientFactorscontent: Concealment by Engineer A + approval by Engineer B + award to a contractor who examined the documents ensured the deficiencies would surface only at the pre-construction stagecounterfactualcontent: Had Engineer A informed the owner or federal agency of the incompleteness, the deficiency would have been revealed before advertisement and bidding, not at the pre-construction conferenceagentKnowledgecontent: Engineer A knew the information was missing and 'was confident that sufficient federal funds (and not local funding) would cover any potential increased costs'interveningFactorscontent: Engineer B's approval lending apparent legitimacy to the documents; Local agency's inability to reviewcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Nondisclosure of Incompleteness', 'proeth:description': 'Engineer A informs no one that the sealed documents are incomplete'}; {'proeth:step': 2, 'proeth:element': 'Plan Approval', 'proeth:description': 'Engineer B approves the plans without detecting deficiencies'}; {'proeth:step': 3, 'proeth:element': 'Construction Contract Award', 'proeth:description': 'Contract awarded to Hi-Lo based on the deficient documents'}; {'proeth:step': 4, 'proeth:element': 'Pre-Construction Conference', 'proeth:description': 'Parties convene before construction begins'}; {'proeth:step': 5, 'proeth:element': 'Design Deficiency Revealed', 'proeth:description': "Incompleteness and 'unbuildable' portions become known to all parties"}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_4",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450603+00:00",
"proeth:agentKnowledge": "Engineer A knew the information was missing and \u0027was confident that sufficient federal funds (and not local funding) would cover any potential increased costs\u0027",
"proeth:causalLanguage": "Engineer A generally agrees with Hi-Lo\u2019s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date, but did not inform anyone as to their incompleteness.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A informs no one that the sealed documents are incomplete",
"proeth:element": "Nondisclosure of Incompleteness",
"proeth:step": 1
},
{
"proeth:description": "Engineer B approves the plans without detecting deficiencies",
"proeth:element": "Plan Approval",
"proeth:step": 2
},
{
"proeth:description": "Contract awarded to Hi-Lo based on the deficient documents",
"proeth:element": "Construction Contract Award",
"proeth:step": 3
},
{
"proeth:description": "Parties convene before construction begins",
"proeth:element": "Pre-Construction Conference",
"proeth:step": 4
},
{
"proeth:description": "Incompleteness and \u0027unbuildable\u0027 portions become known to all parties",
"proeth:element": "Design Deficiency Revealed",
"proeth:step": 5
}
],
"proeth:cause": "Nondisclosure of Incompleteness",
"proeth:counterfactual": "Had Engineer A informed the owner or federal agency of the incompleteness, the deficiency would have been revealed before advertisement and bidding, not at the pre-construction conference",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Design Deficiency Revealed",
"proeth:interveningFactors": [
"Engineer B\u0027s approval lending apparent legitimacy to the documents",
"Local agency\u0027s inability to review"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s silence about the missing design detail",
"No party with knowledge of the deficiencies until the contractor\u0027s review",
"Progression of the project to construction phase before discovery"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Concealment by Engineer A + approval by Engineer B + award to a contractor who examined the documents ensured the deficiencies would surface only at the pre-construction stage"
],
"proeth:withinAgentControl": true
}
Causal Language: the project is thereafter duly advertised for bids and a contract is awarded to the low bidder, Hi-Lo Construction
Necessary Factors (NESS):
- Federal agency approval of the signed and sealed documents
- Federal grant funding contingent on that approval
- Owner's decision to proceed to procurement
Sufficient Factors:
- Approval by the funding agency + owner's procurement process was enough to trigger advertisement
Responsibility Attribution:
Agent: Engineer B
Type: indirect
Within Agent Control:
Yes
Causal Sequence:
-
Plan Approval
Engineer B approves the incomplete plans on behalf of the funding agency -
Bid Advertisement
The project is duly advertised for bids based on the approved documents
Field classification (triples vs literals)
cause: Plan Approvaleffect: Bid AdvertisementresponsibleAgent: Engineer B
causalLanguagecontent: the project is thereafter duly advertised for bids and a contract is awarded to the low bidder, Hi-Lo ConstructionnecessaryFactorscontent: Federal agency approval of the signed and sealed documents; Federal grant funding contingent on that approval; Owner's decision to proceed to procurementsufficientFactorscontent: Approval by the funding agency + owner's procurement process was enough to trigger advertisementcounterfactualcontent: Without Engineer B's approval, the federally funded project would not have been advertised for bids on incomplete documentsagentKnowledgecontent: Unknown whether Engineer B recognized the deficiencies; the Board notes 'we do not know all of the facts and circumstances relating to the decision to approve'interveningFactorscontent: Local agency's lack of in-house technical review capacitycausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Plan Approval', 'proeth:description': 'Engineer B approves the incomplete plans on behalf of the funding agency'}; {'proeth:step': 2, 'proeth:element': 'Bid Advertisement', 'proeth:description': 'The project is duly advertised for bids based on the approved documents'}responsibilityTypeassessment: indirectwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_5",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450625+00:00",
"proeth:agentKnowledge": "Unknown whether Engineer B recognized the deficiencies; the Board notes \u0027we do not know all of the facts and circumstances relating to the decision to approve\u0027",
"proeth:causalLanguage": "the project is thereafter duly advertised for bids and a contract is awarded to the low bidder, Hi-Lo Construction",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B approves the incomplete plans on behalf of the funding agency",
"proeth:element": "Plan Approval",
"proeth:step": 1
},
{
"proeth:description": "The project is duly advertised for bids based on the approved documents",
"proeth:element": "Bid Advertisement",
"proeth:step": 2
}
],
"proeth:cause": "Plan Approval",
"proeth:counterfactual": "Without Engineer B\u0027s approval, the federally funded project would not have been advertised for bids on incomplete documents",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Bid Advertisement",
"proeth:interveningFactors": [
"Local agency\u0027s lack of in-house technical review capacity"
],
"proeth:necessaryFactors": [
"Federal agency approval of the signed and sealed documents",
"Federal grant funding contingent on that approval",
"Owner\u0027s decision to proceed to procurement"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"Approval by the funding agency + owner\u0027s procurement process was enough to trigger advertisement"
],
"proeth:withinAgentControl": true
}
Causal Language: Presumably, Engineer C had an opportunity to review the bidding documents which included appropriate engineering drawings, plans, and specifications.
Necessary Factors (NESS):
- Public advertisement making bid documents available
- Engineer C's decision to bid despite reviewable inadequacies
- Low-bid procurement framework
Sufficient Factors:
- Advertisement + Engineer C's willingness to bid low 'presumably knowing inadequacies of the documents as well as the obvious risks involved'
Responsibility Attribution:
Agent: Engineer C
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Bid Advertisement
Project advertised with incomplete drawings and specifications -
Bid Document Review
Engineer C has the opportunity to review the deficient bidding documents -
Low Bid Submission
Engineer C submits the low bid despite knowable inadequacies and risks
Field classification (triples vs literals)
cause: Bid Advertisementeffect: Low Bid SubmissionresponsibleAgent: Engineer C
causalLanguagecontent: Presumably, Engineer C had an opportunity to review the bidding documents which included appropriate engineering drawings, plans, and specifications.necessaryFactorscontent: Public advertisement making bid documents available; Engineer C's decision to bid despite reviewable inadequacies; Low-bid procurement frameworksufficientFactorscontent: Advertisement + Engineer C's willingness to bid low 'presumably knowing inadequacies of the documents as well as the obvious risks involved'counterfactualcontent: Without the advertisement there could be no bid; and had Engineer C priced the inadequacies or sought clarification, the low bid as submitted would likely not have occurredagentKnowledgecontent: As an engineer and contractor, Engineer C 'had the necessary background and experience to carefully evaluate the engineering drawings' and presumably knew the documents were inadequateinterveningFactorscontent: Incomplete documents produced by Engineer A; Competitive low-bid selection processcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Bid Advertisement', 'proeth:description': 'Project advertised with incomplete drawings and specifications'}; {'proeth:step': 2, 'proeth:element': 'Bid Document Review', 'proeth:description': 'Engineer C has the opportunity to review the deficient bidding documents'}; {'proeth:step': 3, 'proeth:element': 'Low Bid Submission', 'proeth:description': 'Engineer C submits the low bid despite knowable inadequacies and risks'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_6",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450644+00:00",
"proeth:agentKnowledge": "As an engineer and contractor, Engineer C \u0027had the necessary background and experience to carefully evaluate the engineering drawings\u0027 and presumably knew the documents were inadequate",
"proeth:causalLanguage": "Presumably, Engineer C had an opportunity to review the bidding documents which included appropriate engineering drawings, plans, and specifications.",
"proeth:causalSequence": [
{
"proeth:description": "Project advertised with incomplete drawings and specifications",
"proeth:element": "Bid Advertisement",
"proeth:step": 1
},
{
"proeth:description": "Engineer C has the opportunity to review the deficient bidding documents",
"proeth:element": "Bid Document Review",
"proeth:step": 2
},
{
"proeth:description": "Engineer C submits the low bid despite knowable inadequacies and risks",
"proeth:element": "Low Bid Submission",
"proeth:step": 3
}
],
"proeth:cause": "Bid Advertisement",
"proeth:counterfactual": "Without the advertisement there could be no bid; and had Engineer C priced the inadequacies or sought clarification, the low bid as submitted would likely not have occurred",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Low Bid Submission",
"proeth:interveningFactors": [
"Incomplete documents produced by Engineer A",
"Competitive low-bid selection process"
],
"proeth:necessaryFactors": [
"Public advertisement making bid documents available",
"Engineer C\u0027s decision to bid despite reviewable inadequacies",
"Low-bid procurement framework"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer C",
"proeth:sufficientFactors": [
"Advertisement + Engineer C\u0027s willingness to bid low \u0027presumably knowing inadequacies of the documents as well as the obvious risks involved\u0027"
],
"proeth:withinAgentControl": true
}
Causal Language: a contract is awarded to the low bidder, Hi-Lo Construction
Necessary Factors (NESS):
- Hi-Lo's bid being the lowest submitted
- Low-bid award rules governing public procurement
- Owner's acceptance of the bid
Sufficient Factors:
- Lowest responsive bid + mandatory low-bid selection was enough to secure the award
Responsibility Attribution:
Agent: Engineer C (with the local public agency administering the award)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Low Bid Submission
Engineer C submits the lowest bid on the deficient documents -
Construction Contract Award
Contract awarded to Hi-Lo Construction under low-bid selection
Field classification (triples vs literals)
cause: Low Bid Submissioneffect: Construction Contract AwardresponsibleAgent: Engineer C (with the local public agency administering the award)
causalLanguagecontent: a contract is awarded to the low bidder, Hi-Lo ConstructionnecessaryFactorscontent: Hi-Lo's bid being the lowest submitted; Low-bid award rules governing public procurement; Owner's acceptance of the bidsufficientFactorscontent: Lowest responsive bid + mandatory low-bid selection was enough to secure the awardcounterfactualcontent: Had Hi-Lo not submitted the low bid, another contractor would have received the award, and Engineer C would not have encountered the buildability problemsagentKnowledgecontent: Engineer C 'submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involved'interveningFactorscontent: Owner's lack of technical resources to screen the documents or bids for feasibilitycausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Low Bid Submission', 'proeth:description': 'Engineer C submits the lowest bid on the deficient documents'}; {'proeth:step': 2, 'proeth:element': 'Construction Contract Award', 'proeth:description': 'Contract awarded to Hi-Lo Construction under low-bid selection'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_7",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450661+00:00",
"proeth:agentKnowledge": "Engineer C \u0027submitted the low bid on the project, presumably knowing inadequacies of the documents as well as the obvious risks involved\u0027",
"proeth:causalLanguage": "a contract is awarded to the low bidder, Hi-Lo Construction",
"proeth:causalSequence": [
{
"proeth:description": "Engineer C submits the lowest bid on the deficient documents",
"proeth:element": "Low Bid Submission",
"proeth:step": 1
},
{
"proeth:description": "Contract awarded to Hi-Lo Construction under low-bid selection",
"proeth:element": "Construction Contract Award",
"proeth:step": 2
}
],
"proeth:cause": "Low Bid Submission",
"proeth:counterfactual": "Had Hi-Lo not submitted the low bid, another contractor would have received the award, and Engineer C would not have encountered the buildability problems",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Construction Contract Award",
"proeth:interveningFactors": [
"Owner\u0027s lack of technical resources to screen the documents or bids for feasibility"
],
"proeth:necessaryFactors": [
"Hi-Lo\u0027s bid being the lowest submitted",
"Low-bid award rules governing public procurement",
"Owner\u0027s acceptance of the bid"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Engineer C (with the local public agency administering the award)",
"proeth:sufficientFactors": [
"Lowest responsive bid + mandatory low-bid selection was enough to secure the award"
],
"proeth:withinAgentControl": true
}
Causal Language: At the pre-construction conference, it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are “unbuildable” without major changes.
Necessary Factors (NESS):
- Convening of the pre-construction conference as a forum
- Engineer C's detailed knowledge of the documents' inadequacies
- Engineer C's decision to raise the issue
Sufficient Factors:
- Conference forum + Engineer C's knowledge of missing design detail was enough to produce the disclosure
Responsibility Attribution:
Agent: Engineer C
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Construction Contract Award
Hi-Lo becomes the contractor obligated to build from the deficient documents -
Pre-Construction Conference
Scheduled conference convenes with all project parties -
Deficiency Disclosure
Engineer C declares design detail lacking and parts of the project unbuildable -
Admission With Justification
Engineer A agrees with the characterization, citing deadline pressure and expected federal funds -
Design Deficiency Revealed
Incompleteness becomes known to all project parties
Field classification (triples vs literals)
cause: Pre-Construction Conferenceeffect: Deficiency DisclosureresponsibleAgent: Engineer C
causalLanguagecontent: At the pre-construction conference, it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are “unbuildable” without major changes.necessaryFactorscontent: Convening of the pre-construction conference as a forum; Engineer C's detailed knowledge of the documents' inadequacies; Engineer C's decision to raise the issuesufficientFactorscontent: Conference forum + Engineer C's knowledge of missing design detail was enough to produce the disclosurecounterfactualcontent: The deficiencies would eventually have surfaced during construction, but the conference provided the setting for disclosure before work began; without it, discovery would likely have been later and more costlyagentKnowledgecontent: Engineer C knew from reviewing the documents that much of the design detail was lacking and parts were unbuildableinterveningFactorscontent: Timing of the conference after contract award rather than before biddingcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Construction Contract Award', 'proeth:description': 'Hi-Lo becomes the contractor obligated to build from the deficient documents'}; {'proeth:step': 2, 'proeth:element': 'Pre-Construction Conference', 'proeth:description': 'Scheduled conference convenes with all project parties'}; {'proeth:step': 3, 'proeth:element': 'Deficiency Disclosure', 'proeth:description': 'Engineer C declares design detail lacking and parts of the project unbuildable'}; {'proeth:step': 4, 'proeth:element': 'Admission With Justification', 'proeth:description': 'Engineer A agrees with the characterization, citing deadline pressure and expected federal funds'}; {'proeth:step': 5, 'proeth:element': 'Design Deficiency Revealed', 'proeth:description': 'Incompleteness becomes known to all project parties'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_8",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450679+00:00",
"proeth:agentKnowledge": "Engineer C knew from reviewing the documents that much of the design detail was lacking and parts were unbuildable",
"proeth:causalLanguage": "At the pre-construction conference, it is pointed out by Engineer C, owner of Hi-Lo Construction, that much of the design detail is lacking in the drawings and specifications and that Hi-Lo Construction declares that certain parts of the project are \u201cunbuildable\u201d without major changes.",
"proeth:causalSequence": [
{
"proeth:description": "Hi-Lo becomes the contractor obligated to build from the deficient documents",
"proeth:element": "Construction Contract Award",
"proeth:step": 1
},
{
"proeth:description": "Scheduled conference convenes with all project parties",
"proeth:element": "Pre-Construction Conference",
"proeth:step": 2
},
{
"proeth:description": "Engineer C declares design detail lacking and parts of the project unbuildable",
"proeth:element": "Deficiency Disclosure",
"proeth:step": 3
},
{
"proeth:description": "Engineer A agrees with the characterization, citing deadline pressure and expected federal funds",
"proeth:element": "Admission With Justification",
"proeth:step": 4
},
{
"proeth:description": "Incompleteness becomes known to all project parties",
"proeth:element": "Design Deficiency Revealed",
"proeth:step": 5
}
],
"proeth:cause": "Pre-Construction Conference",
"proeth:counterfactual": "The deficiencies would eventually have surfaced during construction, but the conference provided the setting for disclosure before work began; without it, discovery would likely have been later and more costly",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Deficiency Disclosure",
"proeth:interveningFactors": [
"Timing of the conference after contract award rather than before bidding"
],
"proeth:necessaryFactors": [
"Convening of the pre-construction conference as a forum",
"Engineer C\u0027s detailed knowledge of the documents\u0027 inadequacies",
"Engineer C\u0027s decision to raise the issue"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer C",
"proeth:sufficientFactors": [
"Conference forum + Engineer C\u0027s knowledge of missing design detail was enough to produce the disclosure"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A generally agrees with Hi-Lo’s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date
Necessary Factors (NESS):
- Engineer C's public identification of the missing design detail
- Engineer A's presence at the conference
- Engineer A's inability to credibly deny the documented deficiencies
Sufficient Factors:
- Direct confrontation with accurate deficiency claims at the conference was enough to elicit Engineer A's admission
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Deficiency Disclosure
Engineer C points out lacking design detail and unbuildable elements -
Admission With Justification
Engineer A agrees but defends himself citing time pressure and expected federal funds
Field classification (triples vs literals)
cause: Deficiency Disclosureeffect: Admission With JustificationresponsibleAgent: Engineer A
causalLanguagecontent: Engineer A generally agrees with Hi-Lo’s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified datenecessaryFactorscontent: Engineer C's public identification of the missing design detail; Engineer A's presence at the conference; Engineer A's inability to credibly deny the documented deficienciessufficientFactorscontent: Direct confrontation with accurate deficiency claims at the conference was enough to elicit Engineer A's admissioncounterfactualcontent: Without Engineer C's disclosure, Engineer A would have had no occasion to admit the incompleteness, having previously 'not inform[ed] anyone as to their incompleteness'agentKnowledgecontent: Engineer A had known all along the documents were incomplete; the Board finds the justification 'wholly unconvincing' and the federal-funds rationale 'borders on fraud and misrepresentation'interveningFactorscontent: Engineer C's confrontation forcing acknowledgmentcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Deficiency Disclosure', 'proeth:description': 'Engineer C points out lacking design detail and unbuildable elements'}; {'proeth:step': 2, 'proeth:element': 'Admission With Justification', 'proeth:description': 'Engineer A agrees but defends himself citing time pressure and expected federal funds'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/85#",
"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/85#CausalChain_9",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T13:31:41.450697+00:00",
"proeth:agentKnowledge": "Engineer A had known all along the documents were incomplete; the Board finds the justification \u0027wholly unconvincing\u0027 and the federal-funds rationale \u0027borders on fraud and misrepresentation\u0027",
"proeth:causalLanguage": "Engineer A generally agrees with Hi-Lo\u2019s characterization, but in his defense responds that he felt pressured to deliver the drawings and specifications on a specified date",
"proeth:causalSequence": [
{
"proeth:description": "Engineer C points out lacking design detail and unbuildable elements",
"proeth:element": "Deficiency Disclosure",
"proeth:step": 1
},
{
"proeth:description": "Engineer A agrees but defends himself citing time pressure and expected federal funds",
"proeth:element": "Admission With Justification",
"proeth:step": 2
}
],
"proeth:cause": "Deficiency Disclosure",
"proeth:counterfactual": "Without Engineer C\u0027s disclosure, Engineer A would have had no occasion to admit the incompleteness, having previously \u0027not inform[ed] anyone as to their incompleteness\u0027",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Admission With Justification",
"proeth:interveningFactors": [
"Engineer C\u0027s confrontation forcing acknowledgment"
],
"proeth:necessaryFactors": [
"Engineer C\u0027s public identification of the missing design detail",
"Engineer A\u0027s presence at the conference",
"Engineer A\u0027s inability to credibly deny the documented deficiencies"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Direct confrontation with accurate deficiency claims at the conference was enough to elicit Engineer A\u0027s admission"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (13)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| RFP issuance by local public agency |
before
Entity1 is before Entity2 |
award of design contract to Engineer A's firm |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A responds to an RFP from a small local public agency... Engineer A's firm's impressive bro... [more] |
| brochure submission and personal interview |
before
Entity1 is before Entity2 |
award of design contract |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A's firm's impressive brochure and personal interview results in the award of a contract |
| delivery of signed and sealed drawings and specifications |
before
Entity1 is before Entity2 |
Engineer B's approval |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
The signed and sealed drawings and specifications are ultimately approved by Engineer B |
| Engineer B's approval of drawings and specifications |
before
Entity1 is before Entity2 |
advertisement of project for bids |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
the project is thereafter duly advertised for bids |
| advertisement for bids |
before
Entity1 is before Entity2 |
contract award to Hi-Lo Construction |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
the project is thereafter duly advertised for bids and a contract is awarded to the low bidder, Hi-L... [more] |
| contract award to Hi-Lo Construction |
before
Entity1 is before Entity2 |
pre-construction conference |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
a contract is awarded to the low bidder, Hi-Lo Construction. At the pre-construction conference, it ... [more] |
| Engineer C's revelation of design inadequacies |
during
Entity1 occurs entirely within the duration of Entity2 |
pre-construction conference |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
At the pre-construction conference, it is pointed out by Engineer C, owner of Hi-Lo Construction, th... [more] |
| Engineer A's admission of incompleteness |
during
Entity1 occurs entirely within the duration of Entity2 |
pre-construction conference |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt ... [more] |
| pre-construction conference |
before
Entity1 is before Entity2 |
construction of the dam project |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
At the pre-construction conference... certain parts of the project are 'unbuildable' without major c... [more] |
| Engineer A's failure to disclose incompleteness |
during
Entity1 occurs entirely within the duration of Entity2 |
period between document delivery and pre-construction conference |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
but did not inform anyone as to their incompleteness |
| Engineer C's opportunity to review bidding documents |
before
Entity1 is before Entity2 |
Engineer C's bid submission |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Presumably, Engineer C had an opportunity to review the bidding documents... Engineer C submitted th... [more] |
| Engineer C's bid submission |
before
Entity1 is before Entity2 |
problems encountered in attempting to build the project |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer C had no one to fault but himself for the problems Engineer C encountered in attempting to ... [more] |
| deadline pressure on Engineer A |
overlaps
Entity1 starts before Entity2 and ends during Entity2 |
preparation of drawings and specifications |
time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps |
he felt pressured to deliver the drawings and specifications on a specified date |
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.