KAEL
KAEL is the Knowledge-Augmented Execution Layer of AeThex: a conversational system, knowledge interface, integration runtime, and permissioned operator layer.
| Field | Value |
|---|---|
| Product maturity | Live / evolving |
| Documentation status | Active |
| Chat | chat.aethex.tech |
| System surface | kael.aethex.tech |
| API | api.aethex.tech |
| Last source review | 2026-06-26 |
KAEL // Knowledge-Augmented Execution Layer
AeThex knowledge, context, and permissioned action.
KAEL connects chat, AeThex knowledge, identity, memory, integrations, models, and carefully scoped tools through one evolving runtime.
Start here
What is implemented
KAEL currently provides:
- Streaming and non-streaming conversation.
- AeThex knowledge matching.
- Model selection based on access.
- Session history and keyed memory.
- Passport-aware identity context.
- Discord interactions.
- Tenant-specific prompts and knowledge.
- Generated documents, feeds, and ratings.
- Permissioned tools, agents, observations, and world-state operations for authorized roles.
See KAEL Capabilities for exact boundaries.
System model
KAEL is not one webpage. It is a connected set of surfaces:
| Surface | Role |
|---|---|
chat.aethex.tech |
Public conversation |
kael.aethex.tech |
Dedicated KAEL and operator experience |
api.aethex.tech |
Runtime, state, integrations, and streaming |
| Discord | Signed command interactions |
| AeThex knowledge | Canonical ecosystem context |
| Passport and ARM | Identity and clearance inputs |
Documentation map
- KAEL Quickstart — begin as a user.
- KAEL Architecture — understand the runtime and data flow.
- KAEL Capabilities — distinguish shipped behavior from plans.
- KAEL API — public API groups and OpenAPI contract.
- KAEL Memory — history, persistent memory, and user controls.
- Discord Integration — Discord behavior and security.
- KAEL Safety — permissions, privacy, tools, and incident handling.
- KAEL Build — staged implementation model.
- KAEL Roadmap — intended direction.
- KAEL Changelog — dated shipped changes.
Operating principle
KAEL should be useful before it is powerful, transparent before it is autonomous, and explicitly authorized before it changes an external system.
If the documentation conflicts with the running system, treat that as a documentation defect. Record the observed behavior, verify it against source, and update KAEL Changelog.