Commit 164094

2026-06-23 21:23:59 Anonymous: -/-
/dev/null .. kael-endpoints.md
@@ 0,0 1,60 @@
+ # KAEL Endpoints
+
+ KAEL Endpoints documents the public KAEL-related web surfaces and what each one is supposed to represent.
+
+ <div class="docs-section-heading">
+ <h2>Public surfaces</h2>
+ <p>These domains should point users to the right KAEL experience without blurring their purpose.</p>
+ </div>
+
+ ## chat.aethex.tech
+
+ **Purpose:** conversational entry point.
+
+ Use **chat.aethex.tech** for direct interaction with KAEL-style chat experiences. This surface should focus on conversation, guidance, support preparation, docs navigation, and user-facing assistant behavior.
+
+ Expected responsibilities:
+
+ - Let users ask questions in natural language.
+ - Explain AeThex concepts and docs.
+ - Help users find the right AeThex page or support path.
+ - Keep user-facing behavior clear and approachable.
+
+ ## kael.aethex.tech
+
+ **Purpose:** dedicated KAEL identity and system surface.
+
+ Use **kael.aethex.tech** as the KAEL-specific home for build notes, experiments, agent interface work, deeper system behavior, and future KAEL-specific workflows.
+
+ Expected responsibilities:
+
+ - Present KAEL as a named AeThex system.
+ - Host or link KAEL-specific experiments.
+ - Point to the changelog and docs.
+ - Separate KAEL system identity from general support or marketing pages.
+
+ ## Related AeThex surfaces
+
+ - **docs.aethex.support** — durable documentation and operating notes.
+ - **aethex.support** — support and help entry point.
+ - **aethex.net** — broader AeThex network/gateway presence.
+
+ <div class="docs-grid">
+ <a class="docs-card" href="https://chat.aethex.tech">chat.aethex.tech</a>
+ <a class="docs-card" href="https://kael.aethex.tech">kael.aethex.tech</a>
+ <a class="docs-card" href="/KAEL-Changelog">KAEL Changelog</a>
+ <a class="docs-card" href="/KAEL-Build">KAEL Build</a>
+ </div>
+
+ ## Endpoint documentation checklist
+
+ For each KAEL surface, track:
+
+ 1. Current status.
+ 2. Intended audience.
+ 3. What users can do there today.
+ 4. What is experimental.
+ 5. Where bugs, support, or feedback should go.
+
+ > [!WARNING]
+ > Do not document private admin URLs, tokens, hidden endpoints, internal credentials, or unfinished privileged routes on public docs pages.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9