Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -169,8 +169,10 @@ is `STOP`.
every Definition of Done item in Execution Directive v2.
- [`docs/empirical-release-plan.md`](docs/empirical-release-plan.md) — gated path from synthetic
preview to trained, calibrated, independently reproducible release.
- [`docs/standalone-launch.md`](docs/standalone-launch.md) — current production exit gates,
evidence status, and operator inputs, with MC-1 excluded from standalone scope only.
- [`docs/stateless-core-api.md`](docs/stateless-core-api.md#production-gates) — production
gates for the separate no-collection recommendation API; see its [release policy](docs/release-policy.md).
- [`docs/standalone-launch.md`](docs/standalone-launch.md) — broader research/directive
evidence gates and operator inputs; these do not make training a prerequisite for the stateless API.
- [`docs/launch-announcement.md`](docs/launch-announcement.md) — canonical launch copy plus
LinkedIn, X, and Hacker News variants with a publication checklist.
- [`docs/prior-art.md`](docs/prior-art.md) — explicit attribution links and the canonical novelty
Expand Down
9 changes: 9 additions & 0 deletions docs/standalone-launch.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# Standalone C3R production launch gate

> **Scope:** This document tracks the research collection, empirical release and
> broader directive-integration program. For the separate stateless,
> recommendation-only API launch, use [Core API production gates](stateless-core-api.md#production-gates)
> and the [scope-specific release policy](release-policy.md). Training, empirical
> DecisionMix publication and research-collection approval are not prerequisites
> for that no-collection API. Host and image security, rollback, live runtime,
> TLS/key isolation, operational controls and consumer acceptance still require
> their own evidence. This scope distinction is not production approval.

MC-1 product integration is explicitly out of scope for the **standalone** launch. It
remains in Execution Directive v2 and must not be marked complete there. This document
distinguishes tested code, private operational evidence, and public release evidence.
Expand Down
Loading