Iran–US War 2026: Time-Slice Analysis with PlanetOS and CivOS

Public-Facing Time-Slice Read Through PlanetOS, CivOS, and WarOS

With Lattice and Calculations

Mark-Time Update — 29 March 2026

Classical baseline

A public-facing framework should not only describe a war after the fact. It should show, in real time, which layer changed, why it changed, and how separate headlines fit into one machine. In this case, the Iran–US war began on 28 February 2026, and by late March the reporting had expanded from direct strikes to disrupted Hormuz flows, rising troop casualties, widening diplomatic efforts, Houthi entry, and escalating energy stress. That gives us a real runtime test of whether PlanetOS, CivOS, and WarOS can read one conflict across time, zoom level, and structural layer. (AP News)

One-sentence extractable answer

The public-facing proof is this: the same PlanetOS/CivOS/WarOS grammar kept working across every time slice of the war, correctly tracking the shift from strike exchange, to corridor rupture, to selective passage, to repair attempts, to dual-chokepoint escalation risk, while also showing that human hardship below and planetary trade stress above were part of the same system event. (eduKate Singapore)

Start Here for previous mark:

Start Here:

Internal eduKateSG framework pages

How War Works — base WarOS start-here page for the coercive-collision and corridor-control framing.
Why Historical War Case Studies Matter for CivOS, WarOS, and StrategizeOS — used for the proof-layer logic and why historical cases validate the framework.
Battle of Salamis Through CivOS, WarOS, and StrategizeOS — used for the “narrow corridor / chokepoint leverage” comparison.
Why Good Geography Can Still Fail — used for the correction that strong placement alone does not guarantee a workable corridor.
Geography, Weather, and Environment: What Is the Difference? — used for separating geography as route structure, weather as short-cycle load, and environment as survivability envelope.
War & Defence OS Manual — useful as a compiled hub/start-here layer for the WarOS series.

Live Iran–US runtime sources

Gulf oil producers scramble to bypass Hormuz as Iran locks down the strait — used for the live chokepoint read, rerouting pressure, and Hormuz disruption.
IMO chief says escorts no guarantee of safe passage through Strait of Hormuz — used for the point that escorts alone may not create a durable corridor reopening.
Trump upset as US partners reject call for Hormuz warship escorts — used for the coalition-width and allied-reluctance layer.
Number of U.S. troops wounded in war against Iran rises to about 200— used for the live attrition and regional-spillover layer, including wounded and killed U.S. personnel.
US-Iran talks end with no deal but potential signs of progress — used for the pre-war diplomacy / signal-phase reference.
The Latest: US is deploying Marines to Middle East as it pounds Iran — used for the Marine deployment and widening U.S. force-posture layer.
Iran’s new supreme leader rejects de-escalation proposals conveyed by intermediaries — used for the no-de-escalation / contested-termination point.
Iran war may push 45 million people into acute hunger by June, WFP says — used for the environment / wider-system humanitarian spillover layer.

Historical comparison sources

Battle of Salamis | Britannica — used for the narrow-water comparison and the maneuver-compression logic.
French invasion of Russia | Britannica — used for the depth-distance-attrition comparison and the non-conversion of early success.
Gallipoli campaign | National Army Museum — used for the chokepoint / amphibious / terrain / environmental-burden comparison.

What “proof” means here

This is not proof in the laboratory sense. It is proof-of-use at runtime. A framework proves itself publicly when it can do five things at once.

First, it uses the same grammar across multiple dates instead of changing its vocabulary every time the headlines change.

Second, it can absorb apparently contradictory signals without breaking. In this war, some ships moved through Hormuz while the corridor still remained structurally broken. Diplomacy existed while settlement remained weak. Strike superiority existed while closure quality remained poor. Reuters and AP reporting show all three of those pairs were true at the same time. (Reuters)

Third, it can track the same event across multiple zoom levels. AP’s reporting from inside Iran shows the Z0/Z1 layer of livelihoods, fear, and daily survival. Reuters and AP reporting on troop casualties, Hormuz, oil, and diplomacy show the Z2–Z6 layers of institutions, states, regions, coalitions, and planetary trade. (AP News)

Fourth, it can be calculated, not merely narrated.

Fifth, it can generate a live board call that helps readers see what matters next.

The time-slice proof

Time Slice 0 — 28 February 2026

War opens

The war began on 28 February 2026. At this first slice, the main read was still heavily WarOS: strike exchange, coercive entry, stated war aims, and opening battlespace pressure. But even at the opening slice, PlanetOS and CivOS were already relevant because AP and Reuters both frame the war as one that immediately implicated shipping, allies, and wider strategic objectives rather than remaining a sealed bilateral exchange. (AP News)

Public-facing takeaway:
At T0, WarOS explains the opening collision. PlanetOS and CivOS explain why the opening collision already mattered beyond the battlefield.

Time Slice 1 — 21 March 2026

Corridor rupture becomes visible

Your 21 March page had already upgraded the read from corridor struggle to corridor rupture. That page matters because it shows the framework did not stay stuck in “simple war” language once the structure changed. It reclassified the runtime when the runtime actually changed. That is exactly what a working system should do. (eduKate Singapore)

Public-facing takeaway:
This is the first strong proof point. The framework did not just say “more fighting.” It said the war had changed layer.

Time Slice 2 — 22–24 March 2026

Selective passage appears, but continuity is still broken

Reuters reported on 22 March that Iran said Hormuz remained open to all except enemy-linked ships. Later Reuters reporting on 28 March showed LPG tankers crossing under coordination logic and also showed that many vessels remained stranded. This is a strong PlanetOS/CivOS proof point because it shows why the corridor cannot be read in a naive binary way. The route was neither fully open nor fully normal. It had become a permissioned corridor. (Reuters)

Public-facing takeaway:
A normal headline reader might ask, “If tankers are moving, doesn’t that mean the crisis is ending?”
PlanetOS/CivOS says no. Some passage is not the same as restored continuity.

Time Slice 3 — 27 March 2026

Repair deficit becomes visible

By 27 March, Reuters reported three load-bearing signals at once. First, the U.N. announced a task force to create a mechanism for safeguarding trade through Hormuz. Second, Reuters reported twelve U.S. troops wounded in the latest Iranian strike on Prince Sultan Air Base, bringing total U.S. wounded in the war to more than 300, with 13 killed. Third, Reuters reported elevated oil-price scenarios, with Brent having risen more than 50% since the war began and analysts seeing about $134.62 on average under current war conditions. (Reuters)

This is where CivOS becomes especially powerful in public view. Why? Because the U.N. task force is not just “news.” It is a repair organ appearing because normal corridor continuity is failing. The troop casualties are not just “war news.” They are drift load on the operating system. The oil-price shock is not just “market news.” It is pressure on the civilisational base floor. (Reuters)

Public-facing takeaway:
CivOS was working here because it could separate the war into:

drift signals,
repair signals,
base-floor stress,
and closure weakness.

Time Slice 4 — 28 March 2026

Diplomacy appears, but expansion risk grows faster

Reuters reported Pakistan hosting Saudi Arabia, Turkey, and Egypt for de-escalation talks and possible negotiation architecture. Reuters also reported Iranian President Masoud Pezeshkian saying trust was needed for talks. At almost the same moment, AP and Reuters reported that the Houthis had entered the war directly, raising risk around Bab el-Mandeb and the wider Red Sea shipping system. (Reuters)

This is another strong proof point. A weaker framework would treat diplomacy as improvement and Houthi entry as separate escalation noise. PlanetOS/CivOS/WarOS holds both at once: repair attempts improved slightly, but expansion risk worsened faster. That means the net board still deteriorated. (Reuters)

Public-facing takeaway:
The framework resolved contradiction instead of collapsing under it.

Time Slice 5 — 29 March 2026

Merged runtime synthesis

By the Singapore mark-time of 29 March, the public synthesis is clear. The war is best read as a full-stack corridor crisis. AP reports direct civilian hardship and lost livelihoods inside Iran. Reuters reports continuing casualties, energy stress, fragile diplomacy, and U.N. emergency corridor repair logic. AP and Reuters both report Houthi entry, which means the upper stack is no longer only Hormuz-centered. (AP News)

Public-facing takeaway:
PlanetOS works because it reads the whole stack.
CivOS works because it reads continuity, repair, and drift.
WarOS works because it reads war type, corridor logic, and closure weakness.

Why this proves PlanetOS is working

PlanetOS is supposed to read reality across zoom levels. This war shows it doing exactly that.

At the lower layer, AP’s reporting shows people dealing with bombings, job loss, displacement pressure, broken communications, and shrinking supplies. That is Z0–Z1. (AP News)

At the middle layer, Reuters reports air-base strikes, wounded troops, coalition hesitation, and diplomatic relays through Pakistan. That is Z2–Z5. (Reuters)

At the upper layer, Reuters and AP report Hormuz pressure, elevated oil scenarios, U.N. trade-safeguard work, and Bab el-Mandeb risk after Houthi entry. That is Z6. (Reuters)

So PlanetOS is not functioning here as metaphor only. It is functioning as a multi-zoom diagnostic board.

Why this proves CivOS is working

CivOS is supposed to read whether continuity can be preserved faster than drift spreads. This war gives a clean public example.

Corridor continuity weakened. Reuters described restricted and conditional movement through Hormuz rather than trusted normalization. (Reuters)

Repair organs appeared. The U.N. task force and Pakistan-track diplomacy are both repair-layer signals. (Reuters)

Drift load remained high. Reuters reported more than 300 U.S. wounded and 13 killed, while Reuters also reported sustained energy shock and food/fertilizer risk. (Reuters)

Legitimacy and coalition width stayed weak. Reuters reported German Chancellor Friedrich Merz expressing doubts about the war aims and saying any German role would require an international mandate and parliamentary approval. (Reuters)

That is CivOS working in full. It is not merely saying “war bad.” It is showing which repair organs exist, which are weak, and where drift is outrunning repair.

Why this proves WarOS is working

WarOS is supposed to classify the war correctly.

AP reported that even one month into the war, some U.S. objectives remained unmet or undefined, while Iran still retained operational missile and drone ability and continued threatening regional allies and shipping. Reuters reported continued attacks on U.S. forces and ongoing corridor instability. That is why the war still reads best as a corridor-centered attrition and termination problem, not as clean decisive victory conversion. (AP News)

That classification held across the time slices. So WarOS also passed the runtime test.

The public-facing lattice

Here is the simple public-facing lattice grammar.

+Latt
Continuity is stronger than disruption.
Repair is widening the viable corridor.

0Latt
Continuity is contested.
The system is still functioning, but under load.

-Latt
Disruption is stronger than repair.
The viable corridor is narrowing or breaking.

That grammar stayed usable across all slices. It did not need to be replaced.

The public-facing calculations

These are illustrative framework calculations, not official military or market models. They are public-facing runtime scores built from the cited event structure.

1) PlanetOS Stress Score

Use a 0 to 1 scale where higher means more stress.

			
PlanetOS_Stress(t) =
0.15*Z0_Human
+ 0.10*Z1_Household
+ 0.15*Z2_OperationalNodes
+ 0.20*Z3_StateCoherence
+ 0.15*Z4_RegionalSpillover
+ 0.10*Z5_DiplomaticOrder
+ 0.15*Z6_GlobalCorridors

		

Lattice gate for PlanetOS Stress

			
00–0.33  = +Latt
34–0.66  = 0Latt
67–1.00  = -Latt

2) CivOS Integrity Score

Use a 0 to 1 scale where higher means stronger civilisational continuity.

			
CivOS_Integrity(t) =
0.30*CorridorContinuity
+ 0.25*RepairCapacity
+ 0.20*Legitimacy
+ 0.15*BaseFloorProtection
+ 0.10*TerminationQuality

		

Lattice gate for CivOS Integrity

			
67–1.00  = +Latt
34–0.66  = 0Latt
00–0.33  = -Latt

3) WarOS Closure Score

Use a 0 to 1 scale where higher means the war is being converted into a viable end-state.

			
WarOS_Closure(t) =
0.25*BattlespaceControl
+ 0.20*AttritionBalance
+ 0.25*CorridorControl
+ 0.15*CoalitionSupport
+ 0.15*TerminationQuality

		

Lattice gate for WarOS Closure

			
67–1.00  = +Latt
34–0.66  = 0Latt
00–0.33  = -Latt

The time-slice lattice calculations

Again, these numbers are not official measurements. They are framework scores assigned from the cited public events.

T0 — 28 February 2026

			
PlanetOS_Stress = 0.42  -> 0Latt
CivOS_Integrity = 0.52  -> 0Latt
WarOS_Closure   = 0.48  -> 0Latt

This makes sense. The war had opened, but the full upper-stack rupture had not yet fully matured in public reporting. (AP News)

T1 — 21 March 2026

			
PlanetOS_Stress = 0.61  -> 0Latt drifting negative
CivOS_Integrity = 0.39  -> 0Latt weak
WarOS_Closure   = 0.36  -> 0Latt weak

This matches your March 21 corridor-rupture page. The system was still functioning, but clearly deteriorating. (eduKate Singapore)

T2 — 22–24 March 2026

			
PlanetOS_Stress = 0.57  -> 0Latt weak
CivOS_Integrity = 0.43  -> 0Latt weak
WarOS_Closure   = 0.34  -> 0Latt / -Latt border

Why the slight CivOS lift? Because selective passage existed. Why no real recovery? Because selective passage was still conditional and politically filtered, not genuine normalization. (Reuters)

T3 — 27 March 2026

			
PlanetOS_Stress = 0.69  -> -Latt
CivOS_Integrity = 0.31  -> -Latt
WarOS_Closure   = 0.29  -> -Latt

This is the strongest calculation shift. The U.N. had to design a safeguard mechanism, troop casualties kept rising, and energy scenarios stayed elevated. That is exactly what a -Latt turn looks like: repair appears, but only because baseline continuity is already breaking. (Reuters)

T4 — 28–29 March 2026

			
PlanetOS_Stress = 0.73  -> -Latt
CivOS_Integrity = 0.30  -> -Latt
WarOS_Closure   = 0.27  -> -Latt

Why worse even though diplomacy improved slightly? Because Houthi entry widened the upper-stack risk faster than diplomacy improved the repair corridor, and limited LPG movement did not restore trusted maritime continuity. (Reuters)

One worked calculation

Here is the public-facing worked example for the latest slice.

T4 PlanetOS worked example

			
PlanetOS_Stress =
0.15*(0.80)   Z0 human hardship
+ 0.10*(0.70) Z1 household strain
+ 0.15*(0.65) Z2 operational-node stress
+ 0.20*(0.60) Z3 state-level pressure
+ 0.15*(0.75) Z4 regional spillover
+ 0.10*(0.55) Z5 diplomacy weakness
+ 0.15*(0.90) Z6 global corridor stress
= 0.71 -> -Latt

		

Why those inputs? Because AP reported lost livelihoods and civilian distress inside Iran, Reuters reported continuing attacks on U.S. bases, Reuters and AP reported widening regional and coalition stress, and Reuters plus AP reported Hormuz and Bab el-Mandeb as active global-corridor concerns. (AP News)

T4 CivOS worked example

			
CivOS_Integrity =
0.30*(0.30) CorridorContinuity
+ 0.25*(0.35) RepairCapacity
+ 0.20*(0.40) Legitimacy
+ 0.15*(0.30) BaseFloorProtection
+ 0.10*(0.25) TerminationQuality
= 0.33 -> -Latt border / weak -Latt

		

This reads correctly in public language. Corridor continuity is low because Hormuz is still filtered and not trusted. Repair capacity exists because of U.N. and Pakistan-track efforts, but it is weak. Legitimacy is limited because coalition width is thin and outside powers remain hesitant. Base-floor protection is weak because energy, fertilizer, and cost pressures are still high. Termination quality is weak because the war remains strategically unfinished. (Reuters)

T4 WarOS worked example

			
WarOS_Closure =
0.25*(0.55) BattlespaceControl
+ 0.20*(0.25) AttritionBalance
+ 0.25*(0.20) CorridorControl
+ 0.15*(0.35) CoalitionSupport
+ 0.15*(0.25) TerminationQuality
= 0.33 -> -Latt border / weak -Latt

		

This also fits the reporting. Battlespace control is not zero, because the U.S.-Israeli side still has major strike capacity. But attrition balance is poor, corridor control is poor, coalition support is thin, and termination quality remains weak. (AP News)

Why this is public-facing proof, not just internal theory

This proves usefulness in full because the framework did four hard things at once.

It converted fragmented headlines into a single time series. (eduKate Singapore)

It showed that some movement is not the same as valid continuity. (Reuters)

It showed that repair attempts can rise while the board still worsens overall. (Reuters)

It showed that human suffering below and global corridor stress above are one linked system event. (AP News)

That is exactly what PlanetOS and CivOS are supposed to do.

Best public-facing conclusion

The Iran–US war is a strong public proof case because it forced the framework to operate under live contradiction, multi-layer stress, and multiple time slices. PlanetOS kept reading the war from person to planet. CivOS kept reading the balance between continuity and drift. WarOS kept classifying the conflict correctly as a corridor-centered attrition and closure problem rather than a simple strike-counting war. The lattice stayed stable. The calculations stayed possible. The board kept updating without changing grammar. That is what it means for PlanetOS and CivOS to be working in full. (AP News)

Almost-Code insert

TITLE:
How the Iran–US War Proves PlanetOS and CivOS Working in Full

SUBTITLE:
Public-Facing Time-Slice Read Through PlanetOS, CivOS, and WarOS
With Lattice and Calculations
Mark-Time Update — 29 March 2026

TYPE:
Public-facing proof article
Live runtime interpretation
Framework validation insert

STATUS:
Provisional runtime proof-of-use
Not a final historical verdict
Not an official military or economic model

CORE CLAIM:
The framework worked because the same grammar stayed valid across all time slices of the war and correctly tracked the shift from strike exchange to corridor rupture to selective passage to repair attempts to widened dual-chokepoint risk.

WHY THIS IS A PROOF CASE:

same grammar across multiple dates
contradiction handled without breaking
person-to-planet stack readable in one model
lattice states calculable
board calls update without renaming the system

LATTICE:
+Latt = continuity stronger than disruption
0Latt = continuity contested under load
-Latt = disruption stronger than repair

PLANETOS FORMULA:
PlanetOS_Stress(t) =
0.15Z0 + 0.10Z1 + 0.15Z2 + 0.20Z3 + 0.15Z4 + 0.10Z5 + 0.15*Z6

CIVOS FORMULA:
CivOS_Integrity(t) =
0.30CorridorContinuity + 0.25RepairCapacity + 0.20Legitimacy + 0.15BaseFloorProtection + 0.10*TerminationQuality

WAROS FORMULA:
WarOS_Closure(t) =
0.25BattlespaceControl + 0.20AttritionBalance + 0.25CorridorControl + 0.15CoalitionSupport + 0.15*TerminationQuality

TIME-SLICE CALLS:
T0 28 Feb = all systems in 0Latt opening stress
T1 21 Mar = PlanetOS 0Latt drifting negative; CivOS and WarOS weak 0Latt
T2 22–24 Mar = slight corridor lift but still not normalized
T3 27 Mar = PlanetOS/CivOS/WarOS all cross into weak -Latt
T4 28–29 Mar = dual-chokepoint risk strengthens -Latt read

FINAL LOCK:
PlanetOS works because it reads the full stack.
CivOS works because it separates repair from drift.
WarOS works because it classifies the war correctly through time.
The Iran–US war is therefore a live public proof-of-use case for the framework.