Operations — Pomegranate Interactive

Order of work

State before spectacle.

The active front is deliberately narrow: three released games to keep in order, one game to finish. Nothing is announced before it exists.

01

Maintain

The released builds are the public record. Defects reported by players are answered on the published packages, not on a local branch.

02

Deliver

And We Burn The Sky was released on 7 October 2026 as version 1.0.0, for Windows. Its dossier left the development group and now carries its distribution page.

03

Extend

Red Flags 2 grows place by place. A map joins the campaign chain when it can be played through, saved and resumed.

04

Publish

A game is called released when a public distribution page exists and the game can be obtained. Not before.

Public register

The exact state carried by each name.

A name, its availability or its state, and the date that state refers to. Each line leads to its dossier and stops where the evidence stops.

And We Burn The Sky 1.0.0Released on itch.io. An aerial combat campaign for Windows, in French: an instruction chapter, twelve missions and a playable epilogue, an Arcade mode, single player and offline. Released 7 October 2026 · recorded 9 October 2026

Red Flags: Open the Line 1.2.1Released on itch.io. A standalone twenty-one-map campaign across five episodes for Windows, in English and French, carrying its own runtime and requiring no commercial IWAD. Its field guide can be downloaded from the dossier. Released · version 1.2.1 recorded 14 October 2026

DreamWeb: Pomegranate Reconstruction 1.0.0Released on itch.io. A complete start-to-credits reconstruction for Windows and Linux, with the point-and-click structure preserved, modern fullscreen presentation and save/load. Released · recorded 28 August 2026

Red Flags 2In development. The latest candidate plays seven maps in one chain, from Sainte-Anne to the first Jerma maps; the last two are technical constructions built from provisional material. Art, enemies and arsenal are in production. No package and no distribution page. Latest candidate · 2 October 2026

Field HorizonA local retrieval, provenance, replay and canonical-synthesis engine. Its source is published; it is operated locally and has no hosted deployment. Source published 2 September 2026

What a status on this site means.

Evidence boundary

On this site, “released” means a public distribution page exists and the game can actually be obtained. Packaged, tagged, tested or playable is not enough. Three games meet that threshold.
“In development” means a build runs and is shown as it is. It carries no release date, no price and no store page, because none exists.
A capture of a game in development names its build and its date. It shows a visible runtime surface; it is not human acceptance, a distribution right or a commercial certification.
Where a figure comes from a project’s own reports, tests or status files, it is presented as reported, not as freshly recertified here.
Runnable is not accepted. Packaged is not released. A built campaign route is not a finished game. A roadmap is not shipped content.
A study, a test bench or a production direction is labelled as such and is never counted as a delivered feature.
The public portfolio was narrowed on 3 October 2026 to the games and the system the initiative is carrying. Dossiers that left it are no longer served; their former routes redirect permanently and no page names them.
Code excerpts on the Field Horizon dossier are extracted from its repository at a named commit by a tool that refuses to read a working tree. They show what the code was at that commit; they are not a claim that a test was run here.

Public status will keep lagging local reality. That remains the honest cost of showing a state instead of announcing one.

Three released games. One production front.