# Breakthrough Integration Pass — What Was Imported and Why

This pass integrates only the patterns that add real value across project scopes:

- certificate schemas and an engine contract (certificate or obstruction)
- a referee map template that ties every claim to a theorem and an artifact
- an analytic hypotheses menu to keep assumptions explicit
- a constants and thresholds ledger to avoid hidden inequalities
- a lightweight audit script to validate WSC margin rules

Integrated files

- `engine/schemas/`
  - `witness_stability_certificate_schema.json`
  - `witness_obstruction_schema.json`
  - `universality_report_schema.json`
  - `SCHEMA_GUIDE.md`

- `engine/contracts/`
  - `engine_contract.md`
  - `referee_map_template.md`
  - `analytic_hypotheses_menu.md`
  - `constants_thresholds.md`

- `engine/audit/`
  - `audit_wsc.py`

What was intentionally not imported

- domain-specific RU theorems and proofs that do not transfer to SFT’s phase-field setting
- large application writeups that are not needed to strengthen SFT’s core claim boundary

Reason

SFT gains the most by adopting the RU-style artifact discipline, not by borrowing unrelated mathematics.
