DV.OS 8.X/WORK/INTERNAL TOOLS
Skip to the case study
Digital Vision
~/digital-vision/work/internal-tools.md

Internal tools · Digital Vision

A one-person studio,
run with tools I built for it.

~/digital-vision/work/walkthrough.md

Walk through it

Tap the pulsing marker, or use Next.

Open it full screen →

~/digital-vision/work/brief.md

The problem

Digital Vision is one person doing the work of a small team. What makes that possible is a set of tools built for the studio itself: they remember the business, check the work before it ships, count the days, and show clients what they are getting before it goes live.

A solo studio loses time in the same places every week: rebuilding context at the start of a session, catching the same kinds of bug late, guessing where the days went, and explaining a build to a client in words when they need to see it.

Each tool here started from one of those losses. None was built until what already existed could not do the job.

~/digital-vision/work/build.md

The toolkit

  • DV OS: the studio's memory. Standards, decisions, platform pitfalls and every document, in one repository that each working session reads first.
  • Release gate: one command runs five reviews before anything ships (a grumpy senior reviewer, security, resilience, a cold read as the platform's CTO, and a check that every claim in the copy is true), then checks versions and a clean rebuild. The answer is GO or BLOCKED, with the reasons listed.
  • Hosted DV OS: a private dashboard on Wix Headless with separate sign-ins and views for the owner, the team and clients.
  • Walkthroughs: a reusable click-through of a new site or app in a phone or laptop frame, with numbered pins and a tap marker. The walkthroughs on these case study pages run on it.
  • Work log: records which days went to which project, automatically, so time is counted rather than guessed.
~/digital-vision/work/public.md

Two you can see

Web Clarity is a free AI website diagnostic. It reads a site, Ava (the AI web strategist) asks about the business in a short chat, and a report scores nine areas out of ten with the fixes that matter most.

Prospector finds businesses that fit a brief, checks each one against its own website and public records, and drafts one short, factual first email per business. A person approves every email before it goes.

~/digital-vision/work/result.md

Where it stands

DV OS, the release gate, the work log and the walkthroughs are in daily use. The hosted dashboard is live for the studio. Web Clarity is public. Prospector is working but has not been used for outreach yet: the first send waits for a legal review of its sending rules.

  • 5reviews before every release
  • 1,200+commits to the studio's memory since April 2026
  • 108automated tests across the dashboard's access rules and Prospector's sending rules
  • 29days of build time, from the studio’s work log (calls and planning not counted)

How it came together: building the studio's brain, the four-reviewer gauntlet, verify everything.

~/digital-vision/work/design.md

Design decisions

Plain files over a database wherever a person also needs to read the thing. DV OS is Markdown in Git, so every change has a history and Claude can read it in full at the start of a session without an export.

Days, not hours. The work log counts a day as worked on a project when anything was logged for it that day. Any rule that guesses where a session ended undercounts reading, testing and waiting on slow jobs, so the figure is always shown as a minimum.

Show, don't describe. The walkthrough engine puts real screens in a device frame with pins on what matters, because a client understands a build faster by clicking through it than by reading about it.

~/digital-vision/work/stack.md

Architecture

DV OS and the work log. Claude's global instructions import DV OS, so every session starts by reading it. Session hooks append one line per prompt and tool call to a log file per Mac (time, machine, project folder), so two machines never edit the same file. At the end of a session the log and configuration are committed and pushed, and the last day worked per app is written for the dashboard.

Hosted DV OS. A Wix Managed Headless site built with Astro. Wix handles sign-in and holds who may sign in and their role; the records stay in the business's own GitHub, read through the GitHub API and saved back as commits named after the person who made the change. A save that collides with another is retried on the newer file.

Web Clarity. A Base44 app: a React front end and Deno backend functions that take the site address, crawl the site, run the chat, score the report and clean up old records. The chat and scoring call Claude through the Anthropic API; the crawl also runs a page-speed check. A de-identified summary of each finished report (no name, email or transcript) goes to a small Cloudflare Worker and D1 database, so sites can be compared over time.

Prospector. Also on Base44. Every decision about who qualifies and what an email says lives in shared modules with offline tests, used by the backend functions that run campaigns, send, read replies and tidy up. Scheduled workflows run a weekly finder, a daily check for replies and follow-ups, and a monthly clean-up.

~/digital-vision/work/security.md

Security and privacy

Hosted DV OS. Anyone not on the owner's list sees nothing, even with an account, and team and client roles apply only once Wix has confirmed the person's email. Every form post is checked as coming from the site itself. The GitHub keys are fine-grained, limited to named repositories with read and write on contents only, and stored as Wix secrets; the client view uses a separate key, so it cannot reach the business's own records. Uploads are checked by their first bytes, capped in size and never overwrite. The access rules have their own tests.

Web Clarity. Report records are readable and writable by admins only. The one public way to read a report is a backend function that checks a session token: 32 random bytes, of which only a hash is stored, valid for seven days. It removes the token hash, IP address and contact details before anything reaches the browser. New diagnostics are rate-limited per IP address by the hour and by the day, with a daily ceiling overall, and a scheduled job deletes records older than twelve months. The crawler refuses private, loopback and link-local addresses, follows at most three redirects, and stops at a size and time limit.

Prospector. Each account's records are kept separate, and the functions that run campaigns, find leads, read replies and switch accounts check for an admin on the server. It reads pages through a fetcher that refuses private and internal addresses. Gmail access is send-only. Before every send the code refuses personal webmail, anyone on the do-not-contact list, anyone who has replied or closed, and anything over the daily cap, and it allows one follow-up at most.

~/digital-vision/work/hosting.md

Hosting and delivery

DV OS lives on GitHub and both Macs pull from it, so there is no server to keep up for the memory itself. The hosted dashboard runs on Wix's hosting and CDN. Web Clarity and Prospector run on Base44's hosting, with their secrets held in the app's settings rather than in code, and Web Clarity's comparison store runs on Cloudflare's network.

Prospector's changes are made in its repository first, tested offline, uploaded, and checked in the live app after publishing.

~/digital-vision/work/next.md

Got something like this?

Tell me what you need and I'll tell you what it would take.

More work →