Files

Andrew Stoltz 09387f90e1 brochure: ARCHIVED 2026-05-19 — was a misinterpretation, do not re-enable

The brochure split project was a misinterpretation of an operator request
to make TtsReader + AI Station production-ready. Somewhere in the planning
chain it spun up into a separate "showcase brochure product" with its own
host, repo, NuGet, and Codex pack — none of which the operator actually
wanted. The project itself is pointless and a waste of credits.

Archive (not delete) per operator decision 2026-05-19, because some work
shipped under the misinterpretation may still have reusable value:

- FlowerCore.Intranet.Web PR #8 (merged) introduced FlowerCore.Brochure.Content
  content-NuGet carve-out — pattern may apply to TtsReader/AiStation production
  polish.
- Sprint 32 Cl-5 substrate has design ideas for public-twin vs operator-host
  separation that may transfer.
- magpie-doc-writer / wren-walkthrough skills still author useful Intranet
  content — those skills stay active.

These manifests stay at replicas: 0 for ArgoCD continuity. Cleanup options
(move out of apps/* glob, or delete entirely) are documented in README.md
for an operator-explicit future call.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-19 10:34:28 -05:00

brochure.yaml

brochure: ARCHIVED 2026-05-19 — was a misinterpretation, do not re-enable

2026-05-19 10:34:28 -05:00

README.md

brochure: ARCHIVED 2026-05-19 — was a misinterpretation, do not re-enable

2026-05-19 10:34:28 -05:00

README.md

FlowerCore Brochure — ARCHIVED 2026-05-19

Status: ARCHIVED. Do not re-enable, do not rebuild the image.

What this was

A proposed public-facing brochure subdomain (brochure.flowercore.io) that would carve /whats-new, /walkthroughs, and /galleries content out of FlowerCore.Intranet.Web and serve it anonymously through a new thin Blazor host backed by a FlowerCore.Brochure.Content NuGet.

Why it was archived

The operator asked for TtsReader and AI Station to become production-ready. Somewhere along the way that request was misinterpreted by the planning chain into "spin up a new showcase brochure product". The brochure project itself is pointless and a waste of credits. The two actual productionization arcs (TtsReader + AI Station) get the focus instead.

Archive (don't delete) rationale

Some of the work shipped under this misinterpretation may still have value if pulled back into the actual productionization work:

FlowerCore.Intranet.Web PR #8 (merged Sprint 32) introduced the FlowerCore.Brochure.Content content-split carve-out. That code may be reusable as a content-NuGet pattern for TtsReader/AiStation production polish.
The Sprint 32 Cl-5 substrate (docs/standards/sprint-32-intranet-brochure-split-substrate-2026-05-24.md) contains design ideas for public-twin vs. operator-host separation that could apply elsewhere.
The magpie-doc-writer / wren-walkthrough skills that authored flowercore-whats-new, flowercore-walkthroughs, flowercore-galleries content still produce useful Intranet content — those skills are NOT archived.

The Sprint 34 Cl-4 brochure rebuild Codex pack is at docs/archived/codex-2026-05-18-fc-brochure-web-rebuild-pack.md in FlowerCore.Notes.

Cluster state

These manifests stay at replicas: 0. ArgoCD keeps the brochure namespace + service + cert + IngressRoute objects alive for continuity, but nothing serves real traffic. The localhost/fc-brochure-web:v20260524-sprint32 image still exists on RKE2 nodes — that image is the wrong codebase (an FlowerCore.Intranet.Web binary mis-tagged as brochure during Sprint 33 Cx-5) and can be safely ctr images rm'd in a future cleanup.

Cleanup choices for a future sprint

Leave as-is (current state). Negligible cluster footprint. Operator can re-evaluate later.
Move directory to apps-archived/brochure/ (outside the apps/* ApplicationSet glob). ArgoCD prunes the infra-brochure Application + the brochure namespace. Manifests preserved in git history.
Delete entirely. Removes from git too. Use only after confirming no reusable patterns are still pending extraction.

All three are valid. Operator-explicit at the time of cleanup.