Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:50:10 UTC

E.17.2:5.3 - Responsibility diagram and actual assignment

A responsibility-diagram episteme E concerns exact System H. Exact local reference r_allocation : U.ViewpointRef resolves exact P_allocation; EpistemeViewpointConformanceRelation(E,P_allocation) obtains.

Diagram cue. One box names MaintainerSystemRole@Plant. That spelling can help locate the plant-side definition; by itself it establishes neither an exact local system-role kind, an assigned-kind domain, a C.3.2 judgment, nor an assignment.

Classification-only claim. If a current claim says PumpUnit-3 counts as CoolingCirculatorSystemRole for exact CoolingCirculatorKindSignature-2 and PlantSlice-7, recover J(PumpUnit-3, CoolingCirculatorSystemRole, CoolingCirculatorKindSignature-2, PlantSlice-7) = true under C.3.2. No assignment is required.

Assignment claim. If a separate claim says admitted System S holds an assignment, first recover the exact local kind—here named MaintainerSystemRole—through C.3 and declare the exact assigned-kind domain—here named PlantMaintenanceSystemRoleKindDomain. The diagram cue identifies neither. Then recover exact RA : MaintenanceWorkAssignment <: U.SystemRoleAssignment under A.2.1, with S in HolderSystemSlot, PlantMaintenanceSystemRoleKindDomain as the declaration-local assigned-kind domain, and MaintainerSystemRole as RA’s assigned-kind value.

E can assert or describe RA without becoming RA. Any responsibility of S remains a separately governed direct claim.