This page shows the pre-commit working store (the raw extraction under review). This case was committed to OntServe on 2026-07-25 15:09; the committed record differs by design (deduplication, typing, and agent binding are applied at commit). View the committed record

PASS 1: Contextual Framework Facts Section

Case 16: Impaired Engineering

R Roles
1
Classes
11
Individuals
S States
11
Classes
11
Individuals
Rs Resources
1
Classes
1
Individuals

Extracted Ontology Entities

36 RDF entities extracted organized by concept type

R Roles

Roles Classes
1
changed
EngineerRole
rdfs:subClassOf Roles
C16
Definition
Extracted from facts primary
A graduate engineer employee in the early years of practice who performs engineering design work and develops construction drawings under the responsible charge of a licensed professional engineer, without authority to sign and seal engineering documents.
Inherited from EngineerRole · note
A professional role involving engineering practice and responsibilities. Occupational archetype head for all engineer specializations and extracted engineer-role leaves.
Properties
Text References:
"Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience"
"Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings"
Confidence: 0.85
Role Category: employer_relationship
Role Kind: professional
Distinguishing Features:
  • Performs engineering design as an unlicensed graduate engineer under the supervision and responsible charge of a licensed professional engineer
  • Cannot sign and seal engineering documents in their own right
  • Gaining the supervised experience required for professional licensure
Professional Scope: Engineering design and construction drawing development performed under the supervision and review of a licensed professional engineer.
Typical Qualifications:
  • Engineering degree
  • Engineer intern or engineer-in-training standing working toward professional licensure
Associated Virtues:
  • Diligence
  • Honesty
  • Awareness of the limits of one's own competence
[facts] "Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience. The way they operated was, Engineer Intern C (who was fully aware ..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience; Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings
  • roleCategory content: employer_relationship
  • roleKind content: professional
  • distinguishingFeatures content: Performs engineering design as an unlicensed graduate engineer under the supervision and responsible charge of a licensed professional engineer; Cannot sign and seal engineering documents in their own right; Gaining the supervised experience required for professional licensure
  • professionalScope content: Engineering design and construction drawing development performed under the supervision and review of a licensed professional engineer.
  • typicalQualifications content: Engineering degree; Engineer intern or engineer-in-training standing working toward professional licensure
  • associatedVirtues content: Diligence; Honesty; Awareness of the limits of one's own competence
  • confidence assessment: 0.85
