Skip to content

Type site

An archaeological site selected as the defining reference for a named archaeological culture, assemblage or typological unit.

Version
v1 · 2026-09-08 · History
Domain-specific #
7300
Origin domain
archaeological classification
Subdomain
archaeological classification

Core Idea

A type site anchors comparison but need not be earliest, most typical or uniquely representative; later evidence can revise the unit while the historical name persists. A diagnostic assemblage and stratigraphic context at one site provide the reference pattern against which other sites are compared and assigned to or separated from the typological unit. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

Type site belongs to archaeological classification and is useful where the analyst can specify the typed archaeological classification carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the archaeological unit and naming history, reference site and context, diagnostic materials and features, chronology, comparison criteria, geographic scope, later revisions and evidential limits are explicit. The scope is broad within that domain but bounded by the need for the archaeological unit and naming history, reference site and context, diagnostic materials and features, chronology, comparison criteria, geographic scope, later revisions and evidential limits are explicit. Descriptive archaeological classification only; no excavation or artifact-handling procedure is provided.

Clarity

The abstraction clarifies a crowded vocabulary by making the archaeological unit and naming history, reference site and context, diagnostic materials and features, chronology, comparison criteria, geographic scope, later revisions and evidential limits are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Type site can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Type site. Type site compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed archaeological classification carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the archaeological unit and naming history, reference site and context, diagnostic materials and features, chronology, comparison criteria, geographic scope, later revisions and evidential limits are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of archaeological classification because they reuse the typed archaeological classification carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, A diagnostic assemblage and stratigraphic context at one site provide the reference pattern against which other sites are compared and assigned to or separated from the typological unit., and type the carrier, state every parameter and convention in the definition, test that the archaeological unit and naming history, reference site and context, diagnostic materials and features, chronology, comparison criteria, geographic scope, later revisions and evidential limits are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Type siteParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Type siteDOMAINPrime abstraction: Classification — is a kind ofClassificationPRIME

Current abstraction Type site Domain-specific

Parents (1) — more general patterns this builds on

  • Type site is a kind of Classification Prime

    The proposed strict upward parent is prime:classification.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Type site sits in a crowded region of the domain-specific corpus (33rd percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Exhibition, Heritage & Visual Design (12 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08