xpager

xPager (OnePager)

Produce a three-page branded OnePager for a 31C product, module, or offering. Renders to PDF + HTML.

Variables

• product: name (default ODUN.ONE), with base+suffix split for the wordmark (e.g., ODUN + ONE)
• tagline: 1-2 sentence positioning statement
• audience: who the xPager is for (regulator, operator, investor, partner)
• stats: exactly 4 top-line data points
• capabilities: 4-6 capability cards (key, title, description)
• proof_points: 4 proof cards (key, title, description)
• contact: name, title, email, phone of the point of contact

Phase 0: Context Loading

Read:

• reference/corporate-style-guide.md - locked template, checklist (xPager section)
• .claude/rules/corporate-docs.md - guardrail
• .claude/rules/terminology.md - ODUN.ONE, DPI+, Five Principles
• reference/misha-voice.md - voice for taglines and descriptions
• Existing xPager reference: outputs/content/odun-one-xpager-2026/ for visual continuity

Phase 1: Classify and Confirm

Announce:

Using /xpager (OnePager template). PDF + HTML will be rendered. Full-bleed cover, locked wordmark with blue .ONE accent, stats bar, capability cards, proof cards, and brand footer applied.

Confirm product name, audience, and whether this is a fresh xPager or an update to an existing one.

Phase 2: Draft

Constraints:

• Cover tagline under 180 characters, no corporate jargon.
• Stats bar: exactly 4 data points. Use Voss precision on numeric values.
• Capability cards: 4-6. Each card's description 1-2 sentences, under 220 characters.
• Proof cards: exactly 4. the flagship deployment is a mandatory proof point for any ODUN.ONE xPager.
• Contact: use the actual executive issuing the xPager.
• Use "Tribe" never "team". Use "ODUN.ONE" never "Odun One" or "odun.one".

Do NOT attempt to rebuild the closing page in HTML - if a raster closing exists in outputs/content/odun-one-xpager-2026/extracted-assets/, reuse it; otherwise, the three-page layout suffices.

Phase 3: Present for Approval

Show:

• Cover preview (tagline + stats)
• Capability card grid
• Proof card grid
• Contact block

Run the authoring checklist from reference/corporate-style-guide.md (xPager section).

Wait for explicit approval before rendering. Hard stop.

Phase 4: Render

Assemble the JSON payload for the xpager schema. Write to outputs/documents/{sender-slug}/xpager/_work/data.json. Invoke:

python scripts/render-doctype.py --type xpager \
  --data outputs/documents/{sender-slug}/xpager/_work/data.json \
  --out outputs/documents/{sender-slug}/xpager/

Outputs: PDF + HTML. Both files are deliverables - HTML for web/preview, PDF for print and sharing.

Phase 5: Report

Full absolute paths of the PDF and HTML. State: "Word count: X. Hidden characters: clean."

NEVER

• Use decrypted traffic claims. ODUN.ONE classifies encrypted traffic via metadata and AI. Never "decrypts".
• Mention presence in sanctioned countries.
• Use round numbers in stats bar or pricing references.
• Use "team" - always "Tribe".
• Rebuild the PDF-extracted logotype in HTML. Use the white logo from datastore/brand/assets/logos/ only.
• Skip the hidden-character scan.