A field guide to organized knowledge

Inside my
second brain.

Every folder has a job. Here’s how I organize what I learn, connect it to my work, and find my way back to it.

Brian BarnicleSeptember 21, 2026Read + explore

Open the folder map Follow one idea through it

THE ARCHITECTUREMASTER / 01 / 02 / 03

Brian’s Second BrainOne master folder. Connected knowledge.

00_InboxOriginal sources 01_Knowledge_WikiUseful knowledge 02_ProjectsWork in context 00_DashboardWhere to go next

15 main foldersA view inside the real structure ↗

Clickable folder mapPlain-language definitionsPublic structural tour

First, the idea

Memory I can
come back to.

I save research, ideas, project notes and lessons from doing the work. My second brain gives that material a home—and gives me a way to turn it into something useful.

The system grew through exploration. As it grew, I needed to ask a basic question of every part: What is this here for, and where should I go next? The recent cleanup helped make those answers clearer. This is the map we worked toward.

AI can help read selected context, summarize sources, compare ideas and prepare drafts. The organization makes those tasks easier to direct. I still need to check the evidence, keep decisions clear and review the result.

A vault is the master folder containing these connected files. Markdown (.md) is a plain-text note format. Obsidian gives me a convenient way to read the notes and follow their links.

Start / The master folder

The whole vault

The container for the knowledge, navigation and working context.

Brian_Second_Brain_Starter_Vault/

Layer 1 / Main areas

A place for each job

Inbox, knowledge, projects and the other areas with distinct responsibilities.

00_Inbox/

Layer 2 / Inside an area

More specific homes

The folders and notes that divide an area into useful parts.

Raw/ · Processed/ · Intake_Register.md

Layer 3 / Inside a section

The working pieces

Source batches, document roles and system modules, with their purpose and readiness.

Web_Clips/ · source batches

The interactive field guide

Open the system.

Choose an area, open a section, then explore its working pieces. Each layer explains what belongs there, what it prevents and how ready it is to use.

Structure checked September 21, 202627 root items · 130 second-layer items · 82 sections explored deeper

New / The third layer

Open a folder. Then ask what is inside.

A source batch, a blank form and a working script can all look like files. Their roles and readiness tell you how to use them.

BRIAN’S SECOND BRAIN / FOLDER MAP

The vault

Brian_Second_Brain_Starter_Vault/

Start here

One master folder holds the knowledge I want to find, understand and use again. Inside it, each area has a specific job.

What it is: A collection of linked notes, original sources, project context, reusable methods and instructions. Most notes are plain-text Markdown files, which I browse in Obsidian.
Why the structure matters: It gives me—and an AI assistant working within the task’s access—a route to the relevant context. We can check what already exists before creating more.

Four useful places to begin

Capture the source00_Inbox · Keep what came in. Keep the useful knowledge01_Knowledge_Wiki · Explain and connect it. Give it a purpose02_Projects · Tie it to real work. Find the next action00_Dashboard · Orient, review and resume.

The main folders are the first layer. Choose one to see its role, then open a child item to explore the second layer. Folder sections open further into the roles of their notes, source batches and modules. Guides and settings sit alongside those folders and have their own jobs.

The front desk

00_Dashboard/

Layer 1 · folder

Find current work, decisions waiting for me and past reports.

What belongs here: Navigation, proposed action plans, review views, dated reports and selected transfer records.
What this helps prevent: Gives me one starting point without mistaking an old plan for today’s task.

Illustrative exampleOpen the dashboard to find the next decision on a sample website project.

One level inside

Layer 2 · 5 items

Action_Plans/Action Plansfolder · explore

Turn findings into prioritized proposed work.

What belongs here: Proposed work in a useful order, with links to the findings that prompted it.
Why it has its own place: Keeps proposed work and historical plans distinct from current assignments.

Illustrative exampleReview a proposed three-step cleanup before assigning it.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Plans with disposition links

A saved plan records intent. Its linked project controls establish what remains.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Prioritized plansdocument role · Proposed or historical

Put proposed work in a useful order.

What it contains: Reasons, dependencies and a recommended sequence.
What it helps prevent: Starting the next attractive idea before checking existing commitments.
Readiness: Proposed or historical

Link to this role

Handoff briefsdocument role · Check receiving outcome

Define a bounded piece of work for a receiving project.

What it contains: Scope, inputs, expected output and review conditions.
What it helps prevent: Treating a sent specification as an implemented system.
Readiness: Check receiving outcome

Link to this role

Reports/Reportsfolder · explore

Give Brian synthesized findings and evidence for decisions.

What belongs here: Written inspection results, findings, scope limits and supporting evidence.
Why it has its own place: Lets me inspect the evidence behind a recommendation.

Illustrative exampleRead what a navigation review checked and which links still need attention.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Dated review evidence

Reports explain a particular inspection. They do not continuously certify the current system.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Inspection reportsdocument role · Dated findings

Explain what was examined and learned.

What it contains: Findings, scope, checks and remaining questions.
What it helps prevent: Losing the reasoning behind a cleanup decision.
Readiness: Dated findings

Link to this role

Evidence packagesdocument role · Bounded evidence

Keep the supporting material for a recorded review together.

What it contains: Check results, comparison records and related receipts.
What it helps prevent: Separating a positive summary from its actual evidence.
Readiness: Bounded evidence

Link to this role

Review_Packets/Review Packetsfolder · explore

Provide convenient interactive views of existing Markdown decisions and actions.

What belongs here: Interactive views of notes, decisions and action items prepared for review.
Why it has its own place: Makes a review easier while keeping the underlying notes as the maintained record.

Illustrative exampleExpand a sample meeting action to read the context before approving it.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Local review views

The maintained notes remain the underlying record.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Interactive review pagesdocument role · Prepared views

Make linked decisions and actions easier to inspect.

What it contains: Local HTML views prepared from selected notes.
What it helps prevent: Mistaking a convenient display for the authoritative project record.
Readiness: Prepared views

Link to this role

Packet guidancedocument role · Reference

Explain where a review view came from and how to use it.

What it contains: Usage instructions and source pointers.
What it helps prevent: Assuming a browser checkbox updates the source note.
Readiness: Reference

Link to this role

Project_Transfer_Register.mdProject Transfer Registerfile

Track what reached another repository and what was actually checked or accepted.

What belongs here: Selected transfers, receiving destinations and the limits of recorded verification.
Why it has its own place: Distinguishes “copied across” from “tested and accepted.” It records selected checked transfers.

Illustrative exampleSee that a research brief was received while its build still awaits testing.

index.mdSection mapfile

Serve as the vault’s owner-facing navigation page.

What belongs here: Links to the main working areas and the records used to understand current work.
Why it has its own place: Routes me to current work, owner review and dated evidence.

Illustrative exampleFind the project hub that owns a pending decision.

The receiving area

00_Inbox/

Layer 1 · folder

Keep original material, quick captures and the record of what has been processed.

What belongs here: Original captures, source batches, quick notes, optional review lanes and processing records.
What this helps prevent: Preserves the source so we can check where an answer came from.

Illustrative exampleSave an article, then record whether it has been summarized and what question remains.

One level inside

Layer 2 · 8 items

Raw/Rawfolder · explore

Preserve original evidence at stable source locations.

What belongs here: Original source files and batches, including sources that have already been processed.
Why it has its own place: Keeps originals available even after summarizing. Raw does not mean unprocessed.

Illustrative exampleKeep an original article capture after creating a summary that links back to it.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Original evidence; mixed coverage

Raw describes the source, not whether it has already been summarized.

Curated roles · related items may be grouped; private contents omitted.

Web_Clipsmodule · Preserved originals

Receive browser captures in the current general capture lane.

What it contains: Original clipped Markdown and capture context.
What it helps prevent: Losing the original when making a useful summary.
Readiness: Preserved originals

Link to this role

Source batchesdocument role · Check summary coverage

Group related research inputs without claiming they are all processed.

What it contains: Batch guides, source files and intake manifests.
What it helps prevent: Reprocessing a whole batch because a few sources remain open.
Readiness: Check summary coverage

Link to this role

Loose source filesdocument role · Triage before processing

Hold general incoming material before more specific routing.

What it contains: Manual captures and original documents.
What it helps prevent: Forcing every new idea into a project too early.
Readiness: Triage before processing

Link to this role

Processed/Processedfolder · explore

Archive original sources whose movement after processing was approved.

What belongs here: Original source material moved into this archive through an approved processing step.
Why it has its own place: Keeps archived originals separate from the knowledge made from them.

Illustrative exampleRetain an archived source after an approved move, with its reference still traceable.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Archived originals

Movement into this folder is separately approved; it is not factual approval.

Curated roles · related items may be grouped; private contents omitted.

Archived source files and batchesdocument role · Preserved evidence

Keep source evidence after an approved move.

What it contains: Original records and their retained source context.
What it helps prevent: Confusing archived evidence with the knowledge extracted from it.
Readiness: Preserved evidence

Link to this role

Needs_Review/Needs Reviewfolder · explore

Provide an optional holding lane for sources requiring Brian’s judgment.

What belongs here: An optional holding place for material requiring human judgment.
Why it has its own place: Sets aside ambiguous material for a person to review; other projects may also have review queues.

Illustrative exampleSet aside a confusing capture until its intended project is clear.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only holding lane

The local index is a reserved route. Other projects can have their own review queues.

Curated roles · related items may be grouped; private contents omitted.

Trash_or_Ignore/Trash or Ignorefolder · explore

Retain low-value material outside active processing without losing it immediately.

What belongs here: Material kept outside active processing until its disposition is decided.
Why it has its own place: Keeps low-value material out of active work without automatically deleting it.

Illustrative exampleKeep an irrelevant capture out of the active queue without deleting it immediately.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only retention lane

A low-value disposition can be recorded without deleting or moving the original automatically.

Curated roles · related items may be grouped; private contents omitted.

Quick_Capture.mdQuick Capturefile

Capture short thoughts, reminders and fragments before they have a project home.

What belongs here: Short ideas, reminders and fragments awaiting a more specific home.
Why it has its own place: Lets me capture a thought before deciding where it belongs.

Illustrative exampleCapture “compare two workshop formats” before deciding which project owns it.

Raw_Processing_Workflow.mdRaw Processing Workflowfile

Define the source-to-summary-to-useful-note process and completion checklist.

What belongs here: Steps and completion checks for turning a source into useful linked notes.
Why it has its own place: Checks for existing work, preserves sources and makes processing repeatable.

Illustrative exampleCheck for an existing summary before processing the same article again.

Intake_Register.mdIntake Registerfile

Find source batches, recorded processing coverage and remaining review.

What belongs here: Source-batch locations, recorded coverage and remaining review questions.
Why it has its own place: Helps avoid duplicate processing and makes unknown coverage visible.

Illustrative exampleFind whether a saved webinar has a summary or is still awaiting review.

index.mdSection mapfile

Explain intake lanes and route readers to batch authorities.

What belongs here: A guide to the intake lanes and the records that explain each batch.
Why it has its own place: Explains where a capture belongs and where to check its status.

Illustrative exampleChoose the correct home for a new capture.

The reference library

01_Knowledge_Wiki/

Layer 1 · folder

Keep source summaries, concepts, methods, people, companies and tool research.

What belongs here: Source summaries and reusable reference notes organized by concepts, methods, people, organizations and tools.
What this helps prevent: Turns scattered reading into knowledge I can find and reuse.

Illustrative exampleReuse a well-sourced explanation of a planning method in two different projects.

One level inside

Layer 2 · 8 items

Books_Articles_Videos/Media catalogfolder · explore

Alternative navigation catalog for source media.

What belongs here: An alternate catalog pointing to source-media summaries.
Why it has its own place: Provides an alternate route to source summaries, without storing another copy of each source.

Illustrative exampleFind a book summary through the media catalog and open its maintained note.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Selected reading view

This is a linked selection of summaries, not a second copy of the source library.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Companies/Companiesfolder · explore

