Official Examples, Localized Jido core + signals + memory + persist

Jido example agents running inside this app.

This workspace turns the official Jido example patterns into concrete, supervised agents in the repo. Everything below is live: state changes, emitted signals, memory spaces, and persisted checkpoints all flow into the centralized agent monitor.

Live Agents

4

Counter, document processor, notebook, and metrics collector.

Patterns

5

Mapped directly from the official Jido examples page into this repo.

Persisted Count

None

Latest checkpoint for the counter example.

Counter Agent

Stateful counter with threshold signals

Mirrors the classic counter example, but also emits threshold milestones into the metrics agent and supports save/restore via `Jido.Persist`.

idle

Count

0

Threshold

10

Operations

0

Last Change

No counter changes yet.

Saved Snapshot

No persisted counter snapshot yet.

Metrics Agent

Cross-agent signal collector

Receives emitted `metric.recorded` signals from the other example agents so you can see multi-agent fan-out without leaving the app.

Total Metrics

0

Metric Families

No emitted metrics yet

Recent Metrics

Trigger a counter or document action to generate emitted metric traffic.

Document Processor

Inbound or uploaded document routing

Submit a document shape and the agent will classify it, store local state, emit a metrics signal, and add a note into the memory-backed notebook agent.

Processed Total

0

Last Classification

none

Recent Documents

No documents have been processed yet.

Counts

Contract 0
Identity 0
Invoice 0
Spreadsheet 0
Unknown 0
Origin: Inbound 0
Origin: Uploaded 0

Notebook Agent

Memory-backed notes

Uses Jido memory spaces for durable in-process note storage. The document processor also writes into this agent through an emitted signal.

Note Count

0

Memory Spaces

No spaces yet

Recent Notes

Manual notes and document-derived notes will show up here.

Documentation

How the local demos map to the official Jido examples

The goal here is not to copy the examples page verbatim, but to operationalize the same primitives inside a Phoenix app with shared monitoring.

Counter Agent

CounterAgent

Stateful counter with increment, decrement, reset, and threshold milestones.

Jido.Agent signal routing state ops

Signal Patterns & Routing

DocumentProcessorAgent

Accepts inbound or uploaded documents, classifies them, and records typed document state.

Jido.Agent Jido.Signal routing

Emit Directive

MetricsAgent + NotebookAgent fan-out

Counter and document flows emit follow-on signals into other agents so the monitor sees agent-to-agent traffic.

Directive.Emit cross-agent signals central monitor

Plugin Basics

NotebookAgent

Stores notes in memory spaces with category totals and a live note feed.

Jido.Memory.Plugin Jido.Memory.Agent

Persist

CounterAgent checkpoint

Saves and restores a counter snapshot so the same agent state can be thawed back into the running server.

Jido.Persist Jido.Storage.File