Decisions written down first. Then the plan, then the build.
~/digital-vision/work/brief.md
The problem
Digital Vision is one person with a lot of work in flight. The planning behind it is a set of plain files in one repository, read at the start of every working session and kept current as the work happens, so nothing depends on memory.
A one-person studio runs several products, client builds and conversations at once. The thinking behind each one has to survive a week away, a switch between two Macs and a fresh working session that starts with no memory at all.
An earlier tracking setup went quiet in the summer of 2026 because moving machines broke it: it pointed at folders that no longer existed and failed without saying so. The rebuild started from that failure.
~/digital-vision/work/build.md
The method
Every decision goes into one shared file, with its date and the reason next to it. Documents open with what was decided and what a reader must not get wrong; the history comes after, so nobody has to rebuild a decision from a discussion.
Before anything is built, the proposal goes through five checks. They exist because each one matches a real mistake: a design that looked complete and was wrong once traced through the running code, a tool built when an existing one already did the job.
Nothing new unless what already exists cannot do the job.
Trace it through the real thing before saying it works. "It should" is not a result.
List what is already there before designing anything.
Decisions first, reasoning after.
Who pays, and what do they pay today? Answered from outside research before building anything meant to earn.
~/digital-vision/work/kept-current.md
What stays current
Three files carry the day-to-day picture. Each has one job, and each is updated when the fact arrives rather than at a weekly tidy-up.
Context: the decisions, the open questions and the shared terms the business uses, each decision dated and quoted from the person who made it.
Pipeline: one row per conversation that could become work: what was asked, what was promised, what needs chasing. Anything not known is marked as not known.
Session log: one line per working session that changed a product's status, a promise or a contact, in the form date, project, what changed.
~/digital-vision/work/result.md
Where it stands
Time is counted in days worked per piece of work, not hours. A day counts when anything was logged or committed for that work that day, and the figure is always shown as a minimum. Hours were dropped on purpose: any rule that guesses where a working session ended undercounts long reading, testing and waiting on slow jobs.
Those days sit beside a record of what each piece of work returned, so the question of where the next week goes is answered from evidence. Unpaid groundwork is counted as groundwork, not waste, because a lot of it pays off later.
1,200+commits to the planning repository since April 2026
5checks before anything is built
1home for every document
~/digital-vision/work/design.md
Design decisions
Plain Markdown, not a planning app. Markdown can be read by a person, diffed line by line, and read in full by Claude at the start of a session without an export step or an account.
One file per job, with a version and a last-updated date at the top of each. A small number of well-named files beats a deep folder tree when the main reader arrives with no context and has to find the right page quickly.
One home per document. Never a second copy elsewhere; to share, send a copy or a link.
If it is not pushed, it is not saved. Documents are committed and pushed in the session they are written.
Names say what and when: kebab-case, with a date on anything that is a snapshot.
Fail loudly. If something the system reads is missing, it says so instead of showing an empty page.
~/digital-vision/work/stack.md
Architecture
The single source of truth is a private Git repository on GitHub. A filing map decides where each kind of document lives (client folders, meetings, planning, decisions, platform pitfalls), so filing is a lookup, not a judgement call made fresh each time.
Claude's global instructions import the repository's own instructions file, so every session on either Mac starts by reading it. That file points to the deeper documents and says when each one is worth reading, which keeps the start of a session short.
Session hooks do the bookkeeping. At the start of a session, the shared configuration and memory are pulled from GitHub. On every prompt and tool call, a small script appends one line to that Mac's work log. At the end, changes are committed and pushed, and the pipeline file is synced to the dashboard. Every hook exits cleanly on failure, so bookkeeping can never block the work.
~/digital-vision/work/dashboard.md
Mission Control
Mission Control is a local dashboard over the same files, run as a background service on the Mac. It has views for today, the portfolio, the pipeline, releases, documents, search, a wiki and health.
Its wiki is rebuilt from the repository every morning. Once a week a self-check tests what can be proved from outside (sites responding, store listings, dates on open proposals, the last activity in each repo) and flags anything that disagrees with the files. That check is the second of the five rules applied to the planning system itself.
~/digital-vision/work/security.md
Security and privacy
The repository is private. The filing rules keep passwords, keys, environment files and bank details out of it entirely, and personal documents stay out too.
The work log records the time, the Mac and the project folder for each event. Each Mac writes its own file, so two machines never edit the same one, and the files travel by Git rather than a shared drive.
~/digital-vision/work/hosting.md
Hosting and delivery
GitHub holds everything and both Macs pull from it, which means there is no server to keep alive for the planning itself. The dashboard runs locally, and a hosted version of the studio's dashboard reads the same files from GitHub, so the two cannot drift apart.
~/digital-vision/work/next.md
Got something like this?
Tell me what you need and I'll tell you what it would take.