Source-based reference knowledge about organizations, platforms, and suppliers.

What belongs here: Reference research about organizations, platforms and suppliers.
Why it has its own place: Keeps company research separate from my actual dealings with that company.

Illustrative exampleRecord what a software company offers, with a source and date.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reference notes

A company reference describes the subject; relationship history belongs in CRM.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Company and supplier referencesdocument role · Source-grounded references

Explain organizations relevant to saved research.

What it contains: Attributed descriptions, related tools or sources, and questions to verify.
What it helps prevent: Confusing a researched organization with an active business relationship.
Readiness: Source-grounded references

Link to this role

Concepts/Conceptsfolder · explore

Reusable explanations, principles, and mental models.

What belongs here: Explanations of ideas, principles and mental models.
Why it has its own place: Explains an idea once so multiple projects can use it.

Illustrative exampleExplain the difference between a leading indicator and a lagging indicator.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reusable explanations

Each concept should link back to evidence and say where it is useful.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Knowledge and context conceptsdocument role · Maintained explanations

Explain how capture, summaries and reusable knowledge relate.

What it contains: Definitions, routing explanations and boundaries.
What it helps prevent: Treating the folder name as the processing status.
Readiness: Maintained explanations

Link to this role

Subject conceptsdocument role · Verify before consequential use

Keep useful distinctions from research easy to reuse.

What it contains: Definitions and qualified lessons from relevant domains.
What it helps prevent: Repeating an attractive claim without its source or limits.
Readiness: Verify before consequential use

Link to this role

Frameworks/Frameworksfolder · explore

Reusable decision methods, checklists and system models.

What belongs here: Reusable methods, checklists and decision structures.
Why it has its own place: Makes a method reusable while keeping its project-specific use elsewhere.

Illustrative exampleKeep a repeatable checklist for evaluating a new workflow.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Methods with differing evidence

A well-organized method can still be a proposal.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Research and evaluation methodsdocument role · Methods and proposals

Provide a repeatable way to ask and check a question.

What it contains: Source filters, evaluation criteria and evidence requirements.
What it helps prevent: Calling an answer reliable without saying how it was checked.
Readiness: Methods and proposals

Link to this role

Practical decision checklistsdocument role · Review for the specific task

Turn a reusable lesson into a sequence of decisions.

What it contains: Questions, constraints and steps linked to underlying research.
What it helps prevent: Starting from scratch or losing qualifications when applying a lesson.
Readiness: Review for the specific task

Link to this role

People/Peoplefolder · explore

Source/reference profiles and evidence about people.

What belongs here: Reference profiles and attributed ideas from source material.
Why it has its own place: Keeps reference knowledge about someone separate from our relationship history.

Illustrative exampleLink an author’s idea to its source without creating a CRM relationship.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reference profiles

Profiles are kept separate from private relationship records.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Source-author profilesdocument role · Reference; verify claims

Connect an author or practitioner to relevant research.

What it contains: Attributed ideas, source links and uncertainty.
What it helps prevent: Treating a person’s authority as verification of every claim.
Readiness: Reference; verify claims

Link to this role

Source_Summaries/Source summariesfolder · explore

Provenance-linked interpretation of original sources and evidence for processing coverage.

What belongs here: Source-linked explanations, takeaways, qualifications and related notes.
Why it has its own place: Links the useful explanation back to the original. Summarized does not automatically mean verified.

Illustrative exampleSummarize a workshop while separating the presenter’s claim from verified evidence.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Curated source knowledge

Coverage records distinguish summarized, captured-only and unavailable material.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Topic collectionsmodule · Summaries with source limits

Group useful summaries by subject.

What it contains: Source-linked takeaways, useful applications and verification limits.
What it helps prevent: Losing a summary because the original arrived in a large batch.
Readiness: Summaries with source limits

Link to this role

Research packetsmodule · Check packet coverage

Keep a related research batch and its coverage together.

What it contains: Packet indexes and summaries linked to original inputs.
What it helps prevent: Calling an entire packet complete when individual sources have gaps.
Readiness: Check packet coverage

Link to this role

Meeting summary lanemodule · Private contents omitted

Keep interpreted meeting knowledge connected to the original record.

What it contains: Selected meeting summaries with their evidence and action context.
What it helps prevent: Promoting an interpretation into an agreed commitment.
Readiness: Private contents omitted

Link to this role

Tools/Toolsfolder · explore

Knowledge and evaluation notes about software, equipment and practical reference aids.

What belongs here: Research and evaluation notes about software, equipment and practical aids.
Why it has its own place: Keeps tool research separate from installed code or purchasing decisions.

Illustrative exampleCompare two note-taking tools without implying either is installed.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reference notes about tools

These explain tools. Executable helpers belong in 09_Tools.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Tool and workflow referencesdocument role · Check dates and versions

Record what a tool is for and how it might fit.

What it contains: Usage notes, research findings and source references.
What it helps prevent: Mistaking an old product description for a current tested capability.
Readiness: Check dates and versions

Link to this role

index.mdSection mapfile

Entry router to the distilled-knowledge sections.

What belongs here: Navigation for the reusable knowledge sections.
Why it has its own place: Helps people and AI navigate the knowledge without reading it all.

Illustrative exampleLocate an existing framework before writing another explanation of it.

The project desks

02_Projects/

Layer 1 · folder

Keep objectives, research, decisions and next steps for business, client and personal projects.

What belongs here: Project hubs with objectives, research, decisions, next actions and links to any receiving build repository.
What this helps prevent: Connects knowledge to a specific outcome and its current owner.

Illustrative exampleCheck whether a related tool already exists before researching a new version of it.

One level inside

Layer 2 · 10 items

AI_Agents/AI Agentsfolder · explore

Build/evaluation hubs for specific agent systems.

What belongs here: Hubs for specific assistant systems, with research and receiving-work pointers.
Why it has its own place: Keeps agent research and build decisions together; a separate build repository may own the working system.

Illustrative exampleFind the existing assistant project and identify its next unanswered research question.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Research hubs and receiving links

Each hub has its own state. Folder presence does not establish an accepted agent.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Agent project hubsmodule · Project-specific status

Connect a proposed agent to its research and implementation home.

What it contains: Goals, constraints, evaluation notes and receiving-repository links.
What it helps prevent: Building the same agent twice or relying on an obsolete plan.
Readiness: Project-specific status

Link to this role

Evaluation workspacemodule · Experimental

Keep bounded local-agent comparisons together.

What it contains: Test proposals and recorded evaluation context.
What it helps prevent: Calling a promising demonstration an accepted operating system.
Readiness: Experimental

Link to this role

AI_Media_Branding/AI Media Brandingfolder · explore

Project/application hub for AI-assisted creative services and story/brand experiments.

What belongs here: Project-specific creative experiments, brand applications and supporting decisions.
Why it has its own place: Connects creative experiments to a specific objective and its evidence.

Illustrative exampleKeep the purpose and evaluation of a sample visual concept together.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Creative plans and test records

Private creative projects and client names are represented by role.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Creative control notesdocument role · Plans and recorded progress

Track a creative project’s objective and next decision.

What it contains: Progress, bounded plans and production constraints.
What it helps prevent: Confusing a production plan with finished approved material.
Readiness: Plans and recorded progress

Link to this role

Website intake packagemodule · Project-specific evidence

Preserve source context used in a creative website project.

What it contains: Project intake and related references.
What it helps prevent: Losing the input context when a build moves to its own repository.
Readiness: Project-specific evidence

Link to this role

Voice demonstrationdocument role · Demonstration

Record a bounded creative messaging test.

What it contains: Test framing, candidate output and review context.
What it helps prevent: Presenting experimental copy as approved client work.
Readiness: Demonstration

Link to this role

Ancient_Technology_Living_Systems_and_Design_Research/Cross-domain design researchfolder · explore

Bounded cross-domain research project and its processing controls.

What belongs here: A defined cross-domain research hub with source claims, verification and design interpretation.
Why it has its own place: Keeps a defined research question separate from general reference notes.

Illustrative exampleSeparate a historical claim from a proposed modern design experiment.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Research program

Historical analogies and source claims remain research until checked for their intended use.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Source catalog and processing mapdocument role · Research controls

Locate research inputs and track coverage.

What it contains: Source listings, processing queues and evidence lanes.
What it helps prevent: Skipping provenance while combining interesting ideas.
Readiness: Research controls

Link to this role

Comparison and idea trackersdocument role · Exploratory methods

Compare functions across sources.

What it contains: Cross-source threads, comparison questions and visual-translation ideas.
What it helps prevent: Presenting an analogy as technical proof.
Readiness: Exploratory methods

Link to this role

Manifests and scriptsmodule · Inspect before running

Support bounded research handling.

What it contains: Inventory records and local research utilities.
What it helps prevent: Losing track of the scope of a processing step.
Readiness: Inspect before running

Link to this role

Barnicle_Productions/Barnicle Productionsfolder · explore

Business project hub for photography, video, branding and production systems.

What belongs here: Production-business project context and links to separate implementation work.
Why it has its own place: Keeps my production-business project context connected to its working buildouts.

Illustrative exampleFollow a media-production research note to the project responsible for implementation.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Business project context

The receiving website repository owns the current implementation.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Website project hubmodule · Check receiving controls

Connect website research to its dedicated build.

What it contains: Historical prototype context and receiving links.
What it helps prevent: Editing a historical copy as though it were the maintained website.
Readiness: Check receiving controls

Link to this role

Media plans and handoff contractdocument role · Plans and contract

Describe proposed editing work and how a project should transfer.

What it contains: Integration plans, scope and delivery requirements.
What it helps prevent: Equating a planned integration with installed capability.
Readiness: Plans and contract

Link to this role

Personal design projectPersonal design projectGeneral category

General category · General category shown; the specific local name is omitted from this public tour.

Personal design-development project with coordinated editable artifacts.

What belongs here: A private personal design project with coordinated decisions and editable artifacts.
Why it has its own place: Keeps design decisions with the drawings; a drawing alone is not structural approval.

Illustrative exampleKeep a sample drawing revision connected to the decision that changed it.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Private design project

The identifying folder name is generalized in this tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Design basisdocument role · Project-specific review

Record the project’s requirements and assumptions.

What it contains: Constraints and decisions to verify before using outputs.
What it helps prevent: Treating a drawing as an approved construction design.
Readiness: Project-specific review

Link to this role

Inputs, correspondence and outputsmodule · Private contents omitted

Separate received evidence from generated work.

What it contains: Input records, communications and candidate deliverables.
What it helps prevent: Losing the source of a design decision.
Readiness: Private contents omitted

Link to this role

Scripts and QAmodule · Check-specific evidence

Keep project utilities and checks near their outputs.

What it contains: Generation support and recorded review material.
What it helps prevent: Assuming generated output is correct without inspection.
Readiness: Check-specific evidence

Link to this role

Client_Projects/Client Projectsfolder · explore

Client-specific hub and governance layer.

What belongs here: Client project hubs, scope records and pointers to each project’s working home.
Why it has its own place: Keeps client scope and decisions together, with links to the client’s own working system.

Illustrative exampleOpen a fictional client’s project scope before applying a reusable method.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Client project hubs

Only structural roles appear here; client identities and work products remain private.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Client workspacesmodule · Use canonical client authority

Connect research, goals and decisions for each engagement.

What it contains: Project context, operating hubs and receiving evidence.
What it helps prevent: Creating competing master client records in every workflow.
Readiness: Use canonical client authority

Link to this role

Grow_Wild/Grow Wildfolder · explore

Upstream Grow Wild project, research and control hub with links to distributed business knowledge.

What belongs here: Business research and project coordination linked to its separate execution workspace.
Why it has its own place: Connects Grow Wild research to its separate business and execution workspace.

Illustrative exampleConnect a planting-method study to the project where it might be tested.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Research, project hubs and proposed field work

Research findings, field evidence and approved claims are separate.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Research and source-library hubsmodule · Mixed research maturity

