OCE.6:5 - Archetypal Grounding – PumpWorks Assignment and Access
PW-ReleaseEvidenceIntegrationPosition exists and is vacant. PumpWorks considers Engineer-E27, an actual System classified under SystemsIntegrationEngineerSystemRole, for the recurring release-evidence integration contribution.
The organization declares PumpWorksReleaseIntegrationAppointment <: U.SystemRoleAssignment. Its required participants are the holder System, one assigned role-kind value from the PumpWorks integration-role domain, and the actual PW-ReleaseEvidenceIntegrationPosition. Its predicate requires an effective appointment decision issued under the named PumpWorks staffing authority, an in-force position, fixed participants, the required holder acceptance, and no current suspension. One occurrence is the maximal uninterrupted interval during which that predicate remains true for those participants.
Appointment decision PW-APPT-2026-17 becomes effective on 2026-10-01. The resulting assignment occurrence has Engineer-E27 as holder and SystemsIntegrationEngineerSystemRole as assigned kind. The decision record describes and supports the occurrence because this species gives the effective decision constitutive force; the file alone is not the assignment.
| Needed relation | Current result | Consequence |
|---|---|---|
| release-integration assignment | effective from 2026-10-01 under the species above | Holder and assigned kind are usable for the bounded contribution |
| test-rig access | effective rig-access occurrence under the admitted PumpWorks rig-access predicate for the named rig and release window after provisioning evidence | Integration Work may use the rig within that scope; licence or account evidence outside the interval does not establish access during it |
| provider-artifact repository access | decided but not effective because provider identity federation has not completed | Work entry remains blocked for provider-artifact integration; Administration/security owns the provisioning return |
| release-evidence coordination responsibility | source text says “responsible”, but no admitted predicate and participants are current | Return missing-governor; do not convert the assignment or position expectation into a responsibility occurrence |
| safety-evidence acceptance authority | the direct safety-evidence-acceptance authority relation obtains for another named Safety holder under its own predicate and basis | Engineer-E27 coordinates evidence and cannot issue the acceptance result |
| release authority | the direct release-authority relation obtains for the release director under its own predicate and basis | The integration assignment supplies no release decision power |
| holder capability | current evidence supports the required integration Work envelope except provider-tool use | HCD or a supervised trial can address the capability gap without changing the effective appointment |
For the repository-access action alone, the existing appointment and an adequate service instruction are sufficient inputs to ADM.2. Administration identifies the eligible requester and decision holder through ADM.2. The applicable grant or ADM.8 establishes whether the intended provisioning action is permitted. The provider supplies the federation result or reports the obstacle to access. Repeating all appointment work would add delay without helping that action. Successful provision would settle access within its returned scope; provider-tool capability remains a separate condition for integration.
Now suppose federation can be completed only after the booked rig window ends. The access owner and rig owner can each return a correct result, yet those results do not jointly enable provider-artifact integration in the planned interval. OCE.6’s coordination compares the conditions against that one contribution and returns a new-window question to the rig owner and a corresponding access-window question to Administration/security. The result may be a compatible later window, a supported alternative arrangement, or no available window. Until then the appointment remains effective, the independently supported electrical-evidence preparation may continue under its own conditions, and provider-artifact integration remains blocked. The coordination does not extend a booking or grant access. If the current service case already obtains and reconciles these answers, reuse it rather than opening a parallel OCE case.
The result supplied to OCE.9 contains one effective assignment, one effective rig-access relation, one pending provider-access relation, two separately held authority relations, a missing responsibility governor, and the bounded capability gap. Return the authorized holder/resource-assignment result to ADM.2 for the Administration work that depends on it.
OCE.6:5.1 - Transfer Probes
| Setting | Reusable move | Required return or changed content |
|---|---|---|
| public-hospital emergency flow | Use the applicable appointment or shift-assignment species, or define it if it is missing, recover licensed holder, clinical authority, access, equipment, and current interval | Statutory authority, licensure, labor, fatigue, privacy, safety, and bed/equipment availability can each block entry; verify the required conditions from their current evidence rather than the HR roster alone |
| distributed standards association | Use an applicable bylaw- or election-sensitive assignment species, or define it if needed for a volunteer position and recover publication, ballot, repository, and financial access | Employer assignments, volunteer acceptance, elected term, member authority, several time zones, and employer permission remain separate; no executive staffing predicate is imported |