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
Topic
Domain
19 cairns tagged "domain"
Field Geometry Carries Work Intent
Why points, lines, and polygons should preserve dispatch, evidence, and as-built meaning
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
Osprey Strike API Architecture: The Developer Map
How the API server turns emergency callouts into auditable, recoverable workflow
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
Fiber Industry Acronym Finder
A table-based quick reference rebuilt from the Fiber Industry Notion database
Two Tenants, One ECO
Why Osprey Strike needs a two-dimensional tenancy model instead of a generic SaaS checkbox
The Lakehouse
What Osprey Vantage is actually building, and why it looks the way it does
From Contractor to Operator
How O&M agreements and CLEC licensing are reshaping who runs fiber networks
When the Fiber Goes Dark
The emergency callout problem in outside plant fiber construction
What's Next
Where Osprey Strike stands today, what's coming, and the questions that still need answers
The Shape of the System
How Osprey Strike is structured, from mono-repo to multi-tenant
The ECO Lifecycle
From outage detection to field resolution — how an emergency callout moves through the system
Events All the Way Down
Event sourcing and CQRS in Osprey Strike — the architecture, the migration, and the escape hatch