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
Topic
Tools
34 cairns tagged "tools"
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
MCP Is an Interface Boundary
Why agent tools need typed contracts, policy, and confirmation instead of clever prompt glue
Please Do Not Worship the Robot
A theatrical reminder that Q is useful because the team makes him show his work
What Q Can Help With
A practical map of Q's Slack, repo, Notion, Google Workspace, and GitHub capabilities
Using Q from Slack
How to ask for help, what to expect, and where the observer sandbox draws the line
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
Your Box and Your Trust Model
What runs on your machine, and how much rope you give the agent — one has a project answer, the other is yours
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
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
How Conduit is Shaped
The architecture that lets one consumer site read N project repos without coupling either side to the other
The Only Locked Door
How OpenClaw gives Q a real computer without letting public channels rewrite the machine it runs on
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, tokf, and the small CLI multipliers that compound across every session
Just: One Place to Discover
The discovery surface that turns project incantations into a known place humans and agents both look first
How We Build Here
What's changed about writing production software, and what this trail is going to teach you
From Plan to Pull Request: A Day on Strike
One realistic feature, end to end, with every prior cairn put to work
Codex as Second Opinion
When a single model is bluffing or stuck, a second model is the cheapest unblock available
Claude Code as Daily Driver
The agent harness most of us reach for first, what we run inside it, and the alternatives that are perfectly fine
Beads, the Backbone
The CLI issue tracker that gives an agent a memory that survives the next compaction
From Intake Folder to Project Memory
A design pack for turning KCCI project folders into a managed, searchable, auditable knowledge system
What Q Remembers
Why Q feels like one teammate while memory still follows the room where the work happened
Fiber Industry Acronym Finder
A table-based quick reference rebuilt from the Fiber Industry Notion database
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 Weekend Knowledge Base
Building a self-improving knowledge system from zero in under 8 hours of actual effort — and what that says about internal tooling in 2026
The Memory Problem
Why AI Agents Forget Everything and What To Do About It
The Quiet Teammate
What Happens When an AI Agent Picks Up the Work Nobody Owns