Blame
|
1 | # KAEL Build |
||||||
| 2 | ||||||||
|
3 | KAEL Build tracks how the implemented system is being stabilized and extended. |
||||||
|
4 | |||||||
|
5 | | Field | Value | |
||||||
| 6 | |---|---| |
|||||||
| 7 | | Product maturity | Live / evolving | |
|||||||
| 8 | | Documentation status | Active | |
|||||||
| 9 | | Roadmap | [[KAEL Roadmap]] | |
|||||||
|
10 | | Last source review | 2026-06-27 | |
||||||
|
11 | |||||||
|
12 | ## Layer 1 — Surfaces |
||||||
|
13 | |||||||
|
14 | Implemented: |
||||||
|
15 | |||||||
|
16 | - Public chat at `chat.aethex.tech`. |
||||||
| 17 | - Dedicated KAEL surface at `kael.aethex.tech`. |
|||||||
| 18 | - API runtime at `api.aethex.tech`. |
|||||||
| 19 | - Discord interactions. |
|||||||
| 20 | - Optional Telegram and audio modules. |
|||||||
|
21 | |||||||
|
22 | Current work: |
||||||
|
23 | |||||||
|
24 | - Keep responsibilities distinct. |
||||||
| 25 | - Make identity and state visible to users. |
|||||||
| 26 | - Improve client error handling and accessibility. |
|||||||
|
27 | |||||||
|
28 | ## Layer 2 — Knowledge |
||||||
|
29 | |||||||
|
30 | Implemented: |
||||||
|
31 | |||||||
|
32 | - Structured AeThex knowledge entries. |
||||||
| 33 | - Runtime reload when knowledge files change. |
|||||||
| 34 | - Query matching before model generation. |
|||||||
| 35 | - Tenant-specific knowledge injection. |
|||||||
|
36 | - Generated documentation corpus with canonical URLs and verification metadata. |
||||||
| 37 | - Source-backed Ask KAEL answers using server-resolved corpus records. |
|||||||
|
38 | |||||||
|
39 | Current work: |
||||||
|
40 | |||||||
|
41 | - Detect stale knowledge. |
||||||
|
42 | - Improve retrieval ranking and evaluate answer/source agreement. |
||||||
|
43 | |||||||
|
44 | ## Layer 3 — Context and continuity |
||||||
|
45 | |||||||
|
46 | Implemented: |
||||||
|
47 | |||||||
|
48 | - Recent session history. |
||||||
| 49 | - Passport-associated history. |
|||||||
| 50 | - Visitor- and Passport-scoped memory. |
|||||||
| 51 | - Profile and ARM context. |
|||||||
|
52 | |||||||
|
53 | Current work: |
||||||
|
54 | |||||||
|
55 | - Make retention behavior explicit. |
||||||
| 56 | - Improve inspect/delete controls. |
|||||||
| 57 | - Prevent identity scope confusion. |
|||||||
| 58 | ||||||||
| 59 | ## Layer 4 — Permissioned tools |
|||||||
| 60 | ||||||||
| 61 | Implemented for authorized levels: |
|||||||
| 62 | ||||||||
| 63 | - Web and service retrieval. |
|||||||
| 64 | - Ecosystem lookup. |
|||||||
| 65 | - Observations. |
|||||||
| 66 | - World-model access. |
|||||||
| 67 | - Agent execution. |
|||||||
| 68 | - Tenant and operator workflows. |
|||||||
| 69 | - Deployment-related operations. |
|||||||
| 70 | ||||||||
| 71 | Current work: |
|||||||
| 72 | ||||||||
| 73 | - Narrow permissions by operation. |
|||||||
| 74 | - Add confirmation boundaries. |
|||||||
| 75 | - Improve action auditability. |
|||||||
| 76 | - Keep privileged routes out of public browser clients. |
|||||||
| 77 | ||||||||
| 78 | ## Release requirements |
|||||||
| 79 | ||||||||
| 80 | A capability is supported only when: |
|||||||
| 81 | ||||||||
| 82 | 1. The running system implements it. |
|||||||
| 83 | 2. Its authorization boundary is defined. |
|||||||
| 84 | 3. Failure behavior is documented. |
|||||||
| 85 | 4. User data controls are available where needed. |
|||||||
| 86 | 5. It appears in [[KAEL Changelog]]. |
|||||||
| 87 | ||||||||
| 88 | ## Related documentation |
|||||||
| 89 | ||||||||
| 90 | - [[KAEL Architecture]] |
|||||||
| 91 | - [[KAEL Capabilities]] |
|||||||
| 92 | - [[KAEL Safety]] |
|||||||
| 93 | - [[KAEL Roadmap]] |
|||||||
| 94 | - [[KAEL Changelog]] |
|||||||