Purpose
What this record standardizes.
Merge two packages without silent overwrite, preserve unknown extensions, and require explicit resolution for every content conflict.
Integrity-aware local tooling is useful only when state changes, conflicts, evidence custody, and release decisions remain inspectable and reversible.
Normative requirements
What conforming implementations must, should, and may do.
Merge two packages without silent overwrite, preserve unknown extensions, and require explicit resolution for every content conflict.
The implementation preserve imported source content and unknown fields unless a user explicitly selects and records a transformation.
The interface expose applicable standards, UTC event times, reason codes, and exportable machine-readable records.
Game interaction mapping
What players and interfaces do.
Data contract
Inputs and outputs.
Inputs
- Two Operation Packages
- Source checksums
- Resolution choices
Outputs
- Merged package
- Conflict record
- Merged component checksums
State contract
Allowed or expected transitions.
| From | Event | To |
|---|---|---|
| loaded | review requirement evaluated | verified-or-explicitly-unresolved |
Evidence and provenance
Review requirements for claims and consequential state.
- Every consequential result records source identifiers, UTC event time, canonical digest where applicable, responsible local action, and reason code.
- Integrity results distinguish equality from authenticity and never identify a human signer.
User-interface requirements
How the requirement must appear at the point of use.
- Show source paths and both values for every conflict or difference.
- Never disable export of the original imported artifact because validation failed.
- Provide direct links to the canonical standard and machine-readable record.
Accessibility requirements
Equivalent access to essential information and controls.
- Essential information is available without reliance on color, audio, motion, or a VR-only gesture.
- Keyboard, screen-reader, reduced-motion, high-zoom, and print equivalents are documented where the interaction applies.
Telemetry events
Minimum event records for implementation review.
standard.conflict-aware-operation-package-merge.evaluated
Required fields:
Abuse and exploit cases
What the implementation must anticipate.
- A conflict is silently overwritten by source order.
- A checksum mismatch causes imported content to be rewritten.
- Unknown extension data is dropped during merge, migration, backup, or restore.
Failure and recovery
Fail-closed behavior and recovery path.
Fail closed for publication or irreversible merge output. Preserve every imported artifact, explain the failure, and permit export of the original plus the failure record.
Return to the last preserved source state, select or annotate an explicit resolution, recalculate affected digests, and record the new result without altering the originals.
Example implementation
A concise fictional game implementation.
The Conflict-aware Operation Package Merge interface evaluates PKG-02, displays source evidence and reason codes, and exports a local JSON result.
Open complete mission examples →Related records and examples
Continue through the operating model.
Supporting research
Deep links into complete canonical reports.
Revision history
Published changes to this record.
Initial IARPG-OPS-2 2.0.3-wip publication.
Reviewed for canonicalization, round-trip portability, recovery, provenance, compatibility, accessibility, hosting evidence, and stable-promotion gates.
