GEMINI REVIEW Phase7D Claude Implementation Prompt

# Gemini Review Packet — Phase 7C/7D Claude Implementation Prompt Critique

**Project:** StoryTime, formerly Podcast Pipeline  
**Current transition:** Phase 7C / 7C.1 Architecture Baseline Amendment → implementation prompt review  
**Recommended implementation phase name:** Phase 7D — App Containerization Implementation  
**Purpose of this file:** Explain Claude Opus’s Phase 7C.1 amendment, then ask Gemini to critique the Claude Opus implementation prompt before the user sends it to Claude.  
**Status:** Gemini critique packet only. Do not implement from this file.

---

## Instructions for Gemini

You are Gemini 3 Thinking, acting as the Independent Critic / Architecture Reviewer for StoryTime.

Your task is to critique the Claude Opus implementation prompt included later in this file.

Do **not** implement.  
Do **not** write Dockerfiles.  
Do **not** write docker-compose files.  
Do **not** write code.  
Do **not** produce patches.  
Do **not** produce a tarball.

You are reviewing whether the implementation prompt is safe, scoped, testable, and aligned with the locked Phase 7C / 7C.1 Architecture Baseline Amendment.

The user is the final decision-maker. GPT-5.5 Thinking is the mediator/state keeper. Claude Opus 4.7 is the proposed implementation model after this critique.

---

# What Claude Opus Came Up With in Phase 7C / 7C.1

Claude Opus drafted a Phase 7C Architecture Baseline Amendment candidate and then revised it in Phase 7C.1 after Gemini critique.

The amendment is planning-only. It does not implement anything.

## Amendment Decision

Claude recommends amending the Architecture Baseline narrowly to permit **optional, local, single-host, demo-grade app containerization** of the existing blue/green StoryTime slots.

The amendment does **not** authorize cloud deployment or production deployment.

## Key Boundaries from Claude’s Amendment

The amendment says:

- Bare-metal local Python remains the default supported mode.
- Docker remains optional and never required.
- The standard local quality gates remain Docker-free.
- Application containerization is local-only and demo-grade.
- No cloud deployment is authorized.
- No registry publishing is authorized.
- No Kubernetes is authorized.
- No Terraform is authorized.
- No production HA is authorized.
- No production auth is authorized.
- No multi-tenant behavior is authorized.
- No active alerting is authorized.
- No CI/CD automation is authorized.
- No vendor telemetry fan-out is authorized in Phase 7C / 7D.
- Vendor telemetry fan-out remains Phase 8 or later.

## Data / Persistence Rules from Claude’s Amendment

The amendment requires:

- SQLite/event_log/artifacts remain the source of truth.
- `pipeline_run_id` remains the durable correlation key.
- `trace_id` remains ephemeral.
- Blue and green keep separate state roots and separate feed roots.
- No shared SQLite database is allowed.
- No two processes may write to one SQLite database.
- SQLite state must live on per-slot named Docker volumes.
- Cross-platform host bind mounts for SQLite state are prohibited.
- Durable state, `runs/`, and `feed/` artifacts must outlive containers.
- Containers must not store durable state in their writable layer.
- `runs/`, `feed/`, `.env`, caches, and secret-file patterns must be excluded from image build context through `.dockerignore`.

## Blue/Green Rules from Claude’s Amendment

The amendment requires:

- One application image, two containers or services.
- The image is slot-agnostic.
- Blue and green are selected by existing per-slot environment/configuration.
- Blue and green each use separate named volumes.
- Blue and green each expose only loopback-bound backend ports.
- The Phase 7B native Python front door remains host-based.
- The active-slot pointer remains a host file.
- Switch and rollback remain pointer-based, operator-initiated, and demo-grade.
- Blue/green state divergence is explicitly accepted:
  - switching serves a different isolated slot timeline;
  - switching does not merge or migrate state;
  - rollback safety is prioritized over automated state convergence.

## Network / Port Rules from Claude’s Amendment

The amendment requires strict loopback-only publishing, for example: