docs(v1-readiness): 📝 reclassify blob file completeness as out-of-scope#167
Merged
justapithecus merged 1 commit intoMar 22, 2026
Merged
Conversation
§9 (Blob File Completeness) assumed Lode should track files written via Store.Put() directly — bypassing the Dataset write path. This is a caller-side usage pattern, not a Lode gap. The manifest describes files Lode wrote; caller-managed sidecar files are the caller's responsibility. - Reclassify §9 criteria as out-of-scope with rationale - Update quarry friction note: CAS resolved via WithRetryCount (v0.9.0), blob completeness reclassified - Add PUBLIC_API.md §Sidecar Files and Store Access documenting correct patterns (StreamWrite per blob, file inventory in Metadata) and the anti-pattern (Store.Put bypass without tracking) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
justapithecus
deleted the
andrew/docs/v1-readiness/reclassify-blob-completeness
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reclassifies V1_READINESS §9 (Blob File Completeness) as out-of-scope based on quarry dogfood analysis. The friction quarry reported — sidecar files not enumerable via manifest — stems from writing files via
Store.Put()directly, bypassing the Dataset write path. This is a caller-side usage pattern, not a Lode design gap. Adds PUBLIC_API.md guidance documenting correct patterns.Highlights
WithRetryCount) and §9 reclassification. Remaining friction is caller-side.StreamWriteper blob, file inventory inMetadata) and the anti-pattern (Store.Put bypass without tracking).Test plan
scripts/verify-snippets.shpasses (new code fences use<!-- illustrative -->)🤖 Generated with Claude Code