Osprey Strike Mock Server Cookbook
Pick the mock scenario you need, run it, and know what to look for in Strike
Topic
Operations
13 cairns tagged "operations"
Twilio SMS Global Settings
How Strike sysadmins configure SMS delivery callbacks and Twilio opt-out handling without guessing the webhook URL
Render Is a Shared Request Budget
What calls Render, when it calls, and why one credential—not one cluster—sets the ceiling
Field Geometry Carries Work Intent
Why points, lines, and polygons should preserve dispatch, evidence, and as-built meaning
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
The Splice Is the Network's Truth Table
Why closure-level connectivity deserves first-class data modeling, not spreadsheet afterthoughts
Render Networks as the Construction Execution Layer
Why Strike should treat Render as the field execution system, not just a task sink
NOC-Scoped Does Not Mean NOC-Owned
Why Strike owns telephony plumbing even when Twilio context is partitioned per NOC
The As-Built Is the Network Model
Why fiber closeout data should become the operating record, not a folder of drawings
The Trace Is the Baseline
Why fiber test results should be operational data, not closeout paperwork
Projections Are Product Decisions
Why read models are where operational software decides what the truth should look like
Boundary Objects for Operational Software
How ECOs, job numbers, statuses, and timelines carry meaning across teams that do not share a tool
The Last False Complete
Why field workflows need a soft-complete state before they earn the right to be done