1) Diagnostic Identity

Diagnostic Name: Meta-Symmetry Index

Short Name / Symbol: MS_index

Diagnostic Class: Symmetry / Consequence Consistency / Legitimacy / Gate Integrity / Governance Coherence

Primary Function: Estimate whether equivalent actions, effects, risks, evidence, burdens, privileges, violations, repairs, or contributions receive equivalent classification, consequence, review, and restoration across nodes, ranks, roles, groups, or system positions.

Primary Use: Determine whether a system applies standards symmetrically enough to preserve legitimacy, coherence, auditability, and repair.

Core Risk if Ignored: The system may apply different thresholds or consequences to similar cases, producing rank immunity, scapegoating, legitimacy shock, hidden debt, distorted attribution, and boundary failure.

Core Risk if Overtrusted: Mechanical sameness may be mistaken for real symmetry, causing the system to ignore relevant differences in context, role, authority, capacity, harm, vulnerability, or responsibility.

2) Mechanical Definition

MS_index measures whether comparable cases are treated comparably at the meta-level of rule, evidence, consequence, burden, repair, and review.

MS_index answers:

Are equivalent cases receiving equivalent treatment?

This diagnostic does not require identical treatment in every case.

It asks whether differences in treatment are justified by coherent, auditable, role-relevant distinctions rather than rank, power, convenience, narrative protection, proximity, identity, reputation, or institutional preference.

A system has strong meta-symmetry when it can explain:

why this case is treated like that case
why this case is treated differently
what principle governs the difference
who carries burden
who receives protection
who receives consequence
who can appeal
who receives repair

MS_index is the central diagnostic supporting MS-Gate.

Its core logic:

same class of effect → same class of review
same class of harm → same class of repair
same class of authority → same class of accountability
same class of evidence → same class of confidence
same class of contribution → same class of recognition

3) What the Diagnostic Measures

Direct Measurement Target

MS_index measures:

• symmetry of evidence thresholds
• symmetry of consequence thresholds
• symmetry of repair access
• symmetry of appeal access
• symmetry of classification standards
• symmetry of attribution standards
• symmetry of enforcement
• symmetry of forgiveness / correction
• symmetry of burden distribution
• symmetry of credit distribution
• symmetry of exception access
• symmetry of boundary respect
• symmetry of feedback force
• symmetry of audit exposure
• symmetry of memory correction
• symmetry of responsibility relative to authority
• whether differences in treatment are principled and traceable

Indirect / Proxy Signals

MS_index can be estimated from:

• different evidence thresholds by rank
• different consequence levels for similar actions
• high-rank nodes receiving structural explanations
• low-rank nodes receiving identity blame
• unequal access to appeal
• unequal access to exceptions
• unequal access to repair
• unequal exposure to audit
• unequal correction of memory
• unequal burden after system failure
• credit concentrating upward
• blame distributing downward
• affected-node cost not matched by restoration
• “mistakes” for some, “violations” for others
• discretion available to some nodes but not others
• feedback from some nodes changing the system more than feedback from others
• similar boundary crossings interpreted differently by status

What It Does Not Measure

MS_index does not directly measure:

• whether all nodes are identical
• whether all cases should be treated the same
• whether hierarchy is always incoherent
• whether context should be ignored
• whether authority and responsibility are equal for all roles
• whether all consequences should be identical
• whether all harm has the same severity
• whether all contributions are equal
• whether discretion is always corruption
• whether asymmetry is always illegitimate

High MS_index means treatment is more meta-symmetric, proportional, and explainable.

It does not mean identical outcomes.

Low MS_index means treatment varies in ways that may be unprincipled, unauditable, rank-biased, or legitimacy-damaging.

It does not mean every unequal outcome is incoherent; some differences may be valid if grounded in role, authority, capacity, context, or consequence.

4) Canonical State Variables Involved

Canonical state vector:

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

Primary Variables

