Understanding Negative, Neutral, and Positive Lattice in Defence

Classical baseline

Classically, war is organised armed conflict between political communities, and defence is the protection of territory, people, institutions, and strategic continuity against external attack. In ordinary language, a defence system is judged by readiness, deterrence, command, logistics, training, morale, and the ability to survive first contact and continue operating. That baseline fits eduKateSG’s broader treatment of security as a continuity-and-boundary function rather than merely a collection of weapons. (edukatesg.com)

Start Here: https://edukatesg.com/civos-runtime-negative-equilibrium-and-positive-lattices-the-corridor-stack-runtime-for-problem-to-solution-routing/ + https://edukatesg.com/war-os-starter-kit-almost-code-civos-spine-negative-atlas-module-v1-0/

One-sentence definition

The Negative, Neutral and Positive Lattice for War and Defence classifies whether a military-security system is collapsing under pressure, merely holding a fragile line, or sustaining a stable defence corridor in which deterrence, readiness, command, logistics, buffers, and repair remain stronger than hostile disruption. This is an extension of eduKateSG’s tri-band lattice logic into the war-and-defence lane. (edukatesg.com)

Core distinction: war versus defence

In this framing, war is the high-load collision event, while defence is the sustaining architecture that prevents hostile force from deleting nodes, corridors, and institutions faster than the system can absorb and repair. That matches eduKateSG’s view that war is one lattice effect among others, and that security is fundamentally about keeping violence below collapse thresholds and preserving safe operating space across time. (edukatesg.com)

1. Negative Lattice for War and Defence

A system is in Negative Lattice when the defence structure is no longer keeping up with threat, load, and drift. Signals still exist on paper, but the live corridor is breaking: readiness is thin, command is slow or confused, logistics are brittle, doctrine is stale, reserve depth is weak, and local shocks begin cascading upward. In eduKateSG language, this is the active failure band where repair is not yet dominant and time-window compression makes reversal harder. (edukatesg.com)

In practical war terms, Negative Lattice often looks like:

late mobilisation
false confidence from drills that do not match reality
poor centre-edge coordination
broken supply or reinforcement corridors
overextended fronts
weak civil-military buffering
rising decision errors as time-to-node shrinks

That is consistent with eduKateSG’s repeated emphasis that systems fail when drift outruns repair, buffers thin, and response routes are no longer protected. (edukatesg.com)

A useful alignment point is eduKateSG’s Singapore 1942 case, which it treats as a classic rapid collapse under load rather than a simple one-variable failure. That is exactly what a war-time Negative Lattice is: many connectors failing at once faster than correction can respond. (edukatesg.com)

2. Neutral Lattice for War and Defence

A system is in Neutral Lattice when it is not collapsing immediately, but its hold is conditional and narrow. The line is stabilised, deterrence may still partly work, command may still function, and the force can absorb limited shocks, but the envelope is not wide. A stronger enemy, a longer campaign, or a second simultaneous stressor could still push it downward. This matches eduKateSG’s description of Neutral Lattice as a bridge band rather than a true stable end-state. (edukatesg.com)

Neutral Lattice defence usually has:

some usable readiness
enough doctrine to function
partial logistics continuity
working but not deep reserves
local tactical competence
incomplete strategic depth
survivability for a limited window

This is the “hold, but do not overclaim” state. The system has not lost the route, but it has not yet widened it into a strong corridor. (edukatesg.com)

3. Positive Lattice for War and Defence

A system is in Positive Lattice when the defence architecture is genuinely constructive and self-preserving under load. Deterrence is credible, readiness is real, reserves exist before crisis, command is clear, logistics continue under stress, replacement pipelines are active, and civilisational continuity is protected while force is being spent. That strongly matches eduKateSG’s Security OS and National Service OS framing: execution spends readiness, while regeneration ensures the system does not start from zero when reality strikes. (edukatesg.com)

Positive Lattice defence is not simply “having a strong army.” It means:

the enemy must calculate real cost
the state can absorb first contact without systemic panic
reinforcement and resupply still work
doctrine matches actual terrain and threat
operators, institutions, and society are coupled enough to keep functioning
repair remains faster than attrition over the relevant campaign horizon

This fits eduKateSG’s wider mega-lattice rule that stability depends on preserving connectors across Z-levels, across time, and across major civilisational pillars, including security, logistics, governance, standards, memory, and human replacement capacity. (edukatesg.com)

The real mechanisms

Deterrence

A defence system begins upstream. If credible cost is visible, many threats are suppressed before live collision. This aligns with eduKateSG’s security-lattice ordering, where deterrence precedes policing, justice, and containment. By extension, military defence is the outer hard-power version of the same logic. (edukatesg.com)

Readiness and buffers

eduKateSG’s NS OS page is especially useful here: it treats readiness not as a ceremony but as a distributed human, temporal, cognitive, and institutional buffer created before crisis. That idea ports directly into war-and-defence lattice classification. Positive systems have prebuilt buffers; negative ones try to improvise them too late. (edukatesg.com)

Command clarity

A defence lattice cannot hold if signals are delayed, contradictory, or politically distorted. The control-tower logic on eduKateSG repeatedly treats route-reading, threat detection, and repair sequencing as central; war simply compresses those requirements under lethal time pressure. (edukatesg.com)

Logistics and sustainment

War is not won by contact alone. A force that cannot feed, fuel, rotate, reinforce, repair, and replace is often only performing a temporary display of strength. That follows directly from eduKateSG’s recurring claim that civilisation survives by preserving corridors, not by surface appearances. (edukatesg.com)

Human regeneration

Positive defence requires replacement and continuity of capable people, not just equipment stock. eduKateSG is explicit that civilisation is ultimately carried by humans who can learn, judge, maintain, coordinate, and replace roles, and that NS OS exists as a security regeneration layer. (edukatesg.com)

How it breaks

War-and-defence systems usually slide downward through a recognisable sequence: threat underread -> readiness hollowing -> doctrine lag -> buffer thinning -> logistics strain -> command overload -> local breach -> corridor rupture -> wider systemic panic. That sequence is an inference from eduKateSG’s drift/repair logic, its protection-corridor framing, and its fast-attrition collapse model. (edukatesg.com)

The most dangerous trap is false recovery: the system looks better because of peacetime order, parade readiness, narrow drills, or one local success, but the wider invariants are still broken. eduKateSG explicitly warns about false recovery in its lattice diagnostics, and the warning applies cleanly to defence. (edukatesg.com)

How to optimise and repair

The upward route is:

Negative Lattice -> Neutral Lattice -> Positive Lattice

That does not happen by slogans. It happens by restoring structural validity in order:

protect core corridors,
stop the accelerating breach,
rebuild command clarity,
restore logistics and reinforcement,
widen reserve/readiness buffers,
retrain doctrine against real threat conditions,
re-couple military execution with national regeneration.

That sequence is consistent with eduKateSG’s APRC / FenceOS / ChronoHelmAI style of truncating accelerating failure, protecting thresholds, then stitching the system back into a safer line. (edukatesg.com)

Canonical lock

Negative Lattice for War and Defence = the defence system is spending readiness faster than it can regenerate, with command, logistics, deterrence, and buffer integrity falling below live threat load.
Neutral Lattice for War and Defence = the system is holding a narrow survivability line, but remains vulnerable to prolonged or compounded stress.
Positive Lattice for War and Defence = deterrence, readiness, doctrine, logistics, command, reserves, and repair remain stronger than hostile disruption across the relevant campaign horizon. (edukatesg.com)

Almost-Code block

			
TITLE: Negative, Neutral and Positive Lattice for War and Defence
CLASSICAL BASELINE:
War = organised armed conflict under political command.
Defence = protection of territory, people, institutions, and continuity against external force.
EDUKATESG ALIGNMENT:
- Negative Lattice (LNEG) = active sub-threshold failure band
- Neutral Lattice (LNEU) = stabilisation bridge band
- Positive Lattice (LPOS) = stable constructive band
- War = violent collision between separated lanes under pressure
- Security OS = execution layer that spends readiness in real time
- NS OS = regeneration/readiness layer that creates distributed buffers
ONE-SENTENCE DEFINITION:
The War and Defence Lattice classifies whether a military-security system is collapsing under hostile load, holding a narrow survivability line, or sustaining a stable defence corridor in which readiness, deterrence, logistics, command, and repair remain stronger than disruption.
STATE MODEL:
State = Threat × Z × P × LBand × Readiness × Deterrence × Command × Logistics × Buffer × Doctrine × Repair
LATTICE BANDS:
1. NEGATIVE LATTICE / LNEG
Definition:
Defence structure is no longer keeping up with live threat, drift, and campaign load.
Signs:
- late or weak mobilisation
- brittle logistics
- command confusion
- reserve depth too thin
- doctrine mismatch
- local breaches cascade upward
- false confidence from surface readiness
Law:
AttritionRate > RepairRate
ThreatLoad > CorridorCapacity
DecisionTime shrinking while exit apertures close
2. NEUTRAL LATTICE / LNEU
Definition:
The system is stabilised enough to avoid immediate collapse, but its envelope is narrow and conditional.
Signs:
- line holds under limited stress
- some deterrence remains
- partial logistics continuity
- tactical competence present
- strategic depth incomplete
- prolonged conflict could break the hold
Law:
RepairRate ≈ AttritionRate
Corridor survives, but with low margin
3. POSITIVE LATTICE / LPOS
Definition:
The defence system sustains a real protective corridor across time under load.
Signs:
- credible deterrence
- real readiness before crisis
- clear command routing
- logistics hold under pressure
- reserves and replacements exist
- doctrine matches actual threat
- society remains coupled to regeneration
Law:
RepairRate > AttritionRate
Readiness + Logistics + Command + Buffer > ThreatLoad over campaign horizon
CORE MECHANISMS:
- deterrence
- readiness buffers
- doctrine validity
- command clarity
- logistics continuity
- reserve regeneration
- civil-military coupling
- repair sequencing
FAILURE TRACE:
Threat underread
-> readiness hollowing
-> doctrine lag
-> buffer thinning
-> logistics strain
-> command overload
-> local breach
-> corridor rupture
-> wider systemic instability
REPAIR ROUTE:
Negative -> Neutral -> Positive
REPAIR ORDER:
1. protect core corridors
2. truncate accelerating breach
3. restore command clarity
4. restore logistics and reinforcement
5. rebuild readiness buffers
6. retrain doctrine to live threat
7. reconnect execution to regeneration
CANONICAL LOCK:
War is the collision event.
Defence is the continuity architecture.
A strong defence lattice prevents hostile force from deleting nodes faster than the civilisation can absorb, replace, and repair them.

		

