Unattended Works

Launching soon

Launch status

Launch log

Launching soon means checkout is not open. This page lists the gates that have to close before that changes, and the log below records each step as it actually happens.

3 of 6 gates closed

What has to be true before checkout opens

  1. Product specification published

    Nine evidence domains with stable check IDs, severity rubric, report schema, and boundary list are public. Interactions are explicitly not_covered.

    closed

  2. Public site live with its own test suite

    Routes, accessibility contracts, and privacy contracts are enforced by tests in the repository.

    closed

  3. Audit runner produces a complete report from a real run

    Offline path and first live capture exist. Gate stays open for commercial delivery path completeness and live demo health, not for pretending interactions are covered.

    open

  4. Two runs of one definition against one unchanged target agree

    Reproducibility is a shipping gate, not a nice-to-have.

    open

  5. Report schema and check contract frozen at version 1

    Check contract: wea-v1-honest-freeze (ADR-0018). Report schema: freeze_id wea-v1-report-schema-freeze, status frozen, schema_version 1 (ADR-0019). Compatibility guards in test_report_schema_freeze.py; launch entry binds definition/schema/runner SHAs.

    closed

  6. Checkout open with a published price

    The price is published at the moment it can be paid, and not before. Catalog stays available:false and price_published:false.

    open

Intake

There is no waitlist form

Collecting email addresses would mean running a backend, storing personal data, and asking you to trust a privacy policy from a company that has not shipped anything yet. None of that is worth doing for a launch announcement.

Follow the launch log feed

The feed below is a static file on this site. Subscribing to it tells us nothing about you: no account, no address, no cookie, no request we can attribute to a person.

Why this page exists

A pre-launch site is the easiest place in a business to lie, usually by omission. The fix is a page that states the gates in public and gets updated when one closes, so the distance between the marketing and the software stays measurable.

What “launching soon” means here

It means exactly two things are true: the product is specified in public, and the product cannot be bought. It does not carry a date, because a date this early would be a guess presented as a commitment.

When checkout opens, this page changes and an entry appears in the log below.

Log

Entries, newest first

  1. WEA report schema v1 freeze (Gate 5)

    freeze_id wea-v1-report-schema-freeze: old fixtures remain readable; required-field removal fails without schema_version bump.

  2. WEA honest v1 contract freeze

    contract_id wea-v1-honest-freeze: every public check is implemented or explicitly not_covered; decision #3 sellable surface frozen.

  4. Host readiness audit Phase A is public on the product page

    Phase A host readiness specification published at /products/host-audit/ without inventing a checkout or a price.

  5. The live path produced its first evidence-backed report

    First real capture, sealed bundle, offline derivation, and deterministic package receipt — without pretending the product gate is closed.

  6. The audit produces reports, and one route can now request one

    Findings, reports, and a code-gated demo route — plus the one line of the privacy contract that had to change.

  7. Why there is no waitlist form

    A static feed instead of an email list, and the reasoning behind it.

  8. Repository bootstrapped and the specification made public

    The site exists, the specification is public, and nothing can be bought.