yoagent-state 0.3.0

Durable state and lineage for long-running agents.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61

# Safety Model

`yoagent-state` is designed around explicit mutation and evidence-backed promotion.

## Self-modification must be explicit

Agents should not silently mutate prompts, policies, tools, memory, or code.

Use patches.

## Promotion requires evidence

A patch should not be promoted without at least one of:

- passing eval
- passing test
- human approval
- policy approval

The evidence should be represented in lineage, not hidden in a transcript.

```mermaid
flowchart LR
  patch["patch"]
  evidence["eval / test / approval"]
  decision["decision"]
  promoted["promoted status"]

  patch -- validated_by --> evidence
  patch -- approved_by --> decision
  evidence --> promoted
  decision --> promoted
```

## Project base must be checked

If a patch was created against commit `abc123`, do not blindly apply it to another commit.

Mark the patch stale or conflicted, then reobserve.

## Staleness is first-class

Assumptions go stale. So do patches, projections, and observations.

Use stale nodes or statuses when state is no longer current.

## Important artifacts need hashes

Use hashes for:

- diffs
- logs
- files
- eval outputs
- generated reports

Hashes make lineage more trustworthy.

## Keep the layer small

Do not turn `yoagent-state` into a hidden automation engine. Behaviors and policies are allowed, but they should be explicit, registered, replayable, and represented in the graph. State and lineage come first.