Grain to grain transfers: keeping generations straight

Grain to grain transfer is the best deal in cultivation. One colonized quart expands into eight to ten more, in days rather than weeks, with no agar work and no new syringes to buy. It is also the fastest way to end up with a shelf of identical jars and no idea which is a second generation off a strong isolate and which is a sixth generation off something that has been slowing down for a year.

The technique is simple. The bookkeeping is what separates growers who use grain to grain happily for years from growers who quietly abandon it after a bad season.

Decide what a generation means to you

Before labelling anything, fix a definition and never bend it. The one that causes the least confusion:

• G0 — the original: a supplier culture, a spore print isolate, a clone.
• G1 — the first grain you inoculated from that original, whether from agar or a syringe.
• G2 — grain inoculated from G1 grain. Every grain to grain step adds exactly one.

Two rules make this hold up. First, generation counts transfers of the living culture, not containers: splitting one G2 jar into eight bags makes eight G3s, not eight G2s. Second, going back to agar does not reset the count. A wedge cut from a G4 grain jar is still G4 material; agar cleans up contaminants, it does not rejuvenate genetics. If you want a low generation number again, you go back to a stored original, not to a plate.

How far can you go?

Practically, most growers see no measurable difference through about four grain to grain steps, then start noticing slower colonization, more sectoring on agar and lower yields somewhere past that. Oysters tolerate more transfers than most; some cultivated strains senesce noticeably earlier. Rather than trusting a rule of thumb, use your own records: if colonization days per jar are creeping up by generation, that is your ceiling, and it will be specific to your line and your conditions.

The safe habit is to treat grain to grain as expansion for production, and always inoculate from a stored low-generation backup when starting a new season or a new batch of blocks.

A labelling system that survives a busy month

Whatever you write on a jar has to be readable when it is dusty, damp, cold from the fridge, and you are holding two others. Keep it short and put the long version somewhere else.

Four things belong on the physical label:

1. Line code — a short abbreviation for the genetic line, e.g. BLU for a blue oyster isolate.
2. Generation — G3. No ambiguity, no "gen 3-ish".
3. Date inoculated — day and month is enough.
4. A unique ID or QR code — the thing that ties the jar to everything you did not write down.

So: BLU G3 · 14 Mar · #0417. Everything else — which jar it came from, which recipe the grain used, which pressure cooker load, who inoculated it — lives in your records, keyed on that ID. This is the part that scales. Handwriting parentage on a lid works until the day you transfer twelve jars in one session.

Always record the parent

A generation number tells you how deep you are. It does not tell you which branch you are on. If you have two G4 jars and one turns out to be spectacular, you need to know which G3 it came from to repeat it, and which G2 sits behind that.

So every new jar records exactly one parent ID. Done consistently, you get a tree you can walk backwards: this bag came from jar #0417, which came from #0388, which came from the syringe you bought in January. That chain is what lets you retire a bad branch without throwing out a whole line.

Keep backups, and know where they are

Grain to grain has no memory. Once you have expanded from your last jar, the line only exists in the jars in front of you, and jars get contaminated, dry out, or get used.

Two cheap habits prevent losing a line entirely:

• Make a slant or two at low generation. Agar slants in the fridge hold for months to a year. Make them from G1 or G2 material, label them with the same line code and generation, and record where they are stored.
• Keep a syringe in reserve. A liquid culture syringe from a known good jar, dated and labelled, is your fast path back into production.

Record the storage location as part of the culture record. "Fridge, door tray, small box" is enough, and it is the difference between a five minute recovery and an hour of turning out containers.

The transfer session itself

Nothing exotic, but the order matters, and the recording happens during, not after.

1. Pick the parent deliberately. Fully colonized, no off smell, no discoloured patches, and ideally the fastest jar of its batch rather than just the nearest one.
2. Break it up and let it rest. Shake or break the parent one to two days before transferring so the mycelium is active and the grain separates cleanly.
3. Label the destination jars first. Line code, generation, date, ID — written or printed before anything is opened. Labelling afterwards is where mistakes get made.
4. Work clean, work fast. Flow hood or still air box, ratio of roughly one part parent grain to eight or ten parts sterile grain. A heavier ratio colonizes faster and gives contaminants less time.
5. Record parentage as you go. Each new ID gets the parent ID. If you are scanning labels, this is a couple of taps per jar.
6. Note anything unusual immediately. A jar that felt too wet, a lid that did not seat. In four days, that note explains an outcome.

Watch two numbers by generation

You do not need analytics to run a healthy grain program, but two simple series tell you when a line is fading:

• Days to full colonization, averaged per generation. A steady upward drift is the earliest warning sign, and it shows up before yields drop.
• Yield per block, grouped by the generation of the spawn used. If G5 spawn consistently produces smaller first flushes than G2 spawn did on the same recipe, you have your answer.

When both are trending the wrong way, stop expanding that branch, pull a backup, and start a fresh chain from low generation material. Because you recorded parents, you can be precise about which branch to abandon instead of scrapping the whole line.

A short checklist

• One definition of generation, written down.
• Every jar labelled with line, generation, date and a unique ID before inoculation.
• Every jar records exactly one parent.
• Slants and syringes made at low generation, with storage locations recorded.
• Colonization days and yields reviewed by generation each season.

Our software handles the tedious half of this: cultures under a genetic line, one parent per culture, generation numbers that increment on transfer, backups tracked with their storage location, and QR labels that print with the line code and generation already on them. Scan the jar and the whole chain behind it is on screen.