Eklavya — Runtime Architecture Diagram

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
• Budget is per session: mid-task answers Stop then skips

Six hooks, six mechanisms

• SessionStart — stdout; SubagentStart — the JSON form only
• UserPromptSubmit — one line, only when a session logged nothing
• PostToolUse — exit 0 + JSON; skipped inside subagents
• Stop — exit 2 + stderr is what actually blocks the turn
• PreToolUse(Bash) — permissionDecision "deny" on git commit

Server, state and boundaries

• stdout is the protocol; diagnostics are forced to stderr
• retryOnBusy wraps handlers; openDb seeds, then packs
• Repo gate reads .eklavya.json only, never global config
• Two commit gates, session and repo; both fail open
• run.mjs prefers mcp/dist; npx at the pinned version