Quick Start: make Step 3 reference-based instead of inlining a compose file Step 3 no longer duplicates a docker-compose.yml or a "five services" description - both audience-fork branches now just point at their cookbook page's Docker section (Static MDS's, plus its "Use a simulator" section for data to watch; the Demo's). Step 5's health-check example is updated to match what the Static MDS Docker section plus simulator actually reports: the two feed-partitioned projectors (mf-projector-mds-bpipe/-other) in place of the single mf-projector-mds placeholder. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Real health-check examples, gateway role: n/a note, and cookbook health cross-links Operations-Monitoring's "Is the system healthy?" example swaps the mf-mds-consolidated + mf-eta-simulator placeholder for a real Static MDS response (gateway, core services, two feed-partitioned projectors, admin) and rewords the lead-in now that the gateway correctly shows role: n/a rather than ACTIVE. Quick Start's Step 5 example gets the same n/a correction plus a short note that it is normal, not a problem. Each Deployment Cookbook page (Static MDS, Fine-Grained, Static MDS with Compute, Scalable MDS, Demo) gets a "Confirm it's running" pointer to that same health-check section in its Where to go next list. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Quick Start: default to Static MDS instead of the Demo Step 3 now forks by audience: existing MetaFluent users and anyone upgrading start with Static MDS (the real deployment shape - gateway, admin, core services, one MDS projector, and the simulator feeding it - run single-host with an inline, self-contained docker-compose.yml), while newcomers comfortable with Docker can take the faster Demo path instead. The rest of the guide follows Static MDS by default, with the Demo delta called out where it actually differs (the health-check component list). Reframes the intro banner and closing section to match: this single-host setup already has the real deployment shape - the simulator is the only throwaway piece - and growing it means adding capacity and spreading across machines (Fine-Grained, Scalable MDS), not starting over. The Demo remains the pure evaluation peek for readers who took that path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Add Demo cookbook page, hyphenate Fine-Grained, and clean up cookbook prose Adds a greatly simplified Demo entry to the Deployment Cookbook (consolidated image + simulator, laptop/lab-friendly), moves the cookbook group ahead of Concepts in the sidebar since customers install before reading background, and points Quick Start at the new cookbook instead of an inline Docker Compose clone. Also tightens wording across the cookbook pages: consistent "Fine-Grained" hyphenation, substrate-neutral phrasing instead of "in its own container", and removes an internal-guidance sentence and a Docker-only implication from the Fine-Grained intro. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Develop-JMS revisions: jakarta namespace; latest-clone + tag note; mf-session connect + alias note; MarketData view/multi-key callout; expanded selectors; conventions section + new Dynamic Data Conventions page; entitlements note; Elastic MDS (v6) / context wording. Quick Start clone -> latest
Architecture Basics: REST not a content interface; projectors host 1+ adapters; drop REST snapshots; rename 'shape'; neutral request-delivery; unequivocal v5 compatibility + MarketData segue
Quick Start: remove emotive vocabulary (measured tone for engineer audience)
Quick Start Step 2: 'monitor' not 'running'; 'your own system'; drop 'gently'; link DNS-entry how-to in Deployment Basics
Quick Start Step 6: real jms-sdk invocation (prebuilt jar, stable clone), points to Develop-JMS
Quick Start Step 5: real projected application-state capture (name,role,state,info)
Quick Start: simulated (not live) data; two containers; non-Compose alt; reorder host-setup; gentler production nudge; SDK-sourced client; app-state placeholder
Draft Quick Start (consolidated composition + simulator)
Scaffold Elastic MDS wiki: Home, sidebar, footer, page stubs for the full doc set