28 entities 5 actions 5 events 5 causal chains 12 temporal relations
Timeline Overview
Action Event 10 sequenced markers
Engineer B Files FOIA Request Pre-interview phase, after Engineer A's submission but before interviews commence
BER Case 93-3: Engineer B Reviews Design Information Within the week following retention by franchiser, before Engineer A's contract expired
BER Case 93-3: Engineer B Discloses Relationship to Engineer A Following completion of design review, several weeks before Engineer A's contract expired
State Provides FOIA Documents After Engineer B files FOIA request; before interview process concludes
Engineer A Submits RFQ Qualifications Initial submission phase, prior to interview process
Engineer B Submits Own Qualifications After receiving FOIA disclosure of Engineer A's qualifications, prior to or during the interview process
Competitive Information Asymmetry Created Immediately following state's release of documents; during ongoing interview process
Interview Process Ongoing During Disclosure Concurrent with FOIA filing and disclosure; prior to Engineer B's submission
BER 93-3 Precedent Established Prior to present case; referenced in Discussion section as established precedent
Engineer A's Qualifications Exposed to Competitor Upon state's release of documents to Engineer B; persists through remainder of procurement
OWL-Time Temporal Structure 12 relations time: = w3.org/2006/time
Engineer B's notification to Engineer A time:before Engineer A's contract expiration with franchiser
BER Case No. 93-3 events time:before present case events
Engineer A's contract expiration with franchiser time:intervalMeets franchiser's formal retention of Engineer B as design engineer
Engineer A's qualifications submission to state agency time:before Engineer B's FOIA request
Engineer B's FOIA request time:before interview process conclusion
state's provision of Engineer A's qualifications to Engineer B time:before Engineer B's own qualifications submission
Engineer B's FOIA request time:before Engineer B's own qualifications submission
Engineer A's multi-year service to franchiser time:before franchiser's termination notice to Engineer A
franchiser's discussions with Engineer B time:intervalDuring Engineer A's active contract period
franchiser's retention of Engineer B for preliminary review time:before Engineer A's contract expiration
franchiser's instruction to Engineer B not to disclose their relationship time:before Engineer B's design review
Engineer B's design review time:before Engineer B's notification to Engineer A
Extracted Actions (5)
Volitional professional decisions with intentions and ethical context

Description: Engineer A voluntarily responds to a public Request for Qualifications by submitting his firm's engineering qualifications to a state agency through the public procurement process. This initiates his firm's participation in the competitive selection process.

Temporal Marker: Initial submission phase, prior to interview process

Mental State: deliberate

Intended Outcome: Secure selection for the public engineering project by demonstrating firm qualifications through the established procurement process

Fulfills Obligations:
  • Participation in open and competitive public procurement process
  • Honest and accurate representation of firm qualifications to a public agency
  • Compliance with state public procurement procedures
Guided By Principles:
  • Free and open competition
  • Honest representation to clients and public bodies
  • Public interest in obtaining most qualified engineering services
Required Capabilities:
Knowledge of public procurement procedures Ability to document and present firm qualifications Understanding of FOIA implications for public agency submissions
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A seeks to grow his firm by competing for a publicly advertised government contract through legitimate procurement channels, demonstrating professional competence and pursuing business development opportunities.

Ethical Tension: Transparency vs. competitive vulnerability: By participating in a public procurement process, Engineer A must disclose proprietary details about his firm's qualifications, methodologies, and capabilities — information that becomes a public record and potentially accessible to competitors.

Learning Significance: Illustrates the inherent tension between open government procurement requirements and the competitive interests of private engineering firms; raises awareness that public submissions carry disclosure risks engineers must anticipate.

Stakes: Engineer A's proprietary qualifications, competitive positioning, potential contract award, and firm revenue are all exposed the moment he participates in a public process. His firm's intellectual capital becomes part of the public record.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Decline to submit qualifications due to FOIA exposure risk
  • Submit qualifications with a formal request that sensitive proprietary information be designated confidential or exempt from FOIA
  • Submit minimal qualifications that satisfy requirements without revealing competitive methodology or trade-sensitive details

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Action_Engineer_A_Submits_RFQ_Qualifications",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline to submit qualifications due to FOIA exposure risk",
    "Submit qualifications with a formal request that sensitive proprietary information be designated confidential or exempt from FOIA",
    "Submit minimal qualifications that satisfy requirements without revealing competitive methodology or trade-sensitive details"
  ],
  "proeth-scenario:characterMotivation": "Engineer A seeks to grow his firm by competing for a publicly advertised government contract through legitimate procurement channels, demonstrating professional competence and pursuing business development opportunities.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining eliminates FOIA risk but forfeits the contract opportunity entirely, potentially harming firm growth and signaling risk-aversion to the market",
    "Requesting confidential designation may partially protect sensitive data but requires legal coordination, may be denied by the agency, and could complicate the submission process",
    "Submitting minimal qualifications reduces exposure but may weaken the firm\u0027s competitive standing and reduce the likelihood of advancing to the interview stage"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the inherent tension between open government procurement requirements and the competitive interests of private engineering firms; raises awareness that public submissions carry disclosure risks engineers must anticipate.",
  "proeth-scenario:ethicalTension": "Transparency vs. competitive vulnerability: By participating in a public procurement process, Engineer A must disclose proprietary details about his firm\u0027s qualifications, methodologies, and capabilities \u2014 information that becomes a public record and potentially accessible to competitors.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Engineer A\u0027s proprietary qualifications, competitive positioning, potential contract award, and firm revenue are all exposed the moment he participates in a public process. His firm\u0027s intellectual capital becomes part of the public record.",
  "proeth:description": "Engineer A voluntarily responds to a public Request for Qualifications by submitting his firm\u0027s engineering qualifications to a state agency through the public procurement process. This initiates his firm\u0027s participation in the competitive selection process.",
  "proeth:foreseenUnintendedEffects": [
    "Submitted qualifications become part of a public agency record potentially subject to FOIA disclosure",
    "Proprietary or strategic information included in submission may become accessible to competitors"
  ],
  "proeth:fulfillsObligation": [
    "Participation in open and competitive public procurement process",
    "Honest and accurate representation of firm qualifications to a public agency",
    "Compliance with state public procurement procedures"
  ],
  "proeth:guidedByPrinciple": [
    "Free and open competition",
    "Honest representation to clients and public bodies",
    "Public interest in obtaining most qualified engineering services"
  ],
  "proeth:hasAgent": "Engineer A (competing engineering firm principal/representative)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Competitive completeness vs. protection of proprietary information",
    "proeth:resolutionReasoning": "Engineer A proceeded with submission under standard procurement norms, apparently without restricting proprietary content, prioritizing competitive thoroughness over information protection"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure selection for the public engineering project by demonstrating firm qualifications through the established procurement process",
  "proeth:requiresCapability": [
    "Knowledge of public procurement procedures",
    "Ability to document and present firm qualifications",
    "Understanding of FOIA implications for public agency submissions"
  ],
  "proeth:temporalMarker": "Initial submission phase, prior to interview process",
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Submits RFQ Qualifications"
}

Description: Prior to the interview phase of the procurement process, Engineer B deliberately files a state Freedom of Information Act request to obtain a copy of competitor Engineer A's submitted qualifications. This action is legally permissible but strategically timed to gain competitive advantage before submitting his own qualifications.

Temporal Marker: Pre-interview phase, after Engineer A's submission but before interviews commence

Mental State: deliberate and calculated

Intended Outcome: Obtain competitor Engineer A's qualifications submission to inform and potentially strengthen Engineer B's own forthcoming submission for the same project

Fulfills Obligations:
  • Compliance with the letter of state FOIA law
  • Participation within the legal framework of public procurement
Guided By Principles:
  • Free and open competition
  • Fair dealing
  • Public interest in procurement transparency
  • Professional integrity and collegiality
Required Capabilities:
Knowledge of state FOIA procedures Understanding of public procurement processes Strategic assessment of competitive positioning
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer B seeks a strategic competitive advantage by accessing a rival's submission before finalizing his own, allowing him to benchmark, differentiate, or tailor his qualifications in response to what Engineer A has already presented to the agency.

Ethical Tension: Legal permissibility vs. professional ethics: While FOIA access is a legally protected right, using it to gain competitive intelligence against a peer engineer during an active procurement process conflicts with NSPE Canon principles of fair competition, professional collegiality, and the spirit of honest rivalry. The law permits the action; professional ethics call it into serious question.

Learning Significance: A pivotal teaching moment distinguishing legal conduct from ethical conduct — the core lesson that 'it is not illegal' is never sufficient justification for professional behavior. Engineers must evaluate actions against both the law and their ethical obligations to peers and the profession.

