Clarify public/private deployment choice/paths

[alexandratran]

Clarify public vs private deployment to reduce cognitive load on pages that cover both:

• Streamline Deployment models page, ensuring the choice between private and public deployment is presented early and clearly. Drop unrelated customization factors (they're already covered in finalization layer and finality pages as design choices).
• Standardize terminology as "public deployments" vs "private validium," and promote to headings where applicable for visibility in TOC
• Remove the data availability section from the deployment components page; DA is already covered in the next page, and is more a design choice / property / guarantee than a component.

Preview: https://doc-linea-git-public-private-consensys-ddffed67.vercel.app/stack/evaluate/deployment-models

---

Note

Low Risk
Documentation-only edits with no runtime, security, or configuration behavior changes.

Overview
Documentation is refocused so readers choose between public deployments and private validium earlier, with consistent naming across the stack evaluate and deployment pages.

The Deployment models page is restructured: the intro states the two models up front, decision questions link to privacy, compliance, DA, and RBAC, and a comparison table replaces long duplicated characteristic lists. Unrelated “customization factors” are removed from that page (they stay on finalization-focused docs). Next steps becomes See also with clearer cross-links.

Core components drops the standalone data-availability section so DA is treated as a deployment property, not a required component list item. Data availability and finalization renames the public subsection to Public deployments.

Terminology is aligned elsewhere: trust assumptions use Public deployment on Ethereum (not “public rollup”), verification subsections use ### headings, Privacy and data visibility is scoped explicitly to private validium (index card + page intro), and the validium data-flow heading is Private validium data flow.

^{Reviewed by Cursor Bugbot for commit 49542f1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
doc-linea	Ready	Preview	Aug 31, 2026 5:21pm

[bgravenorst]

lgtm