Advisory Scope Completeness Constraint

@prefix core: <http://proethica.org/ontology/core#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix pcsh: <http://proethica.org/shapes/core#> . @prefix proeth: <http://proethica.org/ontology/intermediate#> . @prefix proeth-prov: <http://proethica.org/provenance#> . @prefix prov: <http://www.w3.org/ns/prov#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix sh: <http://www.w3.org/ns/shacl#> . @prefix skos: <http://www.w3.org/2004/02/skos/core#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . proeth:AdvisoryScopeCompletenessConstraint a owl:Class ; rdfs:label "Advisory Scope Completeness Constraint" ; proeth:affectedStakeholders "Client", "Engineer", "Funding Agency", "Public" ; proeth:confidence "0.82" ; proeth:constraintType "ethical" ; proeth:flexibility "hard" ; proeth:mitigationStrategies "Disclose any personal interest that might influence option selection", "Document the basis for any option excluded from analysis", "Present all approved or available options within the advisory scope" ; proeth:textReferences "Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options.", "Under the proposed funding source, there are four approved project delivery methods: Design-Bid-Build, Construction-Management-at-Risk, Fixed-Price-Design-Build, and Progressive-Design-Build." ; proeth:violationImpact "Client makes uninformed decisions based on incomplete information, engineer breaches fiduciary duty, potential disciplinary action for ethics violation" ; proeth-prov:discoveredInCase 14 ; proeth-prov:discoveredInPass 2 ; proeth-prov:discoveredInSection "facts" ; proeth-prov:firstDiscoveredAt "2026-06-04T08:45:47.831992+00:00"^^xsd:dateTime ; proeth-prov:firstDiscoveredInCase 14 ; proeth-prov:matchConfidence 0.72 ; proeth-prov:matchReasoning "The selective omission of options is driven by a conflict of interest and partially maps to Conflict of Interest Avoidance. However, the specific mechanism here is the completeness of advisory disclosure rather than merely the existence of a conflict, making this a variant that warrants a distinct class. The closest existing class is Conflict of Interest Avoidance but it does not capture the affirmative duty to present all options." ; proeth-prov:matchedOntologyClass <http://proethica.org/ontology/concepts#Conflict_of_Interest_Avoidance> ; proeth-prov:matchedOntologyLabel "Conflict of Interest Avoidance (Constraint)" ; proeth-prov:matchesExisting true ; proeth-prov:sourceText "Engineer A prepared a summary memo to City B Administrator and only identified Design-Bid-Build and Progressive-Design-Build as viable project delivery options." ; rdfs:comment "Ethical constraint requiring that an engineer providing advisory services to a client present all materially relevant options, methods, or alternatives within the scope of the advisory request, prohibiting selective disclosure that omits options the client is entitled to consider, particularly when the omission serves the engineer's own interests." ; rdfs:subClassOf proeth:EthicalConstraint, proeth:InviolableConstraint ; skos:definition "Ethical constraint requiring that an engineer providing advisory services to a client present all materially relevant options, methods, or alternatives within the scope of the advisory request, prohibiting selective disclosure that omits options the client is entitled to consider, particularly when the omission serves the engineer's own interests." ; skos:scopeNote "[Conflict_of_Interest_Avoidance] Constraint established by ethics code provisions" ; prov:generatedAtTime "2026-06-04T08:45:47.831992+00:00"^^xsd:dateTime ; prov:wasAttributedTo "Case 14 Extraction", "claude-sonnet-4-6" . pcsh:CaseAnnotationShape a sh:NodeShape ; rdfs:label "Shared per-case annotation schema (all nine components)"@en ; rdfs:comment "The cross-component annotation fields on committed case individuals: proeth:confidence (extraction confidence, decimal; all components except Action, whose Step-3 contract carries no confidence field), proeth:textReferences (verbatim supporting quotes, universal), proeth-prov sourceText (the source snippet, on the Step-1/2 provenance layers; Step-3 A/E individuals ground via textReferences only), and the involvement gloss (proeth:caseInvolvement on role individuals, proeth:caseContext on obligation, capability, and constraint individuals). Values are per-individual; the fields do not individuate any type."@en ; sh:property [ sh:description "Extraction confidence for this individual (0 to 1)." ; sh:name "confidence" ; sh:order 1 ; sh:path proeth:confidence ], [ sh:description "Verbatim case quotes supporting this individual." ; sh:name "text references" ; sh:order 2 ; sh:path proeth:textReferences ], [ sh:description "How this individual figures in the case narrative (role individuals; the same text is routed into rdfs:comment)." ; sh:name "case involvement" ; sh:order 3 ; sh:path proeth:caseInvolvement ], [ sh:description "Grounding context in this case (obligation, capability, and constraint individuals)." ; sh:name "case context" ; sh:order 4 ; sh:path proeth:caseContext ] ; sh:targetClass core:Action, core:Capability, core:Constraint, core:Event, core:Obligation, core:Principle, core:Resource, core:Role, core:State . pcsh:ConstraintDefinitionShape a sh:NodeShape ; rdfs:label "Constraint definition schema (type-level, descriptive, field contract)"@en ; rdfs:comment "What individuates a constraint TYPE: the boundary it states (boundary_type, which drives the subClassOf typing into one of the ten closed boundary-type classes) and the source provision that establishes it. The per-case severity and applicability, the agent it limits, and the action it bounds are per-individual and declared on ConstraintPropertyShape, mirroring the R/P/O/S/Rs/Ca Definition/Property split and the constraint scopeNote (the TYPE is the prohibition plus its source provision; the constrained party, per-occasion applicability, and any exception attach to the case individual). Descriptive only (no validation result); the routing input is the constraint_type schema field (the boundaryType property is its shape-path anchor), not stored as a literal."@en ; sh:property [ sh:description "The controlled boundary type, which drives the subClassOf typing into one of the ten closed boundary-type classes: LegalConstraint, RegulatoryConstraint, ResourceConstraint, CompetenceConstraint, JurisdictionalConstraint, ProceduralConstraint, EthicalConstraint, SafetyConstraint, ConfidentialityConstraint, TemporalConstraint. The prohibition/boundary content that individuates the type. A routing input, not stored as a literal." ; sh:name "boundary type" ; sh:order 1 ; sh:path proeth:boundaryType ], [ pcsh:informationalOnly true ; sh:description "The source CodeProvision that establishes the constraint, via the establishedBy edge. The second type-individuating coordinate: per the scopeNote a constraint type is the boundary it states plus its source provision. Range: CodeProvision." ; sh:name "established by" ; sh:order 2 ; sh:path core:establishedBy ] ; sh:targetClass core:Constraint . pcsh:ConstraintPropertyShape a sh:NodeShape ; rdfs:label "Constraint per-case schema (individual data, non-definitional)"@en ; rdfs:comment "What a given constraint INDIVIDUAL is described by in a specific case: its per-occasion severity and applicability window, the agent whose conduct it limits, and the action it bounds. These do NOT individuate the constraint TYPE (that is ConstraintDefinitionShape, keyed on the boundary it states and its source provision); their values are per-case, asserted on the individual. Descriptive only."@en ; sh:property [ sh:description "The severity of the constraint in this case (critical, high, medium, low); a per-occasion assessment (Dennis severity ordering) that can differ across cases sharing the same boundary." ; sh:name "severity" ; sh:order 1 ; sh:path proeth:severity ], [ sh:description "The situational TRIGGER: the circumstances under which the prohibition applies in this case (the Dennis specification-by-context condition); temporalScope carries the durational window." ; sh:name "applicability condition" ; sh:order 2 ; sh:path proeth:applicabilityCondition ], [ sh:description "The agent whose conduct the constraint limits, via the outgoing constrainedEntity edge. Range: Agent." ; sh:name "constrained entity" ; sh:order 3 ; sh:path core:constrainedEntity ], [ sh:description "The durational WINDOW during which the boundary is in force in this case (e.g. for the duration of the engagement); applicabilityCondition carries the situational trigger under which it applies." ; sh:name "temporal scope" ; sh:order 4 ; sh:path proeth:temporalScope ], [ sh:description "The provision or authority string as extracted, kept verbatim on the individual; each dotted NSPE designation that resolves against the provision registry is also materialized as the establishedBy edge (a non-code source survives only in this literal)." ; sh:name "source" ; sh:order 5 ; sh:path proeth:source ], [ sh:description "The operative must-not clause, kept verbatim; mirrors skos:definition and is one of the narrative source fields the defeasibility harvest reads from committed TTLs." ; sh:name "constraint statement" ; sh:order 6 ; sh:path proeth:constraintStatement ] ; sh:targetClass core:Constraint .