# Requirements Archive: v1.0 Runtime Hardening

**Archived:** 2026-03-31
**Status:** SHIPPED

For current requirements, see `.planning/REQUIREMENTS.md`.

---

# Requirements: AITP vNext Runtime Hardening

**Defined:** 2026-03-31
**Core Value:** AITP must turn vague but meaningful research starts into bounded, durable, and explainable runtime state without pretending uncertainty is already resolved.

## v1 Requirements

### Topic Start

- [ ] **START-01**: A source-heavy new topic can populate `idea_packet.initial_idea` from registered source material when usable source content exists.
- [ ] **START-02**: A source-heavy new topic produces a bounded `first_validation_route` that reflects the inferred lane instead of a generic fallback.
- [ ] **START-03**: A topic start can surface a novelty target from available source evidence or leave an explicit honest gap when none is found.

### Status Explainability

- [ ] **STAT-01**: `topic_state.json` carries machine-readable status explainability for why the topic is here, the current route, the last evidence return, the active human need, and blockers.
- [ ] **STAT-02**: `operator_console.md` and `resume.md` render the explainability surface without reconstructing old chat or logs.
- [ ] **STAT-03**: A later session can answer "what happened, why, and what next?" from current runtime artifacts alone.

### Steering And Checkpoints

- [ ] **STEER-01**: Material steering redirects land in durable steering artifacts before deeper execution continues.
- [ ] **STEER-02**: True human checkpoints become durable runtime artifacts instead of implicit queue text or ad hoc prose.

### Strategy Memory

- [ ] **MEM-01**: Meaningful runs can record strategy-memory rows with bounded confidence and evidence references.
- [ ] **MEM-02**: Later bounded action selection can consult strategy memory without treating it as validated scientific truth.

### Acceptance And Workflow

- [ ] **ACC-01**: At least one code-backed AITP acceptance lane exists and follows benchmark-first research discipline.
- [ ] **ACC-02**: Repo docs explain when to stay in ordinary GSD workflow and when to enter AITP-governed topic execution.

## v2 Requirements

### Packaging

- **PKG-01**: AITP install/update flow works as a polished one-click or marketplace-facing package across supported agents.
- **PKG-02**: Coexistence with other agent systems is documented for public users, not just local operator notes.

## Out of Scope

| Feature | Reason |
|---------|--------|
| Replacing AITP runtime artifacts with GSD summaries | GSD organizes execution, but research state must remain in AITP runtime files |
| Broad new lane expansion before topic-start quality improves | The current bottleneck is sharp bounded starts, not more topic families |
| Claiming autonomous closure for real theory topics | Human checkpoints and bounded validation remain mandatory |

## Traceability

| Requirement | Phase | Status |
|-------------|-------|--------|
| START-01 | Phase 1 | Complete |
| START-02 | Phase 1 | Complete |
| START-03 | Phase 1 | Complete |
| STAT-01 | Phase 1 | Complete |
| STAT-02 | Phase 1 | Complete |
| STAT-03 | Phase 1 | Complete |
| STEER-01 | Phase 2 | Complete |
| STEER-02 | Phase 2 | Complete |
| MEM-01 | Phase 3 | Complete |
| MEM-02 | Phase 3 | Complete |
| ACC-01 | Phase 4 | Complete |
| ACC-02 | Phase 5 | Complete |

**Coverage:**
- v1 requirements: 12 total
- Mapped to phases: 12
- Unmapped: 0

---
*Requirements defined: 2026-03-31*
*Last updated: 2026-03-31 after milestone completion reconciliation*
