# Requirements: v1.95 L2 Promotion Pipeline Closure

## Milestone Goal

Close the L4→L2 promotion pipeline gap so that E2E research runs that validate
at L4 can actually land their results in L2 canonical knowledge.

## Archived Requirements

### Canonical Schema Extension

- [x] `REQ-PROMO-01`: `canonical-unit.schema.json` includes `negative_result`
  in the `unit_type` enum so that validated negative outcomes have a
  staging→canonical promotion path.

- [x] `REQ-PROMO-02`: three runtime proof schemas exist as formal JSON schemas
  in `research/knowledge-hub/schemas/`:
  - `lean-ready-packet.schema.json`
  - `proof-repair-plan.schema.json`
  - `statement-compilation-packet.schema.json`

### Promotion Bridge Code

- [x] `REQ-PROMO-03`: `candidate_promotion_support.py` `_resolve_promotion_context()`
  loads runtime proof schemas and includes their field definitions in the
  promotion context payload.

- [x] `REQ-PROMO-04`: `auto_promotion_support.py` `_validate_auto_promotion()`
  checks that runtime proof schema fields are present and valid before approving
  auto-promotion.

- [x] `REQ-PROMO-05`: `promotion_gate_support.py` `request_promotion()` includes
  runtime schema paths in the gate payload so downstream consumers can verify
  the promotion provenance.

- [x] `REQ-PROMO-06`: a new `runtime_schema_promotion_bridge.py` module
  translates runtime proof artifacts into canonical L2-facing bridge surfaces.

### HCI Foundation

- [x] `REQ-HCI-01`: `aitp status` output is structured into at most 3 tiers
  (summary → key sections → full detail) instead of a flat 40+ section dump.

- [x] `REQ-HCI-02`: `aitp hello` now acts as a zero-config introductory command
  and bootstrap persists `next_action_hint` into runtime state.

## Traceability

| Requirement | Phase | Final Status |
|-------------|-------|--------------|
| REQ-PROMO-01 | Phase 169 | Satisfied |
| REQ-PROMO-02 | Phase 169 | Satisfied |
| REQ-PROMO-03 | Phase 169.1 | Satisfied |
| REQ-PROMO-04 | Phase 169.1 | Satisfied |
| REQ-PROMO-05 | Phase 169.1 | Satisfied |
| REQ-PROMO-06 | Phase 169.1 | Satisfied |
| REQ-HCI-01 | Phase 169.2 | Satisfied |
| REQ-HCI-02 | Phase 169.2 | Satisfied |

## Outcome Notes

- `REQ-PROMO-01` and `REQ-PROMO-02` were satisfied by Phase `169` through the
  canonical-schema and package-schema closure work
- `REQ-PROMO-03` through `REQ-PROMO-06` were satisfied by Phase `169.1`
  through explicit runtime-schema bridge wiring across promotion paths
- `REQ-HCI-01` and `REQ-HCI-02` were satisfied by Phase `169.2` through
  bounded status, zero-config hello, and post-bootstrap next-action guidance

_Archived after milestone closure on 2026-04-14._
