Eklavya runtime architecture

One turn of the loop

• 1 · the agent calls log_session_concepts while it works
• 2 · PostToolUse reads it and returns additionalContext
• 3 · an instruction to ask — never the question itself
• 4 · the model plans, asks, grades with record_attempt (panel: present_question)
• Mid-task and Stop questions share one session budget

Eight hooks, six events

• SessionStart — banner + context; SubagentStart — context
• UserPromptSubmit — one line, only when a session logged nothing
• PostToolUse — capture plus two checkpoint matchers
• Stop — context continues work; memory closes due batches
• PreToolUse — deny commit; file history; [Eklavya] line

Server, state and boundaries

• stdout is the protocol; diagnostics are forced to stderr
• retryOnBusy wraps handlers; openDb seeds, then packs
• Session gate + opt-in Git hook; operational failures allow commits
• A failed memory job backs off; auth or quota pauses the queue, which rechecks itself
• No config in a checkout; settings are per developer, not committed