From 6f6e6d35d84bf7859919cb7865c6d2ea36d215af Mon Sep 17 00:00:00 2001
From: Amine Ilidrissi <38422328+aminevg@users.noreply.github.com>
Date: Fri, 11 Sep 2026 14:20:49 +0900
Subject: [PATCH] docs: define core Mighty terminology

---
 CONTEXT.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 CONTEXT.md

diff --git a/CONTEXT.md b/CONTEXT.md
new file mode 100644
index 0000000..10f7537
--- /dev/null
+++ b/CONTEXT.md
@@ -0,0 +1,21 @@
+# Mighty
+
+Mighty lets a backend of any language render Astro pages on demand, the way Inertia.js lets a backend drive a JavaScript SPA. This glossary fixes the words the packages, docs, and issues use for that.
+
+## Language
+
+**Adapter**:
+The integration between one backend framework (Hono, Laravel) and Mighty. An adapter turns a backend request into a render request and returns the result as a backend response.
+_Avoid_: Integration, plugin, driver
+
+**Render request**:
+The unit of work an adapter hands to Mighty: which Astro page component to render, with which props and shared context, and whether to render it as a partial.
+_Avoid_: Render call, page request
+
+**Shared context**:
+Per-request data the backend exposes to every Astro component in a render, outside of props. Auth user, session flashes, and CSRF tokens are typical.
+_Avoid_: Globals, shared props, locals
+
+**Sidecar**:
+A separate Node process that serves render requests over a local transport for adapters whose backend cannot run Astro in-process.
+_Avoid_: Render server, bridge, daemon