PowerUp Coaching — Living Knowledge Base

Part 5a: An Ambient Folder, End to End (Stages 1-2)

2 min read

Now we build something real. This piece and the next three walk through a complete ambient folder system—from empty directory to mature infrastructure. You’ll see how each concept from the previous pieces actually comes together in practice.

An “ambient folder” is a working directory that contains:

  • Your raw materials (documents, notes, research)
  • Your infrastructure (templates, schemas, standards)
  • Your operations (scripts, workflows, integrations)
  • Your outputs (essays, reports, knowledge base entries)

The folder knows how to read its own contents, understand your standards, and call on AI capabilities to extend your work. By the end, you’ll have a system where asking for output is trivial—the folder does the heavy lifting.

We’ll build this in three stages:

Stage 1 (this piece): Initialize the folder and scaffold the infrastructure Stage 2 (this piece): Set up context retrieval and basic operations Stage 3 (next piece): Add validation, composition, and publishing

Let’s begin.

Stage 1: The folder structure

Start with a blank folder. You’re building a writing/research practice. You’ll eventually publish essays and maintain a knowledge base. For now, you just need the skeleton.

my-ambient-folder/
├── source/              # raw materials (documents, notes, research)
│   └── .gitkeep
├── drafts/              # works in progress
│   └── .gitkeep
├── output/              # finished work ready to publish
│   └── .gitkeep
├── knowledge-base/      # permanent knowledge entries
│   └── .gitkeep
├── templates/           # essay template, concept template, etc.
├── schemas/             # data structure definitions
├── scripts/             # automation scripts
├── config.yml           # folder-level configuration
└── README.md            # folder documentation

This is the skeleton. Every folder is different, but the principles are the same:

  • source/: your raw material (research, notes, PDFs, whatever you work with)
  • drafts/: intermediate outputs while things are being shaped
  • output/: finished work ready to move to the next stage (publishing, knowledge base, etc.)
  • infrastructure: templates, schemas, scripts, config

This structure reflects the workflow: source → draft → output. The ambient layer will orchestrate work flowing through these stages.

Stage 2: Scaffold the infrastructure

Now you need to define what “right” looks like for your folder. This is where you encode your standards.

2.1 Essay template

Create templates/essay.md:

 
[Body content here]
 
title: ""
description: ""
kind: concept
status: draft
tags: []
created: 2026-01-01
updated: 2026-01-01

Graph View