Organize related plant, soil and water research.

What it contains: Knowledge plans, source coverage and references.
What it helps prevent: Repeating research without checking existing coverage.
Readiness: Mixed research maturity

Link to this role

Field-project notesdocument role · Project-specific status

Connect a real project or proposal to its evidence and next decision.

What it contains: Site context, plans, unresolved questions and proof requirements.
What it helps prevent: Treating a proposal as a completed field result.
Readiness: Project-specific status

Link to this role

Decision boards and transfer recordsdocument role · Check latest linked evidence

Point to the current owner of a build or decision.

What it contains: Architecture choices, handoffs, constraints and return receipts.
What it helps prevent: Continuing from an old recommendation after the work has moved.
Readiness: Check latest linked evidence

Link to this role

Review views and control foldersmodule · Navigation and control

Group the controls used to navigate larger workstreams.

What it contains: Indexes, bounded review views and project control records.
What it helps prevent: Losing the maintained record behind a convenient display.
Readiness: Navigation and control

Link to this role

Internal_Systems/Internal Systemsfolder · explore

Projects that improve the vault, internal operations and workflow infrastructure.

What belongs here: Projects for improving the vault, internal tools and operating methods.
Why it has its own place: Gives changes to the vault and internal tools their own project history.

Illustrative exampleTrack a proposed navigation improvement and the evidence used to assess it.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Internal build and research hubs

A personal or business system may be researched here and implemented elsewhere.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

System hubsmodule · Check receiving state

Tie internal research to the system that will use it.

What it contains: Goals, status notes, implementation links and review questions.
What it helps prevent: Rebuilding a capability that already has a receiving home.
Readiness: Check receiving state

Link to this role

Plans, experiments and safety preflightsdocument role · Proposed or historical

Record a proposed workflow and what must be checked.

What it contains: Evaluation plans, processing guidance and bounded experiment notes.
What it helps prevent: Interpreting an old work order as authority to run it now.
Readiness: Proposed or historical

Link to this role

Personal learning planPersonal learning planGeneral category

General category · General category shown; the specific local name is omitted from this public tour.

Personal field-project control note.

What belongs here: A private personal learning and field-project plan.
Why it has its own place: Keeps a personal learning plan separate from general knowledge and current safety advice.

Illustrative exampleKeep a personal course plan distinct from a general reference article.

index.mdSection mapfile

Find the project and check related existing work before new research.

What belongs here: Project-area navigation and the research-resume and return-receipt procedure.
Why it has its own place: Uses an on-demand RepoOps lookup, then the relevant project and receiving records, to avoid repeating work or relying on an old summary.

Illustrative exampleLook up existing related work, check its receiving record, then research only the gap.

The sales shelf

03_Sales_and_Offers/

Layer 1 · folder

Keep discovery questions, pricing logic, proposal sections and follow-up language.

What belongs here: Reusable discovery questions, pricing reasoning, proposal structures, follow-up drafts and proof-story candidates.
What this helps prevent: Lets me reuse good thinking while tailoring each real client conversation.

Illustrative examplePrepare a proposal using a reusable outline, then tailor it to the actual agreed scope.

One level inside

Layer 2 · 8 items

Case_Studies/Case Studiesfolder · explore

Proof-story and demonstration entrypoint.

What belongs here: Illustrative demonstrations and project-proof candidates with distinct approval status.
Why it has its own place: Separates illustrative examples from approved evidence of actual outcomes.

Illustrative exampleKeep a fictional example labeled as a demonstration until real evidence is approved.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Demonstration and proof candidates

A candidate needs evidence and permission before it becomes a public case study.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Illustrative copy demonstrationdocument role · Not client-approved proof

Show how a method might change messaging.

What it contains: A clearly qualified example with approval limits.
What it helps prevent: Presenting a demonstration as measured client success.
Readiness: Not client-approved proof

Link to this role

Linked proof candidatesdocument role · Linked candidates

Point to project evidence that may support a future case study.

What it contains: Links and specific evidence or permission gates.
What it helps prevent: Turning an interesting project into a published result too soon.
Readiness: Linked candidates

Link to this role

Discovery_Calls/Discovery Callsfolder · explore

Reusable qualification questions and call structures.

What belongs here: Reusable qualification questions and conversation structures.
Why it has its own place: Reuses good questions while keeping real call records with their client or project.

Illustrative exampleUse a checklist to ask about the problem, desired outcome and constraints.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reusable question drafts

Questions structure a conversation; they do not record one having taken place.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Call template and domain questionsdocument role · Reusable drafts

Help clarify a prospect’s situation and desired outcome.

What it contains: Discovery prompts, constraints and next-step questions.
What it helps prevent: Starting a proposal before understanding the actual need.
Readiness: Reusable drafts

Link to this role

Follow_Up_Emails/Follow Up Emailsfolder · explore

Reusable draft language for after-call, nudge and objection follow-up.

What belongs here: Draft language and an organizing place for follow-up patterns.
Why it has its own place: Provides draft language; a saved template does not send an email.

Illustrative exampleAdapt a thank-you draft after a fictional call and leave it for review.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Unsent message examples

Actual correspondence and its date belong with the relationship record.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Follow-up librarydocument role · Draft examples

Provide a starting point for a recap, nudge or clarification.

What it contains: Sample wording to adapt and review.
What it helps prevent: Mistaking a draft message for an email that was sent.
Readiness: Draft examples

Link to this role

Objection_Handling/Objection Handlingfolder · explore

Reusable conversation questions and response options for objections.

What belongs here: Reusable questions and response options for sales concerns.
Why it has its own place: Offers useful questions without pretending to know what a particular buyer thinks.

Illustrative exampleAsk what makes a proposal feel risky before assuming the buyer’s motive.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Starter conversation scripts

These are prompts for listening and clarification, not guaranteed sales techniques.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Price and timing responsesdocument role · Adapt before use

Help explore a concern before answering it.

What it contains: Starter scripts for price concerns and needing more time.
What it helps prevent: Using an automatic rebuttal without understanding the concern.
Readiness: Adapt before use

Link to this role

Pricing/Pricingfolder · explore

Reusable pricing logic and offer packaging.

What belongs here: Pricing assumptions, reasoning and reusable offer structures.
Why it has its own place: Keeps pricing logic separate from a specific approved quote.

Illustrative exampleDocument the assumptions behind a sample service package.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Internal logic and offer concepts

These notes are not a public or approved rate card.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Cost and pricing logicdocument role · Internal method

Make the assumptions behind an estimate explicit.

What it contains: Cost categories and scope considerations.
What it helps prevent: Quoting from an incomplete view of the work.
Readiness: Internal method

Link to this role

Offer ladderdocument role · Illustrative concept

Explore how different scopes could fit together.

What it contains: Illustrative offer structure and conditions.
What it helps prevent: Treating an untested package idea as an established product.
Readiness: Illustrative concept

Link to this role

Proposals/Proposalsfolder · explore

Reusable proposal sections and decision checklists.

What belongs here: Proposal sections, structures and decision checklists.
Why it has its own place: Reuses the structure while keeping the actual client proposal and approval with its project.

Illustrative exampleReuse a scope section while keeping the actual quote in its client project.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Scaffolds and reusable draft language

Reusable wording still needs engagement-specific review.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Proposal section librarydocument role · Blank form

Provide the headings for a future proposal library.

What it contains: A blank section scaffold.
What it helps prevent: Assuming a titled library already contains finished material.
Readiness: Blank form

Link to this role

Domain languagedocument role · Draft language

Offer draft explanations for a scoped proposal.

What it contains: Reusable wording linked to the underlying methods.
What it helps prevent: Rewriting from memory without checking the evidence.
Readiness: Draft language

Link to this role

Risk checklistdocument role · Qualified review required

Flag questions that need qualified review.

What it contains: A proposal-risk checklist with review requirements.
What it helps prevent: Treating a checklist as professional clearance.
Readiness: Qualified review required

Link to this role

Sales_Frameworks/Sales Frameworksfolder · explore

Applied selling frameworks, offer filters and worksheets.

What belongs here: Sales methods, offer filters and practical worksheets.
Why it has its own place: Turns general sales ideas into methods that can be tried and reviewed.

Illustrative exampleCompare a sample opportunity against a documented qualification method.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Methods, worksheets and draft offers

Read the item’s maturity before reusing it.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Sales principles and filtersdocument role · Internal methods

Help reason about an offer or sales conversation.

What it contains: Reusable frameworks and qualification questions.
What it helps prevent: Applying a sales tactic without understanding fit.
Readiness: Internal methods

Link to this role

Capacity worksheetdocument role · Worksheet

Make a planning calculation inspectable.

What it contains: Inputs and assumptions to fill in for a particular decision.
What it helps prevent: Using an unfilled worksheet as an actual forecast.
Readiness: Worksheet

Link to this role

Draft service offersdocument role · Draft; needs testing

Explore how a research method could become a service.

What it contains: Proposed deliverables, boundaries and test questions.
What it helps prevent: Marketing an untested workflow as established capability.
Readiness: Draft; needs testing

Link to this role

index.mdSection mapfile

Entry router and source-processing contract for sales assets.

What belongs here: Navigation for reusable selling assets and their routing rules.
Why it has its own place: Routes each selling asset to the right place.

Illustrative exampleFind a discovery-call framework without searching client records.

04_Content_and_Social/

Layer 1 · folder

Keep brand voice, hooks, scripts, content methods and production-system research.

What belongs here: Reusable voice, topic framing, scripts, channel research and distinct content workflow and visual-system workbenches.
What this helps prevent: Connects what I know to what I want to communicate.

Illustrative exampleTurn a researched concept into a reviewed article draft with a clear audience and purpose.

One level inside

Layer 2 · 12 items

content_engine/Content Engine — the production workflowfolder · explore

Organize the reusable content-production workflow and its source materials.

What belongs here: Content briefs, prompts, scripts, captions, review steps and a portable starter.
Why it has its own place: Keeps briefs, drafts and review steps together, with specific downstream buildouts linked where they are used.

Illustrative exampleMove a sample topic through brief, draft and review while preserving its sources.

Layer 3 / Inside this section

Current shape · Populated content workbench

The folder holds prompts, plans, source derivatives and helpers. Each chosen output still needs its own review and release decision.

Curated roles · related items may be grouped; private contents omitted.

The_Content_Machine/Content Machine — the visual explanationfolder · explore

Explain the content system through visual metaphors and design assets.

What belongs here: Visual metaphors, design explanations, source art and prompts.
Why it has its own place: Preserves the source art and prompts while linking to the specific production work that uses them.

Illustrative exampleUse a factory metaphor to show how a raw idea becomes reviewed content.

Layer 3 / Inside this section

Current shape · Visual explanation and source-art library

This system explains the work. The content engine, verification method and whole-business map have different scopes.

Curated roles · related items may be grouped; private contents omitted.

Relationship memory

05_CRM/

Layer 1 · folder

Keep client, prospect, partner, vendor and collaborator context and follow-ups.

What belongs here: Relationship context and follow-up records organized by clients, prospects, partners, collaborators and vendors.
What this helps prevent: Remembers how we know someone and what we promised—not just who they are.

Illustrative exampleRemember the next promised action for a fictional collaborator while keeping project scope in the project hub.

One level inside

Layer 2 · 8 items

CRM_Template.mdCRM Templatefile

Open the maintained relationship-note form from this working area.

What belongs here: A compatibility pointer and embedded view of the central relationship-note form.
Why it has its own place: Keeps old links useful while the single maintained form lives in _Templates/CRM_Note_Template.md.

Illustrative exampleOpen the local shortcut and insert the maintained central form.

Clients/Clientsfolder · explore

Relationship memory for actual clients.

What belongs here: Relationship notes for actual clients; private records are not included in this tour.
Why it has its own place: Remembers the relationship while the project holds the actual work and scope.

Illustrative exampleRecord a fictional client’s preferred meeting format and link to the project.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Dated relationship memory

