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

PASS 3: Temporal Dynamics

Case 19: Duty to Report Misconduct

31 entities 8 actions 4 events 8 causal chains 10 temporal relations
Timeline Overview
Action Event 12 sequenced markers
Prior Project Execution During previous employment, before joining XYZ Engineers
Project Manager Hiring Before proposal marketing began in States Q and Z
Qualification Statement Presentation During proposal and marketing activities in States Q and Z
Disclosure Omission During preparation of qualification statements accompanying project proposals
Ethics Questioning After observing XYZ Engineers' proposal practice
Code and Rules Review After questioning the proposal practice
Reporting Deliberation After reviewing the NSPE Code and both states' rules
Board Determination During ethical review of the case
Rule Divergence Discovery During Engineer A's review of the NSPE Code and both states' licensing rules
Misconduct Constitution Upon submission of the qualification statements in State Z
Reporting Duty Activation Once Engineer A gained knowledge of the noncompliant presentation and the State Z rule
Reporting Obligation Confirmation At the conclusion of the BER's review of the case
OWL-Time Temporal Structure 10 relations time: = w3.org/2006/time
Engineer B's employment at previous firm time:intervalBefore Engineer B's hiring by XYZ Engineers
Engineer B's completion of non-proprietary projects time:intervalDuring Engineer B's employment at previous firm
Engineer B's hiring by XYZ Engineers time:intervalBefore XYZ's marketing of bridge and culvert designs in States Q and Z
XYZ's qualification statement/proposal practice time:intervalDuring XYZ's marketing of designs in both states
XYZ's proposal/marketing practice time:intervalBefore Engineer A's questioning of the practice's ethics
Engineer A's questioning of the practice time:intervalBefore Engineer A's review of the NSPE Code of Ethics and both states' licensing rules
Engineer A's review of the licensing rules time:intervalBefore Engineer A's deliberation on ethics and reporting obligations
Engineer A's deliberation on reporting obligations time:intervalBefore BER analysis and conclusions
Engineer B's role as project manager at XYZ time:intervalOverlaps Engineer A's employment at ABC Consultants
development of State Z's licensing rules (long legislative history) time:intervalBefore Engineer A's review of the rules
Extracted Actions (8)
Volitional professional decisions with intentions and ethical context

Description: Engineer B, while in previous employment at another firm, completed non-proprietary bridge and culvert projects in responsible charge, projects that later became the basis of experience claims in XYZ's proposals.

Temporal Marker: During previous employment, before joining XYZ Engineers interval

Fluent Transitions:
Initiates (1)
  • Engineer B Prior Project Experience

Mental State: deliberate

Intended Outcome: Complete design projects in responsible charge within areas of expertise

Required Capabilities:
Bridge and culvert design Responsible charge project management
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • requiresCapability: Bridge and culvert design; Responsible charge project management
  • initiates: Engineer B Prior Project Experience
Literal extractions (kept for synthesis)
  • description content: Engineer B, while in previous employment at another firm, completed non-proprietary bridge and culvert projects in responsible charge, projects that later became the basis of experience claims in XYZ's proposals.
  • hasAgent content: Engineer B
  • temporalMarker content: During previous employment, before joining XYZ Engineers
  • eventRoleContext content: Project Manager, formerly of another design firm
  • hasMentalState content: deliberate
  • intendedOutcome content: Complete design projects in responsible charge within areas of expertise
  • textReferences content: Engineer B’s projects completed while in previous employment did not involve proprietary design concepts, and the capabilities of project team members on those projects were within Engineer B’s areas of expertise.
  • temporalExtent content: interval
  • temporalSequence content: 1
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Prior_Project_Execution",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.243965+00:00",
  "proeth:description": "Engineer B, while in previous employment at another firm, completed non-proprietary bridge and culvert projects in responsible charge, projects that later became the basis of experience claims in XYZ\u0027s proposals.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Project Manager, formerly of another design firm",
  "proeth:hasAgent": "Engineer B",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Engineer B Prior Project Experience"
  ],
  "proeth:intendedOutcome": "Complete design projects in responsible charge within areas of expertise",
  "proeth:requiresCapability": [
    "Bridge and culvert design",
    "Responsible charge project management"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During previous employment, before joining XYZ Engineers",
  "proeth:temporalSequence": 1,
  "proeth:textReferences": [
    "Engineer B\u2019s projects completed while in previous employment did not involve proprietary design concepts, and the capabilities of project team members on those projects were within Engineer B\u2019s areas of expertise."
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Prior Project Execution"
}

Description: XYZ Engineers hired Engineer B as a new project manager and began marketing bridge and culvert designs in both State Q and State Z in competition with ABC Consultants.

Temporal Marker: Before proposal marketing began in States Q and Z instant

Fluent Transitions:
Initiates (1)
  • Competitive Marketing in Two States

Mental State: deliberate

Intended Outcome: Expand bridge and culvert design business into both states using Engineer B's experience

Required Capabilities:
Business development Personnel management
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • requiresCapability: Business development; Personnel management
  • initiates: Competitive Marketing in Two States
Literal extractions (kept for synthesis)
  • description content: XYZ Engineers hired Engineer B as a new project manager and began marketing bridge and culvert designs in both State Q and State Z in competition with ABC Consultants.
  • hasAgent content: XYZ Engineers
  • temporalMarker content: Before proposal marketing began in States Q and Z
  • eventRoleContext content: Design Firm
  • hasMentalState content: deliberate
  • intendedOutcome content: Expand bridge and culvert design business into both states using Engineer B's experience
  • textReferences content: ABC’s competitors, XYZ Engineers, hired a new project manager, Engineer B, with extensive experience in responsible charge of projects in another region, and began to market bridge and culvert designs in both states.
  • temporalExtent content: instant
  • temporalSequence content: 2
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Project_Manager_Hiring",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.244363+00:00",
  "proeth:description": "XYZ Engineers hired Engineer B as a new project manager and began marketing bridge and culvert designs in both State Q and State Z in competition with ABC Consultants.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Design Firm",
  "proeth:hasAgent": "XYZ Engineers",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Competitive Marketing in Two States"
  ],
  "proeth:intendedOutcome": "Expand bridge and culvert design business into both states using Engineer B\u0027s experience",
  "proeth:requiresCapability": [
    "Business development",
    "Personnel management"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Before proposal marketing began in States Q and Z",
  "proeth:temporalSequence": 2,
  "proeth:textReferences": [
    "ABC\u2019s competitors, XYZ Engineers, hired a new project manager, Engineer B, with extensive experience in responsible charge of projects in another region, and began to market bridge and culvert designs in both states."
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Project Manager Hiring"
}

Description: XYZ Engineers and Engineer B presented qualification statements attributing Engineer B's prior projects to the previous employer at the beginning of the individual qualification section, identifying the prior employer and the associated client for each project.

Temporal Marker: During proposal and marketing activities in States Q and Z interval

Fluent Transitions:
Initiates (1)
  • Proposal Attribution Practice in Effect

Mental State: deliberate

Intended Outcome: Present Engineer B's project experience to prospective clients while crediting the previous employer and clients

Foreseen Unintended Effects:

  • Possible client confusion about which firm performed the listed projects
Obligation Engagement:
Fulfills (1)
  • Credit to Proprietary Interests of Previous Employer
Guided By Principles:
  • Transparency
Required Capabilities:
Proposal preparation Marketing communication
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • fulfillsObligation: Credit to Proprietary Interests of Previous Employer
  • guidedByPrinciple: Transparency
  • requiresCapability: Proposal preparation; Marketing communication
  • initiates: Proposal Attribution Practice in Effect
Literal extractions (kept for synthesis)
  • description content: XYZ Engineers and Engineer B presented qualification statements attributing Engineer B's prior projects to the previous employer at the beginning of the individual qualification section, identifying the prior employer and the associated client for each project.
  • hasAgent content: XYZ Engineers and Engineer B
  • temporalMarker content: During proposal and marketing activities in States Q and Z
  • eventRoleContext content: Project Manager
  • hasMentalState content: deliberate
  • intendedOutcome content: Present Engineer B's project experience to prospective clients while crediting the previous employer and clients
  • foreseenUnintendedEffects content: Possible client confusion about which firm performed the listed projects
  • textReferences content: at the beginning of an individual qualification section, Engineer B’s projects for a different firm are identified as a part of Engineer B’s experience, identifying the prior employer and the associated client for each project
  • temporalExtent content: interval
  • temporalSequence content: 3
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Qualification_Statement_Presentation",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.244427+00:00",
  "proeth:description": "XYZ Engineers and Engineer B presented qualification statements attributing Engineer B\u0027s prior projects to the previous employer at the beginning of the individual qualification section, identifying the prior employer and the associated client for each project.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Project Manager",
  "proeth:foreseenUnintendedEffects": [
    "Possible client confusion about which firm performed the listed projects"
  ],
  "proeth:fulfillsObligation": [
    "Credit to Proprietary Interests of Previous Employer"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency"
  ],
  "proeth:hasAgent": "XYZ Engineers and Engineer B",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Proposal Attribution Practice in Effect"
  ],
  "proeth:intendedOutcome": "Present Engineer B\u0027s project experience to prospective clients while crediting the previous employer and clients",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Proposal preparation",
    "Marketing communication"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "During proposal and marketing activities in States Q and Z",
  "proeth:temporalSequence": 3,
  "proeth:textReferences": [
    "at the beginning of an individual qualification section, Engineer B\u2019s projects for a different firm are identified as a part of Engineer B\u2019s experience, identifying the prior employer and the associated client for each project"
  ],
  "proeth:violatesObligation": [],
  "proeth:withinCompetence": true,
  "rdfs:label": "Qualification Statement Presentation"
}

