Exercise 2: What OpenSearch Actually Is, and Why the Forked Version Matters — Possible Solution
====================================================================

WHAT OPENSEARCH IS IN RELATION TO ELASTICSEARCH
------------------------------
Per this chapter, "rather than accept the new, more restrictive
licensing, AWS — along with several other companies — forked the last
Apache 2.0-licensed version of Elasticsearch and Kibana, creating
OpenSearch." OpenSearch is not an independent, from-scratch reimplementation
of a search engine that merely resembles Elasticsearch — it is a
direct fork, meaning it started as an actual literal copy of
Elasticsearch's own codebase, at a specific point in time, which AWS
and other contributors then began developing independently from that
point forward.

WHAT SPECIFIC VERSION WAS FORKED
------------------------------
Per this chapter, the fork used "the last Apache 2.0-licensed version"
of Elasticsearch and Kibana — that is, the final release Elastic NV
made before its own January 2021 announcement moved future versions to
the new Elastic License/SSPL dual-license model. OpenSearch's own
starting codebase is that exact last-Apache-licensed snapshot of
Elasticsearch/Kibana, not an earlier or later version.

WHY THIS DETAIL MATTERS FOR UNDERSTANDING OPENSEARCH'S OWN ORIGINS
------------------------------
This detail matters for two real reasons. First, it explains why
OpenSearch and Elasticsearch started out with genuinely near-identical
functionality and API shape — OpenSearch literally began as a full
copy of Elasticsearch's own actual code, not a reinvention built to
merely resemble it. Second, it explains why understanding the two
projects' own subsequent, independent development since that fork
point (covered in search1-9) actually matters for a real deployment
decision — every feature or change either project has made SINCE that
exact fork point is a genuine divergence between the two, while
everything from before that point is shared, common ancestry. Knowing
precisely where the fork happened is what makes it possible to reason
about what's still shared and what's genuinely different between the
two engines today.

WHY THIS WORKS AS AN ANSWER
------------------------------
It states precisely what kind of software artifact OpenSearch is (a
literal fork, not a rewrite), identifies exactly which version was
forked using the chapter's own wording, and explains why that specific
detail is practically significant for reasoning about the two
projects' own current relationship rather than just being a historical
footnote.