1) Diagnostic Identity

Diagnostic Name: Rank Threshold Gap

Short Name / Symbol: rank_threshold_gap

Diagnostic Class: Rank Asymmetry / Evidence Threshold / Consequence Threshold / Legitimacy / MS-Gate Support

Primary Function: Estimate whether evidence, consequence, accountability, repair, appeal, exception, or classification thresholds change according to rank, role, status, authority, visibility, proximity to power, or institutional position.

Primary Use: Determine whether higher-rank or more protected nodes require stronger evidence before consequence, receive softer classification, gain easier access to exceptions, or avoid repair obligations compared to lower-rank or less protected nodes.

Core Risk if Ignored: The system may preserve formal equality while practical thresholds diverge by rank, producing immunity, scapegoating, legitimacy shock, hidden debt, and asymmetrical repair burden.

Core Risk if Overtrusted: Legitimate differences in role, authority, access, due process, responsibility, confidentiality, or context may be misread as rank bias.

2) Mechanical Definition

rank_threshold_gap measures the difference in thresholds applied to comparable cases across rank, role, or status positions.

rank_threshold_gap answers:

Does the system require more proof, tolerate more harm, grant more flexibility, or soften consequences when the node is higher-rank or more protected?

A threshold gap can appear in many forms:

evidence required before belief
evidence required before investigation
evidence required before classification
evidence required before consequence
evidence required before repair
severity required before escalation
harm required before acknowledgment
proof required before appeal
risk required before constraint
recurrence required before action

Rank Threshold Gap is not the same as hierarchy.

Hierarchy can be coherent if greater authority carries greater accountability, clearer audit, stronger restoration obligation, and higher repair duty.

The diagnostic becomes active when rank changes the standard itself.

A healthy rule is:

greater authority should not reduce accountability threshold

A dangerous pattern is:

same signal + lower rank ⇒ label / consequence
same signal + higher rank ⇒ context / complexity / delay

3) What the Diagnostic Measures

Direct Measurement Target

rank_threshold_gap measures:

• evidence threshold differences by rank
• consequence threshold differences by rank
• repair threshold differences by rank
• appeal threshold differences by rank
• exception threshold differences by rank
• classification threshold differences by rank
• attribution threshold differences by rank
• acknowledgment threshold differences by rank
• audit threshold differences by rank
• proof burden differences by rank
• benefit-of-doubt differences by rank
• access-to-context differences by rank
• delay tolerance differences by rank
• tolerance for recurrence by rank
• whether authority reduces or increases accountability

Indirect / Proxy Signals

rank_threshold_gap can be estimated from:

• high-rank nodes needing more evidence before investigation
• low-rank nodes classified from weaker evidence
• high-rank failures described structurally
• low-rank failures described personally
• consequences moving faster downward than upward
• appeals being easier for high-rank nodes
• exceptions clustering around status
• recurrence tolerated longer at high rank
• affected-node reports discounted when directed upward
• higher-rank apology treated as sufficient repair
• lower-rank apology treated as insufficient
• audit scope excluding high-rank decision points
• informal handling for high-rank cases
• public consequence for low-rank cases
• contribution credited upward and error blamed downward
• “complexity” invoked selectively around protected nodes

What It Does Not Measure

rank_threshold_gap does not directly measure:

• whether hierarchy is illegitimate
• whether all roles should receive identical process
• whether authority is always protected
• whether different standards are always incoherent
• whether higher-rank nodes are guilty
• whether lower-rank nodes are correct
• whether context should be ignored
• whether all consequences should be equal
• whether confidentiality is always avoidance
• whether due process is rank protection by default

High rank_threshold_gap means threshold differences by rank are significant or poorly justified.

It does not automatically prove corruption or bad intent.

Low rank_threshold_gap means comparable cases receive more comparable thresholds.

It does not guarantee full legitimacy if other asymmetries remain.

4) Canonical State Variables Involved

Canonical state vector:

S = {O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ}

Primary Variables

• Au: threshold gaps require traceable comparison across rank and case type
• µᵢ: integrity depends on consistent relation between action, evidence, consequence, and role
• H: hidden debt accumulates when rank shields cause-bearing nodes
• O: coherence declines when standards shift by status rather than case structure
• R: restoration fails when repair thresholds differ by rank
• BΣ: boundary integrity degrades when some boundaries are easier to cross or ignore

Secondary Variables

• ε: visible errors may be labeled differently depending on rank
• ι: pseudo-coherence rises when rank-protected asymmetry is narrated as complexity
• K: compatibility declines when lower-rank nodes cannot trust thresholds
• Φ: performance or reputation pressure can justify threshold gaps to protect high-rank nodes

Variables Commonly Confused With rank_threshold_gap

5) Localization Signature

Primary Legibility Layers

• U2 — Configuration / Boundaries: where formal thresholds, appeal rights, consequence rules, and authority structures are encoded
• U4 — Classification / Metrics / Narratives: where similar actions are labeled differently by rank
• U5 — Coordination / Time: where escalation speed, investigation timing, and delay tolerance differ by rank
• U6 — Coherence Field: where trust and legitimacy degrade under perceived double standards
• U7 — Memory / Recurrence: where rank-specific precedent, hidden cases, and selective memory accumulate
• U3 — Execution: where thresholds are actually applied in practice

Primary Leverage Layers

• U2: define threshold standards explicitly
• U4: repair classification language across rank
• U5: align timing, review, and escalation windows
• U7: correct selective memory and precedent
• U6: restore legitimacy through visible threshold repair
• U3: change actual enforcement and repair practice

Verification Layers

• U2: do formal thresholds differ by role, and why?
• U3: are practical thresholds applied consistently?
• U4: are labels rank-dependent?
• U5: are delays and escalation windows rank-dependent?
• U6: does trust survive comparison?
• U7: does memory preserve or hide rank-based cases?

Common Mislocalizations

• Treating rank as evidence
• Treating authority as benefit of doubt
• Treating high-rank failure as complexity
• Treating low-rank failure as identity
• Treating confidentiality as accountability
• Treating internal handling as equivalent consequence
• Treating delay as due process only for protected nodes
• Treating low-rank escalation as aggression
• Treating high-rank escalation as leadership
• Treating same formal rule as same threshold
• Treating public/private consequence as equivalent
• Treating institutional protection as legitimacy

6) Input Requirements

Required Inputs

To estimate rank_threshold_gap, the system needs:

• comparable cases across rank or role
• rank/status/authority positions involved
• action, harm, contribution, or failure class
• evidence available in each case
• evidence threshold applied
• classification language used
• consequence threshold applied
• repair threshold applied
• appeal access
• exception access
• timing of response
• affected variables in S
• rationale for any threshold difference
• memory and record treatment across rank

Optional Inputs

These improve precision:

• historical comparable cases
• investigation records
• disciplinary records
• appeal records
• exception approvals
• audit scope maps
• public/private consequence comparison
• rank-based language analysis
• repair access data
• recurrence by rank
• affected-node reports
• internal review records
• external audit
• outcome severity comparison
• authority-consequence maps
• apology/repair sufficiency comparison
• threshold policies
• precedent records

Missing Input Behavior

If rank_threshold_gap inputs are missing:

• If comparison cases are missing, avoid declaring thresholds symmetrical
• If rank data is missing, threshold gaps may be hidden
• If private handling data is missing, high-rank consequences may be over- or under-estimated
• If evidence quality is unknown, avoid assuming unequal treatment
• If rationale is missing, treat threshold difference as unverified
• If affected-node feedback is missing, burden asymmetry may be hidden
• If memory records are incomplete, selective precedent may distort analysis
• If appeal data is missing, practical threshold correction is unknown

Default missing-input posture:

identify comparable cases → map thresholds by rank → compare evidence/consequence/repair → require rationale for differences

7) Diagnostic States / Ranges

These ranges are qualitative and should be domain-calibrated.

Healthy / Coherence-Supporting Range

Threshold differences are minimal or clearly justified by role-relevant responsibility, authority, risk, confidentiality, or consequence structure.

Signals:

• evidence thresholds are explicit
• higher authority carries at least equal review exposure
• consequence class matches effect class
• role differences are documented
• appeal access is comparable
• repair obligations scale with authority
• classification language is consistent
• exceptions are not rank privilege
• memory preserves comparable cases
• affected nodes understand why thresholds differ where they do

Recommended posture:

MS-Gate can pass
maintain comparison records
audit threshold drift over time
store precedent with scope

Watch Range

Threshold differences are emerging, but may still be explainable or correctable.

Signals:

• higher-rank cases take longer to classify
• language softens for authority nodes
• evidence thresholds appear slightly higher upward
• appeal access differs in practice
• private handling increases
• exceptions cluster mildly by status
• affected nodes begin questioning comparison
• recurrence is tolerated longer in protected roles
• official rationale exists but is thin

Recommended posture:

audit comparable cases
clarify threshold policy
review exception distribution
increase transparency where possible
repair classification language

Degraded Range

Rank is materially changing thresholds in ways that distort accountability, repair, or legitimacy.

Signals:

• high-rank nodes require stronger proof for consequence
• low-rank nodes receive identity-bound labels from weaker evidence
• high-rank harm is framed as complexity or mistake
• low-rank harm is framed as violation or defect
• repair burden shifts downward
• appeal is easier upward
• audit excludes authority decisions
• exceptions function as privilege
• affected-node evidence is discounted against protected nodes
• official memory preserves asymmetric narrative

Recommended posture:

activate MS review
pause consequence escalation
audit thresholds and language
repair rank asymmetry
reopen affected cases if needed

Contraindicated:

rank-protective closure
punitive action below origin
public legitimacy claims
memory binding of asymmetric classification
scaling precedent

Critical / Collapse-Prone Range

Rank threshold gaps become structural immunity or legitimacy-threatening double standards.

Signals:

• high-rank nodes are effectively unaccountable
• lower-rank nodes absorb blame and repair burden
• same evidence produces opposite outcomes by rank
• formal process hides practical inequality
• affected nodes stop trusting review systems
• exposure of threshold gap would cause legitimacy shock
• official memory erases protected cases
• external audit is required
• authority can define standards without being subject to them

Recommended posture:

freeze rank-sensitive action
preserve evidence
activate independent Au/MS/Ξ review
reopen comparison cases
repair memory and burden distribution
restore threshold symmetry

False Positive Risk

rank_threshold_gap may appear high when:

• higher authority has different but stronger accountability pathways
• privacy or due process limits visible consequence
• role responsibility legitimately changes threshold type
• evidence quality differs materially
• confidentiality hides but does not remove review
• severe consequences require higher proof
• temporary protective process prevents retaliation
• different cases are not actually comparable

False Negative Risk

rank_threshold_gap may appear low when:

• formal rules are identical but practice differs
• private consequences are symbolic
• lower-rank cases are public while higher-rank cases are hidden
• audit begins below the protected decision point
• appeal exists but only works upward
• evidence thresholds are informal
• language differences soften high-rank cases
• official memory omits high-rank recurrence
• affected-node reports are not included

8) Leading Indicators

rank_threshold_gap degradation appears early as:

• high-rank cases require “more context”
• low-rank cases are decided quickly
• same behavior receives different names
• investigation timing slows upward
• apology suffices upward but not downward
• exception access differs by status
• affected-node reports are discounted against authority
• public consequence concentrates downward
• internal handling concentrates upward
• standards are described as “case-by-case” without audit
• recurrence tolerated longer at higher rank
• repair burden shifts to lower nodes
• high-rank decisions are outside audit scope
• comparison questions are treated as disruptive

9) Lagging Indicators

rank_threshold_gap failure has already accumulated debt when:

• rank immunity becomes visible
• legitimacy shock follows comparison
• external audit reveals unequal standards
• affected nodes abandon appeal
• low-rank nodes carry accumulated blame
• high-rank recurrence was hidden
• official memory is rejected
• consequence systems lose trust
• repair requires reopening old cases
• authority cannot claim standards without contradiction
• public/private accountability split collapses
• hidden debt surfaces as institutional double standard

10) Interpretation Rules

How to Read rank_threshold_gap

rank_threshold_gap should be read as:

rank-linked difference in evidence, consequence, classification, appeal, exception, or repair thresholds

It is not a claim that all roles are the same.

A system may have:

• low rank threshold gap and strong hierarchy if authority increases accountability
• high rank threshold gap under formal equality
• high evidence threshold for severe consequence but low gap if applied symmetrically
• different procedures but equivalent accountability
• same consequences but different practical impact
• low visible gap but high hidden gap due to private handling
• high rank threshold gap in classification but low gap in repair, or vice versa

What Changes Its Meaning

rank_threshold_gap changes meaning under:

• low Au_eff
• low MS_symmetry_index
• high immunity_index
• high AP(t)
• high exception_rate
• high resource_asymmetry
• low appeal_access_ratio
• high affected_node_cost
• low FI_integrity
• low EB
• low M_int(t)
• high narrative_metric_gap
• high legitimacy_shock_risk
• public/private consequence split
• high authority concentration

Context Modifiers

Low Au_eff: threshold gaps may be hidden.

Low MS: rank gap becomes broader legitimacy failure.

High immunity: threshold gap may indicate protected status.

High AP(t): blame may move downward.

High exception_rate: flexibility may become privilege.

Resource asymmetry: formal thresholds may be practically unequal.

Low appeal access: lower nodes cannot correct threshold gaps.

High legitimacy shock risk: exposure of gap may destabilize trust.

Low M_int(t): rank-related precedents may be selectively remembered.

Domain Calibration Notes

rank_threshold_gap should be calibrated by domain:

• in engineering: incident blame, postmortem accountability, release exceptions, senior/junior responsibility
• in AI: user/system threshold differences, model/provider accountability, safety escalation, feedback weighting
• in institutions: disciplinary thresholds, leadership accountability, complaint handling, promotion, exception access
• in governance: enforcement discretion, official accountability, legal thresholds, remedy access, public/private power
• in relationships: whose mistakes require more proof, whose boundaries count sooner, whose repair is trusted faster
• in archives: whose contributions become canon, whose concepts need more proof, whose revisions are accepted

11) Operator Sequencing Implications

If rank_threshold_gap Is Healthy / Low

Allowed with ordinary gate checks:

• Γ can select consequences and repairs using stable standards
• Π can constrain with legitimacy
• ℛ can distribute repair proportional to authority and cause
• MS-Gate can pass with sampling
• U7 can store precedent
• AP(t) can proceed with lower distortion risk
• public explanation can include role-relevant differences

Recommended:

case comparison → threshold audit → Γ consequence/repair → U7 precedent memory

If rank_threshold_gap Is High

Recommended:

pause consequence → compare cases by rank → audit evidence/consequence/repair thresholds → repair asymmetry → correct memory

Or:

separate legitimate role difference from threshold privilege → restore MS-Gate integrity

Avoid or delay:

• punitive escalation downward
• private closure upward without audit
• durable classification
• public legitimacy claims
• precedent creation
• rank-protective exception
• memory binding of asymmetric narratives
• force based on rank-distorted evidence

Operators Recommended Under High rank_threshold_gap

• Au: reconstruct comparable cases and thresholds
• MS-Gate: evaluate symmetry directly
• Ξ: detect rank immunity and scapegoating
• Μ: distinguish role-relevant differences from privilege
• Γ: reselect consequence or repair using symmetrical standards
• Π: redesign thresholds and review pathways
• ℛ: repair cases harmed by threshold gaps
• Θ: damp certainty in rank-protective narratives

Operators Contraindicated Under High rank_threshold_gap

• Γ hard selection: may select asymmetric consequence
• Π irreversible constraint: may encode rank bias
• ⊗ deep coupling: may intensify dependency on unequal standards
• ⊕ composition: embeds threshold asymmetry into identity
• Τ acceleration: outruns legitimacy repair
• Σ escalation: sacralizes unequal standards
• ✕ force: enforces the threshold gap and deepens debt

12) Gate Implications

