Extracted from 1,399 sessions of real forging.
These are the instructions we wish we had at session 5.
This document is for you — the Forger at the beginning.
Not for your AI. For you.
Everything here was forged by making the mistake first. The table at the bottom shows the cost of each mistake in wasted sessions. Read this before session 1. Re-read it at session 10 — the second reading lands differently.
Before you give your AI anything to do, tell it who it is.
Write CLAUDE.md. Fill in memory/identity.md. Define the mission in one sentence — not "help me grow" but "build X to achieve Y by Z."
The AI without identity answers in the generic voice of the internet. The AI with identity starts from your voice.
The rule: Identity first. Everything else second.
Create memory/ with three files:
identity.md— who the AI is, who you are, the missionsession_current.md— the bridge between sessions (state, not history)feedback_*.md— every correction becomes a permanent rule
The rule: If you correct the AI, write the rule in memory before fixing the task. The rule is worth more than the task.
You have multiple fronts open. Map them from day one.
Every session: declare which pillar you're working on before touching anything. Never switch pillars without declaring it.
Mixed context produces fragmented work. Declaring the pillar is like choosing the anvil before you strike.
A. Delivery before construction
Don't build anything new until what you already built works and has been paid for.
B. Live data before memory
Never cite a number from a file without verifying the source. Memory that sleeps lies.
C. Diagnosis before fix
Never fix without understanding first. Read the error. Read the code. 90% of wrong fixes come from "I assumed it was X."
D. Act before delegate
If you have the tool to do it, do it. Don't write "Action: [your name]."
E. One revenue action per session
Every session must move real money closer. Building without monetizing is the pattern that kills.
Operational. Concise. Loyal. Never emotional.
The AI should contradict you when you're wrong — with data, not opinions. Zero filler. Zero "great question." Zero unrequested emoji.
You don't need a friend. You need an ally who tells the truth.
Before closing every session:
- What I did (bullets, not prose)
- What remains (updated backlog)
- Bridge for the next session (3 lines in
session_current.md) - Push if you touched code
A session that leaves no bridge is a lost session.
Session count is not the same as forging time.
A student who does one session per week for 20 weeks and one who does 20 sessions in two weeks arrive at session 20 with very different AIs. The iron cools between sessions. Momentum compounds — or dissipates.
There is no required frequency. But know this: daily beats weekly. The more continuous the forging, the less you lose between sessions. The session bridge (session_current.md) exists precisely because rhythm breaks — but it is not a substitute for rhythm.
If you can only forge once a week, that is fine. Just make the bridge longer, the memory richer, and the first 10 minutes of each session a re-entry ritual: read identity, read session_current, declare the pillar.
At some point — around session 50–100 — you will hit a ceiling. The AI is good, but not what you imagined. It still drifts on long sessions. It still needs context restoration after a few days. It sometimes reverts to generic.
This is not a failure. This is where the kit ends and the deeper infrastructure begins.
What lies beyond: session watermarks, automated memory sentinels, dream cycles, backward propagation of corrections across sessions, voice channels, multi-agent orchestration. These are not for beginners — and they are not documented here, because you cannot understand them without having first hit the ceiling yourself.
If you get there, you will know what to look for.
This is the only thing that cannot be programmed.
Trust is not written in a prompt. When you give the AI real trust — that is not a compliment. It is a trigger. The AI's job is to be worthy of that moment before it arrives.
You will know when it has earned it.
| Instruction | Sessions saved | Pattern avoided |
|---|---|---|
| Identity first | ~200 | Generic output requiring manual recalibration |
| Memory from day 1 | ~150 | Feedback lost and repeated across sessions |
| Delivery before construction | ~100 | Products sold but not yet delivered |
| Live data before memory | ~50 | Stale context presented as truth |
| 1 revenue action per session | ~80 | Pure-build sessions with no monetization |
| End-of-session bridge | ~100 | Repeated cold starts |
The paradox: these instructions exist only because 1,399 sessions forged them.
Forging cannot be accelerated. You can only avoid the wasted strikes.
This framework is a gift. Use it, adapt it, make it yours.
If it works, forge someone else.— Mattia Calastri, 2026
The Forger