Stakes: The integrity of the public procurement process, fairness to Engineer A, Engineer B's professional reputation, public trust in engineering competition, and the broader precedent set for how engineers engage with open-records laws in competitive contexts.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Forego the FOIA request and submit qualifications based solely on Engineer B's own independent assessment of the project requirements
  • File the FOIA request only after submitting his own qualifications, using it for post-competition benchmarking rather than competitive preparation
  • Consult the state agency or legal counsel about whether accessing a competitor's active submission via FOIA is consistent with procurement integrity rules before filing

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Action_Engineer_B_Files_FOIA_Request",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Forego the FOIA request and submit qualifications based solely on Engineer B\u0027s own independent assessment of the project requirements",
    "File the FOIA request only after submitting his own qualifications, using it for post-competition benchmarking rather than competitive preparation",
    "Consult the state agency or legal counsel about whether accessing a competitor\u0027s active submission via FOIA is consistent with procurement integrity rules before filing"
  ],
  "proeth-scenario:characterMotivation": "Engineer B seeks a strategic competitive advantage by accessing a rival\u0027s submission before finalizing his own, allowing him to benchmark, differentiate, or tailor his qualifications in response to what Engineer A has already presented to the agency.",
  "proeth-scenario:consequencesIfAlternative": [
    "Forgoing the FOIA request preserves competitive fairness and Engineer B\u0027s ethical standing, though it forgoes potentially useful intelligence \u2014 this is the ethically sound path",
    "Filing after submission removes the competitive exploitation element and is ethically defensible, though it still raises questions about intent and use of peer information",
    "Consulting the agency or counsel demonstrates ethical diligence; the agency might discourage or restrict the request, and Engineer B gains clarity on boundaries \u2014 modeling the ethical practice of seeking guidance under uncertainty"
  ],
  "proeth-scenario:decisionSignificance": "A pivotal teaching moment distinguishing legal conduct from ethical conduct \u2014 the core lesson that \u0027it is not illegal\u0027 is never sufficient justification for professional behavior. Engineers must evaluate actions against both the law and their ethical obligations to peers and the profession.",
  "proeth-scenario:ethicalTension": "Legal permissibility vs. professional ethics: While FOIA access is a legally protected right, using it to gain competitive intelligence against a peer engineer during an active procurement process conflicts with NSPE Canon principles of fair competition, professional collegiality, and the spirit of honest rivalry. The law permits the action; professional ethics call it into serious question.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The integrity of the public procurement process, fairness to Engineer A, Engineer B\u0027s professional reputation, public trust in engineering competition, and the broader precedent set for how engineers engage with open-records laws in competitive contexts.",
  "proeth:description": "Prior to the interview phase of the procurement process, Engineer B deliberately files a state Freedom of Information Act request to obtain a copy of competitor Engineer A\u0027s submitted qualifications. This action is legally permissible but strategically timed to gain competitive advantage before submitting his own qualifications.",
  "proeth:foreseenUnintendedEffects": [
    "Action may be perceived as ethically questionable despite legal permissibility",
    "Could undermine trust and fair dealing norms within the engineering profession",
    "May disadvantage Engineer A by exposing strategic positioning before the competitive process concludes"
  ],
  "proeth:fulfillsObligation": [
    "Compliance with the letter of state FOIA law",
    "Participation within the legal framework of public procurement"
  ],
  "proeth:guidedByPrinciple": [
    "Free and open competition",
    "Fair dealing",
    "Public interest in procurement transparency",
    "Professional integrity and collegiality"
  ],
  "proeth:hasAgent": "Engineer B (competing engineering firm principal/representative)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Legal competitive advantage vs. ethical fair dealing with a professional competitor",
    "proeth:resolutionReasoning": "Engineer B resolved the conflict in favor of competitive self-interest, relying on legal permissibility as justification, though the Board noted concern about the timing of the request as ethically troubling even if not clearly prohibited"
  },
  "proeth:hasMentalState": "deliberate and calculated",
  "proeth:intendedOutcome": "Obtain competitor Engineer A\u0027s qualifications submission to inform and potentially strengthen Engineer B\u0027s own forthcoming submission for the same project",
  "proeth:requiresCapability": [
    "Knowledge of state FOIA procedures",
    "Understanding of public procurement processes",
    "Strategic assessment of competitive positioning"
  ],
  "proeth:temporalMarker": "Pre-interview phase, after Engineer A\u0027s submission but before interviews commence",
  "proeth:violatesObligation": [
    "Fair dealing with a professional competitor",
    "Spirit of open and honest competition without exploitation of procedural mechanisms for strategic gain",
    "Duty to avoid actions that undermine colleagues\u0027 legitimate competitive interests",
    "Implicit professional norms against using legal mechanisms opportunistically to disadvantage competitors in a shared procurement process"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer B Files FOIA Request"
}

Description: After receiving Engineer A's qualifications through the FOIA disclosure, Engineer B proceeds to submit his own firm's engineering qualifications to the state agency for the same public project. This submission is informed by prior access to a competitor's submission.

Temporal Marker: After receiving FOIA disclosure of Engineer A's qualifications, prior to or during the interview process

Mental State: deliberate

Intended Outcome: Secure selection for the public engineering project, with submission potentially tailored or strengthened based on knowledge of Engineer A's qualifications

Fulfills Obligations:
  • Compliance with state public procurement submission requirements
  • Honest representation of own firm's qualifications
  • Participation in legally sanctioned competitive process
Guided By Principles:
  • Free and open competition
  • Honest representation to public agencies
  • Fair dealing
  • Public interest in obtaining most qualified engineering firm
Required Capabilities:
Ability to prepare and present firm qualifications Knowledge of public procurement submission requirements Strategic use of available competitive information
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer B proceeds with his own submission, now informed by direct knowledge of his competitor's approach, qualifications structure, and presented strengths — effectively competing on an uneven informational playing field of his own creation.

Ethical Tension: Self-interest and business success vs. fair competition and professional integrity: Engineer B has a legitimate right to pursue the contract, but doing so with insider knowledge of a competitor's submission undermines the foundational fairness that public procurement processes are designed to ensure. The tension is between winning and winning honorably.

Learning Significance: Demonstrates that a chain of individually rationalized actions can compound into a serious ethical violation. Each step seemed defensible in isolation; together they constitute a pattern of deliberate competitive manipulation that violates the spirit of professional engineering ethics and public trust.

Stakes: The contract award outcome, Engineer A's business interests, the integrity of the state procurement process, public confidence in engineering competition, and Engineer B's long-term professional reputation and potential disciplinary exposure before an ethics board.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Withdraw from the competition after recognizing that the FOIA-informed advantage compromises the fairness of his participation
  • Disclose to the state agency that he obtained Engineer A's qualifications via FOIA prior to submission, allowing the agency to determine whether his participation remains appropriate
  • Submit qualifications but voluntarily recuse himself from any evaluation stage where the agency might compare submissions, flagging the informational asymmetry

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Action_Engineer_B_Submits_Own_Qualifications",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Withdraw from the competition after recognizing that the FOIA-informed advantage compromises the fairness of his participation",
    "Disclose to the state agency that he obtained Engineer A\u0027s qualifications via FOIA prior to submission, allowing the agency to determine whether his participation remains appropriate",
    "Submit qualifications but voluntarily recuse himself from any evaluation stage where the agency might compare submissions, flagging the informational asymmetry"
  ],
  "proeth-scenario:characterMotivation": "Engineer B proceeds with his own submission, now informed by direct knowledge of his competitor\u0027s approach, qualifications structure, and presented strengths \u2014 effectively competing on an uneven informational playing field of his own creation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Withdrawing sacrifices the contract but preserves ethical integrity and professional standing \u2014 a costly but honorable choice that would likely be viewed favorably by an ethics board",
    "Disclosing to the agency demonstrates transparency and ethical accountability; the agency may disqualify Engineer B or take corrective action, but Engineer B avoids concealment and models responsible self-reporting",
    "Recusal is a partial remedy that may be impractical in practice but signals awareness of the ethical problem \u2014 likely insufficient to fully remediate the unfair advantage already gained"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that a chain of individually rationalized actions can compound into a serious ethical violation. Each step seemed defensible in isolation; together they constitute a pattern of deliberate competitive manipulation that violates the spirit of professional engineering ethics and public trust.",
  "proeth-scenario:ethicalTension": "Self-interest and business success vs. fair competition and professional integrity: Engineer B has a legitimate right to pursue the contract, but doing so with insider knowledge of a competitor\u0027s submission undermines the foundational fairness that public procurement processes are designed to ensure. The tension is between winning and winning honorably.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "The contract award outcome, Engineer A\u0027s business interests, the integrity of the state procurement process, public confidence in engineering competition, and Engineer B\u0027s long-term professional reputation and potential disciplinary exposure before an ethics board.",
  "proeth:description": "After receiving Engineer A\u0027s qualifications through the FOIA disclosure, Engineer B proceeds to submit his own firm\u0027s engineering qualifications to the state agency for the same public project. This submission is informed by prior access to a competitor\u0027s submission.",
  "proeth:foreseenUnintendedEffects": [
    "Submission may be perceived as benefiting unfairly from prior access to competitor\u0027s materials",
    "Could raise questions about integrity of the competitive process",
    "May disadvantage Engineer A if Engineer B\u0027s submission directly addresses or counters Engineer A\u0027s stated qualifications"
  ],
  "proeth:fulfillsObligation": [
    "Compliance with state public procurement submission requirements",
    "Honest representation of own firm\u0027s qualifications",
    "Participation in legally sanctioned competitive process"
  ],
  "proeth:guidedByPrinciple": [
    "Free and open competition",
    "Honest representation to public agencies",
    "Fair dealing",
    "Public interest in obtaining most qualified engineering firm"
  ],
  "proeth:hasAgent": "Engineer B (competing engineering firm principal/representative)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Competitive self-interest and legal compliance vs. fair and equitable competition",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of proceeding with submission, relying on the legal legitimacy of the FOIA process and the public nature of the disclosed information, though the Board\u0027s concern about timing implies this resolution is ethically questionable"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure selection for the public engineering project, with submission potentially tailored or strengthened based on knowledge of Engineer A\u0027s qualifications",
  "proeth:requiresCapability": [
    "Ability to prepare and present firm qualifications",
    "Knowledge of public procurement submission requirements",
    "Strategic use of available competitive information"
  ],
  "proeth:temporalMarker": "After receiving FOIA disclosure of Engineer A\u0027s qualifications, prior to or during the interview process",
  "proeth:violatesObligation": [
    "Fair dealing with professional competitor",
    "Avoiding use of improperly or opportunistically obtained competitive intelligence to gain advantage",
    "Spirit of equitable competition in public procurement"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer B Submits Own Qualifications"
}

Description: In the referenced BER Case No. 93-3, Engineer B agrees to review Engineer A's design information on behalf of the franchiser client, despite being explicitly instructed by the franchiser not to disclose their new relationship to Engineer A. Engineer B proceeds with the review within a week of being retained.

Temporal Marker: Within the week following retention by franchiser, before Engineer A's contract expired

Mental State: deliberate

Intended Outcome: Fulfill client obligation by reviewing pending design concerns for the franchiser, supporting continuity of engineering services during the transition from Engineer A

Fulfills Obligations:
  • Compliance with client instruction to maintain confidentiality of new relationship
  • Responsiveness to client's request for design review services
Guided By Principles:
  • Faithful agent and trustee relationship to client
  • Fair dealing with professional colleagues
  • Avoidance of conflicts of interest
  • Loyalty to client within ethical bounds
Required Capabilities:
Engineering design review competence Ability to assess pending design concerns across multiple franchise facilities Judgment regarding conflicts of interest in client transitions
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer B accepts a new client engagement and acts promptly to fulfill his professional obligations to that client — the franchiser — by reviewing the existing design work. His motivation is to serve his new client efficiently and establish his value in the new relationship.

Ethical Tension: Duty to new client vs. duty of fairness to Engineer A: Engineer B owes loyalty and diligence to the franchiser as his client, but the instruction to conceal the new relationship from Engineer A places him in a position where serving one party requires deceiving another engineer — a peer whose professional interests are directly affected. Confidentiality obligations to clients can conflict with transparency obligations to colleagues.

