vrr/ouroboros
2
0
Fork 0
mirror of https://github.com/razzant/ouroboros.git synced 2026-10-14 22:54:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
ouroboros/docs/ARCHITECTURE.md
Ouroboros 2163db3ec3 release: 7.6.0 
Every version carrier moves to 7.6.0 through ouroboros.tools.release_sync:
VERSION, pyproject.toml and uv.lock, web/package.json and its lock, the
gateway contract version, the README badge and download links, the two
install pages and the architecture header. The README Version History
gains the 7.6.0 row, which also generates the release notes, and the
oldest minor row (7.1.0) moves to the retained-in-Git sentence, keeping
the history within its limits (2 major, 5 minor, 5 patch rows).

The row discloses that the old dialogue memory is imported one way:
rolling the code back to 7.5.1 does not bring back what the new memory
recorded after the update. Its claims were checked against the code and
the commits since v7.5.1 by a separate review row, not against PR bodies.
2026-10-05 20:59:39 +03:00

1.7 KiB
Raw Permalink Blame History

Ouroboros v7.6.0 — Architecture & Reference

This is the present-tense operational map of Ouroboros (BIBLE P6), in three layers: structure (what exists and where), operation (files, env keys, state paths, endpoints, flows), and rationale; it is NOT a changelog, and version history lives in README.md, git tags, and the commit log. Every important WHY stays in this book at least briefly, while mechanism detail lives in the module docstring the map points to by name, and rationale must be self-contained — future maintainers should not need old commits to understand why a guard, review gate, or lifecycle exists. The chapters below are the book: each owns one section of the map, and a change replaces the description of the node it touched.

Chapters