Theatre of War

An idea, clearly labeled as an idea

Theatre of War is a planned explainer channel about conflict news, and it has not launched. The name is a working title. As of the planning notes dated October 2, 2026, no channel had been created or published. It shows up on stream as a recurring line on the to-do list (“push the Theatre of War project forward”) and in the October 8 go-live announcement, where it is described as a news feed that sits next to the avatar reaction channel. This page records the plan so that its status is clear and so that anyone who wants to follow its progress knows what to expect.

It belongs on a creator hub for a simple reason: it uses the same production habits as everything else here. Agents draft and organize, free local tools do the rendering and a human approves anything sensitive. If the plan works, it becomes another independent income stream, and if it does not, the notes will say why.

The promise

The channel’s stated purpose is to explain what changed in a conflict, where it happened, what evidence supports it and how it affects ordinary people and global systems. It would combine concise narration, real footage, clear geographic visuals and measured analysis. The initial coverage in the plan is the Russia–Ukraine war and the Iran, Gulf and Strait of Hormuz situation, with broader politics, shipping, energy, insurance, AI chips and public reactions included only when they connect to those stories. The explicit rule is to avoid turning the channel into a general technology or celebrity news feed.

The target audience is defined by need rather than age: people who want a clear explanation without specialist military knowledge. That means explaining acronyms, showing readable place labels, adding captions and making economic consequences concrete.

Content pillars

1. Battlefield developments: verified changes in control, strikes and military operations.
2. Logistics and infrastructure: ports, energy systems, transport, replenishment, shipping and supply chains.
3. Civilian consequences: displacement, access to utilities, prices, aid and public safety.
4. Leadership and diplomacy: statements, negotiations, sanctions, protests and public reactions.
5. Economic consequences: measured changes in energy, freight, insurance and affected industries, with dates and clear sourcing.

Editorial rules that come first

A conflict channel can do real harm if it is careless, so the plan puts the rules before the production. Every episode would follow the same evidence standards for every party. Documented wrongdoing is named precisely; contested allegations are attributed to their source. The plan distinguishes a source’s report of an act, an attribution of responsibility and a formal legal determination, and it refuses to manufacture balance by giving unsupported claims equal weight to well-supported evidence.

• Protecting people. Blur every face in combat footage, blur fallen bodies entirely and obscure severe wounds and excessive blood. The owner must approve any sensitive footage.
• Labeling. Real footage, illustrative footage and reconstructions are clearly identified, and old B-roll is not passed off as footage of a specific mission.
• Provenance. Rights evidence, claim attribution, event dates, publication dates and uncertainty are preserved for each item.
• Reactions are illustrations. Public reaction clips show selected responses, not representative opinion. Polling and systematic data are different evidence.
• Corrections. Sources and corrections are linked with each episode.

Episode shape

The working pilot is an eight-to-ten-minute weekly recap with three main stories and about 45 to 90 seconds of 3D overall, as a test target and not a quota. A nine-minute pilot would open with a twenty-second hook on the biggest verified change, then headlines and geographic context, a Ukraine block, a Gulf and Hormuz block, a logistics and economics segment, civilian and diplomatic developments and a wrap-up of known facts and open questions. Every story follows the same chain: what changed, necessary context, a geographic explanation, real evidence, what remains uncertain and why it matters. Real footage comes before 3D when the evidence leads the explanation.

The provisional rhythm is one weekly recap plus two Shorts drawn from it and a community post asking which coverage viewers want next. These slots are untested hypotheses. The plan says to measure retention, returning viewers, source and correction quality and production time separately before committing to anything faster, such as a daily show.

The zero-budget constraint

The pilot must cost nothing beyond subscriptions that already exist. That means AI narration, free and open-source software, free models and datasets, local rendering and tools already in use, such as DaVinci Resolve and Blender with their MCP connections. Paid options are listed only under future upgrades. No new paid API usage, credits or trials that require payment are allowed. This is the same frugality that runs through the rest of the channel, and it forces creative decisions, such as favoring a 3D globe and a few well-sourced maps over expensive stock footage.

The 3D map sandbox

A significant part of the plan is a small 3D sandbox so that geography can be explained visually. Its central idea is one story file that holds places, tracks of moving units (longitude, latitude, altitude and time), fronts, areas and a shot list, and that is read by two renderers. A browser preview built on the CesiumJS globe renders briefing shots quickly and frame-exact, and an Unreal Engine pipeline can build a detailed georeferenced level for close-ups. Baking real surface heights into each waypoint keeps ships at the waterline. Models are normalized with Blender scripts to real-world size and orientation and exported as glTF, and a registry records each asset’s source and licence.

The licensing caveat is written in plain sight. The sandbox’s globe data plan is for non-commercial use, which covers a private pilot, and a paid plan or another data route is needed before monetized publishing. Every model is a temporary third-party asset for the private pilot and is to be replaced or cleared before anything is published. In other words, the sandbox is a prototype, and the notes refuse to treat a pretty render as proof that the channel is ready.

What would count as success

The plan lists a build order: an editorial foundation with coverage boundaries and a source registry, pilot research that traces one week of stories to original sources, a short visual trial that measures quality and render time, a full pilot episode, a brand and launch package, a second episode to measure repeatability and only then selective automation of collection, deduplication, source badges and export. A beautiful 3D world alone does not prove that the channel can ship good coverage efficiently, and the notes say so.

Until a pilot is public, the best place to follow progress is the livestream. The avatar reaction videos that share some of the tooling are on the avatar shorts page, the agent workflow is described in The vibe-coding workflow and the broader context is on the about page. Nodal’s own history page shows how earlier plans changed when reality arrived, which is a fair preview of what to expect here.