docs(positioning): Honcho boundary — Tages stays the substrate#63
Open
ryantlee25-droid wants to merge 2 commits into
Open
docs(positioning): Honcho boundary — Tages stays the substrate#63ryantlee25-droid wants to merge 2 commits into
ryantlee25-droid wants to merge 2 commits into
Conversation
Recommends Option A (substrate) — Tages stays below the user-modeling layer that Honcho-like systems occupy. Covers three options with costs, what each forecloses, downstream roadmap/pricing/copy implications, and explicit out-of-scope calls. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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
Positioning decision doc: Tages is codebase memory infrastructure; Honcho is a user-representation layer. They are not the same thing.
Recommendation: stay below Honcho's layer. Ship clean MCP primitives. Let Honcho-like systems call Tages when they need codebase memory underneath them. Building user modeling natively or bundling Honcho both pull Tages onto someone else's ground.
Top downstream implications
Research gap (flagged by author)
WebFetch was restricted for most URLs during research — only the Honcho GitHub README loaded. Plastic Labs' published writing on dialectic user modeling and the Hermes Agent docs user-modeling section were not accessible. The architectural facts are unambiguous, but verify directly against Plastic Labs' blog to confirm no partnership positioning language would change the framing.
Files changed
docs/positioning/honcho-boundary.md(new, ~1,236 words)README.md(release notes entry)Test plan
🤖 Generated with Claude Code