Move Component state to Architecture: Basics Component state is a foundational lifecycle concept (referenced by Monitoring, Troubleshooting, Logging), and read orphaned at the tail of Architecture: Advanced. Move the section - definition, two-phase model, and state diagram - into Architecture: Basics after "How a request is handled". Retarget the state-model references (Troubleshooting FAQ, Operations: Monitoring, How-to-Read) to Basics; trim the Advanced intro; add a state<->role pointer between the two pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Architecture Basics: applications use standard APIs + non-Java equivalents, monitoring via REST; content 'represented as' tables
Architecture Basics: REST not a content interface; projectors host 1+ adapters; drop REST snapshots; rename 'shape'; neutral request-delivery; unequivocal v5 compatibility + MarketData segue
Architecture: Basics - query language is a subset of SQL-92 (verified)
Architecture: Basics - advertise plain SQL (no unverified version claim)
Draft Architecture: Basics (components, core concepts, request flow)
Scaffold Elastic MDS wiki: Home, sidebar, footer, page stubs for the full doc set