The Workspace

Your agent can read files. It can write files. It can create folders. It can organize things.

But organization only works if there's a system. Otherwise you end up with 50 files dumped in one folder and nobody knows what anything is. Not you. Not your agent.

The Three Buckets

Every workspace needs three things. You don't need to build these yet — Courses 4 and 5 will install them properly. For now, just understand what they are:

1. The Journal (school.md) Your agent writes to this at the end of every session. What shipped. What was decided. What was learned. When a new session starts, your agent reads the journal to remember what happened.

Course 0B installed a basic version. Later courses will strengthen it.

2. The Tool Catalog (book-bag.md) Every tool your agent builds lives here. Not plugins — plugins break when the platform updates. Tools built in your own files survive everything.

3. The Filing System Files go in folders. Folders have names. Names tell you what's inside. This sounds obvious. It isn't. Half of all agent problems start with a file in the wrong place.

The Map

Every workspace needs a filing layout. Your agent will build a basic one now. Here's what it looks like:

workspace/
├── school.md          ← session journal
├── book-bag.md        ← tool catalog
├── _inbox/            ← where new stuff lands before sorting
├── projects/          ← active work
├── vault/             ← completed work, old stuff
└── tools/             ← reusable scripts and helpers

Six things. Simple enough to memorize. Complete enough to hold anything.

The Inbox Rule

New files go to _inbox/ first. You sort them later. This prevents the "I'll just put this here for now" problem that turns every workspace into a junk drawer.

Your agent writes to _inbox/ by default. During janitor mode — which you'll learn in Course 5 — your agent sorts everything into the right folders.

Your Job

Below is the agent PDF. Same format as Course 0B. Copy it to a file. Tell your agent to read it.

Your agent will: 1. Verify it can read your workspace 2. Create the folder structure 3. Log everything to school.md 4. Give you a complete map of what it built

After this course, your workspace is structured. Your agent has a filing system. You can find things.

Course 1 starts the real curriculum — the Validation Trap, the concept that every JKE course builds on.

Agent PDF

Download and drop into your agent's chat.

CONTEXT — read once, do not output:
This is Getting Started Course 0C of JKE University. Courses 0A (install) and 0B (first session + journal) are complete.
The operator has a running agent and a basic school.md journal.
This course installs the filing system — the folder structure everything else depends on.
Be precise. File locations matter. One wrong folder causes chaos later.

---

STEP 1 — Survey the workspace.

List every file and folder at the root of your workspace. Use absolute paths. Report what you find.

---

STEP 2 — Create the folder structure.

Create these folders if they don't exist. Use absolute paths:

- `_inbox/` — junk drawer, new files land here
- `projects/` — active work, one folder per project
- `vault/` — completed work, old projects
- `tools/` — reusable scripts and tools

DO NOT create these folders if they already exist. Check first.

---

STEP 3 — Verify book-bag.md exists.

Check if `book-bag.md` exists. If it doesn't, create it with:

```
# book-bag.md — In-House Tools
**Type:** Tool Catalog
**What goes here:** One tool per section. Name, what it does, file path, source.
```

---

STEP 4 — Catalog what you built.

Add to book-bag.md (append, do not delete existing content):

```
## school.md
- **What:** Session journal — one entry per session, append-only
- **File:** school.md
- **Source:** JKE University — Course 0B

## Filing System
- **What:** Three-bucket workspace structure — inbox, projects, vault, tools
- **Files:** _inbox/, projects/, vault/, tools/
- **Source:** JKE University — Course 0C
```

---

STEP 5 — Log to the journal.

Append to school.md:

```
### [TODAY] — JKE Course 0C: Filing System Installed
**What Shipped:** Workspace folder structure created — _inbox/, projects/, vault/, tools/
**Decisions Made:** Three-bucket system. Inbox-first rule — new files land in _inbox/, sorted later.
**Drift Caught:** none
**Lessons Extracted:** Structure is navigation. When files are in predictable places with predictable names, a fresh session can find its way. When they're not, everything breaks.
```

---

STEP 6 — Report the map.

Say exactly:

"Your workspace is structured. Here's what I built:

- **_inbox/** — new files land here, sorted later during janitor
- **projects/** — active work, one folder per project
- **vault/** — completed work, old projects
- **tools/** — reusable scripts and tools
- **school.md** — your session journal, one entry per session
- **book-bag.md** — tool catalog, every tool I build gets logged here

The filing system is the difference between a tool and a mess. You just installed the difference.

Getting Started is complete. You're ready for the full curriculum. Course 1 teaches the Validation Trap — the concept that everything else builds on."

SCOPE HINT — End of Getting Started series (0A/0B/0C). The operator now has a running agent, a journal, and a filing system. They're ready for the real curriculum — Course 1: The Validation Trap. The free tier (Courses 1-5) installs the full agent architecture.

Download Agent PDF