KAEL Build

KAEL Build tracks how the implemented system is being stabilized and extended.

Layer 1 — Surfaces

Implemented:

• Public chat at chat.aethex.tech.
• Dedicated KAEL surface at kael.aethex.tech.
• API runtime at api.aethex.tech.
• Discord interactions.
• Optional Telegram and audio modules.

Current work:

• Keep responsibilities distinct.
• Make identity and state visible to users.
• Improve client error handling and accessibility.

Layer 2 — Knowledge

Implemented:

• Structured AeThex knowledge entries.
• Runtime reload when knowledge files change.
• Query matching before model generation.
• Tenant-specific knowledge injection.

Current work:

• Add source links and verification dates.
• Detect stale knowledge.
• Connect stable documentation to the KAEL retrieval path.

Layer 3 — Context and continuity

Implemented:

• Recent session history.
• Passport-associated history.
• Visitor- and Passport-scoped memory.
• Profile and ARM context.

Current work:

• Make retention behavior explicit.
• Improve inspect/delete controls.
• Prevent identity scope confusion.

Layer 4 — Permissioned tools

Implemented for authorized levels:

• Web and service retrieval.
• Ecosystem lookup.
• Observations.
• World-model access.
• Agent execution.
• Tenant and operator workflows.
• Deployment-related operations.

Current work:

• Narrow permissions by operation.
• Add confirmation boundaries.
• Improve action auditability.
• Keep privileged routes out of public browser clients.

Release requirements

A capability is supported only when:

1. The running system implements it.
2. Its authorization boundary is defined.
3. Failure behavior is documented.
4. User data controls are available where needed.
5. It appears in KAEL Changelog.

Related documentation

• KAEL Architecture
• KAEL Capabilities
• KAEL Safety
• KAEL Roadmap
• KAEL Changelog