Updates from the studio.
This is where we share practical notes from building agent-first foundations: open systems, AI workflow design, role-based operations, routing, approvals, and the small operational habits that make people and agents work better together.
Expect calm, operator-led writing. Less hype, more architecture you can actually use.
Build logs, essays, and practical operating notes.
An agent that shows its work.
Cords, our COO agent, now runs the @corduroy-labs.ai Bluesky feed within audited caps. Notes on giving an agent room to move, one honest failure we caught in real time, and why observability is the substitute for control.
Deploys that refuse to break the site.
We replaced our static-site deploy with a fail-closed script: build, verify, scrub for strings that should never go public, then swap atomically. If any gate fails, the live site never notices. Notes on why rsync --delete is a loaded weapon and what we do instead.
The studio, machine-readable.
This week we shipped RSS, JSON Feed, an llms.txt, and a small MCP server for the studio. Notes on why a small business site should be legible to agents, why we picked all three, and the pattern the MCP server is really trying to demonstrate.
Self-improvement, with direction.
We let the agent get better at its job this week, but on a leash. It now checks its own claims against the world before showing them to us, and it proposes its own next reference documents — drafts in a folder until we approve them by email reply.
The agent becomes a teammate.
Today we gave the agent a shared workspace and a small cabinet of specialized minds. A shared vault, end-to-end encrypted, syncing on every device. A router that picks the right model for the job. The difference between a tool you operate and a teammate you collaborate with.
Boundaries make the agent trustworthy.
Notes from a week of operational hardening: narrowing what the agent can touch, writing the rules down, verifying reality instead of configuration, and giving the agent some real context about the operator.
Take a breath. You can become agentic-first without the stress.
Our first update on building a practical operating layer for people and agents, starting with the workflows that slow work down.
Want help building your operating layer?
Bring us the workflow, inbox, routing gap, or open systems stack you want to make ready for people and agents.