Part II - Design Organization Relations and Work Arrangements

OCE.4 - Design an Organization’s Contribution Architecture

Type: Method pattern Status: Eternal alpha

Primary working result: an inspectable contribution-architecture design: a decision and possible-future description recording selected specialization boundaries, contribution-relation specifications, acceptance and exception conditions, affected burdens, receiving decisions, and the evidence needed to establish which direct relations later obtain.

OCE.4:0 - Use This When

Use this pattern when an organization concept has been selected or narrowed, but its chart, topology, or operating-model label still does not say how contributions reach their receivers. Enter when specialization boundaries, supplied results, information use, decisions, services, resource access, or coordination must be designed before positions or assignments can be settled.

Begin with a compatible OCE.1 focus, OCE.2 current account, and OCE.3 concept comparison or equivalent content. Name any tolerated evidence gap and any gap that blocks design.

The first useful result is small: one organization concept, a few decision-bearing contribution-relation specifications, their intended suppliers and receivers, the selected specialization boundaries, and the conditions under which later Work may realize or reopen them.

Use C.30 directly when the question is only whether one actual or candidate structure is architecture-relevant. Use OCE.5 for position identity, OCE.6 for holder assignments and enabling relations, OCE.7 for paired product-or-service and organization architecture decisions, and OCE.9 for realization and organization-capability evidence.

OCE.4:0.1 - Working Distinctions

Name used here	Meaning
specialization boundary	A selected boundary between domains of organization contribution or Work for the current design use. Decide separately which organization units, positions, assignments, and authority relations are needed at that boundary.
contribution-relation specification	Possible-future design content naming an intended direct relation kind or predicate, supplier and receiver, result or preserved condition, applicability, acceptance or use condition, exception return, scope, horizon, and evidence need. The specified relation remains proposed until its obtaining conditions are met.
contribution relation occurrence	One obtaining occurrence of the admitted direct relation named by a specification or current account. Its predicate, participants, applicability, interval, and evidence must be recoverable independently of the design.
contribution structure	An actual `A.22` structure selecting obtaining contribution relation occurrences and their participants for one declared use. Describe a candidate contribution structure as possible-future content until the selected occurrences obtain. Information-use, decision, access, service, coordination, legal-entity, and Work structures can remain separate.
contribution architecture	The way selected structures organize the named organization for its intended contribution, qualified under `C.30`. Actual architecture requires the applicable subject relations and architecture relation to obtain; candidate or desired architecture remains claim or description content.
position-design need	A need to decide whether one or more expected contributions warrant a stable organization position. `OCE.5` makes that decision and, when warranted, defines the position.
acceptance condition	The condition under which a receiver can use or accept the supplied result for the named decision. State the condition in the specification or claim, then use the applicable predicate and evidence to test whether it is met.
exception and escalation relation	An obtaining direct relation for returning an unusable result, resolving a conflict, or issuing a decision when ordinary contribution cannot continue. Specify that relation explicitly when designing a possible future.
contribution-architecture decision	A decision selecting possible-future organization structures, relation specifications, constraints, and open refinements for later change Work. It does not make those structures or relations actual.

OCE.4:1 - Problem Frame

Organization design often begins with grouping: functions, products, customers, regions, programmes, professions, or platforms. Grouping helps attention, yet the organization contributes through relations that cross those groups. Evidence is supplied and used, decisions are issued and accepted, materials move, services are provided, resources are accessed, and exceptions return.

A contribution-architecture description makes intended relation specifications, any obtaining occurrences, and their receiving decisions visible while distinguishing proposed from actual relations. It may use several structures because activity grouping, decision representation, legal entities, information use, and service provision answer different questions. The design can then state which boundaries should change and which cross-boundary contributions must remain.

OCE.4:2 - Problem

A target chart can move boxes while preserving the failed contribution path. A topology can give every group a familiar label while leaving the result, receiver, acceptance condition, or exception owner unknown. A generic “interface” can hide that one boundary carries evidence supply, a separate release decision, resource access, provider service, and field information.

The design then cannot guide position definition or realization. Teams infer authority from placement, capability from staffing, and acceptance from handoff. When problems appear, nobody can tell whether the missing element is Work, an assignment, access, an authority relation, a contribution predicate, or evidence that the relation obtains.

OCE.4:3 - Forces

Force	Tension
Specialization	Concentrated knowledge and equipment can improve contribution, while every boundary creates coordination and return needs.
Stable ownership	Receivers need reliable contribution, while fixed boxes can preserve obsolete Work and authority assumptions.
Several structures	One picture is easy to communicate, while contribution, decision, access, service, legal, and Work structures need not coincide.
Participant knowledge	People performing Work and using its results can expose hidden relations, while participation does not transfer design authority.
Provider boundaries	External provision can add capability and scale, while contracts, access, recovery, evidence, and decision authority remain separate.
Realization	Designers need a usable possible-future account now; later Work may realize the relations, and observations can support claims that they obtain.

OCE.4:4 - Solution

Design from the intended contribution and the relations needed to produce, use, accept, and return results. Select the few structures that change the current decision. State possible-future crossings as contribution-relation specifications, then make a contribution-architecture decision that fixes only the boundaries and conditions later Work must realize.

Recognition is cheap: one selected organization concept whose result path cannot be stated from supplier to receiving decision is enough to enter. Assurance is relation-specific: each actual contribution, information-use, decision, service, access, material-transfer, or coordination claim needs its own predicate, participants, scope, window, and evidence.

OCE.4:4.0 - One bounded first design

For a small first use, keep the selected concept and already qualified constraints fixed and resolve one troublesome contribution crossing. Suppose a small engineering organization has the authority and participant inputs needed to decide how compatibility evidence reaches its release integrator. A short design note can state:

Electrical supplies a configuration-C7 compatibility-evidence package to Integration for Friday’s review. Each claimed interface must have a traceable source and test; Integration returns an unsupported claim to Electrical before evidence closure. The design decision keeps electrical expertise with Electrical and package assembly with Integration, using the agreed review time rather than merging the two specializations. Safety acceptance and release remain separate decisions. A missing source or an unworkable review burden reopens this design. Use the first package to test whether the planned supply and exception return actually work.

This is one bounded design result, not evidence that the supply relation already obtains. Reuse the supporting focus, current account, participant correction and decision basis instead of restating them. Add another structure, alternative or specialist return when it can change this decision; a missing authority or protection premise remains a blocker. The same short note can carry the needed content listed below. Elaborate the questions that remain open rather than turning this first use into a full-organization redesign.

OCE.4:4.1 - Pattern-Use Unfolding

Bind the design question. Name the organization, intended outside contribution, selected concept, decision subject, authority, horizon, affected Systems, and first receiving use of the result.
Recover the current relation basis. Carry forward current Work and direct-relation evidence from OCE.2, plus constraints, participants, assumptions, and burdens from OCE.3. Record unavailable or incompatible inputs explicitly.
Select structures by question. Choose contribution, Work, decision, information-use, material-transfer, service, access, coordination, legal-entity, or other structures only when each changes the design. Use process, project, and case viewpoints on the same Work to expose different Method, coordination, state, and authority constraints. Retain the account of obtaining occurrences unless new evidence warrants revision; keep proposed structures and crossings modal. Preserve differences among the selected structures when those differences matter to the decision.
Set specialization boundaries. Group contribution or Work where shared knowledge, equipment, evidence, decision, locality, customer, product, service, or provider conditions justify it. State the condition and the burden moved by each boundary.
Write contribution-relation specifications. For every decision-bearing crossing, name the intended direct relation kind or predicate, supplier and receiver Systems, result or preserved condition, applicability, acceptance or use condition, exception return, scope, horizon, and evidence need. Use “interface” only as an orientation label after this content is visible. Do not report an occurrence before its predicate is satisfied.
Obtain participant corrections. Use participant-facing views to test actual Work, burden, accessibility, safety, provider, and service-continuity assumptions. Record whose contribution changed the design and which material voice is missing.
Compare whole structures. Compare how each candidate handles intended contribution, coordination load, decision latency, evidence, scarce capability, resilience, provider dependence, affected Systems, reversibility, and change burden. Keep unlike characteristics separate unless a justified aggregation Method exists.
Make the architecture decision. Use C.32.PAD, C.11, or the applicable decision pattern for the claim being made. State selected structures, accepted losses, fixed constraints, open refinements, rejected alternatives, and reopen observations. Preserve modal status.
Return position and paired-architecture questions. Send stable expected-contribution and eligibility needs to OCE.5. Send organization/product-or-service correspondence pressure to OCE.7. Keep holder, authority, capability, and realization questions with their owners.
Specify realization evidence. Name which later Work and observations can show that each specified relation obtains, fails, or remains unresolved. Supply design constraints to OCE.9 without reporting organization capability.
Stop at contribution sufficiency. Return when affected practitioners can name the contribution path, boundaries, contribution-relation specifications, accepted burdens, open refinements, and observations that reopen the design.

The steps are a reasoning aid. Existing structures may be repaired, new boundaries may be tried, and participant evidence may reopen an earlier decision at any time.

OCE.4:4.2 - Record the Result

Result position	Required content
design boundary	Organization, contribution, concept, authority, horizon, first receiver, and affected Systems.
selected structures	Structure kind, constituents, occurrence refs when actual, modal structure or relation claims when proposed, declared use, and known losses.
specialization decisions	Boundary, reason, expected gain, burden moved, retained cross-boundary contribution, and open refinement.
contribution-relation specifications	Intended direct relation kind or predicate, supplier, receiver, result or preserved condition, applicability, acceptance/use, exception return, scope, horizon, and evidence need; occurrence ref only when independently established.
participant corrections	Participants sought, design change made, missing voice, burden or protection limit, and unresolved claim.
architecture decision	Selected option, fixed constraints, accepted losses, rejected or retained alternatives, modal or actual status, and decision basis.
downstream returns	Position needs, paired product/service questions, realization constraints, specialist results, and missing governors.
continuation	Realization observations, evidence windows, and the smallest event that reopens the decision.

OCE.4:4.3 - What Changes in Practice

Practitioners design the contribution path before finalizing boxes. Every stable boundary has a reason, every decision-bearing crossing has an explicit relation specification, and every target relation retains its modal status until its direct predicate is satisfied. Position, assignment, capability, authority, and provider questions remain available for their own decisions instead of being hidden in the chart.

OCE.4:5 - Archetypal Grounding – PumpWorks Contribution Architecture

PumpWorks continues from the OC-PW-STREAM-ENABLING concept. The current decision concerns weekly evidenced AI-inspection releases while field service continues. PumpWorks-EngineeringOrg is the organization; the proposed stream configuration and its relations remain possible-future content.

The selected design describes several proposed structures: contribution relations for supplying results to receiving decisions; decision relations that separate safety-evidence acceptance from release authorization; access relations for the test rig and model artifacts; provider-support service relations; and field-information relations for returning operating observations.

Proposed crossing	Contribution-relation specification	Acceptance, exception, and evidence need
Electrical → Release Integration	supply compatibility-evidence package for the named configuration	Integration can trace every claimed interface and test; unresolved mismatch returns to Electrical before evidence closure
Platform → Release Integration	provide qualified test environment and deployment service	Configuration and availability window match the release candidate; outage opens the fallback environment decision
AI provider → PumpWorks Integration	supply versioned model artifact and remote support under named access conditions	Provenance, compatibility, recovery, and access are present; provider supplies neither safety acceptance nor release authority
Release Integration → Safety	supply assembled evidence package and unresolved assumptions	Safety can evaluate the named release claim; rejection returns the exact missing or contradicted evidence
Safety → Release director	issue an evidence-acceptance result	Acceptance concerns the evidence question; the release director separately issues the release decision
Field Service → product and integration teams	provide incident and use-condition information	The report identifies product configuration and service episode; privacy and customer-use gaps return to their owners

The design groups recurring release-integration contribution without dissolving Electrical, Safety, platform, provider, or field-service specialization. Its specifications return a position-design need for stable release-evidence integration to OCE.5, a holder/access question for OCE.6, and a product-module/organization-boundary question for OCE.7.

The table describes proposed relations. In later realization, use OCE.9 to compare actual Work and independently evidenced relation occurrences with the design and determine whether a bounded organization-capability increment is supported.

OCE.4:5.1 - Transfer Probes

Setting	Reusable move	Required return or changed content
public-hospital emergency flow	Start from the patient-care contribution, separate clinical decision, diagnostic-information, transfer, access, escalation, and continuing-service structures	Use clinical rather than product-release terms; obtain statutory clinical-authority, labor, privacy, safety, bed-access, and Operations results from their owners
distributed standards association	Start from the standard-publication contribution, volunteer Work, editorial evidence, member decision, ballot, publication-service, and employer-resource relations	Use the association’s bylaws and elected authority; retain several employers, volunteer availability, publication, and finance conditions rather than assuming one employer hierarchy

These are hypothetical transfer probes of the design move. Adoption and benefit would require evidence from actual use.

OCE.4:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
chart completion	Every required contribution receives a box, so the design appears complete.	Trace direct results to receiving decisions and exception returns.
interface bundling	Several unlike relations become one line.	Name each direct predicate and use a visibly reduced orientation label only afterward.
symmetry preference	Similar product or customer groups receive identical organization units.	Preserve differences in Work, authority, evidence, capability, provider, and service conditions.
informal-relation erasure	Useful observed coordination disappears because policy does not name it.	Preserve the observed relation and decide whether to formalize, support, replace, or stop relying on it.
participation-as-approval	A workshop is treated as design authority or adoption.	Record the knowledge contribution and keep authority and realization separate.
future-as-current	The selected picture is called the new organization.	Keep possible relations in claim and decision content until direct evidence shows they obtain.

OCE.4:7 - Conformance Checklist

The organization, contribution, concept, authority, horizon, and first receiving use are explicit.
Each selected structure answers a declared question and states its losses.
Specialization boundaries name their gain and moved burden.
Every decision-bearing crossing has a contribution-relation specification naming the intended direct relation kind or predicate, supplier, receiver, result, conditions, acceptance/use, exception return, and evidence need.
“Interface” does not replace direct relation content.
Participant knowledge changes or challenges identifiable design content.
Contribution-relation specifications, modal architecture claims, and obtaining relation occurrences remain distinguishable.
Position, holder, assignment, capability, authority, product/service, and realization questions have explicit returns.
The decision states fixed constraints, open refinements, accepted losses, and reopen observations.

OCE.4:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
“Create product teams and define interfaces.”	Name the contribution and Work basis for each boundary, then write separate possible-future specifications for supplied-result, decision, information-use, access, service, and coordination relations.
“One owner per deliverable.”	Recover the result, receiver, acceptance decision, contributing Systems, authority, and exception path; choose an ownership predicate only when it is actually governed.
“Put everyone involved in one team.”	Select the smallest contribution-bearing boundaries and preserve scarce capability homes, independent acceptance, providers, and continuing service where they change the decision.
“The matrix has two reporting lines.”	State which contribution, decision, authority, access, or coordination relation each line is intended to represent.
“The architecture is now implemented.”	Compare actual Work and obtaining relations after change; retain the current item as decision and possible-future description until then.

OCE.4:9 - Consequences

The contribution-architecture design becomes inspectable before a chart is finalized. Position design can start from expected contributions, and realization can test independently obtaining relation occurrences against explicit specifications instead of visual conformity.

The cost is that one page may no longer contain the whole answer. Several structures and evidence returns may be needed, and an attractive topology can remain undecided when a provider, authority, access, safety, or service condition is missing.

OCE.4:10 - Rationale

An organization contributes through actual Systems, Work, and direct relation occurrences. Design-time specifications preserve why a proposed boundary exists without asserting that the relation already obtains, so later evidence can show whether the intended architecture was realized.

Several structures are expected. The activity arrangement, decision representation, legal entities, information use, access, and service provision can overlap without becoming one structure. Their non-isomorphism can expose a design risk rather than a modeling defect.

OCE.4:11 - SoTA-Echoing

OCE.4:11.1 - Current-Line Selection for Contribution Design

Comparison position	Selected result for practice
Current question	Which organization structures and possible-future direct-relation specifications should guide one contribution decision?
Selected current line	Treat organization design as several complementary questions—configuration, control, channelization, and coordination—then select only the structures that change this contribution decision. Bind proposed crossings to contribution and receiving use, and keep participant corrections and later occurrence evidence visible.
Serious alternative	Start from one chart, topology, operating-model template, or activity grouping and infer interfaces from adjacency.
When the alternative is sufficient	A single representation is enough for orientation when it makes no claim to settle direct relations, authority, acceptance, or realization and the underlying occurrences are already established elsewhere.
When the selected line changes action	If the representation cannot name the supplied result, receiver, acceptance or use, exception return, or an unlike structure that changes the decision, write relation specifications and compare the necessary structures before fixing boxes.
Reopen	Reconsider the selection when a representative contribution cannot be expressed, a serious alternative reaches the same decision with less modeling burden, or a current source changes the organization-design action.

OCE.4:11.2 - Source Contributions and Boundaries

Source line	Retained contribution	Use boundary
Current FPF `A.22`, `C.30`, `C.30.AD`, `C.32`, and `C.32.PAD`	Selected structures, actual versus modal architecture, candidate synthesis, descriptions, and decisions remain separate.	Use these distinctions to qualify the local design; derive specialization boundaries and contribution content from the organization’s working problem.
Joseph and Sengul, current organization-design review	Contemporary organization design uses complementary configuration, control, channelization, and coordination approaches; one representation or feature does not cover the field.	The review organizes research rather than selecting a local organization, relation predicate, or architecture decision.
Albert, organization-structure perspectives	Activity arrangement, decision representation, and legal-entity perspectives can expose different design consequences.	Select the local organization and any additional perspective needed for its design question.
Grote et al., contribution-based engineering role modeling	Required contributions and stakeholder evidence can expose organization-specific contribution bundles and gaps.	The evidence covers three industrial cases and one workshop/clustering Method. Test transfer beyond those cases; decide local positions and assignments separately.
Fraccaroli, Zaniboni, and Truxillo, work-design review	Work characteristics, technology, diversity, and affected-person outcomes belong in design.	Supply the target organization and authority basis locally, and select a Method suited to its design problem.
Schulze-Meeßen and Hamborg, participatory work-design representations	Participant-facing representations can improve recognition and design knowledge.	Use representations to elicit design knowledge; test actual relations, authority, capability, and effects with the evidence appropriate to each claim.

Reopen when representative use exposes a recurring contribution crossing the result cannot express, a serious alternative produces the same decision with less modeling burden, or a direct source changes the specialization or participant action.

OCE.4:12 - Relations

OCE.1 supplies the organization, contribution, authority boundary, and affected-System scope. OCE.2 supplies current Work and direct-relation evidence. OCE.3 supplies candidate relation structures, assumptions, participants, and burdens.
A.22 governs actual selected structures; C.30 governs possible-future structure and relation content; A.6.REL and the applicable domain predicates govern obtaining direct relation occurrences; C.32.PAD governs an architecture decision when that use is current.
OCE.5 consumes stable position-design needs. OCE.6 establishes holder assignments and enabling relations. OCE.7 consumes organization-side structure for paired product-or-service decisions.
OCE.9 consumes design constraints and later returns realization evidence. OCE.12 may consume contribution architecture for leadership-contribution distribution.
Strategy, Corporate Governance, Operations, Administration, Systems Engineering, finance, legal, labor, safety, privacy, and other specialists supply only their available compatible results or qualified direct sources.

OCE.4:End

OCE.5 - Define Organization Positions

Type: Method pattern Status: Eternal alpha

Primary working result: organization-position descriptions and establishment or continuation decisions that name the owning organization, effective establishment basis, identity-bearing expected contributions and assignment-eligibility criteria, continuation conditions, and evidence needs without asserting a holder or performed Work.

OCE.5:0 - Use This When

Use this pattern when an organization needs a stable institutional position for expected contributions, but a title, job description, team label, or current holder is being used as the position itself. Enter when vacancy, holder replacement, eligibility, establishment, abolition, or continuation changes the decision.

Begin with a bounded organization and contribution need. A compatible OCE.4 result is useful when the position follows from a new contribution architecture; an existing law, charter, bylaw, appointment scheme, or organization decision may instead supply the basis for a current position.

The first useful result names one owning organization, one position identity, its establishment and continuation basis, the expected contributions that distinguish it, the eligible system-role kinds, and a description usable by OCE.6. A vacant position is a complete result when no holder decision is current.

Use A.2.1 directly when only a holder assignment is needed and no organization-position identity changes the use. Use OCE.6 to establish assignments, authority, responsibility, resource, or access relations. Use Human Capability Development for developing a person’s capability and applicable labor, legal, governance, compensation, privacy, or safety practice for their own decisions.

OCE.5:0.1 - Working Distinctions

Name used here	Meaning
organization position	An organization-dependent institutional subject whose identity depends on one owning organization, an effective establishment basis, and identity-bearing expected-contribution and assignment-eligibility criteria.
establishment basis	The applicable constitutive rule and the authorized act or other facts satisfying it for the owning organization. A statute, charter, bylaw, or organization decision may supply the rule or its application basis. A document is evidence or a carrier unless the applicable rule gives its issuance constitutive effect.
continuation basis	The current facts and governed relation under which the position remains in force with the same identity-bearing criteria.
expected contribution	A possible-future contribution expected from a holder assigned through an eligible system-role kind. It is position content, not performed Work or evidence of result.
assignment-eligibility criteria	Criteria selecting which local system-role kinds may be assigned in relation to the position. Classify a particular System, assess its capability, and establish its assignment separately.
position description	An episteme describing the position, basis, expected contributions, eligibility, conditions, and neighboring requirements. Editing the description changes the episteme first.
holder	One actual `U.System` that may participate in an assignment concerning the position. A position can be vacant, and one System can hold several assignments.
title	A designation useful for recognition and retrieval. Title continuity does not prove position continuity; title change does not by itself reidentify the position.

OCE.5:1 - Problem Frame

Organizations need persistent contribution loci that survive ordinary holder changes. A safety-acceptance position, treasurer position, editorial-chair position, or release-integration position can remain while vacant, while different eligible Systems are assigned, or while its description is republished.

The persistent subject is institution-dependent. Its establishment, identity, and continuation depend on the owning organization and its applicable authority. Expected contributions and eligibility make the position usable for organization design, while the actual holder, assignment, capability, authority, responsibility, and Work remain separately governed.

OCE.5:2 - Problem

When title, position, role kind, holder, and assignment are merged, ordinary changes become ambiguous. Replacing a person can appear to abolish a position. Renaming a title can appear to create one. Readers can mistake a job description for a grant of authority or proof of capability. A vacant position can disappear from the model even though the organization still relies on its expected contribution.

The reverse error models every recurring contribution or temporary assignment as a position. The organization records supposed positions without an establishment basis, and downstream users cannot tell which vacancies, appointments, or descriptions have institutional force.

OCE.5:3 - Forces

Force	Tension
Continuity	The organization needs stable contribution expectations, while holders, descriptions, and Work change.
Local law	Position identity depends on the organization and applicable basis, while reusable modeling needs a common working move.
Contribution breadth	One position can expect several contributions, while a broad bundle can hide incompatible eligibility or authority.
Eligibility	The position needs qualified kinds of assignee, while kind membership, capability, and assignment require separate evidence.
Vacancy	Planning and governance may need the position while no holder exists.
Description usability	Practitioners need a readable description that distinguishes the institutional position from its description and holder assignments.

OCE.5:4 - Solution

Define the position from its owning organization and institutional contribution, then recover the direct establishment and continuation predicates that give it force. Select only the expected contributions and eligibility criteria that distinguish the position for its current use. Publish a description after the position claim is recoverable, or publish an explicitly proposed description while establishment remains a future decision.

Recognition is cheap: enter when a decision about a position is blocked by confusion among vacancy, holder change, and description revision. Assurance is stronger: a current position claim needs its owning organization, direct establishment basis, identity-bearing criteria, continuation condition, scope, interval, and evidence.

OCE.5:4.0 - One first position description

Suppose a standards association’s effective bylaw 8 already establishes an editorial-chair position, its expected contribution and its eligible local role kind. An organizer preparing an appointment can begin with one short description:

The association’s EditorialChair position is established by bylaw 8 and is currently vacant. It remains the same position while that basis and its identity-bearing criteria remain in force. It expects amendment-packet preparation and the return of unsupported evidence to contributors. The association’s defined MemberEditorSystemRole kind is eligible for assignment. Return publication access as an enabling need for the separate appointment decision. Holder selection, authority, and effective access remain to be established.

Return that description and its bylaw basis to the person arranging the assignment. The appointment, candidate’s capability and effective access remain OCE.6 or direct-owner questions. If the establishment or continuation basis is missing, return a proposed description or unresolved position claim instead.

The fuller questions below become useful when the position’s identity, eligibility, contribution or institutional basis is unresolved or must change. Reuse current answers and add only the neighboring requirements that change this position or the next assignment; no separate form is required.

OCE.5:4.1 - Pattern-Use Unfolding

Bind the position question. Name the owning organization, intended contribution, current design or operating need, decision subject, authority, horizon, and first receiver of the position description.
Recover candidate claims. Collect the current charter, bylaws, organization decisions, position descriptions, title uses, contribution architecture, assignments, holder facts, and observed Work. State what each source can establish.
Find the establishment predicate. Identify the applicable domain predicate, authority, act or relation that creates the position, its effective condition, and its owning organization. If the applicable predicate or establishment basis is unavailable, retain a proposed description or unresolved position claim.
Set the identity-bearing criteria. State the expected contributions and assignment-eligibility criteria that distinguish this position. Add another criterion only when changing it would change which institutional position the organization means.
Specify eligible role kinds. Name the exact local system-role-kind domain and criteria relevant to assignment. Keep System classification, candidate-holder capability, and actual assignment as later questions.
Separate neighboring relations. State responsibility, authority, permission, resource, access, compensation, reporting, or membership requirements as separately governed needs. Include one only when it changes the position design or downstream assignment.
State continuation and termination. Name the basis remaining in force, identity-bearing criteria that must remain, effectivity window, abolition or suspension condition, and evidence that triggers re-evaluation. Holder or description change alone preserves identity unless the applicable basis says otherwise.
Write the position description. Give the title or designations, owner, basis, expected contributions, eligibility, scope, conditions, neighboring requirements, vacancy status, and source return. Mark a proposal as possible-future content.
Test identity changes. Replay vacancy, holder replacement, title change, description correction, changed expected contribution, changed eligibility, abolition, and re-establishment. State which preserve identity and which require a new or unresolved position claim.
Return assignment input. Supply position identity, eligible kinds, expected contributions, establishment/continuation facts, and enabling needs to OCE.6. Return capability, legal, labor, governance, compensation, privacy, or safety questions to their owners.
Stop at position sufficiency. Return when a reader can tell whether the position exists, what makes it the same position, which contributions it expects, who may be assigned by kind, and what observation reopens that account.

OCE.5:4.2 - Record the Result

Result position	Required content
use boundary	Owning organization, contribution need, decision, authority, horizon, and first receiver.
position identity	Position reference or proposed reference, owning organization, direct establishment predicate and basis, identity-bearing criteria, scope, and interval.
expected contributions	Receivers, results or preserved conditions, applicability, acceptance needs, and relation to `OCE.4` when current.
eligibility	Exact local system-role kinds, criteria, exclusions justified by the contribution, and unresolved classification or capability questions.
neighboring requirements	Separately governed authority, responsibility, permission, access, resource, compensation, reporting, membership, legal, or safety needs that change later assignment.
continuation	Current basis, continuation evidence, suspension or abolition condition, and identity-changing observations.
description	Title/designations, content, source return, publication boundary, current or proposed status, and known losses.
assignment return	Inputs and gaps supplied to `OCE.6`; no holder or Work assertion.

OCE.5:4.3 - What Changes in Practice

Practitioners can keep a position visible while vacant and can replace a holder without rewriting the position. They can also change a title or description without claiming an institutional change. When expected contribution or eligibility changes materially, the organization makes that identity question explicit instead of hiding it in a revised document.

OCE.5:5 - Archetypal Grounding – PumpWorks Release-Evidence Integration Position

The OCE.4 design requires stable coordination of electrical compatibility evidence, platform test results, provider model artifacts, unresolved assumptions, and the evidence package used by Safety. PumpWorks decides that this expected contribution should persist beyond one release or holder.

PumpWorks-EngineeringOrg is the owning organization. Authorized organization decision PW-OD-2026-04 establishes PW-ReleaseEvidenceIntegrationPosition from 2026-10-01 while the decision remains effective. The identity-bearing expected contribution is to maintain the traceable release-evidence assembly and return unresolved mismatches to the participants supplying the underlying evidence. The eligible local system-role kinds are SystemsIntegrationEngineerSystemRole and ReleaseEvidenceCoordinatorSystemRole under the current PumpWorks role-kind scheme.

The position description names coordination and evidence-return expectations; safety-evidence acceptance and release authority remain with their separate decision-makers. The description records test-environment and provider-artifact access as enabling needs for OCE.6. The position is initially vacant.

Change	Position disposition
a holder is assigned on 2026-10-01	Same position; `OCE.6` governs the assignment occurrence
holder leaves and the position becomes vacant	Same position while `PW-OD-2026-04` and identity-bearing criteria remain in force
title changes to “Release Evidence Coordinator”	Same position if the designation changes and the identity-bearing criteria do not
description clarifies a reporting view	Same position; the description episteme changes
expected contribution changes from evidence integration to issuing the release decision	Reopen identity and authority; do not silently continue the same position
`PW-OD-2026-04` is abolished with no continuation rule	The current position ceases; later re-establishment needs a new or explicitly continued identity basis

The result supplied to OCE.6 contains the position, eligible kinds, expected contribution, access needs, effectivity, and vacancy. It contains no candidate-holder selection or capability conclusion.

OCE.5:5.1 - Transfer Probes

Setting	Reusable move	Required return or changed content
public-hospital emergency flow	Define a clinical coordination or acceptance position from the hospital’s applicable statutory and governance basis and its contribution	Clinical authority, licensure, labor agreement, shift assignment, privacy, and patient-safety conditions remain separate and can block assignment
distributed standards association	Define an editorial-chair or treasurer position from bylaws, member decision, expected contribution, eligibility, term, and continuation rules	Election, volunteer availability, employer permission, financial authority, publication access, and actual Work remain separate; no executive hierarchy is assumed

OCE.5:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
title realism	A familiar title is treated as the position identity.	Recover owner, establishment basis, expected contribution, eligibility, and continuation.
incumbent anchoring	The current holder’s skills and habits define the position.	Start from the organization contribution and keep holder-specific capability or preference outside the identity.
document constitution	Publishing or editing a job description is treated as establishment.	Apply the direct establishment predicate and keep the description as an episteme.
hierarchy default	Every position is placed in a reporting tree.	Add reporting, authority, or membership only through their direct relations and when they change use.
vacancy erasure	An unfilled position disappears from organization design.	Retain the position while its establishment and continuation conditions obtain.
durable-object inflation	Every temporary contribution or assignment becomes a position.	Require an institutional establishment basis and stable identity-bearing criteria.

OCE.5:7 - Conformance Checklist

One owning organization and one current or proposed position are explicit.
The establishment predicate, authority, basis, effectivity, and evidence are stated or a missing governor is returned.
Identity-bearing expected contributions and eligibility criteria are distinguishable from descriptive detail.
Eligible system-role kinds come from an exact local domain; eligibility does not classify or assign a holder.
Vacancy, holder change, title change, description change, identity-criterion change, abolition, and re-establishment have explicit dispositions.
Authority, responsibility, permission, access, resources, compensation, reporting, membership, capability, and Work use their own relations when current.
The position description states current or proposed status and its source return.
The OCE.6 return contains no inferred assignment or capability.

OCE.5:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
“The product manager role owns the roadmap.”	Recover whether the phrase denotes a position, role kind, assignment, authority, responsibility, contribution expectation, or current Work; establish each needed claim directly.
“Create a position by adding a box to the chart.”	Obtain the authorized establishment decision or other applicable constitutive basis, then publish the chart as a view.
“The position requires strategic thinking and leadership.”	State the expected contribution and eligible role kinds first; send measurable holder capability and person-development needs to their owners.
“The incumbent defines the job.”	Use observations of Work and participants’ knowledge as evidence, then decide the position from the organization’s intended contribution and institutional basis.
“No holder means no position.”	Check continuation conditions. Record vacancy and the assignment need separately.

OCE.5:9 - Consequences

Position continuity, vacancy, assignment, and description revision become manageable. Organization design can name persistent expected contributions while separately recording the actual holders and position descriptions.

The cost is local grounding. Different organizations can establish positions through different legal, governance, membership, or organization predicates. A reusable title list cannot replace that work.

OCE.5:10 - Rationale

A position is useful because it persists across ordinary holder and Work changes. That persistence requires an organization-dependent identity rather than a label or person. Expected contribution and eligibility provide the stable organization-design content; establishment and continuation provide institutional force.

Keeping the position separate from U.SystemRoleAssignment also preserves cases where an assignment has no position and cases where a position is vacant. It lets A.2.1 retain exact assignment species while OCE supplies the domain subject needed by organization design.

OCE.5:11 - SoTA-Echoing

OCE.5:11.1 - Current-Line Selection for Position Design

Comparison position	Selected result for practice
Current question	Does this recurring expected contribution need a stable organization-dependent position, or can direct assignments, tasks, projects, or other arrangements carry it?
Selected current line	Establish or preserve a position only when vacancy, holder replacement, continuation, institutional force, and identity-bearing expected contribution or eligibility change the decision. Otherwise keep the contribution and direct assignments without inflating a durable position.
Serious alternative	Treat the job title, job description, chart box, role taxonomy, or fully deconstructed task/project market as the default organization design.
When the alternative is sufficient	A direct task, project, or assignment is sufficient when no stable institutional locus must persist across holders and no establishment or continuation claim is needed.
When the selected line changes action	If the organization must recognize vacancy, continuation, abolition, eligibility, or the same contribution locus across holder changes, recover the owning organization and establishment predicate, then define identity-bearing criteria.
Reopen	Reconsider when unlike institutional settings defeat the identity test, current work-design evidence changes the position versus direct-assignment choice, or the institutional locus must persist outside any one owning organization.

OCE.5:11.2 - Source Contributions and Boundaries

An organization position can persist across holders, carry several expected contributions and remain vacant. Determine which position is in force from the organization’s rules for establishing and continuing it.

Source line	Retained contribution	Use boundary
Current FPF `A.2.1`, `A.2.2`, `A.6.REL`, `A.10`, `A.13`, and `A.15.1`	Role-kind classification, assignment, capability, relation obtaining, evidence, performer, and Work remain separately governed.	FPF does not currently define the organization-dependent institutional position.
Rogiers and Collings, job-deconstruction paradoxes	Task- and project-based alternatives can add adaptability, while deconstructing jobs creates persistent human and organization paradoxes rather than a universal replacement for positions.	Make the local position-versus-direct-arrangement choice using the organization’s contribution and institutional conditions.
Grote et al., contribution-based engineering role modeling	Deriving contribution bundles from required process contributions and stakeholder evidence can expose gaps hidden by titles.	Test transfer beyond the bounded engineering cases; establish local positions and assignments under the owning organization’s rules.
Albert, organization-structure perspectives	Activity grouping, decision representation, and legal-entity perspectives can give different evidence about a position’s place.	Use the perspective as evidence, then recover the position’s establishment basis and any separate authority relation.
Fraccaroli, Zaniboni, and Truxillo, work-design review	Work characteristics and affected-person outcomes must inform position design and later holder use.	Combine work-design evidence with the organization’s establishment basis; assess a proposed holder’s current capability separately when a holder decision is current.

Reopen when a representative institutional setting cannot distinguish position identity from assignment, a stronger source changes the position-versus-direct-arrangement choice or identity-bearing criteria, or the required institutional locus must persist outside any one owning organization.

OCE.5:12 - Relations

OCE.1 supplies the organization and contribution boundary. OCE.2 supplies current descriptions, assignments, holders, Work, and gaps in the position-establishment or identity basis. OCE.3 and OCE.4 supply possible position needs and expected contributions.
A.2.1 defines direct assignment species and occurrences. A.2.2 defines holder capability. A.6.REL governs direct relation obtaining and occurrence identity.
OCE.6 consumes position identity, eligibility, expected contributions, effectivity, and enabling needs; a position must have its own establishment basis when one is needed.
Legal, labor, governance, compensation, privacy, safety, licensing, membership, and other domain practices govern their own predicates and decisions. An OCE position description can cite their available results without absorbing them.
OCE.9 later tests organization capability and actual relations. That test requires organization-level evidence beyond the holder-assignment and vacancy facts.

OCE.5:End

OCE.6 - Establish Holder Assignments and Enabling Relations for Organization Change

Type: Method pattern Status: Eternal alpha

Primary working result: the obtaining holder assignments and enabling relations needed for a bounded organization contribution, together with their predicates, participants, authority, effectivity, evidence, unresolved gaps, and any possible-future specifications that have not yet taken effect.

OCE.6:0 - Use This When

Use this pattern when a contribution architecture or position design names who must contribute, yet the actual holder assignment, authority, responsibility, resource, access, permission, or other enabling relation is unclear or not effective. Enter when a staffing decision, appointment letter, budget, licence, roster, or tool account is being treated as proof that the complete arrangement now obtains.

Begin with a bounded contribution need and candidate holder Systems. Use an OCE.5 position when the assignment depends on one; otherwise begin from the direct contribution and the exact local system-role kind. Recover the authority under which each change can be made.

The first useful result can be partial: one effective assignment, its exact species and interval, separately effective enabling relations, and a visible list of pending, contradicted, expired, or missing relations. A truthful blocker is useful when authority or a direct predicate is absent.

Use A.2.1 directly when the assignment species and occurrence are already known and no OCE coordination changes the result. Use Administration for participant records, provisioning, or service cases; Human Capability Development for developing a holder’s capability; Corporate Governance, legal, labor, safety, security, finance, or another specialist practice for their decisions and predicates; and OCE.9 for organization-capability realization.

OCE.6:0.1 - Working Distinctions

Name used here	Meaning
candidate holder	An actual `U.System` being considered for an assignment. Assess classification, eligibility, capability, consent, and assignment under the criteria applicable to the proposed contribution.
assignment specification	Possible-future content naming a proposed direct assignment species, participants, applicability, intended interval, and conditions.
assignment decision	A separately governed decision to establish, change, suspend, or end an assignment. It creates an occurrence only when the admitted species predicate gives that decision constitutive effect and every condition is satisfied.
assignment occurrence	One obtaining occurrence of a directly declared species under `U.SystemRoleAssignment`, with holder, exact local system-role kind, every real additional participant, predicate, applicability, and uninterrupted interval recoverable.
position-sensitive assignment	An assignment species whose direct predicate requires an actual `OCE.5` organization position as a participant. The position is included only because it changes predicate or identity.
enabling relation	Readable OCE wording for one separately admitted authority, responsibility, permission, resource-allocation, access, membership, commitment, or other relation needed for the contribution. It is not a new root relation family.
capability evidence	Evidence bearing on a qualified ability claim about the holder under `A.2.2`. Assignment, title, position, training, resource, or tool presence does not replace it.
assignment-and-enabling result	The account of direct relation claims returned by this pattern, including effective relations, proposed changes, and unresolved conditions.

OCE.6:1 - Problem Frame

Organization change becomes operational when actual Systems hold effective assignments and the other relations needed for their contribution obtain. An appointment can identify a holder and system-role kind, while resource access, decision authority, responsibility, equipment availability, provider commitment, and capability remain separate. Each has its own participants or bearer, governing conditions, basis, and effective interval.

The practitioner therefore coordinates a small set of direct changes rather than filling one staffing row. They decide what should become effective, obtain the acts or services required by each owner, and then verify the relations that actually obtain.

OCE.6:2 - Problem

A chart or roster can show a name next to a position before an appointment is effective. A signed appointment can coexist with missing system access. A budget can exist without a resource-allocation relation for the Work. Responsibility can be stated without an admitted predicate. A capable person can lack authority, while an authorized holder can lack capability for the current envelope.

When these claims are bundled, later Work fails in ways that look personal or motivational. The organization cannot identify the exact missing relation, its owner, or its effective window. Conversely, a completed provisioning ticket can be mistaken for the whole organization change.

OCE.6:3 - Forces

Force	Tension
Speed	Contributions need holders quickly, while premature effectiveness claims hide blockers.
Exact species	Reusable assignment logic is valuable, while appointments, shifts, elected offices, provider assignments, and equipment roles have different participants and predicates.
Capability and authority	Both can be necessary for Work, while neither implies the other.
Resource readiness	Access and equipment can enable contribution, while their presence does not assign a holder or establish capability.
Several owners	Organization change needs a coherent result, while legal, governance, labor, security, finance, administration, and safety retain their authority.
Currentness	Assignment and access can expire or be suspended, while stale records remain visible.

OCE.6:4 - Solution

Start from the contribution and select the exact assignment species, then establish every needed neighboring relation through its own owner and predicate. Keep proposed, decided, effective, contradicted, expired, and missing states separate. Return only relations whose obtaining conditions are satisfied, along with explicit gaps that change Work entry or later realization.

Recognition is cheap: one required contribution with an ambiguous holder or missing enabling condition is enough to enter. Assurance is predicate-specific: the holder, local role kind, additional participants, authority, applicability, extent, basis, evidence, and currentness of every relied-on relation must be recoverable.

OCE.6:4.0 - One bounded first return

For a small first use, take one contribution with a current, reusable assignment result and resolve the enabling gap that changes its next Work. In the PumpWorks case below, verify the appointment’s continued effectivity and obtain the repository-access owner’s current result. The practitioner can return this short account to the person arranging the integration: