Establish Echo's sealed public runtime boundary

[flyingrobots]

Goal

Establish the first sealed Rust host facade and freeze the authority-safe Cargo package boundary required before Echo can prepare a public alpha release.

Plan

• Add a publish-disabled flyingrobots-echo-runtime facade for host construction and recovery
• Prove the facade compiles and recovers without native rule bootstrap
• Record the accepted protocol, kernel, WAL, and sealed-runtime ownership boundary
• Add package-prefix, dependency-direction, feature-surface, and authority-escape guards
• Extract the public package closure and prove it with a clean-room external host

Current status

The first construction/recovery witness and canonical architecture policy are complete. Full local PR preflight passes. The crate remains publish = false; warp-core remains an unpublished dependency; no registry, tag, release, ownership, or publication action has occurred. This is a stacked follow-up to the provider branch and intentionally targets that branch until its dependency lands.

Open questions

None for the current checkpoint. Later extraction work must satisfy the frozen authority and feature-surface invariants before publication can be proposed.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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.}