@prefix core: . @prefix owl: . @prefix pcsh: . @prefix proeth: . @prefix proeth-prov: . @prefix prov: . @prefix rdfs: . @prefix sh: . @prefix skos: . @prefix xsd: . proeth:JointRecommendationDocumentationObligation a owl:Class ; rdfs:label "Joint Recommendation Documentation Obligation" ; proeth:confidence "0.78" ; proeth:derivedFromPrinciple "Complete Reporting Principle" ; proeth:enforcementLevel "prima_facie" ; proeth:monitoringCriteria "Written record of joint recommendations including technical findings, required improvements, and timeline submitted to the client before or at the time of the client decision" ; proeth:nspeReference "II.3.b, III.2.b" ; proeth:obligationType "disclosure" ; proeth:stakeholdersAffected "Client governing body", "General public", "Regulatory bodies" ; proeth:textReferences "Both Engineer A and Engineer B met with the MWC at a meeting sparsely attended by the public and recommended that the change in water source be substantially delayed until improvements could be completed.", "Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline." ; proeth:violationConsequences "Loss of evidentiary basis for regulatory escalation; weakened professional accountability record" ; proeth-prov:discoveredInCase 76 ; proeth-prov:discoveredInPass 2 ; proeth-prov:discoveredInSection "facts" ; proeth-prov:firstDiscoveredAt "2026-06-05T11:23:42.907966+00:00"^^xsd:dateTime ; proeth-prov:firstDiscoveredInCase 76 ; proeth-prov:matchConfidence 0.75 ; proeth-prov:matchReasoning "The joint documentation duty is a contextual variant of the existing Complete Technical Reporting Obligation, applied to the specific situation where two engineers jointly present findings and the documentation serves as the evidentiary basis for potential regulatory escalation. The core concept of complete and documented reporting is already captured." ; proeth-prov:matchedOntologyClass proeth:CompleteTechnicalReportingObligation ; proeth-prov:matchedOntologyLabel "Complete Technical Reporting Obligation" ; proeth-prov:matchesExisting true ; proeth-prov:sourceText "Engineer B, a consulting engineer retained by the MWC charged with evaluating water treatment needs for the change in water source, provided a report to Engineer A recommending extensive capital investments and a three-year timeline." ; rdfs:comment "Duty of engineers who jointly develop and present professional recommendations to a client or governing body to ensure that those recommendations, including the technical basis, timeline requirements, and safety rationale, are documented in writing so that the record is available for regulatory escalation if the client overrides the recommendations." ; rdfs:subClassOf proeth:DisclosureObligation ; skos:definition "Duty of engineers who jointly develop and present professional recommendations to a client or governing body to ensure that those recommendations, including the technical basis, timeline requirements, and safety rationale, are documented in writing so that the record is available for regulatory escalation if the client overrides the recommendations." ; skos:scopeNote "[CompleteTechnicalReportingObligation] Duty of an engineer preparing a technical report to include all relevant and pertinent technical information, including facts that may complicate or contradict the primary conclusions, so that the report supports informed review and interpretation by others." ; prov:generatedAtTime "2026-06-05T11:23:42.907966+00:00"^^xsd:dateTime ; prov:wasAttributedTo "Case 76 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:ObligationDefinitionShape a sh:NodeShape ; rdfs:label "Obligation definition schema (type-level, descriptive, field contract)"@en ; rdfs:comment "What individuates an obligation TYPE: its controlled NSPE category, which drives the subClassOf core:Obligation typing. The concrete duty statement and the temporal-scope/compliance-status literals are per-individual, as are the derivedFromPrinciple and obligatedParty edges; all are declared on ObligationPropertyShape, mirroring the Role/Principle Definition/Property split. Descriptive only (no validation result); obligation_type is a routing input, not stored as a literal."@en ; sh:property [ sh:description "The controlled NSPE obligation category, which drives the subClassOf core:Obligation typing: disclosure, safety, competence, confidentiality, reporting, collegial, attribution, legal, ethical." ; sh:name "obligation type" ; sh:order 1 ; sh:path proeth:obligationType ] ; sh:targetClass core:Obligation . pcsh:ObligationPropertyShape a sh:NodeShape ; rdfs:label "Obligation per-case schema (individual data, non-definitional)"@en ; rdfs:comment "What a given obligation INDIVIDUAL is described by in a specific case: the concrete duty it states, the principle it derives from and the party who bears it (both edges), and its temporal scope and compliance status. These do NOT individuate the obligation TYPE (that is ObligationDefinitionShape); their values are per-case, asserted on the individual. Descriptive only."@en ; sh:property [ sh:description "The concrete duty the obligation states (the operative 'shall' clause)." ; sh:name "obligation statement" ; sh:order 1 ; sh:path proeth:obligationStatement ], [ sh:description "The principle the obligation derives from, via the O->P derivedFromPrinciple edge (the P side of R->P->O). Range: Principle." ; sh:name "derived from principle" ; sh:order 2 ; sh:path core:derivedFromPrinciple ], [ sh:description "The agent who bears the obligation, via the obligatedParty edge. Range: Agent." ; sh:name "obligated party" ; sh:order 3 ; sh:path core:obligatedParty ], [ sh:description "When the obligation is in force (the period or condition of applicability)." ; sh:name "temporal scope" ; sh:order 4 ; sh:path proeth:temporalScope ], [ sh:description "Whether the obligation was met in the case: met, unmet, partial, or unclear." ; sh:name "compliance status" ; sh:order 5 ; sh:path proeth:complianceStatus ] ; sh:targetClass core:Obligation .