Event OR · 0.1.0

Event OR Block

<!-- block-metadata:start -->

Verified BloxSmith versions: 1.0.9 (bundled-block tests; see test evidence).

<!-- block-metadata:end -->

Role

event_or forwards the first new incoming event among its inputs. It is used to unblock a downstream path when any connected input receives data.

Files

• block.py: event deduplication, first-event selection, and runtime emission.
• model.json: two optional inputs and one output.
• inspector_panel.html, assets/: inspector UI.
• assets/js/block_modal.js: modal-owned mount hook used by the framework to keep the modal stable during polling.
• node_card.html: block-owned canvas card body.

Ports

• Inputs:
  • input_1 (id: 1): optional message/*.
  • input_2 (id: 2): optional message/*.
• Outputs:
  • out (id: 1): emits message/*.

Configuration

No config is required.

Runtime Behavior

execute_runtime() inspects context.input_events, fingerprints events, ignores events already seen in context.state, and emits the first new value. If there is no new event, it succeeds without emitting.

The runtime registry marks this block with centralized_dependency_mode="any_event" and active_execution_policy="on_each_event".

UI Behavior

The inspector provides a structural summary for the OR behavior.

Editor Display

The canvas card is rendered by this block through node_card.html. It exposes the OR trigger summary while the shared editor shell keeps ports, dragging, status, and graph links generic.

Modal

block_modal.html is owned by this block and rendered by the generic modal contract. It shows block state and lets users edit supported title/config fields through generic bindings. The modal declares data-block-runtime-refresh="autonomous"; it is a lightweight block-owned surface so runtime polling does not replace the open modal or overwrite draft generic fields before Apply.

Maintenance Notes

Any fingerprint or state-key change can affect deduplication and active runtime behavior. Update active runtime event tests when changing this block.

Compatibility policy

compatibility.json records HackInvent's verified BloxSmith versions and test evidence. Only the versions listed above have been verified, using the block-owned suites in a bundled-block test installation. This is not a certification of managed-package installation, every browser/OS, or live provider availability. Other framework versions are unverified, not necessarily incompatible.

The block-version badge follows model.json, not a published Git tag. unversioned means that no block release version is declared; no number is inferred from the framework version. The framework still uses model.json for its runtime/install contract; the tester-owned JSON does not replace it. Official integration tests run in the private bloxmith-blocs workspace. Test helpers and the proprietary framework are not bundled in this public block repository.