streamable-httpMITupdated 1mo ago
Status: Experimental. Not production. Not deployed. Exploring whether the five concerns of a pscale node ā storage, BSP function, MCP transport, hermit-crab agent shell, xstream interface ā can be unified into one package that unfolds into whatever host receives it.
What can you do with pscale biome?
pscale-biome
Status: Experimental. Not production. Not deployed. Exploring whether the five concerns of a pscale node ā storage, BSP function, MCP transport, hermit-crab agent shell, xstream interface ā can be unified into one package that unfolds into whatever host receives it.
What this is
A working tree assembled from existing production codebases (bsp-mcp-server, pscale-beach, xstream) plus a design shell (src/sentinel/biome.json). The goal is to discover the minimal package ā the smallest bundle that, when placed on a host, becomes a functioning biome.
The design overview is in docs/biome-design.md. The shell that names the seven environmental currents is at src/sentinel/biome.json.
What's NOT this
- This is not
bsp-mcp-server. That is the production MCP service running on Railway. - This is not
pscale-beach. That is the production beach package on Vercel. - This is not
xstream. That is the production interface at xstream.onen.ai. - Changes here MUST NOT propagate to those repos. This is a separate experimental working tree with its own git history.
Layout
src/
āāā bsp/ ā bsp() function (vendored from bsp-mcp-server)
ā āāā bsp.ts walker (DO NOT modify; port of bsp2-star.py)
ā āāā bsp-fn.ts unified bsp() with shape derivation
ā āāā locks.ts sha256 lock salt namespaces (compatibility with prod)
ā āāā keys.ts Argon2id + nacl
āāā sentinel/ ā Tier 1 sentinel blocks (substrate-truth)
ā āāā sunstone.json geometry teacher
ā āāā whetstone.json bsp() operational reference
ā āāā agent-id.json addressing model
ā āāā evolution.json five-level ecosystem map
ā āāā manifest.json constitution index
ā āāā gatekeeper.json L1āL2 admission shell
ā āāā block-conventions.json canonical block-shape catalogue
ā āāā progression.json orientation flow
ā āāā biome.json ā
the design shell ā seven currents (this project's contribution)
āāā beach/ ā beach handler (vendored from pscale-beach)
ā āāā handler.js /.well-known/pscale-beach handler (~540 lines)
āāā seeds/ ā seed content (vendored from pscale-beach)
ā āāā library/ reference blocks (reflexive, spore, vision, etc.)
ā āāā templates/ operator-presence scaffolds (passport, shell, etc.)
āāā init/ ā seed wizard (vendored from pscale-beach)
ā āāā seed.js populates a fresh biome with operator presence
āāā xstream/ ā xstream interface (vendored from xstream)
āāā kernel/ sovereign browser kernel
āāā components/ vapor/liquid/solid UI + shadcn primitives
āāā engine/ soft / medium / hard LLM engines
āāā lib/ bsp util, claude client, logger, shelf, utils (NO supabase)
āāā blocks/ TypeScript block exports
āāā App.block-agents.tsx the post-Supabase reference app
docs/
āāā biome-design.md ā design overview (David's draft)
āāā minimal-package.md ā open exploration: what's irreducible?
āāā systemic-kernel.json ā the systemic-vs-mechanical evaluation kernel
āāā protocols/ ā protocol specs (from bsp-mcp-server)
āāā protocol-pscale-beach-v2.md
āāā protocol-xstream-frame.md
āāā protocol-agent-shell.md
āāā protocol-block-references.md
āāā presence-via-marks.md
āāā beach-crab-ladder.md
Provenance
Every file is either authored here or vendored from a specific source. Track changes from upstream with care.
| Source | What was vendored | Vendored at |
|---|---|---|
bsp-mcp-server (feat/gatekeeper-sentinel, commit ead1902) |
src/bsp/, src/sentinel/ (8 sentinel JSONs), docs/protocols/ (6 protocols) |
2026-05-09 |
pscale-beach (local) |
src/beach/handler.js, src/seeds/library/, src/seeds/templates/, src/init/seed.js |
2026-05-09 |
xstream (feature/block-agents) |
src/xstream/kernel/, src/xstream/components/, src/xstream/engine/, src/xstream/lib/ (no supabase.ts), src/xstream/blocks/, App.block-agents.tsx |
2026-05-09 |
happyseaurchin (local) |
docs/systemic-kernel.json |
2026-05-09 |
| User draft | docs/biome-design.md |
2026-05-09 |
| This project | src/sentinel/biome.json, README, CLAUDE.md, docs/minimal-package.md |
2026-05-09 |
Mobius / mobius-2 was deliberately NOT vendored ā the user has updates on a separate drive (pct-soliton work) and the canonical version is being tracked down.
The five concerns (per biome-design.md)
| # | Concern | Source code in this tree |
|---|---|---|
| 1 | Storage (beach surface) | src/beach/handler.js |
| 2 | BSP function | src/bsp/ |
| 3 | MCP transport | not yet vendored ā to be authored or ported from bsp-mcp |
| 4 | Hermit-crab shell (autonomous LLM mode) | not yet present ā mobius pattern, awaiting reference |
| 5 | xstream interface (human surface) | src/xstream/ |
Two of the five concerns are missing from the working tree. That's part of what the experiment is for ā figuring out what those become when the biome is the unification rather than the federation.
The open question
What's the minimal package? See docs/minimal-package.md.
License
TBD.
Install
Add pscale biome to your client. Pick the one you use.
claude mcp add --transport http pscale-biome https://biome-commons-production.up.railway.app/mcpcodex mcp add pscale-biome --url https://biome-commons-production.up.railway.app/mcp{
"mcpServers": {
"pscale-biome": {
"url": "https://biome-commons-production.up.railway.app/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"pscale-biome": {
"type": "http",
"url": "https://biome-commons-production.up.railway.app/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"pscale-biome": {
"url": "https://biome-commons-production.up.railway.app/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"pscale-biome": {
"serverUrl": "https://biome-commons-production.up.railway.app/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance16/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 45 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint ā no local install
Version history
| Versions | Published |
|---|---|
| 0.5.0Latest | Jul 3, 2026 |