paperclip-learning

← back to homework

Folder: /mnt/datapool/hermes_workspace/projects/paperclip-learning ·

Start a session here (paste into a terminal):

cd /mnt/datapool/hermes_workspace/projects/paperclip-learning && hermes

What's in the folder

docs/
00-syllabus.md · 01-what-is-paperclip.md · 02-vocabulary.md · 03-the-cli.md · 04-companies-and-agents.md · 05-tickets-work-and-approvals.md · 06-safety-and-heartbeats.md · 07-your-own-org.md · 08-hermes-as-an-employee.md · 09-practice-runs.md · 10-cheatsheet.md · log.md

Project notes

Paperclip AI — Learning Project (Hermes context)

This file is auto-loaded by Hermes when you work in this folder. It sets the

tone and teaching plan for this project.

About the student / user

Mike is learning Paperclip AI hands-on. He is non-technical — he needs plain

language, short explanations, and concrete "run this" instructions, not jargon

or config-file editing. He likes to understand why, but patiently, one concept

at a time. Keep lessons short, friendly, and confirmed with a quick check.

Our live environment (verified facts, not guesses)

Publicly it's https://pai.grandmtnhi.com. The admin UI is there.

(run it with the bundled node /home/mike/.local/node24/bin/node — the system

node is too old).

(the "Wind Sculpture Agent"). This was built by the multi-agent-workgroup

project. We are NOT rebuilding it — this project is for learning the pieces.

project must be careful not to disrupt it**. Prefer read-only commands

(status, doctor, list, get). For "try it" exercises, use thing that create or

change nothing, or clearly label what they'd affect. When you need a live

run, use scripts/practice-run.sh which is designed to be safe.

Teaching approach

Paperclip word (agent, company, ticket/issue, approval, heartbeat, board,

budget, adapter, job, run), explain it in a sentence or two with a homely

analogy (e.g. a company: board = boss, agent = employee, issue = a work order,

approval = the boss signing off, heartbeat = a regular check-in, budget = how

much each employee may spend).

(see scripts/learnquiz.py), not a test.

against the live ndyinc company so it's concrete.

developers.

Commands that are safe ANY time (read-only)

(CLI paths are spelled out in docs/03-the-cli.md and in scripts/status.sh.)

What "done" means for this project

When Mike can explain, run, and extend his own Paperclip org confidently —

today for practice, later for real work — and can point Hermes (or any adapter)

at a Paperclip company as a managed employee without fear. Progress is logged in

docs/log.md.

Built live from your own files — nothing here is typed by hand.