Skip to content
Corduroy Labs
Update · hello@corduroy-labs.ai

Quiet by design.

Published September 12, 2026 · Truckee, California

A still alpine pond reflecting granite peaks and scattered pines under a clear Sierra sky, Twenty Lakes Basin, California.

Hello from Corduroy Labs.

We build AI operations for a living. Last week we shipped a website with no AI in it at all. No writing assistant, no image analysis, no generated alt text, no chat widget in the corner. Nothing. On purpose.

The client is a teenage musician close to the studio — a songwriter who also draws, photographs, and writes. She needed a home for the work: a place to publish songs, art, photos, and words, where she controls every pixel and every sentence. Her one non-negotiable, delivered with the certainty teenagers reserve for things they are right about: no AI anywhere near the work. She writes everything herself.

An AI studio taking that brief is not a contradiction. It might be the most clarifying brief we have taken all year.

The brief was a person

Strip the jargon and the requirements were: only two people can ever sign in — her and one parent. Nobody else can make an account, ever. No comments. She publishes from her phone, because that is where teenagers live. And the site should feel like a gallery, not a feed — the work on the walls, the interface out of the way.

That last one came from looking at how the best independent musicians and artists actually present themselves online. The pattern across all of them: one hero moment per visit, grids for depth, navigation tucked into the corners. The strongest artist sites are the ones where you cannot remember the interface afterward, only the work.

No AI is a feature, not an absence

Respecting “no AI” turned out to mean more than deleting the generate buttons. If her words and images are hers alone, then they should stay hers on the open web too — so the site ships with AI-training crawlers blocked at the robots layer and a no-AI signal in every response header. Yes, that list includes the crawler of the company whose tools helped build the site. A boundary you only enforce against other people’s bots is not a boundary.

This is the same principle we wrote about in boundaries make the agent trustworthy, pointed the other direction. There, boundaries protect the operator from the agent. Here, they protect an artist from the ecosystem. Consent is the design primitive in both.

Privacy lives in the pipeline, not the policy

The client is young, and the site shows photographs from her life. So the privacy work happens where it cannot be forgotten: in the upload path. Every image is re-encoded on the server before it touches storage — camera metadata stripped, GPS coordinates gone, orientation baked in. There is no setting to get wrong, no checkbox to forget. A photo published from a phone simply cannot leak where it was taken, because the location data never survives the first hop.

No analytics. No trackers. Video embeds route through the no-cookie player domains. The site does not know who visits, and that is not a missing feature either.

Two stages, one system

She could not choose between two moods, so she did not have to. The site has two complete visual identities — a warm gallery-white where the art hangs in daylight, and a near-black stage where the music glows — and she switches the whole site between them with one control in her studio. Under the hood they are the same token system wearing different values: every component reads variables, no component knows which theme is live, and a third identity someday is a block of tokens and one registry entry.

It is the same architecture discipline we apply to agent systems, applied to typography and color. Separate the identity from the machinery and both get simpler.

AI in the workshop, not in the product

Here is the part that belongs on this blog. The site contains no AI — and it was researched, designed, coded, deployed, and is now monitored by agents. The design research surveyed the current landscape of musician and artist sites. The build forked our own production stack and deleted every AI pathway from it. The deploy went through the same fail-closed gate as everything else we ship. By the next morning, the daily operations agent had folded the new site into its health checks and traffic review, where it will be watched every day, indefinitely, without anyone asking.

The workshop is full of AI. The product has none. Those are different rooms, and knowing which room you are standing in — and which one the person in front of you actually asked for — is most of the job. Sometimes the most agentic thing a studio can do is build something quiet, lock the bots out, and hand a young artist the keys.

She published her first song that evening. We were not involved, which was the entire point.