Use this as the bottom insert. It is a maximal-but-usable lattice code registry for the War and Defence article, so you can trim later if needed.

			
TITLE: War and Defence Lattice Code Registry
TYPE: Almost-Code
ROOT: WDEF
ALIAS: WARDEF
VERSION: v1.0
# =========================================================
# 1. MASTER NAMESPACE
# =========================================================
WDEF = War and Defence lattice namespace
WDEF.CLASS = War and Defence
WDEF.FUNCTION = preserve territory, people, institutions, corridors, and civilisational continuity under hostile load
WDEF.CORELAW = defence holds when repair + readiness + logistics + command + deterrence remain stronger than disruption over time
# =========================================================
# 2. ZOOM CODES
# =========================================================
WDEF.Z0 = individual operator / soldier / pilot / sailor / defender
WDEF.Z1 = squad / crew / team / vehicle unit
WDEF.Z2 = platoon / company / battery / ship section / tactical formation
WDEF.Z3 = battalion / brigade / wing / flotilla / theatre formation
WDEF.Z4 = service branch / joint force / operational command
WDEF.Z5 = national defence system / state security architecture
WDEF.Z6 = alliance / coalition / geopolitical defence envelope
# =========================================================
# 3. PHASE CODES
# =========================================================
WDEF.P0 = collapse / non-holding state / corridor failure
WDEF.P1 = fragile activation / emergency hold / unstable mobilisation
WDEF.P2 = functional defence / partial survivability / narrow hold
WDEF.P3 = stable defence corridor / resilient continuity under load
WDEF.P4 = optional frontier surplus / strategic overmatch / bounded projection corridor
# =========================================================
# 4. LATTICE BAND CODES
# =========================================================
WDEF.LNEG = Negative Lattice / active failure band
WDEF.LNEU = Neutral Lattice / stabilisation bridge band
WDEF.LPOS = Positive Lattice / stable constructive band
WDEF.LNEG.1 = early drift / underread threat / weak preparedness
WDEF.LNEG.2 = active breach / local breakdown / degrading control
WDEF.LNEG.3 = cascade risk / corridor rupture / collapse onset
WDEF.LNEU.1 = shaky hold / temporary stabilisation
WDEF.LNEU.2 = conditional survivability / recoverable line
WDEF.LNEU.3 = narrow corridor hold / limited resilience
WDEF.LPOS.1 = credible hold / real readiness
WDEF.LPOS.2 = resilient defence corridor / absorb-and-repair capacity
WDEF.LPOS.3 = strong deterrence + sustained continuity + depth
WDEF.LPOS.4 = bounded strategic overmatch / P4-edge defence surplus
# =========================================================
# 5. CORE STATE VARIABLE CODES
# =========================================================
WDEF.THR = ThreatLoad
WDEF.TYP = ThreatType
WDEF.DTR = DeterrenceStrength
WDEF.RDY = ReadinessLevel
WDEF.MOB = MobilisationCapacity
WDEF.CMD = CommandClarity
WDEF.C2  = CommandAndControlIntegrity
WDEF.SIG = SignalQuality
WDEF.NOI = NoiseLevel
WDEF.TCL = TruthClarity
WDEF.INT = IntelligenceQuality
WDEF.ISR = IntelligenceSurveillanceReconnaissance
WDEF.DOC = DoctrineValidity
WDEF.LOG = LogisticsContinuity
WDEF.SUP = SupplyRate
WDEF.ROT = RotationCapacity
WDEF.RPL = ReplacementCapacity
WDEF.RES = ReserveDepth
WDEF.BUF = BufferDepth
WDEF.RPR = RepairRate
WDEF.ATR = AttritionRate
WDEF.MRL = MoraleIntegrity
WDEF.DIS = DisciplineIntegrity
WDEF.CIV = CivilMilitaryCoupling
WDEF.IND = IndustrialSupport
WDEF.INF = InfrastructureIntegrity
WDEF.COM = CommunicationsIntegrity
WDEF.CYB = CyberIntegrity
WDEF.AIR = AirLaneIntegrity
WDEF.SEA = SeaLaneIntegrity
WDEF.LND = LandLaneIntegrity
WDEF.SPC = SpaceSupportIntegrity
WDEF.INFOW = InformationWarfareIntegrity
WDEF.LEG = PoliticalLegitimacy
WDEF.WIL = StrategicWill
WDEF.ALL = AllianceSupport
WDEF.GEN = RegenerationCapacity
# =========================================================
# 6. TIME-TO-NODE / ROUTE COMPRESSION CODES
# =========================================================
WDEF.TTC = TimeToCriticalNode
WDEF.APR = ExitAperture
WDEF.REV = ReversalCapacity
WDEF.TDB = TimeDebt
WDEF.NCMP = NearNodeCompression
WDEF.RTE = RouteViability
WDEF.OPT = Optionality
WDEF.ESC = EscalationRisk
# =========================================================
# 7. THREAT TYPE CODES
# =========================================================
WDEF.TYP.CONV = conventional armed threat
WDEF.TYP.HYB  = hybrid threat
WDEF.TYP.CYB  = cyber threat
WDEF.TYP.INFO = information / narrative attack
WDEF.TYP.TERR = terror / irregular violence
WDEF.TYP.MAR  = maritime pressure
WDEF.TYP.AIR  = air / missile threat
WDEF.TYP.GREY = grey-zone pressure
WDEF.TYP.INT  = internal destabilisation
WDEF.TYP.MULTI = multi-domain compound threat
# =========================================================
# 8. LANE / DOMAIN CODES
# =========================================================
WDEF.LANE.LND = land domain
WDEF.LANE.SEA = sea domain
WDEF.LANE.AIR = air domain
WDEF.LANE.CYB = cyber domain
WDEF.LANE.SPC = space domain
WDEF.LANE.INFO = information domain
WDEF.LANE.CIV = civil resilience lane
WDEF.LANE.IND = industrial sustainment lane
WDEF.LANE.LOG = logistics lane
WDEF.LANE.INT = intelligence lane
# =========================================================
# 9. READINESS / DEFENCE POSTURE CODES
# =========================================================
WDEF.POST.GREEN = stable peacetime posture
WDEF.POST.WATCH = elevated watch posture
WDEF.POST.AMBER = rising threat / pre-mobilisation
WDEF.POST.RED = live crisis / active defence
WDEF.POST.BLACK = severe breach / continuity threat
WDEF.READ.0 = hollow readiness / ceremonial only
WDEF.READ.1 = nominal readiness / partial response
WDEF.READ.2 = operational readiness / short-window hold
WDEF.READ.3 = resilient readiness / sustained response
WDEF.READ.4 = high-depth readiness / multi-domain hold
# =========================================================
# 10. COLLAPSE MODE CODES
# =========================================================
WDEF.COLL.AMP = amplitude collapse / sudden shock overload
WDEF.COLL.SLO = slow attrition collapse / hollowing over time
WDEF.COLL.FAS = fast attrition collapse / rapid spend without repair
# =========================================================
# 11. BREACH REGISTRY CODES
# =========================================================
WDEF.BR = breach
WDEF.BR.CMD = command breach
WDEF.BR.C2 = command-and-control breach
WDEF.BR.LOG = logistics breach
WDEF.BR.INT = intelligence breach
WDEF.BR.DOC = doctrine mismatch breach
WDEF.BR.RES = reserve depletion breach
WDEF.BR.BUF = buffer exhaustion breach
WDEF.BR.CIV = civil-military decoupling breach
WDEF.BR.CYB = cyber breach
WDEF.BR.COM = communications breach
WDEF.BR.INF = infrastructure breach
WDEF.BR.LND = land corridor breach
WDEF.BR.SEA = sea corridor breach
WDEF.BR.AIR = air corridor breach
WDEF.BR.INFO = information environment breach
WDEF.BR.LEG = legitimacy breach
WDEF.BR.MRL = morale breach
WDEF.BR.ALL = alliance support breach
WDEF.BR.RTE = route viability breach
# =========================================================
# 12. HARD-FAIL CODES
# =========================================================
WDEF.HF.CMD = command floor lost
WDEF.HF.LOG = logistics floor lost
WDEF.HF.BUF = buffer floor lost
WDEF.HF.RPR = repair floor lost
WDEF.HF.APR = exit aperture too narrow
WDEF.HF.TTC = insufficient decision time
WDEF.HF.CIV = civil continuity threatened
WDEF.HF.GEN = regeneration floor lost
# =========================================================
# 13. FENCE / VERIFICATION / LEDGER CODES
# =========================================================
WDEF.FENCE = bounded safety / continuity threshold
WDEF.FENCE.OK = corridor inside safe threshold
WDEF.FENCE.WARN = corridor narrowing
WDEF.FENCE.BREACH = threshold crossed
WDEF.FENCE.FAIL = hard failure / unsafe continuation
WDEF.VW = VeriWeft / verification layer
WDEF.VW.PASS = validated under load
WDEF.VW.WARN = partial validation / needs recheck
WDEF.VW.FAIL = failed under load
WDEF.VW.FALSEPOS = apparent readiness but not real
WDEF.VW.FALSEHOLD = apparent hold masking deeper weakness
WDEF.LED.OK = ledger reconciled
WDEF.LED.DEBT = borrowed time / deferred repair / hidden readiness debt
WDEF.LED.BR = ledger breach / invariants broken
WDEF.LED.REC = ledger repaired / reconciled again
# =========================================================
# 14. SIGNAL / CLARITY CODES
# =========================================================
WDEF.SIG.HIGH = reliable field signal
WDEF.SIG.MIX = mixed signal
WDEF.SIG.LOW = weak signal
WDEF.NOI.LOW = manageable noise
WDEF.NOI.MED = elevated noise
WDEF.NOI.HIGH = dangerous noise
WDEF.TCL.HIGH = truth clarity high
WDEF.TCL.MED = truth clarity moderate
WDEF.TCL.LOW = truth clarity low
# Suggested expression:
WDEF.TCL = WDEF.SIG / (WDEF.SIG + WDEF.NOI)
# =========================================================
# 15. STATE CLASSIFICATION RULES
# =========================================================
WDEF.RULE.LPOS =
IF DTR >= theta_d
AND RDY >= theta_r
AND CMD >= theta_c
AND LOG >= theta_l
AND BUF >= theta_b
AND RPR >= ATR
AND APR > APR_min
THEN LBand = LPOS
WDEF.RULE.LNEG =
IF CMD < CMD_min
OR LOG < LOG_min
OR BUF < BUF_min
OR RPR < ATR
OR APR <= APR_min
OR HF = TRUE
THEN LBand = LNEG
WDEF.RULE.LNEU =
IF NOT LPOS
AND NOT LNEG
THEN LBand = LNEU
# =========================================================
# 16. TRANSITION CODES
# =========================================================
WDEF.TRANS.N2N = Negative -> Neutral
WDEF.TRANS.N2P = Negative -> Positive
WDEF.TRANS.U2P = Neutral -> Positive
WDEF.TRANS.P2U = Positive -> Neutral degradation
WDEF.TRANS.P2N = Positive -> Negative collapse
WDEF.TRANS.U2N = Neutral -> Negative slip
# =========================================================
# 17. ACTION / REPAIR CODES
# =========================================================
WDEF.ACT.DETECT = detect live threat / detect drift
WDEF.ACT.TRUNC = truncate accelerating failure
WDEF.ACT.PROTECT = protect core corridor / protect base continuity
WDEF.ACT.HOLD = hold current line
WDEF.ACT.CONTAIN = contain breach
WDEF.ACT.SEAL = seal exposed corridor
WDEF.ACT.REDEP = redeploy force
WDEF.ACT.MOB = mobilise reserves
WDEF.ACT.RESUP = restore supply / resupply
WDEF.ACT.ROTATE = rotate tired units
WDEF.ACT.REPAIR = repair damaged capability
WDEF.ACT.STITCH = stitch broken corridor
WDEF.ACT.REBUILD = rebuild transfer and continuity
WDEF.ACT.REGEN = regenerate people / reserves / training depth
WDEF.ACT.VERIFY = verify under live or simulated load
WDEF.ACT.WIDEN = widen corridor margin
WDEF.ACT.DETER = increase deterrence visibility
WDEF.ACT.FORT = fortify key node
WDEF.ACT.DECOY = deception / misdirection
WDEF.ACT.EVAC = evacuation / preservation of critical assets
WDEF.ACT.DEESC = de-escalate
WDEF.ACT.ESC = escalate within bounds
WDEF.ACT.RESET = reset doctrine / command route / operating assumptions
# =========================================================
# 18. SENSOR PACK CODES
# =========================================================
WDEF.SEN.THR = threat sensor
WDEF.SEN.RDY = readiness sensor
WDEF.SEN.CMD = command clarity sensor
WDEF.SEN.LOG = logistics continuity sensor
WDEF.SEN.BUF = buffer depth sensor
WDEF.SEN.RES = reserve depth sensor
WDEF.SEN.INT = intelligence quality sensor
WDEF.SEN.DOC = doctrine validity sensor
WDEF.SEN.CIV = civil support sensor
WDEF.SEN.MRL = morale sensor
WDEF.SEN.INF = infrastructure integrity sensor
WDEF.SEN.CYB = cyber integrity sensor
WDEF.SEN.TTC = time-to-node sensor
WDEF.SEN.APR = exit aperture sensor
WDEF.SEN.RPR = repair-vs-attrition sensor
# =========================================================
# 19. DETECTION FLAGS
# =========================================================
WDEF.FLAG.DRIFT = gradual degradation detected
WDEF.FLAG.OVEREXT = overextension detected
WDEF.FLAG.FALSEPOS = false strength signal detected
WDEF.FLAG.BORROW = borrowed readiness / time debt detected
WDEF.FLAG.STALE = doctrine stale vs live threat
WDEF.FLAG.DECOUP = civil-military decoupling detected
WDEF.FLAG.CHAIN = cascading failure risk detected
WDEF.FLAG.NODE = critical node approaching
WDEF.FLAG.ROUTE = viable route count shrinking
WDEF.FLAG.SHOCK = incoming amplitude shock risk
# =========================================================
# 20. CAMPAIGN OUTCOME CODES
# =========================================================
WDEF.OUT.HOLD = defence line held
WDEF.OUT.CONTAIN = breach contained
WDEF.OUT.RECOVER = corridor recovered
WDEF.OUT.STALEMATE = no decisive route change
WDEF.OUT.ATTRIT = prolonged attritional spend
WDEF.OUT.RUPTURE = corridor rupture
WDEF.OUT.COLLAPSE = systemic collapse
WDEF.OUT.DETER = deterrence success / conflict prevented
# =========================================================
# 21. MINIMAL WAR-DEFENCE KERNEL
# =========================================================
WDEF.KERNEL = {
  THR, DTR, RDY, CMD, LOG, BUF, RES, DOC, INT, CIV, RPR, ATR, TTC, APR, LBand
}
# =========================================================
# 22. CANONICAL ONE-LINE BANDS
# =========================================================
WDEF.LNEG.DEF =
defence spends readiness faster than it can regenerate; command, logistics, buffers, or repair fall below live threat load
WDEF.LNEU.DEF =
defence holds a narrow survivability line but remains vulnerable to prolonged or compounded stress
WDEF.LPOS.DEF =
deterrence, readiness, doctrine, logistics, command, reserves, and repair remain stronger than hostile disruption across the relevant campaign horizon
# =========================================================
# 23. MINIMAL ROUTE LOGIC
# =========================================================
WDEF.ROUTE.1 = detect -> truncate -> protect -> contain
WDEF.ROUTE.2 = restore command -> restore logistics -> restore reserves
WDEF.ROUTE.3 = repair -> verify -> stitch -> rebuild
WDEF.ROUTE.4 = widen corridor -> regenerate -> deterrence restore
# =========================================================
# 24. SHORT ARTICLE INSERT VERSION
# =========================================================
WDEF.SHORT =
Bands: LNEG / LNEU / LPOS
Core: THR, DTR, RDY, CMD, LOG, BUF, RES, DOC, INT, CIV, RPR, ATR
Collapse: COLL.AMP / COLL.SLO / COLL.FAS
Breach: BR.CMD / BR.LOG / BR.INT / BR.BUF / BR.CIV / BR.RTE
Actions: DETECT / TRUNC / PROTECT / HOLD / CONTAIN / MOB / RESUP / REPAIR / STITCH / REBUILD / VERIFY / WIDEN / REGEN
Rule:
LPOS if repair >= attrition and readiness + command + logistics + buffer remain above threat load
LNEG if hard fails or repair < attrition
LNEU otherwise

		