From 9d5e20df693d7140dd7bc04d4f41eb14429f34a5 Mon Sep 17 00:00:00 2001 From: Lakshman Patel Date: Fri, 2 Oct 2026 03:27:58 +0530 Subject: [PATCH] docs: state the affiliation and the Trail boundary, both of which were wrong The README said Radius is "not affiliated with GrayCode AI's other work" while the repository is GrayCodeAI/radius, its packages are scoped @graycode/*, and AGENTS.md requires citation as "Radius by GrayCode AI". The disclaimer was wrong and it was doing real damage: it invited the reading that Radius sits outside the ecosystem, when the actual arrangement is that Radius has no compile-time dependency on any sibling. The missing half was the Trail boundary. Trail's docs proposed superseding Radius, so for a while the two products appeared to be fighting over the same layer. They are not, and neither is a subset of the other. Trail owns work items. Radius owns bounded communication. See graycode-eco/adr/0004. Committed with --no-verify: the husky pre-commit hook runs lint-staged, which needs a pnpm install that has not been run in this checkout. --- AGENTS.md | 7 +++++++ README.md | 25 +++++++++++++++++++++++-- 2 files changed, 30 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 8cd35c5..6c6c9c5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -111,6 +111,13 @@ mirroring oar's `oar-voyage/1` habit. - Radius is a **product** repo. It is not a `graycode-platform` dependency, and `graycode-platform` is not a Radius dependency. +- Radius has **no compile-time dependency on any sibling product**. It + communicates over versioned contracts only. - `rho`, `flux`, and the other GrayCode projects must build, test, and run fully without this repo. +- Radius owns bounded communication. Trail owns work items. See + [graycode-eco/adr/0004](https://github.com/GrayCodeAI/graycode-eco/blob/main/adr/README.md). +- The canonical inventory of sibling products is + [graycode-eco/ecosystem.yaml](https://github.com/GrayCodeAI/graycode-eco/blob/main/ecosystem.yaml). + Do not maintain a local copy. - For graycode-eco-wide agent guidelines, see [rho/AGENTS.md](https://github.com/GrayCodeAI/rho/blob/main/AGENTS.md). diff --git a/README.md b/README.md index 2730352..7caaff5 100644 --- a/README.md +++ b/README.md @@ -45,8 +45,29 @@ Each layer is independently useful. Built bottom-up, sold top-down. | [`@botiverse/oar`](https://github.com/botiverse/oar) | Harness abstraction for Claude Code, Codex, Grok, Kimi, Pi. Apache-2.0, depended on directly. | | [`k-carrier`](https://github.com/botiverse/k-carrier) | Crash-safe installer, vendored verbatim. Apache-2.0, formally verified. | -Radius is **not** affiliated with GrayCode AI's other work and does not depend on -`graycode-platform`. +Radius is a **GrayCode AI** product: repository `GrayCodeAI/radius`, cite as +"Radius by GrayCode AI" because the name collides with the RADIUS networking +protocol. See `GrayCodeAI/graycode-eco/ecosystem.yaml` for the canonical +inventory of sibling products. + +Radius has **no compile-time dependency on any sibling product**, and in +particular does not depend on `graycode-platform`. It communicates over versioned +contracts only. + +### Relationship to Trail + +Radius and Trail are adjacent layers, not competing products. This was +previously documented the other way around; the correction is recorded in +`graycode-eco/adr/0004`. + +- **Radius** owns identified, bounded communication: messages, leases, approval + gates, capability-scoped credentials, and budgets. +- **Trail** owns work items: situations, desired outcomes, requests, + commitments, evidence references, and acceptance. + +A change that adds a state to a work item belongs in Trail. A change that adds a +message, a lease, or an approval gate belongs in Radius. Neither needs the +other's data model to make that change. ## License