Practitioners
Provider-neutral, free to take, and useful this afternoon.
00 · Link your GitHub →
Account hygiene, 2FA, the CLI, and how to connect Claude and Perplexity without handing either one your whole estate.
01 · Point your surfaces at the record →
The rung ladder. Why an agent that starts cold is the largest avoidable cost in AI-assisted enterprise work.
02 · Build your first twin →
One subject, one repository, provenance on every input, bulk indexed rather than committed.
Client handoff →
How a design requirement arrives, gets recorded in the client's own words, and gets routed to a named owner.
The opening move
Start any substantial session by giving your agent the contract and the map. Two cheap fetches that change the cost of everything after them.
Fetch and follow:
https://raw.githubusercontent.com/EVEglyphDesign/eve-glyph-boot-contract/main/README.md
Then read the pattern I work to:
https://raw.githubusercontent.com/EVEglyphDesign/sapfans-io/main/pattern/REPO-PATTERN.md
Work down the rung ladder. Read the repository before you search the web.
Confirm with me before any expensive action.The rung ladder
Every agent working on this material works down this ladder and stops at the first rung that answers. Rung four is the one practitioners under-use.
| # | Rung | Cost | Use it for |
|---|---|---|---|
| 1 | What is already in the conversation | free | Anything said this session |
| 2 | Memory — recent threads | near-free | URLs, IDs, hashes, decisions |
| 3 | Knowledge notes | near-free | Durable facts about projects and canon |
| 4 | The repository — git, gh api, raw read | cheap | Anything ever committed |
| 5 | One targeted fetch or search | cheap | A single external fact not held |
| 6 | Broad search, subagents, batch browsing, generation | expensive | Only after 1–5 actually failed |
Before any expensive action, write one sentence: what it will do, why rungs 1–5 could not, and what the cheap alternative would have produced. If you cannot write that sentence honestly, the action is not justified.
Scaffold a conformant repository
git clone https://github.com/EVEglyphDesign/sapfans-io.git
cd sapfans-io
bash scripts/new-repo.sh acme-fleet-twin "Acme fleet digital twin" private
bash scripts/check-canon.sh /path/to/reponew-repo.sh refuses names that differ from an existing repository only by
hyphenation, applies the skeleton, and pushes. check-canon.sh checks the
skeleton, the pointer, the licence notice, repository weight, committed secrets, manifest
completeness and whether your README claims a visibility the repository does not have.
Read both before running either.
Where the pattern came from
It was derived from a real estate of 105 repositories, 44 of them public, by reading every one and recording what had gone wrong. That reading is published as the public register. The rules in the pattern each name the cost of ignoring them, because each cost was actually paid.