Implementation

Bluesky-owned Osprey effects receiver

Reported Kafka-to-receiver-to-Ozone path applies platform decisions; distinguishes engine outputs from local enforcement.

What the records show

OspreyBluesky-owned Osprey effects receiver

was reported to send results through Kafka to a local receiver

2026-02-04 – 2026-02-04

Case study describes atproto events into Osprey, custom functions, Kafka and a Bluesky-owned effects receiver calling Ozone. Engine outputs become actions through this separate operator implementation.

BlueskyBluesky-owned Osprey effects receiver

owns the reported effects receiver and local enforcement choices

2026-02-04 – 2026-02-04

Published account locates effects at the platform. No grant authority, upstream template author or ROOST repository permission is shown issuing a specific content order through this path.

Further reading

Named adopters: Osprey at Discord and Bluesky

Read the original source 1

What the connections say

2 relationships
1

Ospreywas reported to send results through Kafka to a local receiverBluesky-owned Osprey effects receiver

2026-02-04 – 2026-02-04

Reported by the cited source

Case study describes atproto events into Osprey, custom functions, Kafka and a Bluesky-owned effects receiver calling Ozone. Engine outputs become actions through this separate operator implementation.

Read the original source 1