Skip to content

Managing a Kelp Strain Catalogue: Genetics Records for the Hatchery

How to build and run a kelp strain catalogue: naming, provenance records, gametophyte lineage tracking, outcrossing rotation, and audit-ready hatchery documentation.

Dr. Elias BrandtRestoration Geneticist11 min read
On this page

Every kelp hatchery accumulates a genetic library whether it means to or not: a shelf of culture tubes, a freezer box of cryopreserved gametophytes, a rack of flasks labelled in marker pen. The difference between a collection and a catalogue is paperwork — full reproductive histories of every lineage, written down in a way that survives staff turnover, audits, breeding decisions in year five, and worst of all, your own memory. At Tidewright's Holdfast nurseries, the strain catalogue is the single document a restoration director reaches for first when we ask "which seed belongs on this reef?" This guide explains how to build one that answers that question confidently.

Why the catalogue matters more than the cultures

A hatchery's worst quiet failure is genetic drift through neglect: a strain line repeatedly back-crossed with itself, mislabeled flasks, lost provenance, two strains silently merged after a contamination event. By the time anyone notices — a farm complaining that "this year's seed" underperforms — the genealogy that could diagnose it is gone.

A working catalogue prevents three catastrophes:

  1. Inbreeding collapse. Kelp gametophytes can be clonally propagated separately as male and female lines for years. Cross the same two lines too many generations and homozygosity erodes the exact traits — stress tolerance, growth variance — you farmed them for. Documented pedigrees let you see the inbreeding coefficient before you see the symptom.
  2. Provenance violations. Regulators and ethical buyers increasingly require seedstock provenance: where did the parents come from, and does the strain belong in this water? See Native Seedstock Rules for why getting this wrong is both an ecological and a licensing failure.
  3. Audit death. Certification programs, restoration funders, and carbon-credit verifiers all ask for seed documentation. A catalogue audit-ready by construction saves a week-long archaeological dig through fridge labels.

Naming: the boring decision that saves you later

Adopt a naming schema before lineage number one, and never improvise. A robust scheme encodes species, region, collection event, and generation. Tidewright's convention (adapted freely — ours is fictional, the logic is real):

<SPECIES>-<REGION>-<SITE>-<YEAR>-<FAMILY>-<SEX>-<ISOLATE>

For example: SLAT-ATLN-BJ07-2024-F12-F-03 reads as sugar kelp, Atlantic North region, collection site BJ07, wild parents collected 2024, family 12 from that collection, female gametophyte, isolate 03. Six fields, each answered from the collection sheet alone, and any flask can be decoded by a new technician with no oral history.

Rules that keep it working:

  • Every physical object carries the full code plus a human alias ("Bjørnøya 12 female"). Aliases are for bench conversation; codes are for the record.
  • Never re-use a code, even after a line is retired. Retired lines are marked inactive in the catalogue, not erased.
  • Every code exists in one system of record — one database or, honestly, one disciplined spreadsheet — and labels point to it.

Provenance: what to record at collection

The provenance record is born on the boat, not in the culture room. For each wild collection that founds a family, record:

  • Where: site name, coordinates, depth, substrate, exposure. This later drives site-matching for restoration outplanting.
  • When and how: date, which life stage (fertile sporophylls/sorus tissue), how many distinct parent blades contributed, and the collector.
  • Site condition: water temperature at collection, recent heat history if known, canopy condition. A strain collected from a reef that survived a heatwave is a different thing from one collected at a healthy baseline — that context becomes valuable in climate-resilient seedstock breeding.
  • Permit reference: the collection licence under which tissue was taken. Always.

The number of parents per founding family matters genetically. Crossing tissue from a single blade produces a family of half- and full-siblings; founding families from fewer than five parent blades sets a low genetic ceiling for everything downstream. Standard practice in our program: no founding family from a single sorus unless the point of the family is the sorus (e.g., a deliberate single-line archive).

Lineage tracking: the pedigree layer

Above provenance sits the reproductive ledger. Each culture entry, at minimum:

Field Captures
Strain code The object identity
Parent codes Male × female gametophyte codes for every cross that produced it
Cross date & batch When the cross was made and which production batch it fed
Generation depth Crosses since wild collection (F1, F2…)
Ploidy/sex Male, female, or sporophyte
Genome notes Any genotyping results — microsatellite or SNP panel — where performed
Status Active / banked / retired / culled, with date and reason

With those seven fields you can compute inbreeding coefficients, trace any farm complaint back to a mating pair, and answer a verifier's hardest question: show me the ancestors of the seed that went onto that reef. At Holdfast, lineage records feed directly into the delivery dossier that travels with every Holdfast seed batch — the genetic biography of the seed a reef receives.

Outcrossing rotation: breeding against the clock

