Historical implementation specification, preserved from revision 61e75e9. Requirements describe the work planned at that time, not current usage instructions. Original document.

Technical specification: OKF v0.2 durability contract in `store/fs`

1. Assessment

store/fs stores opaque regular-file bytes and can already durably save v0.2 metadata and assets. Production changes specific to the specification are unnecessary; an explicit contract test corpus is required.

Dependencies: task10.md, task11.md, task16.md.

2. Fixture

Create a bundle containing:

root okf_version: "0.2";
nested sources/generated/verified/lifecycle;
Attested Computation;
references/computations/*.sql;
references/attesters/*.py;
an executor .md file.

3. Tests

All tests use AAA.

Snapshot Paths/ReadFile preserve metadata and assets byte for byte.
Any metadata or asset byte change changes the revision.
An index migration that changes only the version changes the revision.
Failure after durable journal synchronization → reopen/recovery → exact post-transaction state.
Commit receipt replay is idempotent.
Tampered, missing or symlinked staged payload → storage corruption, with no partially visible write.
v0.1 fallback and the final v0.2 state pass staged validation.
The existing Darwin/Linux and unsupported-platform matrix continues to pass.

Do not duplicate generic large-payload, provenance or no-follow tests without adding coverage for a new v0.2 contract.

4. Boundary

Keep journal and receipt schema versions unchanged.
Do not store runtime attestation receipts.
.okf/** remains private and invisible to revision computation.
An asset-only change must at least appear in ChangedFiles; reverse semantic ChangedRefs for computation dependencies is a separate graph/store extension, excluded until a public asset mutation operation exists.

5. Acceptance criteria

Crash/recovery supports an Appendix-style v0.2 bundle byte for byte.
The transaction protocol is identical for v0.1/v0.2.
go test ./store/fs and the platform matrix pass.