Home A - Z
Page Index

AeThex Docs

Blame

be64c9 AeThex Docs 2026-06-27 00:39:17
Build out operational docs platform
1 
# KAEL Capabilities
2
3
This page separates implemented KAEL behavior from roadmap items.
4
5
| Field | Value |
6
|---|---|
7
| Product maturity | Live / evolving |
8
| Documentation status | Active |
9
| Last source review | 2026-06-26 |
10
| Changelog | [[KAEL Changelog]] |
11
12
## Implemented public capabilities
13
14
- Non-streaming and Server-Sent Events chat.
15
- Model catalog discovery.
16
- Anonymous and authenticated sessions.
17
- Recent conversational history.
18
- Key/value user memory.
19
- AeThex knowledge matching.
20
- Identity and profile summaries.
21
- Feedback ratings.
22
- Featured and activity feeds.
23
- Generated-document creation and storage.
24
- Email one-time-code and AeThex OAuth-style sign-in flows where configured.
25
- Image-aware requests through a compatible model tier.
26
27
## Implemented integrations
28
29
- Discord interaction verification and slash-command handling.
30
- AeThex service-status checks.
31
- Signed deployment webhooks.
32
- Optional Telegram bot initialization.
33
- Optional transcription and text-to-speech routes.
34
- DB-backed scheduled tasks and daily briefs.
35
- Tenant-specific prompts, knowledge, models, and rate limits.
36
37
## Permissioned capabilities
38
39
Depending on clearance and operator authorization, KAEL can expose tools for:
40
41
- Live web retrieval.
42
- AeThex service checks.
43
- Passport and ecosystem lookup.
44
- Persistent world-model reads and writes.
45
- Observations and operator context.
46
- Agent execution.
47
- Deployment actions.
48
- Tenant administration.
49
50
> [!WARNING]
51
> The existence of a server route does not make it a public API. Operator and owner routes require explicit authorization and are intentionally excluded from public client examples.
52
53
## Capability boundaries
54
55
KAEL does not guarantee:
56
57
- That every provider model is always enabled.
58
- That a public user has access to every tool.
59
- That experimental endpoints remain stable.
60
- That generated answers are authoritative without a linked source.
61
- That an available hostname means every feature is production-ready.
62
63
## Client guidance
64
65
- Discover models using `/kael/models`.
66
- Treat clearance as server-calculated.
67
- Expect rate-limit events inside an SSE response.
68
- Store no operator token in browser code.
69
- Keep session IDs unguessable when they protect anonymous continuity.
70
- Provide users a way to inspect and clear memory.
71
72
## Roadmap
73
74
Planned work belongs in [[KAEL Roadmap]]. Shipped behavior belongs here and in [[KAEL Changelog]].