Architecture refactor #1660

Author: LandauRaz

.htaccess

@@ -421,3 +421,4 @@ RewriteRule ^architecture-and-concepts/smart-contracts/cairo-and-sierra/$ https:
 RewriteRule ^architecture-and-concepts/smart-contracts/serialization-of-cairo-types/$ https://book.cairo-lang.org/ch102-04-serialization-of-cairo-types.html [R=301,L]
 RewriteRule ^architecture-and-concepts/(.*)$ /architecture/$1 [R=301,L]
 RewriteRule ^architecture/economics-of-starknet/$ /architecture/strk? [R=301,L]
+RewriteRule ^architecture/protocol-overview/$ /architecture/overview? [R=301,L]

components/Starknet/antora.yml

@@ -4,7 +4,7 @@ title: Starknet
 nav:
   - modules/ROOT/nav.adoc
   - modules/guides/nav.adoc
-  - modules/tools/nav.adoc
   - modules/architecture/nav.adoc
+  - modules/tools/nav.adoc
   - modules/ecosystem/nav.adoc
   - modules/resources/nav.adoc

components/Starknet/modules/ROOT/pages/index.adoc

@@ -11,11 +11,9 @@ If you're completely new to Starknet or its programming language, https://www.ca
 
 🦮 Go to _Guides_ to keep talking to a minimum and follow Starknet's lead
 
-🛠️ Go to _Tooling_ to harness the power of Starknet's toolchain
-
-🚦 Go to _Protocol_ to learn about Starknet's unique features and design
+🏛️ Go to _Architecture_ to learn about Starknet's unique features and design
 
-🥞 Go to Stack to break down Starknet's architecture layer by layer
+🛠️ Go to _Tooling_ to harness the power of Starknet's toolchain
 
 🌍 Go to _Ecosystem_ to explore Starknet's third-party landscape
 

components/Starknet/modules/architecture/nav.adoc

@@ -1,18 +1,15 @@
-* Protocol
-    ** xref:protocol-overview.adoc[Overview]
+* Architecture
+    ** xref:overview.adoc[Overview]
     ** xref:accounts.adoc[]
     ** xref:blocks.adoc[]
     ** xref:cryptography.adoc[]
     ** xref:data-availability.adoc[]
     ** xref:fees.adoc[]
     ** xref:messaging.adoc[]
+    ** xref:sharp.adoc[]
+    ** xref:os.adoc[]
     ** xref:staking.adoc[]
+    ** xref:starkgate.adoc[]
     ** xref:state.adoc[]
     ** xref:strk.adoc[]
     ** xref:transactions.adoc[]
-* Stack
-    ** https://book.cairo-lang.org/[Cairo ↗^]
-    ** xref:sharp.adoc[SHARP]
-    ** xref:os.adoc[SNOS]
-    ** xref:starkgate.adoc[]
-    ** https://docs.starknet.io/stwo-book/[Stwo ↗^]

components/Starknet/modules/architecture/pages/os.adoc

@@ -1,9 +1,9 @@
 [id="sn_os"]
-= SNOS (Starknet operating system)
+= SNOS
 
 == Overview
 
-As an L2 validity rollup, Starknet's state on Ethereum can't be updated without proving that all the blocks between the current state and the new state are valid. SNOS is xref:what_is_snos?[the key element in Starknet's architecture] that xref:how_does_snos_work?[verifies the validity of Starknet blocks] and is required for xref:using_snos_to_update_starknets_state[
+As an L2 validity rollup, Starknet's state on Ethereum can't be updated without proving that all the blocks between the current state and the new state are valid. SNOS (**S**tark**N**et **O**perating **S**ystem) is xref:what_is_snos?[the key element in Starknet's architecture] that xref:how_does_snos_work?[verifies the validity of Starknet blocks] and is required for xref:using_snos_to_update_starknets_state[
 updating Starknet's state]. SNOS has two xref:implementations[implementations], a fully-open source one in Rust and a partially open-source one in Python.
 
 [NOTE]

components/Starknet/modules/architecture/pages/overview.adoc

@@ -0,0 +1,11 @@
+= Architecture overview
+
+Starknet is a coordinated system, with each element in its architecture playing a specific yet interconnected role.
+
+As with other blockchains, everything starts with an xref:accounts.adoc[account]. On Starknet, accounts are smart contracts — a model which is known as native account abstraction, and allows for flexible authorization logic like multisig, session keys, or passkey-based authentication, all without changes to the protocol itself. When users want to interact with the network, they send xref:transactions.adoc[transactions]. These can invoke contract functions, deploy new contracts, or register new classes, and may involve communication between Ethereum and Starknet — The latter are handled through xref:messaging.adoc[L1↔L2 messaging], enabling secure bridges such as xref:starkgate.adoc[].
+
+Periodically, transactions are collected and ordered into xref:blocks.adoc[blocks], which include a xref:cryptography.adoc[cryptographic] commitment the xref:state.adoc[state] of the network after executing them. To ensure that state transitions are valid, Starknet uses xref:sharp.adoc[SHARP] to generate and aggregate proofs of running the xref:os.adoc[SNOS] program. These proofs compress the entire block's execution into a succinct, verifiable artifact, which are submitted to Ethereum to be verified, so that Starknet's execution can be trusted without re-running it. Starknet also ensures access to the data involved in the computation through xref:data-availability.adoc[data availability], publishing compressed state diffs to Ethereum so the full state can be reconstructed and verified.
+
+All of this — execution, proof generation, and L1 publishing — isn't free, which is where xref:fees.adoc[fees] come in. Users pay fees to cover the cost of using network resources, and these fees are paid in xref:strk.adoc[STRK], Starknet's native token. STRK is also used to power Starknet's xref:staking.adoc[staking protocol], where validators selected from STRK stakers help secure the sequencing layer and validate block production. This mechanism is designed to support decentralization and provide economic guarantees around block inclusion and ordering.
+
+All together, these elements form a tightly integrated architecture, enabling scalable and expressive applications with low fees and strong security — all without compromising on decentralization or Ethereum alignment.

components/Starknet/modules/architecture/pages/protocol-overview.adoc

@@ -1,10 +1,10 @@
 [id="provers"]
-= SHARP (Shared Prover)
+= SHARP
 :down_arrow: ￬
 
-== Introduction
+== Overview
 
-SHARP is like public transportation for proofs on Starknet, aggregating multiple Cairo programs to save costs and boost efficiency. It uses recursive proofs, enabling parallelization and optimization, making it more affordable for all users. Critical services like the gateway, validator, and Prover work together with a stateless design for flexibility. SHARP’s adoption by StarkEx and Starknet highlights its significance and potential for future optimization.
+SHARP (**SHAR**ed **P**rover) is like public transportation for proofs on Starknet, aggregating multiple Cairo programs to save costs and boost efficiency. It uses recursive proofs, enabling parallelization and optimization, making it more affordable for all users. Critical services like the gateway, validator, and Prover work together with a stateless design for flexibility. SHARP’s adoption by StarkEx and Starknet highlights its significance and potential for future optimization.
 
 This topic discusses SHARP, how it has evolved to incorporate recursive proofs, and its role in reducing costs and improving efficiency within the Starknet network.
 

components/Starknet/modules/architecture/pages/sharp.adoc

@@ -1,4 +1,4 @@
-= State management
+= State
 
 == Overview