Roles Individuals
11
Text References:
"Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development"
"As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report"
"Engineer A did not report Engineer B to the State Board"
Confidence: 0.9
Actor: Engineer A
Role Class: Consultant Engineer Role
Role Category: professional_peer
Role Kind: professional
Specialty: Civil engineering and surveying associated with land development
Employer: His own consulting engineering firm
Technical Background: Civil engineering and surveying
Additional Relationships: {'type': 'declined to report to', 'target': 'State Board', 'quote': 'Engineer A did not report Engineer B to the State Board.'}
Case Involvement: Owns the consulting firm, discovered the structural failure, confronted Engineer B privately with the faulty design as a professional courtesy, and because of their long friendship and Engineer B's impairment did not report Engineer B to the State Board.
Business status: Business has been very successful and Engineer A has taken steps to expand
Professionalpeerof: Engineer B
"As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty ..."
[facts] "Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer A
  • attributes: {'business_status': 'Business has been very successful and Engineer A has taken steps to expand'}
  • relationships: {'type': 'professionalPeerOf', 'target': 'Engineer B', 'quote': 'As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A owns a consulting engineering firm specializing in civil engineering and surveying services associated with land development; As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report; Engineer A did not report Engineer B to the State Board
  • roleClass content: Consultant Engineer Role
  • roleCategory content: professional_peer
  • roleKind content: professional
  • specialty content: Civil engineering and surveying associated with land development
  • employer content: His own consulting engineering firm
  • technicalBackground content: Civil engineering and surveying
  • additionalRelationships content: {'type': 'declined to report to', 'target': 'State Board', 'quote': 'Engineer A did not report Engineer B to the State Board.'}
  • caseInvolvement content: Owns the consulting firm, discovered the structural failure, confronted Engineer B privately with the faulty design as a professional courtesy, and because of their long friendship and Engineer B's impairment did not report Engineer B to the State Board.
  • confidence assessment: 0.9
Text References:
"Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design"
"Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure"
Confidence: 0.88
Actor: Engineer A
Role Class: Client Role
Role Kind: participant
Additional Relationships:
  • {'type': 'retained', 'target': 'Engineer B', 'quote': 'he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design'}
  • {'type': 'retained', 'target': 'Architect', 'quote': 'he retained an architect'}
  • {'type': 'retained', 'target': 'Engineer R', 'quote': 'Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure'}
Case Involvement: Commissioned the new office building, retaining an architect, Engineer B for structural design, and later Engineer R for independent review and complete redesign after the basement structural failure.
Asset: purchased land for a new office building
[facts] "Among other things, Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structura..."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer A
  • attributes: {'asset': 'purchased land for a new office building'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design; Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure
  • roleClass content: Client Role
  • roleKind content: participant
  • additionalRelationships content: {'type': 'retained', 'target': 'Engineer B', 'quote': 'he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design'}; {'type': 'retained', 'target': 'Architect', 'quote': 'he retained an architect'}; {'type': 'retained', 'target': 'Engineer R', 'quote': 'Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure'}
  • caseInvolvement content: Commissioned the new office building, retaining an architect, Engineer B for structural design, and later Engineer R for independent review and complete redesign after the basement structural failure.
  • confidence assessment: 0.88
Text References:
"he retained an architect"
Confidence: 0.8
Actor: Architect
Role Class: Architect Role
Role Category: provider_client
Role Kind: professional
Case Involvement: Retained by Engineer A for the new office building project.
Hasclient: Engineer A
"he retained an architect"
[facts] "Among other things, Engineer A purchased land for a new office building, he retained an architect, and he retained Engineer B, his friend and a structural engineer consultant, to perform the structura..."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Architect
  • relationships: {'type': 'hasClient', 'target': 'Engineer A', 'quote': 'he retained an architect'}
Literal extractions (kept for synthesis)
  • textReferences content: he retained an architect
  • roleClass content: Architect Role
  • roleCategory content: provider_client
  • roleKind content: professional
  • caseInvolvement content: Retained by Engineer A for the new office building project.
  • confidence assessment: 0.8
Text References:
"he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design"
"Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office"
"Engineer B divulged he had suffered a stroke a few months prior"
"Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience"
Confidence: 0.92
Actor: Engineer B
Role Class: Structural Engineer Role
Role Category: provider_client
Role Kind: professional
License: Licensed professional engineer, the only one in his firm
Specialty: Structural engineering
Employer: His own firm
Technical Background: Structural design
Case Involvement: Retained by Engineer A to perform the structural design of the office building; after suffering a stroke he delegated practically all design work to Engineer Intern C, and his design was found by Engineer R to contain serious errors, omissions, and faulty details that led to the basement failure.
Health condition: suffered a stroke a few months prior
Friendship: personal friend of Engineer A
Hasclient: Engineer A
"he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design"
Workreviewedby: Engineer R
"Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement struct..."
Relatedto: Engineer Intern C
"Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience"
[facts] "he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer B
  • attributes: {'health_condition': 'suffered a stroke a few months prior', 'friendship': 'personal friend of Engineer A'}
  • relationships: {'type': 'hasClient', 'target': 'Engineer A', 'quote': 'he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design'}; {'type': 'workReviewedBy', 'target': 'Engineer R', 'quote': 'Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure'}; {'type': 'relatedTo', 'target': 'Engineer Intern C', 'quote': 'Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience'}
Literal extractions (kept for synthesis)
  • textReferences content: he retained Engineer B, his friend and a structural engineer consultant, to perform the structural design; Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office; Engineer B divulged he had suffered a stroke a few months prior; Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience
  • roleClass content: Structural Engineer Role
  • roleCategory content: provider_client
  • roleKind content: professional
  • license content: Licensed professional engineer, the only one in his firm
  • specialty content: Structural engineering
  • employer content: His own firm
  • technicalBackground content: Structural design
  • caseInvolvement content: Retained by Engineer A to perform the structural design of the office building; after suffering a stroke he delegated practically all design work to Engineer Intern C, and his design was found by Engineer R to contain serious errors, omissions, and faulty details that led to the basement failure.
  • confidence assessment: 0.92
Text References:
"Engineer A retained Engineer R to completely redesign the structure"
Confidence: 0.88
Actor: Engineer R
Role Class: Design Engineer Role
Role Category: provider_client
Role Kind: professional
Specialty: Structural engineering
Case Involvement: After his review revealed serious design errors, Engineer R was retained by Engineer A to completely redesign the structure.
Hasclient: Engineer A
"Engineer A retained Engineer R to completely redesign the structure"
[facts] "Engineer A retained Engineer R to completely redesign the structure."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer R
  • relationships: {'type': 'hasClient', 'target': 'Engineer A', 'quote': 'Engineer A retained Engineer R to completely redesign the structure'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A retained Engineer R to completely redesign the structure
  • roleClass content: Design Engineer Role
  • roleCategory content: provider_client
  • roleKind content: professional
  • specialty content: Structural engineering
  • caseInvolvement content: After his review revealed serious design errors, Engineer R was retained by Engineer A to completely redesign the structure.
  • confidence assessment: 0.88
Text References:
"Engineer B’s wife took over management of the business"
Confidence: 0.85
Actor: Engineer B's Wife
Role Class: Business Manager Role
Role Kind: participant
Employer: Engineer B's firm
Additional Relationships: {'type': 'manages business of', 'target': 'Engineer B', 'quote': 'Engineer B’s wife took over management of the business'}
Case Involvement: Took over management of Engineer B's firm after his stroke, without performing or being responsible for the engineering work.
[facts] "Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience..."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer B's Wife
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B’s wife took over management of the business
  • roleClass content: Business Manager Role
  • roleKind content: participant
  • employer content: Engineer B's firm
  • additionalRelationships content: {'type': 'manages business of', 'target': 'Engineer B', 'quote': 'Engineer B’s wife took over management of the business'}
  • caseInvolvement content: Took over management of Engineer B's firm after his stroke, without performing or being responsible for the engineering work.
  • confidence assessment: 0.85
Text References:
"Engineer A did not report Engineer B to the State Board."
Confidence: 0.8
Actor: State Board
Role Class: Regulatory Authority Role
Role Kind: participant
Case Involvement: The statutory licensure body to which Engineer A did not report Engineer B, because of their long friendship and consideration of Engineer B's impairment.
[facts] "Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: State Board
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A did not report Engineer B to the State Board.
  • roleClass content: Regulatory Authority Role
  • roleKind content: participant
  • caseInvolvement content: The statutory licensure body to which Engineer A did not report Engineer B, because of their long friendship and consideration of Engineer B's impairment.
  • confidence assessment: 0.8
Text References:
"Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience"
"Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings"
Confidence: 0.88
Actor: Engineer Intern C
Role Class: Engineer Intern Role
Role Category: employer_relationship
Role Kind: professional
License: Not licensed, graduate engineer intern
Specialty: Structural design
Experience Level: About two years’ experience
Employer: Engineer B's firm
Technical Background: Graduate engineer
Case Involvement: Performed practically all of the structural design and developed the construction drawings for Engineer A's building while fully aware of Engineer B's impaired condition, with Engineer B signing and sealing the drawings with little to no review.
Awareness: fully aware of Engineer B’s impaired condition
Employedby: Engineer B
"Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience"
Workreviewedby: Engineer B
"Engineer B would sign and seal the drawings with little to no review"
[facts] "Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer Intern C
  • attributes: {'awareness': 'fully aware of Engineer B’s impaired condition'}
  • relationships: {'type': 'employedBy', 'target': 'Engineer B', 'quote': 'Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience'}; {'type': 'workReviewedBy', 'target': 'Engineer B', 'quote': 'Engineer B would sign and seal the drawings with little to no review'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience; Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings
  • roleClass content: Engineer Intern Role
  • roleCategory content: employer_relationship
  • roleKind content: professional
  • license content: Not licensed, graduate engineer intern
  • specialty content: Structural design
  • experienceLevel content: About two years’ experience
  • employer content: Engineer B's firm
  • technicalBackground content: Graduate engineer
  • caseInvolvement content: Performed practically all of the structural design and developed the construction drawings for Engineer A's building while fully aware of Engineer B's impaired condition, with Engineer B signing and sealing the drawings with little to no review.
  • confidence assessment: 0.88
Text References:
"a contract was let, and the contractor began construction of the new office building"
Confidence: 0.8
Actor: Contractor
Role Class: Contractor Role
Role Kind: participant
Additional Relationships: {'type': 'contracted to construct building for', 'target': 'Engineer A', 'quote': 'a contract was let, and the contractor began construction of the new office building'}
Case Involvement: Began construction of the new office building including the basement, where the significant structural failure occurred early in construction.
[facts] "Construction drawings were completed, permits were issued, a contract was let, and the contractor began construction of the new office building – which included a basement."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Contractor
Literal extractions (kept for synthesis)
  • textReferences content: a contract was let, and the contractor began construction of the new office building
  • roleClass content: Contractor Role
  • roleKind content: participant
  • additionalRelationships content: {'type': 'contracted to construct building for', 'target': 'Engineer A', 'quote': 'a contract was let, and the contractor began construction of the new office building'}
  • caseInvolvement content: Began construction of the new office building including the basement, where the significant structural failure occurred early in construction.
  • confidence assessment: 0.8
Engineer B Sealing Engineer
Responsible Charge Engineer Role
Text References:
"Engineer B would sign and seal the drawings with little to no review"
"Being the only licensed professional engineer in his firm"
Confidence: 0.85
Actor: Engineer B
Role Class: Responsible Charge Engineer Role
Role Kind: professional
License: Licensed professional engineer, the only one in his firm
Specialty: Structural engineering
Employer: His own firm
Case Involvement: As the only licensed professional engineer in his firm, signed and sealed the construction drawings prepared by Engineer Intern C with little to no review, a process the case says ultimately led to the failure of Engineer A's building.
Review practice: signed and sealed drawings with little to no review
Relatedto: Engineer Intern C
"Engineer B would sign and seal the drawings with little to no review"
[facts] "Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings wi..."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer B
  • attributes: {'review_practice': 'signed and sealed drawings with little to no review'}
  • relationships: {'type': 'relatedTo', 'target': 'Engineer Intern C', 'quote': 'Engineer B would sign and seal the drawings with little to no review'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B would sign and seal the drawings with little to no review; Being the only licensed professional engineer in his firm
  • roleClass content: Responsible Charge Engineer Role
  • roleKind content: professional
  • license content: Licensed professional engineer, the only one in his firm
  • specialty content: Structural engineering
  • employer content: His own firm
  • caseInvolvement content: As the only licensed professional engineer in his firm, signed and sealed the construction drawings prepared by Engineer Intern C with little to no review, a process the case says ultimately led to the failure of Engineer A's building.
  • confidence assessment: 0.85
Text References:
"Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure"
"Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details"
Confidence: 0.92
Actor: Engineer R
Role Class: Structural Engineer Role
Role Category: provider_client
Role Kind: professional
Specialty: Structural engineering
Technical Background: Structural engineering review and design
Case Involvement: Retained by Engineer A to independently review the structural drawings and the failed basement structure; his review revealed serious structural design errors, omissions, and faulty details in both built and unbuilt portions.
Reputation: well-respected structural engineer
Hasclient: Engineer A
"Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement struct..."
Reviewsworkof: Engineer B
"Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement struct..."
[facts] "To obtain a second opinion about the failure, Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement ..."
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer R
  • attributes: {'reputation': 'well-respected structural engineer'}
  • relationships: {'type': 'hasClient', 'target': 'Engineer A', 'quote': 'Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure'}; {'type': 'reviewsWorkOf', 'target': 'Engineer B', 'quote': 'Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure; Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details
  • roleClass content: Structural Engineer Role
  • roleCategory content: provider_client
  • roleKind content: professional
  • specialty content: Structural engineering
  • technicalBackground content: Structural engineering review and design
  • caseInvolvement content: Retained by Engineer A to independently review the structural drawings and the failed basement structure; his review revealed serious structural design errors, omissions, and faulty details in both built and unbuilt portions.
  • confidence assessment: 0.92

S States

States Classes
11
changed
Competence Gap State
rdfs:subClassOf States
Definition
Extracted from facts primary
A condition in which an agent lacks, has insufficient, or has not exercised the competence required for the work at hand, here Engineer B's impaired condition following a stroke while continuing to practice as the only licensed professional engineer in his firm.
Inherited from CompetenceGapState · note
A condition in which an agent lacks, has insufficient, or has not exercised the competence required for the work at hand, undercutting the obligations that attach to it.
Properties
Text References:
"Engineer B divulged he had suffered a stroke a few months prior."
Confidence: 0.95
State Category: competence
Persistence Type: inertial
Activation Conditions: A licensed professional suffers an impairing medical event while remaining in responsible charge of engineering work
Termination Conditions: The professional recovers, suspends practice, or arranges qualified review of the work
Obligation Activation: Obligation to perform services only in areas of competence
Action Constraints: Constraint against sealing work the professional cannot competently review
Principle Transformation: The competence principle becomes a concrete duty for the impaired engineer to limit or restructure his practice rather than continue sealing unreviewed work.
[facts] "At this meeting, Engineer B divulged he had suffered a stroke a few months prior."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B divulged he had suffered a stroke a few months prior.
  • stateCategory content: competence
  • persistenceType content: inertial
  • principleTransformation content: The competence principle becomes a concrete duty for the impaired engineer to limit or restructure his practice rather than continue sealing unreviewed work.
  • confidence assessment: 0.95
Derived (reconstructable from the graph)
  • activationConditions: A licensed professional suffers an impairing medical event while remaining in responsible charge of engineering work
  • terminationConditions: The professional recovers, suspends practice, or arranges qualified review of the work
  • obligationActivation: Obligation to perform services only in areas of competence
  • actionConstraints: Constraint against sealing work the professional cannot competently review
changed
Seal Authority State
rdfs:subClassOf States
Definition
Extracted from facts primary
A regulatory condition concerning the application of a professional engineer's seal to a work product, here Engineer B signing and sealing construction drawings prepared by Engineer Intern C with little to no review.
Inherited from SealAuthorityState · note
A regulatory condition concerning the application of a professional engineer's seal to a work product, here a draft report submitted to the client with language clearly identifying it as a draft and with the seal applied consistent with state law.
Properties
Text References:
"Engineer B would sign and seal the drawings with little to no review"
Confidence: 0.88
State Category: regulatory
Persistence Type: inertial
Activation Conditions: A licensed engineer signs and seals drawings prepared by another with little to no review
Termination Conditions: The sealing practice ends or responsible review is instituted
Obligation Activation: Obligation to seal only work prepared under the engineer's responsible charge
Action Constraints: Constraint against sealing unreviewed work
Principle Transformation: The seal-in-responsible-charge principle becomes a concrete duty not to sign and seal drawings the engineer has not reviewed.
[facts] "Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings wi..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B would sign and seal the drawings with little to no review
  • stateCategory content: regulatory
  • persistenceType content: inertial
  • principleTransformation content: The seal-in-responsible-charge principle becomes a concrete duty not to sign and seal drawings the engineer has not reviewed.
  • confidence assessment: 0.88
Derived (reconstructable from the graph)
  • activationConditions: A licensed engineer signs and seals drawings prepared by another with little to no review
  • terminationConditions: The sealing practice ends or responsible review is instituted
  • obligationActivation: Obligation to seal only work prepared under the engineer's responsible charge
  • actionConstraints: Constraint against sealing unreviewed work
changed
Incomplete Submission State
rdfs:subClassOf States
Definition
Extracted from facts primary
A condition in which a delivered work product is deficient, containing errors or omissions that call its accuracy and reliability into question, here Engineer B's structural drawings containing serious design errors, omissions, and faulty details that led to the failure of Engineer A's building.
Inherited from IncompleteSubmissionState · note
A condition in which a delivered work product is deficient, containing errors or omissions that call its accuracy and reliability into question, here AI-generated design documents with misaligned dimensions and omitted safety features.
Properties
Text References:
"Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report."
Confidence: 0.85
State Category: risk
Persistence Type: inertial
Activation Conditions: Structural drawings containing serious errors and omissions are delivered and construction proceeds on them
Termination Conditions: The structure is completely redesigned
Principle Transformation: The deficient deliverable makes the general duty of accurate work concrete as a need to withdraw and replace the faulty design.
[facts] "As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report.
  • stateCategory content: risk
  • persistenceType content: inertial
  • principleTransformation content: The deficient deliverable makes the general duty of accurate work concrete as a need to withdraw and replace the faulty design.
  • confidence assessment: 0.85
Derived (reconstructable from the graph)
  • activationConditions: Structural drawings containing serious errors and omissions are delivered and construction proceeds on them
  • terminationConditions: The structure is completely redesigned
changed
ConfirmedRiskState
rdfs:subClassOf States
Definition
Extracted from facts primary
An epistemic condition in which a professional's identification of a problem has risen from preliminary suspicion to established fact, here Engineer R's independent review revealing a surprising number of serious structural design errors, omissions, and faulty details in both the failed basement and the unbuilt portions of the structure.
Inherited from ConfirmedRiskFindingState · note
An epistemic condition in which a professional's identification of a risk has risen from preliminary concern to the technical and moral level of fact, here the condition after additional studies identify a potential risk that heavy rainfall could lead to stormwater runoff from the development reaching the nearby watershed, so that the runoff risk is now a fact of the case.
Properties
Text References:
"Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that h..."
Confidence: 0.9
State Category: epistemic
Persistence Type: inertial
Activation Conditions: An independent review confirms serious design errors
Termination Conditions: The structure is completely redesigned and the errors corrected
Obligation Activation: Obligation to correct the confirmed design deficiencies
Principle Transformation: Confirmed knowledge of serious errors converts general prudence into a concrete duty to redesign before further construction.
[facts] "Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that h..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet.
  • stateCategory content: epistemic
  • persistenceType content: inertial
  • principleTransformation content: Confirmed knowledge of serious errors converts general prudence into a concrete duty to redesign before further construction.
  • confidence assessment: 0.9
Derived (reconstructable from the graph)
  • activationConditions: An independent review confirms serious design errors
  • terminationConditions: The structure is completely redesigned and the errors corrected
  • obligationActivation: Obligation to correct the confirmed design deficiencies
changed
SelectiveReportingState
rdfs:subClassOf States
New C16
Definition
Extracted from facts primary
A disclosure condition in which a professional who is aware of another engineer's apparent code violation or impaired practice has not reported it to the licensing authority, so the information remains withheld from the body charged with protecting the public, here Engineer A not reporting Engineer B to the State Board.
Properties
Text References:
"Engineer A did not report Engineer B to the State Board."
Confidence: 0.85
State Category: disclosure
Persistence Type: inertial
Activation Conditions: A professional becomes aware of another engineer's apparent violation and does not report it
Termination Conditions: The professional reports the violation to the appropriate authority
Obligation Activation: Obligation to report code violations to appropriate authorities
Principle Transformation: The withheld information keeps the general duty to report violations applicable and undischarged for as long as the nonreporting condition holds.
[facts] "Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A did not report Engineer B to the State Board.
  • stateCategory content: disclosure
  • persistenceType content: inertial
  • principleTransformation content: The withheld information keeps the general duty to report violations applicable and undischarged for as long as the nonreporting condition holds.
  • confidence assessment: 0.85
Derived (reconstructable from the graph)
  • activationConditions: A professional becomes aware of another engineer's apparent violation and does not report it
  • terminationConditions: The professional reports the violation to the appropriate authority
  • obligationActivation: Obligation to report code violations to appropriate authorities
changed
Conflict Of Interest State
rdfs:subClassOf States
Definition
Extracted from facts primary
A condition in which an agent holds competing interests or loyalties that bias or constrain the exercise of professional judgment, here Engineer A's long friendship with Engineer B and consideration of his impairment weighing against reporting Engineer B to the State Board.
Inherited from ConflictOfInterestState · note
A condition in which an agent holds competing interests or loyalties, or competing role-derived duties, that cannot all be fully served and that bias or constrain the exercise of professional judgment. As a content kind it is the standing tension among interests, covering both conflict of interest and competing duties. Its deontic relevance is that it renders the affected obligations defeasible against one another and grounds the competesWith, prevailsOver, and defeasibleUnder edge family.
Properties
Text References:
"Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board."
Confidence: 0.85
State Category: conflict_of_interest
Persistence Type: inertial
Activation Conditions: A professional discovers apparent misconduct by a personal friend
Termination Conditions: The professional resolves the tension by reporting or the matter is otherwise closed
Principle Transformation: The friendship loyalty places the reporting duty in tension with personal loyalty, making the general duty concrete as a decision whether to report.
[facts] "Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board.
  • stateCategory content: conflict_of_interest
  • persistenceType content: inertial
  • principleTransformation content: The friendship loyalty places the reporting duty in tension with personal loyalty, making the general duty concrete as a decision whether to report.
  • confidence assessment: 0.85
Derived (reconstructable from the graph)
  • activationConditions: A professional discovers apparent misconduct by a personal friend
  • terminationConditions: The professional resolves the tension by reporting or the matter is otherwise closed
changed
FinancialConstraintState
rdfs:subClassOf States
Definition
Extracted from facts primary
A resource condition in which a professional's financial means constrain his willingness to suspend work or close his office, here Engineer B, the only licensed professional engineer in his firm, feeling he could not afford to suspend work or close his office after his stroke.
Properties
Text References:
"Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office."
Confidence: 0.97
State Category: resource
Persistence Type: inertial
Activation Conditions: A professional's firm depends financially on his continued practice and he suffers an event that would otherwise call for suspending work
Termination Conditions: The financial constraint eases or the professional restructures or closes the practice
Principle Transformation: Financial pressure conditions the feasibility of the impaired engineer's duty to suspend work, reordering how his duties are discharged in practice.
[facts] "Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office.
  • stateCategory content: resource
  • persistenceType content: inertial
  • principleTransformation content: Financial pressure conditions the feasibility of the impaired engineer's duty to suspend work, reordering how his duties are discharged in practice.
  • confidence assessment: 0.97
Derived (reconstructable from the graph)
  • activationConditions: A professional's firm depends financially on his continued practice and he suffers an event that would otherwise call for suspending work
  • terminationConditions: The financial constraint eases or the professional restructures or closes the practice
changed
CompetenceGapState
rdfs:subClassOf States
Definition
Extracted from facts primary
A competence condition in which an engineer intern who has not yet obtained professional licensure carries out delegated design work, here Engineer Intern C, a graduate engineer with about two years of experience, performing practically all structural design and construction drawings for Engineer B's firm.
Inherited from PreLicensurePracticeState · note
A competence condition in which an engineer intern who has not yet obtained professional licensure carries out delegated project work under a senior engineer's responsibility, here Engineer Intern D, about to sit for the PE exam, performing the Shadyvale DOT project delegated by Engineer W.
Properties
Text References:
"Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience."
Confidence: 0.9
State Category: competence
Persistence Type: inertial
Activation Conditions: Design work is delegated to an unlicensed engineer intern
Termination Conditions: The intern obtains licensure or the delegation arrangement ends
Obligation Activation: Obligation of the responsible engineer to review and remain in responsible charge of delegated work
Principle Transformation: The responsible-charge principle becomes a concrete duty of meaningful review over the intern's delegated design work.
[facts] "Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience.
  • stateCategory content: competence
  • persistenceType content: inertial
  • principleTransformation content: The responsible-charge principle becomes a concrete duty of meaningful review over the intern's delegated design work.
  • confidence assessment: 0.9
Derived (reconstructable from the graph)
  • activationConditions: Design work is delegated to an unlicensed engineer intern
  • terminationConditions: The intern obtains licensure or the delegation arrangement ends
  • obligationActivation: Obligation of the responsible engineer to review and remain in responsible charge of delegated work
changed
Supervisory Direction State
rdfs:subClassOf States
Definition
Extracted from facts primary
A resource condition in which a subordinate professional works without the guidance, direct supervision, or review their role presupposes, here Engineer Intern C performing practically all structural design while Engineer B sealed the drawings with little to no review.
Inherited from SupervisoryDirectionState · note
A resource condition in which a subordinate professional who works within the safety net of a supervisor's guidance and direct supervision no longer has that guidance, direct supervision, or review available, leaving the subordinate without the supervisory support their role presupposes.
Properties
Text References:
"Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings wi..."
Confidence: 0.88
State Category: resource
Persistence Type: inertial
Activation Conditions: The supervising engineer becomes unable or fails to provide review of the subordinate's design work
Termination Conditions: Meaningful supervisory review is restored
Principle Transformation: The absence of supervisory review turns the abstract responsible-charge principle into an unmet concrete condition for the delegated design work.
[facts] "The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would si..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review.
  • stateCategory content: resource
  • persistenceType content: inertial
  • principleTransformation content: The absence of supervisory review turns the abstract responsible-charge principle into an unmet concrete condition for the delegated design work.
  • confidence assessment: 0.88
Derived (reconstructable from the graph)
  • activationConditions: The supervising engineer becomes unable or fails to provide review of the subordinate's design work
  • terminationConditions: Meaningful supervisory review is restored
changed
Unquantified Risk State
rdfs:subClassOf States
Definition
Extracted from facts primary
An epistemic condition in which a professional is aware of a potential problem but has not yet quantified or fully characterized it, here Engineer A noticing what he believed was odd structural bracing and other questionable structural details while observing the failed system, before obtaining an independent review.
Inherited from UnquantifiedRiskState · note
An epistemic condition in which a professional is aware of a potential risk but has not yet quantified or fully characterized it, so the professional's knowledge of the hazard is speculative or preliminary rather than measured.
Properties
Text References:
"While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details."
Confidence: 0.85
State Category: epistemic
Persistence Type: inertial
Activation Conditions: A professional observes signs of a potential defect without yet characterizing it
Termination Conditions: An independent review confirms or dispels the suspected defect
Obligation Activation: Obligation to obtain a competent second opinion before acting on a suspicion
Principle Transformation: The duty of objective judgment becomes a concrete step of retaining an independent reviewer to characterize the suspected defect.
[facts] "While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details.
  • stateCategory content: epistemic
  • persistenceType content: inertial
  • principleTransformation content: The duty of objective judgment becomes a concrete step of retaining an independent reviewer to characterize the suspected defect.
  • confidence assessment: 0.85
Derived (reconstructable from the graph)
  • activationConditions: A professional observes signs of a potential defect without yet characterizing it
  • terminationConditions: An independent review confirms or dispels the suspected defect
  • obligationActivation: Obligation to obtain a competent second opinion before acting on a suspicion
changed
KnowledgeState
rdfs:subClassOf States
C16
Definition
Extracted from facts primary
A condition of what an agent knows with respect to facts material to a decision, here Engineer Intern C being fully aware of Engineer B's impaired condition while performing the design work that Engineer B sealed with little to no review.
Inherited from EpistemicState · note
A condition of what an agent knows, believes, or is uncertain of with respect to facts material to a decision. As a content kind it captures the agent's knowledge state, the classical Aristotelian epistemic condition for responsibility: an agent is answerable for conduct in proportion to what the agent knew or should have known; Sarmiento et al. (2023) name epistemic aspects fundamental for moving beyond causality to responsibility. Its deontic relevance is that knowledge conditions the obligations governing informed decision and decision-under-uncertainty.
Properties
Text References:
"who was fully aware of Engineer B’s impaired condition"
Confidence: 0.85
State Category: epistemic
Persistence Type: inertial
Activation Conditions: The subordinate learns of the supervising engineer's impaired condition
Termination Conditions: The impairment ends or the arrangement is corrected
Principle Transformation: The intern's knowledge of the impairment bears on the responsibility that attaches to continuing under the unreviewed sealing arrangement.
[facts] "Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings wi..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: who was fully aware of Engineer B’s impaired condition
  • stateCategory content: epistemic
  • persistenceType content: inertial
  • principleTransformation content: The intern's knowledge of the impairment bears on the responsibility that attaches to continuing under the unreviewed sealing arrangement.
  • confidence assessment: 0.85
Derived (reconstructable from the graph)
  • activationConditions: The subordinate learns of the supervising engineer's impaired condition
  • terminationConditions: The impairment ends or the arrangement is corrected
States Individuals
11
Text References:
"Engineer B would sign and seal the drawings with little to no review"
Confidence: 0.9
State Class: Seal Authority State
Subject: Construction drawings sealed by Engineer B
Active Period: Throughout the period in which Intern C prepared drawings that Engineer B signed and sealed
Triggering Event: Engineer B began signing and sealing drawings prepared by Engineer Intern C with little to no review
Terminated By: Not stated in the case
Affected Parties:
  • Engineer B
  • Engineer Intern C
  • Engineer A
Urgency Level: high
[facts] "Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings wi..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer Intern C; Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B would sign and seal the drawings with little to no review
  • stateClass content: Seal Authority State
  • subject content: Construction drawings sealed by Engineer B
  • activePeriod content: Throughout the period in which Intern C prepared drawings that Engineer B signed and sealed
  • triggeringEvent content: Engineer B began signing and sealing drawings prepared by Engineer Intern C with little to no review
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.9
  • urgencyLevel assessment: high
Engineer A Defect Suspicion
UnquantifiedRiskState
Text References:
"While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details."
Confidence: 0.85
State Class: Unquantified Risk State
Subject: Engineer A
Active Period: From observing the failed system until Engineer R's review characterized the defects
Triggering Event: Engineer A observed the failed basement system and noticed odd structural bracing and questionable details
Terminated By: Engineer R's independent review revealed the serious structural design errors
Affected Parties: Engineer A
Urgency Level: medium
[facts] "While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: While observing the failed system, Engineer A noticed what he believed was “odd” structural bracing and other questionable structural details.
  • stateClass content: Unquantified Risk State
  • subject content: Engineer A
  • activePeriod content: From observing the failed system until Engineer R's review characterized the defects
  • triggeringEvent content: Engineer A observed the failed basement system and noticed odd structural bracing and questionable details
  • terminatedBy content: Engineer R's independent review revealed the serious structural design errors
  • confidence assessment: 0.85
  • urgencyLevel assessment: medium
Text References:
"The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would si..."
Confidence: 0.88
State Class: Supervisory Direction State
Subject: Engineer Intern C's design work
Active Period: For the duration of the delegation arrangement after Engineer B's stroke
Triggering Event: Engineer B's impairment left him providing little to no review of Intern C's design work
Terminated By: Not stated in the case
Affected Parties:
  • Engineer Intern C
  • Engineer A
Urgency Level: high
[facts] "The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would si..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer Intern C; Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: The way they operated was, Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings with little to no review.
  • stateClass content: Supervisory Direction State
  • subject content: Engineer Intern C's design work
  • activePeriod content: For the duration of the delegation arrangement after Engineer B's stroke
  • triggeringEvent content: Engineer B's impairment left him providing little to no review of Intern C's design work
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.88
  • urgencyLevel assessment: high
Text References:
"Engineer B divulged he had suffered a stroke a few months prior."
Confidence: 0.95
State Class: Competence Gap State
Subject: Engineer B
Active Period: From the stroke a few months prior through the period in which the drawings were prepared and sealed
Triggering Event: Engineer B suffered a stroke a few months prior
Terminated By: Not stated in the case
Affected Parties:
  • Engineer B
  • Engineer A
  • Engineer Intern C
Urgency Level: high
[facts] "At this meeting, Engineer B divulged he had suffered a stroke a few months prior."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer A; Engineer Intern C
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B divulged he had suffered a stroke a few months prior.
  • stateClass content: Competence Gap State
  • subject content: Engineer B
  • activePeriod content: From the stroke a few months prior through the period in which the drawings were prepared and sealed
  • triggeringEvent content: Engineer B suffered a stroke a few months prior
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.95
  • urgencyLevel assessment: high
Engineer B Financial Pressure
Financial Pressure State
Text References:
"Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office."
Confidence: 0.95
State Class: Financial Pressure State
Subject: Engineer B and his firm
Active Period: After the stroke, while the firm continued operating
Triggering Event: Engineer B's stroke combined with his position as the only licensed professional engineer in his firm
Terminated By: Not stated in the case
Affected Parties:
  • Engineer B
  • Engineer B's firm
Urgency Level: medium
[facts] "Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer B's firm
Literal extractions (kept for synthesis)
  • textReferences content: Being the only licensed professional engineer in his firm, for financial and other reasons, Engineer B felt he could not afford to suspend work or close his office.
  • stateClass content: Financial Pressure State
  • subject content: Engineer B and his firm
  • activePeriod content: After the stroke, while the firm continued operating
  • triggeringEvent content: Engineer B's stroke combined with his position as the only licensed professional engineer in his firm
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.95
  • urgencyLevel assessment: medium
Text References:
"Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience."
Confidence: 0.9
State Class: Pre-Licensure Practice State
Subject: Engineer Intern C
Active Period: From Engineer B's delegation of design work until the arrangement was exposed by the failure
Triggering Event: Engineer B delegated practically all design work to Engineer Intern C after his stroke
Terminated By: Not stated in the case
Affected Parties:
  • Engineer Intern C
  • Engineer B
  • Engineer A
Urgency Level: high
[facts] "Rather, Engineer B’s wife took over management of the business, and Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer Intern C; Engineer B; Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B delegated practically all design work to Engineer Intern C, a graduate engineer employee with about two years’ experience.
  • stateClass content: Pre-Licensure Practice State
  • subject content: Engineer Intern C
  • activePeriod content: From Engineer B's delegation of design work until the arrangement was exposed by the failure
  • triggeringEvent content: Engineer B delegated practically all design work to Engineer Intern C after his stroke
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.9
  • urgencyLevel assessment: high
Text References:
"Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that h..."
Confidence: 0.92
State Class: Confirmed Risk Finding State
Subject: Engineer A, holding Engineer R's confirmed findings of serious structural design errors
Active Period: From Engineer R's review until the structure was completely redesigned
Triggering Event: Engineer R's independent review revealed serious structural design errors, omissions, and faulty details
Terminated By: Engineer A retained Engineer R to completely redesign the structure
Affected Parties:
  • Engineer A
  • Engineer B
  • Engineer R
Urgency Level: high
[facts] "Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that h..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer A; Engineer B; Engineer R
Literal extractions (kept for synthesis)
  • textReferences content: Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet.
  • stateClass content: Confirmed Risk Finding State
  • subject content: Engineer A, holding Engineer R's confirmed findings of serious structural design errors
  • activePeriod content: From Engineer R's review until the structure was completely redesigned
  • triggeringEvent content: Engineer R's independent review revealed serious structural design errors, omissions, and faulty details
  • terminatedBy content: Engineer A retained Engineer R to completely redesign the structure
  • confidence assessment: 0.92
  • urgencyLevel assessment: high
Text References:
"Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report."
Confidence: 0.85
State Class: Incomplete Submission State
Subject: Engineer B's structural drawings for Engineer A's office building
Active Period: From delivery of the construction drawings until the complete redesign by Engineer R
Triggering Event: Engineer B's firm delivered structural drawings containing serious design errors, omissions, and faulty details
Terminated By: Engineer R completely redesigned the structure
Affected Parties:
  • Engineer A
  • Engineer B
Urgency Level: high
[facts] "As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer A; Engineer B
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report.
  • stateClass content: Incomplete Submission State
  • subject content: Engineer B's structural drawings for Engineer A's office building
  • activePeriod content: From delivery of the construction drawings until the complete redesign by Engineer R
  • triggeringEvent content: Engineer B's firm delivered structural drawings containing serious design errors, omissions, and faulty details
  • terminatedBy content: Engineer R completely redesigned the structure
  • confidence assessment: 0.85
  • urgencyLevel assessment: high
Text References:
"who was fully aware of Engineer B’s impaired condition"
Confidence: 0.85
State Class: Epistemic State
Subject: Engineer Intern C
Active Period: Throughout the delegation arrangement after Engineer B's stroke
Triggering Event: Engineer Intern C became fully aware of Engineer B's impaired condition
Terminated By: Not stated in the case
Affected Parties:
  • Engineer Intern C
  • Engineer B
Urgency Level: medium
[facts] "Engineer Intern C (who was fully aware of Engineer B’s impaired condition) would perform the structural design and develop the construction drawings, and Engineer B would sign and seal the drawings wi..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer Intern C; Engineer B
Literal extractions (kept for synthesis)
  • textReferences content: who was fully aware of Engineer B’s impaired condition
  • stateClass content: Epistemic State
  • subject content: Engineer Intern C
  • activePeriod content: Throughout the delegation arrangement after Engineer B's stroke
  • triggeringEvent content: Engineer Intern C became fully aware of Engineer B's impaired condition
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.85
  • urgencyLevel assessment: medium
Engineer B Violation Unreported
SelectiveReportingState
New C16
Text References:
"Engineer A did not report Engineer B to the State Board."
Confidence: 0.85
State Class: Unreported Violation State
Subject: Engineer A's knowledge of Engineer B's conduct, withheld from the State Board
Active Period: From Engineer A's discovery of the faulty design and sealing arrangement onward
Triggering Event: Engineer A decided not to report Engineer B because of their long friendship and consideration of Engineer B's impairment
Terminated By: Not stated in the case
Affected Parties:
  • Engineer A
  • Engineer B
  • State Board
  • Public
Urgency Level: high
[facts] "Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer A; Engineer B; State Board; Public
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A did not report Engineer B to the State Board.
  • stateClass content: Unreported Violation State
  • subject content: Engineer A's knowledge of Engineer B's conduct, withheld from the State Board
  • activePeriod content: From Engineer A's discovery of the faulty design and sealing arrangement onward
  • triggeringEvent content: Engineer A decided not to report Engineer B because of their long friendship and consideration of Engineer B's impairment
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.85
  • urgencyLevel assessment: high
Text References:
"Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board."
Confidence: 0.85
State Class: Conflict Of Interest State
Subject: Engineer A
Active Period: From Engineer A's discovery of the faulty design and Engineer B's impairment onward
Triggering Event: Engineer A discovered his personal friend Engineer B's faulty design and impaired condition
Terminated By: Not stated in the case
Affected Parties:
  • Engineer A
  • Engineer B
  • State Board
Urgency Level: medium
[facts] "Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer A; Engineer B; State Board
Literal extractions (kept for synthesis)
  • textReferences content: Because of their long friendship and consideration of Engineer B’s impairment, Engineer A did not report Engineer B to the State Board.
  • stateClass content: Conflict Of Interest State
  • subject content: Engineer A
  • activePeriod content: From Engineer A's discovery of the faulty design and Engineer B's impairment onward
  • triggeringEvent content: Engineer A discovered his personal friend Engineer B's faulty design and impaired condition
  • terminatedBy content: Not stated in the case
  • confidence assessment: 0.85
  • urgencyLevel assessment: medium

Rs Resources

Resources Classes
1
changed
ReferenceMaterial
rdfs:subClassOf Resources
Definition
Extracted from facts primary
An independent engineering review report or similar documentation supporting professional practice, consulted as a knowledge source in evaluating professional conduct. In this case, an independent structural review report documenting design errors, omissions, and faulty details.
Inherited from ReferenceMaterial · note
Handbooks, manuals, guides, and other documentation supporting professional practice with technical and procedural knowledge.
Properties
Text References:
"Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure."
"Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report."
Confidence: 0.85
Resource Category: reference_material
[facts] "To obtain a second opinion about the failure, Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement ..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A retained a well-respected structural engineer, Engineer R, to perform an independent review of the structural drawings and the failed basement structure.; Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report.
  • resourceCategory content: reference_material
  • confidence assessment: 0.85
Resources Individuals
1
changed
Engineer R's Report
Reference Material
Text References:
"Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report."
"Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that h..."
Confidence: 0.88
Resource Class: Reference Material
Document Title: Engineer R's report
Topic: structural design errors, omissions, and faulty details in the office building design
Used By: Engineer A
[facts] "As a professional courtesy, and because he considered Engineer B a personal friend, Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report."
Field classification (triples vs literals)
Relations (structural triples)
  • usedBy: Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A met privately with Engineer B and confronted him with the faulty design, including Engineer R’s report.; Engineer R’s review revealed a surprising number of serious structural design errors, omissions, and faulty details, not only for the failed basement, but also for the portions of the structure that had not been built yet.
  • resourceClass content: Reference Material
  • documentTitle content: Engineer R's report
  • topic content: structural design errors, omissions, and faulty details in the office building design
  • confidence assessment: 0.88

Pass 1: Contextual Framework - Facts
Review extracted entities, then continue to the next step