Status and Release Policy

This page explains how the public website interprets task status.

The public site uses a narrower release policy than the raw repository. This page explains that boundary so visitors can distinguish internal benchmark development from the public website surface.

Current Public Rule

For now, the public website shows only tasks marked test.

This is a deliberate release boundary. It keeps the site from implying that every internal task in the repository is already part of the public benchmark surface.

Why the Website Uses a Narrower Subset

The repository and the public website serve different purposes:

• the repository can contain tasks that are still being developed, calibrated, or validated
• the website should present a smaller, clearer public view of what is ready to inspect

That means raw internal status and public visibility are related, but not necessarily identical in the long run.

What test Means on the Website

At the moment, test is the simplest public-facing proxy for:

• ready to browse publicly
• stable enough to expose as a benchmark example
• appropriate to include in the generated public task catalog

What May Change Later

Over time, the benchmark may adopt a more explicit public visibility layer, for example:

• a dedicated public_ready concept
• a richer release policy for task visibility
• separate internal lifecycle and public website status

For now, however, the public website keeps things simple: test tasks only.