Skip to content

docs: state the affiliation and the Trail boundary, both of which were wrong #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Patel230 merged 1 commit into from
Oct 4, 2026
Merged

docs: state the affiliation and the Trail boundary, both of which were wrong #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
25 changes: 23 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading