Skip to content
Wakeplane

Status

This page defines what Wakeplane means by alpha, beta, and 1.0. It is intentionally operational, not promotional.

Current Public State

Section titled “Current Public State”

Wakeplane is publicly labeled beta as of v0.2.0-beta.1.

The beta gate is now satisfied:

  • the repository is public at https://github.com/justyn-clark/wakeplane
  • trust files are present
  • public docs are code-verified
  • release binaries and checksums.txt are published
  • install paths were verified against the real public release
  • CI is green for the release cut

What Beta Means Here

Section titled “What Beta Means Here”

Beta means:

  • the public GitHub path resolves and is the canonical source
  • trust files exist and describe how the project operates
  • public docs match shipped code exactly
  • release binaries and checksums are published from tags
  • security posture is explicit on the site and in the repo
  • CI validates code, generated docs, and public-doc examples

Beta does not mean:

  • stable semver guarantees
  • auth or RBAC
  • distributed coordination
  • a web UI

Beta Gate

Section titled “Beta Gate”

Wakeplane is allowed to claim beta only when all of these are true:

  • GitHub link resolves publicly at https://github.com/justyn-clark/wakeplane
  • LICENSE, SECURITY.md, and CONTRIBUTING.md exist
  • public docs match the current repo exactly
  • install docs cover release downloads, go install, and source builds
  • release notes are structured and versioned
  • CI validates builds, tests, generated docs, and public-doc examples
  • at least one smoke-tested tagged release is publicly consumable

1.0 Gate

Section titled “1.0 Gate”

Wakeplane should not be labeled stable until all of these are true:

  • CLI surface is intentionally defined and stable enough for semver promises
  • API and run-status model are intentionally defined and stable enough for semver promises
  • docs are generated or verified directly from code paths
  • upgrade and migration expectations are documented
  • release publishing is routine and reproducible
  • at least one real internal production use case has run long enough to justify the claim
  • security posture is explicit and defensible for the intended deployment model

Explicitly Out Of Scope Today

Section titled “Explicitly Out Of Scope Today”
  • public multi-tenant SaaS scheduling
  • auth-heavy enterprise control plane deployments
  • distributed orchestration or DAG workflow systems
  • plugin loading or dynamic workflow discovery