docs: VOCABULARY.md — shared terms aligned to Bastion #10
Conversation
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
Defines the project's vocabulary and aligns it with Nathan's Bastion so the two tools share language. Adopts Bastion's Site -> Zone -> Asset hierarchy + policy inheritance (history/drift/cadence/vault) and the full id set (ARK, CURIE, badge, RDN, HALO, ZOLO, BLONDE, genus, vault). Resolves four term collisions: - zone = policy/grouping ONLY; packing (solo/bundle/shard) is per-asset, never a zone - 'asset' is canonical (retires the informal 'target') - reclaim 'source drift' renamed to free 'drift' for the policy key - 'genus' = backup lineage (Bastion meaning), not a cosmetic tag Keeps 'quaver' as our deliberately-lossless variant of Bastion's Quantim. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ed by design (not 'lossy') Fixes a wrong characterization I introduced. 'quaver' is Nathan's own term (a property on Bastion's Quantim class), NOT a coinage of ours, and it is not a 'lossless' anything. Quantim deliberately quantizes time-of-day to ~67-second buckets (~1-minute precision, per its docstring) in 7-8 chars — a sensible, intentional choice for backup stamps, not lossy tooling used carelessly. Now defines Quantim/quaver/quake accurately and notes BLONDE embeds the 8-char str(Quantim) form (3-digit year, valid to 2999). We adopt Bastion's encoding as-is; no invented 'lossless' variant. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign in
to join this conversation on GitHub.
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.
Adds
docs/VOCABULARY.md— the shared term definitions for this project, aligned to Bastion so the two tools speak the same language.history/drift/cadence/vault) — a zone is a policy/path grouping (e.g.landing-zonevsrepository), not a packing boundary.Docs-only; defines the language the incremental/size-routing RFC (#7) and PRs build on. Review the term choices.
🤖 Generated with Claude Code