2.1 Module Overview

Each module is a blueprint bundle: a base prompt, sub-prompts, style tokens, acceptance tests, and export profiles (WP/Notion).

2.2 Style Tokens (Tone • Voice • Rhythm • Length)

Attach these tokens to every base prompt. They act like a lint + formatter for prose.

Reusable Style Snippet (append to any prompt):

[STYLE TOKENS]
TONE=Direct-Expert; VOICE=Made2Master; STRUCT=H2/H3+bullets; LEN=220w/section;
NO-REPEAT; READ=Grade8-10; CTA=Subtle
— Enforce: reject overlong sections; convert lists; shingle-check repetition.
    

2.3 Evidence & Compliance Policy

Allowed: official game manuals, publicly released updates/patch notes, developer blogs, museum & academic sources, reputable journalism. Disallowed: leaks, datamining, exploits, reverse engineering, cheat-enabling guidance.

• Attribution: Keep citations in metadata (JSON-LD/notes field); do not inline to avoid overflow.
• Fiction vs Fact: For History Engine, separate speculative flavor from sourced claims.
• Player Safety: No harassment, doxxing, or evasion tactics. Respect platform ToS.

[EVIDENCE RULE]
- Cite source title, org, year, URL in metadata only (JSON-LD "citation" or Article "backmatter").
- Mark any uncertain claim with CONFIDENCE=Low and remove from public render if not verifiable.
    

2.4 Schema Blocks & Anchor Rules

Every page ships with Article JSON-LD. Add FAQPage for Q&A and BreadcrumbList for navigation. Anchors are kebab-case, no renames.

• Required anchors: #executive-summary, #sdk-architecture, #writer-onboarding, #systems-guide, #film-module, #history-engine, #rp-city, #siege-os, #packaging, #execution, #faq.
• Slug policy: consistent: /blogs/news/prompt-os
• Alt text: describe function + context (e.g., “Shot list example table for desert convoy”).

[SCHEMA-PRESET]
- Article: headline, description, author, datePublished/Modified, citation[]
- FAQPage: 6–12 questions, short answers (<80 words)
- BreadcrumbList: Home > Creator Studio > Prompt OS
    

2.5 Prompts as APIs (Versioning • Tests • Logs)

Every base prompt is an endpoint. Version them, test outputs against golden samples, and log parameters for reproducibility.

[BASE PROMPT ENVELOPE v1]
GOAL: {what_to_generate}
CONTEXT: {game_title} | {module} | {audience} | {skill_tier}
CONSTRAINTS: ToS-safe; no leaks/exploits; evidence=allowed_sources_only
STYLE: {style_tokens}
STRUCTURE: {required_sections}
QUALITY BAR: {acceptance_tests}
EXPORT: {format_targets} (WP/Notion/Markdown tables)
LOG: write params, model, time, sha256(content)
    

2.6 QA, Golden Samples & Review Loops

Build a Golden Library: the best-in-class outputs per module. Compare new drafts with diff checks (structure, headings, tables, claims).

• Lint: heading levels, max section length, table presence for numerical content.
• Fact Check: spot-check 3 claims/section; flag unsourced items to metadata or remove.
• Style Pass: tokens enforced; shingle score < threshold for repetition.
• Pre-Publish: schema validation; anchors resolved; alt text present; mobile test (320px).

[QA-CHECKLIST v1]
- STRUCT: H2/H3 correct; sections ≤220w; bullets & tables used
- STYLE: tokens enforced; no passive drift; CTA ≤1/800w
- EVIDENCE: allowed-only; citations in metadata; fiction labeled
- COMPLIANCE: ToS-safe; no reverse engineering/exploits/cheats
- ACCESSIBILITY: alt text; heading order; color contrast; link names
- MOBILE: 320–414px verified; no overflow; buttons ≥44px
- SCHEMA: Article + FAQPage + BreadcrumbList present
    

2.7 Production: Filenames, Calendar, and Exports

Ship predictably with a naming grid and content cadence.

• Weekly cadence: 2 modules + 1 golden refresh.
• Backlog: track per-module deficits (tables/glossaries missing).

2.8 Reusable Prompt Blueprints (Copy • Paste • Run)

Blueprint A — Systems Guide (Stealth & Outposts)

[ENDPOINT] systems.guide/v1/generate
GOAL: Create a mastery-focused guide for {game}:{topic} (e.g., "Stealth in Desert Outposts")
AUDIENCE: Intermediate players; fast application in-game
CONSTRAINTS: ToS-safe; no exploits; evidence from public official sources only
STYLE: TONE=Direct-Expert; VOICE=Made2Master; STRUCT=H2/H3+bullets; LEN=220w/section; NO-REPEAT
REQUIRED SECTIONS:
- Mechanics Snapshot (UI terms, detection, sound/light)
- Tactics by Scenario (day/night, weather, patrol density)
- 5x Plays That Win (step-by-step, timings)
- Loadout & Tools Matrix (table)
- Failure Recovery (escape, reset, heat)
ACCEPTANCE TESTS: tables present; no banned language; glossary present; mobile-ready
EXPORT: WP-HTML + MD table
    

Blueprint B — Virtual Film Pack (Shot List & Dialogue)

[ENDPOINT] film.pack/v1/scene
GOAL: Generate a cinematic pack for {scene_archetype} in {world_region}
STYLE: TONE=Direct-Expert; STRUCT=beats→shots→dialogue→audio
SECTIONS:
- Beat Sheet (6–8 beats)
- Shot List (table: #, lens, movement, subject, est. seconds)
- Dialogue Polish (max 8 lines; subtext notes)
- Score & Foley Cues (ambient layers; SFX moments)
QA: lens terms valid; duration sums to target ±15%; no copyrighted script content
    

Blueprint C — History Engine (Lesson Pack)

[ENDPOINT] history.engine/v1/lesson
GOAL: Build a Discovery-Tour-aligned lesson on {topic, era}
EVIDENCE: museums/universities/journals; separate fiction vs fact
SECTIONS:
- Learning Objectives (SMART)
- Primary vs Secondary Sources (table)
- Site Walkthrough (waypoints; 2–3 artifacts)
- Activities (15, 30, 60-min variants)
- Glossary (10 terms)
QA: citations in metadata; activity timings; accessibility note (alt text)
    

Blueprint D — RP City/Server OS (Codebook)

[ENDPOINT] rp.os/v1/codebook
GOAL: Draft fair-lane rules for {server_name} consistent with {platform_ToS}
SECTIONS:
- Rights & Consent (player safety)
- Laws & Sanctions Ladder (table)
- Economy Knobs (income sinks/sources; caps)
- Staff SOPs (tickets, evidence, appeals)
- Transparency & Logs (public monthly metrics)
QA: ToS-safe; no real-world evasion; clear reporting and appeal windows
    

Blueprint E — Siege Team OS (Comms • VOD • Drills)

[ENDPOINT] siege.team/v1/playbook
GOAL: Produce a comms-first playbook for {rank_range} on {maps[]}
SECTIONS:
- Roles & Brevity Codes
- Round Templates (exec/retake/anchor)
- Utility Tracking Sheet (table)
- VOD Review Rubric (per role)
- Scrim Calendar & KPIs
QA: tournament-safe language; no cheats/macros; drill steps are time-bound and measurable
    

2.9 Compliance Guardrails (Non-Negotiable)

• No reverse engineering or technical bypass content.
• No datamining/leaks (unreleased material is prohibited).
• No exploits/cheats/macros or instructions that enable them.
• Respect IP & copyrights; use official art only with permission.
• Player safety: zero tolerance for harassment/doxxing/targeting.

Failure to meet guardrails = auto-reject in QA.

2.10 Interop & Packaging

• WP Export: semantic HTML; tables as <table> (no images of tables).
• Notion Export: MD with fences; headings preserved; anchors listed up top.
• Assets: alt-text pack (CSV: filename, alt, caption, credit).
• Robots/Sitemap: index,follow; update lastmod on publish.
• Internal Links: /prompt-os, /creator/studio, /education/history-engine

3.1 Orientation: Day One

New contributors start with a two-hour ramp. Goal: embed the Made2Master voice and compliance reflexes immediately.

1. Read the Style Token Primer (Part 2.2) and run two practice prompts.
2. Compare drafts against Golden Samples in the library; mark drift.
3. Complete the Evidence Drill: separate fiction vs fact for a short history entry.
4. Submit outputs via Lint & QA Bot; review error log together.

Result: every writer leaves Day One knowing the exact acceptance bar.

3.2 Quick-Start Pack

The pack is delivered as a Notion page or zip. Contents:

• Style Tokens.md — enforcement rules, reusable snippet.
• Compliance.pdf — ToS guardrails, disallowed categories.
• Golden Samples — one per module (HTML + MD).
• QA Checklist.csv — tick-box for every section.
• Export Templates — WP HTML boilerplate, Notion MD boilerplate.

Distribution note: always watermarked with Made2MasterAI and versioned (e.g., v1.2, lastmod date).

3.3 Golden Sample Library

The Golden Library anchors quality. Each sample is a benchmark output: structured, token-clean, evidence-logged.

• Systems Guide (Stealth) — 1,200 words, dense tables, zero fluff.
• Virtual Film Pack (Market Scene) — full beat sheet, shot list, dialogue cues.
• History Engine (Greek Agora) — lesson plan, museum pairing, glossary.
• RP City OS (Faction Law) — codebook with sanctions ladder table.
• Siege Team OS (Chalet Defense) — comms playbook, utility tracker.

Writers compare new drafts against these samples. Diff logs flag deviations in structure, tone, or compliance.

3.4 QA Workflow

QA is a multi-stage gate. Each stage has non-negotiable checks:

1. Lint Pass: heading hierarchy, section length ≤220 words, bullets/tables enforced.
2. Fact Pass: 3 random claims checked per section. Unverifiable → remove or log in metadata.
3. Style Pass: tokens applied; shingle check prevents repetition drift.
4. Compliance Gate: confirm no exploits, leaks, cheats, or IP misuse.
5. Accessibility Scan: alt text, color contrast, ARIA roles, mobile viewport check.
6. Pre-Publish: schema validated, anchors resolved, robots.txt indexable, sitemap lastmod updated.

[QA-CHECK v2]
- STRUCT: H2/H3 valid; bullets used; section ≤220 words
- STYLE: tokens enforced; CTA ≤1 per 800 words
- FACT: 3 spot-checks per section; metadata citations only
- COMPLIANCE: ToS guardrails clean
- ACCESS: alt text, headings, ARIA labels, no overflow at 320px
- SCHEMA: Article + FAQPage + BreadcrumbList validated
    

3.5 Writer Progression Path

Writers level up via execution tiers:

• T1 — Apprentice: 3 practice prompts; review required for all drafts.
• T2 — Contributor: 10+ accepted outputs; trusted for single-module work.
• T3 — Architect: cross-module mastery; can create new Golden Samples.

Promotion = consistency. Drift = reset.

3.6 Review Loops & Feedback

Reviews are not bureaucracy—they are closed-loop corrections. Each draft goes through:

• Peer Review: fellow writer checks structure + style only.
• Editor Review: QA specialist runs compliance + evidence filter.
• Founder Review: Festus Joe Addai signs off on Golden Sample candidates.

Every rejection must include precise feedback with corrected snippet, not vague notes.

4.1 Stealth Systems

Stealth mechanics are universal: vision cones, sound propagation, suspicion meters. This blueprint outputs mastery guides that strip fluff and explain how to stay unseen.

[ENDPOINT] systems.guide/v1/stealth
GOAL: Create a mastery-focused stealth guide for {game}:{biome/region}
CONSTRAINTS: ToS-safe; only official UI mechanics (no exploits)
STYLE: TONE=Direct-Expert; STRUCT=H2/H3+bullets; LEN=220w/section
SECTIONS:
- Mechanics Snapshot (cones, suspicion, sound radius, cover states)
- Tactics by Scenario (night vs day; rain vs clear)
- 5 Win Plays (step-by-step, timings, fallback)
- Loadout Matrix (table: tool, effect, cooldown, best use)
- Recovery Path (escape, reset heat, safe zones)
QA: tables required; no banned phrases; glossary present
EXPORT: WP-HTML + MD
    

Sample Loadout Matrix (Stealth)

4.2 Wanted Systems

Wanted mechanics = escalation ladders. The SDK enforces clarity: explain how notoriety rises, how it decays, and how players reset heat.

[ENDPOINT] systems.guide/v1/wanted
GOAL: Explain the wanted system for {game}
CONSTRAINTS: ToS-safe; no exploits; only official mechanics
SECTIONS:
- Notoriety Tiers (table: tier, trigger, NPC response, escape difficulty)
- Escalation Flow (diagram/table: actions → tier shift)
- Reset Conditions (cooldown, hiding, surrender, bribery)
- 3 Win Plays: how to drop heat fast
QA: table must map tier names → official UI; no “mod-only” content
EXPORT: WP-HTML + MD
    

Sample Notoriety Tiers

4.3 Outpost Systems

Outposts = the repeatable mastery puzzle. The blueprint ensures guides emphasize scouting, disruption, and layered clears.

[ENDPOINT] systems.guide/v1/outpost
GOAL: Produce a tactics guide for clearing {game}:{outpost/fort}
SECTIONS:
- Recon Phase (map markers, patrol routes, entry points)
- Entry Tactics (night/day, tool choice, distractions)
- 5 Win Plays (specific clears, chained actions, fallback paths)
- Risk Matrix (table: tactic, reward, risk, contingency)
- Post-Clear Loop (loot, reset, respawn timers)
QA: recon map notes must use public UI only; reward loops accurate
EXPORT: WP-HTML + MD
    

Sample Risk Matrix (Outposts)

4.4 QA Rules for Systems Module

• 📊 Tables required for loadouts, notoriety tiers, risk matrices.
• 🛡 No exploit/cheat references; only official UI mechanics.
• 📚 Glossary added: detection, suspicion, notoriety, patrol, cooldown.
• 📱 Mobile test: no overflow, tables scroll horizontally.
• 🔗 Export tested in WP + Notion; anchors preserved.

5.1 Film Pack Blueprint

[ENDPOINT] film.pack/v1/scene
GOAL: Generate a cinematic pack for {scene_archetype} in {game}:{region}
STYLE: TONE=Direct-Expert; STRUCT=beats→shots→dialogue→audio
CONSTRAINTS: ToS-safe; no copyrighted material
SECTIONS:
- Beat Sheet (6–8 beats; 1-2 sentences each)
- Shot List (table: #, lens, movement, subject, est. seconds)
- Dialogue Polish (≤8 lines; subtext notes; original phrasing only)
- Score & Foley Cues (ambient layers; key SFX; emotional hit)
QA: lens terms valid; durations sum to target ±15%; dialogue not copied from IP
EXPORT: WP-HTML + MD
    

5.2 Beat Sheet (Sample)

Beat sheets provide the skeleton of the scene. Each beat is a pulse: one event, one shift in mood or motion.

1. Arrival: Hero enters crowded bazaar; soundscape swells.
2. Foreshadow: Suspicious figures track from balcony.
3. Collision: A merchant cart blocks path; tension rises.
4. Reveal: Antagonist steps into light; crowd parts.
5. Chase Spark: Guards shout; hero bolts through stalls.
6. Close Call: Narrow escape through alleyway gap.
7. Resolution: Safe roof perch; breath slows; city glows below.

5.3 Shot List (Sample)

Shot lists lock cinematics into technical execution. They must include lens, movement, subject, and estimated time.

5.4 Dialogue Polish (Sample)

Dialogue must be tight, subtext-aware, and original. Never copy in-game or copyrighted lines.

• Antagonist: "Running again? That’s all you ever do."
• Hero: "Better running than rotting beside you."
• Guard (off-screen): "Seal the exits!"
• Hero (mutter): "One step ahead… if the rooftops hold."

Note: subtext = Hero refuses to submit; antagonist frames flight as weakness.

5.5 Score & Foley Cues (Sample)

Sound makes the cut stick. Cue packs provide emotional anchors:

• Ambient: Market chatter, livestock, distant bells.
• Score: Tense strings swell at Beat 4 (Reveal).
• SFX: Cart crash at Beat 3; guard boots at Beat 5.
• Resolution: Wind hush + single oud note as camera cranes up.

5.6 QA Rules for Film Module

• 🎥 Shot list tables required; lens/movement valid film terms.
• 📑 Dialogue ≤8 lines per pack; original phrasing only.
• 🎧 Score cues use mood tags, not copyrighted titles.
• 📱 Mobile test: tables scroll; no text overflow.
• 🔗 Metadata logs all source inspirations in citations.json.

6.1 History Engine Blueprint

[ENDPOINT] history.engine/v1/lesson
GOAL: Build a Discovery-Tour-aligned lesson on {topic, era}
AUDIENCE: educators, students, creators
EVIDENCE: museums/universities/journals; separate fiction vs fact
STYLE: TONE=Direct-Expert; STRUCT=objectives→sources→walkthrough→activities→glossary
SECTIONS:
- Learning Objectives (SMART; max 5)
- Primary vs Secondary Sources (table)
- Site Walkthrough (waypoints + artifacts)
- Activities (15, 30, 60-min variants)
- Glossary (10 key terms)
QA: citations logged in metadata; fiction tagged; glossary required
EXPORT: WP-HTML + MD
    

6.2 Learning Objectives (Sample)

• Identify three architectural features of the Athenian Agora.
• Explain the difference between primary and secondary historical sources.
• Compare marketplace trade in ancient Athens with modern urban markets.
• Analyze how public spaces reflected civic identity.

6.3 Primary vs Secondary Sources (Sample Table)

6.4 Site Walkthrough (Sample)

A guided walkthrough provides waypoints + artifact cards. Example: Athenian Agora.

1. Waypoint 1 — Stoa of Attalos: Columns, civic meeting hall.
2. Waypoint 2 — Agora Square: Market hub; currency exchanges.
3. Waypoint 3 — Temple of Hephaestus: Craft guild patron site.

Artifact Card: Bronze coin with owl engraving. Notes: linked to Athena, symbol of wisdom and civic identity.

6.5 Classroom Activities (Sample)

• 15 min: Quick compare: Agora coin vs modern banknote.
• 30 min: Group debate: role of public squares in civic identity.
• 60 min: Research & present: 3 artifacts from Discovery Tour vs museum catalog.

6.6 Glossary (Sample Terms)

• Agora: Central market and civic square in ancient Greece.
• Stoa: Covered walkway or portico for gatherings.
• Polis: Greek city-state.
• Ostracism: Civic practice of temporary exile.
• Hephaestus: God of metalwork and craftsmanship.

6.7 QA Rules for History Module

• 🏛 Sources table mandatory (primary vs secondary).
• 📚 All citations logged in metadata JSON (not inline).
• 🛡 Fiction tagged clearly as creative framing.
• 🎒 Activities provide short, medium, long formats.
• 📱 Mobile: tables scroll cleanly; glossary lists readable.

7.1 RP OS Blueprint

[ENDPOINT] rp.os/v1/codebook
GOAL: Draft a fair-lane governance OS for {server_name} on {platform}
CONSTRAINTS: ToS-safe; no real-world evasion; respect platform rules
SECTIONS:
- Rights & Consent (player safety, no harassment, no doxxing)
- Laws & Sanctions Ladder (infractions → penalties)
- Economy Knobs (income sinks, sources, caps)
- Staff SOPs (tickets, evidence, appeals)
- Transparency & Logs (monthly public metrics)
QA: all laws server-only; economy balanced; sanctions ladder clear
EXPORT: WP-HTML + MD
    

7.2 Rights & Consent (Sample)

• 🔒 Privacy: No recording or sharing without consent.
• 🛡 Safety: No harassment, hate speech, or targeted abuse.
• 🎭 Consent: Major RP arcs (kidnap, trial, faction war) require mutual agreement.
• 📜 Transparency: Admin decisions logged and visible in public channels.

7.3 Laws & Sanctions Ladder (Sample)

7.4 Economy Knobs (Sample)

Server economies collapse if left unchecked. The SDK enforces balance with income sources, sinks, and caps.

7.5 Staff SOPs (Sample)

• 🎫 Tickets: All disputes filed via form with timestamps + evidence.
• 📂 Evidence: Screenshots + logs stored in encrypted drive.
• 🧾 Appeals: Players may appeal within 7 days; decision logged publicly.
• 📊 Metrics: Publish monthly dashboard: strikes, bans, appeals outcome.

7.6 Transparency & Logs

A healthy RP server publishes monthly governance reports:

• # bans issued
• # disputes filed + resolved
• # appeals upheld vs denied
• # economy balance tweaks (jobs, rents, caps)

Logs are made public (Discord pinned / website dashboard) for trust and retention.

7.7 QA Rules for RP OS Module

• ⚖ Sanctions ladder must escalate clearly (warning → fine → ban).
• 💰 Economy knobs balanced (sources vs sinks).
• 🛡 No real-world financial advice, laundering, or evasion tactics.
• 📜 Rights & Consent section mandatory in every draft.
• 📱 Mobile: all tables scroll cleanly at 320px width.

8.1 Siege OS Blueprint

[ENDPOINT] siege.team/v1/playbook
GOAL: Produce a comms-first playbook for {rank_range} on {maps[]}
STYLE: TONE=Direct-Expert; STRUCT=roles→rounds→utility→VOD→scrim
CONSTRAINTS: ToS-safe; esports-legal; no cheats/macros
SECTIONS:
- Roles & Brevity Codes
- Round Templates (execute/retake/anchor)
- Utility Tracking Sheet (operators, gadgets, timing)
- VOD Review Rubric (per role)
- Scrim Calendar & KPIs
QA: brevity list required; tables present; no disallowed terms
EXPORT: WP-HTML + MD
    

8.2 Roles & Brevity Codes (Sample)

Roles prevent overlap; brevity codes cut comms to seconds.

• IGL (In-Game Leader): sets strat call, mid-round pivots.
• Entry: first in, frag pressure, info feed.
• Flex: fills gaps, rotates between entry/support.
• Anchor: holds site, utility defense.
• Support: drones, cams, utility timing.

Brevity Codes:

• “One HP” = enemy nearly dead.
• “Rotate A/B” = shift site immediately.
• “Stack” = group push, no splits.
• “Trade” = guarantee refrag if entry falls.

8.3 Round Templates (Sample)

Round templates keep squads synchronized. Each includes execute, retake, and anchor phases.

8.4 Utility Tracking Sheet (Sample)

Utility decides rounds. This sheet tracks operator gadgets and timing.

8.5 VOD Review Rubric (Sample)

VOD review turns play into data. Each role has its own rubric.

• IGL: Were callouts timely? Did team pivot after lost entry?
• Entry: Did entry frag trade? Drone ahead? Communicate pressure?
• Anchor: Was utility layered? Did cams feed info late round?
• Support: Were drones alive at 30s? Were cams properly rotated?

8.6 Scrim Calendar & KPIs (Sample)

• Weekly: 3 scrims (2hr each) = 6 hrs of team time.
• Monthly: 2 VOD reviews + 1 role swap drill.
• KPI: win % in executes, time-to-plant success, utility wasted per round.

8.7 QA Rules for Siege OS Module

• 🗣 Brevity code list mandatory.
• 📑 Round templates table required.
• 🛡 No references to cheats, macros, exploits.
• 📊 Utility tracker validated against operators used.
• 📱 Mobile test: scrollable tables, no overflow.

9.1 Export Formats

Outputs must ship in two formats:

• Shopify/WP HTML: semantic tags, responsive tables, ARIA roles.
• Notion MD: fenced code, preserved H2/H3, bullet → list.

[EXPORT RULES]
- HTML: use <section>, <article>, <table>, <ul> only
- MD: headers (#, ##, ###), fenced code (```) for prompts
- Tables: always real tables; no images of tables
- Anchors: stable IDs (#executive-summary, etc.)
    

9.2 File Naming Grid

Predictable filenames prevent chaos. Use the Made2Master pattern:

9.3 Alt-Text Packs

Accessibility = SEO. Every visual ships with a CSV:

filename,alt_text,caption,credit
systems-stealth-loadout-1200.webp,"Loadout matrix showing stealth tools","Stealth tool reference table","Made2MasterAI"
film-shotlist-desert-1200.webp,"Shot list table for desert chase scene","Cinematic shot breakdown","Made2MasterAI"
history-sources-table-1200.webp,"Primary vs secondary source table","Educational reference","Oxford Handbook, British Museum"
    

9.4 Schema Bundles

Schema is exported in JSON-LD blocks, bundled per module. Required:

• Article: headline, author, datePublished, citations.
• FAQPage: 6–12 questions, ≤80 words each answer.
• BreadcrumbList: Home → Studio → Prompt OS.

[SCHEMA-PACK]
- {module}-article.json
- {module}-faq.json
- {module}-breadcrumb.json
    

9.5 Review Log

Every output includes a review log documenting checks:

• ✅ QA passed (struct, style, compliance)
• ✅ Mobile test (320px, 414px)
• ✅ Schema validated
• ✅ Alt-text pack complete
• ✅ Robots/sitemap updated (index,follow, lastmod set)

9.6 Publishing Pipeline

The packaging pipeline is a repeatable 6-step process:

1. Generate: run prompt with style tokens + compliance rules.
2. QA Pass: lint, fact check, mobile test.
3. Export: HTML + MD with stable anchors.
4. Bundle: schema + alt-text CSV + filenames.
5. Review: golden sample diff + review log.
6. Publish: upload to WP/Shopify/Notion; update sitemap lastmod.

10.1 Daily Checklist

1. Day 1 — Setup & Orientation
   - Distribute Quick-Start Pack (tokens, guardrails, golden samples).
   - Onboard writers; run 2 practice prompts.
   - Confirm schema + alt-text templates.
2. Day 2 — Systems Guide Module
   - Generate Stealth, Wanted, Outpost drafts.
   - QA pass: section length, tables, glossary.
   - Compare against Systems golden sample.
3. Day 3 — Virtual Film Module
   - Produce 1 cinematic pack (beat sheet + shot list).
   - Verify dialogue originality.
   - Export to WP/Notion.
4. Day 4 — History Engine Module
   - Build lesson pack (objectives, sources table, activities).
   - Metadata log citations.
   - QA separation of fact vs fiction.
5. Day 5 — RP OS Module
   - Draft codebook (laws, sanctions ladder, economy knobs).
   - Publish staff SOPs and rights & consent rules.
   - Transparency log template created.
6. Day 6 — Siege OS Module
   - Create comms playbook + round template.
   - QA brevity codes + utility tracker.
   - Upload VOD review rubric to Notion.
7. Day 7 — Packaging & Launch
   - Bundle alt-text CSV, schema, filenames.
   - Final QA review log completed.
   - Publish to Shopify/WP; update sitemap lastmod.
   - Golden sample refresh; mark v1.0 release.

10.2 Alternative Rollouts

Not every team runs on a 7-day cadence. The OS supports faster or slower tracks:

• Fast Track (3-Day): Merge Systems + Film on Day 2; History + RP + Siege on Day 3. Requires veteran writers only.
• Deep Track (14-Day): Assign 2 days per module; extra QA + class testing for History Engine; ideal for educators.

10.3 Golden Sample Sync

Golden samples are refreshed every 48 hours. Writers run diff checks to ensure outputs haven’t drifted in tone, structure, or compliance.

10.4 Final Review Loop

• ✅ Founder Review (Festus Joe Addai) signs off on v1.0 samples.
• ✅ Schema validated via Google Rich Results Test.
• ✅ Mobile audit: 320px + 414px verified.
• ✅ Robots/sitemap updated with index,follow.