Skip to content

Position the docs around the neutral core, not pi - #88

Merged
rgarcia merged 1 commit into
mainfrom
hypeship/positioning-docs
Aug 15, 2026
Merged

Position the docs around the neutral core, not pi#88
rgarcia merged 1 commit into
mainfrom
hypeship/positioning-docs

Conversation

@rgarcia

@rgarcia rgarcia commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

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.

  • Both README openers now lead with "browser tools for your agent" and introduce pi as one binding, with Eve/AI SDK named as the anticipated next.
  • The extension is framed as the other half of the workflow (harness to experiment, SDK to deploy — same catalog, same identities) instead of "already in pi? install the extension instead."
  • The entry-point tables state the core is neutral and boundary-enforced; "How it works" now leads with the execution layer instead of the pi model layer.
  • package.json descriptions updated in both packages; architecture.md's ./pi bullet notes the future bindings share identities and tool names so transcripts stay comparable.

No code changes. tsc -b clean; 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/loop READMEs lead with the neutral core and stress stable kloop.*.v1 identities across bindings. The pi extension is described as the harness half of the workflow (experiment in pi, deploy the same catalog via attach()), not an alternate install path. Entry-point tables and How it works put execution before the pi model layer; docs/architecture.md notes future bindings share tool names for comparable transcripts.

package.json descriptions at the repo root and @onkernel/loop are 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.

@rgarcia
rgarcia merged commit 398ff39 into main Aug 15, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant