# Phase 165.3-04 Summary

Status: implemented in working tree

## Goal

Open `165.3 / 999.62` by removing protocol jargon from the operator-facing
checkpoint wording that humans actually see, and add a small CI gate so the old
phrases do not silently re-enter those support surfaces.

## What Landed

- checkpoint wording in `topic_shell_support.py` now uses plain language for
  the roadmap-targeted replacements:
  - `adjudication route` -> `how to judge this`
  - `L0 recovery` -> `restart from source intake`
  - `promotion approval` -> `ready to save as reusable knowledge`
  - `bounded route` -> `chosen approach`
- promotion checkpoints now ask whether a candidate is ready to save as
  reusable knowledge instead of asking the operator to "approve promotion"
- contradiction checkpoints now ask how to judge the conflict instead of
  asking for an "adjudication route"
- execution-lane checkpoints now use `chosen approach` in the operator
  response prompt
- operator-facing mode/runtime wording in:
  - `knowledge_hub/mode_envelope_support.py`
  - `knowledge_hub/runtime_bundle_support.py`
  was aligned to the same plain-language vocabulary
- new regression gate:
  - `research/knowledge-hub/tests/test_hci_jargon_gate.py`
  - scans the targeted operator-facing support files for the banned phrases

## Verification

- `python -m pytest research/knowledge-hub/tests/test_hci_jargon_gate.py -q`
- `python -m pytest research/knowledge-hub/tests/test_aitp_service.py -q -k "execution_lane_confirmation_checkpoint_created_before_dispatch or pending_human_promotion_gate_creates_operator_checkpoint or contradiction_checkpoint_uses_plain_language or materialize_steering_preserves_manual_innovation_direction_text or run_topic_loop_materializes_steering_artifacts_from_human_request"`
- `python -m pytest research/knowledge-hub/tests/test_runtime_scripts.py -q`

## Outcome

`165.3` now has a mechanical anti-jargon guard instead of relying only on
manual review:

- the main checkpoint questions read more like operator instructions and less
  like internal protocol labels
- the replacement vocabulary is now enforced in CI for the targeted human
  surfaces

## Remaining Open Work Inside 165.3

- `999.64` natural-language steering via `aitp steer-topic --text ...`
- `999.70` human-oriented subprocess failure messages
- tightening `hello` toward the full onboarding contract after the steering and
  failure surfaces settle
