Crate yoagent_state 

Simple but effective state and lineage for long-running agents.

yoagent-state stores append-only events and derives a small semantic graph for patches, evals, decisions, artifacts, and project references. Git and the filesystem remain the source of truth for concrete project changes.

Re-exports

pub use adapter::*;

pub use artifact::*;

pub use behavior::*;

pub use error::*;

pub use event::*;

pub use fork::*;

pub use git_store::*;

pub use graph::*;

pub use ids::*;

pub use observer::*;

pub use patch::*;

pub use policy::*;

pub use primitives::*;

pub use projector::*;

pub use query::*;

pub use runtime::*;

pub use schema::*;

pub use state::*;

pub use store::*;

Modules

adapter

In-process sink for callback-driven agents — the integration contract as a typed interface. YoAgentStateAdapter routes the entity-creating callbacks (run start/finish, model/tool calls, tool failures) through the paired record_* helpers and records the non-entity-creating finish events (model.finished, tool.finished) raw, auto-chained and correlated to the open run — so a log emitted through the sink is GASP-conformant: runs open/close (with validation), tool and model calls become paired nodes chained to the run, and failures carry ids and pairs.

artifact

behavior

error

event

fork

git_store

Git-backed event store satisfying the GASP store contract (the rules restated inline here are authoritative for this crate; the full spec lives in the gasp repo’s SPEC.md):

graph

ids

observer

patch

policy

primitives

projector

query

runtime

schema

state

store