• O: coherence depends on comparable cases being treated by comparable principles
• Au: symmetry requires traceable standards, thresholds, and outcomes
• µᵢ: agent integrity depends on consistent relation between action, role, consequence, and repair
• BΣ: boundary integrity depends on equivalent respect for equivalent boundaries
• H: hidden debt rises when asymmetry is denied, hidden, or normalized
• R: restoration must be distributed in proportion to harm, responsibility, and repair need

Secondary Variables

• ε: visible deviations may reveal inconsistent treatment
• ι: inversion risk rises when formal equality hides actual asymmetry
• K: compatibility degrades when one node carries asymmetric burden
• Φ: performance or legitimacy pressure may justify asymmetry to preserve metrics or image

Variables Commonly Confused With MS_index

5) Localization Signature

Primary Legibility Layers

• U2 — Configuration / Boundaries: where rules, permissions, gates, consequences, and appeal structures are encoded
• U4 — Classification / Metrics / Narratives: where cases are labeled, compared, justified, or distinguished
• U5 — Coordination / Time: where review timing, escalation, and response windows differ across nodes
• U6 — Coherence Field: where asymmetry affects trust, legitimacy, and shared reality
• U7 — Memory / Recurrence: where past asymmetries become precedent, grievance, institutional memory, or hidden debt

Primary Leverage Layers

• U2: align rules, thresholds, appeal structures, and consequence classes
• U4: repair classifications and case comparisons
• U5: synchronize review and response timing across comparable cases
• U7: correct asymmetric precedent and memory
• U6: restore legitimacy through visible symmetry repair

Verification Layers

• U2: are rules symmetrical across comparable cases?
• U4: are labels and narratives applied consistently?
• U5: are response windows equivalent?
• U6: does the system retain legitimacy under comparison?
• U7: does memory preserve asymmetry or correction accurately?
• U3: do actual behaviors match formal standards?

Common Mislocalizations

• Treating equal language as equal treatment
• Treating unequal context as proof of bias without audit
• Treating status as reason for different standard
• Treating authority as immunity
• Treating responsibility as blame only
• Treating same rule as same burden
• Treating formal appeal as practical appeal
• Treating visible consequence as actual consequence
• Treating punishment symmetry as repair symmetry
• Treating discretion as automatically coherent
• Treating consistency as rigidity
• Treating identical outcomes as justice

6) Input Requirements

Required Inputs

To estimate MS_index, the system needs:

• cases being compared
• relevant action/effect/harm/contribution class
• rule or standard applied
• evidence threshold used
• consequence applied
• repair offered or required
• appeal access
• classification language
• attribution language
• affected variables in S
• rank / role / authority position
• burden distribution
• exception status
• timing of response
• memory status
• rationale for any difference in treatment

Optional Inputs

These improve precision:

• historical cases
• precedent records
• appeal success rates
• exception approval rates
• enforcement records
• rank_threshold_gap
• immunity_index
• affected_node_cost
• feedback impact by rank
• repair burden distribution
• contribution recognition records
• public/private consequence comparison
• time-to-response comparison
• evidence quality comparison
• external audit
• recurrence after asymmetry
• legitimacy indicators
• affected-node validation

Missing Input Behavior

If MS_index inputs are missing:

• If comparison cases are missing, do not infer symmetry from one case
• If rationale for difference is missing, treat asymmetry as unverified
• If rank data is missing, check for hidden threshold gaps
• If appeal data is missing, do not infer contestability
• If repair data is missing, consequence symmetry may be incomplete
• If memory data is missing, asymmetric precedent may be hidden
• If affected-node feedback is missing, burden asymmetry may be under-sampled
• If exception data is missing, flexibility symmetry may be unknown

Default missing-input posture:

identify comparable cases → map thresholds/consequences/repair/access → test rationale → correct asymmetry or document valid distinction

7) Diagnostic States / Ranges

These ranges are qualitative and should be domain-calibrated.

Healthy / Coherence-Supporting Range

Comparable cases receive comparable standards, and differences are principled, traceable, and role-relevant.

Signals:

• evidence thresholds are explicit
• comparable cases are compared
• differences are justified by relevant distinctions
• appeal access is comparable
• repair access is proportional
• consequence class matches effect class
• authority increases accountability rather than immunity
• affected-node cost is recognized
• exceptions are reviewed symmetrically
• memory preserves precedent and correction
• similar boundary violations receive similar review

Recommended posture:

MS-Gate can pass
continue audit sampling
store precedent with scope
use symmetry map for future Γ / Π / ℛ

Watch Range

Symmetry mostly holds, but asymmetry, threshold drift, or unclear distinctions are emerging.

Signals:

• similar cases receive slightly different framing
• rank begins affecting language
• appeal access differs in practice
• exception approvals cluster
• repair burden appears uneven
• consequence severity varies without clear rationale
• affected nodes ask why cases differ
• public and private standards diverge
• memory preserves some cases more strongly than others

Recommended posture:

audit comparison cases
clarify thresholds
review exception distribution
increase Au_eff
repair memory asymmetry

Degraded Range

Comparable cases are being treated inconsistently in ways that produce hidden debt, legitimacy strain, or distorted repair.

Signals:

• high-rank nodes receive softer classification
• low-rank nodes receive harsher consequence
• similar boundary crossings receive different names
• evidence thresholds vary by status
• appeal access is unequal
• repair is available to some nodes but not others
• contribution is credited asymmetrically
• blame is assigned asymmetrically
• official rationale does not explain the difference
• affected-node burden is ignored

Recommended posture:

activate MS-Gate review
pause consequence escalation
map case comparisons
repair threshold asymmetry
redistribute repair burden

Contraindicated:

declaring legitimacy
punitive escalation
closure claims
rank-protective exceptions
memory binding of asymmetric classification
scaling the rule or precedent

Critical / Collapse-Prone Range

Asymmetry becomes structural, normalized, protected, or legitimacy-threatening.

Signals:

• some nodes are effectively immune
• some nodes carry recurring disproportionate burden
• same action receives opposite meaning by rank
• official memory preserves asymmetric narratives
• appeal and repair systems are inaccessible to affected nodes
• exceptions function as privilege
• legitimacy shock occurs after comparison
• system cannot acknowledge asymmetry without destabilization
• formal rules hide actual consequence inequality
• hidden debt accumulates around protected classes

Recommended posture:

freeze asymmetry-dependent actuation
preserve evidence
activate MS / Au / Ξ review
reopen comparable cases
repair affected-node burden
correct U7 precedent memory
restore symmetrical thresholds

False Positive Risk

MS_index may appear low when:

• genuinely different contexts justify different treatment
• different roles carry different responsibilities
• higher authority receives different consequence because authority is different
• affected-node need differs by harm type
• repair must be individualized
• temporary asymmetry is needed to restore prior imbalance
• vulnerability or capacity differences require proportional adjustment
• identical outcomes would create incoherence

False Negative Risk

MS_index may appear high when:

• formal rules are identical but burdens differ
• appeal exists but is inaccessible
• consequences look equal but impact differs
• high-rank cases are resolved privately
• low-rank cases are publicly recorded
• exceptions are hidden
• memory preserves some classifications more strongly
• evidence thresholds differ silently
• official language masks unequal treatment

8) Leading Indicators

MS_index degradation appears early as:

• similar cases are described differently
• “context” is invoked selectively
• high-rank explanations become structural
• low-rank explanations become personal
• exceptions cluster by status
• appeals succeed unevenly
• affected nodes ask for comparison
• consequence language changes by role
• credit concentrates upward
• blame concentrates downward
• repair burden moves to lower-power nodes
• official examples exclude protected cases
• memory of comparable cases becomes selective
• rules are the same but access differs
• enforcement discretion increases without audit

9) Lagging Indicators

MS_index failure has already accumulated debt when:

• legitimacy shock occurs after comparisons become visible
• rank immunity is widely recognized
• affected nodes stop trusting review systems
• appeals are viewed as performative
• external audit reveals unequal thresholds
• old cases must be reopened
• hidden debt surfaces through grievance or rupture
• official memory is rejected as selective
• consequence systems lose authority
• repair requires redistribution of burden
• formal equality is no longer believed
• system cannot repair without naming asymmetry

10) Interpretation Rules

How to Read MS_index

MS_index should be read as:

context-specific consistency of standards across comparable cases

It is not mechanical sameness.

A system may have:

• high MS with different outcomes if differences are principled and traceable
• low MS with identical rules if burden and access differ
• high MS in classification but low MS in repair
• high MS in enforcement but low MS in appeal
• high MS for low-stakes cases and low MS for high-stakes cases
• high formal MS and low practical MS
• rank-asymmetric MS where authority shields consequence

What Changes Its Meaning

MS_index changes meaning under:

• low Au_eff
• high AP(t)
• high exception_rate
• high immunity_index
• high rank_threshold_gap
• high affected_node_cost
• low appeal_access_ratio
• low FI_integrity
• low EB
• low M_int(t)
• high Φ pressure
• high X_c(t)
• high dependency_load
• high public legitimacy pressure
• durable U7 memory risk

Context Modifiers

Low Au_eff: asymmetry may be hidden or unverifiable.

High AP(t): attribution pressure may distort symmetry.

High exception_rate: special cases may become rank privilege.

High immunity_index: protected nodes escape consequence.

High affected_node_cost: burden symmetry must be checked.

Low appeal_access_ratio: formal symmetry may not be practical.

High Φ pressure: asymmetry may protect performance or image.

Low M_int(t): memory may preserve some cases and erase others.

Domain Calibration Notes

MS_index should be calibrated by domain:

• in engineering: incident blame, root-cause ownership, review standards, release exceptions
• in AI: user treatment, safety classification, feedback weight, memory correction access, tool permissions
• in institutions: discipline, promotion, complaint handling, exceptions, repair access, burden distribution
• in governance: enforcement, rights, legal thresholds, public services, appeal, remedy, accountability
• in relationships: responsibility, repair burden, boundary respect, forgiveness, trust rebuilding
• in archives: canon standards, source credit, deprecation rules, status transitions, diagnostic/operator classification

11) Operator Sequencing Implications

If MS_index Is Healthy

Allowed with ordinary gate checks:

• Γ can select consequences or repairs from symmetrical standards
• Π can constrain with legitimacy
• ℛ can distribute repair proportionally
• AP(t) can proceed with lower distortion risk
• U7 memory can store precedent
• Λ / ⊗ can evaluate compatibility under trust
• exceptions can be handled if reviewed symmetrically

Recommended:

case comparison → threshold check → Γ proportional decision → ℛ repair / Π consequence → U7 precedent update

If MS_index Is Low

Recommended:

pause consequence → compare cases → audit thresholds → review rank/exception asymmetry → repair burden distribution → correct memory

Or:

activate MS-Gate → prevent closure until standards are made explicit

Avoid or delay:

• punitive escalation
• rank-protective closure
• durable U7 classification
• public legitimacy claims
• precedent creation
• scaling enforcement
• deep coupling based on asymmetric trust
• consequence assignment without comparison set

Operators Recommended Under Low MS_index

• Au: reconstruct comparable cases and thresholds
• Μ: distinguish relevant from irrelevant differences
• Γ: reselect proportional consequence/repair
• Π: repair rule and threshold consistency
• ℛ: restore asymmetrically burdened nodes
• Ξ: detect immunity, scapegoating, or pseudo-symmetry
• Θ: damp certainty in asymmetric narratives
• MS-Gate: block unreviewed asymmetry

Operators Contraindicated Under Low MS_index

• Γ hard selection: may select asymmetric consequence
• Π irreversible constraint: may encode unequal standards
• ⊗ deep coupling: may increase burden under low trust
• ⊕ composition: may merge unresolved asymmetry into identity
• Τ acceleration: outruns legitimacy repair
• Σ escalation: may sacralize unequal standards
• ✕ force: enforces asymmetry and deepens hidden debt

12) Gate Implications

Gates Strengthened By Reliable MS_index

• MS-Gate: direct diagnostic support for gate pass/fail
• Au-Actuation: evidence and thresholds are traceable
• FI-Gate: feedback can reveal asymmetry
• High Risk Gate: prevents high-risk binding under asymmetric thresholds
• ☷ᵢ: principle constraints are applied consistently across comparable cases

Gates Weakened If MS_index Is Poor or Unknown

If symmetry is unknown or low:

• MS-Gate should fail or require review
• Au may not reveal hidden asymmetry
• FI may receive feedback that cannot correct unequal treatment
• High Risk Gate may allow binding under rank-biased evidence
• ☷ᵢ may be applied selectively
• Π may overconstrain some nodes and underconstrain others
• Γ may select asymmetric repair or consequence
• ℛ may restore protected nodes while burdened nodes remain unrepaired

Gate Outcomes Affected

Low MS_index should push gates toward:

• Pause
• Require comparison set
• Require threshold audit
• Require rank-symmetry review
• Require appeal access review
• Require repair burden review
• Deny asymmetric consequence
• Deny precedent creation
• ∅ for high-impact action if comparable cases receive unexplained different treatment

13) Scaling Behavior

MS_index becomes harder under scale because cases multiply, discretion distributes, records fragment, and rank/power effects become easier to hide.

As systems scale:

• comparable cases become harder to compare
• exceptions multiply
• local practices diverge
• appeal access varies
• high-rank cases move into private channels
• low-rank cases remain formal and visible
• burden distribution becomes harder to trace
• credit and blame concentrate unevenly
• memory stores selective precedent
• public legitimacy depends on formal symmetry
• actual experience diverges from official standards
• feedback from affected nodes is filtered
• rule complexity hides threshold differences

Scaling Risks

• rank immunity
• asymmetric enforcement
• scapegoating
• hidden burden distribution
• appeal inequality
• repair inequality
• credit capture
• blame export
• precedent drift
• legitimacy shock
• formal equality / practical asymmetry split
• exception privilege
• unequal memory correction
• structural distrust
• selective accountability

Scaling Requirements

To scale symmetry safely, systems need:

• case comparison records
• threshold documentation
• consequence class maps
• repair access maps
• appeal access tracking
• rank/role analysis
• exception distribution audits
• burden distribution review
• affected-node cost tracking
• feedback force comparison
• public/private case comparison
• precedent memory with scope
• symmetry stress tests
• external review for high-stakes cases
• correction propagation
• routine MS-Gate sampling

Scaling Rule

Symmetry must scale with authority, consequence severity, exception access, and repair burden.

Sanity constraint:

authority ↑ ⇒ accountability threshold should not decrease

If authority rises while accountability thresholds fall, rank immunity risk increases.

Second constraint:

same effect + different consequence + weak rationale ⇒ legitimacy debt ↑

If comparable effects receive different consequences without clear rationale, hidden legitimacy debt rises.

Third constraint:

high affected_node_cost + low repair access ⇒ MS failure risk ↑

If impacted nodes carry cost without comparable repair access, symmetry degrades.

14) Interaction / Coupling Behavior

MS_index reveals whether a relation, institution, AI system, archive, or interface applies standards consistently enough for trust and repair.

What It Reveals About Coupling

• whether one node’s actions are judged differently
• whether feedback has equal force
• whether repair burden is reciprocal or one-sided
• whether boundary crossings receive equivalent interpretation
• whether exceptions are shared or privileged
• whether one node receives structural explanations while another receives blame
• whether credit and burden are distributed coherently
• whether compatibility is sustained by unequal standards

What It Reveals About Boundary Integrity

Boundary integrity requires symmetrical recognition of equivalent boundaries.

When MS_index is low:

• one node’s boundaries may count more than another’s
• refusal may be respected asymmetrically
• repair obligations may distribute unevenly
• breaches may be named differently by status
• exit and appeal may be available unevenly
• BΣ becomes rank- or role-dependent rather than principle-dependent

What It Reveals About Compatibility

Compatibility requires symmetry in standards, not identical roles.

A coupling may be unsafe if:

one node’s harm is treated as context while another’s is treated as fault

or:

one node’s repair need is urgent while another’s is optional

Healthy compatibility allows role difference without threshold distortion.

Relevant Interface Acts

• ↺ Reflection: compare standards across cases
• ⇩ Relaxation: reduce defensive asymmetry
• ⊘ Attenuation: reduce coupling while asymmetry is repaired
• ⊙ Alignment: apply standards to self before externalizing them
• →? Invitation: invite reciprocal review
• ⚕︎ Restorative Override: requires post-action MS review
• ✕ Force: dangerous when symmetry is unverified

15) Failure Modes Detected

Primary Failure Modes

MS_index detects or predicts:

• rank immunity
• scapegoating
• asymmetric enforcement
• asymmetric repair access
• appeal inequality
• threshold drift
• credit capture
• blame export
• false equivalence
• unequal boundary recognition
• selective accountability
• exception privilege
• legitimacy shock
• hidden burden distribution
• formal equality / practical asymmetry split
• memory asymmetry
• precedent distortion

Composite Regimes Where MS_index Matters

• Extraction Regime: burden and repair are asymmetrically distributed
• Goodhart Collapse: thresholds bend to preserve Φ
• LOS: latent structures decide who receives consequence
• Pseudo-Coherent Basin: unequal standards preserve apparent order
• Coercive Fusion: one node’s standards dominate the other
• Mission Lock: asymmetry is justified by trajectory
• Taboo Lock: protected nodes or meanings cannot be compared
• Repair Theater: symbolic symmetry replaces actual repair
• Crisis Loop: unequal treatment fuels recurrence and legitimacy loss

16) Accountability & Reintegration Implications

If MS_index Was Ignored

Likely consequences:

• comparable cases received unequal treatment
• high-rank nodes avoided consequence
• low-rank nodes carried blame or burden
• affected-node cost went unrepaired
• exceptions became privilege
• appeal access was unequal
• credit concentrated and blame exported
• official memory became selective
• legitimacy declined
• hidden debt accumulated around asymmetric standards

Accountability questions:

• What cases are comparable?
• What standard was applied?
• Did evidence thresholds differ?
• Did consequences differ?
• Did repair access differ?
• Did appeal access differ?
• Did rank or role change treatment?
• Was the difference justified?
• Who benefited from asymmetry?
• Who carried burden?
• Did memory preserve the asymmetry?
• Did recurrence validate the concern?

If MS_index Was Misread

Possible misread forms:

• different contexts mistaken for bias
• identical treatment mistaken for symmetry
• proportional repair mistaken for favoritism
• higher responsibility mistaken for unfair burden
• legitimate role difference mistaken for inequality
• vulnerability-sensitive repair mistaken for asymmetry
• punishment equality mistaken for repair equality
• formal same-rule application mistaken for practical fairness
• discretion mistaken for corruption without audit

Required Restoration

When MS_index failure is found:

identify comparable cases
→ map evidence thresholds
→ map consequences and repair access
→ identify rank/role effects
→ correct classification or consequence asymmetry
→ redistribute repair burden
→ update U7 precedent memory
→ validate affected-node trust

If symmetry failure caused durable labels, High Risk Gate and memory repair should review all downstream bindings.

17) Cross-Domain Examples

Technical / Engineering

A junior engineer is blamed for an outage caused by a deploy, while similar senior-level design decisions are framed as “system complexity.”

Diagnostic implication: attribution and consequence standards are rank-asymmetric.

Operator sequence: incident comparison → MS review → root-cause remap → repair release/design process → U7 postmortem correction.

Institutional / Governance

Policy violations by lower-rank staff lead to formal discipline, while similar higher-rank violations lead to coaching or private handling.

Diagnostic implication: same effect receives different consequence classes.

Operator sequence: threshold audit → consequence map → appeal review → repair harmed trust → precedent correction.

AI / Algorithmic

An AI system applies stricter safety constraints to some user categories or topics than comparable ones without clear rationale.

Diagnostic implication: classification and constraint standards may be asymmetric.

Operator sequence: case comparison audit → policy threshold review → HR/MS gate check → evaluation repair.

Interaction / Relational

One person’s boundary request is treated as valid, while the other’s equivalent boundary request is treated as avoidance or rejection.

Diagnostic implication: boundary recognition is asymmetric.

Operator sequence: ↺ compare cases → clarify boundary standard → repair asymmetry → Λ compatibility re-test.

Archive / Framework Design

One framework is promoted to canon quickly while another with similar evidence remains draft because it came from a less central thread.

Diagnostic implication: canon status thresholds are inconsistent.

Operator sequence: canon threshold audit → compare evidence → adjust status → update U7 registry memory.

18) Test Protocols

1. Comparable Case Test

Are there similar cases to compare?

Failure signal: the system refuses comparison without reason.

2. Evidence Threshold Test

Did comparable claims require comparable evidence?

Failure signal: some nodes require more proof than others.

3. Consequence Class Test

Did comparable effects receive comparable consequences?

Failure signal: consequence class shifts by rank or status.

4. Repair Access Test

Did comparable harms receive comparable repair pathways?

Failure signal: some affected nodes receive recognition or repair, others do not.

5. Appeal Access Test

Can comparable nodes challenge outcomes comparably?

Failure signal: appeal is easier for some nodes.

6. Exception Symmetry Test

Are exceptions distributed by case structure or by status?

Failure signal: exceptions cluster around protected nodes.

7. Attribution Symmetry Test

Are agency and structure applied consistently?

Failure signal: some nodes get structural explanations, others get identity blame.

8. Credit / Blame Symmetry Test

Are credit and blame assigned using comparable causal standards?

Failure signal: credit concentrates upward, blame downward.

9. Memory Symmetry Test

Are comparable cases remembered with similar durability and detail?

Failure signal: some cases become precedent while others disappear.

10. Boundary Symmetry Test

Are equivalent boundaries respected equivalently?

Failure signal: one node’s refusal counts, another’s does not.

19) Anti-Patterns

• Same rule as same burden
• Identical treatment as symmetry
• Rank as evidence
• Authority as immunity
• Discretion as fairness
• Exception as privilege
• Private consequence as equivalent consequence
• Appeal existence as appeal access
• Credit up / blame down
• Structural explanation for some, identity blame for others
• Low-rank proof burden
• High-rank benefit of doubt
• Formal equality / practical asymmetry
• Punishment symmetry as repair symmetry
• Context used only for protected nodes
• Boundary respect by status
• Memory of some cases, erasure of others
• Symmetry review treated as disloyalty
• Difference without rationale
• Sameness without proportionality

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

MS_index Meta-Symmetry Index is the diagnostic estimate of whether comparable actions, effects, harms, contributions, risks, evidence, burdens, violations, repairs, exceptions, or classifications receive comparable standards of review, consequence, repair, appeal, and memory across nodes, ranks, roles, and system positions. It does not require identical treatment; it requires principled, traceable equivalence. Low MS_index indicates risk of rank immunity, scapegoating, asymmetric enforcement, appeal inequality, repair asymmetry, credit capture, blame export, exception privilege, boundary-recognition asymmetry, legitimacy shock, and hidden debt. Under low MS_index, the system should pause consequence escalation, compare cases, audit evidence thresholds, review rank/role asymmetry, repair burden distribution, correct U7 precedent memory, and require MS-Gate review before precedent creation, punitive action, durable classification, or legitimacy claims.