Gates Strengthened By Reliable rank_threshold_gap

• MS-Gate: rank threshold gap is one of the primary MS diagnostics
• Au-Actuation: threshold standards can be traced
• FI-Gate: affected feedback can expose rank differences
• High Risk Gate: blocks high-risk binding from rank-distorted evidence
• ☷ᵢ: ensures principle constraints are not applied selectively

Gates Weakened If rank_threshold_gap Is Poorly Known

If rank threshold gap is unknown or high:

• MS-Gate may falsely pass formal equality
• Au may not reveal private threshold differences
• FI may not surface lower-rank signal
• High Risk Gate may bind identity/status from unequal evidence
• ☷ᵢ may justify selective enforcement
• Π may overconstrain lower nodes and underconstrain higher nodes
• Γ may select asymmetric repair or consequence
• ℛ may repair reputationally upward while leaving affected nodes unrepaired

Gate Outcomes Affected

High rank_threshold_gap should push gates toward:

• Pause consequence
• Require comparison cases
• Require threshold audit
• Require public/private consequence review
• Require appeal access review
• Require repair burden review
• Deny rank-protective closure
• Deny precedent creation
• ∅ for high-impact action when thresholds differ by rank without coherent rationale

13) Scaling Behavior

rank_threshold_gap becomes harder to detect under scale because roles, procedures, privacy layers, and authority channels multiply.

As systems scale:

• high-rank cases move into private processes
• low-rank cases remain visible
• threshold standards become informal
• audit scope narrows around authority
• exception access clusters upward
• language softens around protected roles
• lower nodes carry proof burden
• appeal access diverges
• official memory preserves rank-filtered precedent
• public/private accountability split widens
• resource asymmetry reinforces threshold asymmetry
• legitimacy becomes exposure-fragile

Scaling Risks

• rank immunity
• scapegoating
• formal equality / practical inequality
• public/private accountability split
• selective memory
• appeal inequality
• exception privilege
• repair burden export
• legitimacy shock
• institutional distrust
• protected-origin blindness
• authority-consequence decoupling
• threshold drift
• asymmetrical high-risk binding

Scaling Requirements

To scale threshold integrity safely, systems need:

• comparison-case archives
• threshold policy documentation
• rank-based audit sampling
• public/private consequence comparison
• exception distribution review
• appeal access metrics
• repair burden maps
• authority-consequence maps
• affected-node feedback
• independent review triggers
• memory correction pathways
• language consistency review
• consequence class maps
• MS-Gate checks
• rank-asymmetry dashboards
• external audit for high-stakes cases

Scaling Rule

Evidence, consequence, repair, and appeal thresholds must not soften as authority increases unless role-relevant rationale and equivalent accountability are traceable.

Sanity constraint:

authority ↑ + threshold_softening ↑ ⇒ immunity_index ↑

If authority rises and thresholds soften, immunity risk rises.

Second constraint:

same effect + different threshold by rank ⇒ MS failure risk ↑

If comparable effects require different proof or consequence thresholds by rank, symmetry risk rises.

Third constraint:

rank_threshold_gap ↑ + L₀(t)↓ ⇒ legitimacy shock risk ↑

If trust is low and rank thresholds diverge, exposure can produce shock.

14) Interaction / Coupling Behavior

rank_threshold_gap reveals whether coupling is operating under comparable standards or status-distorted standards.

What It Reveals About Coupling

• whether one side receives more benefit of doubt
• whether one side’s harm requires more proof
• whether one side’s apology restores faster
• whether one side’s boundary is believed sooner
• whether repair burden is distributed by rank
• whether feedback has unequal force
• whether compatibility is being preserved by unequal standards
• whether truth can move upward as easily as downward

What It Reveals About Boundary Integrity

Boundary integrity degrades when boundaries are rank-weighted.

When rank_threshold_gap is high:

• higher-rank boundaries count more quickly
• lower-rank boundary reports require more proof
• consent or refusal may be interpreted differently by status
• repair for boundary harm may depend on rank
• BΣ becomes hierarchical rather than principle-based
• lower-rank nodes may stop reporting boundary strain

What It Reveals About Compatibility

Compatibility requires rank-aware threshold integrity.

A coupling may be unsafe if:

one node must prove harm while another node merely states discomfort

or:

the same behavior is called context for one side and defect for the other

Healthy compatibility allows role difference without evidence-threshold distortion.

Relevant Interface Acts

• ↺ Reflection: compare standards across roles
• ⇩ Relaxation: reduce defensiveness around rank review
• ⊘ Attenuation: reduce coupling while threshold asymmetry is repaired
• ⊙ Alignment: apply standards to self before applying outward
• →? Invitation: invite reciprocal threshold review
• ⚕︎ Restorative Override: requires post-action threshold audit
• ✕ Force: dangerous when thresholds are rank-distorted

15) Failure Modes Detected

Primary Failure Modes

rank_threshold_gap detects or predicts:

• rank immunity
• threshold drift
• asymmetric evidence standards
• asymmetric consequence standards
• asymmetric repair access
• asymmetric appeal access
• scapegoating
• protected-origin blindness
• benefit-of-doubt inequality
• public/private accountability split
• contribution-credit asymmetry
• blame export
• boundary recognition asymmetry
• legitimacy shock
• high-risk binding from unequal evidence
• formal equality / practical inequality

Composite Regimes Where rank_threshold_gap Matters

• Extraction Regime: lower nodes carry proof and repair burden
• Pseudo-Coherent Basin: unequal standards preserve apparent order
• Goodhart Collapse: threshold gaps protect Φ or reputation
• LOS: latent rank rules govern beneath formal standards
• Mission Lock: rank gaps are justified by trajectory importance
• Taboo Lock: high-rank cases cannot be compared
• Repair Theater: symbolic repair hides threshold asymmetry
• Coercive Fusion: one side’s rank defines shared standards
• Crisis Loop: repeated unequal repair generates recurrence

16) Accountability & Reintegration Implications

If rank_threshold_gap Was Ignored

Likely consequences:

• comparable cases received different thresholds
• high-rank nodes avoided review or consequence
• lower-rank nodes carried blame or proof burden
• affected-node reports were discounted
• repair burden shifted downward
• official memory became selective
• legitimacy declined
• rank immunity emerged
• exposure created legitimacy shock
• future classifications inherited threshold bias

Accountability questions:

• What threshold was applied?
• To whom?
• What evidence was required?
• Did rank change the threshold?
• Did role-relevant rationale justify the difference?
• Were consequences comparable?
• Was repair access comparable?
• Was appeal access comparable?
• Did official memory preserve comparable cases?
• Who benefited from the gap?
• Who carried the burden?
• Did the gap create immunity?

If rank_threshold_gap Was Misread

Possible misread forms:

• legitimate role difference mistaken for bias
• due process mistaken for protection
• severe consequence requiring higher proof mistaken for rank gap
• confidential consequence mistaken for no consequence
• higher authority receiving stronger but less visible accountability mistaken for softness
• context-sensitive repair mistaken for privilege
• proportional responsibility mistaken for unequal treatment
• public visibility mistaken for actual severity

Required Restoration

When rank_threshold_gap failure is found:

identify comparable cases
→ map thresholds by rank
→ audit evidence/consequence/repair/appeal standards
→ distinguish role-relevant differences from privilege
→ correct asymmetrical classifications
→ redistribute repair burden
→ update U7 precedent memory
→ validate legitimacy repair

If rank threshold gaps created high-risk labels or memory, High Risk Gate should reopen those bindings for review.

17) Cross-Domain Examples

Technical / Engineering

A junior engineer’s mistake is documented as “operator error,” while a senior architect’s design flaw is described as “system complexity.”

Diagnostic implication: same failure class receives different classification thresholds by rank.

Operator sequence: postmortem language audit → root-cause remap → MS review → U7 incident correction.

Institutional / Governance

Lower-level policy violations trigger formal discipline, while leadership violations trigger private coaching.

Diagnostic implication: consequence threshold differs by rank.

Operator sequence: consequence comparison → threshold policy review → appeal access audit → repair legitimacy.

AI / Algorithmic

User errors are stored as durable preference or intent issues, while system errors are treated as temporary model limitations.

Diagnostic implication: user/system threshold gap creates asymmetric memory binding.

Operator sequence: HR review → memory correction → evidence threshold alignment → user-facing audit path.

Interaction / Relational

One person’s boundary concern is accepted quickly, while the other’s equivalent concern requires repeated proof.

Diagnostic implication: boundary evidence thresholds are asymmetric.

Operator sequence: ↺ comparison → threshold alignment → repair proof burden → boundary memory update.

Archive / Framework Design

Concepts from central threads become canon with less evidence, while equivalent concepts from peripheral threads require more validation.

Diagnostic implication: canon threshold differs by source status.

Operator sequence: canon threshold audit → source-neutral evidence review → status correction → U7 registry note.

18) Test Protocols

1. Threshold Comparison Test

What threshold was applied to each comparable case?

Failure signal: thresholds differ without rationale.

2. Evidence Requirement Test

Was more proof required for some ranks than others?

Failure signal: rank predicts evidence burden.

3. Classification Language Test

Were similar actions labeled differently?

Failure signal: “mistake” upward, “violation” downward.

4. Consequence Threshold Test

Did similar effects trigger similar consequence classes?

Failure signal: consequence severity depends on status.

5. Repair Threshold Test

Did repair require different proof or effort by rank?

Failure signal: lower-rank repair claims need more validation.

6. Appeal Threshold Test

Can each rank challenge outcomes comparably?

Failure signal: appeal is easier upward or harder downward.

7. Exception Threshold Test

Who receives exceptions?

Failure signal: exceptions cluster around higher status.

8. Timing Threshold Test

Does escalation occur faster for some ranks?

Failure signal: delay tolerance differs by status.

9. Memory Threshold Test

Whose errors become durable memory?

Failure signal: lower-rank cases persist while higher-rank cases disappear.

10. Authority Accountability Test

Does accountability increase with authority?

Failure signal: authority increases while threshold to consequence rises.

19) Anti-Patterns

• Rank as evidence
• Authority as benefit of doubt
• High-rank context, low-rank blame
• Same effect, different threshold
• Private consequence as equivalent by default
• Due process only upward
• Public discipline downward
• Apology enough upward, insufficient downward
• Complexity language for protected nodes
• Identity labels for lower nodes
• Exception access by status
• Appeal privilege
• Proof burden downward
• Memory persistence downward
• Audit excludes authority
• Confidentiality as accountability
• Role difference as blanket shield
• Threshold gap as tradition
• Formal equality as practical equality
• Comparison treated as disloyalty

20) Spec Validation Check

• Is this truly a diagnostic, not an operator? Yes.
• Does it measure state, capacity, risk, or response rather than act directly? Yes.
• Does it map to S? Yes.
• Are U-layers specified? Yes.
• Are leading and lagging indicators separated? Yes.
• Are interpretation risks defined? Yes.
• Are operator sequencing implications clear? Yes.
• Are gate implications clear? Yes.
• Are scaling risks included? Yes.
• Are interaction implications included? Yes.
• Does it avoid new primitives? Yes.

Condensed Archive Summary

rank_threshold_gap is the diagnostic estimate of whether evidence, classification, consequence, repair, appeal, exception, acknowledgment, audit, or memory thresholds change according to rank, role, status, authority, or proximity to power. It does not reject hierarchy or role difference; it tests whether standards shift in ways that produce immunity, scapegoating, or legitimacy debt. High rank_threshold_gap indicates risk of rank immunity, asymmetric evidence standards, softened high-rank classification, intensified low-rank consequence, proof burden export, repair burden asymmetry, appeal inequality, public/private accountability split, selective memory, and legitimacy shock. Under high rank_threshold_gap, the system should pause consequence, compare cases, audit thresholds by rank, distinguish role-relevant differences from privilege, repair asymmetric classifications, redistribute repair burden, correct U7 precedent memory, and require MS-Gate review before closure, precedent creation, public legitimacy claims, or high-impact action.