The funny thing about a serious hobby is how quickly it generates more knowledge than your head can hold. A few months into woodworking and you've got jig sketches, finish recipes, blade-sharpening angles, and a strong opinion about a brand of clamp. A year into amateur astronomy and you've got observation logs, eyepiece notes, weather patterns for your specific location, and a list of every Messier object you've actually looked at versus the ones still on the list.
The hobby itself is enjoyable. The note-keeping that makes the hobby compound — that's the part that usually breaks down. People start in a paper notebook, switch to Apple Notes, drift to a folder of Word docs, and end up with knowledge scattered across four systems and findable in none.
A single vault that holds project logs, reference material, and gear inventories — and that has an agent that can read across all of it — fixes this without becoming a new hobby in itself. (For the broader case for keeping casual moments findable, see Turn Casual Captures Into a Searchable Life Archive.)
Project logs that survive the project
The most useful note any hobbyist can keep is a project log. What you tried, what worked, what you'd do differently next time. The reason it's useful is not at the moment of writing — it's six months later when you start a similar project and you've forgotten exactly which finish you used or what depth you set the router to.
In Docapybara, each project gets its own page. Pages nest, OneNote-style, with no depth limit, so a Workshop parent page can hold a child page per project — Walnut bookshelf, Garden bench, Kid's toy chest — and each project page can hold its own sub-pages for stages of the build.
A project page can hold prose ("I started with the carcass; the dado fence was off by 1/16 so I shimmed it"), a small inline database tracking materials and costs, photos at each stage, and a notes section at the end on what you learned. The agent reads across all the project pages when you ask. "How did I finish the walnut piece I made last spring?" The relevant section comes back, with the page it was from.
This is the move that turns scattered notes into a personal reference manual that actually works. You stop reinventing the wheel on the second project that uses a technique you already figured out.
Reference material that's actually searchable
Every hobby has its reference material. PDFs of plans you bought. Magazine scans. The 200-page manual that came with the lathe. The catalog from the supplier you keep using. Most of this lives in a Downloads folder where it's effectively lost.
Docapybara converts uploaded PDFs to markdown automatically. Drop the lathe manual on a page and the agent can actually read it — not just store the file. From then on, you can ask things like "What does the manual say about adjusting the tailstock alignment?" and the agent pulls the relevant section and tells you which page it came from.
For an astronomer, this might be observation guides, equipment manuals, charts. For a woodworker, plans and finish guides. For a gardener, the seed catalogs and the soil reports. The pattern is the same: PDFs become a searchable reference library instead of a file dump. (Gardeners specifically may want Tracking Your Garden: Planting Schedules, Harvests, and Soil Notes.)
Gear inventory that knows what you own and what's worth what
Most hobbies eventually generate a respectable inventory. Hand tools, eyepieces, cameras, brushes, lenses, kits. Knowing what you have stops you buying the third rasp identical to the two already in the drawer.
An inline database inside an Inventory page handles this — name, type, condition, where you bought it, what you paid, current value if it matters. The :::database::: directive lets the database live inside the same page as the prose about how you use the gear.
The agent can update the database. "Add the new 17mm Ethos eyepiece I picked up at the swap meet — paid $400, condition like-new." It adds the row. When you're trying to remember which clamps you have before driving to the show, ask the agent and you've got the list.
For higher-value gear, give each piece its own child page. The page can hold the receipt PDF, any service records, photos, and notes on quirks you've learned about it. The agent treats this nested structure as one searchable pile. The same pattern works at scale for serious collections — see Notes for Collectors: Inventory, Provenance, and Market Research in One Place.
Capture in the moment, write up later
The tricky part of any hobby is that the best information usually shows up when you're hands-deep in it and can't easily stop to write. You're at the lathe, the chisel finally goes through the way you wanted, and you'd love to capture exactly what you did differently. You can't, because your hands are full and there's a cutting tool spinning.
Two captures handle this. Voice — tap record on your phone, talk for thirty seconds, get a transcript on a page. "Slowed the lathe to 800 rpm, used the bowl gouge at 30 degrees, light cuts. Way smoother than yesterday." The transcript lands with a timestamp. After the work is done, you can ask the agent: "Pull the things I dictated this afternoon and add them to the bowl-turning page as a 'what worked' section." The notes get filed without you sitting back down at a desk.
Photos work the same way. Drop them on the project page later, with a one-line caption each. The agent can pull them back when you ask: "Show me the photos from the bookshelf project where I was working on the dovetails."
Long-term observation logs (and why they matter)
For hobbies that involve sustained observation — astronomy, birding, gardening, beekeeping, fishing — the log itself is the hobby's archive. Each session is a node, and the value comes from the patterns you can see across years.
A Logs page with one child page per session works. The session page holds date, conditions, what you observed, what you tried, anything notable. For astronomy, that means seeing conditions, equipment used, objects observed, sketches or photos. For gardening, the weather, what you planted, what was blooming, pests you noticed.
The agent can find patterns across years of logs. "Which weeks last spring had the best seeing here, and what was the moon phase?" Or "When did I first notice the squash bugs each of the last three years?" These are questions you couldn't answer at all from a paper logbook without paging through every entry. The agent reads everything.
This is where a vault stops being a notes app and starts being something more like a personal scientific instrument for the hobby.
Communities, ideas, and the wishlist that grows
Most hobbies have a community attached — forums, Reddit threads, YouTube creators, a local club. The information from these places is rarely the kind you read once. It's the technique you'll want to try in three months, the supplier someone recommended, the deal someone spotted.
A Community notes page with a running stream of clips and links handles this. The agent's web_search tool can pull in summaries with sources when you want them. "Find the consensus opinion on the new Sky-Watcher Dobsonian and pull a few representative comments from amateur astronomy forums." The summary lands with citations. You can save the bits you care about.
The same page or a sibling page holds a wishlist — gear you're considering, projects you want to attempt, materials you're saving up for. The agent can help triage. "Which items on my wishlist are under $200 and would actually fit in my current shop space?" It reads, it filters, it answers.
A starter shape that works on day one
If you're moving from a notebook (or no system at all) to a vault, this is what we'd suggest starting with. None of it is mandatory.
- Projects — parent page with one child page per active project. Update as you work.
- Reference — drop PDFs and manuals here. The agent reads them on demand.
- Inventory — one page with an inline database of gear. Per-item child pages for the high-value pieces.
- Logs — for hobbies with ongoing observation. One page per session.
- Community notes — clips, summaries, wishlist.
That's five pages. Nothing colour-coded, no template required, no taxonomy to invent. The vault grows the way the hobby does, and the agent does the work of finding things across all of it when you ask.
What this changes about the daily loop
The daily loop becomes: capture without thinking, build the project log without ceremony, ask the agent when you need to find something. Six months in, the vault is doing real work for you — saving you from buying the third clamp, reminding you of the finish ratio that worked, telling you which night last September had similar seeing conditions to tonight.
A hobby is more fun when you're not constantly relearning what you already figured out. The vault is what makes the hobby compound instead of starting over each season.
Try Docapybara free — start with one project page and a logbook, and see how the vault grows alongside the hobby.