tegwick
78454c59d8
The Telegram channel publishes posts written from hall entries, not the entries themselves, so the handover's pressure, competition and guardrails are rebuilt around that. Composition sits outside the interface because Blueprint 48.1 forbids an LLM in the mandatory request path, and because a post about a named person's work deserves a human read that a request-path step would never get. Adds FLUID-WP-0009 for the pr- campaign repository convention and for reducing the Hall of Helix case from the thing this framework is for to an example of using it. The prefix deliberately includes "propaganda": a campaign repository that cannot name what it is doing will not govern it well. The workplan starts only after the loop has closed once on real traffic. Extracting a seam before using it is how you learn you cut it in the wrong place. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014KmVxhJ35tCo7rE7UnLwWu Assistant: claude-code Assistant-Model: opus Assistant-Process: 1116572@bnt-lap001 Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400
126 lines
4.1 KiB
Markdown
126 lines
4.1 KiB
Markdown
---
|
|
id: FLUID-WP-0009
|
|
type: workplan
|
|
title: "Establish the pr- campaign repository pattern and reduce hall-of-helix to an example"
|
|
domain: infotech
|
|
repo: fluid-core
|
|
status: active
|
|
owner: worsch
|
|
topic_slug: fluid-core
|
|
created: "2026-09-04"
|
|
updated: "2026-09-04"
|
|
planning_priority: medium
|
|
planning_order: 9
|
|
depends_on:
|
|
- FLUID-WP-0008
|
|
related_repos:
|
|
- fluid-telegram
|
|
- fluid-x
|
|
- fluid-substack
|
|
- hall-of-helix
|
|
- helix-forge
|
|
---
|
|
|
|
# FLUID-WP-0009 — Campaign repositories and example separation
|
|
|
|
Two things this framework needs before it is genuinely reusable, and neither is
|
|
urgent enough to block the first Telegram publication.
|
|
|
|
**A place for campaigns to live.** Publishing the Hall of Helix is an ongoing
|
|
public-relations offering with its own editorial voice, cadence, consent
|
|
records and budget. Today it lives inside `FT-WP-0001`, a workplan that is
|
|
supposed to finish. It needs a repository.
|
|
|
|
**A framework that is not about one campaign.** While the only worked example is
|
|
the Hall of Helix, it is hard to tell which parts of fluid-core and
|
|
fluid-telegram are general and which quietly assume that particular use. The
|
|
test of a framework is a second consumer, and the honest way to find the
|
|
accidental couplings is to look for them deliberately.
|
|
|
|
This workplan should start after `FT-WP-0001` T12 — the loop closing once on
|
|
real traffic. Extracting a seam before using it is how you learn you cut it in
|
|
the wrong place.
|
|
|
|
## T01 — Define the pr- repository convention
|
|
|
|
```task
|
|
id: FLUID-WP-0009-T01
|
|
status: todo
|
|
priority: medium
|
|
```
|
|
|
|
Write down what a `pr-` repository is, so the second one does not have to be
|
|
reverse-engineered from the first.
|
|
|
|
The prefix covers public relations, promotion and propaganda — deliberately
|
|
including the uncomfortable third word, because a campaign repository that
|
|
cannot name what it is doing will not govern it well.
|
|
|
|
A `pr-` repo should carry: its own `INTENT.md`; a campaign intent describing
|
|
audience, voice and what it will not say; consent records for anyone it writes
|
|
about; composition strategies as named variants; and a publishing cadence. It
|
|
consumes one or more `fluid-*` interfaces and owns none of them.
|
|
|
|
## T02 — Establish pr-hall-of-helix
|
|
|
|
```task
|
|
id: FLUID-WP-0009-T02
|
|
status: todo
|
|
priority: medium
|
|
```
|
|
|
|
Create the repository and move the campaign into it, per `FT-WP-0001` T13. The
|
|
split is already written there; this task is the execution and the registration
|
|
with the State Hub under the `infotech` domain.
|
|
|
|
The campaign becomes a consumer of `fluid-telegram` in cohort
|
|
`hall-publishing-jobs`, and runs its own FLUID loop over its own artifacts —
|
|
which composition variant travels — using the per-variant engagement the
|
|
interface reports.
|
|
|
|
## T03 — Find what fluid-core assumes about the Hall of Helix
|
|
|
|
```task
|
|
id: FLUID-WP-0009-T03
|
|
status: todo
|
|
priority: medium
|
|
```
|
|
|
|
Audit fluid-core for anything that assumes this particular campaign. The
|
|
conformance handover test already couples the two repositories deliberately;
|
|
check whether anything else does so by accident.
|
|
|
|
Known candidates to check rather than assume clean: default redaction patterns,
|
|
the classifier's thresholds, the fitness metric names, and whether
|
|
`examples/echo-interface` is doing enough work to be the general example it
|
|
claims to be.
|
|
|
|
## T04 — Reduce the Telegram case to a documented example
|
|
|
|
```task
|
|
id: FLUID-WP-0009-T04
|
|
status: todo
|
|
priority: low
|
|
```
|
|
|
|
Once the campaign lives elsewhere, `docs/handover/fluid-telegram.md` becomes a
|
|
worked example rather than a live handover: here is a real interface, here is
|
|
the pressure it faced, here is how the loop closed on it.
|
|
|
|
That is more valuable as documentation than it is as history, and it is the
|
|
form `fluid-x` and `fluid-substack` will want to read.
|
|
|
|
## T05 — Prove reuse with a second interface
|
|
|
|
```task
|
|
id: FLUID-WP-0009-T05
|
|
status: todo
|
|
priority: low
|
|
```
|
|
|
|
The real test of T03. Take `fluid-x` or `fluid-substack` from empty capability
|
|
canon to a published R-1, and record honestly how much of the fluid-telegram
|
|
handover transferred unchanged.
|
|
|
|
Whatever did not transfer is the accidental coupling, and finding it this way is
|
|
cheaper than arguing about it in advance.
|