A Barnicle Productions field guide · Part 02
From second brain
to Grow Wild.
How I connect what I learn
to the work I care about.
A video becomes a question. A question finds its people, its evidence and a place to work. Here’s the architecture that keeps those connections alive.
Explore the connectionsKeep the source. Find the meaning.
Find the home. Define the assignment.
Give the knowledge a practical job.
Beyond the folder map
Knowledge needs
a way into the work.
In part one, I opened the folders inside my Second Brain. This time, we’re following the connections out of it.
Grow Wild gives this structure a purpose: learning about water, soil, edible landscapes and the people doing thoughtful work in those fields. I want the research to help me ask better questions, develop useful materials and bring the right context into a project.
That takes more than saving a link. I need to know where the source lives, what we made from it, what is still uncertain and who needs to make the next decision.
A repository, or repo, is a project’s home for its files and working history. The master-folder map helps me see which home owns the research, the coordination or the implementation.
The architecture between master folders
Three homes.
Open each one.
Each master folder has a different responsibility. Select one to see what it keeps and what it passes on.
What do we know, and where did it come from?
Keep the research connected.
The vault holds captured sources, useful summaries, research questions and project context. Original material stays available when an interpretation needs checking.
Research home · existing00_Inbox/Original evidence
Preserved captures and intake records. A source may remain here after it has been summarized; its coverage record tells us what has been done.
01_Knowledge_Wiki/Reusable knowledge
Source-linked summaries, concepts and frameworks. This is where a lesson becomes easier to find and compare without losing its qualifications.
02_Projects/Grow_Wild/Research in context
Water Restoration Heroes, the broader Allies and Leaders list, plant research and the questions connecting them. A research lead does not become a customer or collaborator just by appearing here.
What exists, who owns it, and what happens next?
Keep the assignment connected.
RepoOps means repository operations. I use it as my internal Overwatch coordinator: the agent role and working records that help me keep track of projects across master folders.
Coordination · invoked for scoped work00_SYSTEM/Rules & project map
Instructions, project locations, ownership, review status and permission boundaries. These records help the agent find existing work before it proposes another build.
08_WORKING/Drafts & experiments
A place for proposed patches and bounded experiments, including the Water Stories content pilot. An experiment here is not automatically installed in the receiving business workspace.
10_HANDOFF/ · 12_REPORTS/Assignments & receipts
A handoff defines the context, destination, output and allowed actions. A receipt records what was actually produced, checked and left open.
Where can this help the business?
Give the research a working home.
The Grow Wild automation workspace holds business-specific research, tools, plans and working materials. The shelves have different levels of maturity; a folder does not mean its whole workflow is automated.
Mixed working systems, research & planned destinations08_Research_and_Reference/Business research
Plant Radar research and preserved import snapshots connect the business workspace to selected Second Brain material. The Allies and Leaders snapshot arrived through the Permaculture Orchard research import.
Knowledge, content & relationship shelvesIntended destinations
Defined homes for future curated knowledge, content and relationship work. The inspected consolidation shelves do not establish an installed Water Stories library or active outreach system.
Handoff and review recordsTrace what changed
Import manifests and dated receipts identify what reached this workspace. A preserved research snapshot remains research until its next use is deliberately reviewed.
The arrows run both ways: context goes out; results, corrections and open questions come back. This is a curated map of the workflow, not a live browser into private folders.
RepoOps in plain English
The coordinator
between the workspaces.
When I resume work, RepoOps can inspect the relevant records, identify the receiving project and prepare an assignment. The connections come from explicit context and receipts.
“Find me a wetland restoration project in a suburban setting with documented improvements to habitat, water quality and the appearance of the site. Compare it with the high school wetland restoration project I’m working on in Middletown. Show me the evidence and relevant differences, so we can assess whether it supports a case for additional donor funding.”
The question is paraphrased. The answer alongside it comes from our saved July 2026 research.
The saved answer · July 26–28, 2026
- The saved match: A-B Tech.Our Water Stories research selected the stormwater wetland at Asheville-Buncombe Technical Community College in North Carolina. Its transfer card explicitly connected the case to Middletown’s wetland/living-classroom work. Watch the source film ↗
- Why it was useful.The case connects repurposed pavement, native habitat, stormwater treatment and outdoor learning. It shows the combination of a site owner, nonprofit, design professionals, funders, educators and maintenance that a school project may need.
- Where the comparison stops.The saved dossier describes an urban campus, rather than an exact suburban match. Construction was documented as complete, while measured water-quality improvement and long-term habitat results were still pending in that review.
- What could support a donor conversation.The saved recommendation was to show the project’s partners, educational purpose, monitoring and maintenance needs. Middletown’s own site evidence and plans would still be needed. This is a precedent for explaining the opportunity, not proof of local outcomes or future donations.
RepoOps can bring back the existing answer, its sources and what still needs work before it becomes a donor-facing proposal. This example summarizes a saved research result; it does not recreate a verbatim chat exchange.
“Overwatch” describes its coordinating role. These instructions and records do not mean an agent is continuously watching every folder or synchronizing everything in the background.
Grow WildLandscapes with a living purpose.Now, give that architecture a purpose
Follow the water.
Find the connections.
The next part of the story belongs to Grow Wild: the sources we learn from, the people worth understanding and the questions we bring back to the landscape.
A real research thread
Water Stories becomes
a connected research library.
The Water Stories films and teaching introduced a network of projects, practitioners and approaches to water restoration. The Second Brain gives those leads a structure I can revisit.
Start with a specific story.
One example follows the A-B Tech stormwater wetland in North Carolina. The film and technical webinar give us a source trail; our project dossier organizes the context and the questions.
A channel inventory tells us what was collected. It does not prove every video has received a complete technical review.
Keep the explanation attached to its evidence.
We connect the project to people, place, methods and individual claims. That lets us ask a precise question instead of adopting the whole story as a design recipe.
For example, the A-B Tech liner explanation remains attributed professional testimony in our notes. The underlying geotechnical and contamination records were not obtained. It stays a research question rather than a general instruction about when to line a wetland.
See the question this creates ↗RepoOps gives a selected subset a job.
In a bounded Water Stories experiment, RepoOps coordinated a source-and-claim packet into a private content master and derivative drafts, including a newsletter lead, carousel and short-video script.
The experiment lived in RepoOps’s working area. It demonstrates a scoped build and verification loop; it does not establish that the full research library was installed into Grow Wild’s operating system.
The return receipt can contain a correction.
A derivative draft dropped “approximately” from a source claim. A complementary review caught the stronger wording. RepoOps preserved the failed version, corrected the affected line and checked the revised package.
That small word explains why the return path matters. A technically checked artifact, owner business acceptance and permission to publish are separate decisions. This experiment’s saved receipt keeps the latter two open.
Sources connect us to people
A map of people
worth learning from.
Water Restoration Heroes connects water-focused practitioners and projects. The broader Grow Wild Allies and Leaders list grew through Permaculture Orchard research and other public sources. They are linked research views with different origins.
Zach
Weiss
His Elemental Ecosystems project accounts connect water-restoration ideas to observation, phasing and maintenance. We retain their context as practitioner accounts.
Meet the practitioner ↗Rajendra
Singh
His work offers a route into community water stewardship. Credit belongs with the residents, Tarun Bharat Sangh and local institutions alongside the individual.
Explore the public profile ↗Eric
Toensmeier
The allies list links his perennial-plant work to our existing Perennial Solutions research: a useful route into plant choice, site fit and harvest questions.
Visit Perennial Solutions ↗Stefan
Sobkowiak
The Permaculture Orchard research adds long-term questions about canopy change, establishment and maintenance. It broadens the water story into the care of a living landscape.
Open the linked orchard source ↗It means potential alignment with Grow Wild’s purpose, not a claim of contact, endorsement or partnership. A preserved snapshot of the broader list reached Grow Wild’s Plant Radar research workspace through the September Permaculture Orchard import. That transfer did not create CRM relationships or authorize outreach.
How the research helps our work
A better question
is a useful output.
The strongest connection is often a question to carry into a Grow Wild project. We compare the idea with our site, evidence and responsibilities before deciding what to do.
Water & site contextWhere should the water go?+
Research connection: A-B Tech’s project and technical account prompt us to look at site conditions before choosing a water-management approach.
Grow Wild question: For runoff work, what are the water sources, soil conditions, constraints, overflow route and maintenance responsibilities?
The video does not establish infiltration suitability or a liner specification for another property. That needs site evidence and appropriate technical review.
Stewardship over timeWhat happens after installation?+
Research connection: The Tabula Rasa Phase 1 story and later Phase 2 update make this an evolving case, with new questions about establishment, inspection and repair.
Grow Wild question: Who checks the work after storms and through the seasons? What would trigger maintenance, replacement or a change of plan?
These are owner and practitioner accounts, not independent long-term monitoring. A Grow Wild maintenance plan and measured outcome still need their own records.
Plant choice & useful harvestWill this idea work here?+
Research connection: The linked orchard and perennial-plant research connects water placement to light, moisture, climate and long-term care.
Grow Wild question: Will a plant merely survive, or provide a useful harvest in this setting? What changes as the canopy matures, and can the owner maintain it?
A successful example elsewhere is a starting point. Our Plant Radar and foodscaping work still need local species, cultivar and site checks.
These are generalized question bridges drawn from our research and planning. They are not published client case studies, engineering designs or claims of measured Grow Wild performance.
Where the work stands
Keep the next step visible.
The architecture helps me return to the right stage instead of starting over—or assuming something is finished because a folder exists.
- Research
- Sources, summaries, a water-restoration network and a broader people-and-purpose list exist.
- Coordinated build
- A bounded Water Stories content experiment produced and checked a review package.
- Receiving workspace
- A separate Orchard import preserved the allies-list snapshot in Grow Wild’s research area.
- Next decisions
- Review each proposed use, accept the relevant output and authorize any publication or outreach separately.
Sources & how to read this example
This article draws on our saved research and coordination records, checked for this draft in September 2026. Public links below let you explore the source projects. We have not reproduced private records, transcripts or third-party media.
- Water Stories — source films, education and water-restoration context.
- A-B Tech film and technical webinar — the selected research example; attributed explanations remain distinct from independently verified findings.
- RiverLink’s A-B Tech project page and A-B Tech’s project account — project-party context, not independent verification of every claim.
- Tabula Rasa’s collaboration account — an owner’s account behind the maintenance questions.
- Perennial Solutions and the linked Permaculture Orchard source — a separate, connected branch of the allies and plant research.
The workflow map explains responsibilities. The Middletown question is paraphrased; the A-B Tech answer summarizes our July 26 transfer card and July 28 project dossier. The bounded experiment and preserved research snapshot are also drawn from dated records. None of those is evidence of a continuously running synchronization service.
One connected practice
Learn with context.
Build with a purpose.
For me, that is the value of a Second Brain: I can return to an idea, understand why it mattered and connect it to a thoughtful next step.