# Product-to-Production Continuum

Webdev Agent OS v13 preserves the reason a product exists from the moment a product direction is approved through production implementation, controlled release, measurement, and the next product decision.

## Operating chain

```text
Approved product decision
  → Product contract
  → Traceable requirements
  → Acceptance criteria
  → Studio work
  → Feature flags
  → Approved and verified release
  → Post-release measurements
  → Continue, revise, kill, or hold
```

A generated concept is not a production mandate. A completed task is not proof of user value. A deployed feature is not a successful product. Each stage requires evidence appropriate to that stage.

## Product contract

A contract is created only when the source product decision is approved and includes evidence references. It records:

- the source Product Laboratory program and tournament;
- the approved concept or prototype;
- the target Portfolio and Studio projects;
- audience, objective, and primary outcome;
- constraints and success criteria;
- target release and decision dates;
- accountable owners.

## Requirement trace

Each requirement can link to five evidence dimensions:

1. **Product evidence** — hypotheses and research records.
2. **Acceptance** — explicit criteria and verification evidence.
3. **Production work** — one or more Studio task IDs.
4. **Release** — the release in which the requirement appeared.
5. **Measurement** — the post-release metric used to evaluate it.

Each dimension contributes 20 points to the trace score. The score is a coverage indicator, not a claim that the underlying evidence is strong or statistically conclusive.

## Release gates

The system evaluates six gates:

- approved product decision with evidence;
- accepted requirements;
- verified must-have acceptance criteria;
- production work linked to requirements;
- verified release with evidence;
- completed post-release measurement.

A gate blocker is made visible; it is not silently waived.

## Feature flags

Feature flags provide controlled exposure and must record:

- default and treatment variants;
- rollout state and percentage;
- kill-switch availability;
- approval requirement;
- responsible owner;
- reviewer identity when activated.

Feature flags are control records. The included implementation does not modify an external flag provider or production deployment by itself.

## Measurements

A completed measurement requires:

- a metric and direction;
- baseline, target, and actual value;
- a sample size;
- a measurement window;
- evidence references;
- an interpretation that distinguishes directional evidence from proof.

## Lifecycle authority

Only a reviewer or owner can approve a continue, revise, kill, or hold decision. A decision requires:

- at least one verified release;
- at least one completed measurement;
- decision evidence;
- an explicit rationale.

The system does not infer that a missed target automatically means kill, or that a met target automatically means continue. Human judgment remains responsible for product commitment.

## Files

```text
config/continuum-seed.json
config/continuum-store.json
config/continuum-store.schema.json
scripts/continuum-core.js
scripts/continuum-cli.js
scripts/continuum-report.js
dashboard/continuum.js
reports/product-to-production/
```

## Commands

```bash
npm run continuum:stats
npm run continuum:report
node scripts/continuum-cli.js view
node scripts/continuum-cli.js view <contract-id>
node scripts/continuum-cli.js blueprint <contract-id>
```

## Safety boundary

Webdev Agent may generate a traceable plan and summarize evidence. It may not:

- invent product approval;
- mark acceptance criteria passed without evidence;
- claim a deployment occurred without release evidence;
- represent fixture metrics as live results;
- activate an external feature flag without an authorized integration;
- make the final product lifecycle decision without a reviewer.