Spherewright

mcp
Guvenlik Denetimi
Uyari
Health Uyari
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

MCP bridge for structured, normal-rules automation of Dyson Sphere Program.

README.md

Spherewright

English · 简体中文

Spherewright connects an external Agent to Dyson Sphere Program through a matching MCP server and BepInEx Plugin. Structured observation, deterministic planning helpers and bounded native actions preserve ordinary materials, research, power, construction drones and game time. The product embeds no LLM or autonomous expansion loop.

Plugin, MCP, Contracts and Bridge.Core form one version-coupled monorepo. Spherewright-Lab owns scenarios, operational handoffs and detailed evidence; product builds, tests and packages do not depend on Lab.

Current status

Item Current state
Latest formal release v0.6.0, published 2026-11-21 from 78274df5e93ca912a2d4b6670f7eb707d3562e94 for DSP 0.10.35.29151 and BepInEx 5.4.17.0
0.6 Ascension In one peaceful 1× save, an Agent completed a shell through normal production and launches. All 150 structure points and 224 cells survived a cold reload, and the same receiver produced power during the sampled daylight intervals. Live acceptance
Voyager baseline All three original clauses are accepted within their recorded source scopes; the same-source review pair is retained in Lab
First-sail/carrier-rocket extension Bounded live acceptance recorded 2026-11-06: local off-world manufacture, four sails launched into the swarm, one carrier rocket arrival with one added Native structure point, auxiliary delivery and normal save/cold continuation
First-sail/rocket implementation source d3b7ac897bb44d62c8a7ed54c51a55ff2b8de7b0; exact-source CI, Native builds, coherent installation and package payload checks passed within the recorded scope
Stacking implementation source 19cd5eb505ffd30f4832f3bfbf0ced9ddad4a889, with9 models/19 directed pairs, warehouse-layer filters and real piler aggregation. Both implementation layouts passed cold continuation with47 members and the complete backpack preserved
0.5 publication GitHub tag and six release assets are published and downloaded-byte-verified. The release source adds eight Markdown files to the live-accepted implementation. Thunderstore publicly lists0.5.0 on2026-11-11

For a direct Windows installation, download the manual ZIP and its checksum. For Thunderstore Mod Manager or r2modman, select Arcueid_77-Spherewright 0.6.0. GitHub downloads · Thunderstore

The release manifest identifies the archived source and the build used for live validation. Product status · Roadmap · Ascension live record

Capabilities and boundaries

  • Overseer: bounded production, power, logistics and research observations, upstream tracing and diagnosis. Recommendations grant no write authority.
  • Foundry: recipe, material, machine, power, site and dependency plans with explicit external supplies. Preview and execution remain separate.
  • Finite native actions: construction, configuration, supported upgrades, procurement and bounded blueprints, with per-object progress, cancellation and fresh continuation.
  • Governor: pre-execution production declarations and game-tick measurements. Inventory, rated capacity and short samples do not prove sustained production.
  • Save continuity: ticket-bound exact-owned-primary resume with durable Journal continuity and separately confirmed disclosed migration. No arbitrary save picker or editor.
  • Voyager and launch expansion: native-visible exploration, finite flight/recovery, local manufacture/work and logistics primitives. The accepted baseline and first-sail/carrier-rocket review retain their recorded scopes and do not establish universal coverage.

Every write requires fresh native prepare, plan-bound commit, original-action/idempotency reconciliation and relevant readback. Unknown outcomes are quarantined. Item/technology injection, instant construction, teleportation and direct game-buffer writes are excluded. Dark Fog/combat, multiplayer/Nebula, broad third-party Mod compatibility and another-computer use remain unvalidated.

Install and learn

  1. Install the matching Plugin and MCP, register the executable, then confirm the connection with the read-only spherewright_get_status call. The installation guide includes a Codex CLI example.
  2. Keep interrupted-installation recovery available before replacing an existing installation.
  3. Follow the Agent playbook; it is also embedded in MCP and included in packages.
  4. Check the protocol, safety model and architecture when integrating or reviewing behavior.

Release evidence is separated by source and purpose. 0.6 release notes, 0.5.1 Wind Recovery, 0.5 release notes, 0.4 release notes, 0.4 validation, 29151 compatibility evidence and the fixed source-specific runtime report. The complete documentation index is in docs/README.md.

Develop

dotnet restore Spherewright.Core.slnf --locked-mode
dotnet build Spherewright.Core.slnf -c Release --no-restore
dotnet test Spherewright.Core.slnf -c Release --no-build
pwsh -File scripts/verify-documentation.ps1

Full Plugin builds require legally installed DSP/BepInEx references; see environment setup. Package scripts record this repository's own source SHA and clean state; they do not fetch or execute Lab.

Start scenario work from Lab and treat its fixed product submodule as read-only. Implement reusable changes in an independent product clone/worktree, test and commit them, and obtain successful exact-SHA CI before Lab updates its gitlink/lock. Read contribution policy, contributor rules and Lab setup.

Licensed under MIT, with a Chinese explanatory translation.

Yorumlar (0)

Sonuc bulunamadi