Preserve
Checkpoint local work and get useful history off single machines before anything else is started.
OPERATIONS NOTE / 3 SEPTEMBER 2026
Two fronts have crossed the boundary.
The development-environment migration and repository preservation work continue, but two lines are no longer internal promises. Red Flags: Open the Line and DreamWeb: Pomegranate Reconstruction are released for Windows and Linux. The public register must now separate what has shipped from what remains under construction, without turning the rest of the portfolio into a premature announcement.
ops/migration.status
STATE PRESERVATION..... ACTIVE
LOCAL CHECKPOINTS...... IN PROGRESS
RELEASE CANDIDATES..... FREEZE FIRST
HUMAN CERTIFICATION.... OPEN
PUBLIC STATUS.......... LAG EXPECTED
rule: state before spectacle
LOCAL CHECKPOINTS...... IN PROGRESS
RELEASE CANDIDATES..... FREEZE FIRST
HUMAN CERTIFICATION.... OPEN
PUBLIC STATUS.......... LAG EXPECTED
rule: state before spectacle
Order of work
State before spectacle.
The initiative is deliberately narrowing its active front. Preservation and release hardening come first; breadth resumes afterwards.
Freeze
Name an immutable release candidate, then re-run the evidence against that exact hash rather than a moving target.
Certify
Human passes and native-platform verification are separate gates. Automation cannot sign them.
Resume
Only then widen the front again. Three delivery priorities at a time, the rest in explicit maintenance.
Control plane
The tools that carry the migration.
The control plane is not three equal organs. Pomegranate Command routes and delivers the work, PEP makes the governance transferable, and BAM carries state between machines. The reconciliation organ that once sat beside them has been withdrawn from the public portfolio; this page does not claim more for what remains than the artefacts can show.
Release register
The exact state carried by each name.
Versions, not adjectives. Every line below is a package, a tag or a gate that exists on disk, and every line stops where the evidence stops.
Red Flags: Open the Line 1.0.0Released on itch.io. A standalone twenty-one-map campaign across five episodes for Windows and Linux, carrying its own runtime and requiring no commercial IWAD.
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.
Pomegranate Command 0.6.0Four provider families, Human Mode, a local Ollama concierge and PostgreSQL operational memory. Internal infrastructure, not a product for sale.
NOEMA/OS R0.2Two operator chambers over the Field Horizon workstation. A handoff release; hardware certification remains open.
PEP / PEP Forge 0.1.0A packaged, machine-readable project governance protocol with one live smoke project. Not a proven standard.
BAM v1.0A handoff exists. Daily adoption is not asserted here, because the artefacts cannot evidence it.
Rebel Moon Rising — Mission 1 baselineOne mission converted from retail data, calibrated against the original runtime and playable on a stock hash-pinned engine build. A checkpoint tag behind a deterministic package; there is no distribution page and no owner acceptance.
RED FLAGS 2: COLOR OF POMEGRANADE — vertical sliceA standalone package of 1,153 deterministic entries with one production map of twenty-three integrated, runtime-proven and physically traversed. Platform bundles have not started and the owner's art lock is open. Not released.
What a status on this site means.
Evidence boundary
- Project statuses on this site follow a portfolio audit dated 18 August 2026, corrected on 28 August 2026 for the two works that have since been publicly released.
- That audit verified repository history, commit dates, tags, the existence and dates of release artefacts, and the content of canonical status files. It replayed no gate.
- Where a figure comes from a project's own reports, tests or status files, it is presented as reported, not as freshly recertified here.
- A screenshot proves a visible runtime surface. It is not human acceptance, a distribution right or a commercial certification.
- Runnable is not accepted. Packaged is not released. Tagged is not commercially published. A roadmap is not shipped content.
- A project with substantial engineering evidence but no human, legal or native-platform certification is described as exactly that.
- Two dossiers were withdrawn from the public portfolio on 3 September 2026: one operational system the initiative no longer uses, and one game abandoned before its campaign began. Their routes redirect permanently and no page names them.
- Code excerpts on the technical dossiers are extracted from a project 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.
- 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. Two works meet that threshold; every other project keeps its existing distinction between prototype, candidate, reconstruction and release.
The audit found the gap running one way: this site had been under-declaring its own portfolio. Correcting that is not permission to start over-declaring it. Public status will keep lagging local reality, and that remains the honest cost of preserving state instead of announcing it.