The As-Built Is the Network Model
Why fiber closeout data should become the operating record, not a folder of drawings
Topic
Domain
13 cairns tagged "domain"
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