Finding Osprey Server Logs
How new developers should use Grafana first, then kubectl through the EKS tunnel when they need live cluster evidence
Topic
DevOps
33 cairns tagged "devops"
Crabbox Commands Reference
The quick command map for setup, warm boxes, gates, screenshots, tunnels, and cleanup
Evals Are Production Tests
How to turn agent judgment into a quality gate the team can actually improve
Crabbox on qs-mac-studio
How isolated branch boxes run tests, full stacks, screenshots, and browser tunnels on the Mac Studio
Trace the Work, Not Just the Error
Why agentic operations need causal telemetry, not bigger log piles
The Work That Writes Itself
Why we built Conduit, and what it gives the team that nothing else did
How Conduit Runs
Onboarding a project, surviving operational failure, and what's deferred until the system grows
Osprey Strike API Architecture: The Developer Map
How the API server turns emergency callouts into auditable, recoverable workflow
Preview Environments Are Operational Contracts
Why every pull request needs a runnable, shareable, policy-bound place to prove what changed before production has to care
CI/CD Maturity in the Age of Agentic Engineering
How a small high-throughput team can evolve from CI to continuous delivery to selective continuous deployment without outrunning its safety systems
GitHub Events Routines
How PR review webhooks leave GitHub, cross AWS, and wake OpenClaw routines on the local host
Easy Installation
The shortest path from a fresh laptop to a working Osprey Strike checkout
What Q Can Help With
A practical map of Q's Slack, repo, Notion, Google Workspace, and GitHub capabilities
Runbooks Are Interfaces
How to write operational instructions that humans and agents can both execute
Operator's Guide to Q
The private lanes, debug channels, maintenance rituals, and boundaries behind the Slack teammate
The Status Light
How Q announces maintenance, checks for active work, and proves it came back online
Where the Work Lives
Coordinating between GitHub and beads, for the people doing the planning and the people doing the building
The Workshop
A map of every tool between you and a shipped pull request, and where each one comes from
How Conduit is Shaped
The architecture that lets one consumer site read N project repos without coupling either side to the other
AI-Native Engineering: Can You Migrate Incrementally?
Why bolting agents onto an unchanged SDLC plateaus at 5–20%, and how the 10x teams rebuilt their operating model
Working in Parallel (Mostly)
Worktrees, the bd worktree warning, and the one Docker constraint we have not solved yet
Timbers, the Ledger
The second ledger every commit needs — one line of what, why, and how, searchable forever
Quiet Power Tools
RTK, Ponytail, tokf, and the small multipliers that compound across every session
Quality Gates: The Contract That Lets You Move Fast
Lint, types, tests, coverage, audits — the deterministic constraints that make agent-driven work safe to ship
Just: One Place to Discover
The discovery surface that turns project incantations into a known place humans and agents both look first
From Plan to Pull Request: A Day on Strike
One realistic feature, end to end, with every prior cairn put to work
Beads, the Backbone
The CLI issue tracker that gives an agent a memory that survives the next compaction
Three Gates, One Identity
How Osprey Strike authenticates browsers, webhooks, and upstream APIs without collapsing them into one trust boundary
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
Timbers
A Development Ledger for the Age of AI Agents
The Shape of the System
How Osprey Strike is structured, from mono-repo to multi-tenant
Running in Production
From Cloudflare edge to PostgreSQL — how Osprey Strike deploys, authenticates, and scales
The Quiet Teammate
What Happens When an AI Agent Picks Up the Work Nobody Owns