Trails / From Emergency to Resolution

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.

18 parts ~262 min total exec product engineering business operations support
Start the trail →

Parts

  1. Part 1

    When the Fiber Goes Dark

    The emergency callout problem in outside plant fiber construction

    14 min exec product engineering
  2. Part 2

    From Contractor to Operator

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

    12 min exec product engineering
  3. Part 3

    The Shape of the System

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

    16 min product engineering
  4. Part 4

    Two Tenants, One ECO

    Why Osprey Strike needs a two-dimensional tenancy model instead of a generic SaaS checkbox

    17 min engineering business operations
  5. Part 5

    Events All the Way Down

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

    18 min engineering
  6. Part 6

    The ECO Lifecycle

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

    16 min product engineering
  7. Part 7

    The Last False Complete

    Why field workflows need a soft-complete state before they earn the right to be done

    15 min engineering operations
  8. Part 8

    Boundary Objects for Operational Software

    How ECOs, job numbers, statuses, and timelines carry meaning across teams that do not share a tool

    16 min engineering business operations
  9. Part 9

    Running in Production

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

    16 min engineering operations
  10. Part 10

    What's Next

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

    14 min exec product engineering
  11. Part 11

    NOC-Scoped Does Not Mean NOC-Owned

    Why Strike owns telephony plumbing even when Twilio context is partitioned per NOC

    12 min engineering business operations
  12. Part 12

    Twilio SMS Global Settings

    How Strike sysadmins configure SMS delivery callbacks and Twilio opt-out handling without guessing the webhook URL

    13 min engineering operations
  13. Part 13

    Osprey Strike Twilio Deploy Runbook

    Where the manual Twilio-hosted pager artifacts live, how to deploy them, and how not to create the wrong Flow

    15 min engineering operations
  14. Part 14

    Finding Osprey Server Logs

    How new developers should use Grafana first, then kubectl through the EKS tunnel when they need live cluster evidence

    10 min engineering operations
  15. Part 15

    Render Is a Shared Request Budget

    What calls Render, when it calls, and why one credential—not one cluster—sets the ceiling

    18 min engineering operations product
  16. Part 16

    Osprey Strike API Architecture: The Developer Map

    How the API server turns emergency callouts into auditable, recoverable workflow

    16 min engineering operations
  17. Part 17

    What Render Actually Sends

    Four endpoints, what each one really returns, and how to find out the next thing the spec won't tell you

    11 min engineering
  18. Part 18

    Osprey Strike Mock Server Cookbook

    Pick the mock scenario you need, run it, and know what to look for in Strike

    13 min operations support engineering