mikehostetler

Lua Tool Layer for Jido/Jidoka Agents

Summary

This proposal explores a Lua-based tool layer for agents that need access to large application capability surfaces without sending every tool schema to the model on every turn.

The core idea is simple:

mikehostetler

Sparq: An App Store for Human Expertise

This is an early sketch of a big idea: what if the way experts do great work could be packaged, protected, rented, and improved over time?

Most companies have valuable expertise trapped in people's heads, private playbooks, scattered SOPs, consulting decks, Slack threads, and one-off processes. AI makes this problem more urgent. A generic AI agent can help, but it usually does not know how a great operator, manager, engineer, recruiter, salesperson, or compliance lead actually gets work done.

Sparq is an attempt to turn expert operating models into executable business capabilities.

The Core Idea

mikehostetler

Sensor Attention and Control in Jido

Status: proposal for discussion

Date: 2026-04-12

Related: agentjido/jido#253

Summary

mikehostetler

Jido.Domain

This is a concept sketch, not an implementation plan.

The core idea: Jido.Domain is the missing authoring layer above Jido.Pod.

Jido already has strong primitives:

• Jido.Agent for behavior
• Jido.Pod for durable topology

mikehostetler

Proposed RFC: Pod Runtime Lifecycle Callbacks

Status: Proposed

Author: Codex draft for discussion

Date: 2026-04-08

Summary

mikehostetler

• Prefer gh pr checkout <number> --detach for review-only work so disposable local branches do not accumulate.
• If a separate worktree is useful, give it an obviously temporary name and remove it with git worktree remove <path> when the review is done.
• After temp worktrees are removed or deleted out-of-band, run git worktree prune -v to clear stale metadata.
• Before starting substantial new work, prefer returning the root repo to a clean, current baseline with git status --short --branch, git fetch --prune origin, git checkout main, and git pull --ff-only origin main when that fits the repo workflow.
• Ask before deleting unmerged branches.
• Clean up disposable review branches like pr-<number> and *-review once they are merged or no longer needed.

mikehostetler

Jido 2.0 is here

Mike Hostetler

---

After 18 months of building, rewriting, and rethinking, Jido 2.0 has shipped. It's available on Hex now.

Jido started as a bot platform called BotHive in 2024. Then the AI wave hit and everything changed. I was already using Elixir decided to make a bet: the BEAM the best runtime for agent systems.

mikehostetler

#!/usr/bin/env bash
set -euo pipefail

SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
exec elixir "$SCRIPT_DIR/telegram_ai_agent_spike.exs"

mikehostetler

Opinion: ReAct Tool Execution Should Stay Data-First, With Opt-In Effect Application

Issue: agentjido/jido_ai#170
Date: 2026-02-23

TL;DR

Jido.AI should not switch ReAct tool execution to auto-apply effects by default.

Instead:

mikehostetler

Jido Fly Control Plane Guide (jido_lib)

Date: 2026-02-22

1) Purpose

Build a production-grade Fly control plane inside jido_lib for all GitHub bots while preserving current synchronous bot APIs.

Core stack:

• Fly Machines API writes via req_fly
• Fly GraphQL API for read-side metadata/inventory
• Optional FLAME execution profile for burst workloads