1) Diagnostic Identity

Diagnostic Name: Latent Operational Structures

Short Name / Symbol: LOS

Diagnostic Class: Hidden Operations / Informal Systems / Structural Reality / Governance Drift / Coherence Audit

Primary Function: Estimate the degree to which real system behavior is being governed by hidden, informal, undocumented, unofficial, inherited, workaround-based, relationship-based, exception-based, or unacknowledged structures rather than the formal structure the system claims to operate through.

Primary Use: Determine whether the official map of the system matches the actual operating map, and whether hidden structures are supporting coherence, carrying debt, bypassing constraints, protecting immunity, or producing untraceable effects.

Core Risk if Ignored: The system may repair, govern, audit, classify, or scale based on the formal structure while the real system runs through latent pathways, causing misrepair, legitimacy shock, hidden debt accumulation, and false accountability.

Core Risk if Overtrusted: Every informal practice, tacit skill, relationship, local adaptation, or hidden support layer may be treated as suspicious, even when it is a legitimate, coherence-preserving, or necessary adaptive structure.

2) Mechanical Definition

LOS measures the hidden operating system beneath the formal operating system.

LOS answers:

What actually makes the system run, regardless of what the official structure says?

Latent Operational Structures include:

informal workflows
shadow procedures
hidden repair labor
unwritten rules
backchannel coordination
workarounds
legacy dependencies
unofficial authorities
relationship-based access
rank-based exception paths
informal escalation routes
hidden data flows
unrecorded memory
unofficial interpretation rules
practical veto points
actual decision paths

LOS is not automatically bad.

Some latent structures are adaptive, especially when formal systems are incomplete, immature, overloaded, or too brittle.

But LOS becomes risky when the latent layer:

cannot be audited
contradicts the formal system
carries hidden repair burden
creates rank immunity
bypasses boundaries
exports cost
controls decisions invisibly
prevents formal repair from reaching the real origin

A simple form:

formal structure ≠ actual operation ⇒ LOS must be mapped before repair

3) What the Diagnostic Measures

Direct Measurement Target

LOS measures:

• hidden operating pathways
• informal governance
• undocumented workflows
• unofficial decision authority
• practical veto points
• hidden repair structures
• backchannel coordination
• shadow dependencies
• informal access routes
• unrecorded escalation paths
• latent memory systems
• workaround infrastructure
• inherited operational patterns
• informal exception systems
• hidden burden distribution
• difference between formal and actual operation
• whether latent structures preserve or degrade coherence

Indirect / Proxy Signals

LOS can be estimated from:

• formal process not matching real process
• “how things actually get done” differing from documentation
• recurring workaround use
• hidden labor supporting official success
• certain people or roles quietly becoming bottlenecks
• unofficial approval paths
• undocumented exception handling
• decisions happening before formal meetings
• official records failing to explain outcomes
• repair requiring informal contacts
• new members failing because tacit rules are missing
• formal appeal existing but informal access determining success
• formal metrics missing real burden
• repeated “everyone knows” rules
• official hierarchy differing from practical authority
• repair failing because it targets formal structure only

What It Does Not Measure

LOS does not directly measure:

• whether hidden structures are corrupt
• whether informality is bad
• whether formal structure is superior
• whether tacit knowledge should be eliminated
• whether all latent structures should be exposed publicly
• whether every workaround is incoherent
• whether all undocumented practice is illegitimate
• whether official process is false by intent
• whether local adaptation is failure
• whether all hidden coordination creates harm

High LOS means actual operation diverges significantly from formal structure.

It does not automatically mean the system is incoherent.

Low LOS means formal and actual operation are more aligned.

It does not automatically mean the system is healthy if the formal structure itself is incoherent.

4) Canonical State Variables Involved

Canonical state vector:

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

Primary Variables

• Au: LOS reduces auditability when actual operation is not traceable
• H: hidden debt often lives in latent structures
• O: coherence depends on actual operation, not formal description
• R: restoration must reach latent structures if they carry real function
• BΣ: boundaries can be bypassed or protected by latent structures
• µᵢ: integrity depends on alignment between official role, actual function, and consequence

Secondary Variables

• ε: visible errors may appear in formal systems while origin sits in latent operation
• ι: pseudo-coherence rises when formal order hides latent incoherence
• K: compatibility is distorted when coupling interacts with latent rather than formal structure
• Φ: performance may depend on latent structures while metrics credit formal systems

Variables Commonly Confused With LOS

5) Localization Signature

Primary Legibility Layers

• U3 — Execution: where actual work, workarounds, handoffs, and hidden processes occur
• U5 — Coordination / Time: where informal timing, escalation, sequencing, and backchannels operate
• U7 — Memory / Recurrence: where tacit knowledge, inherited practice, and repeated unofficial patterns persist
• U2 — Configuration / Boundaries: where formal rules differ from practical permissions, access, and constraints
• U4 — Classification / Metrics / Narratives: where formal descriptions, labels, and metrics fail to reflect actual operation
• U6 — Coherence Field: where trust, legitimacy, and shared reality are shaped by the formal/actual gap

Primary Leverage Layers

• U3: map actual execution pathways
• U5: map informal coordination and escalation routes
• U7: preserve tacit knowledge and latent precedent explicitly
• U2: align formal boundaries with actual operation
• U4: correct narratives and classifications
• U6: repair trust when formal story and lived operation diverge

Verification Layers

• U3: how does work actually happen?
• U5: who actually coordinates or approves?
• U7: what practices recur outside formal memory?
• U2: do formal permissions match practical permissions?
• U4: do metrics/narratives describe real operation?
• U6: does the formal/actual gap damage legitimacy?

Common Mislocalizations

• Treating formal process as actual process
• Treating documentation as operation
• Treating official hierarchy as practical authority
• Treating hidden labor as normal efficiency
• Treating workaround use as individual noncompliance
• Treating informal repair as proof formal repair works
• Treating backchannels as harmless by default
• Treating tacit knowledge as low-value
• Treating official metrics as operational truth
• Treating latent dependency as resilience
• Treating formal appeal as actual recourse
• Treating formal boundary as practical boundary

6) Input Requirements

Required Inputs

To estimate LOS, the system needs:

• formal structure being evaluated
• actual observed operation
• recurring informal pathways
• undocumented workflows
• affected variables in S
• formal decision path
• actual decision path
• formal repair path
• actual repair path
• formal authority map
• practical authority map
• formal dependency map
• latent dependency map
• hidden labor indicators
• exception/workaround history
• affected-node feedback
• auditability of actual operation

Optional Inputs

These improve precision:

• process observations
• interviews
• incident timelines
• handoff logs
• access logs
• unofficial escalation records
• informal communication patterns
• onboarding failures
• shadow documentation
• workaround reports
• exception logs
• repair labor records
• hidden dependency analysis
• public/private narrative comparison
• formal/informal authority comparison
• recurrence records
• external audit
• historical evolution of the latent structure

Missing Input Behavior

If LOS inputs are missing:

• If actual operation is unknown, do not rely on formal structure alone
• If hidden labor is unknown, official success may be over-credited
• If actual decision path is unknown, selection traceability is incomplete
• If actual repair path is unknown, repair capacity may be misread
• If affected-node feedback is missing, latent burden may be invisible
• If workaround history is missing, formal process health is uncertain
• If practical authority is unknown, accountability may be mislocalized
• If U7 tacit memory is unknown, recurrence may be misunderstood

Default missing-input posture:

compare formal map to actual operation → identify recurring latent pathways → classify as adaptive support, hidden debt, or governance drift

7) Diagnostic States / Ranges

These ranges are qualitative and should be domain-calibrated.

Healthy / Coherence-Supporting Range

Latent structures exist but are bounded, understood, coherence-supporting, and can be brought into audit or formal repair when needed.

Signals:

• informal practices are known
• tacit knowledge can be taught
• workarounds are temporary or reviewed
• latent repair labor is acknowledged
• actual authority does not contradict accountability
• hidden dependencies are monitored
• formal systems learn from latent practice
• affected nodes can name real operation
• latent structures reduce H rather than hiding it
• U7 preserves why latent practices exist

Recommended posture:

document useful tacit structures
formalize where needed
preserve local adaptation
monitor for drift and burden export

Watch Range

Latent structures are becoming more important, but their coherence role is not yet clear.

Signals:

• workarounds increase
• informal escalation becomes common
• hidden repair labor grows
• practical authority differs from formal authority
• formal process feels slower than actual process
• onboarding depends on tacit knowledge
• exceptions cluster around informal routes
• affected nodes rely on unofficial support
• metrics miss real operation
• official repair partly depends on latent pathways

Recommended posture:

map LOS
audit hidden labor and authority
review formal/actual gaps
decide what to formalize, protect, or remove

Degraded Range

Latent structures govern significant function while remaining unaudited, burdensome, asymmetric, or contradictory to formal structure.

Signals:

• formal process is mostly symbolic
• real decisions happen elsewhere
• hidden repair labor sustains the system
• unofficial access determines outcomes
• rank or relationship controls pathways
• formal appeal does not match actual recourse
• hidden dependencies create fragility
• workarounds become infrastructure
• affected nodes carry cost of the formal/actual gap
• accountability cannot reach actual operators

Recommended posture:

pause formal-only repair
activate Au / Ξ review
map actual operating system
repair hidden burden
align formal structure with real operation

Contraindicated:

scaling formal process
declaring process health from documentation
punishing workaround users without repairing cause
closure from formal compliance

Critical / Collapse-Prone Range

Latent structures have replaced or captured the formal operating system, creating major hidden debt, immunity, or legitimacy risk.

Signals:

• official process no longer governs real outcomes
• shadow authority controls decisions
• formal accountability cannot reach actual power
• hidden workflows are required for survival
• public narrative is materially false
• external audit would reveal major gap
• repair cannot proceed without exposing LOS
• hidden dependencies threaten collapse
• legitimacy depends on not naming actual operation
• latent structure has become regime-level

Recommended posture:

preserve evidence
freeze expansion based on formal map
reconstruct actual operating system
activate independent Au / MS / Ξ review
repair hidden debt and authority gaps
correct U7 and public narrative

False Positive Risk

LOS may appear dangerous when:

• informal practice is legitimate expertise
• tacit knowledge is normal and teachable
• local adaptation preserves coherence
• formalization would destroy flexibility
• hidden structure exists for safety or privacy
• temporary workaround is reviewed and bounded
• informal repair supplements formal repair without replacing it
• formal structure is intentionally minimal

False Negative Risk

LOS may appear harmless when:

• informal pathways are normalized
• hidden labor is culturally expected
• outcomes are good in the short term
• official metrics improve
• affected nodes stop reporting burden
• newcomers fail silently
• practical authority is socially invisible
• workarounds are called efficiency
• hidden dependencies have not yet failed
• formal process survives because latent process carries it

8) Leading Indicators

LOS degradation appears early as:

• “that is not how it really works” becomes common
• workarounds repeat
• documentation fails newcomers
• informal escalation is faster than formal escalation
• hidden repair labor grows
• certain people become unofficial bottlenecks
• official meetings ratify decisions already made elsewhere
• formal appeals rarely change outcomes
• tacit rules decide access
• practical authority diverges from role authority
• exceptions become social rather than procedural
• metrics cannot explain lived operation
• formal process is followed only for recordkeeping
• affected nodes rely on private channels

9) Lagging Indicators

LOS failure has already accumulated debt when:

• formal process collapses under stress
• hidden dependencies fail
• external audit reveals shadow operation
• official memory is rejected
• hidden labor withdraws and system stops functioning
• legitimacy shock occurs
• repair cannot identify real cause
• formal accountability targets the wrong node
• unofficial authority becomes visible during crisis
• workarounds become unmaintainable
• public narrative requires major correction
• system must rebuild formal structure around actual practice

