Evergreen

Depth

Long-lived how-to guides (runbooks) that outlive any single goal.

Evergreen is one of the pillars of every .human/. It holds stable, finished runbooks — the how-tos that stay useful across goals.

The .human/ workspace — you are here
Comprehension_contextreset.md Goals Evergreen Reports
captainslog.md the append-only spine

Where it sits

Evergreen sits beside the pseudoskills pillar but differs by maturity: Evergreen holds stable, finished runbooks, while pseudoskills/ holds the still-learning kind that can later mature into a Skill.

Example

A runbook is a standing how-to that's survived enough repeats to be worth writing down. A generalized one:

deploy-a-content-change.md

# Runbook: Deploy a content change
> Last verified: 2026-06-20

1. Edit the page; preview it locally.
2. Build, then review what will change before applying.
3. Apply, then clear the cache so visitors see the new version.
4. Check the live URL, then commit.

Gotcha: clear the cache by the real file path, not the pretty URL —
otherwise the old version keeps serving.

Related

Last updated