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 the question concerns 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 the Work and direct relations needed to answer the question or support the decision.
The first useful result is a bounded account with each claim’s source, status, window and uncertainty. Stop when it answers the question, supports the decision or identifies the gap that limits the result.
Use OCE.3 for concepts and the responsible design or assignment method when new arrangements are required. Compare any informal relation with the applicable obligations and its observed consequences before judging it defective.
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. Establish the rule, delegation or decision that actually grants that authority. |
| 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 that answers a bounded organizational question or supports a decision, 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.