docs: call Reflexio a learning platform, not a layer

[guangyu-reflexio]

What

The team standardised on "learning platform" as Reflexio's product category — not "learning layer", "self-improving layer/platform", or "self-learning platform". This updates the two places in this repo that named it something else.

File	Was	Now
AI_AGENT_INTEGRATION.md	"best-effort learning layer"	"best-effort learning platform"
benchmark/gdpval/RESULTS.md	"an external self-improvement layer"	"an external learning platform"
benchmark/gdpval/RESULTS.md	"Reflexio, a layer that reads a completed run"	"Reflexio, a learning platform that reads a completed run"

Deliberately left unchanged

RESULTS.md also contains "an agent that is already self-improving". That is a claim about the customer's agent, not about Reflexio's category, and it is load-bearing for the benchmark's framing — the whole research question is whether an external platform adds measurable value on top of an agent that already improves itself. Renaming it would break the argument.

The benchmark/gdpval/memory/ module name is code structure, not marketing, and is untouched.

Related

The enterprise repo carries the same terminology change across the website, docs, and email templates. The superproject's gitlink bump follows once this merges.

Docs only — no code paths affected.

Summary by CodeRabbit

• Documentation
  • Updated integration guidance to describe Reflexio as a best-effort learning platform.
  • Refined benchmark documentation to present Reflexio as a learning platform that adds measurable value to already self-improving agents.
  • Updated client documentation to describe Reflexio as a learning platform for AI agents.
  • Improved consistency in how Reflexio’s capabilities and positioning are described across public-facing technical materials.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 26c5999f-a5c1-4ab0-8e5d-f4556c278c12

📥 Commits

Reviewing files that changed from the base of the PR and between 1ba3070 and ccfbf64.

📒 Files selected for processing (1)

• client_dist/README.md

Included review availability: 1 review is currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour.

---

📝 Walkthrough

Walkthrough

The documentation, benchmark abstract, and client README now describe Reflexio as a learning platform. The integration guidance retains its best-effort, non-blocking behavior description.

Changes

Terminology alignment

Layer / File(s)	Summary
Learning platform terminology AI_AGENT_INTEGRATION.md, benchmark/gdpval/RESULTS.md, client_dist/README.md	Updated Reflexio references from learning layer, external self-improvement layer, or adaptive memory layer to learning platform terminology. The benchmark abstract states that Reflexio reads completed task runs and adds measurable value to an already self-improving agent.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to ccfbf

This PR updates product terminology in documentation and does not change code or runtime behavior; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: yyiilluu

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main documentation change from “learning layer” to “learning platform.”
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/learning-platform-terminology

Warning

Your free Security trial is over. An organization admin can activate billing to continue.

---

_{Comment @coderabbitai help to get the list of available commands.}