External Merge: combining two SOs with no prior containment relation.
This is the "first Merge" case: α and β come from the lexical array and have never been in a structural relation before.
Traditional view: This builds structure "from scratch".
- α : SyntacticObject
First input
- β : SyntacticObject
Second input
- result : SyntacticObject
The result of merging
Inputs must be distinct
THE KEY PRECONDITION: No prior containment relation
The result is formed by merge
Instances For
Internal Merge: re-merging an SO already contained in the structure.
This is movement: the mover is extracted from within the target and re-merged at a higher position.
Traditional view: This creates displacement/copies.
- target : SyntacticObject
The structure containing the mover
- mover : SyntacticObject
The element that moves (already in target)
- result : SyntacticObject
The result of merging
Inputs must be distinct
THE KEY PRECONDITION: Mover is already contained in target
The result is formed by merge (mover goes to specifier position)
Instances For
THEOREM 1 (Same Operation):
Both External and Internal Merge use the same underlying merge function.
The operation itself is identical - only the preconditions differ.
A general Merge operation that abstracts over both types
- left : SyntacticObject
First input (the one that ends up on the left)
- right : SyntacticObject
Second input (the one that ends up on the right)
- result : SyntacticObject
The result
Inputs must be distinct
Result is merge of inputs
Instances For
External Merge is a special case of General Merge
Equations
Instances For
Internal Merge is a special case of General Merge
Equations
Instances For
THEOREM 2 (Exhaustivity): Every General Merge is either External or Internal (no third kind).
The containment precondition is the ONLY distinguishing feature.
When α selects β, the label of {α, β} equals the label of α
When β selects α (and α doesn't select β), the label of {α, β} equals the label of β
Mutual selection with distinct labels breaks labeling symmetry.
This is the key theorem: if both α and β select each other, and they have different labels, then label (merge α β) ≠ label (merge β α). This violates the set-theoretic nature of Merge, where {α,β} = {β,α}.
No mutual selection (with some selection) preserves labeling symmetry.
When at least one element selects the other, but not mutually, labeling is symmetric: label (merge α β) = label (merge β α).
MAIN THEOREM: Labeling symmetry characterization.
When at least one element selects the other, labeling is symmetric if and only if there's no mutual selection OR the labels are equal.
This shows NoMutualSelection is NECESSARY (not just empirically observed) for labeling to be well-defined on unordered sets {α, β}.
No mutual selection: at most one of α, β can select the other.
Within the Minimalist formalism, this is algebraically required:
labeling_symmetric_iff shows that without it (and with distinct labels),
label (merge α β) ≠ label (merge β α), violating the set-theoretic
nature of Merge where {α, β} = {β, α}.
Equations
- Minimalism.NoMutualSelection α β = ¬(Minimalism.selects α β ∧ Minimalism.selects β α)
Instances For
When α selects β, α and {α,β} have the same label
Helper: label of a leaf is always some
Helper lemma: label of a leaf is never none
Corollary: if label α ≠ none, then label returns some LI
For any SO, label never returns none. This follows from the structure: every SO contains a leaf, and label always finds it.
Corollary: getProjectingLI returning some implies label is not none
If α selects β, then α has a label (not none).
When β selects α and α doesn't select β, β and {α,β} have the same label
THEOREM 3 (Labeling Uniformity): The labeling algorithm works identically for External and Internal Merge.
What projects depends on selectional relations, not on whether the merge was external or internal.
COROLLARY: Selection determines projection, not merge type
Property 1 for External Merge: Operation doesn't depend on element nature
Property 1 for Internal Merge: Operation doesn't depend on element nature
Property 2 for External Merge: Labeling depends on selection
Property 2 for Internal Merge: Labeling depends on selection
Property 3 for External Merge: Either element can project.
Requires NoMutualSelection: selection on categories must be acyclic,
so at most one of α, β can select the other.
Property 3 for Internal Merge: Either element can project.
Requires NoMutualSelection: selection on categories must be acyclic.
THEOREM (Harizanov Unification): Both merge types satisfy all three properties.
Property 3 requires NoMutualSelection (acyclicity of selection on categories).
THEOREM 4 (Movement Uniformity): "The properties of movement do not depend on the nature of the moving element"
Whether the mover is a head or a phrase, Internal Merge works the same way. The mover always ends up in the left daughter position of the result.
The mover is always the left daughter after Internal Merge
The target is always the right daughter after Internal Merge
THEOREM 5 (Mover Can Project): "A moved element can project after movement"
This is non-trivial: traditionally, only the target was thought to project. But if the mover has unvalued selectional features that can be satisfied by the target, the mover can project (= head-to-head movement).
Target can also project (standard case).
Requires NoMutualSelection: selection on categories must be acyclic.
The dichotomy: either mover or target projects (one must).
Requires NoMutualSelection: selection on categories must be acyclic.
MAIN THEOREM (Merge Unification): Internal and External Merge are the same operation under different preconditions.
Formally: there exists a single function merge such that both EM and IM
are instances of applying this function, differing only in whether the
containment precondition holds.
Head movement is just Internal Merge where the mover is a head
Equations
Instances For
Phrasal movement is Internal Merge where the mover is a phrase
Equations
Instances For
THEOREM: Head and phrasal movement use the same Internal Merge
The difference is in what projects, not in the operation.
Requires NoMutualSelection: selection on categories must be acyclic.
Containment is a strict partial order: irreflexive, asymmetric, transitive. This is an algebraic property of tree structure, not a stipulation.
- asymm (x y : α) : R x y → ¬R y x
- trans (x y z : α) : R x y → R y z → R x z
Instances For
No element contains itself (well-foundedness of trees)
Containment on syntactic objects forms a strict partial order
TRICHOTOMY THEOREM (Order Theory): For any strict partial order, element pairs fall into exactly one of three cases. This is algebraic - it follows from the definition of strict partial order.
The trichotomy cases are mutually exclusive
COROLLARY: Internal/External partition follows from trichotomy.
Grouping "R x y" and "R y x" gives COMPARABLE (Internal Merge). The third case is INCOMPARABLE (External Merge).
This is why the partition isn't a "choice" - it's forced by order theory.
The "choices" Collins & Stabler mention are about ACCESSIBILITY, not partition.
Different workspace conditions determine which pairs are ACCESSIBLE for Merge:
- "A ∈ W ∧ B ∈ W" → only incomparable pairs accessible (External only)
- "A ∈ W ∧ (A contains B ∨ B ∈ W)" → standard (External + Internal)
- "A ∈ W ∧ B contained in W" → adds sideward merge
But the PARTITION of pairs into comparable/incomparable is algebraic. The "choice" is which partition cells are accessible, not the partition itself.
Accessibility conditions as predicates on (workspace, element, element) triples
Equations
Instances For
External-only: both must be roots
Equations
- Minimalism.externalOnly W A B = (A ∈ W ∧ B ∈ W)
Instances For
Standard (Chomsky): A is root, B is either in A or a root
Equations
- Minimalism.standardAccess W A B = (A ∈ W ∧ (Minimalism.contains A B ∨ B ∈ W))
Instances For
Sideward: A is root, B is anywhere in W
Equations
- Minimalism.sidewardAccess W A B = (A ∈ W ∧ ∃ (C : Minimalism.SyntacticObject), C ∈ W ∧ Minimalism.containsOrEq C B)
Instances For
Full: both anywhere in W
Equations
- Minimalism.fullAccess W A B = ((∃ (C : Minimalism.SyntacticObject), C ∈ W ∧ Minimalism.containsOrEq C A) ∧ ∃ (D : Minimalism.SyntacticObject), D ∈ W ∧ Minimalism.containsOrEq D B)
Instances For
One condition is more permissive than another
Equations
- Minimalism.morePermissive c1 c2 = ∀ (W : Set Minimalism.SyntacticObject) (A B : Minimalism.SyntacticObject), c2 W A B → c1 W A B
Instances For
The conditions form a chain: external ⊂ standard ⊂ sideward ⊂ full
THEOREM (Minimality of Chomsky's Choice): Standard access is the MINIMAL extension of external-only that allows Internal Merge.
"Minimal" means: any condition that allows Internal Merge and is at most as permissive as standard must equal standard on Internal cases.
The pure Internal Merge condition (without External)
Equations
- Minimalism.internalOnly W A B = (A ∈ W ∧ Minimalism.contains A B)
Instances For
THEOREM (Join Characterization): Standard access is exactly the join of External and Internal conditions. This is why Chomsky's choice is canonical - it's a lattice-theoretic join.
Standard is the LEAST condition containing both External and Internal
Containment implies distinctness (uses contains_irrefl from Containment.lean)
Convert a Movement to an InternalMerge
Equations
Instances For
HeadToSpecMovement is an instance of InternalMerge
Equations
Instances For
HeadToHeadMovement is an instance of InternalMerge
Equations
Instances For
THEOREM (Head Movement Unification): Both head movement types are instances of the same InternalMerge operation.
This completes Harizanov's unification: head-to-spec and head-to-head are not different operations, but the same InternalMerge with different labeling outcomes.
The difference between head-to-spec and head-to-head is purely in labeling
MAIN THEOREM (Complete Harizanov Unification):
- External Merge and Internal Merge are the same operation (differ only in precondition)
- Head movement and phrasal movement are both Internal Merge
- Head-to-spec and head-to-head are both Internal Merge (differ only in labeling)
- All three Harizanov properties hold for both External and Internal Merge
The only true distinctions are:
- Containment precondition (External vs Internal)
- Which element projects (determined by selection, not by operation type)