Skip to content

2.3.0 — Contributions, corrections and portable history

Choose a tag to compare

@everywan-dev everywan-dev released this 12 Sep 04:21
· 86 commits to main since this release

Contributions, corrections and portable history

Version 2.3.0 adds an opt-in lifecycle for reviewing and incorporating contributions,
resolving challenges, and tracking correction effects through consumer conclusions
and reports. Portable transfer preserves foreign identities, evidence, dependencies
and supersession history while requiring explicit local correspondence and review.

A complete three-workspace example and everyday playbook cover the path from an
incorrect interpretation to corrected local use, report reflection and final handoff.
Consultation commands do not author canonical adopter files.

Compatibility and upgrade

Version 2.2.0 used consultation storage schema 1. Fresh 2.3.0 workspaces use schema 3.
Existing complete schema 1/2 stores remain readable for ordinary consultation and
are never migrated implicitly. To enable transfer, explicitly run:

python3 -P -m validated_memory consultation --store /absolute/workspace.sqlite upgrade

Upgrade retains workspace identity and original logical event fields. Older clients
refuse schema 3 stores. Schema 2 was an unreleased incorporation format; its retained
history remains compatible with the explicit upgrade.

Export requires --include-workspace-history: selecting a receipt does not narrow
the complete history disclosed. Imports establish retained history, not live source
freshness, authenticated authorship or automatic local authorization. Capsules are
bounded to 8 MiB and stored payloads to 32 MiB per workspace.

Validation

Release validation passed 1,098 local tests independently in three runs, alongside
legacy-client upgrade evidence and a complete synthetic correction lifecycle.
The installable wheel was built and checked independently, including four CLI
checks from the wheel alone. All 97 existing fenced examples remain unchanged.
Remote CI results are verified as part of publication. Predetermined fixture
judgments do not establish empirical usefulness or model/token savings.

Closes #7. Closes #8.