Blame
|
1 | # KAEL Changelog |
||||||
| 2 | ||||||||
| 3 | The KAEL Changelog records visible changes to KAEL docs, surfaces, behavior, integrations, and build direction. |
|||||||
| 4 | ||||||||
| 5 | <div class="docs-section-heading"> |
|||||||
| 6 | <h2>Living update log</h2> |
|||||||
| 7 | <p>Use this page to keep KAEL current instead of letting the docs drift away from the build.</p> |
|||||||
| 8 | </div> |
|||||||
| 9 | ||||||||
| 10 | ## 2026-06-23 |
|||||||
| 11 | ||||||||
| 12 | ### Added |
|||||||
| 13 | ||||||||
| 14 | - Created the dedicated KAEL docs section. |
|||||||
| 15 | - Added the main [[KAEL]] overview page. |
|||||||
| 16 | - Added [[KAEL-Build]] to describe how KAEL is being developed. |
|||||||
| 17 | - Added [[KAEL-Endpoints]] to document public KAEL-related surfaces. |
|||||||
| 18 | - Documented **chat.aethex.tech** as the conversational KAEL entry point. |
|||||||
| 19 | - Documented **kael.aethex.tech** as the dedicated KAEL surface. |
|||||||
| 20 | ||||||||
| 21 | ### Clarified |
|||||||
| 22 | ||||||||
| 23 | - KAEL should be treated as AeThex's intelligence layer, not merely a chatbot. |
|||||||
| 24 | - KAEL documentation should distinguish current capability from future intent. |
|||||||
| 25 | - Permissioned actions should require authentication, authorization, and auditability. |
|||||||
| 26 | ||||||||
| 27 | ### Next documentation tasks |
|||||||
| 28 | ||||||||
| 29 | - Add screenshots or interface notes once the public KAEL surfaces stabilize. |
|||||||
| 30 | - Document supported commands, flows, or intents when they exist. |
|||||||
| 31 | - Add integration notes for Passport, support routing, and developer workflows. |
|||||||
| 32 | - Define which KAEL behaviors are experimental, beta, or stable. |
|||||||
| 33 | ||||||||
| 34 | ## Changelog rules |
|||||||
| 35 | ||||||||
| 36 | When KAEL changes, add an entry with: |
|||||||
| 37 | ||||||||
| 38 | 1. Date. |
|||||||
| 39 | 2. Surface affected: chat, KAEL site, docs, API, support, or backend. |
|||||||
| 40 | 3. Type: added, changed, fixed, removed, security, or experimental. |
|||||||
| 41 | 4. Plain-language summary. |
|||||||
| 42 | 5. Links to affected docs pages. |
|||||||
| 43 | ||||||||
| 44 | ## Entry template |
|||||||
| 45 | ||||||||
| 46 | ## YYYY-MM-DD |
|||||||
| 47 | ||||||||
| 48 | ### Added |
|||||||
| 49 | ||||||||
| 50 | - Summary of new behavior or surface. |
|||||||
| 51 | ||||||||
| 52 | ### Changed |
|||||||
| 53 | ||||||||
| 54 | - Summary of changed behavior. |
|||||||
| 55 | ||||||||
| 56 | ### Fixed |
|||||||
| 57 | ||||||||
| 58 | - Summary of resolved issue. |
|||||||
| 59 | ||||||||
| 60 | ### Notes |
|||||||
| 61 | ||||||||
| 62 | - Any migration, limitation, or follow-up. |
|||||||
| 63 | ||||||||
| 64 | > [!NOTE] |
|||||||
| 65 | > Keep this changelog factual. Do not describe planned work as shipped work. |
|||||||