Identities, correspondence and contact details are omitted from this public tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Client relationship recorddocument role · Reconfirm current disposition

Keep relationship context separate from general knowledge.

What it contains: Recorded interactions, linked projects and action checklists.
What it helps prevent: Confusing an old proposed next touch with a current verified obligation.
Readiness: Reconfirm current disposition

Link to this role

Collaborators/Collaboratorsfolder · explore

Actual or potential working relationships.

What belongs here: Context for actual or possible working relationships.
Why it has its own place: Distinguishes a possible collaboration from an agreed engagement.

Illustrative exampleDistinguish an exploratory conversation from an agreed collaboration.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Dated relationship memory

Identities, correspondence and contact details are omitted from this public tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Collaborator relationship recorddocument role · Reconfirm current disposition

Keep relationship context separate from general knowledge.

What it contains: Recorded interactions, linked projects and action checklists.
What it helps prevent: Confusing an old proposed next touch with a current verified obligation.
Readiness: Reconfirm current disposition

Link to this role

Follow_Ups/Follow Upsfolder · explore

Cross-relationship view of promised next touches and waiting loops.

What belongs here: A view of promised next touches and links to their relationship records.
Why it has its own place: Points back to the actual promise and owner; it is not an automatic reminder service.

Illustrative exampleFind the owner and context for a sample promised follow-up.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Linked review view

The relationship note owns the original action; this view helps find it.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Four-source action viewdocument role · Review before resuming

Point back to relationship records with recorded actions.

What it contains: Source dates, proposed or promised work and unverified current disposition.
What it helps prevent: Losing an action or duplicating it into a competing task list.
Readiness: Review before resuming

Link to this role

Partners/Partnersfolder · explore

Relationship memory for ongoing partners and allied organizations.

What belongs here: Context for ongoing partners and allied organizations.
Why it has its own place: Preserves relationship context without treating a label as a legal agreement.

Illustrative exampleDocument the purpose of a fictional partnership and link to the agreed work.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Dated relationship memory

Identities, correspondence and contact details are omitted from this public tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Partner relationship recordsdocument role · Reconfirm current disposition

Keep relationship context separate from general knowledge.

What it contains: Recorded interactions, linked projects and action checklists.
What it helps prevent: Confusing an old proposed next touch with a current verified obligation.
Readiness: Reconfirm current disposition

Link to this role

Prospects/Prospectsfolder · explore

Optional place for real prospective-client opportunities.

What belongs here: An optional place for real prospective-client opportunities.
Why it has its own place: Separates real opportunities from generic market research.

Illustrative exampleSeparate a fictional active opportunity from generic market research.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only reserved home

An index establishes a place for future relationship records; it does not establish an active pipeline.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Vendors/Vendorsfolder · explore

Relationship/operational memory for suppliers Brian actually evaluates or uses.

What belongs here: Notes on actual supplier evaluation, experience and working relationships.
Why it has its own place: Keeps actual supplier experience separate from general company research.

Illustrative exampleKeep a sample supplier experience separate from public company research.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only reserved home

An index establishes a place for future relationship records; it does not establish an active pipeline.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

index.mdSection mapfile

Relationship-memory router with creation and linking rules.

What belongs here: Relationship navigation, note-creation rules and project-linking guidance.
Why it has its own place: Makes relationships findable without turning every named person into a contact record.

Illustrative exampleDecide whether a name belongs in a reference note or a relationship record.

Reusable AI methods

06_Prompt_Systems/

Layer 1 · folder

Keep image, video, meeting and prompt-quality methods, plus agent-design research.

What belongs here: Reusable AI instructions, creative methods, quality checks and viewpoint-design research.
What this helps prevent: Keeps useful instructions and lessons from starting over in every chat.

Illustrative exampleReuse an image-brief method with new inputs while retaining its quality checklist.

One level inside

Layer 2 · 12 items

Brand_Characters/Brand Charactersfolder · explore

Reusable brand spokesperson, mascot and character-continuity design.

What belongs here: Methods for spokesperson, mascot and character continuity.
Why it has its own place: Keeps a character’s visual identity consistent across creative work.

Illustrative exampleDescribe the stable visual traits of a fictional mascot.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Character definition in development

A definition can specify the intended role while continuity references and release checks remain unfinished.

Curated roles · related items may be grouped; private contents omitted.

Character definitiondocument role · Definition; continuity work remains

Give a recurring presenter a clear job.

What it contains: Voice, appearance, teaching role and intended uses.
What it helps prevent: Prevents unrelated experiments becoming an inconsistent character.
Readiness: Definition; continuity work remains

Link to this role

Character QA requirementsdocument role · Review requirements

Keep synthetic media understandable and accountable.

What it contains: Continuity, source, likeness and disclosure checks.
What it helps prevent: Prevents generated scenes being mistaken for documentary proof.
Readiness: Review requirements

Link to this role

Client_Meetings/Client Meetingsfolder · explore

Reusable workflow for turning meetings into evidence-linked project and knowledge outputs.

What belongs here: A reusable method for turning meetings into source-linked outputs.
Why it has its own place: Keeps the reusable meeting method separate from private recordings and actual decisions.

Illustrative exampleConvert a fictional meeting into decisions, questions and proposed actions.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reusable processing method

Private client knowledge remains scoped to its source project. Reusable lessons must be generalized before public use.

Curated roles · related items may be grouped; private contents omitted.

Meeting output formdocument role · Reusable reference

Capture useful project information.

What it contains: Decisions, uncertainties, actions and source references.
What it helps prevent: Prevents a conversation becoming only a vague summary.
Readiness: Reusable reference

Link to this role

Dual-use workflowdocument role · Reusable reference

Separate client memory from reusable learning.

What it contains: Evidence handling, attribution, revision and review rules.
What it helps prevent: Prevents private details leaking into general content.
Readiness: Reusable reference

Link to this role

Processing promptdocument role · Reusable reference

Invoke the method on a bounded conversation.

What it contains: Inputs, selected scope and expected outputs.
What it helps prevent: Keeps a saved method distinct from an automatic run.
Readiness: Reusable reference

Link to this role

Higgsfield/Higgsfieldfolder · explore

Reserved home for Higgsfield-specific patterns and QA lessons.

What belongs here: A reserved place for provider-specific patterns and quality lessons.
Why it has its own place: Reserves provider-specific learning; this folder alone does not prove a working integration.

Illustrative exampleStore a future reviewed lesson from an authorized image test.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reserved reference shelf

The folder does not establish an installed model or live integration.

Curated roles · related items may be grouped; private contents omitted.

Higgsfield indexnavigation · Index-only scaffold

Provide a place to find model-specific lessons.

What it contains: An index awaiting useful prompt patterns and QA lessons.
What it helps prevent: Keeps a named route available without inventing content.
Readiness: Index-only scaffold

Link to this role

Image_Generation/Image Generationfolder · explore

Provider-neutral image/style/control prompt patterns.

What belongs here: Provider-neutral patterns for image briefs, style and controls.
Why it has its own place: Reuses image methods across projects without duplicating every output.

Illustrative exampleUse a structured composition brief for a fictional product image.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Linked reference entry point

The folder does not establish an installed model or live integration.

Curated roles · related items may be grouped; private contents omitted.

Image generation indexnavigation · Linked-only

Provide a place to find model-specific lessons.

What it contains: Links to relevant saved methods or source summaries.
What it helps prevent: Keeps a named route available without inventing content.
Readiness: Linked-only

Link to this role

index.mdSection mapfile

Navigation and rules for reusable prompt/agent design patterns.

What belongs here: Navigation and rules for reusable prompting and agent-design methods.
Why it has its own place: Routes methods to the right provider, task and quality checks.

Illustrative exampleFind the appropriate method and its checks before preparing a new task.

Kling/Klingfolder · explore

Reserved Kling-specific motion and failure-pattern notes.

What belongs here: A reserved place for provider-specific motion patterns and failure notes.
Why it has its own place: Reserves provider-specific learning; local tests or integration were not established by this audit.

Illustrative exampleRecord a future test’s motion limitation with its date and settings.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reserved reference shelf

The folder does not establish an installed model or live integration.

Curated roles · related items may be grouped; private contents omitted.

Kling indexnavigation · Index-only scaffold

Provide a place to find model-specific lessons.

What it contains: An index awaiting useful prompt patterns and QA lessons.
What it helps prevent: Keeps a named route available without inventing content.
Readiness: Index-only scaffold

Link to this role

Nano_Banana/Nano Bananafolder · explore

Reserved Nano Banana-specific prompt and behavior notes.

What belongs here: A reserved place for provider-specific prompting and behavior notes.
Why it has its own place: Reserves provider-specific learning; separate client buildouts own their production workflows.

Illustrative exampleSave a reusable lesson while keeping a client’s actual assets in its project.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reserved reference shelf

The folder does not establish an installed model or live integration.

Curated roles · related items may be grouped; private contents omitted.

Nano Banana indexnavigation · Index-only scaffold

Provide a place to find model-specific lessons.

What it contains: An index awaiting useful prompt patterns and QA lessons.
What it helps prevent: Keeps a named route available without inventing content.
Readiness: Index-only scaffold

Link to this role

Perspective_Engine__AI_Agent_Personality_System/Perspective Engine — viewpoint researchfolder · explore

Develop and compare governed viewpoints and assistant profiles.

What belongs here: Viewpoint and agent-profile research, design, calibration and local tooling.
Why it has its own place: Keeps source evidence, viewpoint design and evaluation together; the folder’s existence does not establish an approved production service.

Illustrative exampleCompare two proposed viewpoints using a fictional question and an explicit review rubric.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Research and calibration workbench

There is no approved compiled runtime. Local tools and useful demonstrations do not remove the independent evaluation and owner-approval gates.

Curated roles · related items may be grouped; private contents omitted.

System architecturemodule · Research and proposed contracts

Define what may be trusted and how a response is recorded.

What it contains: Identity, evidence, versioning, authority and output contracts.
What it helps prevent: Prevents a connected graph being mistaken for approved runtime.
Readiness: Research and proposed contracts

Link to this role

Source researchmodule · Research workbench

Plan and ground the lens library.

What it contains: Source maps, research queues and capture forms.
What it helps prevent: Prevents viewpoints without a source or explicit interpretation.
Readiness: Research workbench

Link to this role

Lens templatesmodule · Templates, not approved lenses

Give a viewpoint a consistent shape.

What it contains: Forms for role, personality, symbolic and audience lenses.
What it helps prevent: Prevents a new schema for every idea.
Readiness: Templates, not approved lenses

Link to this role

Business-role librarymodule · Starter and candidate lenses

Explore the responsibilities of a practical role.

What it contains: Priorities, concerns, blind spots and review questions.
What it helps prevent: Keeps operational judgment visible.
Readiness: Starter and candidate lenses

Link to this role

Archetype librarymodule · Interpretive starters

Explore story and emotional emphasis.

What it contains: Interpretive patterns used in brand and character design.
What it helps prevent: Keeps creative interpretation separate from diagnosis.
Readiness: Interpretive starters

Link to this role

Personality frameworksmodule · Mixed research and starters

Keep different evidence modes distinct.

What it contains: Research-backed, interpretive and symbolic framework families.
What it helps prevent: Prevents unlike models becoming one false certainty.
Readiness: Mixed research and starters

Link to this role

Profile composermodule · Candidate procedures

Combine selected lenses for a bounded job.

What it contains: Profile forms, weights, conflict rules and panel presets.
What it helps prevent: Prevents an unstructured blend of viewpoints.
Readiness: Candidate procedures

Link to this role

Perspective promptsmodule · Workbench prompts

Produce separate views before synthesis.

What it contains: Single-view, council, extraction and normalization patterns.
What it helps prevent: Keeps disagreements visible rather than smoothing them away.
Readiness: Workbench prompts

Link to this role

Tests and calibrationmodule · Calibration; approval remains separate

Examine whether outputs are distinct and useful.

