You're at the hardware store on a Saturday morning, halfway through a deck repair, and you cannot remember whether last year's project used 2-1/2" or 3" deck screws. The receipts are in a pile somewhere. The Amazon order history is searchable but only kind of. The note you took on your phone is buried in a chat thread. So you guess, buy a box of each, and end up with seventy extra screws in the garage.
Most DIY-ers run into this version of the problem. The information about every project — what you bought, what worked, what you'd do differently next time — exists across receipts, photos, mental notes, and the part of the project where you swore you'd remember. By the time the next similar project comes around, the memory is fuzzy and you're solving the same small problems from scratch.
A vault that holds one page per project, with materials, build steps, photos, and a "what I learned" section, fixes most of it. The agent does the searching when something comes up.
One page per project, with everything attached
Each DIY project gets its own page. The deck repair, the closet build-out, the bathroom tile job, the chicken coop, the workbench. Pages nest with no depth limit, so a big project like a kitchen renovation can have child pages for Demolition, Plumbing, Cabinets, Electrical, and Finish work, each with its own materials list and notes.
For people running ongoing projects in parallel, group them under a DIY parent page. Each project keeps its own scope; the agent searches across when you need to remember something. "What kind of flooring underlayment did I use in the basement project last fall?" The answer comes back with the page it came from.
If you're managing larger renovations with contractor coordination overlapping the DIY work, see How to Track Home Renovation Costs and Contractor Communication for the broader version of the same shape.
A materials list that survives between projects
The materials section is the workhorse. An inline database via the :::database::: directive lets a small spreadsheet live alongside the prose on the project page. Columns for item name, spec (size, finish, model number), quantity, supplier, cost, and notes.
The agent can update this from voice or text. "Add a box of 2-1/2 inch deck screws, exterior grade, from the orange-box store, $14.99." Row appears. At the next store run, you ask: "What lumber do I still need for the deck repair?" and you get a clean shopping list pulled from the materials database, broken out by what's bought versus what's outstanding.
The reason this matters more than a one-off list is the cross-project search. "What primer did I use on the exterior trim project last year? Was I happy with it?" The agent reads across the materials databases plus the lessons-learned sections and gives you the answer with sources. That's a real decision that's hard to answer well without records.
For projects with a lot of small components — a workbench with hardware, a built-in with cabinet pulls and adjustable shelf pegs — the materials database becomes the parts inventory you'll want when something needs to be replaced or matched.
Build steps captured as you go, not after
The build notes are the part that fades fastest. Two months after the project, you remember the rough sequence; six months later, you remember almost nothing about why a specific step took longer than expected.
Voice notes work well during the build because your hands are usually full. Tap record, talk for thirty seconds. "Frame is square but the floor's out of level by about a quarter inch over six feet. Going to shim the joists rather than re-pour. Will note the shim locations in case future me needs to know." The transcript drops on the page with a timestamp.
Photos are the other half. Phone photos drop on the project page directly, captioned with a quick voice note if it matters. The "before I closed up the wall" photos of plumbing routing or electrical runs are the ones future you (or the next owner) will want most. The agent can pull from these descriptions when something comes up — "Where did I run the new water line in the bathroom remodel?" references back to the photo and the voice note that captioned it.
For projects with a particular technique you want to remember the specifics of, paste the technique notes inline. The corner joint that finally worked. The tool setting that made the cut clean. The order of operations that prevented a mess. These are the things that are worth seconds to write and minutes to recover later.
PDFs from manuals, supplier sheets, and product specs
Manufacturer documentation is the artefact that makes the difference when something goes wrong six months in. The fan you installed has a part number; the manual says where the reset switch is; the manufacturer warranty is in the PDF you tossed in a drawer. Drop them on the project page and they become searchable.
PDFs convert to markdown automatically, so the agent can actually read them. "What's the maintenance schedule for the bathroom exhaust fan I installed?" The agent reads the manual and answers with the citation. No digging through a folder of PDFs.
For complex projects involving permits, code references, or inspection requirements, the same applies. The permit PDF lives on the page; the inspection checklist is searchable. "What's the code requirement for outlet spacing on the basement wall?" gets a real answer if the relevant document is on the page.
What I learned — the section that pays off years later
The last section on every project page is a Lessons learned block. Three to five bullet points, written within a week of finishing. What worked, what didn't, what you'd do differently next time. This is the section that's easy to skip and where the highest learning rate lives.
It doesn't have to be elaborate. "The pre-stain conditioner makes a real difference on pine — don't skip it again." "The cordless impact made the deck screws much faster than the drill — buy more bits next time." "The supplier on Main Street had better prices on dimensional lumber than the orange-box store but a worse selection."
Months later, the agent can find these when you ask. "I'm about to start staining a pine bookshelf. Any lessons from past projects with pine?" The answer comes back grounded in your own notes. That's a meaningfully different answer than what a generic guide would tell you.
This pattern overlaps with the broader habit covered in Notes for Hobbyists: From Woodworking to Astronomy in One Vault — DIY shares a lot of shape with hobbyist record-keeping, and the vault scales across both.
Suppliers, pricing, and the contacts you'll want again
Most DIY-ers accumulate a short list of suppliers worth keeping. The lumberyard with the actually-flat boards, the tile supplier who orders specialty stock, the appliance parts shop that helped diagnose the dishwasher, the plumber who answered the phone on a Sunday.
A Suppliers page (or a child page on each project for project-specific suppliers) holds these. Name, what they're good for, contact info, recent prices for things you've bought, any project-specific notes. The agent can pull the right list when you need it. "Who did I get the slate tiles from? Were they good to deal with?"
For products you're researching before a project, the agent's web_search tool can pull current reviews and pricing. "Find what current reviewers say about [tool model] for hobbyist woodworking." Comes back with sources. The notes on what reviewers said become part of your project page, so the next time you're considering a similar tool, you've got your own research history to start from instead of starting fresh. The same shape applies if you're comparing options for any major decision — DIY purchases are just one flavor of that.
A starter shape that works on day one
If you're moving from "everything in receipts and the part of my brain that's stretched thin" to a vault, this is what we'd suggest:
- One page per project. Title with the project name and the year.
- A materials database on each project page. Item, spec, quantity, supplier, cost, notes.
- Build notes captured as voice or text as you go. Photos drop on the page.
- PDFs from manuals and specs land directly on the page — they become searchable.
- A lessons-learned section at the bottom, written within a week of finishing.
That's it. No template, no taxonomy. The vault grows project by project; the search gets richer with each one.
The point isn't to turn DIY into a record-keeping project. It's that the small amount of structure you keep means the next similar project starts from your own actual experience, not from scratch. The hardware-store run gets shorter. The supplier you forgot you liked is findable again. The mistakes you made once tend not to happen twice.
Try Docapybara free — start with the project you're working on this weekend, and the next time you're in the lumber aisle wondering what worked last time, the answer will be in your pocket.