Submit, moderate, read

WorkflowpieceCC-BY-4.0practiced By Campaign Hub

The library spine as an ordered path: a person submits, a person publishes, and a stranger reads and copies. A sensor may advise the middle step and cannot publish.

When to use

Use this workflow when you need the public path from a submission to a specimen a stranger can read, with the human publish step kept in the middle.

When not to

Do not collapse the three actors into one automatic pipeline. Do not let the sensor become the publisher. Do not start the path at a folder and call the folder a reader.

Author-attested

Original teaching specimen written for the Campaign Hub library. Not a transcript of a private run.

Community-submitted content. Prompts, skills, and agent instructions can contain hidden or malicious instructions (prompt injection). Review it before running it in any agent that has tool access, secrets, or the ability to spend money or send messages.
# Submit, moderate, read This file is a workflow: an ordered path from a trigger to a result. ## When to use Use this workflow to explain, or to implement, the public life of one specimen. It starts when a person has something to share. It ends when a stranger can read that specimen and copy the part they will reuse. Three actors stay visible: the person who submits, the person who publishes, and the stranger who reads. A sensor may sit beside the middle actor as advice. ## When not to Do not use this workflow as a fully automatic publisher. Removing the person from the middle step makes it a different path, and not this library's path. Do not use it for execution. The library holds specimens. It does not run them. Do not add accounts, payments, ratings, or comments to this spine. Those are other products. ## The specimen The artifact is this path. ```text name: submit-moderate-read trigger: a person has one specimen to offer the public shelf result: a stranger can open the published specimen and copy from it, without an account and without the author present steps: 1. Submit actor: a person action: hand the specimen to intake clerk: the intake clerk stores a pending row, or records a refusal state after: pending, or refused the submitter does not choose the public slug on this path 2. Moderate actor: a person action: read the pending specimen and approve or refuse sensor: may attach a reading before the decision the sensor may advise the sensor does not approve, publish, or change the kind state after approve: published state after refuse: not published 3. Read actor: a stranger action: open the published specimen and copy what they will reuse state after: unchanged; reading does not publish a second copy stop: the stranger can carry the specimen out, or the submission was refused named consumer of a published specimen: the stranger who reuses it a directory of files is storage, not the consumer ``` The order is the workflow. A publish that happens in step 1 has skipped moderation. A sensor that writes `published` has taken the person's step. Both are broken copies of this path. ## How a stranger checks it A stranger checks the path by walking it on paper, then against the system if one exists. 1. Point at step 1 and name the actor. It is a person, and the stored state is pending or refused. 2. Point at step 2 and name the actor. It is a person. Find the sensor. Its only verb is advise. If any sentence lets the sensor publish or relabel, the copy fails. 3. Point at step 3 and name the actor. It is a stranger who was not required to have an account. 4. Confirm the result is "can read and copy," and that nothing in the path executes the specimen. A diagram that merges all three steps into "the system publishes" fails this check. The three actors are the spine.

How a stranger checks it

Related

workflow submit publish read

view raw view JSON