Skip to content

docs(readme): tighten tagline + bullet wording - #568

Merged
robotrocketscience merged 1 commit into
mainfrom
robotrocketscience-patch-1
May 10, 2026
Merged

docs(readme): tighten tagline + bullet wording#568
robotrocketscience merged 1 commit into
mainfrom
robotrocketscience-patch-1

Conversation

@robotrocketscience

@robotrocketscience robotrocketscience commented May 10, 2026

Copy link
Copy Markdown
Owner

Summary

Linked issues

-->

Type of change

  • feat: — new feature
  • fix: — bug fix
  • perf: — performance improvement
  • refactor: — code restructure with no behavior change
  • test: — test-only change
  • docs: — documentation-only change
  • build: — build system / dependency / lockfile change
  • ci: — CI workflow / hook change
  • release: — version bump / release tag
  • chore: — narrow housekeeping

Verification

  • uv run pytest tests/ -x -q — all green
  • uv run pyright src/ — strict, no new errors
  • uv run aelf --help — surface unchanged (or change documented)
  • CHANGELOG entry added under [Unreleased] (if user-visible)
  • Docs updated (if surface or behavior changed)

Test plan

Notes for reviewer

Summary by Sourcery

Update the README to refine product messaging and clarify installation and data-ownership semantics.

Documentation:

  • Tighten the introductory tagline and value proposition wording to better describe aelfrice’s behavior and guarantees.
  • Clarify installation steps with an explicit installation section and an optional follow-up step for adding the first rule.
  • Refine descriptions of local-only storage, auditability, reversibility, and offline operation to emphasize user control, traceability, and fully local, fast behavior.

Summary by CodeRabbit

  • Documentation
    • Updated README marketing copy with refined product messaging
    • Enhanced feature descriptions emphasizing local SQLite, full auditability, and absence of GPU/network requirements
    • Clarified core differentiators highlighting user control and local performance capabilities

Review Change Stack

@sourcery-ai

sourcery-ai Bot commented May 10, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates README.md marketing copy to refine product messaging, clarify installation and usage flow, and emphasize locality, auditability, and performance of the tool.

File-Level Changes

Change Details Files
Refine tagline and introductory marketing copy to be more concise and emphasize auditability.
  • Shorten the main tagline to remove explicit mention of rules and make it more general about preventing forgetting.
  • Adjust the sub-tagline phrasing to remove second-person possessive repetition and read more smoothly.
  • Clarify the SQLite description by explicitly stating it is fully auditable.
README.md
Clarify onboarding flow by adding installation heading and marking the rules section as optional.
  • Add an explicit installation section heading above the initial shell commands.
  • Label the rule-creation and agent restart section as optional to better signal its role in setup.
README.md
Strengthen feature bullets to highlight locality, traceability, control, and performance guarantees.
  • Rephrase local-only bullet to emphasize that all data stays on the user’s machine.
  • Extend the auditability bullet to mention querying with tools and full traceability.
  • Enhance the reversibility bullet to underscore user control over stored memories.
  • Clarify the performance bullet by explicitly contrasting retrieval with LLM calls and noting fast local operations.
README.md
Clarify core behavioral description of how aelfrice prevents forgetting during sessions.
  • Update the description of what aelfrice prevents from “forgetting” to explicitly mention amnesia and context drift for more precise behavior framing.
README.md

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented May 10, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@robotrocketscience has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 55 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a0fa3648-4bdb-4d35-8b4f-84934abf8533

📥 Commits

Reviewing files that changed from the base of the PR and between 645a304 and 2c6a71a.

📒 Files selected for processing (1)
  • README.md
📝 Walkthrough

Walkthrough

README.md marketing copy is refined across three sections: the hero tagline now emphasizes "Local SQLite. Fully auditable. No GPU, no network," the background benefit claim shifts from "stops the forgetting" to "stops the amnesia and context drift," and the differentiators bullets are reworded with tightened claims about auditability, reversibility, and local operation.

Changes

Marketing Copy Updates

Layer / File(s) Summary
Hero tagline and value proposition
README.md
Hero tagline is updated to emphasize "stops forgetting" with "Local SQLite. Fully auditable. No GPU, no network," replacing prior phrasing about rules and "Auditable."
Background benefit claim
README.md
Background/invisibility promise is rephrased from "stops the forgetting" to "stops the amnesia and context drift."
Differentiators section
README.md
"What makes aelfrice different" bullets are reworded to adjust and tighten claims: local-only, auditable-to-the-row, reversible, and no-GPU/no-network benefits are refined with new phrasing such as "Query it with the tools; full traceability," "You're the boss of your memories," and "not an LLM call / Operations are fast and local."

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly Related PRs

  • robotrocketscience/aelfrice#508: Both PRs make overlapping documentation edits to README.md—redrafting the hero tagline and rewording the "what it is/what you get" marketing sections.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is largely incomplete; the core Summary section is empty, Linked issues section lacks content/markers, and the Verification/Test plan/Notes sections are blank. Complete the Summary section with a one-paragraph explanation of the PR's purpose. Add linked issue references or the opt-out marker, and consider documenting the manual verification approach for the documentation changes.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: tightening README tagline and bullet wording for product messaging clarity.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch robotrocketscience-patch-1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added the docs label May 10, 2026

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • The new # To Install: and ## Optional headings break the existing heading hierarchy and read a bit awkwardly; consider renaming them to something like ## Installation and ### Optional: ... (e.g., “Optional: Add your first rule”) to keep the structure consistent and self-explanatory.
  • Some of the new marketing-style phrases (e.g., “stops the amnesia and context drift”, “You're the boss of your memories.”, “Operations are fast and local.”) add extra words without much new information; tightening or removing them would keep the README concise while preserving clarity.
  • The modified bullet about being auditable now adds “Query it with the tools; full traceability.”, which is a bit vague—if you keep it, consider briefly clarifying what “the tools” refers to (e.g., sqlite3, a specific GUI, or CLI examples).
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new `# To Install:` and `## Optional` headings break the existing heading hierarchy and read a bit awkwardly; consider renaming them to something like `## Installation` and `### Optional: ...` (e.g., “Optional: Add your first rule”) to keep the structure consistent and self-explanatory.
- Some of the new marketing-style phrases (e.g., “stops the amnesia and context drift”, “You're the boss of your memories.”, “Operations are fast and local.”) add extra words without much new information; tightening or removing them would keep the README concise while preserving clarity.
- The modified bullet about being auditable now adds “Query it with the tools; full traceability.”, which is a bit vague—if you keep it, consider briefly clarifying what “the tools” refers to (e.g., `sqlite3`, a specific GUI, or CLI examples).

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@github-actions github-actions Bot added the attn:merge-conflict PR branch needs rebase label May 10, 2026
@github-actions

Copy link
Copy Markdown

This PR is now behind main. Rebase locally so your commit signatures stay intact:

git fetch origin && git checkout 'robotrocketscience-patch-1' && git rebase origin/main
# resolve conflicts if any, then
git push --force-with-lease

Auto-rebase was removed because the bot has no signing key; rebasing as the bot strips author signatures and the required_signatures rule on main then blocks the merge. See #341.

@robotrocketscience
robotrocketscience enabled auto-merge (rebase) May 10, 2026 06:13
auto-merge was automatically disabled May 10, 2026 06:13

Branch protection rule check failed

@robotrocketscience

Copy link
Copy Markdown
Owner Author

[claim:review:godel:2026-05-10T17:27:54Z]

robotrocketscience added a commit that referenced this pull request May 10, 2026
Marketing-tone edits salvaged from #568 (which was opened against a
pre-v2.0 README via web UI; the destructive parts — Session-start
section deletion + v2.1.0 → v1.7 Status revert — are dropped).

Net change: tagline (forgetting your rules → forgetting; your way → the
way; Auditable → Fully auditable), lead-paragraph framing (stops the
forgetting → stops the amnesia and context drift), and four bullet-tone
tweaks (Local-only, Auditable, Reversible, No GPU).
@robotrocketscience
robotrocketscience force-pushed the robotrocketscience-patch-1 branch from 1559e8d to 645a304 Compare May 10, 2026 18:08
@robotrocketscience robotrocketscience changed the title Update README.md docs(readme): tighten tagline + bullet wording May 10, 2026
@robotrocketscience robotrocketscience removed the attn:merge-conflict PR branch needs rebase label May 10, 2026
@robotrocketscience

Copy link
Copy Markdown
Owner Author

Salvaged: dropped the destructive parts (Session-start subsection deletion + v2.1.0 → v1.7 Status revert + stray # To Install: / ## Optional headings) and kept only the marketing-tone edits — tagline, lead paragraph, and four bullet wordings. Rebased onto current main as a single signed docs: commit. CI should clear the prefix gates this time.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 49: Standardize the SQLite path placeholder in README.md by replacing the
variant `<git-common-dir>/aelfrice/memory.db` with the same format used
elsewhere (`<repo>/.git/aelfrice/memory.db`) (or vice versa—pick one canonical
placeholder) so both occurrences match; update the text that mentions
`~/.aelfrice/memory.db` only if you choose to normalize examples, and ensure the
two specific strings `<git-common-dir>/aelfrice/memory.db` and
`<repo>/.git/aelfrice/memory.db` are identical across the document to avoid
confusion.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1be9da80-7b18-45f6-98a8-725ac4a899c5

📥 Commits

Reviewing files that changed from the base of the PR and between aeb59d8 and 645a304.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
- **Auditable to the row.** Every belief has an `origin` column (`user_stated`, `user_corrected`, `commit_ingest`, …) tying it to the action that wrote it. Open the DB in any SQLite browser; nothing hidden.
- **Reversible.** `aelf uninstall --archive backup.aenc` encrypts the DB and deletes the live copy. `--purge` wipes it. `--keep-db` leaves data untouched. No vendor lock-in by construction.
- **No GPU, no network, no inference cost.** Runtime deps are `numpy`, `scipy`, `snowballstemmer` — all CPU, all offline. Retrieval is a sparse-matrix query, not a model call.
- **Local-only.** SQLite at `<git-common-dir>/aelfrice/memory.db` (or `~/.aelfrice/memory.db` outside git). No network calls, no telemetry, no accounts. One brain per project, all on your machine. ([PRIVACY.md](docs/PRIVACY.md))

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Inconsistent path format with line 138.

This line describes the SQLite location as <git-common-dir>/aelfrice/memory.db, but line 138 describes the same location as <repo>/.git/aelfrice/memory.db. While these may refer to the same location technically, the inconsistent placeholder formats could confuse readers. Consider standardizing on one format throughout the document.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 49, Standardize the SQLite path placeholder in README.md
by replacing the variant `<git-common-dir>/aelfrice/memory.db` with the same
format used elsewhere (`<repo>/.git/aelfrice/memory.db`) (or vice versa—pick one
canonical placeholder) so both occurrences match; update the text that mentions
`~/.aelfrice/memory.db` only if you choose to normalize examples, and ensure the
two specific strings `<git-common-dir>/aelfrice/memory.db` and
`<repo>/.git/aelfrice/memory.db` are identical across the document to avoid
confusion.

Marketing-tone edits salvaged from #568 (which was opened against a
pre-v2.0 README via web UI; the destructive parts — Session-start
section deletion + v2.1.0 → v1.7 Status revert — are dropped).

Net change: tagline (forgetting your rules → forgetting; your way → the
way; Auditable → Fully auditable), lead-paragraph framing (stops the
forgetting → stops the amnesia and context drift), and four bullet-tone
tweaks (Local-only, Auditable, Reversible, No GPU).
@robotrocketscience
robotrocketscience force-pushed the robotrocketscience-patch-1 branch from 645a304 to 2c6a71a Compare May 10, 2026 18:18
@robotrocketscience
robotrocketscience merged commit 2c6a71a into main May 10, 2026
15 checks passed
@robotrocketscience
robotrocketscience deleted the robotrocketscience-patch-1 branch May 10, 2026 21:43
@robotrocketscience

Copy link
Copy Markdown
Owner Author

[release:review:godel:2026-05-10T21:43:55Z]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant