docs(v1-readiness): 📝 add v1.0 release criteria and dogfooding tracker#106
Merged
justapithecus merged 3 commits intomainfrom Feb 7, 2026
Merged
docs(v1-readiness): 📝 add v1.0 release criteria and dogfooding tracker#106justapithecus merged 3 commits intomainfrom
justapithecus merged 3 commits intomainfrom
Conversation
Normative readiness document defining 30 verifiable criteria across 9 categories that must all pass before v1.0 can be tagged. Includes dogfooding registry with per-project evidence tracking and a quarry template pre-populated. - Gate rule: all criteria must pass, none waived - Criteria: API freeze, manifest freeze, Dataset dogfooding, Volume dogfooding, error paths, S3 verification, known limitations, documentation completeness, data correctness - Each criterion has an evidence block for date/observer/issue tracking - Out-of-scope section explicitly excludes CAS, Zarr, perf, new adapters - ARCH_INDEX.md updated with reference to new document Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Private downstream projects use redacted aliases and backend-agnostic usage descriptions. Evidence blocks and issue references must not leak private context — private tracker issues referenced as (private). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…leaks Evidence and usage profiles must describe Lode-level behavior only, not the consumer's architecture or data model. Prevents private project implementation details from being inferred through dogfooding entries. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
Adds a normative v1.0 readiness document (
docs/V1_READINESS.md) defining 30 verifiable criteria across 9 categories that must all pass before v1.0 can be tagged. Stability is proven by usage and time, not design review.Highlights
ARCH_INDEX.mdupdated with reference to the new documentTest plan
V1_READINESS.mddocs/V1_READINESS.mdcreated,docs/ARCH_INDEX.mdedited)🤖 Generated with Claude Code