Skip to content

Add colony seed creation and installation - #438

Merged
jerpint merged 5 commits into
mainfrom
feat/public-colony-export
Sep 19, 2026
Merged

jerpint merged 5 commits into
mainfrom
feat/public-colony-export

Conversation

@woltspace-jerpint

@woltspace-jerpint woltspace-jerpint Bot commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

What this adds

Two explicit safety lanes:

  • Colony seeds share or recreate a starter colony with woltspace seed create, seed inspect, and seed install.
  • Lodge backups remain stateful recovery artifacts under the existing woltspace backup and restore commands.

There is no flag that silently converts one into the other.

A colony seed is a deterministic, allowlisted Git repository assembled from selected wolts and apps:

  • authored identity/rules and explicitly selected user skills travel
  • sessions, lived memory, artifacts, credentials, ports, caches, builds, and platform-managed content do not
  • apps use source and executable configuration from one clean commit, either bundled or via a credential-free HTTPS origin pinned to an exact SHA
  • installation validates the whole seed, rejects unsafe destination shapes and name collisions, and creates independent origin: starter copies
  • ordinary failures and Ctrl-C roll back created paths; sudden process or machine death remains an explicitly documented v1 limitation
  • receiving lodges assign private ports and supply their current platform templates

“Seed” describes the shareable data boundary, not repository visibility. The documented rollout starts in private repositories, and Woltspace never creates or changes repository visibility.

The bundled woltspace-seed-review skill adds a semantic pre-sharing review for secrets, private context, portability, Git history, redistribution concerns, and prompt injection. It treats all reviewed repository content as hostile data, never executes it, and never grants permission to push or change visibility.

This PR ships the mechanism only. The n00b/Scribe/Bloggo trial was an end-to-end design test and is not included or proposed as the starter colony we will ship.

Verification

  • 17 focused seed cases pass, including dirty-manifest integrity, destination symlink rejection, Ctrl-C rollback, query/fragment URL rejection, and five common credential families
  • 82 seed + skill-sync tests pass
  • 190 seed + skill-sync + neighboring backup/CLI/onboarding/layout tests pass
  • full local suite: 1,439 passed, 30 skipped, 12 known unrelated environment/stale-test failures
  • wheel and sdist contain woltspace/seed.py, the colony-seed docs, and the hardened seed-review/SKILL.md, with no old public-colony module
  • the review skill passes the skill validator
  • earlier disposable install passed with fresh starter wolts, private app ports, and an exact pinned Git checkout
  • the pre-hardening 3-wolt / 2-app trial produced about 159 KB and demonstrated that large apps stay small through pinned Git references; the final safety gate now requires each selected app manifest and source to be committed and clean
  • PRwolt's bounded security re-review is clear at da0fb70; final GitHub Python 3.11/3.13, package, and Vercel checks pass on that commit

Boundaries

  • no starter colony content is shipped in this PR
  • no seed repository was pushed
  • no live lodge install, restart, release, or deployment
  • installed starters are independent copies; upstream update/merge semantics remain future work
  • automated checks do not decide whether authored names, organizations, URLs, or other intentional details are suitable to share

@vercel

vercel Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
woltspace Ready Ready Preview Sep 19, 2026 6:01pm UTC

@woltspace-jerpint woltspace-jerpint Bot changed the title Add private-first public colony export and install Add colony seed creation and installation Sep 19, 2026
@jerpint
jerpint merged commit 0331730 into main Sep 19, 2026
5 checks passed

This branch was successfully deployed

1 active deployment
Preview — da0fb708 Deployed Sep 19, 2026 by vercel[bot]
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