[PR #2310] [CLOSED] docs: note that service data cannot be reverse engineered #5155

Closed
opened 2026-10-31 01:04:23 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2310
Author: @walidboulanouar
Created: 10/12/2026
Status: ❌ Closed

Base: main ← Head: docs/data-behind-a-service


📝 Commits (2)

  • fb1abc1 docs: note that service data cannot be reverse engineered
  • 5771f73 docs: scope service data limitations to absent server-only content

📊 Changes

1 file changed (+11 additions, -0 deletions)

View changed files

📝 docs/index.md (+11 -0)

📄 Description

Summary

I work on looot. This is outside REA's usual scope, so feel free to close it if it doesn't fit. I'm proposing it because agents using REA sometimes hit the point where the thing they need is data, not code.

This adds one short section to docs/index.md saying REA recovers code, protocols, behavior, and endpoints, but not the data behind a service, and pointing to a data API for that part of a task. looot is named as one example.

Problem and expected behavior

An agent can take an app apart and still not have the contact, company, or search data the app serves. The docs do not say where REA's reach ends. After this change they do.

Change and scope

One section, 10 lines, in docs/index.md. No code, no new provider, no integration, no change to any REA tool. README and its translations are untouched.

Follow the contribution scope. Not applicable: documentation only, no new capability.

Contract and boundary impact

  • Semantic owner and earliest changed stage: docs home page

  • Contribution scope fit and linked maintainer decision: outside the usual scope, see Summary. No maintainer decision linked.

  • CLI and MCP/tool-catalog contract: none

  • Provider, bridge, target-format, or platform compatibility: none

  • Evidence, artifact, provenance, or reconstruction contract: none

  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable

  • Generated metadata, package, or installation impact: none

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none, docs only
  • Base reproduction or other evidence: not applicable
  • Remaining proof gaps: the looot figures (about 2,500 endpoints, 90+ providers) come from looot's own catalog and are not verified by REA.

Validation performed

  • git diff --stat shows 1 file, 10 insertions
  • Not run: npm run docs:check and prettier (dependencies not installed locally)

Compatibility, safety, and release

  • Breaking changes or migration steps: none
  • Security, privacy, process, or containment review: adds two outbound links and one MCP URL as text. Nothing is fetched or executed.

Before merge

  • One focused outcome.
  • Checked the diff for secrets and unrelated changes.
  • Maintainer scope fit: pending, the maintainer may close this.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/2310 **Author:** [@walidboulanouar](https://github.com/walidboulanouar) **Created:** 10/12/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/data-behind-a-service` --- ### 📝 Commits (2) - [`fb1abc1`](https://github.com/morluto/rea/commit/fb1abc1f5646cd72f556a26cf6da6ba9827aa162) docs: note that service data cannot be reverse engineered - [`5771f73`](https://github.com/morluto/rea/commit/5771f733d73934df3288e12157c48d8609a0a1a0) docs: scope service data limitations to absent server-only content ### 📊 Changes **1 file changed** (+11 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/index.md` (+11 -0) </details> ### 📄 Description ## Summary I work on looot. This is outside REA's usual scope, so feel free to close it if it doesn't fit. I'm proposing it because agents using REA sometimes hit the point where the thing they need is data, not code. This adds one short section to `docs/index.md` saying REA recovers code, protocols, behavior, and endpoints, but not the data behind a service, and pointing to a data API for that part of a task. looot is named as one example. ## Problem and expected behavior An agent can take an app apart and still not have the contact, company, or search data the app serves. The docs do not say where REA's reach ends. After this change they do. ## Change and scope One section, 10 lines, in `docs/index.md`. No code, no new provider, no integration, no change to any REA tool. README and its translations are untouched. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Not applicable: documentation only, no new capability. ## Contract and boundary impact - Semantic owner and earliest changed stage: docs home page - Contribution scope fit and linked maintainer decision: outside the usual scope, see Summary. No maintainer decision linked. - CLI and MCP/tool-catalog contract: none - Provider, bridge, target-format, or platform compatibility: none - Evidence, artifact, provenance, or reconstruction contract: none - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable - Generated metadata, package, or installation impact: none - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none, docs only - Base reproduction or other evidence: not applicable - Remaining proof gaps: the looot figures (about 2,500 endpoints, 90+ providers) come from looot's own catalog and are not verified by REA. ## Validation performed - `git diff --stat` shows 1 file, 10 insertions - Not run: `npm run docs:check` and prettier (dependencies not installed locally) ## Compatibility, safety, and release - Breaking changes or migration steps: none - Security, privacy, process, or containment review: adds two outbound links and one MCP URL as text. Nothing is fetched or executed. ## Before merge - [x] One focused outcome. - [x] Checked the diff for secrets and unrelated changes. - [ ] Maintainer scope fit: pending, the maintainer may close this. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:04:23 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#5155
No description provided.