Description: XYZ Engineers and Engineer B did not repeat the prior-employer attribution notice within all paragraphs of the lengthy individual project descriptions, a non-performance the case treats as the conduct that violates State Z's specific rules.

Temporal Marker: During preparation of qualification statements accompanying project proposals instant

Fluent Transitions:
Initiates (2)
  • State Z Rule Noncompliance
  • Potentially Misleading Presentation

Mental State: not clearly deliberate; the case notes the section-level notice appears to indicate an intent to provide transparency

Intended Outcome: Avoid repetitive disclaimers within lengthy project descriptions

Foreseen Unintended Effects:

  • Reduced clarity about which projects were performed for the previous employer
Obligation Engagement:
Violates (2)
  • State Z Attribution Requirement
  • Avoidance of Misrepresentation of Qualifications
Required Capabilities:
Proposal preparation
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • violatesObligation: State Z Attribution Requirement; Avoidance of Misrepresentation of Qualifications
  • requiresCapability: Proposal preparation
  • initiates: State Z Rule Noncompliance; Potentially Misleading Presentation
Literal extractions (kept for synthesis)
  • description content: XYZ Engineers and Engineer B did not repeat the prior-employer attribution notice within all paragraphs of the lengthy individual project descriptions, a non-performance the case treats as the conduct that violates State Z's specific rules.
  • hasAgent content: XYZ Engineers and Engineer B
  • temporalMarker content: During preparation of qualification statements accompanying project proposals
  • eventRoleContext content: Project Manager
  • hasMentalState content: not clearly deliberate; the case notes the section-level notice appears to indicate an intent to provide transparency
  • intendedOutcome content: Avoid repetitive disclaimers within lengthy project descriptions
  • foreseenUnintendedEffects content: Reduced clarity about which projects were performed for the previous employer
  • textReferences content: this notice was not included in all paragraphs of the lengthy individual descriptions of those projects; That qualifier was not repeated within the specific descriptions of each of those projects.
  • temporalExtent content: instant
  • temporalSequence content: 4
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Disclosure_Omission",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.244461+00:00",
  "proeth:description": "XYZ Engineers and Engineer B did not repeat the prior-employer attribution notice within all paragraphs of the lengthy individual project descriptions, a non-performance the case treats as the conduct that violates State Z\u0027s specific rules.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Project Manager",
  "proeth:foreseenUnintendedEffects": [
    "Reduced clarity about which projects were performed for the previous employer"
  ],
  "proeth:fulfillsObligation": [],
  "proeth:hasAgent": "XYZ Engineers and Engineer B",
  "proeth:hasMentalState": "not clearly deliberate; the case notes the section-level notice appears to indicate an intent to provide transparency",
  "proeth:initiates": [
    "State Z Rule Noncompliance",
    "Potentially Misleading Presentation"
  ],
  "proeth:intendedOutcome": "Avoid repetitive disclaimers within lengthy project descriptions",
  "proeth:raisesObligation": [],
  "proeth:requiresCapability": [
    "Proposal preparation"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "During preparation of qualification statements accompanying project proposals",
  "proeth:temporalSequence": 4,
  "proeth:textReferences": [
    "this notice was not included in all paragraphs of the lengthy individual descriptions of those projects",
    "That qualifier was not repeated within the specific descriptions of each of those projects."
  ],
  "proeth:violatesObligation": [
    "State Z Attribution Requirement",
    "Avoidance of Misrepresentation of Qualifications"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Disclosure Omission"
}

Description: Engineer A questioned whether XYZ's proposal and marketing practice was misleading to clients and unethical, initiating the ethical inquiry of the case.

Temporal Marker: After observing XYZ Engineers' proposal practice instant

Fluent Transitions:
Initiates (1)
  • Ethical Concern Raised

Mental State: deliberate

Intended Outcome: Determine whether the proposal practice is misleading and unethical

Foreseen Unintended Effects:

  • Potential appearance of competitive motive, since Engineer A works for a rival firm
Guided By Principles:
  • Transparency
Required Capabilities:
Ethical judgment
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Transparency
  • requiresCapability: Ethical judgment
  • initiates: Ethical Concern Raised
Literal extractions (kept for synthesis)
  • description content: Engineer A questioned whether XYZ's proposal and marketing practice was misleading to clients and unethical, initiating the ethical inquiry of the case.
  • hasAgent content: Engineer A
  • temporalMarker content: After observing XYZ Engineers' proposal practice
  • eventRoleContext content: Employee, ABC Consultants
  • hasMentalState content: deliberate
  • intendedOutcome content: Determine whether the proposal practice is misleading and unethical
  • foreseenUnintendedEffects content: Potential appearance of competitive motive, since Engineer A works for a rival firm
  • textReferences content: Engineer A questions whether this proposal/marketing practice is misleading to clients and unethical.
  • temporalExtent content: instant
  • temporalSequence content: 6
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Ethics_Questioning",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.244487+00:00",
  "proeth:description": "Engineer A questioned whether XYZ\u0027s proposal and marketing practice was misleading to clients and unethical, initiating the ethical inquiry of the case.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Employee, ABC Consultants",
  "proeth:foreseenUnintendedEffects": [
    "Potential appearance of competitive motive, since Engineer A works for a rival firm"
  ],
  "proeth:guidedByPrinciple": [
    "Transparency"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Ethical Concern Raised"
  ],
  "proeth:intendedOutcome": "Determine whether the proposal practice is misleading and unethical",
  "proeth:requiresCapability": [
    "Ethical judgment"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "After observing XYZ Engineers\u0027 proposal practice",
  "proeth:temporalSequence": 6,
  "proeth:textReferences": [
    "Engineer A questions whether this proposal/marketing practice is misleading to clients and unethical."
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Ethics Questioning"
}

Description: Engineer A decided to review the NSPE Code of Ethics and the engineering licensing board laws and rules of professional conduct in both State Q and State Z, finding State Q's rules general and State Z's rules highly specific.

Temporal Marker: After questioning the proposal practice interval

Fluent Transitions:
Initiates (1)
  • Knowledge of Divergent Jurisdictional Rules

Mental State: deliberate

Intended Outcome: Understand the applicable ethical and regulatory standards in both jurisdictions before deciding whether to act

Required Capabilities:
Regulatory research Ethical judgment
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • requiresCapability: Regulatory research; Ethical judgment
  • initiates: Knowledge of Divergent Jurisdictional Rules
Literal extractions (kept for synthesis)
  • description content: Engineer A decided to review the NSPE Code of Ethics and the engineering licensing board laws and rules of professional conduct in both State Q and State Z, finding State Q's rules general and State Z's rules highly specific.
  • hasAgent content: Engineer A
  • temporalMarker content: After questioning the proposal practice
  • eventRoleContext content: Employee, ABC Consultants
  • hasMentalState content: deliberate
  • intendedOutcome content: Understand the applicable ethical and regulatory standards in both jurisdictions before deciding whether to act
  • textReferences content: Engineer A decides to review the NSPE Code of Ethics and the engineering licensing board law and rules of professional conduct in both states.
  • temporalExtent content: interval
  • temporalSequence content: 7
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Code_and_Rules_Review",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.244515+00:00",
  "proeth:description": "Engineer A decided to review the NSPE Code of Ethics and the engineering licensing board laws and rules of professional conduct in both State Q and State Z, finding State Q\u0027s rules general and State Z\u0027s rules highly specific.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Employee, ABC Consultants",
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Knowledge of Divergent Jurisdictional Rules"
  ],
  "proeth:intendedOutcome": "Understand the applicable ethical and regulatory standards in both jurisdictions before deciding whether to act",
  "proeth:requiresCapability": [
    "Regulatory research",
    "Ethical judgment"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "After questioning the proposal practice",
  "proeth:temporalSequence": 7,
  "proeth:textReferences": [
    "Engineer A decides to review the NSPE Code of Ethics and the engineering licensing board law and rules of professional conduct in both states."
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Code and Rules Review"
}

Description: Engineer A considered whether the proposal and marketing practice was unethical under the NSPE Code of Ethics and whether there was an obligation to report to the two licensing jurisdictions, the pending decision the case poses.

Temporal Marker: After reviewing the NSPE Code and both states' rules interval

Fluent Transitions:
Initiates (1)
  • Reporting Decision Pending

Mental State: deliberate

Intended Outcome: Decide whether an obligation exists to report the conduct to the licensing boards of State Q and State Z

Foreseen Unintended Effects:

  • Reporting a competitor could be perceived as self-interested
Guided By Principles:
  • Duty to Report Violations
Required Capabilities:
Ethical judgment Regulatory interpretation
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Duty to Report Violations
  • requiresCapability: Ethical judgment; Regulatory interpretation
  • initiates: Reporting Decision Pending
Literal extractions (kept for synthesis)
  • description content: Engineer A considered whether the proposal and marketing practice was unethical under the NSPE Code of Ethics and whether there was an obligation to report to the two licensing jurisdictions, the pending decision the case poses.
  • hasAgent content: Engineer A
  • temporalMarker content: After reviewing the NSPE Code and both states' rules
  • eventRoleContext content: Employee, ABC Consultants
  • hasMentalState content: deliberate
  • intendedOutcome content: Decide whether an obligation exists to report the conduct to the licensing boards of State Q and State Z
  • foreseenUnintendedEffects content: Reporting a competitor could be perceived as self-interested
  • textReferences content: Engineer Q considers whether this proposal/marketing practice is unethical in accordance with the NSPE Code of Ethics and whether Engineer A has an obligation to report to the two licensing jurisdictions.
  • temporalExtent content: interval
  • temporalSequence content: 10
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Reporting_Deliberation",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.244541+00:00",
  "proeth:description": "Engineer A considered whether the proposal and marketing practice was unethical under the NSPE Code of Ethics and whether there was an obligation to report to the two licensing jurisdictions, the pending decision the case poses.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventRoleContext": "Employee, ABC Consultants",
  "proeth:foreseenUnintendedEffects": [
    "Reporting a competitor could be perceived as self-interested"
  ],
  "proeth:guidedByPrinciple": [
    "Duty to Report Violations"
  ],
  "proeth:hasAgent": "Engineer A",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "Reporting Decision Pending"
  ],
  "proeth:intendedOutcome": "Decide whether an obligation exists to report the conduct to the licensing boards of State Q and State Z",
  "proeth:requiresCapability": [
    "Ethical judgment",
    "Regulatory interpretation"
  ],
  "proeth:temporalExtent": "interval",
  "proeth:temporalMarker": "After reviewing the NSPE Code and both states\u0027 rules",
  "proeth:temporalSequence": 10,
  "proeth:textReferences": [
    "Engineer Q considers whether this proposal/marketing practice is unethical in accordance with the NSPE Code of Ethics and whether Engineer A has an obligation to report to the two licensing jurisdictions."
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Reporting Deliberation"
}

Description: The BER determined that Engineer A had no obligation to report to the State Q licensing board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to the State Z licensing board under that state's specific rules.

Temporal Marker: During ethical review of the case instant

Fluent Transitions:
Initiates (1)
  • State Z Reporting Obligation Established
Terminates (1)
  • Reporting Decision Pending

Mental State: deliberate

Intended Outcome: Resolve whether the practice constituted misrepresentation and whether Engineer A must report in each jurisdiction

Guided By Principles:
  • Duty to Report Violations
Required Capabilities:
Ethical analysis Regulatory interpretation
Within Competence: Yes
Field classification (triples vs literals)
Relations (structural triples)
  • guidedByPrinciple: Duty to Report Violations
  • requiresCapability: Ethical analysis; Regulatory interpretation
  • initiates: State Z Reporting Obligation Established
  • terminates: Reporting Decision Pending
Literal extractions (kept for synthesis)
  • description content: The BER determined that Engineer A had no obligation to report to the State Q licensing board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to the State Z licensing board under that state's specific rules.
  • hasAgent content: NSPE Board of Ethical Review
  • temporalMarker content: During ethical review of the case
  • eventRoleContext content: BER
  • hasMentalState content: deliberate
  • intendedOutcome content: Resolve whether the practice constituted misrepresentation and whether Engineer A must report in each jurisdiction
  • textReferences content: The BER concludes that it would not riseto misrepresentation, and that Engineer A did not have an obligation to report to the engineering licensing board in State Q.; The BER concludes that Engineer A has a clear obligation to report the misconduct to the engineering licensing board in State Z.
  • temporalExtent content: instant
  • temporalSequence content: 11
  • withinCompetence assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Action_Board_Determination",
  "@type": "proeth:Action",
  "generatedAtTime": "2026-07-14T22:01:19.244565+00:00",
  "proeth:description": "The BER determined that Engineer A had no obligation to report to the State Q licensing board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to the State Z licensing board under that state\u0027s specific rules.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventRoleContext": "BER",
  "proeth:guidedByPrinciple": [
    "Duty to Report Violations"
  ],
  "proeth:hasAgent": "NSPE Board of Ethical Review",
  "proeth:hasMentalState": "deliberate",
  "proeth:initiates": [
    "State Z Reporting Obligation Established"
  ],
  "proeth:intendedOutcome": "Resolve whether the practice constituted misrepresentation and whether Engineer A must report in each jurisdiction",
  "proeth:requiresCapability": [
    "Ethical analysis",
    "Regulatory interpretation"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "During ethical review of the case",
  "proeth:temporalSequence": 11,
  "proeth:terminates": [
    "Reporting Decision Pending"
  ],
  "proeth:textReferences": [
    "The BER concludes that it would not riseto misrepresentation, and that Engineer A did not have an obligation to report to the engineering licensing board in State Q.",
    "The BER concludes that Engineer A has a clear obligation to report the misconduct to the engineering licensing board in State Z."
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Board Determination"
}
Extracted Events (4)
Occurrences that trigger ethical considerations and state changes

Description: Under State Z's specific rule requiring the previous firm and the licensee's role to appear next to each project listing, the qualification statement's noncompliance automatically constituted misconduct by both Engineer B and XYZ Engineers once the presentation failed to meet the rule's specifics.

Temporal Marker: Upon submission of the qualification statements in State Z instant

Fluent Transitions:
Initiates (1)
  • State Z Misconduct State

Caused By Action: Action_Disclosure_Omission

Field classification (triples vs literals)
Relations (structural triples)
  • causedByAction: http://proethica.org/ontology/case/19#Action_Disclosure_Omission
  • initiates: State Z Misconduct State
Literal extractions (kept for synthesis)
  • description content: Under State Z's specific rule requiring the previous firm and the licensee's role to appear next to each project listing, the qualification statement's noncompliance automatically constituted misconduct by both Engineer B and XYZ Engineers once the presentation failed to meet the rule's specifics.
  • temporalMarker content: Upon submission of the qualification statements in State Z
  • textReferences content: The presentation by Engineer B and XYZ Engineers did not meet the specifics of this Rule and, accordingly, under that Rule, constituted misconduct on the part of both the individual and the firm.
  • eventType content: automatic
  • temporalExtent content: instant
  • temporalSequence content: 5
  • confidence assessment: 0.9
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Event_Misconduct_Constitution",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T22:01:19.244683+00:00",
  "proeth:causedByAction": "http://proethica.org/ontology/case/19#Action_Disclosure_Omission",
  "proeth:confidence": "0.9",
  "proeth:description": "Under State Z\u0027s specific rule requiring the previous firm and the licensee\u0027s role to appear next to each project listing, the qualification statement\u0027s noncompliance automatically constituted misconduct by both Engineer B and XYZ Engineers once the presentation failed to meet the rule\u0027s specifics.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventType": "automatic",
  "proeth:initiates": [
    "State Z Misconduct State"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Upon submission of the qualification statements in State Z",
  "proeth:temporalSequence": 5,
  "proeth:textReferences": [
    "The presentation by Engineer B and XYZ Engineers did not meet the specifics of this Rule and, accordingly, under that Rule, constituted misconduct on the part of both the individual and the firm."
  ],
  "rdfs:label": "Misconduct Constitution"
}

Description: During the review of licensing rules, it emerges that State Q's rules are general and patterned after the NCEES Model Rules while State Z's rules are much more specific about crediting prior projects, creating awareness that the same practice may be treated differently in the two jurisdictions.

Temporal Marker: During Engineer A's review of the NSPE Code and both states' licensing rules instant

Fluent Transitions:
Initiates (2)
  • Knowledge of Jurisdictional Rule Differences
  • Knowledge of Possible Rule Violation

Caused By Action: Action_Code_and_Rules_Review

Field classification (triples vs literals)
Relations (structural triples)
  • causedByAction: http://proethica.org/ontology/case/19#Action_Code_and_Rules_Review
  • initiates: Knowledge of Jurisdictional Rule Differences; Knowledge of Possible Rule Violation
Literal extractions (kept for synthesis)
  • description content: During the review of licensing rules, it emerges that State Q's rules are general and patterned after the NCEES Model Rules while State Z's rules are much more specific about crediting prior projects, creating awareness that the same practice may be treated differently in the two jurisdictions.
  • temporalMarker content: During Engineer A's review of the NSPE Code and both states' licensing rules
  • textReferences content: Engineer Q finds that the Rules in State Z, which have a long and unique legislative history, are much more specific, indicating in part that “a licensee who has been an employee of another design firm may not claim unconditional credit for design projects contracted for in the name of a previous employer”
  • eventType content: outcome
  • temporalExtent content: instant
  • temporalSequence content: 8
  • confidence assessment: 0.85
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Event_Rule_Divergence_Discovery",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T22:01:19.244648+00:00",
  "proeth:causedByAction": "http://proethica.org/ontology/case/19#Action_Code_and_Rules_Review",
  "proeth:confidence": "0.85",
  "proeth:description": "During the review of licensing rules, it emerges that State Q\u0027s rules are general and patterned after the NCEES Model Rules while State Z\u0027s rules are much more specific about crediting prior projects, creating awareness that the same practice may be treated differently in the two jurisdictions.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "outcome",
  "proeth:initiates": [
    "Knowledge of Jurisdictional Rule Differences",
    "Knowledge of Possible Rule Violation"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "During Engineer A\u0027s review of the NSPE Code and both states\u0027 licensing rules",
  "proeth:temporalSequence": 8,
  "proeth:textReferences": [
    "Engineer Q finds that the Rules in State Z, which have a long and unique legislative history, are much more specific, indicating in part that \u201ca licensee who has been an employee of another design firm may not claim unconditional credit for design projects contracted for in the name of a previous employer\u201d"
  ],
  "rdfs:label": "Rule Divergence Discovery"
}

Description: Because the rules in both states require a licensee with knowledge or reason to believe a violation has occurred to report it in writing, Engineer A's acquired knowledge of the State Z rule violation automatically triggered the applicability of the written reporting requirement.

Temporal Marker: Once Engineer A gained knowledge of the noncompliant presentation and the State Z rule instant

Fluent Transitions:
Initiates (1)
  • Reporting Obligation Active in State Z

Caused By Action: Action_Code_and_Rules_Review

Field classification (triples vs literals)
Relations (structural triples)
  • causedByAction: http://proethica.org/ontology/case/19#Action_Code_and_Rules_Review
  • initiates: Reporting Obligation Active in State Z
Literal extractions (kept for synthesis)
  • description content: Because the rules in both states require a licensee with knowledge or reason to believe a violation has occurred to report it in writing, Engineer A's acquired knowledge of the State Z rule violation automatically triggered the applicability of the written reporting requirement.
  • temporalMarker content: Once Engineer A gained knowledge of the noncompliant presentation and the State Z rule
  • textReferences content: The Rules in both states require a licensee who has knowledge or reason to believe that a person or firm has violated those Rules to report such knowledge or belief to the Board of Licensure in writing.
  • eventType content: automatic
  • temporalExtent content: instant
  • temporalSequence content: 9
  • confidence assessment: 0.78
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Event_Reporting_Duty_Activation",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T22:01:19.244709+00:00",
  "proeth:causedByAction": "http://proethica.org/ontology/case/19#Action_Code_and_Rules_Review",
  "proeth:confidence": "0.78",
  "proeth:description": "Because the rules in both states require a licensee with knowledge or reason to believe a violation has occurred to report it in writing, Engineer A\u0027s acquired knowledge of the State Z rule violation automatically triggered the applicability of the written reporting requirement.",
  "proeth:discoveredInSection": "facts",
  "proeth:eventType": "automatic",
  "proeth:initiates": [
    "Reporting Obligation Active in State Z"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "Once Engineer A gained knowledge of the noncompliant presentation and the State Z rule",
  "proeth:temporalSequence": 9,
  "proeth:textReferences": [
    "The Rules in both states require a licensee who has knowledge or reason to believe that a person or firm has violated those Rules to report such knowledge or belief to the Board of Licensure in writing."
  ],
  "rdfs:label": "Reporting Duty Activation"
}

Description: The BER's determination resulted in the conclusions that Engineer A had no obligation to report to State Q's board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to State Z's licensing board.

Temporal Marker: At the conclusion of the BER's review of the case instant

Fluent Transitions:
Initiates (2)
  • Confirmed Reporting Obligation in State Z
  • Confirmed Absence of State Q Reporting Obligation
Terminates (1)
  • Reporting Uncertainty

Caused By Action: Action_Board_Determination

Field classification (triples vs literals)
Relations (structural triples)
  • causedByAction: http://proethica.org/ontology/case/19#Action_Board_Determination
  • initiates: Confirmed Reporting Obligation in State Z; Confirmed Absence of State Q Reporting Obligation
  • terminates: Reporting Uncertainty
Literal extractions (kept for synthesis)
  • description content: The BER's determination resulted in the conclusions that Engineer A had no obligation to report to State Q's board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to State Z's licensing board.
  • temporalMarker content: At the conclusion of the BER's review of the case
  • textReferences content: The BER concludes that it would not riseto misrepresentation, and that Engineer A did not have an obligation to report to the engineering licensing board in State Q.; The BER concludes that Engineer A has a clear obligation to report the misconduct to the engineering licensing board in State Z.
  • eventType content: outcome
  • temporalExtent content: instant
  • temporalSequence content: 12
  • confidence assessment: 0.88
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#Event_Reporting_Obligation_Confirmation",
  "@type": "proeth:Event",
  "generatedAtTime": "2026-07-14T22:01:19.244733+00:00",
  "proeth:causedByAction": "http://proethica.org/ontology/case/19#Action_Board_Determination",
  "proeth:confidence": "0.88",
  "proeth:description": "The BER\u0027s determination resulted in the conclusions that Engineer A had no obligation to report to State Q\u0027s board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to State Z\u0027s licensing board.",
  "proeth:discoveredInSection": "discussion",
  "proeth:eventType": "outcome",
  "proeth:initiates": [
    "Confirmed Reporting Obligation in State Z",
    "Confirmed Absence of State Q Reporting Obligation"
  ],
  "proeth:temporalExtent": "instant",
  "proeth:temporalMarker": "At the conclusion of the BER\u0027s review of the case",
  "proeth:temporalSequence": 12,
  "proeth:terminates": [
    "Reporting Uncertainty"
  ],
  "proeth:textReferences": [
    "The BER concludes that it would not riseto misrepresentation, and that Engineer A did not have an obligation to report to the engineering licensing board in State Q.",
    "The BER concludes that Engineer A has a clear obligation to report the misconduct to the engineering licensing board in State Z."
  ],
  "rdfs:label": "Reporting Obligation Confirmation"
}
Causal Chains (8)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: ABC’s competitors, XYZ Engineers, hired a new project manager, Engineer B, with extensive experience in responsible charge of projects in another region, and began to market bridge and culvert designs in both states.

Necessary Factors (NESS):
  • Hiring of Engineer B by XYZ Engineers
  • Engineer B's prior project experience at another firm
  • XYZ's decision to market designs in both states
Sufficient Factors:
  • Combination of hiring Engineer B + marketing effort requiring qualification statements citing Engineer B's prior projects
Counterfactual Test: Without hiring Engineer B, XYZ would not have had his prior-employer projects to include in qualification statements, and the presentation practice at issue would not have arisen
Responsibility Attribution:

Agent: XYZ Engineers
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Project Manager Hiring
    XYZ Engineers hires Engineer B, who has extensive prior-employer project experience
  2. Marketing Expansion
    XYZ begins marketing bridge and culvert designs in State Q and State Z
  3. Qualification Statement Presentation
    XYZ's proposals cite Engineer B's prior-employer projects as part of the firm's qualifications
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Project Manager Hiring
  • effect: Qualification Statement Presentation
  • responsibleAgent: XYZ Engineers
Literal extractions (kept for synthesis)
  • causalLanguage content: ABC’s competitors, XYZ Engineers, hired a new project manager, Engineer B, with extensive experience in responsible charge of projects in another region, and began to market bridge and culvert designs in both states.
  • necessaryFactors content: Hiring of Engineer B by XYZ Engineers; Engineer B's prior project experience at another firm; XYZ's decision to market designs in both states
  • sufficientFactors content: Combination of hiring Engineer B + marketing effort requiring qualification statements citing Engineer B's prior projects
  • counterfactual content: Without hiring Engineer B, XYZ would not have had his prior-employer projects to include in qualification statements, and the presentation practice at issue would not have arisen
  • agentKnowledge content: Knew Engineer B's project experience came from a previous employer and intended to leverage it in marketing
  • interveningFactors content: Competitive market for bridge and culvert design services in two states
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Project Manager Hiring', 'proeth:description': 'XYZ Engineers hires Engineer B, who has extensive prior-employer project experience'}; {'proeth:step': 2, 'proeth:element': 'Marketing Expansion', 'proeth:description': 'XYZ begins marketing bridge and culvert designs in State Q and State Z'}; {'proeth:step': 3, 'proeth:element': 'Qualification Statement Presentation', 'proeth:description': "XYZ's proposals cite Engineer B's prior-employer projects as part of the firm's qualifications"}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_1",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244796+00:00",
  "proeth:agentKnowledge": "Knew Engineer B\u0027s project experience came from a previous employer and intended to leverage it in marketing",
  "proeth:causalLanguage": "ABC\u2019s competitors, XYZ Engineers, hired a new project manager, Engineer B, with extensive experience in responsible charge of projects in another region, and began to market bridge and culvert designs in both states.",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ Engineers hires Engineer B, who has extensive prior-employer project experience",
      "proeth:element": "Project Manager Hiring",
      "proeth:step": 1
    },
    {
      "proeth:description": "XYZ begins marketing bridge and culvert designs in State Q and State Z",
      "proeth:element": "Marketing Expansion",
      "proeth:step": 2
    },
    {
      "proeth:description": "XYZ\u0027s proposals cite Engineer B\u0027s prior-employer projects as part of the firm\u0027s qualifications",
      "proeth:element": "Qualification Statement Presentation",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Project Manager Hiring",
  "proeth:counterfactual": "Without hiring Engineer B, XYZ would not have had his prior-employer projects to include in qualification statements, and the presentation practice at issue would not have arisen",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Qualification Statement Presentation",
  "proeth:interveningFactors": [
    "Competitive market for bridge and culvert design services in two states"
  ],
  "proeth:necessaryFactors": [
    "Hiring of Engineer B by XYZ Engineers",
    "Engineer B\u0027s prior project experience at another firm",
    "XYZ\u0027s decision to market designs in both states"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "XYZ Engineers",
  "proeth:sufficientFactors": [
    "Combination of hiring Engineer B + marketing effort requiring qualification statements citing Engineer B\u0027s prior projects"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: However, while this notice appears to indicate an intent to provide transparency, this notice was not included in all paragraphs of the lengthy individual descriptions of those projects.

Necessary Factors (NESS):
  • Inclusion of Engineer B's prior projects in the proposal
  • Lengthy multi-paragraph project descriptions
  • Decision to place the attribution notice only at the beginning of the qualification section
Sufficient Factors:
  • Combination of attribution at the section beginning only + long project descriptions without repeated attribution
Counterfactual Test: Had attribution been repeated next to each project listing and within each paragraph, no omission would have existed
Responsibility Attribution:

Agent: XYZ Engineers and Engineer B
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Qualification Statement Presentation
    XYZ prepares proposals identifying Engineer B's prior-employer projects with employer and client names
  2. Attribution Placement Choice
    The attribution notice is placed only at the beginning of the individual qualification section
  3. Disclosure Omission
    The prior-employer notice is not repeated within all paragraphs of the lengthy project descriptions
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Qualification Statement Presentation
  • effect: Disclosure Omission
  • responsibleAgent: XYZ Engineers and Engineer B
Literal extractions (kept for synthesis)
  • causalLanguage content: However, while this notice appears to indicate an intent to provide transparency, this notice was not included in all paragraphs of the lengthy individual descriptions of those projects.
  • necessaryFactors content: Inclusion of Engineer B's prior projects in the proposal; Lengthy multi-paragraph project descriptions; Decision to place the attribution notice only at the beginning of the qualification section
  • sufficientFactors content: Combination of attribution at the section beginning only + long project descriptions without repeated attribution
  • counterfactual content: Had attribution been repeated next to each project listing and within each paragraph, no omission would have existed
  • agentKnowledge content: Aware the projects were performed under previous employment and intended some transparency, but did not verify attribution appeared throughout the descriptions
  • interveningFactors content: Length and structure of the individual project descriptions
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Qualification Statement Presentation', 'proeth:description': "XYZ prepares proposals identifying Engineer B's prior-employer projects with employer and client names"}; {'proeth:step': 2, 'proeth:element': 'Attribution Placement Choice', 'proeth:description': 'The attribution notice is placed only at the beginning of the individual qualification section'}; {'proeth:step': 3, 'proeth:element': 'Disclosure Omission', 'proeth:description': 'The prior-employer notice is not repeated within all paragraphs of the lengthy project descriptions'}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_2",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244826+00:00",
  "proeth:agentKnowledge": "Aware the projects were performed under previous employment and intended some transparency, but did not verify attribution appeared throughout the descriptions",
  "proeth:causalLanguage": "However, while this notice appears to indicate an intent to provide transparency, this notice was not included in all paragraphs of the lengthy individual descriptions of those projects.",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ prepares proposals identifying Engineer B\u0027s prior-employer projects with employer and client names",
      "proeth:element": "Qualification Statement Presentation",
      "proeth:step": 1
    },
    {
      "proeth:description": "The attribution notice is placed only at the beginning of the individual qualification section",
      "proeth:element": "Attribution Placement Choice",
      "proeth:step": 2
    },
    {
      "proeth:description": "The prior-employer notice is not repeated within all paragraphs of the lengthy project descriptions",
      "proeth:element": "Disclosure Omission",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Qualification Statement Presentation",
  "proeth:counterfactual": "Had attribution been repeated next to each project listing and within each paragraph, no omission would have existed",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Disclosure Omission",
  "proeth:interveningFactors": [
    "Length and structure of the individual project descriptions"
  ],
  "proeth:necessaryFactors": [
    "Inclusion of Engineer B\u0027s prior projects in the proposal",
    "Lengthy multi-paragraph project descriptions",
    "Decision to place the attribution notice only at the beginning of the qualification section"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "XYZ Engineers and Engineer B",
  "proeth:sufficientFactors": [
    "Combination of attribution at the section beginning only + long project descriptions without repeated attribution"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A questions whether this proposal/marketing practice is misleading to clients and unethical.

Necessary Factors (NESS):
  • Disclosure omission in XYZ's proposals
  • Engineer A's awareness of XYZ's proposal practice as a competitor employee
  • Engineer A's sensitivity to professional ethics obligations
Sufficient Factors:
  • Combination of observable ambiguous attribution practice + Engineer A's professional ethical vigilance
Counterfactual Test: If the attribution had been consistently repeated in every paragraph, the practice would likely not have appeared potentially misleading and Engineer A would have had no basis to question it
Responsibility Attribution:

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

Causal Sequence:
  1. Disclosure Omission
    Attribution notice absent from all paragraphs of the project descriptions
  2. Observation by Competitor
    Engineer A becomes aware of XYZ's qualification statement practice
  3. Ethics Questioning
    Engineer A questions whether the practice is misleading to clients and unethical
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Disclosure Omission
  • effect: Ethics Questioning
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer A questions whether this proposal/marketing practice is misleading to clients and unethical.
  • necessaryFactors content: Disclosure omission in XYZ's proposals; Engineer A's awareness of XYZ's proposal practice as a competitor employee; Engineer A's sensitivity to professional ethics obligations
  • sufficientFactors content: Combination of observable ambiguous attribution practice + Engineer A's professional ethical vigilance
  • counterfactual content: If the attribution had been consistently repeated in every paragraph, the practice would likely not have appeared potentially misleading and Engineer A would have had no basis to question it
  • agentKnowledge content: Observed the proposal practice and knew of the NSPE Code and state licensing rules as sources of guidance
  • interveningFactors content: Competitive relationship between ABC Consultants and XYZ Engineers
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Disclosure Omission', 'proeth:description': 'Attribution notice absent from all paragraphs of the project descriptions'}; {'proeth:step': 2, 'proeth:element': 'Observation by Competitor', 'proeth:description': "Engineer A becomes aware of XYZ's qualification statement practice"}; {'proeth:step': 3, 'proeth:element': 'Ethics Questioning', 'proeth:description': 'Engineer A questions whether the practice is misleading to clients and unethical'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_3",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244850+00:00",
  "proeth:agentKnowledge": "Observed the proposal practice and knew of the NSPE Code and state licensing rules as sources of guidance",
  "proeth:causalLanguage": "Engineer A questions whether this proposal/marketing practice is misleading to clients and unethical.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Attribution notice absent from all paragraphs of the project descriptions",
      "proeth:element": "Disclosure Omission",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A becomes aware of XYZ\u0027s qualification statement practice",
      "proeth:element": "Observation by Competitor",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A questions whether the practice is misleading to clients and unethical",
      "proeth:element": "Ethics Questioning",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Disclosure Omission",
  "proeth:counterfactual": "If the attribution had been consistently repeated in every paragraph, the practice would likely not have appeared potentially misleading and Engineer A would have had no basis to question it",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Ethics Questioning",
  "proeth:interveningFactors": [
    "Competitive relationship between ABC Consultants and XYZ Engineers"
  ],
  "proeth:necessaryFactors": [
    "Disclosure omission in XYZ\u0027s proposals",
    "Engineer A\u0027s awareness of XYZ\u0027s proposal practice as a competitor employee",
    "Engineer A\u0027s sensitivity to professional ethics obligations"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of observable ambiguous attribution practice + Engineer A\u0027s professional ethical vigilance"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A decides to review the NSPE Code of Ethics and the engineering licensing board law and rules of professional conduct in both states.

Necessary Factors (NESS):
  • Engineer A's ethical concern about the practice
  • Existence of applicable NSPE Code and state licensing rules
  • Engineer A's practice in both State Q and State Z
Sufficient Factors:
  • Engineer A's ethical concern combined with availability of governing codes and rules to consult
Counterfactual Test: Without questioning the practice, Engineer A would have had no reason to undertake the review of the Code and both states' rules
Responsibility Attribution:

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

Causal Sequence:
  1. Ethics Questioning
    Engineer A questions whether the marketing practice is misleading and unethical
  2. Code and Rules Review
    Engineer A reviews the NSPE Code of Ethics and both states' licensing rules
  3. Rule Divergence Discovery
    Engineer A discovers that State Q's rules are general while State Z's are highly specific
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Ethics Questioning
  • effect: Code and Rules Review
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer A decides to review the NSPE Code of Ethics and the engineering licensing board law and rules of professional conduct in both states.
  • necessaryFactors content: Engineer A's ethical concern about the practice; Existence of applicable NSPE Code and state licensing rules; Engineer A's practice in both State Q and State Z
  • sufficientFactors content: Engineer A's ethical concern combined with availability of governing codes and rules to consult
  • counterfactual content: Without questioning the practice, Engineer A would have had no reason to undertake the review of the Code and both states' rules
  • agentKnowledge content: Knew ethical questions should be resolved by consulting the NSPE Code and applicable state licensing rules
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Ethics Questioning', 'proeth:description': 'Engineer A questions whether the marketing practice is misleading and unethical'}; {'proeth:step': 2, 'proeth:element': 'Code and Rules Review', 'proeth:description': "Engineer A reviews the NSPE Code of Ethics and both states' licensing rules"}; {'proeth:step': 3, 'proeth:element': 'Rule Divergence Discovery', 'proeth:description': "Engineer A discovers that State Q's rules are general while State Z's are highly specific"}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_4",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244871+00:00",
  "proeth:agentKnowledge": "Knew ethical questions should be resolved by consulting the NSPE Code and applicable state licensing rules",
  "proeth:causalLanguage": "Engineer A decides to review the NSPE Code of Ethics and the engineering licensing board law and rules of professional conduct in both states.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A questions whether the marketing practice is misleading and unethical",
      "proeth:element": "Ethics Questioning",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A reviews the NSPE Code of Ethics and both states\u0027 licensing rules",
      "proeth:element": "Code and Rules Review",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A discovers that State Q\u0027s rules are general while State Z\u0027s are highly specific",
      "proeth:element": "Rule Divergence Discovery",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Ethics Questioning",
  "proeth:counterfactual": "Without questioning the practice, Engineer A would have had no reason to undertake the review of the Code and both states\u0027 rules",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Code and Rules Review",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s ethical concern about the practice",
    "Existence of applicable NSPE Code and state licensing rules",
    "Engineer A\u0027s practice in both State Q and State Z"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Engineer A\u0027s ethical concern combined with availability of governing codes and rules to consult"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer Q finds that the Rules in State Z, which have a long and unique legislative history, are much more specific, indicating in part that “a licensee who has been an employee of another design firm may not claim unconditional credit for design projects contracted for in the name of a previous employer”

Necessary Factors (NESS):
  • Engineer A's decision to review the rules of both jurisdictions
  • Actual textual difference between State Q's general rules and State Z's specific rules
Sufficient Factors:
  • Careful review of both states' rules given their pre-existing divergence
Counterfactual Test: Without reviewing both jurisdictions' rules, the divergence between State Q's general standard and State Z's specific attribution requirement would not have been discovered
Responsibility Attribution:

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

Causal Sequence:
  1. Code and Rules Review
    Engineer A reviews the NSPE Code and both states' licensing rules
  2. State Q Rule Reading
    Engineer A finds State Q's rules are general and patterned after the NCEES Model Rules
  3. State Z Rule Reading
    Engineer A finds State Z's rules specifically require prior-firm attribution next to each project listing
  4. Rule Divergence Discovery
    The differing stringency of the two jurisdictions' rules emerges
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Code and Rules Review
  • effect: Rule Divergence Discovery
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: Engineer Q finds that the Rules in State Z, which have a long and unique legislative history, are much more specific, indicating in part that “a licensee who has been an employee of another design firm may not claim unconditional credit for design projects contracted for in the name of a previous employer”
  • necessaryFactors content: Engineer A's decision to review the rules of both jurisdictions; Actual textual difference between State Q's general rules and State Z's specific rules
  • sufficientFactors content: Careful review of both states' rules given their pre-existing divergence
  • counterfactual content: Without reviewing both jurisdictions' rules, the divergence between State Q's general standard and State Z's specific attribution requirement would not have been discovered
  • agentKnowledge content: Knew rules could vary between jurisdictions and that both states governed the practice at issue
  • interveningFactors content: State Z's long and unique legislative history producing more specific rules
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Code and Rules Review', 'proeth:description': "Engineer A reviews the NSPE Code and both states' licensing rules"}; {'proeth:step': 2, 'proeth:element': 'State Q Rule Reading', 'proeth:description': "Engineer A finds State Q's rules are general and patterned after the NCEES Model Rules"}; {'proeth:step': 3, 'proeth:element': 'State Z Rule Reading', 'proeth:description': "Engineer A finds State Z's rules specifically require prior-firm attribution next to each project listing"}; {'proeth:step': 4, 'proeth:element': 'Rule Divergence Discovery', 'proeth:description': "The differing stringency of the two jurisdictions' rules emerges"}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_5",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244891+00:00",
  "proeth:agentKnowledge": "Knew rules could vary between jurisdictions and that both states governed the practice at issue",
  "proeth:causalLanguage": "Engineer Q finds that the Rules in State Z, which have a long and unique legislative history, are much more specific, indicating in part that \u201ca licensee who has been an employee of another design firm may not claim unconditional credit for design projects contracted for in the name of a previous employer\u201d",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A reviews the NSPE Code and both states\u0027 licensing rules",
      "proeth:element": "Code and Rules Review",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A finds State Q\u0027s rules are general and patterned after the NCEES Model Rules",
      "proeth:element": "State Q Rule Reading",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A finds State Z\u0027s rules specifically require prior-firm attribution next to each project listing",
      "proeth:element": "State Z Rule Reading",
      "proeth:step": 3
    },
    {
      "proeth:description": "The differing stringency of the two jurisdictions\u0027 rules emerges",
      "proeth:element": "Rule Divergence Discovery",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Code and Rules Review",
  "proeth:counterfactual": "Without reviewing both jurisdictions\u0027 rules, the divergence between State Q\u0027s general standard and State Z\u0027s specific attribution requirement would not have been discovered",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Rule Divergence Discovery",
  "proeth:interveningFactors": [
    "State Z\u0027s long and unique legislative history producing more specific rules"
  ],
  "proeth:necessaryFactors": [
    "Engineer A\u0027s decision to review the rules of both jurisdictions",
    "Actual textual difference between State Q\u0027s general rules and State Z\u0027s specific rules"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Careful review of both states\u0027 rules given their pre-existing divergence"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: The presentation by Engineer B and XYZ Engineers did not meet the specifics of this Rule and, accordingly, under that Rule, constituted misconduct on the part of both the individual and the firm.

Necessary Factors (NESS):
  • Failure to place the previous firm's name and Engineer B's specific role next to each project listing
  • State Z's specific rule requiring such placement
  • Marketing of the proposals within State Z's jurisdiction
Sufficient Factors:
  • Combination of the omission + State Z's specific attribution rule applying to the proposals
Counterfactual Test: Had the attribution appeared next to each specific project listing as State Z's rule requires, no misconduct would have been constituted; note the same omission did not constitute misrepresentation under State Q's more general rule
Responsibility Attribution:

Agent: XYZ Engineers and Engineer B
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Disclosure Omission
    Attribution notice not repeated within all paragraphs or next to each project listing
  2. Proposal Submission in State Z
    The qualification statements are used to market designs in State Z
  3. Rule Application
    State Z's rule requiring attribution next to each project listing applies to the presentation
  4. Misconduct Constitution
    The presentation fails the rule's specifics and constitutes misconduct by Engineer B and XYZ
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Disclosure Omission
  • effect: Misconduct Constitution
  • responsibleAgent: XYZ Engineers and Engineer B
Literal extractions (kept for synthesis)
  • causalLanguage content: The presentation by Engineer B and XYZ Engineers did not meet the specifics of this Rule and, accordingly, under that Rule, constituted misconduct on the part of both the individual and the firm.
  • necessaryFactors content: Failure to place the previous firm's name and Engineer B's specific role next to each project listing; State Z's specific rule requiring such placement; Marketing of the proposals within State Z's jurisdiction
  • sufficientFactors content: Combination of the omission + State Z's specific attribution rule applying to the proposals
  • counterfactual content: Had the attribution appeared next to each specific project listing as State Z's rule requires, no misconduct would have been constituted; note the same omission did not constitute misrepresentation under State Q's more general rule
  • agentKnowledge content: Intended transparency by identifying the prior employer and clients at the section beginning, but apparently did not verify compliance with State Z's specific rule
  • interveningFactors content: State Z's uniquely specific rules arising from its legislative history
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Disclosure Omission', 'proeth:description': 'Attribution notice not repeated within all paragraphs or next to each project listing'}; {'proeth:step': 2, 'proeth:element': 'Proposal Submission in State Z', 'proeth:description': 'The qualification statements are used to market designs in State Z'}; {'proeth:step': 3, 'proeth:element': 'Rule Application', 'proeth:description': "State Z's rule requiring attribution next to each project listing applies to the presentation"}; {'proeth:step': 4, 'proeth:element': 'Misconduct Constitution', 'proeth:description': "The presentation fails the rule's specifics and constitutes misconduct by Engineer B and XYZ"}
  • responsibilityType assessment: shared
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_6",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244911+00:00",
  "proeth:agentKnowledge": "Intended transparency by identifying the prior employer and clients at the section beginning, but apparently did not verify compliance with State Z\u0027s specific rule",
  "proeth:causalLanguage": "The presentation by Engineer B and XYZ Engineers did not meet the specifics of this Rule and, accordingly, under that Rule, constituted misconduct on the part of both the individual and the firm.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Attribution notice not repeated within all paragraphs or next to each project listing",
      "proeth:element": "Disclosure Omission",
      "proeth:step": 1
    },
    {
      "proeth:description": "The qualification statements are used to market designs in State Z",
      "proeth:element": "Proposal Submission in State Z",
      "proeth:step": 2
    },
    {
      "proeth:description": "State Z\u0027s rule requiring attribution next to each project listing applies to the presentation",
      "proeth:element": "Rule Application",
      "proeth:step": 3
    },
    {
      "proeth:description": "The presentation fails the rule\u0027s specifics and constitutes misconduct by Engineer B and XYZ",
      "proeth:element": "Misconduct Constitution",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Disclosure Omission",
  "proeth:counterfactual": "Had the attribution appeared next to each specific project listing as State Z\u0027s rule requires, no misconduct would have been constituted; note the same omission did not constitute misrepresentation under State Q\u0027s more general rule",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Misconduct Constitution",
  "proeth:interveningFactors": [
    "State Z\u0027s uniquely specific rules arising from its legislative history"
  ],
  "proeth:necessaryFactors": [
    "Failure to place the previous firm\u0027s name and Engineer B\u0027s specific role next to each project listing",
    "State Z\u0027s specific rule requiring such placement",
    "Marketing of the proposals within State Z\u0027s jurisdiction"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "XYZ Engineers and Engineer B",
  "proeth:sufficientFactors": [
    "Combination of the omission + State Z\u0027s specific attribution rule applying to the proposals"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: The Rules in both states require a licensee who has knowledge or reason to believe that a person or firm has violated those Rules to report such knowledge or belief to the Board of Licensure in writing.

Necessary Factors (NESS):
  • Actual violation of State Z's rule by Engineer B and XYZ
  • Engineer A's knowledge of the violation gained through review
  • State Z's mandatory reporting rule for licensees with knowledge of violations
Sufficient Factors:
  • Combination of constituted misconduct + Engineer A's knowledge + the mandatory reporting rule
Counterfactual Test: If no misconduct had been constituted (as in State Q), Engineer A would have had no knowledge of a violation and the mandatory reporting duty would not have been triggered
Responsibility Attribution:

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

Causal Sequence:
  1. Misconduct Constitution
    XYZ's presentation constitutes misconduct under State Z's specific rule
  2. Knowledge Acquisition
    Engineer A's rule review gives him knowledge or reason to believe a violation occurred
  3. Reporting Duty Activation
    Both states' mandatory reporting rules attach to Engineer A's knowledge, obligating written report
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Misconduct Constitution
  • effect: Reporting Duty Activation
  • responsibleAgent: Engineer A
Literal extractions (kept for synthesis)
  • causalLanguage content: The Rules in both states require a licensee who has knowledge or reason to believe that a person or firm has violated those Rules to report such knowledge or belief to the Board of Licensure in writing.
  • necessaryFactors content: Actual violation of State Z's rule by Engineer B and XYZ; Engineer A's knowledge of the violation gained through review; State Z's mandatory reporting rule for licensees with knowledge of violations
  • sufficientFactors content: Combination of constituted misconduct + Engineer A's knowledge + the mandatory reporting rule
  • counterfactual content: If no misconduct had been constituted (as in State Q), Engineer A would have had no knowledge of a violation and the mandatory reporting duty would not have been triggered
  • agentKnowledge content: After review, knew or had reason to believe XYZ's presentation violated State Z's specific rule
  • interveningFactors content: State Z's mandatory reporting rule; NSPE Code obligation to report those believed guilty of unethical or illegal practice
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Misconduct Constitution', 'proeth:description': "XYZ's presentation constitutes misconduct under State Z's specific rule"}; {'proeth:step': 2, 'proeth:element': 'Knowledge Acquisition', 'proeth:description': "Engineer A's rule review gives him knowledge or reason to believe a violation occurred"}; {'proeth:step': 3, 'proeth:element': 'Reporting Duty Activation', 'proeth:description': "Both states' mandatory reporting rules attach to Engineer A's knowledge, obligating written report"}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_7",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244931+00:00",
  "proeth:agentKnowledge": "After review, knew or had reason to believe XYZ\u0027s presentation violated State Z\u0027s specific rule",
  "proeth:causalLanguage": "The Rules in both states require a licensee who has knowledge or reason to believe that a person or firm has violated those Rules to report such knowledge or belief to the Board of Licensure in writing.",
  "proeth:causalSequence": [
    {
      "proeth:description": "XYZ\u0027s presentation constitutes misconduct under State Z\u0027s specific rule",
      "proeth:element": "Misconduct Constitution",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A\u0027s rule review gives him knowledge or reason to believe a violation occurred",
      "proeth:element": "Knowledge Acquisition",
      "proeth:step": 2
    },
    {
      "proeth:description": "Both states\u0027 mandatory reporting rules attach to Engineer A\u0027s knowledge, obligating written report",
      "proeth:element": "Reporting Duty Activation",
      "proeth:step": 3
    }
  ],
  "proeth:cause": "Misconduct Constitution",
  "proeth:counterfactual": "If no misconduct had been constituted (as in State Q), Engineer A would have had no knowledge of a violation and the mandatory reporting duty would not have been triggered",
  "proeth:discoveredInSection": "facts",
  "proeth:effect": "Reporting Duty Activation",
  "proeth:interveningFactors": [
    "State Z\u0027s mandatory reporting rule",
    "NSPE Code obligation to report those believed guilty of unethical or illegal practice"
  ],
  "proeth:necessaryFactors": [
    "Actual violation of State Z\u0027s rule by Engineer B and XYZ",
    "Engineer A\u0027s knowledge of the violation gained through review",
    "State Z\u0027s mandatory reporting rule for licensees with knowledge of violations"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Combination of constituted misconduct + Engineer A\u0027s knowledge + the mandatory reporting rule"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: The BER concludes that it would not riseto misrepresentation, and that Engineer A did not have an obligation to report to the engineering licensing board in State Q.

Necessary Factors (NESS):
  • BER's assessment that the presentation did not rise to misrepresentation under State Q's general rule
  • BER's finding that the presentation failed State Z's specific rule
  • The divergent texts of the two states' rules
Sufficient Factors:
  • BER's application of each jurisdiction's rule text to the same set of facts
Counterfactual Test: Had State Z's rules been as general as State Q's, the BER would likely have found no reporting obligation in either state; had State Q's rules been as specific as State Z's, reporting would have been required in both
Responsibility Attribution:

Agent: NSPE Board of Ethical Review (BER)
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Reporting Deliberation
    Engineer A considers whether the practice is unethical and whether he must report to both jurisdictions
  2. Board Determination (State Q)
    BER determines the presentation does not rise to misrepresentation under State Q's general rule
  3. Board Determination (State Z)
    BER determines the presentation constituted misconduct under State Z's specific rule
  4. Reporting Obligation Confirmation
    BER concludes no obligation to report in State Q but a clear obligation to report in State Z
Field classification (triples vs literals)
Relations (structural triples)
  • cause: Board Determination
  • effect: Reporting Obligation Confirmation
  • responsibleAgent: NSPE Board of Ethical Review (BER)
Literal extractions (kept for synthesis)
  • causalLanguage content: The BER concludes that it would not riseto misrepresentation, and that Engineer A did not have an obligation to report to the engineering licensing board in State Q.
  • necessaryFactors content: BER's assessment that the presentation did not rise to misrepresentation under State Q's general rule; BER's finding that the presentation failed State Z's specific rule; The divergent texts of the two states' rules
  • sufficientFactors content: BER's application of each jurisdiction's rule text to the same set of facts
  • counterfactual content: Had State Z's rules been as general as State Q's, the BER would likely have found no reporting obligation in either state; had State Q's rules been as specific as State Z's, reporting would have been required in both
  • agentKnowledge content: Full knowledge of the case facts, the NSPE Code, and both states' rules of professional conduct
  • interveningFactors content: Jurisdictional variation in rules of professional conduct
  • causalSequence content: {'proeth:step': 1, 'proeth:element': 'Reporting Deliberation', 'proeth:description': 'Engineer A considers whether the practice is unethical and whether he must report to both jurisdictions'}; {'proeth:step': 2, 'proeth:element': 'Board Determination (State Q)', 'proeth:description': "BER determines the presentation does not rise to misrepresentation under State Q's general rule"}; {'proeth:step': 3, 'proeth:element': 'Board Determination (State Z)', 'proeth:description': "BER determines the presentation constituted misconduct under State Z's specific rule"}; {'proeth:step': 4, 'proeth:element': 'Reporting Obligation Confirmation', 'proeth:description': 'BER concludes no obligation to report in State Q but a clear obligation to report in State Z'}
  • responsibilityType assessment: direct
  • withinAgentControl assessment: True
RDF JSON-LD 
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/ontology/case/19#",
    "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/19#CausalChain_8",
  "@type": "proeth:CausalChain",
  "generatedAtTime": "2026-07-14T22:01:19.244951+00:00",
  "proeth:agentKnowledge": "Full knowledge of the case facts, the NSPE Code, and both states\u0027 rules of professional conduct",
  "proeth:causalLanguage": "The BER concludes that it would not riseto misrepresentation, and that Engineer A did not have an obligation to report to the engineering licensing board in State Q.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A considers whether the practice is unethical and whether he must report to both jurisdictions",
      "proeth:element": "Reporting Deliberation",
      "proeth:step": 1
    },
    {
      "proeth:description": "BER determines the presentation does not rise to misrepresentation under State Q\u0027s general rule",
      "proeth:element": "Board Determination (State Q)",
      "proeth:step": 2
    },
    {
      "proeth:description": "BER determines the presentation constituted misconduct under State Z\u0027s specific rule",
      "proeth:element": "Board Determination (State Z)",
      "proeth:step": 3
    },
    {
      "proeth:description": "BER concludes no obligation to report in State Q but a clear obligation to report in State Z",
      "proeth:element": "Reporting Obligation Confirmation",
      "proeth:step": 4
    }
  ],
  "proeth:cause": "Board Determination",
  "proeth:counterfactual": "Had State Z\u0027s rules been as general as State Q\u0027s, the BER would likely have found no reporting obligation in either state; had State Q\u0027s rules been as specific as State Z\u0027s, reporting would have been required in both",
  "proeth:discoveredInSection": "discussion",
  "proeth:effect": "Reporting Obligation Confirmation",
  "proeth:interveningFactors": [
    "Jurisdictional variation in rules of professional conduct"
  ],
  "proeth:necessaryFactors": [
    "BER\u0027s assessment that the presentation did not rise to misrepresentation under State Q\u0027s general rule",
    "BER\u0027s finding that the presentation failed State Z\u0027s specific rule",
    "The divergent texts of the two states\u0027 rules"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "NSPE Board of Ethical Review (BER)",
  "proeth:sufficientFactors": [
    "BER\u0027s application of each jurisdiction\u0027s rule text to the same set of facts"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (10)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
Engineer B's employment at previous firm before
Entity1 is before Entity2 		Engineer B's hiring by XYZ Engineers time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		XYZ Engineers, hired a new project manager, Engineer B, with extensive experience in responsible cha... [more]
Engineer B's completion of non-proprietary projects during
Entity1 occurs entirely within the duration of Entity2 		Engineer B's employment at previous firm time:intervalDuring
http://www.w3.org/2006/time#intervalDuring 		Engineer B's projects completed while in previous employment did not involve proprietary design conc... [more]
Engineer B's hiring by XYZ Engineers before
Entity1 is before Entity2 		XYZ's marketing of bridge and culvert designs in States Q and Z time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		XYZ Engineers, hired a new project manager, Engineer B... and began to market bridge and culvert des... [more]
XYZ's qualification statement/proposal practice during
Entity1 occurs entirely within the duration of Entity2 		XYZ's marketing of designs in both states time:intervalDuring
http://www.w3.org/2006/time#intervalDuring 		XYZ Engineers' qualifications statements accompanying their project proposals clearly indicate their... [more]
XYZ's proposal/marketing practice before
Entity1 is before Entity2 		Engineer A's questioning of the practice's ethics time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer A questions whether this proposal/marketing practice is misleading to clients and unethical
Engineer A's questioning of the practice before
Entity1 is before Entity2 		Engineer A's review of the NSPE Code of Ethics and both states' licensing rules time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer A questions whether this proposal/marketing practice is misleading... Engineer A decides to... [more]
Engineer A's review of the licensing rules before
Entity1 is before Entity2 		Engineer A's deliberation on ethics and reporting obligations time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		Engineer Q finds that the Rules in State Z... are much more specific... Engineer Q considers whether... [more]
Engineer A's deliberation on reporting obligations before
Entity1 is before Entity2 		BER analysis and conclusions time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		The BER subsequently analyzed the case, concluding no reporting obligation exists in State Q but tha... [more]
Engineer B's role as project manager at XYZ overlaps
Entity1 starts before Entity2 and ends during Entity2 		Engineer A's employment at ABC Consultants time:intervalOverlaps
http://www.w3.org/2006/time#intervalOverlaps 		Engineer A works in a metropolitan area bordering on two states, and designs bridges and culverts as... [more]
development of State Z's licensing rules (long legislative history) before
Entity1 is before Entity2 		Engineer A's review of the rules time:intervalBefore
http://www.w3.org/2006/time#intervalBefore 		the Rules in State Z, which have a long and unique legislative history, are much more specific
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.

Back to Extraction Continue to Step 4

© Licensed under the GNU GPL v3