What it contains: Fixtures, internal results, blind-review packets and validators.
What it helps prevent: Prevents a compelling demonstration being treated as proof.
Readiness: Calibration; approval remains separate

Link to this role

Product ideasmodule · Proposed work

Record possible future interfaces and offers.

What it contains: MVP, intake, user-interface and service concepts.
What it helps prevent: Keeps future scope out of the current research task.
Readiness: Proposed work

Link to this role

Example profilesmodule · Mixed examples; curated public roles only

Make the schemas inspectable.

What it contains: Fictional examples and privately scoped workbench records.
What it helps prevent: Shows the format while retaining different privacy boundaries.
Readiness: Mixed examples; curated public roles only

Link to this role

Sales-perspective modulemodule · Research and candidate lenses

Test how an offer is framed.

What it contains: Principle-based lenses, broad response hypotheses and channel forms.
What it helps prevent: Prevents imitation or unsupported claims about a buyer.
Readiness: Research and candidate lenses

Link to this role

Research pipelinemodule · Methods and dated run evidence

Turn a source into a reviewed proposal.

What it contains: Queues, summaries, claim cards, QA and approval records.
What it helps prevent: Separates source processing from promotion.
Readiness: Methods and dated run evidence

Link to this role

Customer-context designmodule · Starter design; no live runtime implied

Define permitted context and reviewable routing.

What it contains: Profile schemas, signals, scoring, overrides and privacy controls.
What it helps prevent: Prevents unsupported private inference.
Readiness: Starter design; no live runtime implied

Link to this role

File conversionmodule · Preprocessing tools and methods

Make an unreadable source usable as text.

What it contains: Conversion workflows, status records and OCR escalation.
What it helps prevent: Prevents guessing what an unreadable file says.
Readiness: Preprocessing tools and methods

Link to this role

Task specificationsmodule · Historical and reusable specifications

Retain reusable or historical work requests.

What it contains: Bounded task prompts and links to recorded outcomes.
What it helps prevent: Prevents an old instruction being mistaken for new authorization.
Readiness: Historical and reusable specifications

Link to this role

Build and research reportsmodule · Evidence records

Record what was actually done.

What it contains: Dated imports, research runs, QA and remaining decisions.
What it helps prevent: Keeps preparation, execution and approval distinct.
Readiness: Evidence records

Link to this role

Prompt_QA/Prompt QAfolder · explore

General prompt/workflow quality, research extraction, context and risk controls.

What belongs here: Reusable checks for prompting, extraction, context and output quality.
Why it has its own place: Keeps reusable checks and lessons separate from one-off results.

Illustrative exampleCheck whether a sample answer distinguishes source evidence from inference.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Reusable methods and checks

A Markdown workflow can guide an agent without being installed, scheduled or currently tested.

Curated roles · related items may be grouped; private contents omitted.

Planning and context methodsdocument role · Reusable reference

Give a task the right scope and supporting information.

What it contains: Handoffs, source reconciliation and bounded planning.
What it helps prevent: Prevents lost constraints and repeated work.
Readiness: Reusable reference

Link to this role

Design and content workflowsdocument role · Reusable reference

Apply repeatable quality checks to creative output.

What it contains: Voice, evidence, style, format and review methods.
What it helps prevent: Prevents polished but unsupported output.
Readiness: Reusable reference

Link to this role

Security and evaluation checksdocument role · Reusable reference

Test important risks and failure modes.

What it contains: Permission boundaries, source handling and comparison methods.
What it helps prevent: Keeps a passing example separate from broad trust.
Readiness: Reusable reference

Link to this role

Prompt_Template.mdPrompt Templatefile

Open the maintained prompt-note form from this working area.

What belongs here: A compatibility pointer and embedded view of the central prompt-note form.
Why it has its own place: Keeps old links useful while the single maintained form lives in _Templates/Prompt_Note_Template.md.

Illustrative exampleUse the maintained form to record a prompt’s inputs, expected output and checks.

Veo/Veofolder · explore

Veo-specific video prompting and quality context.

What belongs here: Provider-specific video prompting research and quality context.
Why it has its own place: Keeps provider research and reported limitations; saved notes are not fresh product verification.

Illustrative exampleRecord a dated observation that would need rechecking before a new project.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Linked reference entry point

The folder does not establish an installed model or live integration.

Curated roles · related items may be grouped; private contents omitted.

Veo indexnavigation · Linked-only

Provide a place to find model-specific lessons.

What it contains: Links to relevant saved methods or source summaries.
What it helps prevent: Keeps a named route available without inventing content.
Readiness: Linked-only

Link to this role

Video_Generation/Video Generationfolder · explore

Provider-neutral video, scene, editing, motion and QA workflows.

What belongs here: Reusable scene, motion, editing and quality-review methods.
Why it has its own place: Keeps scene, motion and editing methods reusable while project media stays with its project.

Illustrative examplePlan a fictional three-scene sequence while leaving production media with its project.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Methods with reserved workflow shelves

Accepted production tools live in their receiving buildouts. These reference notes and empty shells do not create another orchestrator.

Curated roles · related items may be grouped; private contents omitted.

Planning and continuity methodsdocument role · Reusable reference

Prepare a sequence before generating it.

What it contains: Scripts, scenes, references, continuity and review gates.
What it helps prevent: Prevents disconnected clips and avoidable rework.
Readiness: Reusable reference

Link to this role

Editing and finishing referencesdocument role · Dated methods; verify before use

Choose how human and tool work fit together.

What it contains: Hybrid editing, animation and dated feasibility notes.
What it helps prevent: Keeps a tool claim separate from current tested capability.
Readiness: Dated methods; verify before use

Link to this role

Reserved workflow spacesreserved space · Empty scaffolds

Hold a future bounded workflow if needed.

What it contains: Two currently empty workflow shelves, including an output-package placeholder.
What it helps prevent: Makes their unfinished state explicit.
Readiness: Empty scaffolds

Link to this role

The field notebook

07_Field_and_Operations/

Layer 1 · folder

Keep Grow Wild job methods, estimating notes, materials, observations and handoff formats.

What belongs here: Practical job methods, estimates, materials, design reasoning, observations and handoff formats, including reserved areas.
What this helps prevent: Brings knowledge back to practical work; drafts still need field review.

Illustrative exampleCapture a site observation, connect it to a proposed method and retain the assumptions for review.

One level inside

Layer 2 · 9 items

Client_Handoffs/Client Handoffsfolder · explore

Aftercare, closeout, warranty/watering and client education lane.

What belongs here: A lane for aftercare, closeout and client-education material.
Why it has its own place: Reserves an aftercare/closeout lane without implying a handoff has already been delivered.

Illustrative examplePrepare a draft care sheet for a fictional planting project.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only reserved home

Reserved for aftercare, closeout and client education records. No local records were present at the reviewed layer.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Daily_Labor_Logs/Daily Labor Logsfolder · explore

Field work, crew time, weather, materials and next-action records.

What belongs here: A structure for work performed, crew time, weather, materials and next actions.
Why it has its own place: Provides a way to record work; an empty tracker is not a completed timecard.

Illustrative exampleRecord a fictional workday’s observations without treating a blank form as completed work.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Draft tracking specification

The current item describes a workflow; it is not a set of filled job logs.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Weekly field trackerdocument role · Draft specification

Define how dispatch, time and closeout could be recorded.

What it contains: A reusable tracking specification.
What it helps prevent: Mistaking a proposed tracker for integrated timekeeping.
Readiness: Draft specification

Link to this role

Estimates/Estimatesfolder · explore

Scope, costing assumptions and draft estimating knowledge.

What belongs here: Draft scopes, costing assumptions and estimating knowledge.
Why it has its own place: Keeps assumptions visible before they become an approved estimate.

Illustrative exampleList assumptions before calculating a sample estimate.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Blank estimate form

No approved rates or completed job estimates are shown here.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Small-job profitability carddocument role · Blank form

Give scope and costs a consistent place.

What it contains: Fields for assumptions, costs and review.
What it helps prevent: Losing overhead or scope assumptions when estimating.
Readiness: Blank form

Link to this role

Field_Log_Template.mdField Log Templatefile

Open the maintained field-note form from this working area.

What belongs here: A compatibility pointer and embedded view of the central field-log form.
Why it has its own place: Keeps old links useful while the single maintained form lives in _Templates/Field_Log_Note_Template.md.

Illustrative exampleOpen the shortcut to capture a fictional field observation consistently.

index.mdSection mapfile

Practical Grow Wild job-memory and method navigation.

What belongs here: Navigation for practical methods and job memory.
Why it has its own place: Routes practical methods and job memory, including draft or reserved areas.

Illustrative exampleFind the right place for a site observation or reusable procedure.

Installation_Methods/Installation Methodsfolder · explore

Reusable field procedures, QA, troubleshooting and observation protocols.

What belongs here: Reusable procedures, checks, troubleshooting and observation methods.
Why it has its own place: Keeps procedures and checks together; field-validation status still matters.

Illustrative exampleDocument a sample procedure and the field checks it still requires.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Methods and observation forms

Domain methods need project-specific verification before field use.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Method drafts and walkthroughsdocument role · Draft methods

Explain proposed field practices and the reasoning behind them.

What it contains: Soil-related methods and audience-specific walkthrough drafts.
What it helps prevent: Treating a saved how-to as evidence of a successful installation.
Readiness: Draft methods

Link to this role

Field-record templatedocument role · Blank form

Provide a place for actual observations.

What it contains: Blank observation, evidence and follow-up fields.
What it helps prevent: Confusing the method with the result of using it.
Readiness: Blank form

Link to this role

Materials/Materialsfolder · explore

Material quantities, suppliers, substitutions and lessons.

What belongs here: A reserved lane for quantities, substitutions, supplier references and lessons.
Why it has its own place: Reserves material records without pretending a full supplier database exists.

Illustrative exampleRecord the reason for a proposed material substitution.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only reserved home

Reserved for material, supplier, quantity and substitution references. No local records were present at the reviewed layer.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Planting_Designs/Planting Designsfolder · explore

Plant palettes, concepts, substitutions, layout and phased design decisions.

What belongs here: Plant palettes, layout reasoning, alternatives and phased design decisions.
Why it has its own place: Keeps design reasoning and alternatives; research palettes still need project approval.

Illustrative exampleCompare two hypothetical planting palettes against a sample site’s constraints.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Historical palette research

Historical plant references are candidates, not approved planting designs.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Palette referencesdocument role · Research candidates

Preserve design ideas for later suitability checks.

What it contains: Historical references and candidate ideas.
What it helps prevent: Selecting plants without checking the specific site and constraints.
Readiness: Research candidates

Link to this role

Site_Notes/Site Notesfolder · explore

Observed sun, soil, water, access, slopes, drainage and constraints.

What belongs here: A lane for observed site conditions and practical constraints.
Why it has its own place: Reserves site observations without claiming an inspection occurred.

Illustrative exampleSeparate an observed drainage issue from an untested explanation of its cause.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only reserved home

Reserved for dated site observations and constraints. No local records were present at the reviewed layer.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Personal reflection

08_Journal_and_Reflection/

Layer 1 · folder

A separate home for notes I explicitly label as journal, reflection or personal decisions.

What belongs here: Private, explicitly chosen journal, reflection, decision and review notes. This public tour shows the structure only.
What this helps prevent: Keeps personal thinking distinct from business facts. This tour shows structure only.

Illustrative exampleChoose to record a lesson from a fictional week and a question to revisit.

One level inside

Layer 2 · 7 items

Business_Reflection/Business Reflectionfolder · explore

Brian’s explicitly identified reflections on business direction and execution.

What belongs here: Personal reflections explicitly identified as such by the owner.
Why it has its own place: Keeps explicitly labeled personal reflection separate from general business research.

Illustrative exampleWrite a fictional reflection about which type of work to prioritize next.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only; structure reviewed

Reserved for business direction and tradeoffs. No private narrative was inspected or copied into this tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Creative_Blocks/Creative Blocksfolder · explore

