Reframe README.md around U2U/U2I/I2I generalization#363
Open
em3s wants to merge 2 commits into
Open
Conversation
dosubot
Bot
added
size:M
em3s
changed the title
em3s
changed the title
em3s
force-pushed
the
docs/readme-u2u-u2i-i2i-framing
branch
2 times, most recently
from
13ebfab to
b723e22
Compare
Move the main framing from listing use-cases (likes/views/follows) to the three axes that fall out of the same source -> action -> target model: User-User (U2U), User-Item (U2I), and Item-Item (I2I). The underlying model is unchanged; only the lens shifts. - Update tagline to "One database for U2U, U2I, and I2I interactions" - Add a Why Actionbase section that introduces the three axes - Refresh the supported-operations list (GET, COUNT, SCAN/SEEK, AGG) and note multi-hop traversals are expressed by composing them - Surface planned operations (Global TopK, Per-entity TopK) - Rename "When (Not) to Use It" to "When to Use It" - State production timeline as "since 2024" instead of "for years" Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
em3s
force-pushed
the
docs/readme-u2u-u2i-i2i-framing
branch
from
b723e22 to
f395420
Compare
Expand U2U/U2I/I2I abbreviations in the opening tagline so first-time GitHub visitors understand the scope without scrolling. The abbreviations are still introduced in the Why Actionbase section below. Co-Authored-By: Claude Sonnet 4.6 (1M context) <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
Reframes the README around the generalized interaction database angle. The main framing moves from listing use-cases (likes / views / follows) to the three axes that fall out of the same abstraction: User–User (U2U), User–Item (U2I), and Item–Item (I2I).
The underlying model — source → action → target — is unchanged. Only the lens shifts: likes and follows are no longer the headline, but one slice (U2I) of a more general shape.
This framing came out of conversations with @zipdoki and @eazyhozy on a walk.
Other adjustments along the way:
Changes
README.mdaround the U2U / U2I / I2I axesHow to Test
Visual review via the GitHub README preview. No changes to external links (actionbase.io, blog, issue, stories) or to their targets.
AI Assistance
Repo About suggestion (out of PR scope; needs a maintainer to update via the GitHub UI):