Markdown carrier
How to carry any specimen as one markdown file: short front matter for the fields, then the body. The carrier adds no runtime, server, or package.
When to use
Use this carrier when a specimen needs to move as one file that a person can read, diff, and paste into the submit form, without installing a runner.
When not to
Do not add a runtime, a package manifest, or a server to the carrier. Do not split one specimen across several files and still call it this adapter.
Author-attested
Original teaching specimen written for the Campaign Hub library. Not a transcript of a private run.
# Markdown carrier
This file is an adapter: one markdown carrier, fields in front matter, prose in the body, no runtime.
## When to use
Use this adapter when you need to carry a specimen onto a harness that can read a markdown file, or into a form that a person fills by hand. The file holds the fields in a short front matter block and the teaching in the body under it.
One specimen, one file. A stranger can open it in any text editor.
## When not to
Do not turn the carrier into a project. No package file, no server, no runner that "executes the specimen." The library does not execute specimens, and this adapter does not sneak execution in through a build step.
Do not use the carrier to store a second, drifted copy of the roster. The front matter of a real filing still takes slug, title, and kind from the roster row.
## The specimen
The artifact is this file shape. The example is a toy rule so the shape is visible. It is not a roster row.
```markdown
---
schema: campaignhub.specimen/v1
slug: example-standing-rule
title: Example standing rule
kind: rule
license: CC-BY-4.0
maturity: practiced
audience_role: any
safety_class: public_teaching
shot: na
harness:
- generic
tags:
- example
- rule
use_when: Use the rule inside when a claim of done needs an observation.
avoid_when: Do not quote the rule in place of running the check.
provenance: Original teaching specimen written for the Campaign Hub library. Not a transcript of a private run.
---
# Example standing rule
## When to use
Use the rule when a model is about to claim the work is done.
## When not to
Leave the rule unused when no claim is being made.
## The specimen
Rule: a claim of done points at an observation a stranger can rerun.
## How a stranger checks it
Ask for a claim with no observation attached. The rule requires the words "not verified."
```
Front matter is the fields. The body is the specimen a person reads. The carrier adds no command to run, no port to bind, and no dependency to install. To submit, a person copies the fields into the form and the body into the body field. The workflow that receives them is "Submit, moderate, read." This adapter binds that path to a file. It does not become a fourth step.
## How a stranger checks it
A stranger checks the carrier by inspection.
1. The example is one fenced file, not a directory.
2. The file begins with a line that is exactly `---`, a block of `key: value` lines, and a closing `---`.
3. The body after the closing marker contains the specimen's prose, including when to use it and when not to.
4. Search the file for an install command, a server entrypoint, a port, or a runner. None of those belong. Finding one fails the copy.
5. The slug in the example is `example-standing-rule`. It is a shape demo. A real filing replaces that slug with a roster slug and does not add the example to the roster.
A carrier that needs a program to be "opened" is not this adapter.
How a stranger checks it
- CARRY-1 The carrier is one markdown file with front matter and a body, and it names no runtime, server, or package install. Open the fenced file. Confirm it starts with front matter between --- lines, the body follows, and the file contains no install command, port, or server entrypoint.