Deployment Modes

Publishing House supports three deployment modes. You choose during intake — the choice determines how much process your project goes through and where it ends up.

	Onboarded	Self-Published	Express
Purpose	RHDP catalog item	Your own content	One-off demo
Git repo	Yes	Yes	No
Gates	Hard (enforce quality)	Soft (advisory)	None
Jira	Automatic	No	No
Durability	Permanent	Permanent	Disposable

graph TD
    I["Intake"] --> V["Vetting"]

    V --> SR["Spec Refinement"] --> AP["Approval"]
    AP --> W["Writing"]
    AP --> AU["Automation"]
    W --> ED["Editing"]
    AU --> ED
    ED --> CR["Code Review"]
    ED --> SEC["Security Review"]
    CR --> E2E["E2E Testing"]
    SEC --> E2E
    E2E --> FR["Final Review"]
    FR --> PUB["Ready for Publishing"]

    V --> EXP["Environment Creation"]
    EXP --> HAND["Handoff"]

    style I fill:#1a73e8,color:#fff
    style V fill:#1a73e8,color:#fff
    style SR fill:#2a6496,color:#fff
    style AP fill:#d4a017,color:#000
    style W fill:#3c763d,color:#fff
    style AU fill:#3c763d,color:#fff
    style ED fill:#8a6d3b,color:#fff
    style CR fill:#31708f,color:#fff
    style SEC fill:#31708f,color:#fff
    style E2E fill:#8a6d3b,color:#fff
    style FR fill:#8a6d3b,color:#fff
    style PUB fill:#4caf50,color:#fff
    style EXP fill:#e8711a,color:#fff
    style HAND fill:#e8711a,color:#fff

Onboarded and self-published projects take the upper path (all 12 phases). Express takes the lower path after vetting.

---

Onboarded

For content going into the RHDP catalog.

What makes it different:

• Hard gates enforce quality at each phase boundary
• Jira Epic and tasks created automatically, synced as work progresses
• Content and automation built for you, ready to onboard
• All review phases required before publishing

Example:

You: /rhdp-publishing-house
PH:  What deployment mode?
You: onboarded

     → Intake captures requirements, generates spec and module outlines
     → RCARS checks for content overlap
     → Spec reviewed and approved (cannot self-approve)
     → Writer generates AsciiDoc modules
     → Automation builds catalog configuration + deployment code
     → Editor reviews against spec and Red Hat standards
     → Code review, security review, e2e testing, final review
     → Ready for publishing in the RHDP catalog

---

Self-Published

For content that won't be published in the RHDP catalog. You can still use RHDP to order and provision it — you just manage the lifecycle yourself.

What makes it different:

• Soft gates — PH flags issues but never blocks you from advancing
• No automatic Jira tracking
• You decide when it's ready

Example:

You: /rhdp-publishing-house
PH:  What deployment mode?
You: self-published

     → Same intake and spec process as onboarded
     → Same writing and editing tools
     → Gates produce findings but don't block — you choose when to advance
     → No Jira tasks created
     → You deploy using your own infrastructure

---

Express

For when you need a working demo environment quickly — a customer meeting next week, a conference next month. No full lab, no review process.

In development

The intake path for express mode exists and routes correctly. The environment creation skill is not yet built.

What makes it different:

• No git repo — state lives in Central only
• Minimal lifecycle: intake, vetting, then environment creation
• No writing, editing, or review phases
• Environment is disposable

If an express demo proves valuable enough to maintain, start a new onboarded or self-published project from scratch.

---

Choosing a Mode

PH presents all three during intake. Three questions to decide:

1. Is this going in the RHDP catalog? → Onboarded
2. Is this content you'll maintain but host yourself? → Self-published
3. Do you just need a demo environment? → Express