Position the docs around the neutral core, not pi - #88
Merged
Conversation
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
The repo and package READMEs framed the library as pi-scoped — "built on pi" in the repo front door, "computer-use for pi" in the line npm renders — inverting the actual architecture: a framework-neutral core (boundary-enforced since #86) with pi as the first binding. This is a prose-only pass realigning the user-facing docs with that positioning.
./pibullet notes the future bindings share identities and tool names so transcripts stay comparable.No code changes.
tsc -bclean; 34 files / 428 tests pass.Note
Low Risk
Documentation and metadata only; no code, APIs, or behavior changes.
Overview
User-facing docs now describe Loop as browser tools for any agent, with pi as the first binding (Eve and AI SDK named as next), instead of framing the repo as pi-first (“built on pi”, “computer-use for pi”).
The root and
packages/loopREADMEs lead with the neutral core and stress stablekloop.*.v1identities across bindings. The pi extension is described as the harness half of the workflow (experiment in pi, deploy the same catalog viaattach()), not an alternate install path. Entry-point tables and How it works put execution before the pi model layer;docs/architecture.mdnotes future bindings share tool names for comparable transcripts.package.jsondescriptions at the repo root and@onkernel/loopare updated to match. No runtime or API changes.Reviewed by Cursor Bugbot for commit 3fe0544. Bugbot is set up for automated code reviews on this repo. Configure here.