docs: add cross-host local learning marketing brief

[yyiilluu]

Summary

• Add a dated marketing brief for the cross-host local learning positioning now that Claude Code, Codex, and OpenCode are all covered in public docs/metadata.
• Capture read-only market signals from GitHub metadata and X/Twitter search without taking any external write action.
• Provide ready-to-post first-party copy, X draft/reply copy for Yi to review, non-X distribution ideas, and guardrails.

Test Plan / Validation

• git diff --cached --check
• python3 validation that the brief preserves public terminology and avoids raw Reflexio storage/API names.

Marketing rationale

• The public conversation around coding-agent memory is broad and crowded; this brief keeps claude-smart differentiated around learning from corrections into Preferences, Project-specific skills, and Shared skills.
• The copy is factual, low-risk, and tied to repo-visible capabilities plus the benchmark already documented in EXPERIMENT.md.

Summary by CodeRabbit

• Documentation
  • Added a marketing brief for claude-smart describing cross-host local learning across Claude Code, Codex, and OpenCode.
  • Included messaging guidance, market research notes, ready-to-post update copy, reply drafts, and alternative distribution prompts.
  • Documented the correction-to-shared-skill learning loop and references for further validation.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a dated marketing brief positioning claude-smart as a cross-host local learning layer, documenting market signals, proof hooks, post drafts, distribution prompts, and messaging guardrails.

Changes

Marketing brief

Layer / File(s)	Summary
Positioning and proof framing marketing/2026-07-13-cross-host-local-learning-brief.md	Defines the cross-host local learning narrative, records read-only market signals, and identifies dashboard, local storage, and EXPERIMENT.md proof references.
Distribution drafts and guardrails marketing/2026-07-13-cross-host-local-learning-brief.md	Adds first-party, X, and non-X distribution drafts with restrictions on unsupported claims, automatic posting, competitor attacks, and conditional release messaging.

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

🚥 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 summarizes the change: adding a marketing brief about cross-host local learning.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch marketing/cross-host-memory-20260713

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

marketing/2026-07-13-cross-host-local-learning-brief.md (1)

5-19: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Make the market claims reproducible.

The origin/main metadata and X-search findings are time-sensitive, but the brief records neither a check date nor durable source references. Add the verification date and links or a captured search artifact so this dated brief can be revalidated before reuse.

🤖 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 `@marketing/2026-07-13-cross-host-local-learning-brief.md` around lines 5 - 19,
Update the “Read-only market signals checked” section with the verification date
and durable references for the origin/main metadata and X-search findings.
Include links or a captured search artifact that preserves the checked results,
while keeping the existing market claims unchanged.

🤖 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 `@marketing/2026-07-13-cross-host-local-learning-brief.md`:
- Line 34: Update the posting guidance sentence to require that issue `#130` is
resolved before using the post, removing the contradictory “especially if issue
`#130` is still open” condition. Keep the existing instruction to use it after
active release/install issues are resolved and align it with the guidance on
line 86.

---

Nitpick comments:
In `@marketing/2026-07-13-cross-host-local-learning-brief.md`:
- Around line 5-19: Update the “Read-only market signals checked” section with
the verification date and durable references for the origin/main metadata and
X-search findings. Include links or a captured search artifact that preserves
the checked results, while keeping the existing market claims unchanged.

🪄 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 269829a1-86f9-4904-9b2b-2838c9e6a1f0

📥 Commits

Reviewing files that changed from the base of the PR and between 800343f and 58a7b52.

📒 Files selected for processing (1)

• marketing/2026-07-13-cross-host-local-learning-brief.md

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Fix the contradictory issue #130 posting condition.

This says to use the post after the issue is resolved, “especially if issue #130 is still open,” while Line 86 correctly says to avoid broad amplification while it remains open. The current wording could authorize posting during the blocked state.

Suggested wording

-Use after any active release/install issue is resolved, especially if issue `#130` is still open when posting.
+Use only after active release/install issues are resolved. If issue `#130` is still open, keep messaging to docs/feedback channels until fixed.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Use after any active release/install issue is resolved, especially if issue #130 is still open when posting.
	Use only after active release/install issues are resolved. If issue `#130` is still open, keep messaging to docs/feedback channels until fixed.

🤖 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 `@marketing/2026-07-13-cross-host-local-learning-brief.md` at line 34, Update
the posting guidance sentence to require that issue `#130` is resolved before
using the post, removing the contradictory “especially if issue `#130` is still
open” condition. Keep the existing instruction to use it after active
release/install issues are resolved and align it with the guidance on line 86.