# Public Milestones

These milestones are written for public communication. They are not a replacement for the private internal task list.

## Milestone table

| Milestone | Public description | Public status |
|---|---|---|
| M0 - Private foundation | Repository, specification structure, and initial planning models exist in private development. | Done |
| M1 - Public documentation pack | Prepare public-safe vision, roadmap, milestones, use cases, and benchmark-summary pages. | Done |
| M2 - Toronto stadium scenario narrative | Explain the stadium location-capacity planning scenario in plain language. | Initial public page published |
| M3 - Toronto stadium benchmark summary | Publish reviewed summaries comparing optimized alternatives with a benchmark site, including transport-access and planning tradeoffs. | Planned |
| M4 - Airport-transit scenario narrative | Explain the airport-transit hub and regional candidate-system scenario in public-safe language. | Initial public page published |
| M5 - Benchmark methodology | Publish how benchmark summaries are structured, what metrics are reported, and what assumptions remain private. | Initial public page published |
| M6 - Public visuals | Publish selected charts, maps, or screenshots that explain outcomes without exposing code. | Initial SVG assets published |
| M7 - Controlled demo | Share a non-code demonstration, static outputs, or a limited interface. | Future |
| M8 - External feedback | Invite feedback from planners, researchers, investors, agencies, and infrastructure analysts. | Future |

## Current public milestone

The current public milestone is **M3 - Toronto stadium benchmark summary**.

Completion criteria:

- benchmark scenario name is clear
- assumptions are documented at a public-safe summary level
- outputs have been reviewed
- units and limitations are stated
- no source code, proprietary data, or internal tasks are exposed
- sensitivity results are included where needed

## Evidence milestones

The most important credibility milestones are not code releases. They are evidence releases:

1. a clear benchmark methodology
2. a reviewed summary of results
3. sensitivity results showing how assumptions affect recommendations
4. selected visuals that explain tradeoffs
5. limitations stated plainly

## What should remain private

The following should not be treated as public milestones unless explicitly approved later:

- source-code release
- private algorithm release
- full task-board release
- raw data release
- unrevised experimental results
- internal bug or limitation logs
- exact calibration details that create competitive advantage

## Suggested milestone language for announcements

> Sarus-Optimizer has published its first public information pack, including the vision, roadmap, use cases, case narratives, milestone status, benchmark-summary approach, and public visuals while the source code remains private.