Clonal gametophyte lines can live for years, but seed performance decays if each production year draws on the same pair. Rotation rules we recommend, informed by conservation-genetics practice:

  • Cycle the parents. Maintain several distinct male and female lines per strain-family; rotate mating pairs so no pair contributes more than roughly a third of consecutive production batches.
  • Refresh from the vault. Every few generations, cross production lines back to cryopreserved founders (or collect anew under permit). Cryopreservation protocols — the insurance this strategy depends on — are covered in Freezing Time: Cryopreserving Kelp Gametophytes.
  • Watch effective family size, not flask count. Ten flasks of one female line is one female. Genetic diversity lives in distinct lineages, not volume.
  • Cull deliberately. Retirement should mostly be a decision — documented, with reason — not an accident of contamination. A catalogue full of silently dead lines hides the health of the living ones.

For hatcheries doing directed improvement rather than maintenance breeding, the catalogue integrates with the selection pipeline described in Selective Breeding for Kelp; crossing decisions generate future catalogue entries, and the catalogue constrains crossing decisions. The two documents should be one.

Banking standards and the catalogue's quiet twin

The strain catalogue records meaning; the gametophyte bank records locations and conditions. Every banked line's entry should name its physical custody: room, rack transfer dates, cryo tank, cane, and viability-testing history. The twin discipline mirrors the standards in The Seed Vault of the Sea: triplicate custody (two in-house copies plus one at a partner institution), annual viability checks on a rotating sample, and a disaster plan no more than one step from the catalogue itself.

A catalogue line that says a strain exists but can't tell you which tank holds it in under a minute does not, in a flood or freezer failure, contain that strain at all.

Making the catalogue audit-ready

Auditors — certification bodies, grant funders, restoration verifiers — don't want your database. They want confidence that five-minute interrogation returns consistent answers. Practical habits:

  • One page per strain, printable. Code, provenance, pedigree thumbnail, custody, production history. If you can print it, you can defend it.
  • Change log. Who edited which field and when. A catalogue with silent edits will be torn apart by any competent reviewer; a change log converts editing from liability to evidence.
  • Quarterly reconciliation. Walk the culture room with a printout: every flask matches a catalogue entry, every entry has a flask (or a retirement record). We time this at about two hours per 200 lines — the cheapest quality assurance in the hatchery.
  • Link downstream. Production batches, farm deliveries and, at Tidewright, restoration outplanting events all reference strain codes — so the catalogue is the hub from farm complaint back to wild parents.

Our own catalogue underpins the genetic reporting in the impact methodology that Tidewright publishes alongside its (illustrative) restoration statistics — the chain from reef survey to strain code to outplanted seed is part of what makes a restoration claim auditable at all.

Software: start simple, design the schema first

A spreadsheet is a fine beginning for under a few hundred lines if the schema above is followed strictly: one row per strain, immutable IDs, controlled vocabulary for status fields, and a read-only change log sheet. At 500+ lines or multiple sites, move to a lightweight relational database or a lab information management system (LIMS) with a custom module; the schema in this article maps directly onto such systems. The tool matters far less than the rule that the catalogue is authoritative and the flasks are copies. When the two disagree, you have a contamination or labeling event — not a spreadsheet problem.

Key takeaways

  • A strain catalogue turns a culture collection into a managed asset: immutable codes, provenance, pedigrees, custody and status, all in one system of record.
  • Founding families need provenance born on the boat — coordinates, parent counts, permit reference — and should rarely trace to fewer than five parent blades.
  • Track male × female crosses, generation depth and genotyping so you can see inbreeding before it appears in farm performance.
  • Rotate mating pairs, refresh from the cryopreserved founders, and cull deliberately — genetic diversity lives in distinct lineages, not flask volume.
  • Pair every catalogue entry with a banked-custody record you can locate in under a minute, and reconcile the room against the catalogue quarterly.
  • Auditability is the point: one printable page per strain, a complete change log, and strain codes linked downstream to every farm delivery and outplanting.

FAQ

Do small hatcheries really need this much record-keeping?

A five-line hobby-scale hatchery needs the schema, not the software. Code every line, record provenance at collection, and log crosses. Genetics doesn't scale its patience to your operation size — a mislabeled flask breeds the same problems in a closet as in a campus.

How many gametophyte lines should we maintain per strain?

Enough that no single mating pair dominates production: commonly three to six male and three to six female lines per production strain-family, plus cryopreserved founders. Exact numbers depend on cross-compatibility and breeding goals; the catalogue is what tells you whether your rotation is actually achieving balance.

What's the minimum genotyping we should do?

None is required for basic provenance management — the lineage records carry you a long way. Genotyping (SNP or microsatellite panels) becomes worth its cost when you're doing directed selection, verifying lines after a suspected mix-up, or certifying strains for high-stakes restoration where identity guarantees are contracted.

How long can a gametophyte line be kept before refreshing?

Clonally perpetuated under clean, low-light, cool conditions, lines can persist years; cryopreserved, decades. The limiting factor is usually not lifespan but performance confidence: refresh production from refreshed or re-collected founders every few generations, and record each refresh as a catalogue event.

What happens if two strains are accidentally mixed?

Quarantine both sources, re-isolate, and genotype if identity matters. Then record it as an incident in the catalogue change log — mixed and honest beats clean and wrong. An audit that finds an incident log finds a functioning system; one that finds nothing amiss in ten years finds a fiction.