# For agents: A continuing responsibility

The ideal OpenProse · board 12 of 17 · 2026-10-09.
This deck describes a proposed experience.

Maintain a responsibility across invocations, doing work when evaluation shows it is needed.

## On the slide

**Keep the documentation aligned with the selected model.**

Observe → evaluate → if unmet, do required work → reassess

Preserve evidence and responsibility between invocations.

## Explanation

An ongoing agreement can take the complete documentation contract as its subject. After the first successful update, the responsibility continues. Later invocations receive relevant changes, the selected agreement, and enough retained state to understand what remains. A result may need updating; a new review may be due even if the text is unchanged. Someone or something must own the continuing responsibility. The environment supplies event delivery, scheduling, access, and persistence. The contract makes the requirements explicit; the operational system must actually provide the capabilities that keep them active.

## Whiteboard sequence

Open only the frames useful to the question. Later frames add to the same board;
the final frame contains the complete drawing.

- [Frame 1 — black core](https://prose.md/visual-guide/2026-10-09/ideal/slide-12-layer-01.png)
- [Frame 2 — cumulative reveal](https://prose.md/visual-guide/2026-10-09/ideal/slide-12-layer-02.png)
- [Frame 3 — final](https://prose.md/visual-guide/2026-10-09/ideal/slide-12-layer-03.png)

These explanations add no normative requirements. Read the
[selected kernel 0.3.0-rc.3](https://pkg.prose.md/releases/0.3.0-rc.3/core/README.md) for language rules.

[Previous: Back pressure from checking contracts](https://prose.md/visual-guide/ideal/11.md) · [Next: Open question: what starts the next invocation?](https://prose.md/visual-guide/ideal/13.md)

[All The ideal OpenProse boards](https://prose.md/visual-guide/ideal.md) · [Guide index](https://prose.md/visual-guide.md) · [Agent entry](https://prose.md/agents.md)