10) Interpretation Rules

How to Read LOS

LOS should be read as:

degree and consequence of formal/actual operating divergence

It is not a moral judgment on informality.

A system may have:

• high LOS and high coherence if latent structures are adaptive, bounded, and auditable
• high LOS and low coherence if latent structures hide debt or immunity
• low LOS and low coherence if formal system itself is brittle
• low LOS and high coherence if formal system reflects real operation
• high beneficial tacit knowledge and low governance drift
• high hidden authority and high legitimacy risk
• low visible LOS but high hidden dependency

What Changes Its Meaning

LOS changes meaning under:

• low Au_eff
• high exception_rate
• high immunity_index
• low MS_symmetry_index
• high repair_burden_distribution asymmetry
• high affected_node_cost
• high narrative_metric_gap
• high pseudo_damping_risk
• low FI_integrity
• low EB
• low L₀(t)
• high legitimacy_shock_risk
• high dependency_load
• high boundary_strain
• low M_int(t)

Context Modifiers

Low Au_eff: latent structures become untraceable.

High exception_rate: repeated exceptions may be latent governance.

High immunity: LOS may protect cause-bearing nodes.

Low MS: latent structures may distribute standards asymmetrically.

Repair burden asymmetry: LOS may hide who repairs.

High affected-node cost: latent operation may export cost.

Narrative gap: formal story may diverge from actual function.

Low FI: feedback cannot correct latent structures.

Low L₀(t): exposure of LOS may create legitimacy shock.

Domain Calibration Notes

LOS should be calibrated by domain:

• in engineering: undocumented scripts, tribal knowledge, shadow deploy paths, hidden dependencies, unofficial owners
• in AI: hidden prompt/tool/memory dependencies, informal eval practices, unrecorded policy interpretation, undocumented agent routing
• in institutions: informal authority, backchannel approvals, shadow staffing, undocumented complaint pathways, invisible repair labor
• in governance: informal enforcement discretion, hidden veto points, patronage networks, administrative workarounds, emergency practices
• in relationships: unspoken rules, hidden labor, tacit repair expectations, unofficial authority patterns
• in archives: undocumented canon rules, tacit naming conventions, hidden dependency chains, unrecorded source hierarchy

11) Operator Sequencing Implications

If LOS Is Healthy / Adaptive

Allowed with ordinary gate checks:

• Μ can incorporate latent structure into model
• Γ can decide whether to formalize, preserve, or leave tacit
• Π can protect useful informal pathways
• ℛ can use latent repair knowledge
• U7 can store tacit knowledge with provenance
• Δ can test formal/actual alignment
• scaling may proceed if latent dependencies are visible

Recommended:

map LOS → classify adaptive vs debt-bearing → preserve or formalize → update U7 → monitor drift

If LOS Is Degraded

Recommended:

pause formal-only action → map actual operations → audit hidden authority/labor/dependencies → repair formal/actual gap

Or:

separate adaptive tacit knowledge from hidden governance → formalize only what must be accountable

Avoid or delay:

• scaling formal process
• punishing workaround users before repairing cause
• closure from formal compliance
• relying on official hierarchy
• treating documentation as reality
• canonizing formal structure without LOS audit
• high-impact action based on formal map only

Operators Recommended Under Degraded LOS

• Au: reconstruct actual operating pathways
• Ξ: detect pseudo-formal coherence
• Μ: model formal/actual gap
• Γ: select which latent structures to preserve, formalize, repair, or remove
• Π: align boundaries and authority
• ℛ: repair hidden burden and dependencies
• MS-Gate: review asymmetry in latent operation
• Ψ: attend to affected-node lived operation

Operators Contraindicated Under Degraded LOS

