Commit 9566c9
2026-06-23 21:23:59 Anonymous: -/-| /dev/null .. kael-build.md | |
| @@ 0,0 1,62 @@ | |
| + | # KAEL Build |
| + | |
| + | KAEL Build tracks how KAEL is being built: architecture direction, working surfaces, near-term development priorities, and the difference between current capability and intended capability. |
| + | |
| + | <div class="docs-section-heading"> |
| + | <h2>Build direction</h2> |
| + | <p>KAEL is being shaped as the intelligence layer for AeThex, starting with conversation and documentation support.</p> |
| + | </div> |
| + | |
| + | The KAEL build should move in stages. Each stage should be useful by itself, but also prepare the system for deeper AeThex integration later. |
| + | |
| + | ## Stage 1 — Identity and surfaces |
| + | |
| + | Current focus: |
| + | |
| + | - Establish the KAEL docs section. |
| + | - Connect the public surfaces: **chat.aethex.tech** and **kael.aethex.tech**. |
| + | - Define KAEL's role inside the AeThex ecosystem. |
| + | - Keep a current [[KAEL-Changelog]]. |
| + | - Avoid overstating unfinished capabilities. |
| + | |
| + | ## Stage 2 — Knowledge layer |
| + | |
| + | KAEL should understand AeThex docs and support materials before it takes actions. Priority knowledge sources include: |
| + | |
| + | - [[Home]] and the docs index. |
| + | - [[Platform-Overview]] |
| + | - [[Passport]] |
| + | - [[Authentication]] |
| + | - [[Projects]] |
| + | - [[Permissions]] |
| + | - [[Security]] |
| + | - [[Api-Reference]] |
| + | |
| + | ## Stage 3 — Guided workflows |
| + | |
| + | Once the knowledge layer is stable, KAEL can guide users through workflows: |
| + | |
| + | - Finding the right docs page. |
| + | - Explaining AeThex concepts. |
| + | - Helping users prepare support requests. |
| + | - Walking developers through API and SDK setup. |
| + | - Helping admins reason about organizations, teams, and permissions. |
| + | |
| + | ## Stage 4 — Permissioned actions |
| + | |
| + | Action-taking should come later and must respect [[Authentication]], [[Permissions]], [[Security-Model]], and [[Multi-Tenancy]]. Examples may include: |
| + | |
| + | - Creating draft docs or support summaries. |
| + | - Preparing project setup steps. |
| + | - Checking status or configuration. |
| + | - Suggesting changes before a human approves them. |
| + | |
| + | > [!WARNING] |
| + | > KAEL should not perform destructive, security-sensitive, or external actions without explicit permission and a clear audit trail. |
| + | |
| + | <div class="docs-grid"> |
| + | <a class="docs-card" href="/KAEL">KAEL Overview</a> |
| + | <a class="docs-card" href="/KAEL-Changelog">Changelog</a> |
| + | <a class="docs-card" href="/KAEL-Endpoints">Endpoints</a> |
| + | <a class="docs-card" href="/Security-Model">Security Model</a> |
| + | </div> |