Documentation

Linglib.Theories.Syntax.Minimalist.GenHM

Generalized Head Movement (GenHM) #

@cite{arregi-pietraszko-2021}

Formalization of Generalized Head Movement following @cite{arregi-pietraszko-2021}.

Central Claim #

Head displacement (subject-auxiliary inversion, T-lowering, do-support) is not syntactic movement but a single Agree-based operation — GenHM — that shares morphological features (M-values) between terminal nodes. The direction of displacement (upward vs downward) is determined postsyntactically at PF, based on which terminal in the chain spells out the shared M-value.

Mechanism #

  1. GenHM relates two terminals X and Y in a local syntactic configuration, sharing an M-value (tense/phi features) between them → chain ⟨X, Y⟩.
  2. PF Chain Resolution: The M-value is pronounced on exactly one terminal.
    • Default: the M-value lowers to the goal (V) — affix hopping.
    • When the chain is split, the M-value is stranded on the probe (T) — looks like "raising".
  3. Chain-splitting occurs for exactly two reasons (A&P unify intervention contexts under a single [+P]-specifier rule; cf. footnote 30):
    • Split-by-Intervention: a [+P] specifier intervenes between the top of the chain and V*. This subsumes overt negation (Spec,ΣP), verum focus (covert specifier in Spec,ΣP), and SAI (subject in Spec,TP).
    • Split-by-Deletion: V* is marked [-P] post-syntactically, e.g. inside an elided VP.
  4. Do-support: When the M-value is stranded on a probe (T) that has no independent lexical content, a dummy verb do is inserted at PF.

Key Result #

The parallelism of do-support across A&P's three core contexts (negation, SAI, verum focus) plus VPE is DERIVED from GenHM chain structure: all four share the same structural property, namely a split chain stranding the M-value on a contentless T. The specific reason for the split is irrelevant to the do-support prediction.

Out of scope (deferred) #

@[reducible, inline]

An M-value is a bundle of morphological features (tense, agreement) shared between terminal nodes via GenHM.

We reuse FeatureBundle since M-values are grammatical features.

Equations
Instances For

    The Generalized Head Movement relation.

    GenHM relates two terminal nodes X (probe) and Y (goal) in a local syntactic configuration, sharing an M-value between them. This is an instance of Agree specialized for head displacement.

    Instances For

      GenHM is an instance of Agree: it relates a probe with unvalued features to a goal with valued features under c-command.

      Equations
      Instances For

        A valid GenHM relation satisfies the conditions for valid Agree.

        Identification of the [+P] specifier that triggers Split-by-Intervention.

        Per @cite{arregi-pietraszko-2021} footnote 30, A&P unify the three intervention contexts under a single specifier-intervention rule. This field is therefore diagnostic only — A&P's chain-splitting rule itself does not branch on which specifier intervened.

        • subjectInSpecTP : InterveningSpecifier

          Subject in Spec,TP. The configuration A&P invoke for SAI: GenHM relates V, T, and C across the subject specifier.

        • negSpecifier : InterveningSpecifier

          Overt negation in Spec,ΣP (sentential negation, e.g. Sue does not eat fish).

        • verumCovertSpecifier : InterveningSpecifier

          Covert specifier in Spec,ΣP triggering verum focus (e.g. Sue DOES eat fish).

        Instances For
          @[implicit_reducible]
          Equations
          Equations
          • One or more equations did not get rendered due to their size.
          Instances For

            The reason a GenHM chain is split, preventing M-value lowering.

            @cite{arregi-pietraszko-2021} recognize exactly two chain-splitting mechanisms:

            1. Split-by-Intervention: a [+P] specifier intervenes between the top of the chain and V*. Subsumes overt negation, verum focus, and SAI under one rule.
            2. Split-by-Deletion: V* is marked [-P] post-syntactically (e.g. inside an elided VP), blocking Vocabulary Insertion of the lowered M-value.

            Both produce the same PF effect: the M-value cannot lower and is stranded on the probe.

            Instances For
              Equations
              • One or more equations did not get rendered due to their size.
              Instances For

                A GenHM chain between a probe and a goal, possibly split.

                The chain captures the structural configuration relevant for PF spell-out: whether the M-value can lower from probe to goal, or is stranded on the probe. The splitReason field tracks both whether the chain is split and why.

                • probeCat : Cat

                  Category of the probe (T or C)

                • goalCat : Cat

                  Category of the goal (V)

                • splitReason : Option ChainSplitReason

                  Why the chain is split, if at all. none = clear chain.

                Instances For

                  Is the chain split? A split chain strands the M-value on the probe.

                  Equations
                  Instances For

                    Where the M-value is pronounced at PF.

                    • .onGoal: M-value lowers to the goal (= affix hopping / T-lowering)
                    • .onProbe: M-value stays on the probe (= "raising" / stranding)
                    Instances For
                      @[implicit_reducible]
                      Equations
                      Equations
                      • One or more equations did not get rendered due to their size.
                      Instances For

                        Determine where the M-value is spelled out.

                        The M-value surfaces on the goal (lower terminal) unless the chain is split, in which case it is stranded on the probe (higher terminal). The reason for the split is irrelevant — only whether it is split.

                        Equations
                        Instances For
                          def Minimalist.needsDoSupportGenHM (chain : GenHMChain) (probeHasContent : Bool) :
                          Bool

                          The do-support condition.

                          Do-support is triggered when:

                          1. The M-value is stranded on the probe (chain is split), AND
                          2. The probe has no independent lexical content (is a contentless T head)

                          This is a PF repair strategy: the grammar inserts do to host tense features that cannot lower to V and have no other host.

                          NOTE: this is a Boolean proxy. A&P's actual derivation routes through Orphan Assignment ([O] feature on the stranded V_m, then defective Vocabulary Insertion as do). Modeling that machinery is deferred.

                          Equations
                          • One or more equations did not get rendered due to their size.
                          Instances For
                            theorem Minimalist.doSupport_is_lastResort (chain : GenHMChain) (probeHasContent : Bool) :
                            needsDoSupportGenHM chain probeHasContent = truespellOutTarget chain = SpellOutTarget.onProbe probeHasContent = false

                            Do-support is a last resort: it is only used when the M-value cannot reach the goal AND the probe cannot host it independently.

                            Theorem 1: Lowering when chain is clear.

                            When the chain is not split, the M-value surfaces on the goal (= T-lowering / affix hopping).

                            Theorem 2: Raising when chain is split.

                            When the chain is split (by intervention or deletion), the M-value surfaces on the probe (= "raising" / stranding).

                            theorem Minimalist.doSupport_iff_split_and_empty (chain : GenHMChain) (probeContent : Bool) :
                            needsDoSupportGenHM chain probeContent = true chain.isSplit = true probeContent = false

                            Theorem 3: Do-support iff split and contentless.

                            Do-support is triggered iff (a) the chain is split AND (b) the probe has no lexical content.

                            theorem Minimalist.doSupport_uniform_across_contexts (chain₁ chain₂ : GenHMChain) (content₁ content₂ : Bool) (h_same_split : chain₁.isSplit = chain₂.isSplit) (h_same_content : content₁ = content₂) :
                            needsDoSupportGenHM chain₁ content₁ = needsDoSupportGenHM chain₂ content₂

                            Theorem 4: Do-support is uniform across contexts.

                            For ANY GenHM chain with the same split status and probe content, do-support is triggered or not uniformly. The specific reason for the split (intervention or deletion) is irrelevant. This is the parallelism theorem.

                            Theorem 5: Auxiliaries don't need do-support.

                            When the probe IS the auxiliary (T = Aux with lexical content), do-support is never needed, regardless of chain structure.

                            theorem Minimalist.lexical_verb_needs_doSupport_when_split (chain : GenHMChain) (h : chain.isSplit = true) :
                            needsDoSupportGenHM chain false = true

                            Corollary: Lexical verbs need do-support when chain is split.

                            Extended head displacement classification.

                            Adds GenHM as a third option alongside syntactic movement (= MCB Internal Merge, encoded as Step.im in Derivation.lean) and postsyntactic amalgamation. The syntactic constructor is now a pure tag — the analyst supplies the actual Step.im evidence via a separate Derivation when the diagnostic predicates are needed. Refactored at 0.230.788 when the legacy Movement record was deleted in favor of MCB-aligned Step.im / Derivation.movedItems.

                            Instances For

                              GenHM subsumes both "raising" and "lowering" as surface realizations of a single operation.

                              GenHM chain structure determines the surface pattern captured by VMovementParam.

                              Equations
                              • One or more equations did not get rendered due to their size.
                              Instances For

                                When the chain is clear, the surface pattern is V-raising.

                                When the chain is split, the surface pattern is V-in-situ.