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.
Start the trail →Parts
-
Part 1
When the Fiber Goes Dark
The emergency callout problem in outside plant fiber construction
-
Part 2
From Contractor to Operator
How O&M agreements and CLEC licensing are reshaping who runs fiber networks
-
Part 3
The Shape of the System
How Osprey Strike is structured, from mono-repo to multi-tenant
-
Part 4
Two Tenants, One ECO
Why Osprey Strike needs a two-dimensional tenancy model instead of a generic SaaS checkbox
-
Part 5
Events All the Way Down
Event sourcing and CQRS in Osprey Strike — the architecture, the migration, and the escape hatch
-
Part 6
The ECO Lifecycle
From outage detection to field resolution — how an emergency callout moves through the system
-
Part 7
The Last False Complete
Why field workflows need a soft-complete state before they earn the right to be done
-
Part 8
Boundary Objects for Operational Software
How ECOs, job numbers, statuses, and timelines carry meaning across teams that do not share a tool
-
Part 9
Running in Production
From Cloudflare edge to PostgreSQL — how Osprey Strike deploys, authenticates, and scales
-
Part 10
What's Next
Where Osprey Strike stands today, what's coming, and the questions that still need answers