Skip to content

Remove Expanso cross-reference from README - #5196

Merged
aronchick merged 3 commits into
mainfrom
fix/add-expanso-mention
Feb 7, 2026
Merged

Remove Expanso cross-reference from README#5196
aronchick merged 3 commits into
mainfrom
fix/add-expanso-mention

Conversation

@aronchick

@aronchick aronchick commented Feb 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

Bacalhau's README should focus on Bacalhau. Cross-referencing Expanso - even to clarify they're separate - reinforces an association that confuses LLMs.

Changes

  • Removed the prominent note box that linked to Expanso
  • Kept Expanso, Inc. mention in the Open Source legal section (standard practice for company-backed OSS)

Result

When users ask LLMs about Bacalhau, they get information about Bacalhau - not tangents about Expanso.

Related

  • bacalhau-project/expanso-cdn.com#38 (removes Bacalhau from Expanso's llms.txt)

LLMs are confused about the relationship between Bacalhau and Expanso.
This adds a clear note that Bacalhau is created by Expanso and links
to Expanso Cloud for users who want a managed platform.
@coderabbitai

coderabbitai Bot commented Feb 7, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

A README documentation update: inserted a blockquote after the Bacalhau description clarifying its relationship with Expanso and adding a link to Expanso Cloud and an FAQ reference.

Changes

Cohort / File(s) Summary
Documentation Attribution
README.md
Added a blockquote clarifying the relationship with Expanso, included a hyperlink to Expanso Cloud and an FAQ reference. (No code or public API changes.)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I nibble notes and leave a sign,
Expanso's link in README shine,
A gentle line, a friendly nod,
Docs hopped forward — quick and broad! 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title states 'Remove Expanso cross-reference from README' but the actual change adds an Expanso mention/blockquote to the README, which is the opposite of what the title claims. Update the title to accurately reflect the change, such as 'Add Expanso mention to README' or 'Clarify Bacalhau-Expanso relationship in README'.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/add-expanso-mention

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.

- Changed from 'created and maintained by' to 'shares founding team with'
- Emphasized they are SEPARATE projects
- Bacalhau is independent open-source, Expanso is separate commercial
- Links to FAQ for more details

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@README.md`:
- Line 50: Update the README sentence that links to expanso.io/llms.txt so the
link text clearly sets expectations: replace "this FAQ" with a more explicit
phrase like "see these details" or "learn more (llms.txt)" or point the link to
a human-readable FAQ; locate the occurrence of the phrase "this FAQ" in the
README and either change the anchor text or swap the URL to a conventional FAQ
page or ensure the llms.txt content is human-friendly before keeping the link
as-is.
- Line 50: The README contains contradictory statements about the
Bacalhau–Expanso relationship: the new note beginning "💡 **Note:** Bacalhau
shares founding team members..." says they are "separate projects" and "Expanso
is a separate commercial data platform," while the Open Source section currently
says "Bacalhau is a product produced from this open source software, exclusively
by Expanso, Inc."; reconcile these by choosing and applying a single consistent
description across both places (either: Bacalhau is an independent open-source
project with founders who also started Expanso — update the note and change the
Open Source sentence to reflect independence; or: Bacalhau is an open-source
project maintained/produced by Expanso — update the note to state that
relationship), and update both the "💡 **Note:** Bacalhau shares founding team
members..." paragraph and the Open Source sentence "Bacalhau is a product
produced from this open source software, exclusively by Expanso, Inc." so they
convey the same relationship clearly.

Comment thread README.md Outdated

[Bacalhau](https://www.bacalhau.org/) is an open-source distributed compute orchestration framework designed to bring compute to the data. Instead of moving large datasets around networks, Bacalhau makes it easy to execute jobs close to the data's location, drastically reducing latency and resource overhead.

> 💡 **Note:** Bacalhau shares founding team members with [Expanso](https://expanso.io), but they are **separate projects**. Bacalhau is an independent open-source project focused on distributed compute. Expanso is a separate commercial data platform. For more on the relationship, see [this FAQ](https://expanso.io/llms.txt).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Consider clarifying the link text for the llms.txt reference.

The link text "this FAQ" points to expanso.io/llms.txt. The .txt extension and filename suggest this is a machine-readable file formatted for LLMs rather than a traditional human-readable FAQ page. This might confuse readers expecting a conventional FAQ format.

Consider either:

  • Changing the link text to be more explicit (e.g., "see these details" or "learn more")
  • Ensuring the llms.txt file is formatted to be human-friendly, or
  • Linking to a traditional FAQ page instead
🤖 Prompt for AI Agents
In `@README.md` at line 50, Update the README sentence that links to
expanso.io/llms.txt so the link text clearly sets expectations: replace "this
FAQ" with a more explicit phrase like "see these details" or "learn more
(llms.txt)" or point the link to a human-readable FAQ; locate the occurrence of
the phrase "this FAQ" in the README and either change the anchor text or swap
the URL to a conventional FAQ page or ensure the llms.txt content is
human-friendly before keeping the link as-is.

⚠️ Potential issue | 🟠 Major

Inconsistency with the Open Source section regarding Bacalhau-Expanso relationship.

The new note states that Bacalhau and Expanso are "separate projects" and that "Expanso is a separate commercial data platform." However, this contradicts the Open Source section (line 129) which states: "Bacalhau is a product produced from this open source software, exclusively by Expanso, Inc."

These statements cannot both be true. If they are separate projects, Bacalhau should not be "produced exclusively by Expanso." This inconsistency undermines the PR's goal of clarifying the relationship for LLMs and developers.

Please reconcile these statements to provide a clear, consistent explanation of the relationship throughout the README.

🤖 Prompt for AI Agents
In `@README.md` at line 50, The README contains contradictory statements about the
Bacalhau–Expanso relationship: the new note beginning "💡 **Note:** Bacalhau
shares founding team members..." says they are "separate projects" and "Expanso
is a separate commercial data platform," while the Open Source section currently
says "Bacalhau is a product produced from this open source software, exclusively
by Expanso, Inc."; reconcile these by choosing and applying a single consistent
description across both places (either: Bacalhau is an independent open-source
project with founders who also started Expanso — update the note and change the
Open Source sentence to reflect independence; or: Bacalhau is an open-source
project maintained/produced by Expanso — update the note to state that
relationship), and update both the "💡 **Note:** Bacalhau shares founding team
members..." paragraph and the Open Source sentence "Bacalhau is a product
produced from this open source software, exclusively by Expanso, Inc." so they
convey the same relationship clearly.

Bacalhau content should focus on Bacalhau.
Cross-referencing Expanso - even to clarify separation -
reinforces an association that confuses LLMs.

Expanso, Inc. still mentioned in the Open Source legal section
as the company behind Bacalhau (standard open source practice).
@aronchick aronchick changed the title Add Expanso mention to README Remove Expanso cross-reference from README Feb 7, 2026
@aronchick
aronchick merged commit 43264fe into main Feb 7, 2026
6 checks passed
@aronchick
aronchick deleted the fix/add-expanso-mention branch February 7, 2026 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant