docs: align runtime vocabulary#19
Open
BunsDev wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Aligns documentation vocabulary so autonomous coding tools are described as “runtimes,” and updates a few index/concepts pages to better match the chamber/runtime framing while keeping existing harness/harness-adapter docs intact.
Changes:
- Updates the Roadmap “North Star” sentence to use “autonomous coding runtimes” instead of “harnesses”.
- Adjusts Memory + Models boundary wording (runtime/chamber boundary phrasing).
- Refines Familiars index copy to emphasize runtime primitives and harness adapters.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| content/docs/reference/roadmap.mdx | Rewords “North Star” sentence to say autonomous coding tools are “runtimes”. |
| content/docs/memory-models/index.mdx | Updates the boundary sentence describing what Coven records vs what clients/harnesses own. |
| content/docs/guide/concepts.mdx | Tweaks OpenCoven definition sentence to incorporate chamber/runtime vocabulary. |
| content/docs/familiars/index.mdx | Updates Familiars index description/body to reference runtime primitives and harness adapters. |
| ## OpenCoven | ||
|
|
||
| OpenCoven is the ecosystem and organization around the runtime, cockpit, and integrations. | ||
| OpenCoven is the ecosystem and organization around the runtime chamber, cockpit, and integrations. |
| import { Mermaid } from '@/components/mermaid'; | ||
|
|
||
| Memory is what turns a one-off harness session into a persistent familiar. Models are the provider side of that familiar's reasoning, but Coven does not become a model gateway. The durable runtime boundary is: Coven records sessions and events; clients/familiars derive memory from those events; harnesses own provider auth and model access. | ||
| Memory is what turns a one-off harness session into a persistent familiar. Models are the provider side of that familiar's reasoning, but Coven does not become a model gateway. The durable chamber boundary is: Coven records sessions and events; clients/familiars derive memory from those events; harnesses own provider auth and model access. |
| --- | ||
| title: Familiars | ||
| description: Project- and session-scoped runtimes — sessions, harnesses, clients, and the cast agent. | ||
| description: Project- and session-scoped runtime primitives — sessions, harness adapters, clients, and the cast agent. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
pnpm run buildNotes
This intentionally leaves the established
harnesses/docs and harness-adapter terminology alone.