--- title: "How we work: Walter ยท Woodshack" description: "Walter is the server that runs the shop. He holds every project's context, keeps a memory that stays current, and runs a review gauntlet nothing skips." url: https://woodshack.net/walter/ site: Woodshack (https://woodshack.net/) about_this_site: https://woodshack.net/for-ai/ --- How we work # Meet Walter. The shop's command center. Walter is one server that holds every project we touch and sharpens a two-person shop into something closer to a small engineering department. He's the honest answer to "how do two people do all of this?" He isn't for sale, because he's built around exactly how we work. We'll happily build you one of your own. Why it matters to you ## A small shop with a big shop's discipline. You don't buy Walter. You benefit from him. When you hand us a problem, it gets built inside a system with the memory, the review discipline, and the operational care of a much larger team, and delivered with the directness of working with the two people who actually wrote the code. That's the whole idea. Use the best tools available, keep humans doing the engineering, and let the machine handle everything that isn't the interesting part. Want one of your own? ## Not a chatbot. A supercharger built for your business. Walter isn't for sale because he's purpose-built for us. The same idea, built around your business, is something we'll happily talk about. That doesn't mean a chat window on your website. It means a system that knows your projects, your customers and your history, is wired into the tools you already use, remembers the lessons your team has paid for, and puts the right one in front of the right person before they hit the same problem twice. - **Built around how you actually work,** not a generic assistant you have to work around. - **Connected to your real systems:** email, tickets, project tracking, documents, the CRM. - **A memory that keeps itself current,** so knowledge doesn't walk out the door with whoever learned it. - **People stay in charge.** It proposes, a person decides, and anything that can change things is fenced in by design. [Talk to us about yours](https://woodshack.net/contact/?topic=walter#form) Human in the loop ## We still do the engineering. All of it. This is the part that matters, so we'll be plain about it. Walter makes us faster and sharper. He does not do the thinking. We architect the system before a line is written. We plan the build, review the code, write the tests, run the servers, and maintain what ships. Today's best AI models are part of how we move quickly, and we treat them as what they are: powerful instruments that we point, that speed up every step and replace none of them. This is not a vibe-coding shop. Under the hood ## For the technical folks. The rest of this page is how Walter actually works: the memory, the review gauntlet, the design choices and the phone-first front door. Skip it if you just want the thing fixed; the short version is above. What he is ## A workshop that remembers everything. Every project lives in one place: its code, its history, where it runs, what's fragile about it, and every lesson we've learned the hard way keeping it alive. Walter holds all of that and puts the right piece of it in front of us at the right moment. He never forgets a detail of a project we touched eight months ago. He surfaces the exact trap we hit last time before we hit it again. And he lets us run the whole shop, from architecture to a production fix, from a laptop or a phone. Design choices ## The ideas we're proud of. A few of the design choices that make Walter more than a folder full of scripts. ### Memory that writes itself back A lesson learned once gets written into the machine's own playbooks the same day, so it reaches every future session automatically. Knowledge that doesn't evaporate when the laptop closes. ### Cross-lab review as signal Models from different companies review each other's work. Their disagreement isn't noise to smooth over. It's a map of exactly where a human's judgment is needed. ### It audits its own decay Scheduled jobs mine each day's work for lessons that never got written down, and each week flag knowledge going stale or projects going quiet. The system looks for its own rot before we have to. ### A local brain, always available A small language model runs on the box itself, so the everyday helper keeps working even if every cloud vendor is unreachable. It can only propose from a fixed menu of safe actions. Its worst failure is "unhelpful," never "dangerous." ### One writer, no exceptions By construction, exactly one agent can change code, and every reviewer is read-only. The safety isn't a policy someone remembers to follow. It's built into how the machine is wired. The gauntlet ## Nothing ships without passing review. Whatever gets written, by us or drafted with a model, runs the same gauntlet before it reaches you. The reviewers come from rival AI labs: different models have different blind spots, and where they disagree is exactly where we look closest. The reviewers only advise. Not one of them can write a line or push a commit. 1. **The Floor**: Static analysis on every repo, always on. 2. **The Gatekeeper**: Automated code review on every change. 3. **The Panel**: Cross-lab model review, scaled to the risk. 4. **The Inspector**: A sandboxed reader with no write access. 5. **A person**: Architect, reviewer, and the only one who ships. The door ## The whole shop, from a phone. Walter has a web front door, built mobile-first on purpose. Most of the useful moments are not at a desk: a question arrives at dinner, something needs checking on a train, a fix wants shipping before we get home. Nearly everything in it started as a command someone was tired of typing on a phone keyboard. The rule since: if you wouldn't want to do it from a bus, it doesn't belong in the door. It sits behind a real login, with long-lived sessions we can revoke from anywhere and an audit trail. It exposes genuine power, so the security is load-bearing rather than decorative. The result is that the shop doesn't have office hours. Picking up a project mid-thought takes about ten seconds, from wherever we are. - **Sessions.** Live terminal sessions, exactly as we left them, resumable from any device. - **Project registry.** Every project, what it is, where it runs, and what state it's in. - **Local sites.** The development site fleet, with what's actually running shown as evidence rather than assumed. - **Files.** Browse the box, pull a file down, drop one in. Credentials and key directories are refused outright. - **Notes.** Quick capture for the thought that arrives at the wrong moment, where a later session can turn it into a real ticket. - **Health.** A light in the corner watching disk, memory, services, and whether the backups are actually fresh. ## Bring us something interesting. A messy integration, a tool that doesn't exist yet, or a codebase that needs a real set of eyes. This is the shop it gets built in. [Bring us a problem](https://woodshack.net/contact/)