Internal pub/sub for neural network component communication using pg.

This module provides a thin wrapper around OTP's pg (process groups) for communication between network components (cortex, sensors, neurons, actuators). It uses pg's built-in group management with network-specific naming conventions.

Design Philosophy

Network components communicate through events rather than direct calls: - Publishers don't need to know subscriber PIDs - Subscribers don't need to know publisher PIDs - New observers can be added without modifying existing code - Events form a clear contract between components

Event Types

| Event | Publisher | Description | |-------|-----------|-------------| | evaluation_cycle_started | cortex | When sync is triggered | | sensor_output_ready | sensor | When sensor produces output | | neuron_output_ready | neuron | When neuron fires | | actuator_output_ready | actuator | When actuator produces output | | backup_requested | cortex | When weight backup is needed | | network_terminating | cortex | When network is shutting down |

Usage

Initialize pubsub for a network (typically in cortex): network_pubsub:init(NetworkId)

Subscribe to events: network_pubsub:subscribe(NetworkId, evaluation_cycle_started) network_pubsub:subscribe(NetworkId, [sensor_output_ready, neuron_output_ready])

Publish events: network_pubsub:publish(NetworkId, evaluation_cycle_started, #{cycle => 1}) network_pubsub:publish(NetworkId, sensor_output_ready, #{from => SensorPid, signal => Signal})

Receive events in subscriber: receive {network_event, evaluation_cycle_started, Data} -> %% Handle evaluation start ... end

Implementation

Uses OTP pg (process groups) with group names of the form: {network_pubsub, NetworkId, Topic}

This allows multiple network instances to have independent pubsub.