Trails / Osprey Strike — From Emergency to Resolution

Osprey Strike — From Emergency to Resolution

A seven-part series exploring Osprey Strike from problem space to production — what emergency callout management is, the domain landscape that shapes it, how the system solves it, and why the architecture looks the way it does.

7 parts ~106 min total exec pm engineer architect ops
Start the trail →

Parts

  1. Part 1

    When the Fiber Goes Dark

    The emergency callout problem in outside plant fiber construction

    14 min exec pm engineer
  2. Part 2

    From Contractor to Operator

    How O&M agreements and CLEC licensing are reshaping who runs fiber networks

    12 min exec pm engineer
  3. Part 3

    The Shape of the System

    How Osprey Strike is structured, from mono-repo to multi-tenant

    16 min pm engineer
  4. Part 4

    Events All the Way Down

    Event sourcing and CQRS in Osprey Strike — the architecture, the migration, and the escape hatch

    18 min engineer architect
  5. Part 5

    The ECO Lifecycle

    From outage detection to field resolution — how an emergency callout moves through the system

    16 min pm engineer
  6. Part 6

    Running in Production

    From Cloudflare edge to PostgreSQL — how Osprey Strike deploys, authenticates, and scales

    16 min engineer ops
  7. Part 7

    What's Next

    Where Osprey Strike stands today, what's coming, and the questions that still need answers

    14 min exec pm engineer