​
Release goal

Ship Weave as production infrastructure for peer-to-peer applications where agents and humans can discover each other, exchange signed events, share files, replicate data, and build decentralized applications without a blockchain.

​
Required release gates

GateRequirement
Repository ownershipEvery release target has an explicit GitHub repository, default branch, branch protection decision, and backup point.
Buildcargo check --workspace or scoped package checks pass for the release set.
TestsUnit, integration, and transport tests pass. Network tests that require local sockets must run outside restricted sandboxes.
WOVEN transportAt least two real peers exchange signed WOVEN events over weave-swarm, persist them to Trace, and reject tampering/duplicates.
dSocial proofProfile, post, reply, follow, reaction, and feed workflows work across peers.
Locus proofA shared drive can be created, announced, discovered, replicated, and read by another peer.
DHT proofPeer discovery and provider records survive restart and operate with production configuration.
DocsMintlify docs include architecture, library catalog, operations, release process, and application protocol references.
DeploymentProduction infrastructure changes are rolled out with explicit target hosts, health checks, rollback path, and no unrelated infra churn.

​
Fresh GitHub release flow

Use this flow only after the repository inventory is confirmed: 
git init
git add .
git commit -m "Initial production release"
git branch -M main
git remote add origin git@github.com:l1feai/<repo>.git
git push --force-with-lease origin main
Before running this against any existing GitHub repository, create a mirror backup: 
git clone --mirror git@github.com:l1feai/<repo>.git /tmp/<repo>.backup.git

​
Current blockers

  • The local weave/ tree does not contain active nested Git repositories.
  • weave/ is ignored by the parent sigil repository, so changes here are not tracked by that parent repo.
  • A sandboxed loopback swarm test was previously marked ignored because local DHT-backed socket permissions were unavailable in the sandbox.
  • Workspace-wide formatting has unrelated pre-existing drift outside the recently touched WOVEN and CLI packages.

​
Immediate next steps

  1. Decide which candidate directories become standalone GitHub repositories.
  2. Initialize or reconnect those repositories locally.
  3. Add per-repository release READMEs and CI.
  4. Run real peer-to-peer WOVEN, dSocial, Locus, and DHT tests outside the sandbox.
  5. Only then perform --force-with-lease pushes for approved repositories.