01 · INPUTS
Intent and content
Brands, briefs, authors, personas, topics, research, atoms, and source material.
BriefsBrandsAtomsResearch
Whole-system architecture
How Pearl Prime works
One shared intelligence platform feeds specialist production pipelines, with quality evidence controlling every release.
02 · SHARED PLATFORM
Plan and compose
Contracts, registries, planning, selection, composition, enrichment, and orchestration.
BookContractPlannerComposerModels
03 · PRODUCTION
Specialist pipelines
Each medium applies its own process while consuming shared content and governance.
BooksMangaAudioVideoSocial
04 · OUTPUTS
Validate and release
Structural gates, human acceptance, evidence, publishing, storefronts, and distribution.
QAEvidenceRelease
Diagram 1 · Whole-system map
What is Pearl Prime, end to end?
Six layers, one direction. Specialist production fans out into the four medium-specific pipelines before everything re-converges on quality.
Diagram 2 · Production lifecycle
How does an idea become a released product?
Every medium runs this same nine-step spine. What changes between Books, Manga, Audio, Video, and Social is only what "compose" and "enrich" mean for that format.
Books compose chapters.
Manga converts narrative into episodes and panels.
Audiobooks transform approved prose into speech.
Video transforms beats into scenes.
Social transforms ideas into platform-specific posts.
Diagram 3 · Content systems map
How do atoms, stories, exercises, evidence, and hooks relate?
A chapter job pulls from five parallel content systems, then composition and bridge-writing stitch them into one coherent chapter. Each system links to its own dashboard.
Diagram 4 · Quality and evidence model
What does "working" or "proven" mean?
A file existing is not the same claim as a system working. Every status badge in this portal maps to exactly one of these five stages — nothing else.
| State | Meaning |
|---|---|
| Designed | Specification or intended behavior exists. |
| Code-wired | Implementation is connected to the real path. |
| Executed-real | A real output was produced. |
| Operator-accepted | A human reviewed and accepted the output. |
| Production-repeating | It succeeds consistently under normal operation. |
Status colors across this portal always use this same vocabulary — a gate PASS is at most "code-wired," never "production-repeating."
Foundation
Shared platform
Configuration, content substrate, author/persona systems, models, queues, storage, and integrations.
Control
Quality and governance
Designed → code-wired → executed-real → operator-accepted → production-repeating.
Infrastructure
Where it runs
Gitea canonical, Pearl Star GPU services, Cloudflare delivery, model providers, and operator machines.
