# For agents: OpenProse today

Edition: 2026-10-09.

A dated account of experimental release 0.3.0-rc.3 on October 9, 2026, with published definitions and bounded mathematical, synthetic, and mocked evidence. It includes open questions and a proposed checking assembly; it does not establish broad reliability or an unattended service.

Choose a board for its slide copy, developed explanation, and original image sequence.

- [01 — OpenProse today](https://prose.md/visual-guide/current/01.md): A public Markdown kernel and versioned libraries support an experimental contract-authoring system.
- [02 — A small complete program](https://prose.md/visual-guide/current/02.md): A published brief example preserves fictional quantities, evidence, and unresolved questions.
- [03 — Open question: intent and the contract](https://prose.md/visual-guide/current/03.md): Choosing requirements that preserve user intent remains an open authoring question.
- [04 — The effective agreement](https://prose.md/visual-guide/current/04.md): Adopted definitions govern the brief, while supplied notes remain data.
- [05 — Contracts as parameters](https://prose.md/visual-guide/current/05.md): A collection-assessment contract accepts a checker and preserves each entry’s subject and bindings.
- [06 — The kernel and selected documents](https://prose.md/visual-guide/current/06.md): Read the selected agreement directly, with package installation treated as a separate operation.
- [07 — What is in the libraries](https://prose.md/visual-guide/current/07.md): Select shared definitions as needed across twenty published application libraries.
- [08 — Doing the work and assessing it](https://prose.md/visual-guide/current/08.md): Keep the evaluator’s completed work separate from its finding about the subject.
- [09 — Testing uses the same language](https://prose.md/visual-guide/current/09.md): Compose controlled tests from fixture, observation, and evaluator contracts, retaining every outcome.
- [10 — Back pressure from checking contracts](https://prose.md/visual-guide/current/10.md): A proposed assembly applies supplied checking contracts to retained executions and supports deliberate change.
- [11 — A bounded execution that fulfilled its agreement](https://prose.md/visual-guide/current/11.md): One bounded proof commission fulfilled its selected agreement, including all equality cases.
- [12 — Correct mathematics, incomplete fulfillment](https://prose.md/visual-guide/current/12.md): A separate Classification result had correct mathematics but omitted a required statement.
- [13 — Substitution across application libraries](https://prose.md/visual-guide/current/13.md): Substituting forecast contracts changed feasibility in a synthetic production-planning experiment.
- [14 — Continuing work needs an operating environment](https://prose.md/visual-guide/current/14.md): A maintained-brief agreement preserves history while an external coordinator launches bounded invocations.
- [15 — Open question: entry points and triggers](https://prose.md/visual-guide/current/15.md): Beyond the release-brief example, responsibility between passes and the next trigger remain open.
- [16 — What the evidence supports](https://prose.md/visual-guide/current/16.md): Separate available definitions, bounded observations, and claims the evidence has not established.
- [17 — Your first contract](https://prose.md/visual-guide/current/17.md): Begin with one bounded job, inspect its result, then test whether reuse helps a second job.

[Guide index](https://prose.md/visual-guide.md) · [Agent entry](https://prose.md/agents.md)