docs: clarify Coven as a substrate for harnesses, not a harness itself#17
Merged
Conversation
- getting-started: replace 'local-first runtime for harnesses' with substrate framing; add benefits (provider independence, enforced boundaries, auditable history, unified client surface) - concepts: expand Coven definition to explicitly state it is not a harness and explain what the substrate provides - what-is-a-harness: add prominent 'Coven is not a harness' note at top of the page; add read_when entry for the substrate distinction Co-authored-by: Nova <nova@opencoven.dev>
Indent envelope() responses with two spaces and a trailing newline so the proxy's error payloads are human-readable in browsers and terminals. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
substrate framing; add benefits (provider independence, enforced
boundaries, auditable history, unified client surface)
harness and explain what the substrate provides
top of the page; add read_when entry for the substrate distinction
Co-authored-by: Nova nova@opencoven.dev