Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

OPS.3:11 - SoTA-Echoing

The question is which subjects, relations and times must be recovered before the responsible practitioner can rely on the records for an operating decision. A capable object-centric account already relates events to several objects, retains histories and distinguishes relation meanings. OPS adapts that contribution.

OCEL supplies an exchange model for that account. The 2026 object-centric process management manifesto, particularly §2.3 and §3, distinguishes execution data from their representations and identifies changing relations as a limitation of OCEL 2.0. The 2026 object-centric data-quality study, “Relationship-based quality issues” and its practitioner cases, shows why a well-formed multi-object log can still have wrong or insufficiently qualified links and changing timestamp meanings. These findings motivate checking object links and timestamp meanings in steps 6 and 9 of OPS.3:4.1 and in OPS.3:5. Whether the correction improves a particular operating decision requires evidence from its use there.

In the L17 choice, a competent data-quality procedure that already checks the build, timestamp meaning, correction provenance and affected consumers is sufficient. Use it unchanged. Where it repairs the log but leaves the operating consequence undecided, OPS adds the narrow return: withdraw the unsupported R42 completion, recompute only dependent membership and age, and retain the independently supported work. The extra cost is consulting the responsible source and following the faulty relation into the decisions that relied on it. Recreating every object or copying all histories into a second account is unnecessary. An unresolved relation can block one inference without blocking the rest of the operation.

Current FPF A.6.REL governs the direct relations relied on; distinguish relation occurrences only when the receiving use must tell repeated occurrences apart. C.2.1 governs claim-bearing accounts and B.2.5 the selected two-sided supervision relation. Subject-specific identity and specialist evidence remain with their direct governors. CMMN 1.1, DCR and DEMO’s bounded commitment/coordination account retain their case-planning and relation contributions; none makes record closure proof of physical completion. Integrated network descriptions can retain unlike coupled relations without identifying their subjects.

Reopen this choice when the record’s meaning, relation history, clock, consumer or correction authority changes, or when the incumbent supplies the same bounded correction and operating return at lower effort. For a larger data migration, use the appropriate data-engineering method.