SEAD Exports¶
SEAD exports are the public environmental-archaeology context surfaces derived from SEAD. They help the product explain broader archaeology setting without confusing that setting with direct sample-backed evidence.
They matter because people often need archaeology context that is broader than one country and broader than one excavation-like reading. SEAD helps the repository show the kind of wider human landscape that surrounds a geography without pretending that context and direct evidence are the same thing.
What SEAD Makes Clear¶
- what wider archaeology context surrounds a visible geography
- whether a public interpretation is grounded only in pollen and ancient DNA or also in broader archaeology context
- how to think about archaeology patterns outside the narrowest country frame
- why a public region can be interesting even when direct sample density is not yet strong everywhere
What SEAD Adds To The Public Product¶
SEAD makes the public product more useful by adding:
- broader environmental archaeology framing
- cross-regional context that keeps interpretation from collapsing into one evidence family
- a way to compare archaeological background across visible geographies
What It Does Not Do¶
SEAD exports are contextual publications. They should not be read as if they:
- prove one specific site-level or sample-level claim on their own
- replace chronology, locality, or coordinate review for sample-backed rows
- make a thin ancient DNA surface strong simply by surrounding it with richer archaeology context
How These Exports Broaden The Question¶
When SEAD is visible, you can ask a better question than "is there one sample here?" You can also ask "what kind of surrounding archaeology context does this place sit inside?"
If You Need The Repository-Owned Records¶
The normalized family outputs live under:
data/sead/normalized/
If your question is about the visible publication, continue to maps or reports. If your question is about the family itself, continue to SEAD source guidance.