Skip to content

README.md

Latest commit

 

History

History
41 lines (34 loc) · 2.23 KB

README.md

File metadata and controls

41 lines (34 loc) · 2.23 KB
Raw

Rho Architecture Plan

This directory holds the implementation and design docs for Rho, the main model-agnostic AI coding-agent CLI. graycode-eco is only the local parent folder for independent repositories.

Documents:

  • rho-current-vs-proposed.md - current workspace shape vs target Rho-centered repository architecture
  • graycode-ecosystem-summary.md - one-page repo role, dependency, and future cloud summary
  • rho-product-architecture.md - target architecture and runtime flow
  • rho-repo-roles.md - role of each Rho repo in the product ecosystem
  • rho-dependency-rules.md - import and ownership boundaries
  • eagle-spec.md - shared contracts layer and current status
  • rho-provider-abstraction.md - provider/runtime abstraction design
  • rho-review-verify-lifecycle.md - review and verification lifecycle
  • rho-architecture-v1-definition-of-done.md - realistic shipping bar for architecture v1
  • adr/ADR-0004-file-first-session-history.md - canonical session history and SQLite projection boundary
  • adr/ADR-0001-graycode-platform-telemetry-edge.md - constrained optional runtime edge from Rho to GrayCode Platform
  • tasks.md - historical implementation checklist from the initial architecture pass (superseded by the definition-of-done doc; kept for record)
  • adr/ - accepted architecture decision records, e.g. exceptions to the dependency rules above
    • ADR-0003-grok-behavioral-port-go-multirepo.md - Year 0 Grok behavioral port keeps Go multi-repo
  • Related (historical) execution track: docs/plans/YEAR-0-ACTIVE.md

Core rule:

rho is the main CLI/product. The other repositories are capabilities, contracts, integrations, tooling, or optional platform services that connect to it through the boundaries documented here.

Final target shape:

  • rho is the orchestrator and only primary product surface
  • flux sits below Rho as the provider engine, consumed through its stable engine facade
  • Rho's token/context engine is embedded (internal/token), not a peer repo
  • shared vocabulary lives in Rho's vendored internal/contracts
  • SDKs and community skills sit above Rho as consumers of Rho public surfaces
  • graycode-platform stays outside the Rho runtime module graph and exposes the optional web/BFF/Rho Cloud plane