A campaign that ships one specimen
A one-page campaign whose product is a single specimen. It has one phase, one bead, a human publish gate, and a named reader.
When to use
Use this campaign when the product is one specimen and you need the phase, the bead, the publish gate, and the reader on a single page.
When not to
Do not stretch this page into a multi-product program. Do not drop the human gate, and do not name a directory as the reader of the result.
Author-attested
Original teaching specimen written for the Campaign Hub library. Not a transcript of a private run.
# A campaign that ships one specimen
This file is a campaign: phases, a bead, a gate, and a named reader, on one page.
## When to use
Use this page when the thing you are shipping is one specimen and you want the whole campaign visible at once. A reader should see the phase, the bead, the gate, and the person who consumes the result, without hunting through a stack of notes.
It is the smallest campaign that still has those parts.
## When not to
Do not use this page for a campaign that ships several products. Add beads only by writing a new campaign page. Do not quietly add a second deliverable under the same bead.
Do not remove the gate because the specimen "looks small." Small specimens still wait for a person before they are published. Do not name the output folder as the reader.
## The specimen
The artifact is this campaign. It is one page.
```text
Campaign: Ship one specimen
product: one specimen a stranger can reuse without the author present
reader: the stranger who reuses that specimen
reader_is_not: the directory that stores the file
phase: file
purpose: produce the specimen and hold it until a person publishes
bead:
deliverable: one specimen file
how_checked: the bead check exits 0 on that file, and a stranger can point at the specimen's own check
may_change: the one specimen file
must_not_touch: the roster, the seed, and every other specimen
gate: a person publishes
closed_while: the specimen is pending and no person has approved it
opens_when: a person approves
sensor: may advise the person before the decision
sensor_does_not: open the gate, publish, or change the kind
consumer:
output: the published specimen
reader: the stranger named above
same_place: the output and the reader are named in this block
stop: the stranger can reuse the specimen, or a person has refused it
icing: do not execute the specimen, and do not let a sensor publish
fuel_out: do not apply a half-finished schema change with no previous release to return to
```
The bead inside this page uses the four-field envelope. The gate is the specimen "A person publishes." The consumer block is the specimen "Name the consumer." This page composes them. It does not rewrite their rules. If this page and those specimens disagree, those specimens win on their own subjects, and this page should be edited to point at them again.
## How a stranger checks it
A stranger checks the page by finding four names.
1. The phase is named, and there is one phase.
2. The bead has `deliverable`, `how_checked`, `may_change`, and `must_not_touch`, each with a value.
3. The gate opens when a person approves, and the sensor is forbidden to open it.
4. The reader is a role, the stranger who reuses the specimen. If the only reader named is a folder, a bucket, or "the files," the campaign fails.
The page also fails if a second product appears, or if the stop condition is only "the file exists." Existence of the specimen file is not the campaign's finish line. The stranger's reuse is.
How a stranger checks it
- CAMP-1 The page names one phase, one bead with the four fields, a human publish gate, and a reader who is a role rather than a directory. Read the fenced campaign. Confirm phase, bead, gate, and reader are all present, the gate opens only on a person's approve, and the reader is the stranger who reuses the specimen.