Rolle 2018 — Grammatical tone: CoP-scope and Matrix-Basemap Correspondence #
[Rol18]'s thesis frames dominant vs. non-dominant grammatical tone (GT)
via three problems: the origin (where does the grammatical tune come from?),
the erasure (why do the target's underlying tones go unrealized?), and the
scope (what determines the domain of the GT operation?). This file
formalises Rolle's two central mechanisms; the origin problem is solved by the
floating-tone representation (the tune is part of the trigger's UR, in
Tone/Grammatical.lean).
- CoP-scope (Ch 6) — the scope problem. Structural positions in a cophonological domain are ordered Spec > Head > Complement, and at spell-out syntactic structure is mapped to a morpho-phonological tree via hierarchy exchange. The dominant-GT asymmetry (triggers are dependents, targets are heads) is derived from this ordering rather than stipulated.
- Matrix-Basemap Correspondence (MxBM-C) (Ch 5) — the erasure problem. Dominant GT is faithfulness to a basemap output (a "deficient projection" of the input with all valued tones stripped), extending Output-Output Correspondence ([Ben97]) to the tonal tier.
Main definitions #
CoP-scope #
CoPPosition,CoPPosition.rank,scopesOver,CoPPosition.isDependentCoPNode,hierarchyExchangedominant_gt_asymmetry_from_scope— derives the asymmetry from scope
Matrix-Basemap Correspondence #
deficientProjection,basemapOutput,tonalTierbasemapViolations— IDENT-OO ([McCP95]) on the tonal tier, derived fromCorr.identViolmkBasemapConstraint,tonalOverwrite_basemap_faithful
References #
CoP-scope: cophonological domain scope hierarchy #
CoP-scope positions #
Structural positions within a cophonological domain (CoP), ordered by scope. The ordering Spec > Head > Complement determines which VI's cophonology takes precedence within the domain.
[Rol18] Ch 6 §6.2: each VI has cophonology-scope over all inwardly located morphemes, and cophonologies apply cyclically up the tree, producing layered grammatical tone effects.
- spec : CoPPosition
Specifier: outermost scope. Dependents (modifiers, possessors) typically occupy this position.
- head : CoPPosition
Head: middle scope. Lexical heads (roots, stems) occupy this position.
- complement : CoPPosition
Complement: innermost scope. Complements and some affixes occupy this position.
Instances For
Equations
- Rolle2018.instDecidableEqCoPPosition x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- Rolle2018.instReprCoPPosition = { reprPrec := Rolle2018.instReprCoPPosition.repr }
Equations
- One or more equations did not get rendered due to their size.
Instances For
Scope ordering #
Numeric rank for scope ordering: higher rank = wider scope. Spec (2) > Head (1) > Complement (0).
Equations
Instances For
Does position a scope over position b?
Equations
- Rolle2018.scopesOver a b = decide (a.rank > b.rank)
Instances For
Specifiers scope over heads.
Heads scope over complements.
Specifiers scope over complements (transitivity).
No position scopes over itself.
Heads do not scope over specifiers (asymmetry).
Complements do not scope over heads (asymmetry).
Dependency status (derived from position) #
Whether a position is a dependent position. Derived from the CoP structure: specifiers and complements are dependents; heads are not.
This is not an independent stipulation — it follows from the structural definition of the CoP, where the head is the structural center and specifiers/complements are its dependents.
Equations
Instances For
Specifiers are dependents.
Heads are not dependents.
Complements are dependents.
CoP node — morpho-phonological tree node #
A node in a morpho-phonological tree within a cophonological domain. Each node represents a morpheme at a structural position, with an optional grammatical tone specification.
Dependency status is derived from position via
CoPPosition.isDependent, not independently stipulated. After
hierarchy exchange ([Rol18] Ch 4), syntactic structure
maps to a CoP tree where scope ordering determines evaluation order:
outer-scoping VIs' cophonologies apply after (and thus override)
inner-scoping ones.
- position : CoPPosition
Structural position within the CoP.
- gtSpec : Option Tone.GTSpec
Optional GT specification.
noneif this morpheme has no grammatical tone.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- Rolle2018.instReprCoPNode = { reprPrec := Rolle2018.instReprCoPNode.repr }
Derived dependency status: a node is a dependent iff its position is Spec or Complement.
Equations
- n.isDependent = n.position.isDependent
Instances For
Hierarchy exchange #
Hierarchy exchange: map a set of morphemes (from syntactic structure) to a cophonological evaluation order. The result is sorted by scope rank (highest first), so outer-scoping cophonologies are evaluated last — their effects take precedence.
[Rol18] Ch 4: hierarchy exchange preserves the inside-out derivational history of the syntactic module by referencing asymmetrical c-command, mediated through the CoP-scope ordering.
Equations
- Rolle2018.hierarchyExchange nodes = nodes.mergeSort fun (a b : Rolle2018.CoPNode) => decide (a.position.rank ≥ b.position.rank)
Instances For
Hierarchy exchange preserves the node set (it only reorders).
Deriving the dominant GT asymmetry #
The key lemma: if a position scopes over Head, it must be Spec.
Complement has lower rank than Head, so it cannot scope over Head. Head cannot scope over itself. Only Spec (rank 2 > 1) qualifies.
This is the structural backbone of the dominant GT asymmetry: if dominant GT requires scoping over the head, and only Spec scopes over Head, then dominant triggers must be at Spec.
A position that scopes over Head is a dependent position.
Follows from scopes_over_head_implies_spec (it must be Spec)
and spec_is_dependent (Spec is a dependent).
The dominant GT asymmetry derived from CoP-scope.
Hypotheses:
- The target is at Head position (it's the lexical head)
- The trigger scopes over the target (required for dominance)
From these two facts alone, the CoP-scope hierarchy determines:
- The trigger is at Spec (only Spec scopes over Head)
- Spec is a dependent position
- Head is not a dependent position
Therefore DominantGTAsymmetry.holds is satisfied: the trigger
is a dependent and the target is a head. The Bool values are
computed from positions, not independently stipulated.
Non-trivial prediction: complements are dependents but cannot be dominant triggers, because Complement does not scope over Head.
Complements cannot be dominant triggers despite being dependents: Complement does not scope over Head. This is a non-trivial prediction of the CoP-scope account — the asymmetry is not simply "dependents dominate heads" but specifically "dependents that scope over heads dominate heads."
Heads cannot impose dominant GT on specifiers (outward dominance).
Matrix-Basemap Correspondence (MxBM-C) #
A basemap is an abstract I/O mapping derived from a "deficient projection" of the input: all valued (lexical) tones on the target are stripped, leaving only floating (grammatical) tones. Dominant GT = faithfulness to the basemap output; since the basemap has no valued tones to preserve, the matrix output is forced to match the grammatical tune, so the target's underlying tones go unrealized.
Basemap — deficient projection #
Strip all tones from a host word, replacing them with a default tone. The deficient projection of [Rol18] Ch 5: the input with all valued (lexical) tones removed, leaving only the segmental skeleton ready to receive floating (grammatical) tones.
The defaultTone is the tone assigned to "unvalued" TBUs —
language-specific (often L in African tone languages).
Equations
- Rolle2018.deficientProjection host defaultTone = List.map (fun (tbu : Tone.TBU S) => { seg := tbu.seg, tone := defaultTone }) host
Instances For
Deficient projection produces uniform tone: every TBU gets the default tone.
Basemap output #
Compute the basemap output: apply the grammatical tune to the deficient projection. This represents what the output would look like if the target had no underlying tones — only the floating tones from the trigger determine the surface pattern.
For replacive-dominant GT with a whole-word melody, the basemap output has the grammatical tune on every TBU.
Equations
- Rolle2018.basemapOutput host spec defaultTone = Tone.tonalOverwrite (Rolle2018.deficientProjection host defaultTone) spec
Instances For
Tonal tier extraction #
Extract the tonal tier from a list of TBUs.
Grounded in the Tier abstraction
(TierProjection.apply (TierProjection.total TBU.tone)): an erasing string
homomorphism (TBU S)* → TRN* in the Kleisli category of Option.
The tonal tier is the total (no-erasure) case [Gol76].
Equations
- Rolle2018.tonalTier tbus = (TierProjection.total Tone.TBU.tone).apply tbus
Instances For
The tonal tier reduces to List.map TBU.tone (the historical
formulation), via TierProjection.total's length-preservation property.
Matrix-Basemap Correspondence — derived from Corr #
Matrix-Basemap Correspondence violation count: Hamming distance between the matrix tonal tier and the basemap tonal tier.
Derived from Corr.identViol on the (false, true) edge of the
binary parallel-pair correspondence between the two tiers. This
structurally identifies MxBM-C as IDENT-OO of [McCP95]
/ [Ben97] specialized to the tonal tier — no separate Hamming
implementation, no bridge theorem required.
On unequal-length tiers, the underlying Corr.parallel truncates to the
shorter prefix (matching List.zip semantics).
Equations
Instances For
Self-comparison has zero basemap violations: a tonal tier is
perfectly faithful to itself. Derived from Corr.identity_ident_zero.
Zero basemap violations with equal-length tiers implies the tiers are
identical. The equal-length hypothesis is necessary because the
underlying Corr.parallel truncates to min.
Constraint bridge #
Wrap basemapViolations as a Constraint for use in OT
tableaux and cophonological evaluation.
Given a fixed basemap output (the tonal tier of the basemap-faithful form), this constraint evaluates each candidate by comparing its tonal tier against the basemap. In [Rol18]'s analysis, dominant triggers promote this constraint above default markedness in their cophonology's subranking.
extractTier converts a candidate to its tonal tier for comparison.
This allows the constraint to work with any candidate type, not
just raw List TRN.
Equations
- Rolle2018.mkBasemapConstraint basemapTier extractTier c = Rolle2018.basemapViolations (extractTier c) basemapTier
Instances For
Dominance as basemap faithfulness #
The central theorem of MxBM-C: for replacive-dominant GT with a whole-word single-tone melody, the matrix output's tonal tier equals the basemap output's tonal tier.
This captures [Rol18]'s key insight: dominant GT is not a special deletion rule or markedness constraint, but faithfulness to an abstract basemap. The target's underlying tones go unrealized because the output must match what would happen if those tones were never there.
The basemap output's tonal tier is independent of the host's underlying tones: for whole-word replacement, two hosts with different lexical tones but identical segmental content produce the same basemap tonal tier.
The formal content of "transparadigmatic uniformity" ([Rol18] Ch 5): the basemap abstracts away from the paradigmatic tonal variation of the target.