Skip to content

docs: update the public site for the current Waveframe product and v0.5.6 stack #3

Description

@Wright-Shawn

Problem

The public site is materially behind the shipped product:

  • updates.html still presents Guard v0.13.0 and Cloud v0.3.0 as the current release ledger.
  • index.html and tools.html present Guard Inspector as the hosted commercial investigation surface.
  • Current coordinated releases are Cloud v0.5.6, Guard v0.15.0, Contract Compiler v0.4.0, Ledger v0.5.0, CRI-CORE v0.13.0, and Proposal Normalizer v0.2.0.
  • The current product boundary is Waveframe Cloud as the paid service, Waveframe Console as its web UI, Guard as the developer/runtime boundary, Ledger as authority publication, and Local Inspector as the local/offline companion.

This creates GTM friction precisely when the v0.5.6 governed coding-agent workflow is becoming the canonical five-minute demonstration.

Required outcome

Bring the public site into agreement with the current shipped product and release matrix without expanding the architecture.

Acceptance criteria

  • Update the release ledger through Cloud v0.5.6, Guard v0.15.0, and Compiler v0.4.0.
  • Present Waveframe Cloud + Console as the paid hosted product and human operating surface.
  • Present Guard as the installable developer integration and execution boundary.
  • Present Waveframe Ledger as deterministic authority authoring/publication while retaining the governance-ledger package name where install compatibility requires it.
  • Reframe standalone Guard Inspector as Local Inspector for local/offline workflows; hosted investigation belongs in Console.
  • Add one direct five-minute governed coding-agent demo/quickstart path once the v0.5.6 hosted promotion is proven.
  • Remove stale version and repository references from updates.html, compatibility.html, tools.html, and SUBMODULE_OVERVIEW.txt.
  • Validate internal links and complete a successful Pages deployment.

Boundary

The site should explain and verify the existing product. This issue does not introduce a new product, repository, architecture, or enforcement capability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions