OCE.2 - Recover Current Organization Work and Arrangement

Type: Method pattern Status: Eternal alpha

Primary working result: a grounded current-organization account that identifies the actual Work, supplied results, holder assignments, authority, responsibilities, resource access, information use, material transfer, service provision, coordination, participation, and results needed by one organization-change decision, while keeping formal, observed, contradicted, and unknown claims distinct.

OCE.2:0 - Use This When

Use this pattern when a chart, process map, job catalogue, policy, target operating model, or leader interview is being used as a complete account of the current organization. Enter when a decision depends on how Work actually proceeds, who contributes, which assignments and authority relations obtain, what resources are accessible, or where formal and observed claims diverge.

Begin with a compatible OCE.1 focus or equivalent content. Select only the Work and direct relations that can change the decision.

The first useful result is a bounded account with each claim’s source, status, window and uncertainty. Stop when it supports the decision or identifies the gap that prevents it.

Do not use OCE.2 to invent target positions, assign holders, redesign contribution boundaries, or judge an informal relation defective merely because it differs from policy. Use OCE.3 for concepts and the owning downstream pattern for design or assignment.

OCE.2:0.1 - Working Distinctions

Name used here	Meaning
actual Work	A dated performed occurrence admitted under `A.15.1`, with the performers’ `A.13` basis, an enacted Method, time interval and containing System. If that basis is incomplete, keep the supported observations and the unresolved Work claim. A schedule, workflow description or recurring label is not Work.
supplied result and contribution	A result or preserved condition supplied to a receiving System or Work through a named relation. A duty statement does not prove supply.
organization position	An organization-dependent institutional position governed by OCE.5. Its identity depends on the owning organization, an effective establishment basis, and identity-bearing expected-contribution and assignment-eligibility criteria. It continues only while that basis remains in force and those criteria remain the same. It is neither a System, system-role kind, assignment, holder, nor description.
position description	An episteme describing a position, its expected contributions, eligibility, and applicability. A description does not establish the position or an assignment.
system-role kind	A local classification usable by a declared assignment species. Support any assignment, capability, responsibility, authority or performed-Work claim separately.
assignment	An obtaining occurrence of a declared species under `U.SystemRoleAssignment`. Its holder, assigned system-role kind, scope, window, and any real position participant remain recoverable. Identify the actual performer separately.
authority	A direct relation under which a named System may issue a named decision result within a scope, window, and basis. It is not inferred from assignment, responsibility, seniority, or participation.
resource-access relation	The relation by which Work or a System can use a named resource under stated conditions. Resource presence, budget, and licence are different claims.
boundary relations	Named contribution, information-use, material-transfer, decision, service-provision, access, or coordination relations across a selected organization boundary. “Interface” may be retained as ordinary shorthand only after the boundary, selected structure, members, and direct relations are stated.
formal/observed claim pair	Two separately sourced claims about what should obtain and what evidence says obtains. Their difference is a finding, not automatic failure.
current-organization account	The bounded episteme returned for one decision use, describing the supported Work and organization-relation claims and their gaps.

If an existing organization-position claim lacks an effective establishment basis or the OCE.5 identity criteria, do not infer a position from a title or description. Record the expected-contribution claim, eligibility claim, holder, and assignment separately, plus the missing position-establishment or identity basis.

OCE.2:1 - Problem Frame

Formal descriptions support authorization, communication, administration, or staffing. Observed Work exposes who resolves exceptions, which evidence reaches a decision, where providers enter, what resource is scarce, and which informal coordination preserves service. Both can matter; neither replaces the other.

Select separate contribution, Work, assignment, authority, resource-access, information-use, material-transfer, service-provision, and coordination structures for the decision. They can overlap without being isomorphic. A mathematical graph is an optional lens only after its nodes, edges, semantics, and use are selected.

OCE.2:2 - Problem

When the chart stands for the organization, a designer can move boxes while leaving the actual bottleneck untouched. When observation stands alone, a temporary workaround can be mistaken for a reusable arrangement and formal authority or safety obligations can disappear.

The resulting concept has no defensible baseline. Later claims cannot say which relation changed, whether it obtained before, or who bore the burden.

OCE.2:3 - Forces

Force	Tension
Economy	A fast baseline is needed, while collecting everything produces an unusable inventory.
Formal and observed truth	Formal claims matter, while actual Work can differ and either branch can be stale.
Sensitive evidence	Interviews and traces reveal hidden Work, while they expose people, power, and provider relations.
Several structures	Contributions, Work, authority, and access answer different questions, while one diagram is easier.
Attribution	Practitioners need to know who performed Work and issued decisions, while assignment, authority, and performance are easy to collapse.
Currentness	Relations change during recovery, while false precision can outlive its evidence window.

OCE.2:4 - Solution

Recover the smallest evidence-bearing set of actual Work and direct organization relations that can change the decision. Use A.22 to select each structure and the direct FPF or domain governor for each relation. Preserve formal, observed, contradicted, and unknown statuses, evidence provenance, and currentness.

One decision-changing difference between a formal description and observed Work is enough to enter. Support each Work, supply, assignment, authority, access, information-use, transfer, service-provision or coordination claim with evidence appropriate to its meaning and time window.

OCE.2:4.1 - Pattern-Use Unfolding

Bound the recovery use. State organization, contribution, decision, horizon, Work families, selected structures, and exclusions.
Collect sources for the needed claims. These may include charts, position descriptions, policies, decision records, Work products, observations, interviews, provider records and service evidence. State what each can establish.
Recover actual Work and results. For a relied-on Work claim, recover the performers’ A.13 basis and the A.15.1 occurrence basis. Keep plans, routine descriptions, schedules and reports distinct from the Work occurrences they describe. When the basis is incomplete, record the supported observations and the missing basis.
Recover supplied-result and boundary relations. For every relevant path, name supplier and receiver Systems, result or content, direct predicate, conditions, and evidence. Distinguish a contribution supplied, information used, material transferred, decision issued or accepted, service provided, resource accessed, and coordination occurrence.
Recover position-related claims without invention. A current organization position requires its establishment and continuation basis. Otherwise record only the position description, expected contribution, eligible system-role kinds, holder Systems, and assignments that are separately supported. Use A.2.1 for obtaining assignments.
Recover authority, responsibility, resources, and access. Name each direct relation. Record a blocker instead of inferring authority or access from hierarchy, responsibility, budget, or tool presence.
Compare formal and observed claims. State agree, contradict, unknown, or changed-window for each decision-changing pair. Ask what result and consequence the difference has; do not call it dysfunction by default.
Inspect participation and consequences. Identify whose Work and burden are absent, which affected-System questions remain open, and which sensitive claims require protection or specialist handling.
Stop at the decision boundary. Return the account, gaps, and constraints when they are enough to generate concepts or expose a blocker. Do not design the target inside the baseline.
Reopen from evidence. Reopen the smallest Work or relation claim when a new occurrence, source edition, participant account, provider condition, authority decision, or service result defeats it.

OCE.2:4.2 - Record the Result

Result position	Required content
use boundary	Organization, contribution, receiving decision, horizon, selected structures, and exclusions.
source evidence	Source or observation, claim kind, scope/window, sensitivity, and evidential limit.
actual Work	Supported occurrences, performers and their A.13 basis, enacted Methods, time intervals, conditions, containing Systems, associated results and limits; otherwise the observations and unresolved occurrence claim.
supplied results and boundary relations	Participants, direct predicate, result/content/resource, conditions, carrier/support distinction, evidence, and status.
position-related claims and assignments	Position establishment/continuation basis when available; otherwise separate description, expected-contribution, eligibility, holder, and assignment facts plus the missing establishment or identity basis.
authority, responsibility, resources	Direct relations, subjects, scopes, windows, bases, evidence, and blockers.
formal/observed comparison	Matched claims with `agree`, `contradict`, `unknown`, or `changed-window` and the decision consequence.
participation/consequences	Missing participants, hidden burden, affected-System questions, protection needs, and specialist returns.
return	Grounded account, unresolved gaps, constraints for `OCE.3` or `OCE.11`, stop, and reopen triggers.

OCE.2:4.3 - What Changes in Practice

The organization is no longer represented by one chart. Practitioners can see which Work and relations matter, where formal and observed claims differ, what remains unknown, and which gap must be resolved before a concept or coexistence decision can be trusted.

OCE.2:5 - Archetypal Grounding – PumpWorks Current Relations

The OCE.1 focus selects PumpWorks-EngineeringOrg and weekly evidenced AI-inspection releases while service continues. Recovery is limited to release Work, result supply and use, decision authority, provider service, rig access, and field-service information return.

Selected claim	Formal claim	Observed or current evidence	Current disposition
integrated-release evidence	Software prepares the integrated package at the quarterly checkpoint	Electrical engineers supply compatibility evidence used in a recurring cross-functional review with Software	Both supplied-result and information-use relations obtain in sampled occurrences; the chart does not show them
safety and release decisions	“Safety signs the release”	A named safety reviewer issues an evidence-acceptance result; the release director issues the release decision	Preserve two decision and authority relations
field-service information return	Field Service supplies quarterly feedback	Fault-pattern information reaches Product through a service liaison; completeness and window are unknown	Retain the observed information-supply/use relations and evidence gap
provider contribution	Provider supplies inspection models	Provider supplies model artifacts and remote support; access, exception handling, assurance, and decision authority differ by case	Recover each supply, service, access and authority relation separately; a claim that both parties form one organization needs its own basis
inspection-rig access	Engineering has the rig	The rig is shared with service diagnostics and unavailable in some release windows	Resource presence is supported; decision-window access is not
“release team”	A cross-functional release team performs releases	No maintained team assignment or position-establishment basis is supported; named people contribute through several assignments and coordination occurrences	Keep the phrase as a view label; recover holders, assignments, Work, and authority separately

The account records sampled occurrences and source windows. Organization capability and causal-bottleneck claims need additional evidence appropriate to those claims. The rig-access gap, separate safety and release decisions, informal service return, and provider exception path constrain OCE.3 and a future OCE.11 decision.

OCE.2:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
chart realism	Formal reporting relations become all organization relations.	Select each decision-changing structure and recover its relations.
observation realism	One workaround becomes a stable arrangement.	State occurrence, scope, recurrence evidence, and currentness.
title-to-position bias	A title identifies a position, system-role kind, assignment, capability, and authority.	Require the position basis or keep every supported claim separate.
carrier-as-relation bias	A meeting, ticket, API, or document becomes the contribution relation.	Name participants, direct predicate, result or content, conditions, and carrier use.
deviation-as-defect bias	Any formal/observed mismatch is called resistance.	Ask what result and consequence the difference produces.
complete-model bias	Recovery expands until every relation is mapped.	Stop at the receiving decision or blocker.

OCE.2:7 - Conformance Checklist

The account names one decision, horizon, selected structures, and exclusions.
Sources state scope, window, sensitivity, and evidential limits.
Actual Work is separate from plans, routines, process descriptions, and reports.
Contribution supply, information use, material transfer, decision, service provision, access, and coordination remain distinct.
A position claim has an establishment/continuation basis, or only its separately supported neighboring facts are recorded.
Job title, position, system-role kind, holder, assignment, capability, responsibility, participation, and authority remain distinct.
Every authority and access relation names its participants, scope, window, basis, and evidence.
Formal/observed differences have explicit status and are not judged by mismatch alone.
The result stops before target design and supplies usable constraints.

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

Anti-pattern	Repair
“The org chart is the as-is architecture.”	Recover the Work and direct relations needed by the decision.
“The process map proves this is how work happens.”	Treat it as an episteme; identify actual occurrences and evidence.
“The product owner owns the decision.”	Recover the authority or ownership relation; the word “owner” supplies neither.
“Everyone works around the process, so adoption is low.”	Name the formal/observed relation difference, result, burden, and reason first.
“We need a complete digital twin.”	Recover only the structures and currentness needed by the decision.

OCE.2:9 - Consequences

The baseline can support concept generation because claims are tied to subjects, relations, evidence, and windows. It can also preserve valuable informal contributions that a target design might destroy.

The cost is plural representation. Contribution, authority, Work, access, and information-use structures may need different views. Their non-isomorphism is a finding.

OCE.2:10 - Rationale

Ground the account in observed Work and supported direct relations. Separating formal and observed claims makes discrepancies inspectable. Requiring a position-establishment basis prevents a title or description from becoming an organization object by wording alone.

OCE.2:11 - SoTA-Echoing

Source line	Retained contribution	Use boundary
Current FPF `A.22`, `A.6.REL`, `A.2.1`, `A.13`, `A.15.1`, and `A.10`	Structure selection, relation recovery, assignments, performers, Work, and evidence use.	OCE.2 selects organization-specific questions and direct receiving relations.
Albert, organization-structure perspectives	Activity, decision, and legal-entity structures can all matter and need not coincide.	The perspectives are lenses for recovery, not one complete model.
Grote et al., contribution-based engineering role modeling (`SRC-ENGINEERING-ROLE-MODELING-2025`)	Required contributions can expose role bundles more accurately than inherited titles.	Use the role bundles to examine needed contributions. Assignment and transfer beyond the studied cases require their own basis.
Fraccaroli, Zaniboni, and Truxillo, work-design review	Actual Work characteristics and affected-person outcomes belong in the baseline.	Use direct evidence for authority and capability claims, and a separate decision for the target organization.

Reopen when representative use exposes a decision-changing relation the result cannot preserve, or when a stronger source changes how formal and observed claims should be compared.

OCE.2:12 - Relations

OCE.1 supplies organization, contribution, Work/capability questions, affected-System gaps, authority boundary, and horizon.
A.22 governs selected structure identity; direct relation patterns govern supplied-result, assignment, authority, access, information-use, transfer, service, and coordination claims.
Use A.13 for the performer basis, then A.15.1 for actual Work; use A.2.1 for assignments. Support each claim needed by the receiving decision.
OCE.5 governs organization-position identity and descriptions; OCE.6 governs holder assignments and enabling relations. Until their needed result is available, record the missing position-establishment or identity basis rather than inferring a position.
OCE.3 consumes the grounded Work and direct-relation account. OCE.11 consumes it for change/continuing-Work coexistence.