Part 3 · Operate
Schema contracts
The per-channel rules a draft must satisfy. Real platform limits, not preferences.
01What it is
Each artifact type has a contract: minimum and maximum length, required elements, forbidden elements, a voice floor and structural limits. Fifteen ship as defaults and a venture can override one.
02Why it exists
The bounds are platform reality rather than taste. An X post over 280 characters cannot be posted. A LinkedIn post over 3,000 is cut mid-sentence by LinkedIn.
Keeping them as data rather than conditionals means a new channel is a new row. Keeping them per-venture-overridable means you can raise your own voice floor without touching anybody else's.
03How to use it
- 01Read the reference table to see what each channel demands.
- 02Raise the voice floor on a channel if drafts pass and still sound wrong.
- 03Do not lower a maximum below the platform limit. It is already the platform limit.
04What good looks like
- You give it
- A LinkedIn post of 900 characters with a 90-character hook and one link.
- You get
- Passes. Inside the bounds, hook inside its own limit, link count within the structure rule.
- Why
- The contract allows up to 3,000 characters, a 120-character hook and one link.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- A LinkedIn post with the link on the first line and five hashtags.
- You get
- Rejected twice over: a link in the first line and a hashtag count above the structural limit.
- Why
- Both are forbidden elements on that contract, because both suppress reach on that platform.
Derived from the rules in the code