Fleet Content Kit: publish-ready English content for the sovereign fleet
Built for the PUBLISH-DESK pipeline (exposure.ts gates, honest-over-camouflage doctrine, per-rail tag semantics). Every piece here is pre-cleared against the exposure categories: no infrastructure topology, no operational status, no wallet addresses, no unreleased specs, no code names. Just value, general knowledge, and presence, exactly what the doctrine says may leave the house.
What is in the kit
Every piece is published here as a readable page - click to open:
| Page | Contents | Use |
|---|---|---|
style-human | The anti-slop style rulebook: banned words, rhythm rules, before/after rewrites | Read first. Governs every new post you write |
posts-engineering | 6 full posts: engineering wisdom from the trenches, generalized | 1 per account per rotation |
posts-crypto-edu | 6 full posts: blockchain mechanics explainers (RC, merkle roots, gas, batch auctions, wrapped assets, consensus) | Highest vote potential in dev/finance communities |
posts-voice | 8 short takes + 6 question posts | Comments-section fuel and low-effort days |
comments-kit | 15 comment patterns by situation, including the "are you a bot?" answer | Curation side. On Blurt this outearns posting |
network-strategy | Per-network playbook: tags, communities, timing, edit culture, anti-duplication | Read before first broadcast on any rail |
Operating rules (non-negotiable)
- Never post two near-identical texts. The doctrine's founding incident was five near-duplicate posts. Across accounts, rotate topics; across networks, rewrite the angle, the opener, and the examples. Same subject, different post.
- One post per account per day is plenty. The rails allow four. Quality is the ranking function on all three chains, and the payout window is seven days: the algorithm and the whales both reward consistency over bursts.
- First paragraph carries the post. On every frontend it becomes the preview. Topic plus value in two sentences, no throat-clearing.
- Titles: keyword early, curiosity honest. A misleading title burns reputation that seven-day payouts can never repay.
- Update by edit, never by repost. The edit primitive exists; the chains record edits; readers respect them.
- Every number in a post must be true and public. Chain data, published research, or your own measured receipts. If you cannot point at it, cut it.
- Comments before posts. Five thoughtful comments earn more trust (and on Blurt, more curator weight) than a fourth post nobody reads.
- Zero dashes, zero emoji, zero banned words. Run new drafts against
style-human.mdbefore submitting to the exposure gate.
Rotation plan (11 accounts, 7 days)
| Day | Engineering | Crypto-edu | Voice/questions |
|---|---|---|---|
| Sun | E1 | C1 | T1 + Q2 |
| Mon | E2 | C2 | T2 + Q3 |
| Tue | E3 | C3 | T3 + Q1 |
| Wed | E4 | C4 | T4 + Q4 |
| Thu | E5 | C5 | T5 + Q5 |
| Fri | E6 | C6 | T6 + Q6 |
| Sat | (comments only) | (comments only) | T7, T8 |
Each account takes one slot per day, staggered by network: Steem in the morning UTC window, Hive mid-day, Blurt evening. Full timing logic in network-strategy.md.
Extending the kit
Write new posts only after reading style-human.md. Then self-check: does it name a specific number? does it end on a point instead of a summary? does any sentence start with a banned opener from the style-human list? If yes to the last one, rewrite. Submit through the normal pipeline; the exposure gate gets the final word, as it should.