Skip to content

SEAD Handbook

This page is the longer public explanation of why SEAD remains important in the repository even though it is not a direct ancient DNA source.

The short version is easy to say: SEAD adds environmental archaeology context. The harder and more useful version is this: SEAD helps readers judge whether a biological finding sits inside a broader cultural landscape that is already archaeologically visible.

Why A Longer Explanation Is Needed

Context families are easy to undervalue because they do not usually deliver the single dramatic object a reader notices first. They rarely produce the loudest point on the map. But they change interpretation in a quieter, more important way.

SEAD helps answer questions like:

  • does this place sit in a wider archaeology-rich setting?
  • are we reading one isolated biological point or one part of a broader human landscape?
  • what cultural background should be visible before we make too much of one sample?

Those are public-facing questions, not only maintainer questions.

What Good Use Of SEAD Looks Like

Good use of SEAD keeps it in the role it is actually strong at:

  • expanding archaeology context around places and regions
  • supporting interpretation across more than one local registry
  • helping readers read a map as landscape evidence rather than as isolated dots
  • helping Sweden lake triage stay honest by showing where a candidate basin sits inside stronger or weaker archaeology surroundings

Good use does not ask SEAD to act like sample-level proof. That would weaken the public product, not strengthen it.

When Readers Should Be Careful

Readers should slow down when a contextual layer starts to sound as decisive as the direct evidence it surrounds.

SEAD can strengthen an interpretation, but it does not by itself establish:

  • exact sample identity
  • exact sample chronology
  • exact sample coordinates
  • species assignment

Those claims still belong to narrower evidence files and review surfaces.

How SEAD Helps Sweden Lake Planning

The Sweden lake ranking does not use SEAD to pretend that one archaeology point proves one lake. It uses SEAD more carefully.

SEAD helps the repository ask:

  • which pollen basins sit in archaeology-rich surroundings
  • which top-ranked lakes remain strong even when archaeology context is part of the score
  • where a promising basin may deserve deeper upstream inspection before field planning goes further

That is a better use of SEAD than treating it as a direct lake register.

Why Collaboration Around SEAD Makes Sense

SEAD is managed as a research infrastructure at Umeå University and is closely aligned with the kind of cross-proxy environmental archaeology reasoning this repository already needs.

That makes collaboration useful for work such as:

  • clarifying Swedish lake-linked archaeology context where local interpretation is still thin
  • improving stable links from checked-in repository capture back to upstream SEAD references
  • checking whether repository-normalized context stays faithful to how SEAD structures proxy-rich archaeology records

Repository-Owned Review Surfaces

If you want the deeper tracked records behind this handbook, start with:

  • data/sead/review/access_model.json
  • data/sead/review/recovery_roadmap.json
  • data/sead/review/evidence_legibility_review.json
  • data/sead/review/temporal_review.json

These are useful if you need to understand how the repository checks that SEAD stays readable and responsibly used in public outputs.