Plan ID: wip-oss-public-beta
Status: Accepted
Target: v0.2.0-beta.1
Owner: Repository owner
Last review: 2026-08-18
Approval: owner-session-2026-08-16
Local preparation: Extended safety pass complete on 2026-08-18
Public source: Confirmed on 2026-08-18. No tag or GitHub release exists.
The owner approved a capture-only public beta with these boundaries:
- Keep the repository name
wip-commit. - Keep the module path
github.com/nstranquist/wip-commit. - Publish the
wipcommand and a portable agent skill from this repository. - Support shared checkouts and linked worktrees through the same capture transaction.
- Keep branch landing, merging, pushing, and remote coordination out of scope.
- Use
v0.2.0-beta.1only after all public-beta gates pass.
The public source repository now exists at
nstranquist/wip-commit.
Commit 206fa8b6a1dde1d97081133e4d447c0881849922 passed the hosted candidate and
final main checks.
The active main ruleset and security settings passed the hosted setup audit.
PUBLICATION-EVIDENCE.md contains the public record.
No beta tag or GitHub release exists. The independent beta, conduct, security-notification, tag-approval, and tagged-install gates remain.
This approval fixes the repository name, module path, and capture-only scope. It does not approve a release tag. The owner separately completed the first source publication through the first-push handoff on 2026-08-17. The historical authority boundary remains in PUBLICATION-HANDOFF.md. Do not run it again.
The owning integration KEP controls the internal workflow. This plan controls the standalone repository and its public release.
The detailed state is in OSS-PUBLIC-BETA.requirements.yaml. The file uses the JSON subset of YAML. The root Go test enforces its structure without adding a YAML dependency.
Use these status values:
verified: Recorded local or hosted evidence passed on the exact source.prepared: The repository artifact exists, but hosted evidence is absent.planned: Owner-controlled implementation work remains.human-gated: An owner decision or external mutation is required.external-evidence: A hosted system or independent person must supply proof.deferred: The item is outside the public-beta gate.
Do not convert a human gate or external-evidence gate into a failed implementation claim.
The owner-controlled repository work is complete. The checkout now contains:
- a single-domain interlock that prevents standalone and legacy coordination
state from starting in the same Git common directory. Only
wip initcan claim an uninitialized repository. - a resumable
wip inittransaction with safe binary and embedded-skill installation, complete no-overwrite first writes, and immutable recovery values. - no-clobber lease creation, a capture heartbeat, a final exact-set publication fence, and refusal of partially released lanes.
- one bound version 3 draft/reviewed plan schema with private-source bindings and fail-closed stale-plan checks.
- operational status with staged-state classes and ordinary-use lease renewal.
- named message policy outside the capture kernel.
- a typed version 2 cumulative capture-only handoff and guided
wip capturecommand. - bounded
wip doctorinspection, structural capture-receipt validation, and exact recoverable state archival. - receipt-bound archive records and recovery of a deterministic empty batch when interruption occurs before receipt publication.
- filesystem-root confinement for persistent state and private-index directories.
- a portable public skill with a regression test for private dependencies and unsafe commands.
- a deterministic six-target builder with archive, checksum, receipt, and host-binary tests.
- a tag-only prerelease workflow with immutable action references and GitHub artifact attestation.
- an explicit state compatibility policy and typed fail-closed errors for unsupported state.
- failure-boundary tests for state-directory, lane, lease, intent, and profile versions.
- an exact minimum Go 1.25.12 gate that excludes reachable standard-library vulnerabilities found in Go 1.25.0.
- a source-bound, fail-closed hosted-correction command, schema, negative test matrix, and finalized private receipt for the first corrected candidate.
Two clean six-target rehearsals produced equal directory trees. Every recorded archive checksum passed, and the native archive reported the target version. The public base includes hosted CI evidence and active controls. This local feature candidate lacks hosted evidence. It does not satisfy attestation, independent testing, tagged installation, or release gates.
The public beta captures exact staged-index or worktree-snapshot sources into agent-owned local refs. It does not land those refs onto a shared branch.
wip init is the onboarding entry point. It recommends one linked worktree per
task. Shared mode remains available for lanes that require one checkout.
The wizard can install the current binary only after explicit consent. It does not overwrite different bytes.
Both modes use path leases, private sources, private indexes, bounded hooks, durable intents, and an exact ref compare-and-swap. Worktree mode adds worktree ownership. It does not use a different publication algorithm.
The portable agent skill must use only public wip commands and standard Git
inspection. It must not require private helpers, private paths, or an internal
catalog command. The integrated skill can add private policy around the public
command.
The public beta must retain these properties:
- A successful capture leaves the source
HEADunchanged. - A successful capture leaves the complete caller index unchanged.
- An unselected source path cannot enter an agent commit.
- A failed group, hook, gate, or ref race publishes none of a split chain.
- Reconciliation accepts only the original immutable plan evidence.
- Two disjoint shared lanes can capture at the same time.
- A linked-worktree capture leaves both checkout heads and indexes unchanged.
- Release and abort preserve the local agent ref.
- No command lands, merges, pushes, stashes, resets, or cleans work.
- Public and legacy coordination domains cannot start beside each other.
- A long capture keeps the exact active lane lease set captured at its start alive and checks that same set again before publication.
- After an empty coordination-store bootstrap, initialization records every durable step and exact retry value before it changes worktree, lane, lease, profile, binary, or skill resources.
- State inspection is read-only and bounded.
- Archive apply rechecks every reviewed candidate under lock and preserves all lane refs and commits.
- A prepared archive can resume or restore by immutable receipt ID.
- Only
wip initand an exact reviewed migration apply can claim an uninitialized repository. - New lease publication cannot replace an existing lease record. A partial release blocks claim, renewal, and capture until release resumes.
- Every durable record writer rejects bytes that its corresponding reader cannot read. Capture intent rejection occurs before the lane ref update.
- An exact initialization retry repairs an exact active lease that lacks its lane back-reference. Git inspection errors cannot appear as a passed check.
- A heartbeat failure after ref publication returns the applied plan evidence and requires receipt-based reconciliation.
- Invalid legacy actions, legacy dry-runs, queue previews, archive resume, and archive restore cannot claim an uninitialized coordination domain.
- Renewal and release audit the complete lease registry before mutation. Release also verifies ownership and reverse references.
- Portable path keys are idempotent for valid UTF-8 paths. Overlap stays symmetric across Unicode case pairs and component boundaries.
- Inherited Git variables cannot redirect repository discovery, refs, object storage, or prepared hooks away from the selected canonical checkout.
- Operational lane and lease reads use the record-replacement registry fence, including the final durable commit receipt.
wip plan --observechanges no repository bytes and writes no plan file.- A handoff binds the complete base-to-tip capture chain. It never authorizes landing.
- Coordination migration uses one writer fence and never dual-writes both state roots.
- The migration manifest binds the regular lease-registry lock. Apply publishes that lock and the review-plan and handoff directories before it publishes imported lane and lease records.
The threat model remains part of the release contract. Cooperating processes
must honor leases. Hooks and verify commands remain trusted repository code.
The owner approved the repository name, module path, capture-only boundary, and standalone skill ownership boundary on 2026-08-16. The requirement tracker records the same approval reference.
- Add the portable agent skill and its public-only regression tests.
- Remove internal-only instructions from public contributor surfaces.
- Add a single-domain compatibility contract for legacy integrations.
- Add resumable initialization and embedded portable-skill installation.
- Add automatic capture lease renewal and final lease fencing.
- Add bounded state diagnosis and exact recoverable archival.
- Add deterministic archives, checksums, and a provenance workflow.
- Add a state-schema compatibility and migration policy.
- Add governance and support policies that state the current single-maintainer model and do not imply a service level or contributor community.
- Record the capture-only beta boundary and future landing requirements in KEP-0001.
- Add the redacted independent beta exercise, its receipt schema, and the human-gated hosted setup runbook.
- Run the complete local gate with
GOWORK=off. - Scan the complete history and worktree for secrets.
The first source publication ran on 2026-08-17. Do not repeat its bootstrap steps. See PUBLICATION-HANDOFF.md for the historical boundary and HOSTED-STATUS-2026-08-18.md for the live check.
Every new candidate must use the active protected pull-request path. Use the required check names from the live ruleset.
- Open a reviewed candidate pull request without merging it.
- Run Linux, macOS, Windows, race, lint, and dependency-review jobs.
- Close the verification pull request without merging it.
- Use a separately authorized, policy-compliant update for public
main. - Verify the final public commit, tree, and hosted checks.
- Verify the maintainer's personal security-alert notifications.
- Approve a Code of Conduct, assign enforcement responsibility, and configure a confidential conduct-reporting path before soliciting contributions.
Hosted Windows execution is mandatory. A Windows cross-build does not exercise Windows locks, process cleanup, or atomic replacement.
- Ask a non-author to follow BETA-EXERCISE.md.
- Require all six scenarios, including shared and worktree split capture, failure isolation, duplicate refusal, and reconciliation.
- Validate the redacted receipt against BETA-EXERCISE.schema.json. Do not accept repository paths, branch names, commit messages, file names, or contents.
- Fix every data-loss or foreign-content defect before release.
- Repeat the hosted matrix after each release change.
- Create an approved, signed
v0.2.0-beta.1tag. - Build release archives from that exact tag.
- Publish checksums and provenance attestations with the archives.
- Test one archive on each operating system.
- Run the public
go installcommand from a clean environment. - Request the module through the public Go proxy.
- Change catalog and portfolio state only after public verification passes.
Never move or replace a published Go module tag. If a released version is defective, publish a new beta tag.
Run this gate from the standalone repository. Keep GOTOOLCHAIN equal to the
exact minimum in go.mod:
GOTOOLCHAIN=go1.25.12 GOWORK=off go mod tidy -diff
GOTOOLCHAIN=go1.25.12 GOWORK=off go mod verify
GOTOOLCHAIN=go1.25.12 GOWORK=off go test -count=1 ./...
GOTOOLCHAIN=go1.25.12 GOWORK=off go test -race -count=3 ./...
GOTOOLCHAIN=go1.25.12 GOWORK=off go vet ./...
golangci-lint run ./...
GOTOOLCHAIN=go1.25.12 GOWORK=off go run golang.org/x/vuln/cmd/govulncheck@v1.7.0 ./...
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 GOTOOLCHAIN=go1.25.12 GOWORK=off go test -exec=/usr/bin/true ./...
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 GOTOOLCHAIN=go1.25.12 GOWORK=off go test -exec=/usr/bin/true ./...
CGO_ENABLED=0 GOOS=darwin GOARCH=amd64 GOTOOLCHAIN=go1.25.12 GOWORK=off go test -exec=/usr/bin/true ./...
CGO_ENABLED=0 GOOS=darwin GOARCH=arm64 GOTOOLCHAIN=go1.25.12 GOWORK=off go test -exec=/usr/bin/true ./...
CGO_ENABLED=0 GOOS=windows GOARCH=amd64 GOTOOLCHAIN=go1.25.12 GOWORK=off go test -exec=/usr/bin/true ./...
CGO_ENABLED=0 GOOS=windows GOARCH=arm64 GOTOOLCHAIN=go1.25.12 GOWORK=off go test -exec=/usr/bin/true ./...
actionlint
GOTOOLCHAIN=go1.25.12 GOWORK=off go run ./scripts/release --version v0.2.0-beta.1 --out <new-output-a>
GOTOOLCHAIN=go1.25.12 GOWORK=off go run ./scripts/release --version v0.2.0-beta.1 --out <new-output-b>
diff -rq <new-output-a> <new-output-b>
gitleaks git --redact --exit-code 1 .
gitleaks dir --redact --exit-code 1 .
git diff --check
git fsck --strict --no-dangling
Review the pinned govulncheck version before each release audit. Record the
selected version in the evidence tracker. Stop if the exact minimum Go
toolchain has a reachable vulnerability, even when a newer host toolchain is
clean.
The default-branch rule must require the operating-system jobs, race job, lint job, dependency review, and one review. The rule must reject force pushes.
The release job must receive write permissions only in the tag workflow. Test jobs retain read-only repository permissions. Pin every third-party action to a reviewed commit.
The release must contain archives for these targets:
- Linux
amd64andarm64. - macOS
amd64andarm64. - Windows
amd64andarm64.
Each archive must contain the binary, LICENSE, README.md, and
THREAT-MODEL.md. The release must include SHA-256 checksums and build
provenance. Follow RELEASE.md for the local rehearsal, approved
tag, hosted attestation, and verification sequence.
- Use GitHub repository rulesets for branch controls.
- Use GitHub private vulnerability reporting for confidential reports.
- Use GitHub artifact attestations for build provenance.
- Follow the Go module publication sequence for the public tag.
- Use Producing Open Source Software for project, governance, release, and succession practices.
- Use the GitHub Open Source Guides for community health and maintainer practices.
- Review the OpenSSF Concise Guide for Developing More Secure Software.
- Review the OpenSSF Concise Guide for Evaluating Open Source Software.
- Map the secure-development lifecycle to the NIST Secure Software Development Framework.
The command sends no product telemetry. Keep that default for the public beta.
Collect beta evidence through explicit, redacted reports. Record only the
wip version, operating system, Git version, command outcome, and error code.
Also record ref_updated, intent_state, and whether reconciliation was
required. For initialization or archival recovery, record only the typed state
and whether the exact receipt-based retry completed.
Do not collect repository names, paths, file contents, commit messages, credentials, usernames, or remote addresses.
If the configuration is wrong before the first push, delete the empty hosted repository. Local history remains authoritative.
After the first push, treat the complete pushed history as disclosed. Removing a secret from Git history does not revoke it. Revoke the credential first, then publish repaired history under explicit owner direction.
After a tag is public, do not reuse that version. Mark the release as affected, publish a fixed beta version, and document the upgrade.
v1.0.0 requires a public beta period and real compatibility tests. It also
requires an independent security review and state migration policy. No open
data-loss or foreign-staged-content defect can remain.
Landing remains a separate product decision. If the public contract states the boundary clearly, capture-only behavior can remain the stable scope.