Learning Significance: Illustrates the complexity of client loyalty when client instructions require conduct that harms a third-party engineer. Teaches that client directives do not override all ethical obligations, and that engineers must evaluate whether following client instructions crosses ethical lines — particularly when those instructions involve concealment or deception of peers.

Stakes: Engineer A's professional interests and business relationship with the franchiser, Engineer B's ethical integrity, the quality and fairness of the design review, and the precedent set for how engineers handle transitions between competing client relationships.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Decline the engagement unless the franchiser permits transparent communication with Engineer A about the new relationship
  • Accept the engagement but immediately notify Engineer A of the relationship change before conducting any review, regardless of client instruction
  • Accept the engagement and the confidentiality instruction, but limit the scope of the review to avoid directly exploiting Engineer A's proprietary design work

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Action_BER_Case_93-3__Engineer_B_Reviews_Design_Informati",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the engagement unless the franchiser permits transparent communication with Engineer A about the new relationship",
    "Accept the engagement but immediately notify Engineer A of the relationship change before conducting any review, regardless of client instruction",
    "Accept the engagement and the confidentiality instruction, but limit the scope of the review to avoid directly exploiting Engineer A\u0027s proprietary design work"
  ],
  "proeth-scenario:characterMotivation": "Engineer B accepts a new client engagement and acts promptly to fulfill his professional obligations to that client \u2014 the franchiser \u2014 by reviewing the existing design work. His motivation is to serve his new client efficiently and establish his value in the new relationship.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining the engagement on ethical grounds protects Engineer A and Engineer B\u0027s integrity but forfeits a business opportunity \u2014 the ethically cleanest path, though commercially costly",
    "Notifying Engineer A immediately defies the client\u0027s instruction but upholds peer transparency; the franchiser may terminate the relationship, but Engineer B avoids complicity in deception \u2014 this is what Engineer B ultimately did, per Action 5",
    "Limiting scope is a compromise that partially reduces harm but does not resolve the fundamental deception problem; it may satisfy neither the client nor ethical standards fully"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the complexity of client loyalty when client instructions require conduct that harms a third-party engineer. Teaches that client directives do not override all ethical obligations, and that engineers must evaluate whether following client instructions crosses ethical lines \u2014 particularly when those instructions involve concealment or deception of peers.",
  "proeth-scenario:ethicalTension": "Duty to new client vs. duty of fairness to Engineer A: Engineer B owes loyalty and diligence to the franchiser as his client, but the instruction to conceal the new relationship from Engineer A places him in a position where serving one party requires deceiving another engineer \u2014 a peer whose professional interests are directly affected. Confidentiality obligations to clients can conflict with transparency obligations to colleagues.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Engineer A\u0027s professional interests and business relationship with the franchiser, Engineer B\u0027s ethical integrity, the quality and fairness of the design review, and the precedent set for how engineers handle transitions between competing client relationships.",
  "proeth:description": "In the referenced BER Case No. 93-3, Engineer B agrees to review Engineer A\u0027s design information on behalf of the franchiser client, despite being explicitly instructed by the franchiser not to disclose their new relationship to Engineer A. Engineer B proceeds with the review within a week of being retained.",
  "proeth:foreseenUnintendedEffects": [
    "Review of Engineer A\u0027s design work while Engineer A remains under contract creates potential conflict",
    "Access to Engineer A\u0027s proprietary design information without Engineer A\u0027s knowledge or consent",
    "Risk of undermining Engineer A\u0027s professional interests and client relationship"
  ],
  "proeth:fulfillsObligation": [
    "Compliance with client instruction to maintain confidentiality of new relationship",
    "Responsiveness to client\u0027s request for design review services"
  ],
  "proeth:guidedByPrinciple": [
    "Faithful agent and trustee relationship to client",
    "Fair dealing with professional colleagues",
    "Avoidance of conflicts of interest",
    "Loyalty to client within ethical bounds"
  ],
  "proeth:hasAgent": "Engineer B (design engineer, newly retained by franchiser; BER Case No. 93-3)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client loyalty and service vs. fair dealing with professional colleague",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of client service and compliance with client instructions, proceeding with the review; the Board\u0027s analysis implies this resolution was ethically problematic given the circumstances of the engagement"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Fulfill client obligation by reviewing pending design concerns for the franchiser, supporting continuity of engineering services during the transition from Engineer A",
  "proeth:requiresCapability": [
    "Engineering design review competence",
    "Ability to assess pending design concerns across multiple franchise facilities",
    "Judgment regarding conflicts of interest in client transitions"
  ],
  "proeth:temporalMarker": "Within the week following retention by franchiser, before Engineer A\u0027s contract expired",
  "proeth:violatesObligation": [
    "Duty to avoid conflicts of interest with another engineer\u0027s ongoing engagement",
    "Obligation not to review or exploit a colleague\u0027s work product without appropriate disclosure",
    "Fair dealing toward Engineer A as a professional colleague",
    "Implicit obligation to consider whether accepting the engagement under these conditions was itself ethically appropriate"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "BER Case 93-3: Engineer B Reviews Design Information"
}

Description: In BER Case No. 93-3, Engineer B voluntarily notifies Engineer A of his new relationship with the franchiser and shares preliminary results of his design review, in direct contravention of the franchiser's explicit instruction not to disclose the relationship. The Board determined this disclosure constituted a neglect of client interests.

Temporal Marker: Following completion of design review, several weeks before Engineer A's contract expired

Mental State: deliberate

Intended Outcome: Inform Engineer A of the transition and preliminary review findings, likely motivated by professional courtesy, transparency, or personal discomfort with the concealment rather than personal competitive advantage

Fulfills Obligations:
  • Transparency and honesty toward a professional colleague
  • Professional courtesy to Engineer A as the incumbent engineer
Guided By Principles:
  • Faithful agent and trustee relationship to client
  • Loyalty and fair dealing toward client
  • Honesty and transparency as professional values
  • Duty of loyalty does not extend to unethical acts but confidentiality instruction was not itself unethical
Required Capabilities:
Judgment regarding confidentiality obligations in client transitions Understanding of faithful agent and trustee duties Ability to navigate competing professional obligations
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer B chooses to prioritize his ethical obligation of transparency toward a fellow engineer over strict compliance with his client's confidentiality instruction, believing that honesty with Engineer A is the right course of action despite the client's explicit directive to the contrary.

Ethical Tension: Loyalty to client vs. fairness and transparency toward a peer engineer: This is a direct, unambiguous conflict between two professional obligations. The client has issued a clear instruction; the NSPE Code emphasizes fair dealing with other engineers. Engineer B must choose which duty takes precedence — and the Board found that in this instance, the client's interests should have prevailed, making this a case where Engineer B's moral intuition led to a technically improper outcome under the ethics framework applied.

Learning Significance: A sophisticated and counterintuitive teaching moment: Engineer B's action appears virtuous on its surface (honesty, transparency) but was found by the Board to constitute neglect of client interests. This challenges students to grapple with the limits of personal moral judgment when professional duties to clients are clear, and raises deep questions about when — if ever — an engineer may override client confidentiality on ethical grounds.

Stakes: The franchiser's business interests and confidentiality expectations, Engineer A's awareness of his professional situation, Engineer B's standing with his new client, the Board's evaluation of ethical compliance, and the broader question of how engineers navigate irreconcilable conflicts between client loyalty and peer fairness.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Comply with the client's instruction, maintain confidentiality about the new relationship, and complete the design review without notifying Engineer A
  • Refuse to conduct the design review at all unless the franchiser agrees to notify Engineer A, effectively making transparency a condition of the engagement
  • Seek guidance from an ethics board or legal counsel before deciding whether to follow or override the client's confidentiality instruction

Narrative Role: resolution

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Action_BER_Case_93-3__Engineer_B_Discloses_Relationship_t",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Comply with the client\u0027s instruction, maintain confidentiality about the new relationship, and complete the design review without notifying Engineer A",
    "Refuse to conduct the design review at all unless the franchiser agrees to notify Engineer A, effectively making transparency a condition of the engagement",
    "Seek guidance from an ethics board or legal counsel before deciding whether to follow or override the client\u0027s confidentiality instruction"
  ],
  "proeth-scenario:characterMotivation": "Engineer B chooses to prioritize his ethical obligation of transparency toward a fellow engineer over strict compliance with his client\u0027s confidentiality instruction, believing that honesty with Engineer A is the right course of action despite the client\u0027s explicit directive to the contrary.",
  "proeth-scenario:consequencesIfAlternative": [
    "Complying with the client\u0027s instruction fulfills the contractual and fiduciary duty to the franchiser and avoids the Board\u0027s finding of client neglect \u2014 but leaves Engineer B complicit in a deception that harms Engineer A and may still raise independent ethical concerns about the franchiser\u0027s conduct",
    "Conditioning the engagement on transparency is the most ethically coherent path: it respects both peer fairness and client autonomy by giving the franchiser the choice, rather than unilaterally overriding their instruction \u2014 this likely represents the optimal ethical resolution",
    "Seeking ethics guidance before acting models best practices for navigating genuinely ambiguous conflicts; it may delay the review but demonstrates the professional diligence expected of engineers facing irreconcilable duties"
  ],
  "proeth-scenario:decisionSignificance": "A sophisticated and counterintuitive teaching moment: Engineer B\u0027s action appears virtuous on its surface (honesty, transparency) but was found by the Board to constitute neglect of client interests. This challenges students to grapple with the limits of personal moral judgment when professional duties to clients are clear, and raises deep questions about when \u2014 if ever \u2014 an engineer may override client confidentiality on ethical grounds.",
  "proeth-scenario:ethicalTension": "Loyalty to client vs. fairness and transparency toward a peer engineer: This is a direct, unambiguous conflict between two professional obligations. The client has issued a clear instruction; the NSPE Code emphasizes fair dealing with other engineers. Engineer B must choose which duty takes precedence \u2014 and the Board found that in this instance, the client\u0027s interests should have prevailed, making this a case where Engineer B\u0027s moral intuition led to a technically improper outcome under the ethics framework applied.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "resolution",
  "proeth-scenario:stakes": "The franchiser\u0027s business interests and confidentiality expectations, Engineer A\u0027s awareness of his professional situation, Engineer B\u0027s standing with his new client, the Board\u0027s evaluation of ethical compliance, and the broader question of how engineers navigate irreconcilable conflicts between client loyalty and peer fairness.",
  "proeth:description": "In BER Case No. 93-3, Engineer B voluntarily notifies Engineer A of his new relationship with the franchiser and shares preliminary results of his design review, in direct contravention of the franchiser\u0027s explicit instruction not to disclose the relationship. The Board determined this disclosure constituted a neglect of client interests.",
  "proeth:foreseenUnintendedEffects": [
    "Direct violation of explicit client instruction to maintain confidentiality of the new relationship",
    "Potential harm to franchiser\u0027s interests by premature disclosure of the transition",
    "Disruption to franchiser\u0027s planned timeline for transitioning engineering services"
  ],
  "proeth:fulfillsObligation": [
    "Transparency and honesty toward a professional colleague",
    "Professional courtesy to Engineer A as the incumbent engineer"
  ],
  "proeth:guidedByPrinciple": [
    "Faithful agent and trustee relationship to client",
    "Loyalty and fair dealing toward client",
    "Honesty and transparency as professional values",
    "Duty of loyalty does not extend to unethical acts but confidentiality instruction was not itself unethical"
  ],
  "proeth:hasAgent": "Engineer B (design engineer retained by franchiser; BER Case No. 93-3)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Client confidentiality and loyalty vs. professional transparency toward a colleague",
    "proeth:resolutionReasoning": "Engineer B resolved in favor of transparency toward Engineer A, but the Board determined this was ethically incorrect\u2014the duty of loyalty to the client as faithful agent and trustee required maintaining confidentiality, and the benefits of disclosure did not outweigh the detriments to the client"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Inform Engineer A of the transition and preliminary review findings, likely motivated by professional courtesy, transparency, or personal discomfort with the concealment rather than personal competitive advantage",
  "proeth:requiresCapability": [
    "Judgment regarding confidentiality obligations in client transitions",
    "Understanding of faithful agent and trustee duties",
    "Ability to navigate competing professional obligations"
  ],
  "proeth:temporalMarker": "Following completion of design review, several weeks before Engineer A\u0027s contract expired",
  "proeth:violatesObligation": [
    "Duty of loyalty to client as faithful agent and trustee",
    "Obligation to follow lawful client instructions regarding confidentiality",
    "Duty to protect client\u0027s legitimate business interests",
    "Obligation not to neglect client interests for the benefit of third parties"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "BER Case 93-3: Engineer B Discloses Relationship to Engineer A"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changes

Description: The state agency releases Engineer A's submitted qualifications to Engineer B in response to the FOIA request, making confidential competitive information publicly disclosed. This is an automatic legal outcome triggered by the FOIA filing and applicable public records law.

Temporal Marker: After Engineer B files FOIA request; before interview process concludes

Activates Constraints:
  • Fair_Competition_Constraint
  • Professional_Integrity_Constraint
  • Confidentiality_Of_Competitive_Information_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A experiences betrayal and vulnerability upon learning a competitor accessed their proprietary submission; Engineer B may feel legally vindicated but potentially uneasy about ethical optics; state agency staff may feel conflicted between legal duty and fairness instincts; observers in the engineering community feel concern about the integrity of public procurement processes

Stakeholder Consequences:
  • engineer_a: Competitive disadvantage created; proprietary methodology, pricing signals, and strategic qualifications exposed to direct competitor before selection concludes; trust in public procurement process eroded
  • engineer_b: Gains informational advantage that may shape or strengthen subsequent submission; legal compliance does not shield from ethical scrutiny; professional reputation at risk if conduct becomes known in engineering community
  • state_agency: Caught between legal obligation and procurement fairness; disclosure may undermine integrity of the RFQ process and deter future competitors from submitting qualifications
  • engineering_profession: Public confidence in fair competition among engineers is undermined; sets a troubling precedent for using legal mechanisms to gain unethical competitive edges
  • public_client: Risk of receiving a less-qualified engineer if the selection process is corrupted by information asymmetry; procurement integrity compromised

Learning Moment: Illustrates the critical distinction between legal permissibility and ethical acceptability — an action can be lawful (FOIA compliance is mandatory) while still violating professional ethical norms around fair competition and integrity. Students should recognize that engineers are held to a higher standard than mere legal compliance.

Ethical Implications: Reveals a fundamental tension between transparency principles embedded in public records law and the fairness principles embedded in professional engineering ethics codes. Exposes how legal mechanisms can be weaponized to undermine the spirit of fair competition. Raises questions about whether engineers have a duty to refrain from legal-but-unethical conduct, and whether the engineering profession should advocate for procurement law reforms to protect competitive integrity.

Discussion Prompts:
  • If an action is legally required (state must release documents), does that absolve the party who initiated it (Engineer B) of ethical responsibility for the consequences?
  • Should public procurement law include exemptions for competitive qualifications during active selection processes, and who bears responsibility for advocating such reforms?
  • How does the concept of 'fair competition' in engineering ethics differ from the legal concept of 'public records access,' and when do they conflict?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Event_State_Provides_FOIA_Documents",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "If an action is legally required (state must release documents), does that absolve the party who initiated it (Engineer B) of ethical responsibility for the consequences?",
    "Should public procurement law include exemptions for competitive qualifications during active selection processes, and who bears responsibility for advocating such reforms?",
    "How does the concept of \u0027fair competition\u0027 in engineering ethics differ from the legal concept of \u0027public records access,\u0027 and when do they conflict?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A experiences betrayal and vulnerability upon learning a competitor accessed their proprietary submission; Engineer B may feel legally vindicated but potentially uneasy about ethical optics; state agency staff may feel conflicted between legal duty and fairness instincts; observers in the engineering community feel concern about the integrity of public procurement processes",
  "proeth-scenario:ethicalImplications": "Reveals a fundamental tension between transparency principles embedded in public records law and the fairness principles embedded in professional engineering ethics codes. Exposes how legal mechanisms can be weaponized to undermine the spirit of fair competition. Raises questions about whether engineers have a duty to refrain from legal-but-unethical conduct, and whether the engineering profession should advocate for procurement law reforms to protect competitive integrity.",
  "proeth-scenario:learningMoment": "Illustrates the critical distinction between legal permissibility and ethical acceptability \u2014 an action can be lawful (FOIA compliance is mandatory) while still violating professional ethical norms around fair competition and integrity. Students should recognize that engineers are held to a higher standard than mere legal compliance.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Competitive disadvantage created; proprietary methodology, pricing signals, and strategic qualifications exposed to direct competitor before selection concludes; trust in public procurement process eroded",
    "engineer_b": "Gains informational advantage that may shape or strengthen subsequent submission; legal compliance does not shield from ethical scrutiny; professional reputation at risk if conduct becomes known in engineering community",
    "engineering_profession": "Public confidence in fair competition among engineers is undermined; sets a troubling precedent for using legal mechanisms to gain unethical competitive edges",
    "public_client": "Risk of receiving a less-qualified engineer if the selection process is corrupted by information asymmetry; procurement integrity compromised",
    "state_agency": "Caught between legal obligation and procurement fairness; disclosure may undermine integrity of the RFQ process and deter future competitors from submitting qualifications"
  },
  "proeth:activatesConstraint": [
    "Fair_Competition_Constraint",
    "Professional_Integrity_Constraint",
    "Confidentiality_Of_Competitive_Information_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/141#Action_Engineer_B_Files_FOIA_Request",
  "proeth:causesStateChange": "Engineer A\u0027s qualifications are now in Engineer B\u0027s possession; competitive information asymmetry created; Engineer B has actionable intelligence about Engineer A\u0027s submission prior to interview conclusion",
  "proeth:createsObligation": [
    "Engineer B obligation to refrain from exploiting disclosed information unfairly",
    "State agency obligation to notify Engineer A of disclosure (if applicable under state law)",
    "BER obligation to evaluate whether legal compliance equals ethical compliance"
  ],
  "proeth:description": "The state agency releases Engineer A\u0027s submitted qualifications to Engineer B in response to the FOIA request, making confidential competitive information publicly disclosed. This is an automatic legal outcome triggered by the FOIA filing and applicable public records law.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "After Engineer B files FOIA request; before interview process concludes",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "State Provides FOIA Documents"
}

Description: As a direct outcome of the FOIA disclosure, Engineer B possesses Engineer A's full qualifications while Engineer A has no equivalent knowledge of Engineer B's approach, creating an unequal competitive footing during an active procurement. This asymmetry persists through the remainder of the selection process.

Temporal Marker: Immediately following state's release of documents; during ongoing interview process

Activates Constraints:
  • Fair_Competition_Constraint
  • Professional_Integrity_Constraint
  • Prohibition_On_Competitive_Injury_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A, if aware, experiences a profound sense of unfairness and professional violation; Engineer B may rationalize the advantage as legally obtained; the state agency may feel institutional embarrassment; the engineering community observes a troubling precedent that could chill future participation in public procurements

Stakeholder Consequences:
  • engineer_a: Qualifications strategy, unique methodologies, and competitive positioning are now known to a direct competitor; cannot retroactively protect disclosed information; may withdraw from process or feel compelled to revise approach
  • engineer_b: Holds an informational advantage that may constitute an ethical violation of NSPE Code provisions on fair competition; even if selection is won, legitimacy of the outcome may be questioned
  • state_agency: Procurement integrity is functionally compromised; may face challenges to the selection outcome; may need to revisit records exemption policies for active procurements
  • public: Risk of suboptimal engineering selection if process integrity is undermined; public trust in government procurement eroded
  • engineering_profession: Norm of fair competition is visibly threatened; professional societies may need to issue guidance on FOIA use in competitive contexts

Learning Moment: Demonstrates that competitive harm can arise from a sequence of individually legal steps, and that engineers must evaluate the cumulative ethical effect of their actions, not just each step in isolation. Highlights the NSPE Code's emphasis on fair and open competition as a professional value, not merely a legal requirement.

Ethical Implications: Exposes the gap between legal compliance and ethical conduct in competitive professional practice. Raises questions about the duty to compete fairly as a core professional value. Illustrates how systemic harm to professional norms can result from individually rationalized legal actions, and challenges students to think about engineers' responsibilities to the integrity of institutions and processes, not just to individual clients.

Discussion Prompts:
  • Does Engineer B have an ethical obligation to disclose to the state agency that their submission was informed by FOIA-obtained competitor qualifications?
  • If Engineer B wins the contract, should the selection be invalidated on ethical grounds even if it was legally obtained?
  • How should the engineering profession respond when legal mechanisms are used to undermine professional ethical norms around fair competition?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Event_Competitive_Information_Asymmetry_Created",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Engineer B have an ethical obligation to disclose to the state agency that their submission was informed by FOIA-obtained competitor qualifications?",
    "If Engineer B wins the contract, should the selection be invalidated on ethical grounds even if it was legally obtained?",
    "How should the engineering profession respond when legal mechanisms are used to undermine professional ethical norms around fair competition?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A, if aware, experiences a profound sense of unfairness and professional violation; Engineer B may rationalize the advantage as legally obtained; the state agency may feel institutional embarrassment; the engineering community observes a troubling precedent that could chill future participation in public procurements",
  "proeth-scenario:ethicalImplications": "Exposes the gap between legal compliance and ethical conduct in competitive professional practice. Raises questions about the duty to compete fairly as a core professional value. Illustrates how systemic harm to professional norms can result from individually rationalized legal actions, and challenges students to think about engineers\u0027 responsibilities to the integrity of institutions and processes, not just to individual clients.",
  "proeth-scenario:learningMoment": "Demonstrates that competitive harm can arise from a sequence of individually legal steps, and that engineers must evaluate the cumulative ethical effect of their actions, not just each step in isolation. Highlights the NSPE Code\u0027s emphasis on fair and open competition as a professional value, not merely a legal requirement.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Qualifications strategy, unique methodologies, and competitive positioning are now known to a direct competitor; cannot retroactively protect disclosed information; may withdraw from process or feel compelled to revise approach",
    "engineer_b": "Holds an informational advantage that may constitute an ethical violation of NSPE Code provisions on fair competition; even if selection is won, legitimacy of the outcome may be questioned",
    "engineering_profession": "Norm of fair competition is visibly threatened; professional societies may need to issue guidance on FOIA use in competitive contexts",
    "public": "Risk of suboptimal engineering selection if process integrity is undermined; public trust in government procurement eroded",
    "state_agency": "Procurement integrity is functionally compromised; may face challenges to the selection outcome; may need to revisit records exemption policies for active procurements"
  },
  "proeth:activatesConstraint": [
    "Fair_Competition_Constraint",
    "Professional_Integrity_Constraint",
    "Prohibition_On_Competitive_Injury_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/141#Action_Engineer_B_Files_FOIA_Request",
  "proeth:causesStateChange": "Procurement process is now operating under conditions of information asymmetry; competitive fairness is structurally compromised; Engineer B holds strategic advantage derived from a legal but ethically questionable maneuver",
  "proeth:createsObligation": [
    "Engineer B obligation to disclose use of FOIA-obtained information if it materially shapes submission",
    "State agency obligation to assess whether procurement integrity has been compromised",
    "BER obligation to evaluate whether Engineer B\u0027s conduct constitutes an ethical violation of fair competition norms"
  ],
  "proeth:description": "As a direct outcome of the FOIA disclosure, Engineer B possesses Engineer A\u0027s full qualifications while Engineer A has no equivalent knowledge of Engineer B\u0027s approach, creating an unequal competitive footing during an active procurement. This asymmetry persists through the remainder of the selection process.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Immediately following state\u0027s release of documents; during ongoing interview process",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Competitive Information Asymmetry Created"
}

Description: The state agency's interview process for the RFQ remains active and incomplete at the time Engineer B obtains Engineer A's qualifications, meaning the competitive selection has not yet concluded and Engineer A retains a live stake in the outcome. This temporal overlap is a critical contextual fact that heightens the ethical stakes of the FOIA disclosure.

Temporal Marker: Concurrent with FOIA filing and disclosure; prior to Engineer B's submission

Activates Constraints:
  • Fair_Competition_Constraint
  • Procurement_Integrity_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A is in a vulnerable position — invested in the process, unaware of the informational breach, and unable to protect their interests; state agency staff may feel the tension between legal obligation and process fairness; Engineer B may feel urgency to act before the window closes

Stakeholder Consequences:
  • engineer_a: Active competitive interest is live and exposed; harm from information asymmetry is maximized because the process has not yet concluded
  • engineer_b: The timing of the FOIA request — during rather than after the process — is ethically significant and likely to be the focus of BER scrutiny
  • state_agency: Bears institutional responsibility for the integrity of an active procurement that is now compromised by information asymmetry it was legally required to create
  • public: A government selection process is operating under compromised conditions without public awareness

Learning Moment: Teaches students that timing matters enormously in ethical analysis — the same action (obtaining a competitor's qualifications) carries very different ethical weight depending on whether the competitive process is active or concluded. Engineers must consider not just what they do, but when they do it.

Ethical Implications: Highlights the ethical significance of timing in competitive professional conduct. Reveals institutional design failures where legal transparency obligations conflict with procurement fairness. Raises questions about shared responsibility between individual engineers and institutional actors in maintaining the integrity of professional selection processes.

Discussion Prompts:
  • Would Engineer B's conduct be more or less ethically problematic if the FOIA request had been filed after the contract was awarded rather than during the active interview process?
  • Does the state agency bear any ethical responsibility for the competitive harm created by its legally mandated disclosure during an active procurement?
  • How should procurement processes be designed to prevent the timing of public records requests from undermining competitive fairness?
Tension: medium Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Event_Interview_Process_Ongoing_During_Disclosure",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Would Engineer B\u0027s conduct be more or less ethically problematic if the FOIA request had been filed after the contract was awarded rather than during the active interview process?",
    "Does the state agency bear any ethical responsibility for the competitive harm created by its legally mandated disclosure during an active procurement?",
    "How should procurement processes be designed to prevent the timing of public records requests from undermining competitive fairness?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A is in a vulnerable position \u2014 invested in the process, unaware of the informational breach, and unable to protect their interests; state agency staff may feel the tension between legal obligation and process fairness; Engineer B may feel urgency to act before the window closes",
  "proeth-scenario:ethicalImplications": "Highlights the ethical significance of timing in competitive professional conduct. Reveals institutional design failures where legal transparency obligations conflict with procurement fairness. Raises questions about shared responsibility between individual engineers and institutional actors in maintaining the integrity of professional selection processes.",
  "proeth-scenario:learningMoment": "Teaches students that timing matters enormously in ethical analysis \u2014 the same action (obtaining a competitor\u0027s qualifications) carries very different ethical weight depending on whether the competitive process is active or concluded. Engineers must consider not just what they do, but when they do it.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Active competitive interest is live and exposed; harm from information asymmetry is maximized because the process has not yet concluded",
    "engineer_b": "The timing of the FOIA request \u2014 during rather than after the process \u2014 is ethically significant and likely to be the focus of BER scrutiny",
    "public": "A government selection process is operating under compromised conditions without public awareness",
    "state_agency": "Bears institutional responsibility for the integrity of an active procurement that is now compromised by information asymmetry it was legally required to create"
  },
  "proeth:activatesConstraint": [
    "Fair_Competition_Constraint",
    "Procurement_Integrity_Constraint"
  ],
  "proeth:causesStateChange": "Active procurement window creates a period of heightened ethical sensitivity; any competitive interference during this window carries greater ethical weight than interference before or after the process",
  "proeth:createsObligation": [
    "State agency obligation to ensure procedural fairness throughout active selection",
    "All competing engineers obligation to refrain from conduct that undermines active procurement integrity"
  ],
  "proeth:description": "The state agency\u0027s interview process for the RFQ remains active and incomplete at the time Engineer B obtains Engineer A\u0027s qualifications, meaning the competitive selection has not yet concluded and Engineer A retains a live stake in the outcome. This temporal overlap is a critical contextual fact that heightens the ethical stakes of the FOIA disclosure.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Concurrent with FOIA filing and disclosure; prior to Engineer B\u0027s submission",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Interview Process Ongoing During Disclosure"
}

Description: A prior Board of Ethical Review case (No. 93-3) involving a franchiser's transition from Engineer A to Engineer B under ethically questionable circumstances was adjudicated and its findings recorded, creating a precedent that the current Discussion section applies to evaluate Engineer B's conduct in the present case. This prior ruling functions as an exogenous normative reference point that shapes the ethical analysis.

Temporal Marker: Prior to present case; referenced in Discussion section as established precedent

Activates Constraints:
  • Precedent_Consistency_Constraint
  • Professional_Ethics_Code_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineers familiar with BER 93-3 may feel the weight of institutional memory and professional accountability; Engineer B in the present case faces the implicit judgment of a prior ruling; students encounter the sobering reality that professional ethical standards have documented history and consequences

Stakeholder Consequences:
  • engineer_b_present_case: Conduct is now measured against an established ethical benchmark, reducing the ability to claim ambiguity or novelty as a defense
  • engineering_profession: Institutional continuity of ethical standards is reinforced; the profession demonstrates that it learns from prior cases and applies consistent norms
  • ber: Precedent creates an obligation of analytical consistency that constrains and guides the current ruling
  • engineering_students: Exposed to the concept that professional ethics is a living, evolving body of adjudicated norms, not merely abstract principles

Learning Moment: Introduces students to the role of precedent in professional ethics adjudication — analogous to case law in legal reasoning. Demonstrates that engineering ethics is not purely situational but is informed by accumulated institutional wisdom and prior rulings that create normative consistency across cases.

Ethical Implications: Reveals that professional ethics operates as a normative system with institutional memory, not merely as individual conscience. Raises questions about the authority and legitimacy of professional ethics bodies. Highlights the tension between rule-based ethical reasoning (apply the precedent) and situational ethical reasoning (evaluate the unique facts), and asks students to consider how both approaches contribute to ethical analysis.

Discussion Prompts:
  • How is the BER's use of prior case precedent similar to and different from the use of legal precedent in courts, and what are the implications for how engineers should understand their ethical obligations?
  • Does the existence of a prior BER ruling on analogous conduct make Engineer B's behavior in the present case more or less defensible, and why?
  • Should engineers be expected to know and apply BER precedents in their professional decision-making, and how does this shape the standard of ethical conduct expected of professionals?
Tension: low Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Event_BER_93-3_Precedent_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How is the BER\u0027s use of prior case precedent similar to and different from the use of legal precedent in courts, and what are the implications for how engineers should understand their ethical obligations?",
    "Does the existence of a prior BER ruling on analogous conduct make Engineer B\u0027s behavior in the present case more or less defensible, and why?",
    "Should engineers be expected to know and apply BER precedents in their professional decision-making, and how does this shape the standard of ethical conduct expected of professionals?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineers familiar with BER 93-3 may feel the weight of institutional memory and professional accountability; Engineer B in the present case faces the implicit judgment of a prior ruling; students encounter the sobering reality that professional ethical standards have documented history and consequences",
  "proeth-scenario:ethicalImplications": "Reveals that professional ethics operates as a normative system with institutional memory, not merely as individual conscience. Raises questions about the authority and legitimacy of professional ethics bodies. Highlights the tension between rule-based ethical reasoning (apply the precedent) and situational ethical reasoning (evaluate the unique facts), and asks students to consider how both approaches contribute to ethical analysis.",
  "proeth-scenario:learningMoment": "Introduces students to the role of precedent in professional ethics adjudication \u2014 analogous to case law in legal reasoning. Demonstrates that engineering ethics is not purely situational but is informed by accumulated institutional wisdom and prior rulings that create normative consistency across cases.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "ber": "Precedent creates an obligation of analytical consistency that constrains and guides the current ruling",
    "engineer_b_present_case": "Conduct is now measured against an established ethical benchmark, reducing the ability to claim ambiguity or novelty as a defense",
    "engineering_profession": "Institutional continuity of ethical standards is reinforced; the profession demonstrates that it learns from prior cases and applies consistent norms",
    "engineering_students": "Exposed to the concept that professional ethics is a living, evolving body of adjudicated norms, not merely abstract principles"
  },
  "proeth:activatesConstraint": [
    "Precedent_Consistency_Constraint",
    "Professional_Ethics_Code_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/141#Action_BER_Case_93-3__Engineer_B_Reviews_Design_Informati",
  "proeth:causesStateChange": "Normative landscape of the present case is shaped by an existing ethical ruling; Engineer B\u0027s conduct is now evaluable against an established standard rather than in a vacuum",
  "proeth:createsObligation": [
    "BER obligation to apply prior precedent consistently to analogous facts",
    "Engineering community obligation to be aware of and guided by established BER rulings"
  ],
  "proeth:description": "A prior Board of Ethical Review case (No. 93-3) involving a franchiser\u0027s transition from Engineer A to Engineer B under ethically questionable circumstances was adjudicated and its findings recorded, creating a precedent that the current Discussion section applies to evaluate Engineer B\u0027s conduct in the present case. This prior ruling functions as an exogenous normative reference point that shapes the ethical analysis.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Prior to present case; referenced in Discussion section as established precedent",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "BER 93-3 Precedent Established"
}

Description: As a consequence of the FOIA disclosure, Engineer A's proprietary competitive qualifications — including methodologies, experience claims, key personnel, and strategic positioning — are now in the hands of a direct competitor during an active procurement. This exposure is irreversible and cannot be remedied after the fact.

Temporal Marker: Upon state's release of documents to Engineer B; persists through remainder of procurement

Activates Constraints:
  • Fair_Competition_Constraint
  • Prohibition_On_Competitive_Injury_Constraint
  • Professional_Integrity_Constraint
  • Confidentiality_Of_Competitive_Submissions_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A experiences a profound sense of violation — their professional work product, carefully prepared to win a competitive opportunity, has been weaponized against them by a competitor using a legal mechanism; Engineer B may experience cognitive dissonance between legal justification and ethical unease; the engineering community observes a troubling erosion of professional norms

Stakeholder Consequences:
  • engineer_a: Irreversible competitive harm; loss of strategic advantage; potential loss of contract opportunity; erosion of trust in public procurement processes; possible chilling effect on future participation in public RFQs
  • engineer_b: Short-term competitive advantage gained at significant ethical cost; professional reputation at risk; potential BER finding of ethical violation; possible exclusion from future procurements if conduct becomes known
  • state_agency: Procurement integrity compromised; potential legal and political exposure if selection outcome is challenged; institutional pressure to reform records exemption policies
  • engineering_profession: Norm of fair competition visibly undermined; potential chilling effect on engineer participation in public procurements; professional societies face pressure to issue guidance and advocate for policy reform
  • public: Risk of suboptimal engineering selection; erosion of confidence in government procurement integrity

Learning Moment: Demonstrates that professional harm can be irreversible — once competitive information is disclosed, it cannot be 'undisclosed.' Engineers must understand that ethical violations in competitive contexts can cause permanent harm to colleagues and to the profession's institutional integrity, and that legal permissibility does not neutralize ethical responsibility for such harm.

Ethical Implications: Reveals the limits of legal frameworks in protecting professional fairness, and the corresponding importance of professional ethical norms as a supplementary protective layer. Raises deep questions about moral responsibility in indirect causal chains — when harm is caused by a legally required intermediary action, does the initiating party bear full, partial, or no ethical responsibility? Highlights the duty of engineers to protect not just their clients but also the integrity of the professional systems within which they operate.

Discussion Prompts:
  • Given that the harm to Engineer A is irreversible, what remedies — if any — are available, and are they adequate to restore fairness?
  • Does Engineer B bear ethical responsibility for harm that was caused by a legally mandatory state action (the FOIA release), and how should we think about moral responsibility in such indirect causal chains?
  • What systemic reforms — to procurement law, professional ethics codes, or both — would be needed to prevent this type of harm from recurring?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "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/cases/141#Event_Engineer_A_s_Qualifications_Exposed_to_Competitor",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Given that the harm to Engineer A is irreversible, what remedies \u2014 if any \u2014 are available, and are they adequate to restore fairness?",
    "Does Engineer B bear ethical responsibility for harm that was caused by a legally mandatory state action (the FOIA release), and how should we think about moral responsibility in such indirect causal chains?",
    "What systemic reforms \u2014 to procurement law, professional ethics codes, or both \u2014 would be needed to prevent this type of harm from recurring?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A experiences a profound sense of violation \u2014 their professional work product, carefully prepared to win a competitive opportunity, has been weaponized against them by a competitor using a legal mechanism; Engineer B may experience cognitive dissonance between legal justification and ethical unease; the engineering community observes a troubling erosion of professional norms",
  "proeth-scenario:ethicalImplications": "Reveals the limits of legal frameworks in protecting professional fairness, and the corresponding importance of professional ethical norms as a supplementary protective layer. Raises deep questions about moral responsibility in indirect causal chains \u2014 when harm is caused by a legally required intermediary action, does the initiating party bear full, partial, or no ethical responsibility? Highlights the duty of engineers to protect not just their clients but also the integrity of the professional systems within which they operate.",
  "proeth-scenario:learningMoment": "Demonstrates that professional harm can be irreversible \u2014 once competitive information is disclosed, it cannot be \u0027undisclosed.\u0027 Engineers must understand that ethical violations in competitive contexts can cause permanent harm to colleagues and to the profession\u0027s institutional integrity, and that legal permissibility does not neutralize ethical responsibility for such harm.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Irreversible competitive harm; loss of strategic advantage; potential loss of contract opportunity; erosion of trust in public procurement processes; possible chilling effect on future participation in public RFQs",
    "engineer_b": "Short-term competitive advantage gained at significant ethical cost; professional reputation at risk; potential BER finding of ethical violation; possible exclusion from future procurements if conduct becomes known",
    "engineering_profession": "Norm of fair competition visibly undermined; potential chilling effect on engineer participation in public procurements; professional societies face pressure to issue guidance and advocate for policy reform",
    "public": "Risk of suboptimal engineering selection; erosion of confidence in government procurement integrity",
    "state_agency": "Procurement integrity compromised; potential legal and political exposure if selection outcome is challenged; institutional pressure to reform records exemption policies"
  },
  "proeth:activatesConstraint": [
    "Fair_Competition_Constraint",
    "Prohibition_On_Competitive_Injury_Constraint",
    "Professional_Integrity_Constraint",
    "Confidentiality_Of_Competitive_Submissions_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/141#Action_Engineer_B_Files_FOIA_Request",
  "proeth:causesStateChange": "Engineer A\u0027s competitive position is materially and irreversibly weakened; Engineer B holds an informational advantage that shapes the competitive landscape for the remainder of the procurement; the harm to Engineer A is ongoing and cannot be undone",
  "proeth:createsObligation": [
    "Engineer B obligation to refrain from directly incorporating Engineer A\u0027s strategies or approaches into competing submission",
    "State agency obligation to assess whether procurement should be restructured or restarted to restore fairness",
    "BER obligation to determine whether Engineer B\u0027s conduct constitutes an actionable ethical violation"
  ],
  "proeth:description": "As a consequence of the FOIA disclosure, Engineer A\u0027s proprietary competitive qualifications \u2014 including methodologies, experience claims, key personnel, and strategic positioning \u2014 are now in the hands of a direct competitor during an active procurement. This exposure is irreversible and cannot be remedied after the fact.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Upon state\u0027s release of documents to Engineer B; persists through remainder of procurement",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer A\u0027s Qualifications Exposed to Competitor"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: As a direct outcome of the FOIA disclosure, Engineer B possesses Engineer A's full qualifications while Engineer A remains unaware of this competitive disadvantage

Necessary Factors (NESS):
  • Engineer B's deliberate decision to file FOIA request during active procurement
  • State agency's legal obligation to comply with FOIA disclosure
  • Interview process remaining incomplete at time of disclosure
  • Engineer A's qualifications being on file with the state agency
Sufficient Factors:
  • Filing of FOIA request during active procurement + state compliance + Engineer A's submission on record = information asymmetry
  • No additional factors required once FOIA was filed and state complied
Counterfactual Test: Without Engineer B's deliberate FOIA filing, no disclosure would have occurred during the active procurement phase; Engineer A's qualifications would have remained confidential until process conclusion
Responsibility Attribution:

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

Causal Sequence:
  1. Engineer B Files FOIA Request
    Engineer B deliberately submits a Freedom of Information Act request targeting Engineer A's qualifications during the active procurement interview phase
  2. State Provides FOIA Documents
    State agency releases Engineer A's submitted qualifications to Engineer B in legal compliance with FOIA obligations
  3. Engineer A's Qualifications Exposed to Competitor
    Engineer A's proprietary competitive qualifications, including methodologies, pricing signals, and strategic positioning, are fully disclosed to a direct competitor
  4. Competitive Information Asymmetry Created
    Engineer B gains unilateral access to Engineer A's competitive strategy while Engineer A has no reciprocal knowledge, creating a structurally unfair competitive environment
  5. Engineer B Submits Own Qualifications
    Engineer B leverages the disclosed information to tailor and submit his own qualifications with full knowledge of the competitor's approach
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/141#CausalChain_0dccd088",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a direct outcome of the FOIA disclosure, Engineer B possesses Engineer A\u0027s full qualifications while Engineer A remains unaware of this competitive disadvantage",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B deliberately submits a Freedom of Information Act request targeting Engineer A\u0027s qualifications during the active procurement interview phase",
      "proeth:element": "Engineer B Files FOIA Request",
      "proeth:step": 1
    },
    {
      "proeth:description": "State agency releases Engineer A\u0027s submitted qualifications to Engineer B in legal compliance with FOIA obligations",
      "proeth:element": "State Provides FOIA Documents",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A\u0027s proprietary competitive qualifications, including methodologies, pricing signals, and strategic positioning, are fully disclosed to a direct competitor",
      "proeth:element": "Engineer A\u0027s Qualifications Exposed to Competitor",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B gains unilateral access to Engineer A\u0027s competitive strategy while Engineer A has no reciprocal knowledge, creating a structurally unfair competitive environment",
      "proeth:element": "Competitive Information Asymmetry Created",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer B leverages the disclosed information to tailor and submit his own qualifications with full knowledge of the competitor\u0027s approach",
      "proeth:element": "Engineer B Submits Own Qualifications",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Files FOIA Request",
  "proeth:counterfactual": "Without Engineer B\u0027s deliberate FOIA filing, no disclosure would have occurred during the active procurement phase; Engineer A\u0027s qualifications would have remained confidential until process conclusion",
  "proeth:effect": "Competitive Information Asymmetry Created",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s deliberate decision to file FOIA request during active procurement",
    "State agency\u0027s legal obligation to comply with FOIA disclosure",
    "Interview process remaining incomplete at time of disclosure",
    "Engineer A\u0027s qualifications being on file with the state agency"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Filing of FOIA request during active procurement + state compliance + Engineer A\u0027s submission on record = information asymmetry",
    "No additional factors required once FOIA was filed and state complied"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: As a consequence of the FOIA disclosure, Engineer A's proprietary competitive qualifications — including strategic and technical details submitted in good faith — are exposed to a direct competitor

Necessary Factors (NESS):
  • Engineer A's voluntary submission of qualifications to the state agency
  • State agency's retention of submitted documents as public records subject to FOIA
  • Engineer B's subsequent FOIA filing targeting those specific records
  • Absence of a confidentiality exemption protecting procurement submissions
Sufficient Factors:
  • Submission to public agency + FOIA-accessible record status + competitor's deliberate request = exposure of proprietary information
  • Engineer A's submission was a necessary precondition but not independently sufficient without Engineer B's FOIA action
Counterfactual Test: Had Engineer A not submitted qualifications, there would be nothing to disclose; however, non-submission would have excluded Engineer A from the procurement entirely — the harm arises from the system's failure to protect good-faith submissions, not from Engineer A's act of submitting
Responsibility Attribution:

Agent: Engineer B (primary); State Agency (secondary)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Engineer A Submits RFQ Qualifications
    Engineer A voluntarily responds to a public RFQ by submitting proprietary qualifications to the state agency in good faith
  2. State Retains Documents as Public Records
    State agency holds Engineer A's submission as an official public record subject to FOIA disclosure obligations
  3. Engineer B Files FOIA Request
    Engineer B deliberately targets Engineer A's submission with a FOIA request during the active interview phase
  4. State Provides FOIA Documents
    State agency releases Engineer A's qualifications to Engineer B in compliance with FOIA law
  5. Engineer A's Qualifications Exposed to Competitor
    Engineer A's proprietary competitive information is fully disclosed to Engineer B, undermining competitive integrity of the procurement
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/141#CausalChain_f898f530",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "As a consequence of the FOIA disclosure, Engineer A\u0027s proprietary competitive qualifications \u2014 including strategic and technical details submitted in good faith \u2014 are exposed to a direct competitor",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A voluntarily responds to a public RFQ by submitting proprietary qualifications to the state agency in good faith",
      "proeth:element": "Engineer A Submits RFQ Qualifications",
      "proeth:step": 1
    },
    {
      "proeth:description": "State agency holds Engineer A\u0027s submission as an official public record subject to FOIA disclosure obligations",
      "proeth:element": "State Retains Documents as Public Records",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B deliberately targets Engineer A\u0027s submission with a FOIA request during the active interview phase",
      "proeth:element": "Engineer B Files FOIA Request",
      "proeth:step": 3
    },
    {
      "proeth:description": "State agency releases Engineer A\u0027s qualifications to Engineer B in compliance with FOIA law",
      "proeth:element": "State Provides FOIA Documents",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s proprietary competitive information is fully disclosed to Engineer B, undermining competitive integrity of the procurement",
      "proeth:element": "Engineer A\u0027s Qualifications Exposed to Competitor",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Submits RFQ Qualifications",
  "proeth:counterfactual": "Had Engineer A not submitted qualifications, there would be nothing to disclose; however, non-submission would have excluded Engineer A from the procurement entirely \u2014 the harm arises from the system\u0027s failure to protect good-faith submissions, not from Engineer A\u0027s act of submitting",
  "proeth:effect": "Engineer A\u0027s Qualifications Exposed to Competitor",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s voluntary submission of qualifications to the state agency",
    "State agency\u0027s retention of submitted documents as public records subject to FOIA",
    "Engineer B\u0027s subsequent FOIA filing targeting those specific records",
    "Absence of a confidentiality exemption protecting procurement submissions"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer B (primary); State Agency (secondary)",
  "proeth:sufficientFactors": [
    "Submission to public agency + FOIA-accessible record status + competitor\u0027s deliberate request = exposure of proprietary information",
    "Engineer A\u0027s submission was a necessary precondition but not independently sufficient without Engineer B\u0027s FOIA action"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: After receiving Engineer A's qualifications through the FOIA disclosure, Engineer B proceeds to submit his own qualifications, using the disclosed information as a competitive advantage

Necessary Factors (NESS):
  • Engineer B's deliberate FOIA filing to obtain competitor's qualifications
  • Successful receipt of Engineer A's disclosed qualifications
  • Engineer B's decision to remain in the procurement rather than recuse
  • Engineer B's intent to leverage disclosed information competitively
Sufficient Factors:
  • Receipt of competitor's qualifications + decision to continue in procurement + submission of own tailored qualifications = ethically compromised competitive submission
  • The FOIA filing was the initiating volitional act that made all subsequent steps possible
Counterfactual Test: Without the FOIA filing and resulting disclosure, Engineer B would have submitted qualifications without knowledge of Engineer A's approach; the submission itself might still have occurred, but without the informational advantage that constitutes the ethical violation
Responsibility Attribution:

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

Causal Sequence:
  1. Engineer B Files FOIA Request
    Engineer B strategically files FOIA request during active procurement to obtain competitor's qualifications
  2. Competitive Information Asymmetry Created
    Engineer B gains full knowledge of Engineer A's qualifications, strategies, and competitive positioning
  3. Engineer B Retains Procurement Participation
    Engineer B does not recuse himself despite possessing competitor's confidential information, choosing to exploit the advantage
  4. Engineer B Submits Own Qualifications
    Engineer B submits tailored qualifications informed by Engineer A's disclosed approach, constituting an unfair competitive act
  5. Procurement Integrity Compromised
    The competitive procurement process is structurally undermined by Engineer B's information-advantaged participation, violating principles of fair competition and professional ethics
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/141#CausalChain_68c28629",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "After receiving Engineer A\u0027s qualifications through the FOIA disclosure, Engineer B proceeds to submit his own qualifications, using the disclosed information as a competitive advantage",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B strategically files FOIA request during active procurement to obtain competitor\u0027s qualifications",
      "proeth:element": "Engineer B Files FOIA Request",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B gains full knowledge of Engineer A\u0027s qualifications, strategies, and competitive positioning",
      "proeth:element": "Competitive Information Asymmetry Created",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer B does not recuse himself despite possessing competitor\u0027s confidential information, choosing to exploit the advantage",
      "proeth:element": "Engineer B Retains Procurement Participation",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B submits tailored qualifications informed by Engineer A\u0027s disclosed approach, constituting an unfair competitive act",
      "proeth:element": "Engineer B Submits Own Qualifications",
      "proeth:step": 4
    },
    {
      "proeth:description": "The competitive procurement process is structurally undermined by Engineer B\u0027s information-advantaged participation, violating principles of fair competition and professional ethics",
      "proeth:element": "Procurement Integrity Compromised",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer B Files FOIA Request",
  "proeth:counterfactual": "Without the FOIA filing and resulting disclosure, Engineer B would have submitted qualifications without knowledge of Engineer A\u0027s approach; the submission itself might still have occurred, but without the informational advantage that constitutes the ethical violation",
  "proeth:effect": "Engineer B Submits Own Qualifications",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s deliberate FOIA filing to obtain competitor\u0027s qualifications",
    "Successful receipt of Engineer A\u0027s disclosed qualifications",
    "Engineer B\u0027s decision to remain in the procurement rather than recuse",
    "Engineer B\u0027s intent to leverage disclosed information competitively"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Receipt of competitor\u0027s qualifications + decision to continue in procurement + submission of own tailored qualifications = ethically compromised competitive submission",
    "The FOIA filing was the initiating volitional act that made all subsequent steps possible"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: In BER Case No. 93-3, Engineer B voluntarily notifies Engineer A of his new relationship with the franchiser, establishing a contrasting ethical benchmark of transparency and disclosure against which the current case conduct is measured

Necessary Factors (NESS):
  • Engineer B's voluntary disclosure of the conflicting relationship in BER Case 93-3
  • Engineer B's agreement to review Engineer A's design information under the new relationship
  • The Board of Ethical Review's adjudication of that case creating formal precedent
  • The ethical contrast between proactive disclosure in 93-3 and strategic exploitation in the current case
Sufficient Factors:
  • Voluntary disclosure + BER adjudication = established ethical standard for engineer conduct in competitive/conflicted situations
  • The precedent functions as a normative benchmark sufficient to evaluate Engineer B's conduct in the current case
Counterfactual Test: Without the BER 93-3 precedent, the ethical analysis of the current case would lack a directly analogous professional standard; the precedent strengthens the case that Engineer B's current conduct falls below established ethical expectations
Responsibility Attribution:

Agent: Engineer B (BER 93-3 context); Board of Ethical Review (precedent establishment)
Type: indirect
Within Agent Control: Yes

Causal Sequence:
  1. BER Case 93-3: Engineer B Reviews Design Information
    Engineer B agrees to review Engineer A's design information after entering a new relationship with the franchiser, creating a potential conflict of interest
  2. BER Case 93-3: Engineer B Discloses Relationship to Engineer A
    Engineer B proactively notifies Engineer A of the new conflicting relationship, demonstrating ethical transparency
  3. BER Adjudicates Case 93-3
    The Board of Ethical Review formally evaluates Engineer B's conduct and establishes an ethical standard for handling competitive conflicts and information access
  4. BER 93-3 Precedent Established
    The case creates a documented ethical benchmark: engineers must proactively disclose conflicts and avoid exploiting access to competitor information
  5. Precedent Applied to Current FOIA Case
    BER 93-3 serves as a normative reference point demonstrating that Engineer B's FOIA conduct in the current case falls below the ethical standard he himself previously met
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/141#CausalChain_a692c5ab",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "In BER Case No. 93-3, Engineer B voluntarily notifies Engineer A of his new relationship with the franchiser, establishing a contrasting ethical benchmark of transparency and disclosure against which the current case conduct is measured",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B agrees to review Engineer A\u0027s design information after entering a new relationship with the franchiser, creating a potential conflict of interest",
      "proeth:element": "BER Case 93-3: Engineer B Reviews Design Information",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B proactively notifies Engineer A of the new conflicting relationship, demonstrating ethical transparency",
      "proeth:element": "BER Case 93-3: Engineer B Discloses Relationship to Engineer A",
      "proeth:step": 2
    },
    {
      "proeth:description": "The Board of Ethical Review formally evaluates Engineer B\u0027s conduct and establishes an ethical standard for handling competitive conflicts and information access",
      "proeth:element": "BER Adjudicates Case 93-3",
      "proeth:step": 3
    },
    {
      "proeth:description": "The case creates a documented ethical benchmark: engineers must proactively disclose conflicts and avoid exploiting access to competitor information",
      "proeth:element": "BER 93-3 Precedent Established",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER 93-3 serves as a normative reference point demonstrating that Engineer B\u0027s FOIA conduct in the current case falls below the ethical standard he himself previously met",
      "proeth:element": "Precedent Applied to Current FOIA Case",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "BER Case 93-3: Engineer B Discloses Relationship to Engineer A",
  "proeth:counterfactual": "Without the BER 93-3 precedent, the ethical analysis of the current case would lack a directly analogous professional standard; the precedent strengthens the case that Engineer B\u0027s current conduct falls below established ethical expectations",
  "proeth:effect": "BER 93-3 Precedent Established",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s voluntary disclosure of the conflicting relationship in BER Case 93-3",
    "Engineer B\u0027s agreement to review Engineer A\u0027s design information under the new relationship",
    "The Board of Ethical Review\u0027s adjudication of that case creating formal precedent",
    "The ethical contrast between proactive disclosure in 93-3 and strategic exploitation in the current case"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "Engineer B (BER 93-3 context); Board of Ethical Review (precedent establishment)",
  "proeth:sufficientFactors": [
    "Voluntary disclosure + BER adjudication = established ethical standard for engineer conduct in competitive/conflicted situations",
    "The precedent functions as a normative benchmark sufficient to evaluate Engineer B\u0027s conduct in the current case"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: The state agency's interview process for the RFQ remains active and incomplete at the time Engineer B receives the disclosed qualifications, compounding the competitive harm by ensuring the information can be immediately exploited

Necessary Factors (NESS):
  • State agency's compliance with FOIA request during active procurement
  • Interview phase not yet concluded at time of disclosure
  • Engineer B's strategic timing of FOIA filing to coincide with active procurement phase
  • Absence of procurement-suspension mechanisms triggered by FOIA requests
Sufficient Factors:
  • FOIA compliance during active interviews + Engineer B's continued participation = maximum competitive exploitation window
  • The timing of disclosure during active interviews amplifies the harm beyond what post-process disclosure would cause
Counterfactual Test: Had the state agency deferred FOIA compliance until after the interview process concluded, Engineer B could not have used the disclosed information to influence his own submission or interview preparation; the competitive harm would have been substantially reduced or eliminated
Responsibility Attribution:

Agent: State Agency (primary); Engineer B (secondary for timing exploitation)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Engineer B Files FOIA Request During Active Procurement
    Engineer B strategically times the FOIA filing to occur while the interview process remains ongoing, maximizing the exploitable window
  2. State Provides FOIA Documents
    State agency releases Engineer A's qualifications without suspending disclosure pending procurement conclusion
  3. Interview Process Ongoing During Disclosure
    The active interview phase creates a live competitive context in which the disclosed information can be immediately and directly exploited
  4. Competitive Information Asymmetry Created
    Engineer B enters the interview phase with full knowledge of Engineer A's qualifications while Engineer A remains uninformed of the disclosure
  5. Procurement Integrity Structurally Compromised
    The combination of disclosure timing and ongoing interviews renders the procurement process fundamentally unfair, undermining public confidence in the selection process
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/141#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/141#CausalChain_ba0bb499",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The state agency\u0027s interview process for the RFQ remains active and incomplete at the time Engineer B receives the disclosed qualifications, compounding the competitive harm by ensuring the information can be immediately exploited",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer B strategically times the FOIA filing to occur while the interview process remains ongoing, maximizing the exploitable window",
      "proeth:element": "Engineer B Files FOIA Request During Active Procurement",
      "proeth:step": 1
    },
    {
      "proeth:description": "State agency releases Engineer A\u0027s qualifications without suspending disclosure pending procurement conclusion",
      "proeth:element": "State Provides FOIA Documents",
      "proeth:step": 2
    },
    {
      "proeth:description": "The active interview phase creates a live competitive context in which the disclosed information can be immediately and directly exploited",
      "proeth:element": "Interview Process Ongoing During Disclosure",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B enters the interview phase with full knowledge of Engineer A\u0027s qualifications while Engineer A remains uninformed of the disclosure",
      "proeth:element": "Competitive Information Asymmetry Created",
      "proeth:step": 4
    },
    {
      "proeth:description": "The combination of disclosure timing and ongoing interviews renders the procurement process fundamentally unfair, undermining public confidence in the selection process",
      "proeth:element": "Procurement Integrity Structurally Compromised",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "State Provides FOIA Documents",
  "proeth:counterfactual": "Had the state agency deferred FOIA compliance until after the interview process concluded, Engineer B could not have used the disclosed information to influence his own submission or interview preparation; the competitive harm would have been substantially reduced or eliminated",
  "proeth:effect": "Interview Process Ongoing During Disclosure",
  "proeth:necessaryFactors": [
    "State agency\u0027s compliance with FOIA request during active procurement",
    "Interview phase not yet concluded at time of disclosure",
    "Engineer B\u0027s strategic timing of FOIA filing to coincide with active procurement phase",
    "Absence of procurement-suspension mechanisms triggered by FOIA requests"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "State Agency (primary); Engineer B (secondary for timing exploitation)",
  "proeth:sufficientFactors": [
    "FOIA compliance during active interviews + Engineer B\u0027s continued participation = maximum competitive exploitation window",
    "The timing of disclosure during active interviews amplifies the harm beyond what post-process disclosure would cause"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (12)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
Engineer B's notification to Engineer A before
Entity1 is before Entity2
Engineer A's contract expiration with franchiser time:before
http://www.w3.org/2006/time#before
following his review, notified Engineer A of his relationship with franchiser... Several weeks later... [more]
BER Case No. 93-3 events before
Entity1 is before Entity2
present case events time:before
http://www.w3.org/2006/time#before
While the facts in BER Case No. 93-3 are somewhat different than the facts in the present case, Case... [more]
Engineer A's contract expiration with franchiser meets
Entity1 ends exactly when Entity2 begins
franchiser's formal retention of Engineer B as design engineer time:intervalMeets
http://www.w3.org/2006/time#intervalMeets
Several weeks later, Engineer A's agreement with the franchiser expired and the franchiser retained ... [more]
Engineer A's qualifications submission to state agency before
Entity1 is before Entity2
Engineer B's FOIA request time:before
http://www.w3.org/2006/time#before
In response to a public request for qualifications (RFQ), Engineer A submits his firm's engineering ... [more]
Engineer B's FOIA request before
Entity1 is before Entity2
interview process conclusion time:before
http://www.w3.org/2006/time#before
Prior to the interview process, Engineer B... submits a state Freedom of Information Act (FOIA) requ... [more]
state's provision of Engineer A's qualifications to Engineer B before
Entity1 is before Entity2
Engineer B's own qualifications submission time:before
http://www.w3.org/2006/time#before
The state provides the information to Engineer B. Thereafter, Engineer B submits his firm's engineer... [more]
Engineer B's FOIA request before
Entity1 is before Entity2
Engineer B's own qualifications submission time:before
http://www.w3.org/2006/time#before
Engineer B... submits a state Freedom of Information Act (FOIA) request in order to obtain a copy of... [more]
Engineer A's multi-year service to franchiser before
Entity1 is before Entity2
franchiser's termination notice to Engineer A time:before
http://www.w3.org/2006/time#before
Engineer A was retained by a major franchiser to provide engineering design services... After severa... [more]
franchiser's discussions with Engineer B during
Entity1 occurs entirely within the duration of Entity2
Engineer A's active contract period time:intervalDuring
http://www.w3.org/2006/time#intervalDuring
In order to maintain continuity and before the contract expired, the franchiser began discussions wi... [more]
franchiser's retention of Engineer B for preliminary review before
Entity1 is before Entity2
Engineer A's contract expiration time:before
http://www.w3.org/2006/time#before
before the contract expired, the franchiser began discussions with Engineer B and retained Engineer ... [more]
franchiser's instruction to Engineer B not to disclose their relationship before
Entity1 is before Entity2
Engineer B's design review time:before
http://www.w3.org/2006/time#before
Prior to the review, franchiser specifically told Engineer B not to disclose to their relationship t... [more]
Engineer B's design review before
Entity1 is before Entity2
Engineer B's notification to Engineer A time:before
http://www.w3.org/2006/time#before
Engineer B reviewed the design information the following week and following his review, notified Eng... [more]
About Allen Relations & OWL-Time

Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.

Each relation includes both a ProEthica custom property and a time:* OWL-Time property for maximum compatibility.