Tiger Claw White Paper
Builds a branded white paper at one of three points on a scale. The cover and the
numbered confidentiality receipt are the fixed signature (generated by the build
script, identical every time). You author the body to fit the chosen variation.
The scale — pick one
variation |
Reader |
The question it answers |
Lead with |
science |
Researcher / skeptic |
"Is this rigorous and true?" |
Problem, method, evidence, data, references. Marketing is a quiet frame only. |
technology |
Technical buyer / leader evaluating |
"How does it work and will it hold up — and why care?" |
Architecture, data, security, isolation, maturity. Open + close on benefit. |
marketing |
Buyer |
"What's in it for me?" (every few seconds) |
Benefit, their pain, the outcome, proof, one CTA. Just enough tech to be credible. |
All three get the confidentiality receipt + control numbering. See REFERENCE.md
for the full doctrine of each variation, the brand system, and the body CSS classes.
Workflow
- Gather inputs (ask only what you can't infer): recipient, variation, the
single next step (CTA), and any facts to feature. Keep pricing out unless Brent says otherwise.
- Assign the control number. Read LEDGER.md, take the next number,
and append an entry (number, recipient, date, variation). Numbering is internal —
the recipient never learns the others exist.
- Ground-truth every claim against the source white papers / live state. Label
capabilities live / built-but-dark / pending honestly — never oversell. No emojis.
- Write the body as an HTML fragment of
<section class="sheet dark"> pages using
the documented classes (see REFERENCE.md and assets/body.example.html). ~2 sections
per page. Match tone + structure to the variation.
- Write the spec JSON (see
assets/spec.example.json) — cover meta, receipt clause,
bodyHtmlPath, outPath.
- Build:
node scripts/build-whitepaper.mjs <spec.json>
- VERIFY by reading the PDF pages as images — do not claim it rendered, look.
Watch for an overflow/blank page (a sheet exceeding 11in). If a sheet overflows,
move a section to a new sheet or trim spacing, then re-render. Confirm the receipt
sits on exactly one page.
- Deliver the PDF (copy to
~/Desktop/ if Brent wants to open it) and report
page count + what's in it.
Quick start
node scripts/build-whitepaper.mjs assets/spec.example.json # renders the worked example
The worked example (assets/body.example.html + spec.example.json) is the Example Recipient
marketing paper, No. 004 — copy its patterns.
Codex Runtime
Never expose or print secret, credential, or token values.
Mandatory dependencies:
Preflight each dependency using MCP/app capability discovery, CLI availability/version checks, read-only filesystem or Git checks for repositories, and provider auth-status commands without printing secrets, credentials, or tokens.
If any mandatory dependency is unavailable, stop and report a concise blocked state naming the missing dependency and the next action needed.
1---2name: tiger-whitepaper3description: Generate a branded Tiger Claw white paper as a print-ready PDF, anywhere on the technical-to-marketing scale — a science paper, a technology paper (with some marketing), or a marketing paper (with some technology). Every paper carries the same signature: a dark branded cover, a numbered + signable confidentiality receipt, the brand palette/fonts, bigger type, no emojis, and honest live/built/pending labeling. Use when Brent says "white paper", "make a white paper", "team white-label pitch", "science/technical white paper", references white-paper No. NNN, or asks to turn a pitch into a branded PDF for a leader/partner.4---56# Tiger Claw White Paper78Builds a branded white paper at one of three points on a scale. The cover and the9numbered confidentiality receipt are the fixed **signature** (generated by the build10script, identical every time). You author the body to fit the chosen variation.1112## The scale — pick one1314| `variation` | Reader | The question it answers | Lead with |15|---|---|---|---|16| `science` | Researcher / skeptic | "Is this rigorous and true?" | Problem, method, evidence, data, references. Marketing is a quiet frame only. |17| `technology` | Technical buyer / leader evaluating | "How does it work and will it hold up — and why care?" | Architecture, data, security, isolation, maturity. Open + close on benefit. |18| `marketing` | Buyer | "What's in it for me?" (every few seconds) | Benefit, their pain, the outcome, proof, one CTA. Just enough tech to be credible. |1920All three get the confidentiality receipt + control numbering. See [REFERENCE.md](REFERENCE.md)21for the full doctrine of each variation, the brand system, and the body CSS classes.2223## Workflow24251. **Gather inputs** (ask only what you can't infer): recipient, variation, the26 single next step (CTA), and any facts to feature. Keep pricing out unless Brent says otherwise.272. **Assign the control number.** Read [LEDGER.md](LEDGER.md), take the next number,28 and append an entry (number, recipient, date, variation). Numbering is internal —29 the recipient never learns the others exist.303. **Ground-truth every claim** against the source white papers / live state. Label31 capabilities **live / built-but-dark / pending** honestly — never oversell. No emojis.324. **Write the body** as an HTML fragment of `<section class="sheet dark">` pages using33 the documented classes (see REFERENCE.md and `assets/body.example.html`). ~2 sections34 per page. Match tone + structure to the variation.355. **Write the spec JSON** (see `assets/spec.example.json`) — cover meta, receipt clause,36 `bodyHtmlPath`, `outPath`.376. **Build:** `node scripts/build-whitepaper.mjs <spec.json>`387. **VERIFY by reading the PDF pages as images** — do not claim it rendered, look.39 Watch for an overflow/blank page (a sheet exceeding 11in). If a sheet overflows,40 move a section to a new sheet or trim spacing, then re-render. Confirm the receipt41 sits on exactly one page.428. **Deliver** the PDF (copy to `~/Desktop/` if Brent wants to open it) and report43 page count + what's in it.4445## Quick start4647```bash48node scripts/build-whitepaper.mjs assets/spec.example.json # renders the worked example49```5051The worked example (`assets/body.example.html` + `spec.example.json`) is the Example Recipient52marketing paper, No. 004 — copy its patterns.5354## Codex Runtime5556Never expose or print secret, credential, or token values.5758Mandatory dependencies:59- `Node.js`60- `Google Chrome`6162Preflight each dependency using MCP/app capability discovery, CLI availability/version checks, read-only filesystem or Git checks for repositories, and provider auth-status commands without printing secrets, credentials, or tokens.63If any mandatory dependency is unavailable, stop and report a concise blocked state naming the missing dependency and the next action needed.
bbrysonelite-max