• Γ hard selection from formal map: selects from false model
• Π formal constraint expansion: may miss real operation
• ⊗ deep coupling: spreads hidden debt
• ⊕ composition: embeds latent incoherence
• Τ acceleration: scales unmapped operation
• Σ escalation: sacralizes formal fiction
• ✕ force: may punish visible symptoms while preserving hidden cause

12) Gate Implications

Gates Strengthened By Reliable LOS Reading

• Au-Actuation: actual operation becomes traceable
• FI-Gate: feedback can reveal formal/actual gaps
• High Risk Gate: blocks high-risk binding from formal-map-only evidence
• MS-Gate: detects asymmetry in hidden operation
• ☷ᵢ: prevents principle language from covering latent incoherence

Gates Weakened If LOS Is Poorly Known

If LOS is unknown:

• Au may audit the wrong system
• FI may not reach actual decision pathways
• High Risk Gate may bind classifications from incomplete maps
• MS may miss hidden privilege or burden
• ☷ᵢ may validate formal principle while latent practice violates it
• Π may constrain the wrong layer
• Γ may select ineffective repair
• ℛ may target official process while hidden process persists

Gate Outcomes Affected

High or unmapped LOS should push gates toward:

• Pause formal-only closure
• Require actual-operation map
• Require hidden labor review
• Require practical authority review
• Require workaround audit
• Require affected-node validation
• Deny formal-process success claims
• Deny scaling
• ∅ for high-impact action based only on official structure when actual operation is unknown

13) Scaling Behavior

LOS becomes harder to control under scale because informal structures multiply, local adaptations diverge, and tacit knowledge fragments.

As systems scale:

• local workarounds proliferate
• hidden dependencies multiply
• practical authority diverges from formal hierarchy
• hidden labor becomes infrastructure
• onboarding gaps grow
• documentation lags operation
• exception systems become informal
• repair happens through relationships
• formal metrics miss operational reality
• public narrative becomes less accurate
• latent structures protect or burden specific nodes
• formal reform fails because it does not reach actual operation
• exposure risk increases

Scaling Risks

• shadow governance
• hidden labor collapse
• audit failure
• formal/informal split
• latent dependency cascade
• practical immunity
• repair mislocalization
• legitimacy shock
• public/private narrative divergence
• workaround institutionalization
• tacit knowledge loss
• operational fragility
• governance capture
• pseudo-compliance
• official-memory distortion

Scaling Requirements

To scale LOS safely, systems need:

• formal/actual process comparison
• hidden labor tracking
• workaround logs
• tacit knowledge capture
• practical authority maps
• exception pathway audit
• latent dependency maps
• affected-node validation
• onboarding failure analysis
• documentation freshness checks
• repair-path mapping
• public/private narrative comparison
• U7 operational memory
• periodic LOS audits
• external review triggers
• formalization criteria

Scaling Rule

Formal structure may scale only as far as it matches actual operation or explicitly accounts for latent operation.

Sanity constraint:

formal_map_accuracy ↓ + scale ↑ ⇒ misrepair risk ↑

If the formal map is inaccurate and the system scales, repair and governance increasingly target the wrong structure.

Second constraint:

LOS ↑ + Au_eff ↓ ⇒ hidden governance risk ↑

If latent structures are high and auditability is low, shadow governance risk rises.

Third constraint:

LOS ↑ + hidden_repair_labor ↑ ⇒ repair theater risk ↑

If official repair depends on hidden labor, visible repair claims may be misleading.

14) Interaction / Coupling Behavior

LOS reveals whether a coupling is interacting with the formal system or the real system.

What It Reveals About Coupling

• whether the coupling depends on unofficial pathways
• whether one node must learn hidden rules to function
• whether formal compatibility differs from actual compatibility
• whether repair uses official or latent pathways
• whether hidden dependencies transmit debt
• whether trust rests on people rather than structures
• whether exit or appeal is formal only
• whether one node’s actual operating system is invisible to the other

What It Reveals About Boundary Integrity

Latent structures often bypass or substitute for formal boundaries.

When LOS is high:

• practical permissions may differ from formal permissions
• actual access may be relationship-based
• refusal may be bypassed informally
• hidden labor may maintain boundaries
• BΣ may depend on tacit norms
• official boundary repair may fail because actual boundary is elsewhere

What It Reveals About Compatibility

Compatibility requires actual-operation compatibility, not only formal compatibility.

A coupling may be unsafe if:

the formal interface is compatible but the latent operating system is not

or:

one node depends on hidden rules the other cannot see, audit, or repair

Healthy compatibility can include tacit structure, but it must remain teachable, bounded, and repairable.

Relevant Interface Acts

• ↺ Reflection: compare formal story to actual operation
• ⇩ Relaxation: reduce pressure so hidden operation can be named
• ⊘ Attenuation: reduce coupling while LOS is mapped
• ⊙ Alignment: clarify actual self-operation before coupling
• →? Invitation: invite disclosure of practical pathways without punishment
• ⚕︎ Restorative Override: requires post-action LOS review
• ✕ Force: often drives LOS deeper underground

15) Failure Modes Detected

Primary Failure Modes

LOS detects or predicts:

• shadow governance
• hidden labor
• practical immunity
• audit failure
• hidden dependency
• formal/informal split
• workaround infrastructure
• repair mislocalization
• practical authority drift
• appeal theater
• false process compliance
• official-memory distortion
• onboarding failure
• tacit-rule capture
• exception privilege
• public/private narrative divergence
• latent burden export
• legitimacy shock after exposure

Composite Regimes Where LOS Matters

• Pseudo-Coherent Basin: latent operation sustains apparent formal order
• Repair Theater: formal repair depends on hidden repair labor
• Extraction Regime: hidden labor or informal routes carry exported cost
• Goodhart Collapse: formal metrics miss latent operation
• Mission Lock: latent workarounds preserve trajectory
• Taboo Lock: latent structures exist because formal truth cannot be named
• Coercive Fusion: hidden dependencies bind nodes beyond formal terms
• Crisis Loop: formal repairs fail because latent causes persist
• Compression Collapse: formal options shrink while latent options govern reality

16) Accountability & Reintegration Implications

If LOS Was Ignored

Likely consequences:

• repair targeted formal process while actual process persisted
• hidden labor went unacknowledged
• practical authority avoided accountability
• affected nodes carried tacit burden
• workarounds became infrastructure
• formal appeal failed to reach real decision-makers
• official memory misrepresented operation
• hidden dependencies caused failure
• legitimacy shock occurred after exposure
• formal scaling amplified hidden debt

Accountability questions:

• What was the formal process?
• What was the actual process?
• Who actually decided?
• Who actually repaired?
• Who carried hidden labor?
• What unofficial pathway mattered?
• Did formal appeal reach practical authority?
• Did documentation match operation?
• Did hidden structures preserve coherence or hide debt?
• Who benefited from the formal/actual gap?
• Who carried the cost?

If LOS Was Misread

Possible misread forms:

• tacit expertise mistaken for corruption
• local adaptation mistaken for hidden governance
• bounded workaround mistaken for systemic failure
• privacy-preserving process mistaken for shadow authority
• informal repair mistaken for illegitimacy
• formalization assumed to be automatically better
• hidden support treated as suspicious rather than under-acknowledged
• unofficial communication mistaken for bypass without checking function
• transparency demand damaging necessary protected pathways

Required Restoration

When LOS failure is found:

map formal and actual operation
→ identify latent authority, labor, dependency, and memory
→ classify each latent structure as adaptive, debt-bearing, or governance-distorting
→ formalize, protect, repair, or remove as appropriate
→ correct U7 memory and public narrative
→ validate with affected-node experience

If LOS produced asymmetric burden or immunity, MS-Gate should review who had access, who carried hidden labor, who could bypass, and who could not.

17) Cross-Domain Examples

Technical / Engineering

A deployment process is documented, but releases actually depend on one senior engineer’s undocumented scripts and judgment.

Diagnostic implication: formal deployment process hides a latent operational structure.

Operator sequence: script/process audit → document tacit pathway → distribute ownership → create fallback → U7 operational memory.

Institutional / Governance

A complaint process exists formally, but outcomes depend on who knows an informal escalation contact.

Diagnostic implication: formal appeal access is lower than practical backchannel access.

Operator sequence: practical pathway map → appeal repair → MS review → public process correction.

AI / Algorithmic

An AI safety workflow appears policy-driven, but actual outcomes depend on undocumented prompt conventions, hidden tool routing, or informal reviewer norms.

Diagnostic implication: policy layer is not the full operating system.

Operator sequence: trace actual routing → document hidden conventions → eval alignment → memory/policy update.

Interaction / Relational

A relationship claims decisions are mutual, but in practice one person’s preferences set the default unless explicitly challenged.

Diagnostic implication: latent authority structure governs beneath formal mutuality.

Operator sequence: ↺ compare formal/actual decision pattern → rebalance authority → repair boundary memory.

Archive / Framework Design

The archive claims concepts become canon through criteria, but in practice central-thread familiarity determines canon readiness.

Diagnostic implication: latent canon-selection pathway differs from formal canon criteria.

Operator sequence: canon decision audit → selection trace repair → source-neutral criteria → U7 status update.

18) Test Protocols

1. Formal/Actual Map Test

Does the formal map match actual operation?

Failure signal: work happens through pathways not shown in the map.

2. Hidden Labor Test

Who performs work not visible in official records?

Failure signal: official success depends on unacknowledged labor.

3. Practical Authority Test

Who actually decides?

Failure signal: decision authority differs from formal role.

4. Workaround Test

What workarounds are recurring?

Failure signal: workaround is no longer temporary.

5. Appeal Reality Test

Does formal appeal reach actual decision-makers?

Failure signal: appeal pathway is formal while recourse is informal.

6. Onboarding Test

Can newcomers function from documentation alone?

Failure signal: tacit rules are required but unrecorded.

7. Repair Path Test

Where does repair actually happen?

Failure signal: official repair path differs from real repair path.

8. Dependency Test

What hidden dependencies support formal function?

Failure signal: dependency failure would surprise the formal system.

9. Narrative Test

Does the official story match lived operation?

Failure signal: affected nodes describe a different operating system.

10. Stress Test

What latent structures appear under stress?

Failure signal: crisis reveals real authority, dependency, or workflow hidden during normal operation.

19) Anti-Patterns

• Documentation as operation
• Formal hierarchy as practical authority
• Workaround as efficiency
• Hidden labor as normal
• Informal access as fairness
• Formal appeal as actual recourse
• Backchannel as harmless by default
• Tacit knowledge as low-value
• Public process as real process
• Metrics as operational truth
• Local adaptation as noncompliance
• Shadow repair as proof formal repair works
• Unofficial bottleneck as expertise only
• Formal compliance as coherence
• Newcomer failure as incompetence
• Latent dependency as resilience
• Official memory as actual memory
• Repair without LOS audit
• Scaling formal map over actual system
• Force driving latent operation underground

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

LOS Latent Operational Structures is the diagnostic estimate of the degree to which real system behavior is governed by hidden, informal, undocumented, inherited, relationship-based, exception-based, workaround-based, or unacknowledged structures rather than the formal structure the system claims to operate through. It does not treat all informality as incoherent; tacit knowledge and local adaptation can preserve coherence when bounded, teachable, and auditable. High or degraded LOS indicates risk of shadow governance, hidden labor, practical immunity, formal/informal split, repair mislocalization, hidden dependency, appeal theater, public/private narrative divergence, official-memory distortion, and legitimacy shock. Under high LOS, the system should pause formal-only repair, map actual operation, identify latent authority/labor/dependency/memory, classify latent structures as adaptive or debt-bearing, repair formal/actual gaps, update U7 memory, and validate with affected-node experience before scaling, closure, or high-impact action based on the formal map.