coulomb/fluid-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document the pr- campaign repository convention
Some checks failed
ci / build (push) Failing after 22s
Details

Browse source 
Closes FLUID-WP-0009 T01. Writes down what a pr- repository is so the
second one need not be reverse-engineered from the first.

Keeps the workplan's insistence on naming propaganda alongside public
relations and promotion: the mechanism is identical in all three, and what
separates them is whether the campaign is accountable to something outside
itself -- a source it must not contradict, a named reviewer, a consent
basis it can lose.

Beyond the required contents, records the boundary table against fluid-*,
that a declared presence is brand and belongs to the campaign while the
credentials it produces belong to the interface, and that domain and topic
follow the subject being promoted rather than the activity -- the domains
are market sectors, and none of them is "marketing".

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1361245@bnt-lap001
Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a
This commit is contained in:
tegwick 2026-09-04 21:15:52 +02:00
parent 4819fd919a
commit f2330e68e0
2 changed files with 152 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
workplans/FLUID-WP-0009-campaign-repos-and-example-separation.md
View file

@ -46,7 +46,7 @@ the wrong place.
```task
id: FLUID-WP-0009-T01
status: todo
status: done
priority: medium
state_hub_task_id: "2a3aab85-e464-5b17-980f-1896ecd3794f"
```
@ -63,6 +63,16 @@ 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.
**Written: `docs/campaign-repositories.md` (2026-09-04.)** It adds a review step
to the list above, the boundary table against `fluid-*`, the registration rules
(domain and topic follow the *subject*, since the domains are market sectors and
none of them is "marketing"), and the point that a campaign may run its own FLUID
loop over its own artifacts without merging it into the interface's.
It states its own test: whether a second campaign can be created from the
document without reading `pr-hall-of-helix`. Until that happens it describes one
case rather than a general rule — the same caution T05 applies to the framework.
## T02 — Establish pr-hall-of-helix
```task