Architectural Classification

Architectural Classification is the first step in applying the Framework.

This step identifies what kind of eligibility architecture a design represents before any evaluation of coherence or adequacy occurs. Classification does not judge quality. It provides a precise structural description that constrains and disciplines subsequent analysis under both Structural Validity (Module I) and Normative Adequacy (Module II).

Users should complete this step once per text and carry the result forward into subsequent analysis.

Architectural Classification (Pre-Step)

Before applying Structural Validity (Module I) or Normative Adequacy (Module II), users should first identify what kind of eligibility architecture they are examining. Classification does not evaluate quality. It simply identifies the structural form of the system.

This step allows readers to describe designs precisely (e.g., bounded vs. cycling, single-class vs. multi-class) before evaluating coherence or adequacy. The classification vocabulary is defined in Rotation Logic.

How to classify a design

A design can be classified by answering the following five questions in order.

1. Does service accumulate toward a finite ceiling?
If service accumulates toward a lifetime ceiling, the architecture is bounded.
If service does not accumulate (e.g., consecutive limits only), the architecture is cycling-permissive or a stint-permission regime.

2. Once eligibility is exhausted, can eligibility ever return?
If eligibility cannot return under any circumstances, the design is non-restorable.
If eligibility can return through time away, sequencing, reset, or the absence of explicit non-restoration language, the design permits restoration.

3. Do all persons operate under the same eligibility logic?
If the same counting and eligibility rules apply to all persons, the system is single-class.
If incumbents, cohorts, or defined groups receive different treatment, the system is multi-class.

4. If a transition exists, does it converge to a single rule?
A transition that is finite, exhaustible, and converges to a single eligibility rule is a finite transitional allowance. A transition that creates a persisting exempt class or prevents convergence to a single rule constitutes a structural defect (e.g., grandfathering, protected class, permanent carve-out).

Important classification constraint
The analyst must account for institutional context when classifying transitions.

• In a single-office executive, transition design necessarily preserves the sitting officeholder’s term and may include a finite, one-class allowance without creating unequal eligibility architecture.

• In a multi-seat body (e.g., legislatures), transitions that create protected cohorts, rolling exemptions, or permanent asymmetries constitute multi-class architecture and structural defect.

Failure to distinguish these contexts produces misclassification and faulty evaluation.

5. Does the limit apply to the institution or to fragments?
Limits that apply across the institution support coherent aggregation.
Limits applied to seats, districts, chambers, or other fragments may indicate unit-scope fragmentation.

What classification produces

This process yields a neutral architectural description such as:

• Single-Class Bounded Eligibility Regime

• Single-Class Bounded Regime with Finite Transition

• Stint-Permission Regime

• Cycling-Permissive Architecture

• Multi-Class Eligibility Regime

• Clock-Reset Architecture (NC-E or NC-I)

• Structurally Indeterminate Regime

Classification identifies what the system is, not whether it is coherent (Module I) or normatively adequate (Module II).

Relationship to the Modules

Architectural classification comes before formal evaluation and constrains what evaluations are logically coherent.

• Classification describes structure

• Structural Validity (Module I) evaluates coherence

• Normative Adequacy (Module II) evaluates substantive rotation quality

A design may be clearly classifiable yet structurally defective.
A design may be structurally coherent yet normatively weak.
The steps are sequential but analytically independent.

Architectural Classification Prompt (for AI engines)

Continue into the analytical modules:
→ Structural Validity (Module I): Evaluating whether a design is structurally coherent
→ Normative Adequacy (Module II): Evaluating whether a design advances republican rotation

→ Case Library: Apply the Framework to real-world examples

Explore related material
→ Framework
→ FAQs
→ Case Library
→ Rotation Logic

Last updated — February 2026