Explicitly identified creative blocks, stuck points and useful next moves.

What belongs here: Owner-identified stuck points and possible next moves.
Why it has its own place: Captures a stuck point I identify, rather than an AI’s interpretation of my psychology.

Illustrative exampleRecord an illustrative choice to try a smaller first draft.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only; structure reviewed

Reserved for creative obstacles and next steps. No private narrative was inspected or copied into this tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Daily_Journal/Daily Journalfolder · explore

Entries Brian explicitly labels daily journal notes.

What belongs here: Entries the owner deliberately chooses to treat as journal notes.
Why it has its own place: Contains only entries I choose to treat as a journal.

Illustrative exampleCreate a clearly fictional daily reflection for a demonstration.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only; structure reviewed

Reserved for explicitly labeled personal journal entries. No private narrative was inspected or copied into this tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Decision_Log_Template.mdDecision Log Templatefile

Open the maintained decision-note form from this working area.

What belongs here: A compatibility pointer and embedded view of the central decision-note form.
Why it has its own place: Keeps old links useful while the single maintained form lives in _Templates/Decision_Log_Note_Template.md.

Illustrative exampleCapture a sample choice, alternatives, reasons and a revisit date.

Decision_Logs/Decision Logsfolder · explore

Decisions Brian wants to remember, with options/reasons/revisit dates.

What belongs here: Personal decisions with their reasons, alternatives and review points.
Why it has its own place: Preserves personal reasoning without replacing a client approval record.

Illustrative exampleExplain a fictional scheduling choice so its reasoning can be revisited.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only; structure reviewed

Reserved for decisions and reasons to revisit them. No private narrative was inspected or copied into this tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

index.mdSection mapfile

Opt-in home for Brian-labeled journal/reflection/decision/review notes.

What belongs here: The opt-in guide for personal reflection and review notes.
Why it has its own place: Explains this opt-in area. No personal entries were read for this structural tour.

Illustrative exampleChoose whether a note is personal reflection or project evidence.

Weekly_Reviews/Weekly Reviewsfolder · explore

Brian-labeled weekly wins, misses, patterns, decisions and next actions.

What belongs here: Owner-written reviews of wins, misses, patterns and next actions.
Why it has its own place: Keeps my own review distinct from an automated audit of activity.

Illustrative exampleReview a fictional week and select one practical adjustment.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Index-only; structure reviewed

Reserved for weekly patterns and next focus. No private narrative was inspected or copied into this tour.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

The tool cupboard

09_Tools/

Layer 1 · folder

Keep scripts, helper packages, starter kits and planned or reference tools.

What belongs here: Helper scripts, preserved software packages, starter kits and reserved tool ideas, each with its own usage requirements.
What this helps prevent: Separates software that may do work from notes that explain it. Presence is not proof it is running.

Illustrative exampleUse an approved helper to prepare a review view, then inspect its output and source links.

One level inside

Layer 2 · 12 items

index.mdSection mapfile

Discovery map for helper tools.

What belongs here: A discovery map for local helpers and their documented roles.
Why it has its own place: Helps find a helper; listing it does not activate it.

Illustrative exampleLocate a tool’s instructions and recorded checks before deciding to run it.

cross_reference.pycross referencefile

Compare two independently created plans and print a reconciliation/build prompt.

What belongs here: A helper for comparing two plans and preparing a reconciliation prompt.
Why it has its own place: Compares two plans. Remote use would send their contents to the chosen service and needs appropriate permission.

Illustrative exampleCompare two fictional outlines to identify agreements and unanswered questions.

font_replacement_agent/font replacement agentfolder · explore

Reserved home for a future font search/preview tool.

What belongs here: A reserved home for a proposed font search and preview helper.
Why it has its own place: Reserves a possible font tool; planned does not mean installed.

Illustrative exampleA future tool could preview a font substitute in a sample layout.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Prompt workflow; application ideas

A folder named agent does not by itself imply running software.

Curated roles · related items may be grouped; private contents omitted.

Usage READMEdocument role · Reference; later versions proposed

Explain a font-comparison prompt and later ideas.

What it contains: The current prompt workflow and proposed app/API directions.
What it helps prevent: Calling a future interface an installed tool.
Readiness: Reference; later versions proposed

Link to this role

github_backup/Backup and recovery helpersfolder · explore

Committed-history backup and current-working-copy recovery.

What belongs here: Tools and guidance for committed-history backup and working-copy recovery.
Why it has its own place: Separates committed-history backup from local recovery; a folder is not proof a backup succeeded.

Illustrative exampleCheck an actual backup receipt instead of assuming a folder proves backup success.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Scripts and recovery guidance

A backup helper is not proof that a fresh backup exists.

Curated roles · related items may be grouped; private contents omitted.

Backup and snapshot helpersdocument role · Run only for an authorized task

Support authorized backups and local recovery snapshots.

What it contains: Scripts, repository lists, tests and usage guidance.
What it helps prevent: Confusing committed history with unsaved working-copy changes.
Readiness: Run only for an authorized task

Link to this role

Recovery storagemodule · Private contents omitted

Retain local recovery material.

What it contains: Private snapshot storage, not exposed by this guide.
What it helps prevent: Publishing a recovery copy with the public website.
Readiness: Private contents omitted

Link to this role

grow_wild_external_drive_intake/Protected archive intakefolder · explore

Protected-source metadata and evidence tooling for Grow Wild archive intake.

What belongs here: Metadata and evidence helpers for a protected archive-intake process.
Why it has its own place: Keeps archive-intake metadata tools separate from protected source media.

Illustrative exampleInspect an approved inventory without opening or moving source media.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Bounded intake utilities

Historical receipts describe earlier work; no external drive is accessed by this tour.

Curated roles · related items may be grouped; private contents omitted.

Inventory and review utilitiesdocument role · Separate source-access authority required

Support scoped archive inventories and review.

What it contains: Scanners, manifests, review interfaces and tests.
What it helps prevent: Treating a source inventory as finished knowledge processing.
Readiness: Separate source-access authority required

Link to this role

grow_wild_youtube_intake/Business playlist intakefolder · explore

Preserve and reconcile a specific Grow Wild YouTube playlist.

What belongs here: Playlist capture and reconciliation helpers for business research.
Why it has its own place: Preserves playlist capture history; capture is separate from knowledge review.

Illustrative examplePreserve a sample playlist capture and record what still needs summarizing.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Capture adapter with historical receipts

Capture and source interpretation have separate completion states.

Curated roles · related items may be grouped; private contents omitted.

Playlist adapterdocument role · Historical capture evidence

Support resumable capture against an exact source list.

What it contains: Adapter code and usage instructions.
What it helps prevent: Confusing an unavailable caption with a processed source.
Readiness: Historical capture evidence

Link to this role

review_packet_builder/review packet builderfolder · explore

Turn processed meeting notes into an HTML action review surface.

What belongs here: A helper that turns processed meeting notes into an HTML review view.
Why it has its own place: Makes meeting actions easier to review; browser checkboxes do not automatically update the source notes.

Illustrative exampleOpen an illustrative action card while its Markdown note remains the maintained record.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Implemented local helper

Its current built-in packet is specific; it is not a universal automatic review system.

Curated roles · related items may be grouped; private contents omitted.

Builder and templatesdocument role · Local view builder

Turn selected processed notes into a review page.

What it contains: Local generation code and display templates.
What it helps prevent: Assuming a displayed checkbox writes back to Markdown.
Readiness: Local view builder

Link to this role

second-brain-template-kit/second brain template kitfolder · explore

Reusable whole-repository starter architecture.

What belongs here: A reusable starter structure for a whole repository.
Why it has its own place: Keeps a reusable starting structure separate from this live, populated vault.

Illustrative exampleStart a clean example vault without copying private notes from the working vault.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Copy-first distribution scaffold

This parallel structure is a starter package, not a second live vault.

Curated roles · related items may be grouped; private contents omitted.

Knowledge workflow foldersmodule · Configure for each copy

Provide starting homes for a new project’s sources and knowledge.

What it contains: Intake, review, source library, knowledge and output scaffolds.
What it helps prevent: Mixing a reusable kit into the current working vault.
Readiness: Configure for each copy

Link to this role

Instructions and reusable formsmodule · Starter material

Give a new copy consistent working rules.

What it contains: Agents, workflows, templates, prompts and modules.
What it helps prevent: Starting a new workspace without defining how information moves.
Readiness: Starter material

Link to this role

Release and setup recordsdocument role · Check before distribution

Explain setup, limits and distribution checks.

What it contains: Root guides, examples, dependency information and historical validation.
What it helps prevent: Treating an earlier check as fresh release clearance.
Readiness: Check before distribution

Link to this role

standalone_slide_deck_builder/standalone slide deck builderfolder · explore

Preserved portable Markdown/JSON-to-PowerPoint package.

What belongs here: A preserved Markdown/JSON-to-PowerPoint package.
Why it has its own place: Preserves a slide-building package; this audit did not install or run it.

Illustrative examplePrepare a sample deck from fictional notes after checking the package instructions.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Preserved; uninstalled package

Keeping a portable package does not install or execute it.

Curated roles · related items may be grouped; private contents omitted.

README and packaged builderdocument role · Uninstalled package

Keep a portable presentation builder available for future review.

What it contains: Usage context and a preserved archive.
What it helps prevent: Assuming a saved ZIP is an available running application.
Readiness: Uninstalled package

Link to this role

vault_gardener/vault gardenerfolder · explore

Analyze disconnected Markdown nodes and report proposed maintenance.

What belongs here: Helpers for finding disconnected notes and proposing maintenance.
Why it has its own place: Finds disconnected notes and proposes maintenance without silently reorganizing them.

Illustrative exampleIdentify an unlinked sample note and propose where it belongs.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Report-only analysis helper

It reports link structure. It does not decide what can be deleted.

Curated roles · related items may be grouped; private contents omitted.

Link-graph scriptdocument role · Boundary tested with a fixture

Analyze ordinary in-vault Markdown notes.

What it contains: Link parsing, orphan classification and a boundary that skips symlinks.
What it helps prevent: Following linked files outside the intended vault during analysis.
Readiness: Boundary tested with a fixture

Link to this role

Dated reportsmodule · No fresh full-vault run

Preserve the result and scope of a particular run.

What it contains: Historical link and orphan analysis.
What it helps prevent: Treating an old report as a current whole-vault check.
Readiness: No fresh full-vault run

Link to this role

External workspace architecture referenceExternal workspace architecture referenceGeneral category

General category · General category shown; the specific local name is omitted from this public tour.

Reference copy of an external workspace scaffold/audit methodology.

What belongs here: A reference copy of an external workspace-architecture method.
Why it has its own place: Keeps an external method as a reference; a copied instruction is not an active tool.

Illustrative exampleCompare a proposed folder layout against a reference checklist.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Review-only reference package

The identifying package name is generalized in this tour.

Curated roles · related items may be grouped; private contents omitted.

Reference specification and examplesdocument role · Reference; not installed

Preserve an approach to folder-based workspace design.

What it contains: Documentation, examples, scripts and templates.
What it helps prevent: Mistaking upstream install instructions for a local installation.
Readiness: Reference; not installed

Link to this role

youtube_channel_intake/Channel intakefolder · explore

Configuration-driven channel intake plus Water Stories phase tooling.

What belongs here: Channel-capture configuration and batch-processing helpers.
Why it has its own place: Keeps capture tooling and batch controls; capture does not grant rights to publish sources.

Illustrative exampleRecord a sample capture batch separately from its later knowledge review.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Capture and phase-specific helpers

Source acquisition, knowledge processing and publication approval are separate.

Curated roles · related items may be grouped; private contents omitted.

Generic intake enginedocument role · Inspect task scope before use

Support a bounded set of channel-source captures.

What it contains: Capture code and configuration guidance.
What it helps prevent: Losing the exact source list and exception state.
Readiness: Inspect task scope before use

Link to this role

Phase operators and auditsdocument role · Historical, project-specific

