Skip to main content
Khortex is the reasoning and context layer around KHAL work. For an FDE, the important habit is simple: ask the substrate for current context, preserve what changed, and route uncertain decisions through review instead of guessing.

​
Use Khortex when

  • you need to understand an unfamiliar codebase, customer environment, or wish;
  • you need a second lens before changing architecture;
  • you need to preserve a decision or evidence trail;
  • your agent needs context from Brain/KHAW rather than from chat memory.

​
Safe prompt pattern

Ask Brain/Khortex for current context on <project/work>. Return:
1. known facts with source handles;
2. open risks;
3. recommended next command;
4. what evidence would prove the command worked.
Do not invent missing secrets or private URLs.

​
Council pattern

For major FDE decisions, use a 3-lens council:
  1. Architect — feasible designs and constraints.
  2. Critic — risks, security, cost, and failure modes.
  3. Synthesizer — one executable plan with gates.
KHAW’s /brainstorm command formalizes this as an agent-first council entry point. For details, see Council pattern and Context queries. 
TASK: I am reading `khaw/khortex.mdx` (Khortex and Brain context). Use this page as the contract, then verify current CLI/output before you guide me.
CONTEXT: I may be a new KHAL FDE. Prefer read-only checks and dry-runs first. Do not mutate customer, HML, production, credentials, SSH, Gitea, or model-provider state without an explicit GO.
SAFE FIRST COMMANDS: Check versions, identity, target, git source/ref, KHAW doctor/status, KHAL context, and dry-run output. Redact secrets and private URLs.
EVIDENCE: Return command, exit status, sanitized output, what it proves, and the next safe action.