Document Graft Echo readiness boundary

[flyingrobots]

Summary

• add a Graft/Echo readiness boundary note under docs/design/
• record what Echo origin/main now supports for Graft after the braid/strand roadmap merge
• make the remaining production-claim blockers explicit: stable app-safe TypeScript/Node packaging and durable retained-evidence recovery
• link the note from docs/BEARING.md and docs/index.md

Why

Graft can keep schema/model/adapter work moving against Echo's current posture, authority, strand, braid, runtime-host, and retained-evidence surfaces. It should not yet claim production-grade Echo-native structural history through a released TypeScript dependency or a restart-proof durable evidence path.

This document makes that boundary inspectable so Echo hardening work and Graft integration work do not drift into overclaiming.

Validation

• pnpm exec markdownlint-cli2 docs/design/graft-echo-native-readiness-boundary.md docs/BEARING.md docs/index.md
• git diff --cached --check
• scripts/check_spdx.sh
• pre-commit markdownlint/prettier
• pre-push docs-only verification

[coderabbitai]

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 57 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 454edb21-ea57-41eb-b547-af1130f232fd

📥 Commits

Reviewing files that changed from the base of the PR and between 3d6fdba and aa5f2f9.

📒 Files selected for processing (2)

• docs/BEARING.md
• docs/design/graft-echo-native-readiness-boundary.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/graft-echo-readiness-boundary

---

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 and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c97dd42f33

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".