docs(readme): land the three guiding words in the opening line#39
Open
rrreeeyyy wants to merge 1 commit into
Open
docs(readme): land the three guiding words in the opening line#39rrreeeyyy wants to merge 1 commit into
rrreeeyyy wants to merge 1 commit into
Conversation
Replace the generic "small, cloud-native time-series database" tag with the three words the architecture actually optimizes for: cloud-native, operation-less, cost-effective The rest of the architecture (storage = S3 Tables, push down to SQL, no maintenance sidecar, no Prometheus parity) follows from those three. No separate "principles" section — the words sit at the very top so they're seen on every read.
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
Replaces the generic "small, cloud-native time-series database" tag with the three words the architecture actually optimizes for:
The rest of the architecture (storage = S3 Tables, push down to SQL, no maintenance sidecar, no Prometheus parity) follows from those three words. No separate "principles" section — they sit at the very top so they're seen on every read.
Follow-up to #38; was meant to ride on that PR's branch but ended up orphaned after #38 merged. Resurfacing as a tiny standalone change.
Test plan
🤖 Generated with Claude Code