{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_Firm_A_Markets_City_Role_to_Developers",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Market Firm A\u0027s private services based solely on technical expertise, project portfolio, and firm capabilities, with no reference to the city engineer role",
    "Proactively resign the city consulting contract before expanding private developer marketing efforts in the jurisdiction",
    "Seek a formal ethics opinion from the state engineering board before using the city role in any marketing materials"
  ],
  "proeth-scenario:characterMotivation": "Firm A sought a competitive differentiator in the private developer market. Its city engineer role provided unique, demonstrable value \u2014 insider knowledge of the review process and the ability to streamline inspections \u2014 that competitors could not match. The 50% cost savings promise was a rational, if ethically impermissible, business development strategy.",
  "proeth-scenario:consequencesIfAlternative": [
    "Marketing on technical merit alone is fully permissible; Firm A competes on a level playing field, no Code violation occurs, and the city role retains its integrity as a public trust function.",
    "Resigning the city contract before marketing to developers cleanly separates the roles; Firm A loses public sector revenue but is free to compete for private developer work without any conflict, and no ethical violation arises.",
    "Seeking a prior ethics opinion demonstrates good faith and professional responsibility; the board would almost certainly advise against the marketing practice, giving Firm A clear guidance before a violation occurs and potentially prompting a structural redesign of its business model."
  ],
  "proeth-scenario:decisionSignificance": "This is the clearest and most teachable violation in the case: the explicit monetization of a public authority role. Students learn that Section II.4.d is violated not only by biased decisions but by the act of leveraging governmental position as a marketing instrument, regardless of whether any individual inspection is actually compromised. The harm is in the structural corruption of the public role.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s right to market professional services competes directly with the obligation not to exploit a public trust position for private gain. The city role was granted in the public interest; converting it into a commercial advantage betrays that trust and coerces developers into a pay-to-play dynamic, however implicitly. Loyalty to public employer versus loyalty to private clients reaches its sharpest expression here.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Direct violation of NSPE Code Section II.4.d; potential disciplinary action against Firm A; erosion of public trust in municipal engineering; creation of an implicit pay-to-play environment where developers feel pressured to hire Firm A to receive favorable treatment; competitive harm to other engineering firms who cannot offer equivalent leverage.",
  "proeth:description": "Firm A made a deliberate decision to openly use its position as the city\u0027s engineer as a marketing tool to attract private developer clients, explicitly promising prospective clients 50% savings on inspection costs by hiring Firm A. This transformed a public trust role into a private commercial advantage.",
  "proeth:foreseenUnintendedEffects": [
    "Suggests Firm A may provide developers less than the full independent inspection services they need",
    "Creates appearance that city approval is commercially available through Firm A\u0027s dual role",
    "Undermines public confidence in the impartiality of city review and inspection",
    "Potentially compromises the rigor of city-side inspection to maintain developer client relationships"
  ],
  "proeth:guidedByPrinciple": [
    "Integrity and honesty in professional representations",
    "Public trust in engineering oversight functions",
    "Avoidance of conduct that demeans the profession",
    "Faithful agency to the city as primary client"
  ],
  "proeth:hasAgent": "Firm A (private consulting engineering firm, principals and marketing decision-makers)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Commercial self-promotion and revenue growth vs. integrity of public engineering oversight and honest client representation",
    "proeth:resolutionReasoning": "Firm A resolved the conflict in favor of commercial self-interest, using a public trust position as a marketing asset in a manner the Board found particularly troubling, as it suggested the city-side services were being rendered at less than the full standard required"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Attract private developer clients by leveraging the implicit promise that work reviewed by Firm A in its city role would be more readily approved, thereby reducing developers\u0027 total inspection expenditure",
  "proeth:requiresCapability": [
    "Ethical conflict of interest analysis",
    "Understanding of the boundaries between public trust roles and private commercial activity",
    "Honest and transparent client communication"
  ],
  "proeth:temporalMarker": "Ongoing, active marketing decision concurrent with city engagement",
  "proeth:violatesObligation": [
    "Obligation not to exploit a public trust role for private commercial gain (NSPE Code Section II.4.d)",
    "Duty to avoid conduct that creates the appearance of impropriety or compromises impartiality",
    "Obligation to provide developers the full range of independent inspection services they require",
    "Duty not to use confidential or positional information from one client engagement to benefit another",
    "Obligation to act in the public interest, not personal financial interest",
    "Prohibition against solicitation of clients through misleading or ethically compromised representations"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Firm A Markets City Role to Developers"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_Engineer_Serves_Dual_Clients_Simultaneously__BER_6",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the private developer engagement and maintain exclusive loyalty to the county commission",
    "Resign the county commission role before accepting the developer client whose project requires commission negotiation",
    "Accept the developer client but formally recuse from all county commission deliberations involving that developer\u0027s project, with documented recusal"
  ],
  "proeth-scenario:characterMotivation": "The engineering consultant sought to maximize client relationships and revenue by serving both a governmental body (the county commission) and a private developer simultaneously. The county role likely provided prestige and steady income, while the developer client offered project-based fees. The consultant may have believed professional competence would allow impartial service to both.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining the developer engagement preserves the engineer\u0027s impartiality as county staff; the county receives unconflicted advice, and no ethical violation occurs, though the engineer foregoes private revenue.",
    "Resigning the county role before accepting the developer client cleanly separates the relationships; the engineer is free to advocate for the developer without any conflict, though the county loses its engineering resource.",
    "Formal recusal partially mitigates the conflict but may not satisfy the Code if the engineer\u0027s county work has already shaped the standards or policies the developer\u0027s project must meet; the Board in later cases (75-7) found recusal permissible only under specific conditions."
  ],
  "proeth-scenario:decisionSignificance": "BER 62-7 establishes the foundational precedent: dual retention by a governmental body and a private party whose interests are adjudicated by that body is impermissible. Students learn that the conflict is not hypothetical \u2014 the engineer literally cannot review his own work objectively \u2014 and that the structural impossibility of impartiality, not merely its appearance, drives the ethical prohibition.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to provide objective, independent advice to the county commission conflicts with the financial and professional obligation to advance the developer-client\u0027s interests before that same commission. Self-review \u2014 passing judgment on one\u0027s own recommendations \u2014 is the paradigmatic conflict, undermining the integrity of both roles simultaneously.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Integrity of county engineering decisions; fairness to other developers not represented by the county\u0027s engineer; professional credibility of the engineer; validity of county approvals that may have been influenced by self-interest; precedent-setting for future dual-role cases.",
  "proeth:description": "In BER Case 62-7, the engineering consultant made a deliberate decision to accept retention by both a county commission (as de facto engineering staff) and a private developer whose project required extensive negotiation with that same commission. This placed the engineer in the position of passing engineering judgment on his own work and recommendations.",
  "proeth:foreseenUnintendedEffects": [
    "Self-assessment of own recommendations on behalf of the commission",
    "Divided loyalties between commission and developer with potentially opposing interests"
  ],
  "proeth:guidedByPrinciple": [
    "Impartiality in engineering judgment",
    "Faithful agency",
    "Avoidance of self-interest in professional decisions"
  ],
  "proeth:hasAgent": "Engineering consultant (unnamed, BER Case 62-7)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Impartial public engineering judgment vs. private client advocacy",
    "proeth:resolutionReasoning": "Board determined the conflict of interest was inherent and unavoidable; the engineer\u0027s self-interest and divided loyalties were incompatible with ethical practice regardless of good intentions"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Serve both the county commission\u0027s engineering needs and the private developer\u0027s design needs, likely seeking to maximize engagement and revenue",
  "proeth:requiresCapability": [
    "Conflict of interest recognition",
    "Impartial engineering judgment",
    "Client relationship boundary management"
  ],
  "proeth:temporalMarker": "1962, historical precedent",
  "proeth:violatesObligation": [
    "Duty to avoid conflicts of interest",
    "Obligation not to pass engineering judgment on one\u0027s own work",
    "Duty of undivided loyalty to each client",
    "Prohibition against self-dealing in a position of public trust"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer Serves Dual Clients Simultaneously (BER 62-7)"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_Municipal_Engineer_Accepts_Private_Firm_Role__BER_",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline the private firm role entirely and serve only as statutory municipal engineer",
    "Accept the private firm role but contractually prohibit the firm from seeking municipal contracts during the engineer\u0027s statutory tenure",
    "Disclose the dual role to municipal officials and obtain their informed written consent before proceeding"
  ],
  "proeth-scenario:characterMotivation": "The engineer sought to maintain a private consulting income stream while fulfilling a statutory public role, likely viewing the two as complementary given the shared subject matter expertise. The consultant (non-employee) status may have felt like a meaningful distinction that preserved independence while allowing dual participation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining the private role eliminates any conflict concern entirely; the engineer\u0027s statutory service is unconflicted, though the engineer foregoes private income and the municipality may lose a candidate unwilling to serve under those constraints.",
    "Prohibiting private firm municipal contracts structurally separates the revenue streams; the engineer\u0027s statutory advice cannot benefit the private firm, significantly reducing conflict risk while preserving both roles.",
    "Disclosure and consent do not eliminate the conflict but demonstrate transparency and respect for the municipality\u0027s right to informed decision-making; the municipality can then impose conditions or decline, placing the ethical burden appropriately on the institutional client."
  ],
  "proeth-scenario:decisionSignificance": "BER 74-2 introduces important nuance: not all dual roles are impermissible. The Board\u0027s finding of permissibility teaches students that context, structure, and the nature of the relationship matter. The public interest rationale and consultant (rather than employee) status were dispositive. Students learn to analyze dual roles along multiple dimensions rather than applying a blanket prohibition.",
  "proeth-scenario:ethicalTension": "The public interest in having qualified engineers serve statutory municipal roles (which may be difficult to fill) competes with the risk that private consulting work for the same municipality creates financial dependencies that compromise independent judgment. The case tests whether formal employment status is the ethical dividing line or whether functional authority and financial interest matter more.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Availability of qualified engineers for statutory public roles; integrity of municipal engineering advice; potential for financial self-dealing in municipal contracts; precedent for how broadly or narrowly the conflict-of-interest prohibition is construed.",
  "proeth:description": "In BER Case 74-2, the engineer made a deliberate decision to serve simultaneously as the statutory municipal engineer and as a consultant within a private firm providing engineering services to the same municipality. The Board found this permissible given the public interest rationale and the engineer\u0027s consultant (non-employee) status.",
  "proeth:foreseenUnintendedEffects": [
    "Potential appearance of self-dealing in recommending or approving own firm\u0027s work",
    "Tension with conflict of interest principles established in BER Case 62-7"
  ],
  "proeth:fulfillsObligation": [
    "Serving the public interest by providing competent engineering to municipalities lacking in-house capacity",
    "Complying with state law requiring municipal engineer retention"
  ],
  "proeth:guidedByPrinciple": [
    "Public interest in access to competent engineering services",
    "Serving small municipalities that lack engineering resources"
  ],
  "proeth:hasAgent": "Municipal engineer (unnamed, BER Case 74-2)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Strict conflict of interest avoidance vs. public interest in competent engineering for small municipalities",
    "proeth:resolutionReasoning": "Board prioritized public access to competent engineering, reasoning that state law implicitly sanctioned the arrangement; the Board later acknowledged difficulty reconciling this with BER Case 62-7"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Provide comprehensive engineering services to a small municipality that could not otherwise access competent engineering, while maintaining private practice",
  "proeth:requiresCapability": [
    "Municipal engineering",
    "Conflict of interest management",
    "Transparency with municipal client"
  ],
  "proeth:temporalMarker": "1974, historical precedent",
  "proeth:violatesObligation": [
    "Strict avoidance of conflict of interest situations (in tension with BER 62-7 standard)",
    "Duty to avoid self-assessment of own firm\u0027s work"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Municipal Engineer Accepts Private Firm Role (BER 74-2)"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_Commission_Engineer_Abstains_from_Conflicted_Vote_",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Resign from the commission rather than serve in a role where recusal is frequently required, undermining the commission\u0027s deliberative capacity",
    "Cease accepting private clients whose applications will foreseeably come before the commission, maintaining full participation in all commission matters",
    "Abstain from discussion and voting but also proactively disclose the conflict to fellow commissioners and the public record in each instance"
  ],
  "proeth-scenario:characterMotivation": "The engineer sought to remain on the commission (likely for professional prestige, public service commitment, or compensation) while continuing to serve private clients in the same jurisdiction. Abstention was chosen as a procedural mechanism to honor both commitments without formally abandoning either, reflecting an attempt to self-regulate the conflict.",
  "proeth-scenario:consequencesIfAlternative": [
    "Resignation eliminates the conflict entirely and allows the commission to seat a member without conflicting private interests; the engineer loses the public role but serves private clients without restriction.",
    "Limiting private clients to those without commission exposure allows full commission participation; the engineer\u0027s public role is unconflicted, though private practice is constrained geographically or by client type.",
    "Enhanced disclosure beyond mere abstention strengthens transparency and public accountability; fellow commissioners and the public can scrutinize whether informal influence is occurring, adding a layer of external check on the engineer\u0027s conduct."
  ],
  "proeth-scenario:decisionSignificance": "BER 75-7 teaches that procedural self-regulation (abstention) can be ethically sufficient under specific conditions, but the Board\u0027s caveat \u2014 the engineer must not act to influence the favorable decision \u2014 reveals that abstention is a floor, not a ceiling. Students learn to distinguish between formal compliance mechanisms and substantive ethical obligations, and to recognize that informal influence can constitute a violation even without a recorded vote.",
  "proeth-scenario:ethicalTension": "The engineer\u0027s duty to contribute fully to commission deliberations (fulfilling the public role) competes with the duty of loyalty to private clients (whose applications come before the commission). Abstention resolves the vote but not the underlying tension: the engineer\u0027s presence, relationships, and informal influence may still shape outcomes even without a formal vote.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Fairness of commission permit decisions; integrity of the abstention mechanism if informal influence continues; public confidence that commission members are not advantaging their private clients; professional standing of the engineer if the caveat is violated.",
  "proeth:description": "In BER Case 75-7, the engineer serving on a commission made a deliberate decision to abstain from discussion and voting on permit applications involving private owners for whom the engineer also provided services. The Board found this abstention made the dual role ethically permissible, with the caveat that the engineer must not act to influence the favorable decision.",
  "proeth:foreseenUnintendedEffects": [
    "Reduced commission participation and potential gaps in technical expertise during relevant deliberations",
    "Remaining risk of informal influence even absent formal participation"
  ],
  "proeth:fulfillsObligation": [
    "Avoiding participation in decisions where self-interest was implicated",
    "Transparency about conflict through abstention",
    "Duty not to use positional authority to benefit private clients"
  ],
  "proeth:guidedByPrinciple": [
    "Impartiality in public decision-making roles",
    "Avoidance of conflict of interest",
    "Transparency"
  ],
  "proeth:hasAgent": "Engineer serving on commission (unnamed, BER Case 75-7)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Full discharge of commission duties vs. ethical obligation to abstain from conflicted decisions",
    "proeth:resolutionReasoning": "Engineer correctly prioritized ethical abstention; Board affirmed this as the minimum required standard and cautioned against any informal influence"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Maintain ethical propriety in dual role by removing oneself from decision-making processes where personal financial interest in private clients was implicated",
  "proeth:requiresCapability": [
    "Conflict of interest identification",
    "Self-recusal judgment",
    "Boundary management between public and private roles"
  ],
  "proeth:temporalMarker": "1975, historical precedent",
  "proeth:withinCompetence": true,
  "rdfs:label": "Commission Engineer Abstains from Conflicted Vote (BER 75-7)"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_County_Engineer_Withholds_Recommendation_on_Own_Pl",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Resign as county engineer rather than accept a structural role in which recusal from significant decisions is routinely required",
    "Provide the recommendation but with full written disclosure of the private client relationship, leaving the county to weigh the conflict",
    "Arrange for an independent third-party engineer to review and recommend on all submissions from the county engineer\u0027s private clients"
  ],
  "proeth-scenario:characterMotivation": "The part-time county engineer (or the institutional structure governing the role) recognized that recommending approval of plans submitted by the engineer\u0027s own private clients would be transparently self-serving and professionally untenable. Withholding the recommendation was a pragmatic acknowledgment of the inherent conflict, preserving at least the formal integrity of the review process.",
  "proeth-scenario:consequencesIfAlternative": [
    "Resignation eliminates the conflict and allows the county to appoint an engineer without private client entanglements; the county receives unconflicted recommendations on all submissions, though it loses the part-time engineer\u0027s services.",
    "Providing a disclosed recommendation preserves the formal completeness of the review process but the Board\u0027s \u0027useless act\u0027 analysis suggests the recommendation lacks genuine professional value regardless of disclosure; the county may be misled into treating it as independent advice.",
    "Third-party independent review is the most structurally sound alternative: it preserves the county engineer role, eliminates self-review, and ensures that private clients receive genuine independent scrutiny; it does add cost and coordination complexity."
  ],
  "proeth-scenario:decisionSignificance": "BER 67-12 teaches students that the ethical remedy for a structural conflict is not to perform the conflicted act with a disclaimer, but to recognize that the act itself is void of professional integrity and must be withheld. The \u0027useless act\u0027 doctrine is a powerful teaching concept: some professional outputs are inherently worthless when produced under irreconcilable conflict, regardless of how carefully the engineer tries to be objective.",
  "proeth-scenario:ethicalTension": "The county engineer\u0027s duty to provide professional recommendations to the county (fulfilling the public role completely) conflicts with the impossibility of rendering an objective recommendation on one\u0027s own work. The tension is between formal completeness of the public role and the substantive integrity of its outputs. The Board\u0027s \u0027useless act\u0027 characterization reveals that a conflicted recommendation has no genuine professional value.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Validity and reliability of county engineering recommendations; safety of projects approved on the basis of a conflicted review; fairness to developers whose plans are reviewed by a disinterested county engineer while Firm A\u0027s private clients receive de facto self-review; legal exposure of the county if approvals are later challenged.",
  "proeth:description": "In BER Case 67-12, the part-time county engineer acting as a private consultant made (or was directed to make) a deliberate decision not to offer recommendations for approval of plans submitted by developer-clients in his private capacity. The Board affirmed this as the ethically required conduct, characterizing any such recommendation as a \u0027useless act\u0027 given the inherent conflict.",
  "proeth:foreseenUnintendedEffects": [
    "Reduced efficiency in plan review process",
    "Potential awkwardness with private developer clients expecting advocacy"
  ],
  "proeth:fulfillsObligation": [
    "Maintaining integrity of the public engineering review function",
    "Avoiding self-assessment of own professional work",
    "Upholding impartiality in county engineering role"
  ],
  "proeth:guidedByPrinciple": [
    "Impartiality in public roles",
    "Avoidance of self-dealing",
    "Integrity of engineering review processes"
  ],
  "proeth:hasAgent": "Part-time county engineer / private consultant (unnamed, BER Case 67-12)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Private client advocacy vs. impartial public engineering review",
    "proeth:resolutionReasoning": "Board affirmed abstention from recommendation as ethically required, noting the logical and ethical impossibility of objective self-review"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Preserve impartiality of the county engineering review function by refusing to recommend approval of plans the engineer had prepared in a private capacity",
  "proeth:requiresCapability": [
    "Conflict of interest recognition",
    "Self-recusal in review of own work",
    "Boundary management between county and private roles"
  ],
  "proeth:temporalMarker": "1967, historical precedent",
  "proeth:withinCompetence": true,
  "rdfs:label": "County Engineer Withholds Recommendation on Own Plans (BER 67-12)"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_Engineer_A_Accepts_Multiple_Public_and_Private_Rol",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept only one public role at a time and limit private consulting to jurisdictions where Engineer A holds no public appointment",
    "Accept the multiple public roles but decline all private consulting work for firms submitting proposals to any of those public bodies",
    "Seek advance ethics guidance from the state board and establish a formal conflict-management protocol \u2014 with documented recusals and independent review \u2014 before assuming the full portfolio of roles"
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought to maximize professional engagement and income by accumulating multiple public and private roles simultaneously, likely viewing each as complementary expressions of engineering expertise and public service. The amended Code\u0027s \u0027review and recommend rather than decide\u0027 distinction may have been understood as a formal safe harbor that permitted the accumulation of roles.",
  "proeth-scenario:consequencesIfAlternative": [
    "Limiting to one public role and geographically separated private work dramatically reduces conflict risk; each role is served with undivided loyalty, though Engineer A foregoes substantial income and public influence.",
    "Retaining multiple public roles while eliminating private consulting for submitting firms preserves public service breadth without the financial incentive to favor any private client; public recommendations are structurally unconflicted, though Engineer A\u0027s private practice is significantly constrained.",
    "Proactive ethics guidance and a formal conflict-management protocol demonstrate professional responsibility and may reveal that some role combinations are impermissible regardless of procedural safeguards; the process itself educates Engineer A and creates an accountability record that protects both the engineer and the public bodies served."
  ],
  "proeth-scenario:decisionSignificance": "BER 82-4 is the most complex precedent in the sequence, teaching students that formal compliance with amended Code language (\u0027review and recommend\u0027) does not automatically resolve underlying ethical concerns when roles multiply to the point of systemic entanglement. The case also illustrates how Code amendments can create new interpretive boundaries that sophisticated actors may exploit. Students should question whether the \u0027recommend vs. decide\u0027 distinction adequately captures the real conflict when the same engineer recommends across multiple overlapping authorities.",
  "proeth-scenario:ethicalTension": "The breadth of simultaneous roles creates a web of potential conflicts: Engineer A\u0027s private consulting work for firms developing city and county proposals is reviewed and recommended upon by Engineer A in multiple public capacities. Even if no single role crosses the \u0027decision\u0027 threshold, the cumulative effect raises serious questions about whether any recommendation is genuinely independent. The tension is between formal Code compliance and substantive ethical integrity.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Integrity of multiple public engineering functions simultaneously; risk that private consulting fees create systematic bias across county, city, and airport authority recommendations; public accountability when a single engineer holds de facto influence over multiple governmental bodies; the adequacy of the amended Code\u0027s \u0027recommend vs. decide\u0027 safe harbor as a genuine ethical protection.",
  "proeth:description": "In BER Case 82-4, Engineer A made deliberate decisions to simultaneously serve as county engineer, city engineer, project administrator for the county airport authority, administrator of a city block grant program, and private consultant to firms developing city and county project proposals. The Board found these roles permissible under the amended Code because Engineer A reviewed and recommended rather than made final \u0027decisions.\u0027",
  "proeth:foreseenUnintendedEffects": [
    "Appearance of conflict of interest across overlapping jurisdictions",
    "Risk that review and recommendation functions shade into de facto decision-making",
    "Potential for private consulting work to benefit from positional knowledge gained in public roles"
  ],
  "proeth:fulfillsObligation": [
    "Operating within the letter of the amended Code provisions distinguishing decisions from recommendations",
    "Not directly participating in final approval decisions on work in which he had a private interest",
    "Providing engineering services across multiple public entities"
  ],
  "proeth:guidedByPrinciple": [
    "Compliance with amended Code provisions",
    "Public service through engineering expertise",
    "Technical distinction between recommendation and decision authority"
  ],
  "proeth:hasAgent": "Engineer A (unnamed, BER Case 82-4)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Strict conflict avoidance vs. permissible multi-role engagement under amended Code provisions",
    "proeth:resolutionReasoning": "Board resolved by applying the amended Code\u0027s technical distinction between decision-making authority and advisory/review functions, finding Engineer A\u0027s roles fell within the permissible category\u2014though the current case\u0027s Board distinguished Firm A\u0027s situation as more clearly violative"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Maximize professional engagement across multiple public and private clients within the same jurisdiction, providing comprehensive engineering services",
  "proeth:requiresCapability": [
    "Multi-jurisdictional engineering administration",
    "Conflict of interest analysis under amended Code",
    "Role boundary management across public and private engagements"
  ],
  "proeth:temporalMarker": "1982, historical precedent",
  "proeth:violatesObligation": [
    "Spirit of conflict of interest avoidance (arguably)",
    "Duty to avoid situations creating appearance of impropriety across overlapping roles"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Accepts Multiple Public and Private Roles (BER 82-4)"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_City_Engages_Firm_A",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Hire full-time municipal engineering staff to perform plan review and inspection in-house",
    "Retain Firm A under a contract that explicitly prohibits Firm A from accepting private developer clients within city jurisdiction",
    "Establish a rotating panel of multiple consulting firms to share review duties, reducing any single firm\u0027s structural power"
  ],
  "proeth-scenario:characterMotivation": "The city sought an efficient, cost-effective mechanism to ensure developer-submitted plans met municipal engineering standards, leveraging an established private consulting relationship rather than building in-house staff capacity. Administrative convenience and budget optimization drove the decision.",
  "proeth-scenario:consequencesIfAlternative": [
    "In-house staffing would eliminate the dual-loyalty risk entirely but requires capital investment, ongoing personnel costs, and time to build institutional expertise; no ethical conflict arises downstream.",
    "Retaining Firm A with an exclusivity restriction preserves the consulting relationship while closing the conflict-of-interest pathway; Firm A must choose its market, and the city retains a known partner without the downstream marketing abuse.",
    "A rotating panel distributes authority and reduces capture risk but introduces coordination complexity and may reduce consistency in standards application; no single firm gains enough leverage to exploit the city role commercially."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates how well-intentioned governmental outsourcing can inadvertently create the structural preconditions for conflicts of interest before any individual actor behaves unethically. The city\u0027s decision is the root cause of all downstream tensions, teaching students that systemic design choices carry ethical weight independent of individual conduct.",
  "proeth-scenario:ethicalTension": "Public interest in rigorous, impartial engineering review vs. the structural risk of delegating governmental authority to a private firm that operates in the same commercial marketplace as the developers it will oversee. Efficiency competes with institutional independence.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public trust in municipal engineering oversight; integrity of the plan review and inspection process; safety of constructed projects; fairness to all developers who must submit to Firm A\u0027s authority; long-term credibility of the city\u0027s regulatory function.",
  "proeth:description": "The city made a deliberate decision to retain Firm A, a private consulting engineering firm, to provide design review and construction inspection services on the city\u0027s behalf. This foundational arrangement placed Firm A in a dual-authority position over developer-submitted plans.",
  "proeth:foreseenUnintendedEffects": [
    "Potential for Firm A to leverage city role for private business development",
    "Risk of divided loyalties if Firm A simultaneously serves private developers"
  ],
  "proeth:fulfillsObligation": [
    "Providing infrastructure oversight for public benefit",
    "Ensuring development meets city design standards"
  ],
  "proeth:guidedByPrinciple": [
    "Public health and safety",
    "Responsible stewardship of public infrastructure"
  ],
  "proeth:hasAgent": "City (municipal authority/contracting agent)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Engineering competence vs. independence and impartiality",
    "proeth:resolutionReasoning": "City prioritized operational efficiency and competence, analogous to the reasoning in BER Case 74-2, without adequately accounting for the conflict risks identified in BER Case 62-7"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Secure competent engineering review and inspection capacity without maintaining in-house engineering staff",
  "proeth:requiresCapability": [
    "Municipal procurement and contracting",
    "Assessment of engineering firm qualifications"
  ],
  "proeth:temporalMarker": "Pre-case, foundational arrangement",
  "proeth:violatesObligation": [
    "Failure to establish structural safeguards preventing Firm A from serving conflicting clients",
    "Failure to ensure impartiality of the review and inspection function"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "City Engages Firm A"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Action_Firm_A_Accepts_Developer_Clients_Concurrently",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline all private developer engagements within the city jurisdiction for the duration of the city consulting contract",
    "Accept developer clients only for project types or geographic zones outside the city\u0027s oversight authority",
    "Disclose the dual relationship to the city and to each developer client in writing, and implement internal screening procedures with independent review of any submission from a Firm A developer client"
  ],
  "proeth-scenario:characterMotivation": "Firm A sought to maximize revenue by capitalizing on its established presence in the local market. Serving both the city and private developers within the same jurisdiction appeared to offer business synergies \u2014 local knowledge, existing relationships, and economies of scale \u2014 making simultaneous representation commercially attractive.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining developer work eliminates the conflict entirely; Firm A foregoes local private revenue but preserves its integrity as the city\u0027s impartial agent and avoids all subsequent ethical violations.",
    "Limiting private work to outside the city\u0027s jurisdiction allows business growth without creating a supervisory conflict; the city role and private role never intersect, though Firm A must monitor jurisdictional boundaries carefully.",
    "Disclosure and screening partially mitigate but do not eliminate the conflict; the city and developers are informed, and independent review reduces bias risk, but the financial incentive structure remains and the appearance of conflict persists, likely still falling short of the Code\u0027s requirements."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that a conflict of interest is structural, not merely situational. Even if Firm A intends to act impartially, the dual relationship creates an irreducible appearance of bias and places the firm in a position where financial incentives systematically skew toward leniency. Students learn that intent does not neutralize structural conflict.",
  "proeth-scenario:ethicalTension": "Firm A\u0027s professional duty of loyalty to each client (the city and each developer) conflicts directly when the same firm must objectively review, inspect, and potentially reject the work of clients who pay it fees. Financial self-interest in retaining developer clients competes with the obligation to render impartial engineering judgment on their submissions.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Impartiality of engineering inspections; safety of projects that may receive preferential treatment; fairness to developers who are not Firm A clients and may face stricter scrutiny; Firm A\u0027s professional license and reputation; public confidence in the regulatory process.",
  "proeth:description": "Firm A made an ongoing, deliberate decision to simultaneously accept private developer clients within the same city for which it serves as consulting engineer, creating a structural dual-loyalty arrangement. This placed Firm A in the position of reviewing and inspecting work from the same class of clients it also serves professionally.",
  "proeth:foreseenUnintendedEffects": [
    "Divided loyalty between city client and private developer clients",
    "Potential appearance of favoritism in review and inspection outcomes",
    "Risk that developer clients receive less rigorous independent inspection than they require"
  ],
  "proeth:fulfillsObligation": [
    "Technically providing contracted engineering services to multiple clients"
  ],
  "proeth:guidedByPrinciple": [
    "Avoidance of conflict of interest",
    "Faithful agency to each client",
    "Public safety and welfare"
  ],
  "proeth:hasAgent": "Firm A (private consulting engineering firm, principal decision-makers)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Financial self-interest and business expansion vs. undivided professional loyalty to the city",
    "proeth:resolutionReasoning": "Firm A resolved the conflict in favor of financial self-interest, accepting dual engagements without structural safeguards, contrary to the ethical standard reaffirmed by the Board"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Expand revenue base by serving both the city and private developers within the same jurisdiction",
  "proeth:requiresCapability": [
    "Engineering design and inspection",
    "Conflict of interest identification and management",
    "Client relationship management across multiple engagements"
  ],
  "proeth:temporalMarker": "Ongoing, concurrent with city engagement",
  "proeth:violatesObligation": [
    "Duty of loyalty to the city as primary client (NSPE Code Section II.4.d)",
    "Obligation to disclose conflicts of interest to all affected clients",
    "Obligation to avoid situations where self-interest divides professional loyalty",
    "Duty to represent the separate and differing interests of each client adequately",
    "Obligation not to accept compensation from multiple parties on the same project without full disclosure and consent"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Firm A Accepts Developer Clients Concurrently"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Event_Ordinance_Establishes_Mandatory_Review",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does the city bear ethical responsibility for creating a regulatory structure that enables Firm A\u0027s conflict of interest, even if the city acted in good faith?",
    "At what point in the ordinance\u0027s design could an ethically vigilant engineer have flagged the conflict-of-interest risk to city officials?",
    "How should a city structure developer-funded engineering review to preserve impartiality while still achieving cost efficiency?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "City officials feel satisfied with an efficient regulatory solution; Firm A principals likely experience quiet satisfaction at secured revenue stream; developers feel constrained and financially burdened; public remains largely unaware of the structural conflict being created",
  "proeth-scenario:ethicalImplications": "Reveals how institutional arrangements can structurally compromise professional independence before any individual makes a blameworthy choice; highlights the engineer\u0027s obligation to advise clients (including municipal clients) against regulatory designs that undermine public trust; surfaces tension between administrative efficiency and structural impartiality",
  "proeth-scenario:learningMoment": "Illustrates how structural conflicts of interest can be embedded at the institutional/regulatory level before any individual ethical violation occurs; students should recognize that ethical problems often originate in system design, not just individual choices",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "city_government": "Gains streamlined review process but inadvertently creates a structural conflict of interest it is responsible for overseeing",
    "developers": "Lose freedom to choose their own reviewers; face mandatory cost obligations to an entity that may also be their design consultant",
    "engineering_profession": "Professional ethical norms around independence are structurally undermined by the ordinance\u0027s design",
    "firm_a": "Gains captive revenue stream and institutional authority, increasing incentive to exploit dual-role position",
    "public": "Nominally protected by review process, but impartiality of that review is structurally compromised from inception"
  },
  "proeth:activatesConstraint": [
    "Conflict_of_Interest_Monitoring_Constraint",
    "Public_Trust_Preservation_Constraint",
    "Engineer_Impartiality_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/177#Action_City_Engages_Firm_A",
  "proeth:causesStateChange": "Firm A\u0027s role transitions from discretionary consultant to mandatory gatekeeper; all developers seeking city approval must now fund and engage Firm A for review, structurally embedding a potential conflict of interest into the regulatory framework",
  "proeth:createsObligation": [
    "City_Obligation_To_Ensure_Impartial_Review",
    "Firm_A_Obligation_To_Disclose_Potential_Conflicts",
    "Firm_A_Obligation_To_Serve_Public_Interest_As_City_Agent"
  ],
  "proeth:description": "The city formally enacts an ordinance requiring developers to fund engineering review and inspection services exclusively through Firm A, creating a mandatory dependency relationship. This legal instrument transforms an optional consulting arrangement into a compulsory one with city-backed authority.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Initial phase \u2014 prior to Firm A accepting developer clients",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Ordinance Establishes Mandatory Review"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Event_Dual-Role_Conflict_Materializes",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does Firm A\u0027s conflict of interest require proof of actual biased decisions to constitute an ethical violation, or is the structural conflict itself sufficient?",
    "What obligations does Firm A have at the moment it first accepts a developer client \u2014 before any review decisions are made?",
    "If a developer client receives a favorable review from Firm A, how could anyone distinguish legitimate approval from conflicted approval?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Firm A principals may rationalize the arrangement as efficient or mutually beneficial; developer clients may feel reassured by the familiarity but are unaware of compromised oversight; city officials may be oblivious to the operational conflict; public has no visibility into the compromised review process",
  "proeth-scenario:ethicalImplications": "Reveals the distinction between actual bias and structural conflict; highlights that Section II.4.d is violated by the existence of the conflict, not only by its exercise; surfaces the engineer\u0027s duty to protect the integrity of public oversight processes even when serving private clients",
  "proeth-scenario:learningMoment": "Demonstrates that a conflict of interest is not merely theoretical \u2014 it becomes an active ethical violation the moment the conflicting roles are simultaneously occupied, regardless of whether biased decisions have yet been made; students should understand that the appearance of impropriety is itself a violation",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Its mandatory review process is compromised; city may be exposed to liability if deficient work is approved; public trust in city oversight is at risk",
    "competing_engineering_firms": "Disadvantaged by inability to offer the same \u0027streamlined\u0027 review that Firm A can provide to its own clients",
    "developer_clients": "Receive potentially biased (favorable) reviews, creating short-term advantage but long-term liability if projects are later found non-compliant or unsafe",
    "firm_a": "Faces professional ethics violation exposure; financial incentive to approve own clients\u0027 work creates bias risk; reputation and licensure at risk if conflict is investigated",
    "public": "Projects may be approved that do not meet standards, creating safety and quality risks in built environment"
  },
  "proeth:activatesConstraint": [
    "Section_II_4_d_Conflict_of_Interest_Prohibition",
    "Engineer_Impartiality_Constraint",
    "Dual_Role_Incompatibility_Constraint",
    "Public_Trust_Preservation_Constraint",
    "Full_Disclosure_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/177#Action_Firm_A_Accepts_Developer_Clients_Concurrently",
  "proeth:causesStateChange": "Every project in which Firm A serves as both designer/inspector for a developer AND as the city\u0027s mandatory review authority becomes an active conflict-of-interest situation; the independence of the city\u0027s review process is compromised for all such projects",
  "proeth:createsObligation": [
    "Firm_A_Obligation_To_Disclose_Conflict_To_City",
    "Firm_A_Obligation_To_Disclose_Conflict_To_Developer_Clients",
    "Firm_A_Obligation_To_Recuse_From_Reviewing_Own_Clients_Work",
    "City_Obligation_To_Investigate_Impartiality_Of_Review_Process"
  ],
  "proeth:description": "The structural conflict of interest becomes an active reality when Firm A simultaneously holds authority as the city\u0027s mandatory review engineer and accepts private developer clients whose work it must review. The latent conflict created by the ordinance is now operationally present in every project where Firm A serves both roles.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "Concurrent with Firm A Accepts Developer Clients \u2014 ongoing",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Dual-Role Conflict Materializes"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Event_Cost_Savings_Claim_Becomes_Marketing_Outcome",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Why is it ethically problematic for Firm A to offer cost savings based on its city role, even if the savings are real and developers benefit financially?",
    "How does Firm A\u0027s marketing strategy harm engineers who do not hold a public role \u2014 and is that harm ethically relevant?",
    "If a developer knowingly chooses Firm A because of its dual role, does that developer share any ethical responsibility for the conflict?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Firm A principals may feel entrepreneurially clever; developer clients feel they are getting a good deal; competing firms feel unfairly disadvantaged; city officials, if aware, would likely feel betrayed; the public, if aware, would feel that regulatory oversight has been commodified",
  "proeth-scenario:ethicalImplications": "Reveals the commodification of public trust as an ethical violation category; highlights that competitive advantage derived from a conflict of interest is itself a harm, not a neutral market outcome; surfaces the engineer\u0027s duty to ensure that public roles are not leveraged for private commercial gain",
  "proeth-scenario:learningMoment": "Illustrates that using a public engineering role as a marketing tool for private gain is a concrete, identifiable violation of Section II.4.d; students should understand that the harm is not only to specific clients but to the integrity of the entire regulatory system and the engineering profession\u0027s public trustworthiness",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Its regulatory credibility is being used as a commercial product without its knowledge or consent",
    "competing_engineering_firms": "Unable to compete on the same terms; market distortion created by Firm A\u0027s misuse of public authority",
    "developer_clients": "Immediate cost savings; potential long-term liability if projects are later scrutinized for compromised review",
    "firm_a": "Short-term financial gain; long-term exposure to ethics violations, license revocation, and reputational damage",
    "public": "Regulatory oversight is being treated as a commodity rather than a public trust function; safety and quality assurance may be compromised"
  },
  "proeth:activatesConstraint": [
    "Section_II_4_d_Conflict_of_Interest_Prohibition",
    "Engineer_Must_Not_Use_Public_Role_For_Private_Gain_Constraint",
    "Honest_Representation_To_Clients_Constraint",
    "Public_Trust_Preservation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/177#Action_Firm_A_Markets_City_Role_to_Developers",
  "proeth:causesStateChange": "Firm A\u0027s public role has been monetized as a private competitive advantage; the city\u0027s regulatory authority is being used as a marketing asset; prospective developer clients are being recruited on the basis of Firm A\u0027s conflicted position rather than its technical merit",
  "proeth:createsObligation": [
    "Firm_A_Obligation_To_Cease_Using_City_Role_As_Marketing_Tool",
    "Firm_A_Obligation_To_Disclose_Basis_Of_Cost_Savings_To_Prospective_Clients",
    "City_Obligation_To_Investigate_Misuse_Of_Consulting_Engineer_Role"
  ],
  "proeth:description": "Firm A\u0027s promise of 50% savings on inspection costs becomes a realized market outcome, as the dual-role arrangement structurally enables Firm A to offer lower costs to its developer clients by leveraging its city-engineer position. This outcome transforms an ethical conflict into a competitive market advantage.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Concurrent with and following Firm A Markets City Role to Developers",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Cost Savings Claim Becomes Marketing Outcome"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Event_BER_Precedent_Sequence_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the existence of twenty years of progressively refined BER precedent affect the moral culpability of Firm A\u0027s principals \u2014 does it make their conduct more or less blameworthy than if the standards had been newly established?",
    "What does the progressive refinement of dual-role conflict standards across five cases tell us about how the engineering profession identifies and responds to emerging ethical challenges?",
    "Should engineering firms be required to demonstrate awareness of relevant BER precedent as a condition of taking on public-private dual roles?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Retrospectively, Firm A principals should feel the weight of established precedent they cannot credibly claim ignorance of; BER members feel the satisfaction of applying consistent, well-developed standards; students of engineering ethics recognize the profession\u0027s serious and sustained engagement with these issues",
  "proeth-scenario:ethicalImplications": "Reveals that professional ethics is a living, developing body of knowledge that practitioners are obligated to follow; highlights the relationship between institutional precedent and individual moral responsibility; surfaces the question of whether ignorance of professional ethical standards is itself an ethical failing",
  "proeth-scenario:learningMoment": "Demonstrates that professional ethics standards are not static pronouncements but living, evolving interpretations developed through case-by-case reasoning; students should understand the role of precedent in professional ethics and why awareness of prior BER decisions is itself an ethical obligation for practicing engineers",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "board_of_ethical_review": "Its prior work is validated and given practical force in the present case",
    "engineering_educators": "Provided with a rich body of progressive case law for teaching ethical reasoning",
    "engineering_profession": "Demonstrates institutional maturity and seriousness in developing ethical standards over time",
    "firm_a": "Cannot claim the ethical standards were unclear or newly invented; the precedent sequence makes willful disregard more culpable",
    "public": "Benefits from a profession that has proactively developed standards to protect public interest in oversight integrity"
  },
  "proeth:activatesConstraint": [
    "Precedent_Binding_Interpretive_Constraint",
    "Section_II_4_d_Conflict_of_Interest_Prohibition",
    "Engineer_Awareness_Of_Professional_Standards_Constraint"
  ],
  "proeth:causesStateChange": "The ethical landscape governing dual-role conflicts is now well-established and publicly available; any engineering firm operating in a dual-role capacity after 1982 cannot claim ignorance of the applicable standards; the Board\u0027s analysis of Firm A\u0027s conduct is constrained to apply this accumulated precedent",
  "proeth:createsObligation": [
    "Engineering_Firms_Obligation_To_Know_And_Apply_BER_Precedent",
    "Board_Obligation_To_Apply_Precedent_Consistently_In_Present_Case"
  ],
  "proeth:description": "A historical sequence of Board of Ethical Review decisions (BER Cases 62-7, 74-2, 75-7, 67-12, 82-4) accumulates over two decades, progressively refining and strengthening the ethical standards applicable to dual-role conflicts in engineering practice. This body of precedent becomes the authoritative interpretive framework applied to Firm A\u0027s conduct.",
  "proeth:emergencyStatus": "low",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "1962\u20131982 \u2014 prior to and contextualizing the present case",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "BER Precedent Sequence Established"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#Event_Section_II_4_d_Violation_Confirmed",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "The BER\u0027s determination focuses on the structure of Firm A\u0027s arrangement rather than requiring proof of specific biased decisions \u2014 do you agree that structural conflict alone should constitute a violation, or should actual harm be required?",
    "What remedial steps should Firm A take beyond simply ceasing the marketing practice \u2014 and who should be responsible for ensuring those steps are taken?",
    "How should the city respond to the BER\u0027s determination \u2014 does the city bear any ethical or legal responsibility for having created the ordinance that enabled this situation?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Firm A principals face professional censure, reputational damage, and potential loss of contracts; developer clients may feel deceived about the legitimacy of the arrangement they were sold; city officials may feel embarrassed by their role in creating the enabling ordinance; the engineering profession feels its ethical standards have been vindicated; public trust in engineering oversight is partially restored by the determination",
  "proeth-scenario:ethicalImplications": "Reveals that professional ethics enforcement serves systemic functions beyond punishing individual wrongdoers \u2014 it protects the integrity of entire regulatory systems; highlights the distinction between technical compliance and ethical conduct; surfaces the question of institutional responsibility when regulatory design enables individual ethical violations; demonstrates the profession\u0027s self-governance function as a public trust obligation",
  "proeth-scenario:learningMoment": "Demonstrates the concrete professional consequences of conflict-of-interest violations; shows how the BER applies accumulated precedent to reach determinations; illustrates that Section II.4.d is not merely aspirational but enforceable; students should understand that the violation lies in the structure of the arrangement, not only in provable instances of biased decision-making",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "city": "Must review the ordinance structure that enabled the conflict; may need to retain a different firm for review services or implement conflict-of-interest safeguards",
    "competing_firms": "Unfair competitive advantage enjoyed by Firm A is formally condemned; level playing field partially restored",
    "developer_clients": "Must reassess their relationship with Firm A; may need to obtain independent review of previously approved work; face uncertainty about project compliance",
    "engineering_profession": "Code of Ethics is enforced and its relevance to real-world practice is demonstrated; BER precedent is strengthened for future cases",
    "firm_a": "Formal ethics violation on record; required to restructure or terminate dual-role arrangement; potential loss of developer clients; reputational and financial consequences; possible license disciplinary proceedings",
    "public": "Regulatory oversight integrity is affirmed; projects previously reviewed under the conflicted arrangement may warrant re-examination"
  },
  "proeth:activatesConstraint": [
    "Section_II_4_d_Conflict_of_Interest_Prohibition",
    "Professional_Discipline_Consequence_Constraint",
    "Engineer_Must_Cease_Violating_Conduct_Constraint",
    "Public_Trust_Restoration_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/177#Action_Firm_A_Markets_City_Role_to_Developers",
  "proeth:causesStateChange": "Firm A\u0027s conduct is formally classified as an ethics violation; the dual-role arrangement is declared incompatible with Section II.4.d absent full disclosure and consent; the marketing of the city role to private clients is declared impermissible; the case joins the body of BER precedent available for future reference",
  "proeth:createsObligation": [
    "Firm_A_Obligation_To_Cease_Dual_Role_Or_Fully_Disclose_And_Obtain_Consent",
    "Firm_A_Obligation_To_Stop_Marketing_City_Role_To_Private_Clients",
    "City_Obligation_To_Review_And_Restructure_Ordinance_Arrangement",
    "Professional_Body_Obligation_To_Enforce_Code_Violation"
  ],
  "proeth:description": "The Board of Ethical Review formally determines and reaffirms that Firm A\u0027s conduct \u2014 simultaneously serving as city review engineer and private design/inspection consultant to developers whose work it reviews, and marketing the cost savings of that dual role \u2014 constitutes a violation of Section II.4.d of the NSPE Code of Ethics. This determination is the culminating outcome of the case.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Conclusion of the BER\u0027s analysis \u2014 present case decision",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Section II.4.d Violation Confirmed"
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#CausalChain_98cacce3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The city made a deliberate decision to retain Firm A, a private consulting engineering firm, to provide engineering review and inspection services \u2014 a role that, when combined with Firm A\u0027s concurrent acceptance of developer clients, caused the structural conflict of interest to become an active reality when Firm A simultaneously holds authority over both sides of the review relationship.",
  "proeth:causalSequence": [
    {
      "proeth:description": "City retains Firm A as its consulting engineer for development review and inspection, granting it quasi-public authority",
      "proeth:element": "City Engages Firm A",
      "proeth:step": 1
    },
    {
      "proeth:description": "City enacts ordinance requiring developers to fund Firm A\u0027s review services, embedding Firm A structurally between city authority and developer compliance",
      "proeth:element": "Ordinance Establishes Mandatory Review",
      "proeth:step": 2
    },
    {
      "proeth:description": "Firm A simultaneously accepts private developer clients within the same jurisdiction it reviews on behalf of the city",
      "proeth:element": "Firm A Accepts Developer Clients Concurrently",
      "proeth:step": 3
    },
    {
      "proeth:description": "Firm A now holds review authority over entities that are also its private clients, creating an irreconcilable conflict of interest",
      "proeth:element": "Dual-Role Conflict Materializes",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER formally determines this structural arrangement violates NSPE Code Section II.4.d prohibiting engineers from serving conflicting interests",
      "proeth:element": "Section II.4.d Violation Confirmed",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "City Engages Firm A",
  "proeth:counterfactual": "Had the city retained a firm with no private developer clients, or imposed contractual prohibitions on concurrent private work, the dual-role conflict would not have materialized regardless of the ordinance\u0027s existence",
  "proeth:effect": "Dual-Role Conflict Materializes",
  "proeth:necessaryFactors": [
    "City\u0027s decision to delegate engineering review authority to a private firm",
    "Ordinance establishing mandatory developer-funded review (creating the dual-authority structure)",
    "Firm A\u0027s concurrent acceptance of private developer clients within the same jurisdiction",
    "Absence of contractual or ethical safeguards prohibiting concurrent private client relationships"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "City (as contracting authority) and Firm A (as accepting party) \u2014 shared",
  "proeth:sufficientFactors": [
    "City delegation of public review authority + Firm A\u0027s simultaneous private developer relationships + no conflict-of-interest controls = active structural conflict",
    "The combination of public authority and private client interest in the same geographic and regulatory domain was alone sufficient to materialize the conflict"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#CausalChain_eda26eb1",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm A made an ongoing, deliberate decision to simultaneously accept private developer clients within the same jurisdiction where it held public review authority, causing the structural conflict of interest to become an active reality when Firm A simultaneously holds authority over both sides of the review relationship.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm A makes ongoing deliberate decisions to accept private developer clients in the same jurisdiction where it holds city review authority",
      "proeth:element": "Firm A Accepts Developer Clients Concurrently",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm A uses its city engineer position as a marketing tool, explicitly linking its public authority to private client value \u2014 deepening the conflict",
      "proeth:element": "Firm A Markets City Role to Developers",
      "proeth:step": 2
    },
    {
      "proeth:description": "The combination of public authority and private client relationships creates an active, irreconcilable conflict of interest",
      "proeth:element": "Dual-Role Conflict Materializes",
      "proeth:step": 3
    },
    {
      "proeth:description": "The dual-role structure produces the marketed 50% cost savings, financially rewarding the conflicted arrangement and entrenching it",
      "proeth:element": "Cost Savings Claim Becomes Marketing Outcome",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER confirms the conduct violates the prohibition on serving conflicting interests, with the concurrent client acceptance identified as the operative ethical breach",
      "proeth:element": "Section II.4.d Violation Confirmed",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Firm A Accepts Developer Clients Concurrently",
  "proeth:counterfactual": "Had Firm A declined all private developer clients within the jurisdiction, the dual-role conflict would not have materialized even with the city engagement intact",
  "proeth:effect": "Dual-Role Conflict Materializes",
  "proeth:necessaryFactors": [
    "Firm A\u0027s volitional acceptance of private developer engagements in the same jurisdiction",
    "Firm A\u0027s existing retention as city engineer with review and approval authority",
    "Developer clients being subject to the very review process Firm A administered"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm A",
  "proeth:sufficientFactors": [
    "Firm A holding city review authority + accepting private clients subject to that authority = sufficient to constitute a conflict under Section II.4.d",
    "No additional harm or adverse decision needed \u2014 the structural relationship itself was sufficient to trigger the ethical violation"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#CausalChain_eb1817b0",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm A made a deliberate decision to openly use its position as the city\u0027s engineer as a marketing tool, promising developers cost savings \u2014 a promise that became a realized market outcome as the dual-role structure enabled Firm A to deliver the claimed 50% savings on inspection costs, financially entrenching the conflicted arrangement.",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm A explicitly uses its city engineer position as a competitive marketing advantage, promising 50% inspection cost savings",
      "proeth:element": "Firm A Markets City Role to Developers",
      "proeth:step": 1
    },
    {
      "proeth:description": "Developers, attracted by the cost savings promise, engage Firm A as their private consultant \u2014 completing the dual-client relationship",
      "proeth:element": "Firm A Accepts Developer Clients Concurrently",
      "proeth:step": 2
    },
    {
      "proeth:description": "The marketed relationship becomes operational: Firm A simultaneously reviews developer projects in its city role while serving those developers privately",
      "proeth:element": "Dual-Role Conflict Materializes",
      "proeth:step": 3
    },
    {
      "proeth:description": "The promised 50% savings materialize as a realized outcome, financially validating and entrenching the conflicted dual-role structure",
      "proeth:element": "Cost Savings Claim Becomes Marketing Outcome",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER identifies the marketing of the city role as evidence of knowing exploitation of the conflict, reinforcing the ethical violation finding",
      "proeth:element": "Section II.4.d Violation Confirmed",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Firm A Markets City Role to Developers",
  "proeth:counterfactual": "Without Firm A marketing its city role, developers would not have engaged Firm A specifically to exploit the dual-role cost advantage; the savings outcome was contingent on the marketing action activating developer demand",
  "proeth:effect": "Cost Savings Claim Becomes Marketing Outcome",
  "proeth:necessaryFactors": [
    "Firm A\u0027s deliberate use of its city engineer role as a marketing instrument",
    "The ordinance structure requiring developers to pay for review (creating the cost baseline against which savings were measured)",
    "Firm A\u0027s actual ability to influence or streamline review processes by virtue of holding both roles",
    "Developer willingness to engage Firm A based on the cost savings promise"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm A",
  "proeth:sufficientFactors": [
    "Marketing of city role + ordinance-created cost structure + Firm A\u0027s dual-role leverage = sufficient to produce the realized cost savings outcome",
    "The marketing action transformed a latent conflict into an active commercial advantage, making the savings claim self-fulfilling"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#CausalChain_3f48efe3",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A historical sequence of Board of Ethical Review decisions (BER Cases 62-7, 74-2, 75-7, 67-12, 82-4) established and progressively reinforced the ethical standards against which Firm A\u0027s conduct was measured, providing the doctrinal foundation upon which the BER formally determined and reaffirmed that Firm A\u0027s conduct violated Section II.4.d.",
  "proeth:causalSequence": [
    {
      "proeth:description": "BER establishes foundational precedent that simultaneous retention by conflicting clients violates Section II.4.d",
      "proeth:element": "Engineer Serves Dual Clients Simultaneously (BER 62-7)",
      "proeth:step": 1
    },
    {
      "proeth:description": "BER extends the dual-role prohibition to the specific context of statutory municipal engineers accepting private roles \u2014 directly analogous to Firm A\u0027s situation",
      "proeth:element": "Municipal Engineer Accepts Private Firm Role (BER 74-2)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Cases 75-7, 67-12, and 82-4 further refine the standards, establishing both the violation pattern and the inadequacy of partial mitigations (abstention, withholding) when the structural conflict is not eliminated",
      "proeth:element": "BER Precedent Sequence Established",
      "proeth:step": 3
    },
    {
      "proeth:description": "Firm A\u0027s conduct replicates the fact patterns addressed in the precedent sequence, triggering application of established standards",
      "proeth:element": "Dual-Role Conflict Materializes",
      "proeth:step": 4
    },
    {
      "proeth:description": "BER applies the accumulated precedent to Firm A\u0027s conduct and formally confirms the violation, reaffirming the doctrinal line established across prior cases",
      "proeth:element": "Section II.4.d Violation Confirmed",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "BER Precedent Sequence Established",
  "proeth:counterfactual": "Without the established BER precedent sequence, the violation finding would lack authoritative doctrinal grounding; however, the underlying conduct would remain ethically problematic \u2014 the precedent sequence confirmed rather than created the violation",
  "proeth:effect": "Section II.4.d Violation Confirmed",
  "proeth:necessaryFactors": [
    "Prior BER cases establishing that dual-role conflicts violate Section II.4.d (Cases 62-7, 74-2)",
    "BER cases establishing acceptable mitigation measures such as abstention and withholding recommendations (Cases 75-7, 67-12)",
    "BER Case 82-4 synthesizing multiple simultaneous public and private roles as a confirmed violation pattern",
    "Firm A\u0027s conduct matching the fact patterns addressed in prior precedents"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm A (primary); BER (institutional standard-setter)",
  "proeth:sufficientFactors": [
    "The accumulated precedent from Cases 62-7 through 82-4, taken together, was sufficient to establish a clear and unambiguous standard against which Firm A\u0027s conduct could be measured and found violative",
    "Any single precedent case (particularly 62-7 or 74-2) addressing the core dual-client conflict was independently sufficient to provide the normative basis for the violation finding"
  ],
  "proeth:withinAgentControl": true
}

{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/177#",
    "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/177#CausalChain_177df6a6",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "The city formally enacts an ordinance requiring developers to fund engineering review and inspection services \u2014 creating the structural and financial framework within which Firm A\u0027s simultaneous public authority and private client relationships produced an active conflict of interest when Firm A simultaneously holds authority over both sides of the review relationship.",
  "proeth:causalSequence": [
    {
      "proeth:description": "City enacts ordinance creating developer-funded mandatory engineering review, establishing the regulatory and financial structure",
      "proeth:element": "Ordinance Establishes Mandatory Review",
      "proeth:step": 1
    },
    {
      "proeth:description": "City appoints Firm A to administer the ordinance-mandated review, conferring public authority over developer projects",
      "proeth:element": "City Engages Firm A",
      "proeth:step": 2
    },
    {
      "proeth:description": "Firm A accepts private developer clients who are subject to the ordinance-mandated review Firm A administers",
      "proeth:element": "Firm A Accepts Developer Clients Concurrently",
      "proeth:step": 3
    },
    {
      "proeth:description": "The ordinance\u0027s developer-funding mechanism means Firm A receives payment from the same developers whose projects it reviews \u2014 completing the structural conflict",
      "proeth:element": "Dual-Role Conflict Materializes",
      "proeth:step": 4
    },
    {
      "proeth:description": "The ordinance structure enables the 50% cost savings claim to be realized, as Firm A\u0027s dual role allows it to streamline review for its own private clients",
      "proeth:element": "Cost Savings Claim Becomes Marketing Outcome",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Ordinance Establishes Mandatory Review",
  "proeth:counterfactual": "Without the ordinance, Firm A would lack the formal public review authority that creates one pole of the conflict; alternatively, an ordinance with built-in conflict-of-interest provisions would have prevented the conflict from materializing even with Firm A\u0027s appointment",
  "proeth:effect": "Dual-Role Conflict Materializes",
  "proeth:necessaryFactors": [
    "Ordinance creating mandatory developer-funded review (establishing the financial and regulatory structure)",
    "Firm A\u0027s appointment as the reviewing engineer under the ordinance (conferring public authority)",
    "Firm A\u0027s concurrent private developer client relationships (creating the conflicting private interest)",
    "Absence of conflict-of-interest provisions within the ordinance itself"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "City (ordinance design); Firm A (exploitation of ordinance structure) \u2014 shared",
  "proeth:sufficientFactors": [
    "Ordinance structure + Firm A\u0027s dual roles = sufficient structural conflict, regardless of whether any specific biased decision was made",
    "The ordinance\u0027s developer-funding mechanism was particularly significant: it created a direct financial relationship between Firm A and the developers it was supposed to independently review"
  ],
  "proeth:withinAgentControl": true
}