Ringization playbook

Use Founder / Developer tabs in the docs sidebar to filter this page. Shared sections apply to both audiences.

Status: This page is the long-form white-label ringization SSOT for settlers and integrators. The Order Lab Playbook tab is the per-order checklist; this article is the methodology. Product steps also live in code at features/crm/lab/ringization-playbook.ts (seeded into the project room on integrator assign).

Ringization means shipping a clone-local feature overlay on Layer1 ring/web — brand, presets, and optional Tier-3 domain modules — without editing the platform tree (and without treating ring-platform-org as your vertical). Build merge: platform copy → tmp, then clone overlay overwrite (ringdom-clone-build / Forgejo Lab path).

Surface	Role
This playbook	Full vertical / brand / Tier-1–3 methodology
Configuration playbook	Order Lab `?tab=playbook` — this order’s gates
Vertical presets	Named `entities` / `home` / productField catalogs
Customization guide	Config-first branding + thin exclude hygiene
Owner Project Lab	Buyer `/my-orders` · integrator `/my-jobs` chrome

Previous habit	Ring equivalent
Fork all of platform into `ring-*`	Thin `ring-*/web/` overlay + `ringdom-clone-build`
Patch `lib/i18n.ts` / `home-wrapper` per brand	Overlay `lib/overlay/registry.ts` + `features/<id>/`
Nest product under `features.n9life: true`	Top-level `"n9life": { … }` domain block
Exclude whole `lib/` or `lib/overlay/`	Exclude `web/lib/overlay/registry.ts` plug only (+ domain dirs)
`reggie-ringize` plan files as factory	`reggie_autonomous_clone` → merge → forge

Settler pipeline (shared)

Calculator → paid project_order
Order Project Config — home.preset, domainFeatureId, brand fields
Integrator assign → playbook markdown seeded in the project room (PLAYBOOK_SEED_MARKER)
Factory — reggie_autonomous_clone (thin disk overlay) → Forgejo ringdom-clones/<slug> → BuildKit / Lab deploy

Buyers and integrators open the in-app panel on /my-orders/[id] and /my-jobs/[id] (?tab=playbook). Docs deep-link: /docs/customization/ringization-playbook.

Kingdom layers (Final-Split)

Hostname / AI-CONTEXT id ring-platform.org is not a checkout directory. Legacy flat clones (package at clone root) should migrate with layer2-clone-operator Mode B before endemic Tier-3 work.

Hard bans

No Cosmic Mirror / brand locales in platform home-wrapper or lib/i18n
Platform lib/overlay/registry.ts stays maps-empty; clones overlay registrations (maps only)
Platform lib/overlay/runtime.ts + types.ts are SSOT — never fork loaders onto the clone plug
Factory = reggie_autonomous_clone (not reggie-ringize plans)
Do not cp -r ring/web into the clone as a permanent fork

Recommended path

Use Cursor agent clone-customization-with-implementer (orchestrates layer2-clone-operator + ringization-implementer). It does not mutate until you approve the plan / dry-run.

Starter prompt (paste, fill blanks):

Ringize TARGET_CLONE=ring-<slug> with FEATURE_ID=<id> and MODE=A_new_thin | B_migrate_flat_to_web | C_ringize_existing. Overlay root = Final-Split web/. Follow .cursor/agents/layer2-clone-operator.md then .cursor/agents/ringization-implementer.md. Zero edits under ring/web/ or unsolicited ring-platform-org/. Update .reggie-propagate-exclude.json with web/… paths; exclude web/lib/overlay/registry.ts plug only. Dry-run ringdom-clone-build then pause for my approval before apply.

Inputs checklist

TARGET_CLONE, FEATURE_ID, display name / SEO
Home: platform | mvm-landing | <FEATURE_ID>-landing
Scope: thin brand | Tier-2 presets | full Tier-3
Locales (match clone env)

Reggie MCP (after overlay plan approved)

Scaffold / refresh thin overlay: reggie_autonomous_clone with dry_run: true first (clone_name, customization, optional skip_merge)
Propagate Layer1 shared code later with reggie_ringdom_propagate — source_project: "ring", dry_run: true, then review files_planned[] / files_rejected_list[] before dry_run: false
Compose always via ringdom-clone-build (ringdom-mcp) — platform → tmp, clone overlay wins

Manual path

Prerequisites: repo access to Ringdom, clone slug chosen, FEATURE_ID matching ^[a-z][a-z0-9]*$, MCP or local merge script available.

Classify Mode — New thin overlay (A), flat→web/ migrate (B), or ringize existing Final-Split (C). Prefer A/B via layer2-clone-operator before endemic product.
Tier-1 config — Under OVERLAY_ROOT (ring-<slug>/web): set ring-config.json clone.*, seo, home.preset, entity/product presets. For Tier-3 add top-level "<FEATURE_ID>": { "enabled": true, … } — not under boolean features.*.
Tier-2 presets — Prefer platform catalogs (agricultural, mvm-landing, …). Only add clone features/*/presets/<name>.ts + registry overlay when the niche is not upstream yet.
Tier-3 package — Create features/<FEATURE_ID>/ (i18n.ts → appendOverlayMessages, components, optional APIs). Overlay maps-only lib/overlay/registry.ts for i18n + home rail. Optional components/pages/home-presets/<FEATURE_ID>-landing.tsx.
Reggie exclude — At clone root .reggie-propagate-exclude.json: files[] + directories[] + locale_strategy: "new_keys_only". Final-Split paths use web/ prefixes. Always exclude the registry plug; never exclude types.ts / runtime.ts / whole lib/overlay/.
Build verify — ringdom-clone-build({ project_name: "ring-<slug>", dry_run: true }), then typecheck in the merge tmp / .dev-merge. Push forge ringdom-clones/<slug> only after dry-run review.

Exclude skeleton (Final-Split)

Allowlisted domain ids on Layer1 (OVERLAY_FEATURE_IDS): n9life, connect, greenfood, ringdom. New global ids need a separate platform PR to extend the allowlist; one-off clones still use the same id string + clone registry overlay.

Why this matters for your clone

You buy a vertical Ring, not a fork of the entire platform. Ringization keeps your brand and product modules in a thin overlay so platform upgrades (Auth.js, store, matcher, Lab) still flow via Reggie — without wiping Cosmic Mirror, Connect, or your logos.

Pay → Project Config

Set name, slogan, logo, home.preset, and domainFeatureId after calculator checkout.

Order Lab playbook tab

Per-order checklist beside secrets, wiki, and deploy gates.

Vertical presets

Prefer agricultural / mvm-landing shared niches before asking for custom code.

Implementation map

Concern	Verified path
In-app playbook SSOT	`ring-platform-org/web/features/crm/lab/ringization-playbook.ts`
Playbook UI panel	`…/ringization-playbook-panel.tsx`
Seed on assign	`seedRingizationPlaybookMessage` in `order-lab-chat-service.ts`
Project Config domain key	`domainFeatureId` → top-level overlay in `order-project-config.ts`
Layer1 empty registry	`ring/web/lib/overlay/registry.ts`
Socket SSOT	`ring/web/lib/overlay/types.ts`, `runtime.ts`
Feature id allowlist	`OVERLAY_FEATURE_IDS` in `lib/overlay/types.ts`

Frequently asked questions

Impact

Will platform upgrades wipe my Cosmic Mirror / domain UI?

No — if those paths are listed in .reggie-propagate-exclude.json. Missing excludes are how Reggie overwrites vertical code. Always exclude the registry plug + web/features/<id>/.

Do I need Tier-3 for every clone?

No. Prefer Tier-1 brand + Tier-2 named presets. Tier-3 only when you need clone-only UI, locales, or APIs.

Migration

Our clone is still flat (app/ at repo root). What first?

Run layer2-clone-operator Mode B: cut endemic files into web/, rewrite exclude with web/… prefixes, add scripts/merge-dev.sh, then Mode C ringize.

Can integrators edit `ring/web` to “fix” a missing brand string?

No. That is a hard ban. Fix via clone locales / overlay registry / home preset — or upstream a shared preset in a separate Layer1 PR.

Ops

Who deploys — buyer, integrator, or Reggie?

Deploy is integrator/admin from Order Lab. Reggie plans in chat and may scaffold/propagate; it does not deploy. See Owner Project Lab.

What is the factory for a new disk overlay?

reggie_autonomous_clone (thin overlay + optional merge). Not reggie-ringize plan artifacts.

Where do buyers see this playbook in-app?

/my-orders/[id]?tab=playbook (buyer) and /my-jobs/[id]?tab=playbook (integrator). Seeded chat uses PLAYBOOK_SEED_MARKER for idempotent re-assign.

Ringization playbook

Use Founder / Developer tabs in the docs sidebar to filter this page. Shared sections apply to both audiences.

Surface	Role
This playbook	Full vertical / brand / Tier-1–3 methodology
Configuration playbook	Order Lab `?tab=playbook` — this order’s gates
Vertical presets	Named `entities` / `home` / productField catalogs
Customization guide	Config-first branding + thin exclude hygiene
Owner Project Lab	Buyer `/my-orders` · integrator `/my-jobs` chrome

Previous habit	Ring equivalent
Fork all of platform into `ring-*`	Thin `ring-*/web/` overlay + `ringdom-clone-build`
Patch `lib/i18n.ts` / `home-wrapper` per brand	Overlay `lib/overlay/registry.ts` + `features/<id>/`
Nest product under `features.n9life: true`	Top-level `"n9life": { … }` domain block
Exclude whole `lib/` or `lib/overlay/`	Exclude `web/lib/overlay/registry.ts` plug only (+ domain dirs)
`reggie-ringize` plan files as factory	`reggie_autonomous_clone` → merge → forge

Settler pipeline (shared)

Calculator → paid project_order
Order Project Config — home.preset, domainFeatureId, brand fields
Integrator assign → playbook markdown seeded in the project room (PLAYBOOK_SEED_MARKER)
Factory — reggie_autonomous_clone (thin disk overlay) → Forgejo ringdom-clones/<slug> → BuildKit / Lab deploy

Buyers and integrators open the in-app panel on /my-orders/[id] and /my-jobs/[id] (?tab=playbook). Docs deep-link: /docs/customization/ringization-playbook.

Kingdom layers (Final-Split)

Hard bans

No Cosmic Mirror / brand locales in platform home-wrapper or lib/i18n
Platform lib/overlay/registry.ts stays maps-empty; clones overlay registrations (maps only)
Platform lib/overlay/runtime.ts + types.ts are SSOT — never fork loaders onto the clone plug
Factory = reggie_autonomous_clone (not reggie-ringize plans)
Do not cp -r ring/web into the clone as a permanent fork

Recommended path

Use Cursor agent clone-customization-with-implementer (orchestrates layer2-clone-operator + ringization-implementer). It does not mutate until you approve the plan / dry-run.

Starter prompt (paste, fill blanks):

Ringize TARGET_CLONE=ring-<slug> with FEATURE_ID=<id> and MODE=A_new_thin | B_migrate_flat_to_web | C_ringize_existing. Overlay root = Final-Split web/. Follow .cursor/agents/layer2-clone-operator.md then .cursor/agents/ringization-implementer.md. Zero edits under ring/web/ or unsolicited ring-platform-org/. Update .reggie-propagate-exclude.json with web/… paths; exclude web/lib/overlay/registry.ts plug only. Dry-run ringdom-clone-build then pause for my approval before apply.

Inputs checklist

TARGET_CLONE, FEATURE_ID, display name / SEO
Home: platform | mvm-landing | <FEATURE_ID>-landing
Scope: thin brand | Tier-2 presets | full Tier-3
Locales (match clone env)

Reggie MCP (after overlay plan approved)

Scaffold / refresh thin overlay: reggie_autonomous_clone with dry_run: true first (clone_name, customization, optional skip_merge)
Propagate Layer1 shared code later with reggie_ringdom_propagate — source_project: "ring", dry_run: true, then review files_planned[] / files_rejected_list[] before dry_run: false
Compose always via ringdom-clone-build (ringdom-mcp) — platform → tmp, clone overlay wins

Manual path

Prerequisites: repo access to Ringdom, clone slug chosen, FEATURE_ID matching ^[a-z][a-z0-9]*$, MCP or local merge script available.

Classify Mode — New thin overlay (A), flat→web/ migrate (B), or ringize existing Final-Split (C). Prefer A/B via layer2-clone-operator before endemic product.
Tier-1 config — Under OVERLAY_ROOT (ring-<slug>/web): set ring-config.json clone.*, seo, home.preset, entity/product presets. For Tier-3 add top-level "<FEATURE_ID>": { "enabled": true, … } — not under boolean features.*.
Tier-2 presets — Prefer platform catalogs (agricultural, mvm-landing, …). Only add clone features/*/presets/<name>.ts + registry overlay when the niche is not upstream yet.
Tier-3 package — Create features/<FEATURE_ID>/ (i18n.ts → appendOverlayMessages, components, optional APIs). Overlay maps-only lib/overlay/registry.ts for i18n + home rail. Optional components/pages/home-presets/<FEATURE_ID>-landing.tsx.
Reggie exclude — At clone root .reggie-propagate-exclude.json: files[] + directories[] + locale_strategy: "new_keys_only". Final-Split paths use web/ prefixes. Always exclude the registry plug; never exclude types.ts / runtime.ts / whole lib/overlay/.
Build verify — ringdom-clone-build({ project_name: "ring-<slug>", dry_run: true }), then typecheck in the merge tmp / .dev-merge. Push forge ringdom-clones/<slug> only after dry-run review.

Exclude skeleton (Final-Split)

Why this matters for your clone

Pay → Project Config

Set name, slogan, logo, home.preset, and domainFeatureId after calculator checkout.

Order Lab playbook tab

Per-order checklist beside secrets, wiki, and deploy gates.

Vertical presets

Prefer agricultural / mvm-landing shared niches before asking for custom code.

Implementation map

Concern	Verified path
In-app playbook SSOT	`ring-platform-org/web/features/crm/lab/ringization-playbook.ts`
Playbook UI panel	`…/ringization-playbook-panel.tsx`
Seed on assign	`seedRingizationPlaybookMessage` in `order-lab-chat-service.ts`
Project Config domain key	`domainFeatureId` → top-level overlay in `order-project-config.ts`
Layer1 empty registry	`ring/web/lib/overlay/registry.ts`
Socket SSOT	`ring/web/lib/overlay/types.ts`, `runtime.ts`
Feature id allowlist	`OVERLAY_FEATURE_IDS` in `lib/overlay/types.ts`

Frequently asked questions

Impact

Will platform upgrades wipe my Cosmic Mirror / domain UI?

No — if those paths are listed in .reggie-propagate-exclude.json. Missing excludes are how Reggie overwrites vertical code. Always exclude the registry plug + web/features/<id>/.

Do I need Tier-3 for every clone?

No. Prefer Tier-1 brand + Tier-2 named presets. Tier-3 only when you need clone-only UI, locales, or APIs.

Migration

Our clone is still flat (app/ at repo root). What first?

Run layer2-clone-operator Mode B: cut endemic files into web/, rewrite exclude with web/… prefixes, add scripts/merge-dev.sh, then Mode C ringize.

Can integrators edit `ring/web` to “fix” a missing brand string?

No. That is a hard ban. Fix via clone locales / overlay registry / home preset — or upstream a shared preset in a separate Layer1 PR.

Ops

Who deploys — buyer, integrator, or Reggie?

Deploy is integrator/admin from Order Lab. Reggie plans in chat and may scaffold/propagate; it does not deploy. See Owner Project Lab.

What is the factory for a new disk overlay?

reggie_autonomous_clone (thin overlay + optional merge). Not reggie-ringize plan artifacts.

Where do buyers see this playbook in-app?

/my-orders/[id]?tab=playbook (buyer) and /my-jobs/[id]?tab=playbook (integrator). Seeded chat uses PLAYBOOK_SEED_MARKER for idempotent re-assign.

Ringization playbook

Use Founder / Developer tabs in the docs sidebar to filter this page. Shared sections apply to both audiences.

Surface	Role
This playbook	Full vertical / brand / Tier-1–3 methodology
Configuration playbook	Order Lab `?tab=playbook` — this order’s gates
Vertical presets	Named `entities` / `home` / productField catalogs
Customization guide	Config-first branding + thin exclude hygiene
Owner Project Lab	Buyer `/my-orders` · integrator `/my-jobs` chrome

Previous habit	Ring equivalent
Fork all of platform into `ring-*`	Thin `ring-*/web/` overlay + `ringdom-clone-build`
Patch `lib/i18n.ts` / `home-wrapper` per brand	Overlay `lib/overlay/registry.ts` + `features/<id>/`
Nest product under `features.n9life: true`	Top-level `"n9life": { … }` domain block
Exclude whole `lib/` or `lib/overlay/`	Exclude `web/lib/overlay/registry.ts` plug only (+ domain dirs)
`reggie-ringize` plan files as factory	`reggie_autonomous_clone` → merge → forge

Settler pipeline (shared)

Calculator → paid project_order
Order Project Config — home.preset, domainFeatureId, brand fields
Integrator assign → playbook markdown seeded in the project room (PLAYBOOK_SEED_MARKER)
Factory — reggie_autonomous_clone (thin disk overlay) → Forgejo ringdom-clones/<slug> → BuildKit / Lab deploy

Buyers and integrators open the in-app panel on /my-orders/[id] and /my-jobs/[id] (?tab=playbook). Docs deep-link: /docs/customization/ringization-playbook.

Kingdom layers (Final-Split)

Hard bans

No Cosmic Mirror / brand locales in platform home-wrapper or lib/i18n
Platform lib/overlay/registry.ts stays maps-empty; clones overlay registrations (maps only)
Platform lib/overlay/runtime.ts + types.ts are SSOT — never fork loaders onto the clone plug
Factory = reggie_autonomous_clone (not reggie-ringize plans)
Do not cp -r ring/web into the clone as a permanent fork

Recommended path

Use Cursor agent clone-customization-with-implementer (orchestrates layer2-clone-operator + ringization-implementer). It does not mutate until you approve the plan / dry-run.

Starter prompt (paste, fill blanks):

Ringize TARGET_CLONE=ring-<slug> with FEATURE_ID=<id> and MODE=A_new_thin | B_migrate_flat_to_web | C_ringize_existing. Overlay root = Final-Split web/. Follow .cursor/agents/layer2-clone-operator.md then .cursor/agents/ringization-implementer.md. Zero edits under ring/web/ or unsolicited ring-platform-org/. Update .reggie-propagate-exclude.json with web/… paths; exclude web/lib/overlay/registry.ts plug only. Dry-run ringdom-clone-build then pause for my approval before apply.

Inputs checklist

TARGET_CLONE, FEATURE_ID, display name / SEO
Home: platform | mvm-landing | <FEATURE_ID>-landing
Scope: thin brand | Tier-2 presets | full Tier-3
Locales (match clone env)

Reggie MCP (after overlay plan approved)

Scaffold / refresh thin overlay: reggie_autonomous_clone with dry_run: true first (clone_name, customization, optional skip_merge)
Propagate Layer1 shared code later with reggie_ringdom_propagate — source_project: "ring", dry_run: true, then review files_planned[] / files_rejected_list[] before dry_run: false
Compose always via ringdom-clone-build (ringdom-mcp) — platform → tmp, clone overlay wins

Manual path

Prerequisites: repo access to Ringdom, clone slug chosen, FEATURE_ID matching ^[a-z][a-z0-9]*$, MCP or local merge script available.

Classify Mode — New thin overlay (A), flat→web/ migrate (B), or ringize existing Final-Split (C). Prefer A/B via layer2-clone-operator before endemic product.
Tier-1 config — Under OVERLAY_ROOT (ring-<slug>/web): set ring-config.json clone.*, seo, home.preset, entity/product presets. For Tier-3 add top-level "<FEATURE_ID>": { "enabled": true, … } — not under boolean features.*.
Tier-2 presets — Prefer platform catalogs (agricultural, mvm-landing, …). Only add clone features/*/presets/<name>.ts + registry overlay when the niche is not upstream yet.
Tier-3 package — Create features/<FEATURE_ID>/ (i18n.ts → appendOverlayMessages, components, optional APIs). Overlay maps-only lib/overlay/registry.ts for i18n + home rail. Optional components/pages/home-presets/<FEATURE_ID>-landing.tsx.
Reggie exclude — At clone root .reggie-propagate-exclude.json: files[] + directories[] + locale_strategy: "new_keys_only". Final-Split paths use web/ prefixes. Always exclude the registry plug; never exclude types.ts / runtime.ts / whole lib/overlay/.
Build verify — ringdom-clone-build({ project_name: "ring-<slug>", dry_run: true }), then typecheck in the merge tmp / .dev-merge. Push forge ringdom-clones/<slug> only after dry-run review.

Exclude skeleton (Final-Split)

Why this matters for your clone

Pay → Project Config

Set name, slogan, logo, home.preset, and domainFeatureId after calculator checkout.

Order Lab playbook tab

Per-order checklist beside secrets, wiki, and deploy gates.

Vertical presets

Prefer agricultural / mvm-landing shared niches before asking for custom code.

Implementation map

Concern	Verified path
In-app playbook SSOT	`ring-platform-org/web/features/crm/lab/ringization-playbook.ts`
Playbook UI panel	`…/ringization-playbook-panel.tsx`
Seed on assign	`seedRingizationPlaybookMessage` in `order-lab-chat-service.ts`
Project Config domain key	`domainFeatureId` → top-level overlay in `order-project-config.ts`
Layer1 empty registry	`ring/web/lib/overlay/registry.ts`
Socket SSOT	`ring/web/lib/overlay/types.ts`, `runtime.ts`
Feature id allowlist	`OVERLAY_FEATURE_IDS` in `lib/overlay/types.ts`

Frequently asked questions

Impact

Will platform upgrades wipe my Cosmic Mirror / domain UI?

No — if those paths are listed in .reggie-propagate-exclude.json. Missing excludes are how Reggie overwrites vertical code. Always exclude the registry plug + web/features/<id>/.

Do I need Tier-3 for every clone?

No. Prefer Tier-1 brand + Tier-2 named presets. Tier-3 only when you need clone-only UI, locales, or APIs.

Migration

Our clone is still flat (app/ at repo root). What first?

Run layer2-clone-operator Mode B: cut endemic files into web/, rewrite exclude with web/… prefixes, add scripts/merge-dev.sh, then Mode C ringize.

Can integrators edit `ring/web` to “fix” a missing brand string?

No. That is a hard ban. Fix via clone locales / overlay registry / home preset — or upstream a shared preset in a separate Layer1 PR.

Ops

Who deploys — buyer, integrator, or Reggie?

Deploy is integrator/admin from Order Lab. Reggie plans in chat and may scaffold/propagate; it does not deploy. See Owner Project Lab.

What is the factory for a new disk overlay?

reggie_autonomous_clone (thin overlay + optional merge). Not reggie-ringize plan artifacts.

Where do buyers see this playbook in-app?

/my-orders/[id]?tab=playbook (buyer) and /my-jobs/[id]?tab=playbook (integrator). Seeded chat uses PLAYBOOK_SEED_MARKER for idempotent re-assign.

Scenario	What you ask for
Logo + site name only	Tier-1 — `ring-config` + branding assets
Healthy-food marketplace like GreenFood	Tier-2 — `entities`/`productFields`/`productBadges` = `agricultural`, `home.preset` = `mvm-landing`
Unique product (Cosmic Mirror, Connect)	Tier-3 — `features/<id>/*` + registry plug + exclude
Flat legacy clone	Mode B Final-Split migrate before more endemic UI

Tool	Server id
`legiox-knowledge` / agent-selector	`project-0-ringdom-legiox-mcp`
`reggie_autonomous_clone`, `reggie_ringdom_propagate`	`project-0-ringdom-reggie-mcp`
`ringdom-clone-build`	`project-0-ringdom-ringdom-mcp`

Scenario	What you ask for
Logo + site name only	Tier-1 — `ring-config` + branding assets
Healthy-food marketplace like GreenFood	Tier-2 — `entities`/`productFields`/`productBadges` = `agricultural`, `home.preset` = `mvm-landing`
Unique product (Cosmic Mirror, Connect)	Tier-3 — `features/<id>/*` + registry plug + exclude
Flat legacy clone	Mode B Final-Split migrate before more endemic UI

Tool	Server id
`legiox-knowledge` / agent-selector	`project-0-ringdom-legiox-mcp`
`reggie_autonomous_clone`, `reggie_ringdom_propagate`	`project-0-ringdom-reggie-mcp`
`ringdom-clone-build`	`project-0-ringdom-ringdom-mcp`

Scenario	What you ask for
Logo + site name only	Tier-1 — `ring-config` + branding assets
Healthy-food marketplace like GreenFood	Tier-2 — `entities`/`productFields`/`productBadges` = `agricultural`, `home.preset` = `mvm-landing`
Unique product (Cosmic Mirror, Connect)	Tier-3 — `features/<id>/*` + registry plug + exclude
Flat legacy clone	Mode B Final-Split migrate before more endemic UI

Documentation

Quick entry (CTOs · auditors · agents)

Documentation

Quick entry (CTOs · auditors · agents)

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Loading documentation...

Loading documentation...

Ringization playbook

Settler pipeline (shared)

Kingdom layers (Final-Split)

Hard bans

Recommended path

Manual path

Exclude skeleton (Final-Split)

Why this matters for your clone

Pay → Project Config

Order Lab playbook tab

Vertical presets

Frequently asked questions

Impact

Will platform upgrades wipe my Cosmic Mirror / domain UI?

Do I need Tier-3 for every clone?

Migration

Our clone is still flat (app/ at repo root). What first?

Can integrators edit ring/web to “fix” a missing brand string?

Ops

Who deploys — buyer, integrator, or Reggie?

What is the factory for a new disk overlay?

Where do buyers see this playbook in-app?

Related documentation

Related documentation

Configuration playbook

Owner Project Lab

Vertical Presets (SSOT)

Customization Guide

Ringization playbook

Settler pipeline (shared)

Kingdom layers (Final-Split)

Hard bans

Recommended path

Manual path

Exclude skeleton (Final-Split)

Why this matters for your clone

Pay → Project Config

Order Lab playbook tab

Vertical presets

Frequently asked questions

Impact

Will platform upgrades wipe my Cosmic Mirror / domain UI?

Do I need Tier-3 for every clone?

Migration

Our clone is still flat (app/ at repo root). What first?

Can integrators edit ring/web to “fix” a missing brand string?

Ops

Who deploys — buyer, integrator, or Reggie?

What is the factory for a new disk overlay?

Where do buyers see this playbook in-app?

Related documentation

Related documentation

Configuration playbook

Owner Project Lab

Vertical Presets (SSOT)

Customization Guide

Ringization playbook

Settler pipeline (shared)

Kingdom layers (Final-Split)

Hard bans

Recommended path

Manual path

Can integrators edit `ring/web` to “fix” a missing brand string?

Can integrators edit `ring/web` to “fix” a missing brand string?

Can integrators edit `ring/web` to “fix” a missing brand string?