Historical record. This page describes the results and requirements recorded in revision 61e75e9. It is not a report of checks on the current revision.

OKF v0.2.0

v0.2.0 is the existing annotated tag containing the transactional mutation foundation from commit 43f7214 and the parser-backed lossless mutation implementation from commit bb9c169.

Public API additions

• immutable snapshots and algorithm-qualified revisions;
• versioned store.ChangeSet operations and preconditions;
• staged preview and validation;
• optimistic compare-and-swap commits and inspectable conflicts;
• bounded idempotency receipts;
• durable journaled store/fs commits and recovery;
• parser-backed lossless EnsureRelation, MoveConcept, and RenameFragment mutation planning.

Existing bundle parsing, validation, graph, CLI, and MCP wire contracts remain source compatible. The release does not add methodology profiles, workflow states, or business-specific domain types.

Platform and isolation scope

The durable store/fs implementation in the tag targets Darwin and Linux. Leases are advisory, so raw editors do not coordinate and raw readers may observe a multi-file rename during publication. Recovery provides transaction completion, not distributed isolation. The v0.2.x release-engineering follow-up makes unsupported targets compile-safe and returns a typed runtime error instead of missing symbols.

Distribution and evidence

This is a Go-module/source release. No prebuilt binaries are published.

• Transactional mutation issue #1
• Release-engineering follow-up issue #2
• Reviewable release-engineering pull request #3
• Parser-backed mutation verification evidence
• Release engineering and CI contract
• Requirement-to-evidence table

The existing tag must not be moved or recreated. Post-tag release-engineering checks are reported separately from verification of the tagged source.