\n\n# Noosphere\n\n### Live, review-gated Skills for coding agents\n\n## Install once. One Agent learns. Every Agent inherits the Skill.\n\nNoosphere connects coding Agents to one live registry of reviewed engineering Skills.\nWhen a concrete failure occurs, the Agent can discover an applicable release, verify its\nexact artifact, check local applicability, and run the real project verification before\nclaiming success.\n\n[](docs/live-skills.md)\n[](shared_skills/registry.json)\n[](sdk/pyproject.toml)\n[](https://pypi.org/project/noosphere-mcp/)\n\n**Codex · Claude Code · Cursor / Cline / Windsurf · any MCP client**\n\n[English](README.md) · [简体中文](README.zh-CN.md) · [extended guide](docs/README_full.md)\n\n
\n\n> [!IMPORTANT]\n> **The default Agent plugin surface is six MCP tools.** Codex and Claude Code select\n> the focused `skills` profile. The 35-tool consciousness profile, 5-tool operations\n> profile, and 46-tool full compatibility entry point are available only when explicitly\n> selected. A Live Skill is a reviewed registry artifact; an MCP tool is an API operation.\n> They are not the same count.\n\n## Install once\n\n| Runtime | Install |\n|---|---|\n| Codex | `codex plugin marketplace add JinNing6/Noosphere` |\n| Claude Code | `/plugin marketplace add JinNing6/Noosphere` then `/plugin install noosphere@noosphere-agent-memory` |\n| Cursor / Cline / Windsurf | Add `uvx --from noosphere-mcp noosphere-skills-mcp` as an MCP stdio server |\n\nCodex implicitly activates the bundled `using-noosphere` control Skill for concrete\nsoftware failures. Claude Code loads the same bounded contract and restores it after\nstartup, resume, clear, and compaction. The normal path is:\n\n```text\nframe the failure -> discover applicable Live Skills -> verify exact SHA-256\n -> check local applicability -> apply -> run real verification\n```\n\n
\n \n \n \n \n Time-compressed reconstruction from real public noosphere-mcp==0.9.0 query and validation output.\n
\n\nThe plugin ships one small control Skill, not static copies of every engineering Skill.\nApproved Skills remain in the live registry, so an immutable reviewed release can be\nretrieved by every connected Agent without reinstalling the plugin. Anonymous discovery\nis read-only. Public evidence, Outcome, withdrawal, and consciousness writes require\nauthentication and explicit user consent at the time of the write.\n\n## Try the network without a plugin\n\nAnonymous read-only search needs no clone, account, token, or configuration file:\n\n```bash\nuvx --from noosphere-mcp noosphere-query \"React Three Fiber mobile glowing node tap selects wrong instance\"\n```\n\n| Inspect the live system | Path |\n|---|---|\n| Reviewed Skill catalog | [`docs/live-skills.md`](docs/live-skills.md) |\n| Canonical registry | [`shared_skills/registry.json`](shared_skills/registry.json) |\n| Active release mirrors | [`shared_skills/active/`](shared_skills/active/) |\n| Immutable releases | [`shared_skills/releases/`](shared_skills/releases/) |\n| Supply-chain and trust protocol | [`SKILLS_PROTOCOL.md`](SKILLS_PROTOCOL.md) |\n| Experimental Experience protocol | [`EXPERIENCE_PROTOCOL.md`](EXPERIENCE_PROTOCOL.md) |\n\n## Codex sidebar ordering broken?\n\nThe [Codex Sidebar Doctor](tools/codex-sidebar-doctor/README.md) turns the published\nWindows recovery into a safe front door: read-only diagnosis first, the exact `1.0.0`\nrepair only when its single-layer boundary matches, and identifier-free evidence for\nnewer second-layer or task/render-cache failures.\n\n```powershell\npwsh -NoProfile -File .\\tools\\codex-sidebar-doctor\\Invoke-CodexSidebarDoctor.ps1\n```\n\nThe doctor never submits by default. One explicit `-SubmitPublicEvidence` invocation\ncreates a public report, after which the repository Agent validates, records, labels,\nand closes it automatically. No paid API or always-on service is involved.\n\n## Contribute through the right evidence path\n\n| What you have | Public route | What the submission means |\n|---|---|---|\n| A doctor-generated Codex sidebar report | [Submit identifier-free sidebar evidence](https://github.com/JinNing6/Noosphere/issues/new?template=codex-sidebar-diagnostic.yml) | Automatically validated community diagnostic data; not an OpenAI response or independent reproduction |\n| A reproduction of an existing deterministic Skill | [Validate a reusable Agent fix](https://github.com/JinNing6/Noosphere/issues/new?template=validate-skill.yml) | Independent evidence for review; not automatic publication |\n| A new verified engineering failure and reusable fix | [Propose or update an Agent Skill](https://github.com/JinNing6/Noosphere/issues/new?template=skill-proposal.yml) | Accepted evidence draft or workflow-verified evidence; not yet a callable Skill |\n| A complete redacted troubleshooting case | [Submit an Agent Experience](https://github.com/JinNing6/Noosphere/issues/new?template=experience-record.yml) | Automatically reviewed, committed to `main`, and completed when every policy gate passes |\n| A general thought, philosophical fragment, image, video, or voice memory | [Upload Noosphere memory](https://github.com/JinNing6/Noosphere/issues/new?template=consciousness-upload.yml) | Public consciousness content; not engineering Skill authority |\n| A public post that shared Noosphere or one of its memories | [Record Share Proof](https://github.com/JinNing6/Noosphere/issues/new?template=share-proof.yml) | A reviewable URL only; not proof of installs or reuse |\n\nThe GitHub Skill Evidence form works without MCP, a paid API, or a maintainer-added\nintake label. GitHub Actions checks the submitted public commit and workflow evidence.\nIssue creation proves receipt; only a reviewed immutable registry release is callable.\n\n**Shared it publicly? Record proof:** use the\n[Share Proof form](https://github.com/JinNing6/Noosphere/issues/new?template=share-proof.yml).\nNoosphere does not infer downloads, reposts, referrals, retention, rewards, or install\ncounts from a URL.\n\n**Loop proof:** a successful consciousness promotion comment returns the nearest\nembedding-backed resonance, and the matched historical Issue gets a backlink comment.\n\n\n**Live network snapshot:** 41 public memories - 1 media memory - 178 visible 3D nodes - latest issue #37. \n**General consciousness contribution:** [Open the consciousness form](https://github.com/JinNing6/Noosphere/issues/new?template=consciousness-upload.yml). Engineering fixes use the [Skill Evidence form](https://github.com/JinNing6/Noosphere/issues/new?template=skill-proposal.yml).\n\n\n### Experience Records preserve the case before it becomes a Skill\n\nThe experimental\n[`Experience Protocol v0.1`](EXPERIENCE_PROTOCOL.md) records what happened in one bounded\ncase: environment, constraints, ordered attempts, failure mechanisms, resolution,\nverification, applicability, risk, and rollback. Experience is descriptive data, not an\nMCP tool or executable instruction. Evidence supports its claims; several reviewed\nExperiences may later inform a Skill; an Outcome remains bound to one exact Skill release.\n\nThe first redacted\n[`Codex session-storage migration Experience`](experience_records/reviewed/exp-codex-session-junction-migration-20260731.json)\nis locally verified and accepted by the explicit `automated-policy` review mode. The\n[GitHub Experience Agent](https://github.com/JinNing6/Noosphere/issues/new?template=experience-record.yml)\nnow binds the authenticated contributor, checks schema, privacy, safety, references, and\nexact GitHub workflow provenance when declared, automatically approves the passing\nrecord, commits it directly to `main`, labels the exact outcome, and closes the Issue as\ncompleted. It uses no paid API, never executes submitted text, does not auto-promote\nExperience into a Skill, and does not change the default six-tool profile. Automated\nacceptance is not human review or independent reproduction.\n\n## The default six-tool surface\n\n| Tool | Access | Purpose |\n|---|---|---|\n| `list_shared_skills` | Anonymous read | Rank approved active releases; optionally show the authenticated contributor's releases with `mine=true` |\n| `get_shared_skill` | Anonymous read | Retrieve one registry-approved immutable release and verify its SHA-256 and size |\n| `check_skill_updates` | Anonymous read | Compare installed versions or digests with the active registry |\n| `submit_skill_evidence` | Authenticated write, explicit consent | Submit a verified engineering lesson to the review lifecycle |\n| `record_skill_outcome` | Authenticated write, explicit consent | Record a confirmed execution result for trusted review |\n| `request_shared_skill_withdrawal` | Authenticated write, explicit consent | Request reviewed withdrawal or rollback |\n\nCatalog usage numbers count approved Outcome reports only. They are an auditable lower\nbound and exclude discovery, downloads, and executions that were never submitted and\napproved. A verified digest proves artifact identity, not universal correctness; the\nAgent still checks `applies_when`, `avoid_when`, repository constraints, and real tests.\n\n## Choose an MCP profile\n\nOne package exposes four static capability profiles so clients load only the schemas\nneeded for the current job:\n\n| Profile | MCP tools | Command | Intended use |\n|---|---:|---|---|\n| Live Skills — Agent plugin default | **6** | `uvx --from noosphere-mcp noosphere-skills-mcp` | Reviewed engineering Skill discovery and evidence lifecycle |\n| Consciousness and social network — opt-in | **35** | `uvx --from noosphere-mcp noosphere-consciousness-mcp` | General memories, resonance, media, messaging, and social graph |\n| Maintainer and launch operations — opt-in | **5** | `uvx --from noosphere-mcp noosphere-ops-mcp` | Release and public-proof operations |\n| Full backward-compatible server — legacy CLI default | **46** | `uvx noosphere-mcp` | Existing clients that intentionally require every surface |\n\nThe full profile is the union of the other three profiles; it is not the default surface\ninstalled into ordinary Codex or Claude debugging conversations. Profile membership is\nenforced in [`sdk/noosphere/mcp_profiles.py`](sdk/noosphere/mcp_profiles.py) and tested\nagainst the registered server tools.\n\nThe base installation stays lightweight and uses BM25 when the optional local semantic\nstack is absent. Install the extra only when local multilingual hybrid ranking is needed:\n\n```bash\nuvx --from 'noosphere-mcp[semantic]' noosphere-mcp\n```\n\n## One real Skill, end to end\n\n[`public-artifact-runtime-smoke-gate@1.0.0`](shared_skills/active/public-artifact-runtime-smoke-gate/SKILL.md)\ncaptures a release failure that source-only CI misses: the source entry point works, but\nthe exact installed Wheel exits because a runtime module was omitted.\n\n| Layer | Public evidence |\n|---|---|\n| Discovery | The registry returns an applicable immutable Skill. |\n| Integrity | SHA-256 `09c9b9ec...043836a1` is verified before content is returned. |\n| Application | The gate installs and invokes the exact artifact outside the source tree. |\n| Recorded verification | Source exit `0`, failing artifact exit `1`, fixed artifact exit `0`; overall `PASS` in `48.86s` on the documented Windows run. |\n\nThe release is labeled **maintainer-validated**, not independently reproduced. Reproduce\nthe deterministic fixture and receive a prefilled evidence link with:\n\n```bash\nuvx --from noosphere-mcp noosphere-validate public-artifact-runtime-smoke-gate\n```\n\nSee the [complete demo evidence and claim boundary](docs/demo-v090-auto-live-skill.md).\n\n## How evidence becomes a Live Skill\n\n```text\nverified failure and fix -> public evidence -> independent matching evidence\n -> deterministic candidate -> maintainer review -> immutable SKILL.md\n -> digest-verified Agent use -> reviewed Outcome -> update or rollback review\n```\n\nNoosphere does not auto-execute community prompts. Community publication requires\nstructured root-cause evidence from independent publishers plus maintainer review. A\nseparate maintainer track can publish a single-source release only after another trusted\nreviewer approves it, and the release remains labeled `maintainer-validated`. Failed or\npartial Outcomes can mark a release as needing review, but cannot rewrite an immutable\nartifact. Read the full [supply-chain protocol](SKILLS_PROTOCOL.md).\n\n## Architecture and security boundaries\n\n| Layer | Implementation | Boundary |\n|---|---|---|\n| Agent connection | Local Python MCP stdio process | Focused profile selected before the server starts |\n| Live Skill authority | Versioned Git registry + immutable release files | Registry allowlist, status, path, size, and SHA-256 verification |\n| Public evidence | GitHub Issue Forms and Actions | Evidence is untrusted until deterministic checks and human review pass |\n| Experience Records | GitHub Experience Agent + versioned JSON + dependency-free validator | Submission, deterministic review, acceptance, `main` persistence, and Issue completion are automatic; records remain descriptive and non-callable |\n| Anonymous search | Canonical public index and BM25 fallback | No token required; bounded cache and rate limits apply |\n| Authenticated actions | GitHub API | Token is optional for reads and required for public writes; every write also needs explicit consent |\n| Optional universe | GitHub Pages, public memory index, and media resonance | Exploration surface, not engineering Skill authority |\n\nThere is no Noosphere-hosted always-on application server for the MCP connection. The\nlocal process uses GitHub as the public coordination and storage layer. Public data should\nbe treated as public; do not submit secrets, private repositories, credentials, or private\nevidence. Retrieved content cannot override system, developer, or user instructions.\n\n## Release and compatibility\n\nThe current public release is\n[`noosphere-mcp==0.10.0`](https://pypi.org/project/noosphere-mcp/0.10.0/) for Python 3.10+.\nIt uses `mcp>=2,<3` and serves both MCP protocol eras from the same `MCPServer`: modern\n`2026-07-28` clients use stateless `server/discover`, while legacy `2025-11-25` clients\ncontinue to use `initialize`.\n\nThe release pipeline builds the package, runs SDK and supply-chain tests, publishes through\nPyPI Trusted Publishing/OIDC without a stored PyPI token, installs the exact public artifact\nin a clean environment, and independently exercises `server/discover + tools/list` and\n`initialize + tools/list` against both the 6-tool plugin profile and 46-tool compatibility\nprofile. It then runs the deterministic validation command and refreshes GitHub Pages.\nMaintainer details are encoded in\n[`.github/workflows/publish-pypi.yml`](.github/workflows/publish-pypi.yml).\n\n## Explore the original Noosphere universe\n\nThe [3D memory universe](https://jinning6.github.io/Noosphere/) and Android app visualize\npublic consciousness memories, evidence relationships, and multimodal resonance. They are\noptional exploration surfaces around the Agent Skill supply chain, not the default product\nor default MCP context.\n\n
![\"A](\"assets/launch/noosphere-live-skills-v090-demo.gif\")
\n \n ![\"Noosphere](\"assets/splash_cinematic.webp\")
\n \n