Record a particular project’s processing sequence.

What it contains: Phase-specific helpers and audit logic.
What it helps prevent: Restarting a completed phase from an old task file.
Readiness: Historical, project-specific

Link to this role

Reusable forms

_Templates/

Layer 1 · folder

Keep standard note formats and shared processing standards.

What belongs here: Maintained note forms, processing standards and a separate guide for writing templates.
What this helps prevent: Makes important fields—sources, reasons, next steps—harder to forget.

Illustrative exampleInsert the source-summary form so evidence, uncertainty and related notes have a consistent place.

One level inside

Layer 2 · 16 items

index.mdSection mapfile

Canonical discovery list for reusable note forms and standards.

What belongs here: The discovery list for maintained note forms and standards.
Why it has its own place: Helps select the right note form; whole-project starter kits live elsewhere.

Illustrative exampleSelect the project form instead of inventing another structure.

Agent_Context_Pack_Template.mdAgent Context Pack Templatefile

Build a bounded agent handoff.

What belongs here: A form for handing relevant context, limits and next actions to an assistant.
Why it has its own place: Carries the relevant context, limits and next action to another assistant.

Illustrative examplePackage only the sample project context needed for the next task.

CRM_Note_Template.mdCRM Note Templatefile

Define a relationship note schema.

What belongs here: The maintained relationship-note form.
Why it has its own place: Prompts relationship history and follow-up fields without authorizing contact.

Illustrative exampleCreate a fictional relationship record with context and a next action.

Competitor_Profile_Template.mdCompetitor Profile Templatefile

Structure competitor research.

What belongs here: A form for evidence-linked competitor research.
Why it has its own place: Keeps competitor findings organized and tied to evidence.

Illustrative exampleRecord a fictional positioning comparison with clearly labeled assumptions.

Content_Framework_Template.mdContent Framework Templatefile

Create a reusable content structure.

What belongs here: A form for documenting reusable content structures.
Why it has its own place: Captures a reusable structure rather than pretending the draft is approved public copy.

Illustrative exampleDescribe a reusable explainer outline and when it is useful.

Decision_Log_Note_Template.mdDecision Log Note Templatefile

Define a decision record schema.

What belongs here: The maintained form for options, reasons, decisions and review points.
Why it has its own place: Prompts the options, decision, reason and review point.

Illustrative exampleDocument a fictional tradeoff and why one option was chosen.

Decision_Tree_Template.mdDecision Tree Templatefile

Make conditional choices explicit.

What belongs here: A form for conditional choices and escalation points.
Why it has its own place: Makes branches and “ask a person” conditions explicit.

Illustrative exampleMap when a sample request can proceed and when someone needs to decide.

Field_Log_Note_Template.mdField Log Note Templatefile

Define an operational field record schema.

What belongs here: The maintained form for field observations and next actions.
Why it has its own place: Prompts observations and next actions; a log does not certify safety.

Illustrative exampleRecord a fictional site observation and its evidence source.

Note_Template_Writing_Guide.mdNote Template Writing Guidefile

Explain how to write and maintain the reusable note forms.

What belongs here: Instructions for authoring and maintaining reusable note forms.
Why it has its own place: Keeps authoring instructions separate from the blank form inserted into a new note.

Illustrative exampleAdd guidance to the writing guide while keeping the insertion form clean.

Processing_Standards.mdProcessing Standardsfile

Shared knowledge creation and retrieval discipline.

What belongs here: Shared rules for source use, uncertainty, note purpose and retrieval.
Why it has its own place: Keeps evidence, uncertainty and useful purpose visible in the knowledge we create.

Illustrative exampleMark an unsupported claim as a claim instead of turning it into a fact.

Project_Template.mdProject Templatefile

Start a project hub.

What belongs here: A starter form for a project’s objective, context, decisions and next steps.
Why it has its own place: Gives a project an objective, context, decisions and next steps.

Illustrative exampleCreate a sample project hub with an explicit outcome and owner.

Prompt_Note_Template.mdPrompt Note Templatefile

Define a reusable prompt record.

What belongs here: The maintained form for a prompt’s purpose, inputs, output and checks.
Why it has its own place: Preserves a reusable prompt with inputs and checks, not an automatic command.

Illustrative exampleSave a reusable prompt with the conditions needed to evaluate its result.

SEO_Research_Template.mdSEO Research Templatefile

Organize search/content opportunity research.

What belongs here: A form for search and content-opportunity research.
Why it has its own place: Keeps search opportunities and unanswered questions together.

Illustrative exampleSeparate a possible page opportunity from a verified demand claim.

Sales_Framework_Template.mdSales Framework Templatefile

Turn a sales principle into a practical framework.

What belongs here: A form for turning a sales principle into a practical method.
Why it has its own place: Makes a sales principle usable without guaranteeing an outcome.

Illustrative exampleDocument a sample qualification approach and its limits.

Sales_Objection_Template.mdSales Objection Templatefile

Build reusable objection-handling guidance.

What belongs here: A form for objection-handling questions and response options.
Why it has its own place: Encourages better questions while treating inferred motives as guesses.

Illustrative exampleRecord a useful follow-up question without claiming to know a buyer’s motives.

Source_Summary_Template.mdSource Summary Templatefile

Canonical schema for processing source evidence.

What belongs here: The maintained form for source attribution, explanation, takeaways and connections.
Why it has its own place: Keeps the explanation connected to its source, useful takeaways and related notes.

Illustrative exampleSummarize a fictional article and link its claims to the source.

The task handoff

_Codex_Tasks/

Layer 1 · folder

Keep task instructions, a next-task pointer and waiting/completed records.

What belongs here: Task handoff rules, a next-task pointer, completed specifications and waiting lanes.
What this helps prevent: Distinguishes a current assignment from historical instructions.

Illustrative exampleFind the current task pointer without treating an old brief as a new instruction.

One level inside

Layer 2 · 7 items

README.mdStart herefile

Task-shuttle lifecycle and routing guide.

What belongs here: A guide to the task-handoff lifecycle and where decisions belong.
Why it has its own place: Explains the task handoff lifecycle so old tasks do not restart themselves.

Illustrative exampleCheck how a sample task moves from proposed to completed.

000_NEXT_TASK.mdNext-task pointerfile

Current task-shuttle state.

What belongs here: The task shuttle’s next-task pointer or recorded state.
Why it has its own place: Provides a next-task pointer; the current user request still controls what happens.

Illustrative exampleUse the pointer to orient a requested task, subject to the current user instruction.

001_completed/Completed task historyfolder · explore

Historical task specifications.

What belongs here: Preserved specifications for historical tasks.
Why it has its own place: Preserves old task instructions as history.

Illustrative exampleRead what a past sample cleanup was asked to change.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Historical work orders

Original task text remains evidence of what was requested.

Curated roles · related items may be grouped; private contents omitted.

Completed task briefsdocument role · Historical instructions

Preserve the specification for completed shuttle work.

What it contains: Dated instructions with pointers to their outcomes.
What it helps prevent: Running a completed task again because its wording is imperative.
Readiness: Historical instructions

Link to this role

002_waiting_for_brian/Waiting for the ownerfolder · explore

Reserved task slot for blocked work.

What belongs here: A reserved waiting lane for work needing the owner’s input.
Why it has its own place: Provides a waiting lane; an empty folder does not mean every project is approved.

Illustrative exampleLeave a sample unresolved choice visible until the owner decides.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Empty waiting lane

This lane is currently empty. Project-specific decisions may still be waiting elsewhere.

Curated roles · related items may be grouped; private contents omitted.

CODEX_OPERATING_RULES.mdCODEX OPERATING RULESfile

Operating rules for the Codex task shuttle.

What belongs here: Working rules for the assistant task shuttle.
Why it has its own place: Sets working rules for this task handoff.

Illustrative exampleCheck the task’s permitted scope before making a change.

REFINERY_ROLLOUT_PLAN_20260712.mdREFINERY ROLLOUT PLAN 20260712file

Multi-stage method naming/site rollout plan.

What belongs here: A dated proposal for naming and rolling out the method.
Why it has its own place: Preserves a dated rollout proposal; unfinished historical stages are not new assignments.

Illustrative exampleCompare an old proposed stage with a later completion record.

VAULT_HYGIENE_AND_OBSIDIAN_BRIEF_20260710.mdVAULT HYGIENE AND OBSIDIAN BRIEF 20260710file

Dated proposal/handoff for graph hygiene, Obsidian habits and demo.

What belongs here: A dated cleanup and note-app handoff brief.
Why it has its own place: Preserves a dated cleanup proposal; current records establish what was actually completed.

Illustrative exampleRead the historical reason for a navigation improvement.

The work record

_Codex_Reports/

Layer 1 · folder

Keep the latest result and longer-lived implementation and quality reports.

What belongs here: Assistant work summaries, preserved implementation records and quality-check evidence.
What this helps prevent: Shows what was done and checked, beyond a chat saying “done.”

Illustrative exampleReview what a sample cleanup changed and which checks were actually performed.

One level inside

Layer 2 · 4 items

README.mdStart herefile

Defines transient versus preserved Codex report storage.

What belongs here: Guidance on temporary summaries and preserved evidence.
Why it has its own place: Explains what can be replaced and what evidence should be kept.

Illustrative exampleChoose a durable report home for a sample completed task.

latest_result.mdlatest resultfile

Provide a quick result summary or pointer to supporting reports.

What belongs here: A quick result summary or pointer; dated evidence is needed to establish freshness.
Why it has its own place: Helps readers orient quickly; the dated underlying evidence establishes what was checked and when.

Illustrative exampleFollow a summary to the dated report that supports it.

QA_reports/QA reportsfolder · explore

Historical validation artifacts.

What belongs here: Historical validation records and quality-check artifacts.
Why it has its own place: Keeps checks inspectable; a passed test is not a release approval.

Illustrative exampleRead the scope of a sample link check before interpreting its result.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Historical validation evidence

Execution logs alone do not establish an independent acceptance verdict.

Curated roles · related items may be grouped; private contents omitted.

Smoke-test evidence foldermodule · Outcome limited to saved evidence

Keep a historical test’s logs and local explanation together.

What it contains: Preserved write logs and their outcome qualification.
What it helps prevent: Calling a successful file write a complete acceptance test.
Readiness: Outcome limited to saved evidence

Link to this role

implementation_reports/implementation reportsfolder · explore

Durable implementation/audit trail.

What belongs here: Durable records of changes, checks and outstanding review.
Why it has its own place: Preserves what was changed and checked, including work still awaiting review.

Illustrative exampleCompare a completed edit with the report describing its validation.

Layer 3 / Inside this section

The pieces that do the work

Current shape · Durable implementation history

The rolling result pointer is a convenience; project controls own current project state.

Curated roles · related items may be grouped; private contents omitted.

Section indexnavigation · Navigation

Find the maintained notes and their purpose.

What it contains: Links, short descriptions and relevant readiness or review context.
What it helps prevent: Assuming an empty or dated section proves there is no related work elsewhere.
Readiness: Navigation

Link to this role

Dated outcomes and snapshotsdocument role · Dated evidence

Keep the evidence behind completed bounded work.

What it contains: Implementation receipts, preserved summaries and architecture history.
What it helps prevent: Losing unique narrative when a rolling pointer changes.
Readiness: Dated evidence

Link to this role

My review desk

_Manual_Checks/

Layer 1 · folder

Keep questions needing my judgment, access help or a visual check.

What belongs here: Shared pointers for access help, visual checks and owner decisions.
What this helps prevent: Gives the assistant somewhere to stop and ask instead of guessing.

Illustrative exampleFlag a sample visual review for a person and link to the project that owns it.

One level inside

Layer 2 · 4 items

README.mdStart herefile

Shared manual escalation desk.

What belongs here: A guide to requesting human help and finding the relevant project queue.
Why it has its own place: Explains where to ask for human help; it is not every project’s full approval register.

Illustrative exampleRoute a sample decision to the project that owns its approval.

CREDENTIALS_REQUIRED.mdCREDENTIALS REQUIREDfile

Access-request queue.

What belongs here: Requests for access assistance, rather than passwords or secret values.
Why it has its own place: Tracks access help needed. It is a request list, not a password or key store.

Illustrative exampleRecord that a connection needs owner setup without storing a password.

VISUAL_QA_REQUIRED.mdVISUAL QA REQUIREDfile

Manual visual-check queue.

What belongs here: Pointers to visual checks still requiring human inspection.
Why it has its own place: Tracks visual checks still requiring a person.

Illustrative exampleAsk a person to inspect a sample layout at mobile size.

NEEDS_BRIAN_REVIEW.mdNEEDS BRIAN REVIEWfile

Manual decisions and links to project owner queues.

What belongs here: Pointers to owner decisions and project-specific review queues.
Why it has its own place: Points to decisions needing me without pretending to list every open decision in every project.

Illustrative exampleLink a sample unresolved tradeoff to its project decision record.

Master map

index.md

Layer 1 · file

Links the main areas, system guides and important reports.

What belongs here: Links to the main areas, system guides and selected important reports.
What this helps prevent: Lets people and AI find the right starting point.

Illustrative exampleOpen the master map to choose the right working area.

First visit

README_START_HERE.md

Layer 1 · file

Explains the operating idea, opening the vault and the first workflow.

What belongs here: An introduction to the vault and its first practical workflow.
What this helps prevent: Helps someone get oriented before exploring the full structure.

Illustrative exampleRead the overview before exploring the folder tree.

Instructions for the assistant

agents.md

Layer 1 · file

Defines working principles, folder routing, limits and which detailed instructions to read.

What belongs here: Working principles, routing guidance and limits for an AI assistant.
What this helps prevent: Gives AI a consistent starting point; it does not run anything by itself.

Illustrative exampleHave an assistant check related existing work before new research.

Reusable task requests

AI_Processing_Prompts.md

Layer 1 · file

Provides prompts for working with sources using the vault’s existing rules.

What belongs here: Reusable requests for source processing and other bounded vault tasks.
What this helps prevent: Saves rewriting the same request while keeping the current task explicit.

Illustrative exampleAdapt a source-summary request to a newly captured article.

How to open and use it

Obsidian_Setup_Guide.md

Layer 1 · file

Explains the note app setup and the Web Clipper capture route.

What belongs here: Instructions for opening the vault and using its note-app capture route.
What this helps prevent: Makes the folder system usable without requiring every optional plugin.

Illustrative exampleOpen a sample vault in Obsidian and follow its navigation links.

The architecture idea

REFINERY_METHOD_DRAFT.md

Layer 1 · file

A draft explains research and knowledge preparation in the vault, then handoff to separate execution systems.

What belongs here: A draft explanation of research, knowledge preparation and handoff to execution systems.
What this helps prevent: Keeps the research-to-buildout distinction visible. The method name and design remain draft.

Illustrative exampleExplain how a source can inform a build while its original remains traceable.

Change history

log.md

Layer 1 · file

Records meaningful updates and links to the work.

What belongs here: Meaningful changes with links to their supporting records.
What this helps prevent: Helps the next person see what changed rather than guess from a file date.

Illustrative exampleFind why an example folder’s description changed.

What version control should skip

.gitignore

Layer 1 · file

Lists files that should not be newly tracked, such as temporary files and secrets.

What belongs here: Patterns for files that should not be newly tracked by Git.
What this helps prevent: Reduces accidental additions; it does not erase anything already committed.

Illustrative exampleExclude a temporary output from future tracking while checking existing history separately.

Recorded version history

.git/

Layer 1 · folder

Git’s internal folder records committed versions.

What belongs here: Git’s internal records of committed versions.
What this helps prevent: Supports comparison and recovery of committed work; it is not proof of a remote backup.

Illustrative exampleCompare two committed versions of a sample note.

This supporting folder is explained by role. Private settings, version-history contents and personal configurations are not exposed in this tour.

Notes-app settings

.obsidian/

Layer 1 · folder

Stores Obsidian configuration, navigation preferences and plugin settings.

What belongs here: Local note-app configuration and preferences.
What this helps prevent: Keeps the viewing tool’s setup separate from the knowledge files.

Illustrative exampleKeep a viewing preference separate from the portable Markdown notes.

This supporting folder is explained by role. Private settings, version-history contents and personal configurations are not exposed in this tour.

Assistant-specific settings

.claude/

Layer 1 · folder

Contains local settings, commands, skills and worktree configuration for Claude tooling.

What belongs here: Tool-specific assistant settings and support configuration.
What this helps prevent: Keeps one tool’s setup separate from the portable business notes.

Illustrative exampleKeep an assistant command separate from the project knowledge it may use.

This supporting folder is explained by role. Private settings, version-history contents and personal configurations are not exposed in this tour.

Finder housekeeping

.DS_Store

Layer 1 · file

macOS stores folder-display metadata here.

What belongs here: macOS folder-display metadata.
What this helps prevent: Explains an otherwise mysterious file; it has no business-knowledge role.

Illustrative exampleRecognize this as Finder housekeeping when inspecting a folder.

This is a curated structural snapshot, not a live file browser. The third-layer review inventoried 631 immediate items across 82 sections. This public view groups them into useful roles; it does not publish 631 private filenames or claim that every source body was verified. Three identifying child names use visibly marked general categories. Hidden settings are explained by role; private contents and repeated Finder metadata are omitted. Folder presence does not mean every section is populated or every tool is installed. The review continues as the system changes.

From saved information to useful work

Follow one idea.

Imagine I’m improving a client onboarding process. This illustrative example shows where the information goes—and what changes at each step.

01 / Check existing work

Start with what is already known.

Before I research a subject again, I look for related projects and handoffs in RepoOps. Then I check the linked project notes and receiving records. A missing registry entry is a reason to look a little further, not proof that nothing exists.

02_Projects / project hub

Open this area in the map

Illustrative example · not a private document

A better client onboarding process

Question: Have we already researched or built part of this?
Existing context: A project hub links the source notes, working system and last checked outcome.
Next move: Research the unanswered question, rather than restart the whole project.

This lookup happens when research starts. It does not require a nightly AI task.

02 / Keep the original

Save the source with its context.

A browser clip, meeting note or document enters the appropriate inbox lane. I preserve the original so a later summary can always point back to what was actually said.

00_Inbox / Raw / Web_Clips

Open this area in the map

Illustrative example · not a private document

One captured article

Original: A sample article about welcoming a new client.
Source context: Title, author, link and capture date.
Preserved: The original stays intact while useful notes are made elsewhere.

A source can remain in Raw after it has been summarized. Its folder name does not prove whether processing is finished.

03 / Make it understandable

Write one useful source summary.

The summary records the core idea, practical takeaways, uncertainty and a link to the original. It makes the source easier to use without replacing the evidence.

01_Knowledge_Wiki / Source_Summaries

Open this area in the map

Illustrative example · not a private document

A note I can use later

Core idea: A welcome checklist can make responsibilities easier to follow.
Useful takeaway: Try a clear list of what happens next and who owns each step.
Still to check: Whether this approach fits this business and its customers.

A polished summary is still a summary. An attributed claim does not become verified just because it is well written.

04 / Make it reusable

Turn a useful idea into a method.

When a lesson is useful beyond one source, I can create a linked framework, checklist or concept note. The source summary stays connected so the reasoning can be revisited.

01_Knowledge_Wiki / Frameworks

Open this area in the map

Illustrative example · not a private document

An onboarding checklist draft

Reusable pattern: Confirm the goal → name the owner → list the next steps.
Connected evidence: Links back to the source summary and any later observations.
Status: A draft method to try and review, not a proven result.

Not every source needs a new framework or a note for every person it mentions. Create the smallest useful record.

05 / Use it in a project

Connect knowledge to an outcome.

A project hub brings the relevant sources, decisions and remaining questions together. If a working application or dedicated business system is ready to be built, a bounded specification can go to its own repository.

02_Projects / relevant project

Open this area in the map

Illustrative example · not a private document

A scoped onboarding build

Project need: Draft a welcome process for review.
Research home: The vault keeps sources, methods and provenance.
Implementation home: The receiving buildout keeps its code, tests and operating records.

A handoff describes what was delivered. It does not, by itself, mean that the receiving system works or has been accepted.

06 / Record what happened

Bring the result back to the map.

The receiving system records the actual outcome. The project hub and RepoOps link to that evidence and keep the remaining questions visible, so future research starts from a useful checkpoint.

00_Dashboard / Project_Transfer_Register.md

Open this area in the map

Illustrative example · not a private document

A return receipt

Delivered: A bounded checklist or specification reached the receiving project.
Checked: The receipt names exactly what was inspected or tested.
Still open: Owner usefulness review, unverified claims or any separate release decision.

Delivered, tested, accepted and published are different states. Keep each one explicit.

Where the vault fits

Three places.
Three different jobs.

Research can start in the second brain. A working application can grow into its own home. Clear links keep the two connected.

01 / Second Brain

Keep the knowledge.

Original sources, useful summaries, reusable methods and project context. It answers: “What do we know, and where did it come from?”

02 / RepoOps

Track the work.

RepoOps is my repository-operations record: project locations, handoffs and review status. It answers: “What exists, what was checked, and what remains?”

03 / Receiving buildout

Make the system.

A dedicated repository holds a working app or business workflow, its implementation and its tests. It answers: “What was actually built and accepted here?”

Before starting more research, I check the existing project record and its linked evidence. When work changes, its result is recorded back in the appropriate places. That keeps the next conversation connected to the work already done. It is an on-demand practice, not a promise that everything synchronizes itself.

What the cleanup clarified

The boundaries
are part of the design.

A folder name is useful when it tells me both what belongs there and what decision I still need to make.

Original sources and useful knowledge have different homes.

An archived original is still an original. The summary and reusable method belong in the knowledge layer. Moving a source into Processed does not verify its claims, and keeping it in Raw does not mean nobody has reviewed it.

Knowing about someone is different from managing a relationship.

A Wiki note can explain a person or company. CRM records my relationship, conversations and follow-ups. A project hub organizes the work. Each record should point to the relevant context without becoming a competing master copy.

An instruction, a template and a running tool are different things.

Instructions guide how work should be done. A template gives a note a useful shape. A script or application can perform a specific task when it is run. Finding a folder called “engine” or “agent” does not establish that an automated system is operating.

A handoff needs a return path.

If research becomes a buildout, the vault should know where the implementation lives and what the receiving project actually accepted. That is how the next research request can begin with an informed question instead of an obsolete plan.

A small glossary for the tour

Vault: The master folder containing the connected notes and supporting files.
Index: A navigation note that points to the relevant material and tells you where to begin.
Markdown: A readable text format for notes, headings, lists and links. The filenames usually end in .md.
Provenance: The record of where an idea or claim came from, including its source and any useful context.
Handoff: A bounded package sent to the place that will use or implement it.
Receipt: A record of what arrived, what was checked, the result and any remaining review.

Make the structure serve your work

Start smaller. Keep it useful.

My vault reflects several kinds of work and a lot of experimentation. You do not need every folder here to begin. Start with a place for original material, a place for useful knowledge and a place for current work. Add structure when a real need gives it a job.

The goal is a system you can explain, navigate and trust within the limits of its evidence.

Continue with part two: From Second Brain to Grow Wild follows the research through RepoOps, people, project questions and a receiving workspace.

Explore the AI Business Brain

Inside mysecond brain.

Memory I cancome back to.

The whole vault

A place for each job

More specific homes

The working pieces

Open the system.

Open a folder. Then ask what is inside.

The vault

The front desk

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The receiving area

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The reference library

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The project desks

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The sales shelf

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The editorial room

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

Relationship memory

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

Reusable AI methods

One level inside

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

The pieces that do the work

Inside my
second brain.

Memory I can
come back to.

Three places.
Three different jobs.