Architecture
Three Gates, One Identity
How Osprey Strike authenticates browsers, webhooks, and upstream APIs without collapsing them into one trust boundary
Featured Trails
All Trails →Operating Q
How Q evolved from a useful experiment into a sandboxed operational teammate with real lanes, safer boundaries, and cleaner delivery.
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.
Featured Cairn
Three Memories, One Q
Why the current OpenClaw design keeps long-term memory private to each lane and shares knowledge through docs instead
Read CairnRecent
Architecture
The Only Locked Door
How OpenClaw gives Q a real computer without letting public channels rewrite the machine it runs on
Domain
Fiber Industry Acronym Finder
A table-based quick reference rebuilt from the Fiber Industry Notion database
Architecture
Two Tenants, One ECO
Why Osprey Strike needs a two-dimensional tenancy model instead of a generic SaaS checkbox
DevOps
Surviving the Upgrade
What happens when the ground shifts under a running AI agent — and how three days of misdiagnosis led to a five-minute fix