# Migration Summary — HEXT Standard 1.0

Transition from RFC-driven design project to published open standard.

**Publication Date:** July 7, 2026

---

## What Changed

| Aspect | Before (RFC Era) | After (Standard 1.0) |
|---|---|---|
| Repository role | RFC / draft specification | Canonical standard repository |
| Normative document | v2.2.0 Draft / RFC-NVS20 | [SPECIFICATION.md](SPECIFICATION.md) v1.0.0 Stable |
| Version | 2.2.0 Draft | 1.0.0 Stable |
| Status | Draft | Official Release (Stable) |
| Licensing | MIT (repository) | CC BY 4.0 (spec), CC0 (schemas), Apache 2.0 (implementations) |
| Conformance | Informal | Four defined levels (Core, MCP, Registry, Validator) |

---

## Document Hierarchy

```text
Design History (RFCs, drafts)     ← WHY (archived in history/)
        │
        ▼
HEXT Standard 1.0               ← WHAT (SPECIFICATION.md)
        │
        ▼
Schemas + Examples                ← HOW (schemas/, examples/)
        │
        ▼
Implementations                 ← Reference (Gemmina Intelligence)
```

---

## Archived Documents

| Document | New Location |
|---|---|
| SPECIFICATION.md (v2.2.0 draft) | [history/SPECIFICATION-v2.2.0-draft.md](history/SPECIFICATION-v2.2.0-draft.md) |
| RFC-NVS20 v2.2.0 | [history/RFC-NVS20_v2_2_0-source.md](history/RFC-NVS20_v2_2_0-source.md) (unchanged) |
| SPEC.md (v0.1.0) | [history/SPEC-v0.1.0-markdown-ledger.md](history/SPEC-v0.1.0-markdown-ledger.md) (unchanged) |

---

## Compatibility Assessment

| Document / Implementation | Valid under 1.0? | Action |
|---|---|---|
| HEXT Standard 1.0 conforming documents | Yes | Primary target |
| v2.2.0 draft Semantic XML | Likely compatible | Review against §6 conformance levels |
| v0.1.0 `.hxt` legacy format | Yes | Grandfather rules preserved |
| RFC-NVS20 as normative source | No | Superseded — use SPECIFICATION.md |
| `hxt.py` / `hxt.js` legacy refs | Yes (v0.1.0 only) | Migrate to hext-sdk-* for 1.0 |

---

## Implementer Checklist

- [ ] Read [SPECIFICATION.md](SPECIFICATION.md) in full
- [ ] Identify target conformance level (Core / MCP / Registry / Validator)
- [ ] Validate against [schemas/hext-core.xsd](schemas/hext-core.xsd)
- [ ] Test with [examples/](examples/) canonical XML files
- [ ] Review [history/DESIGN-HISTORY.md](history/DESIGN-HISTORY.md) for context only
- [ ] Cite HEXT Standard 1.0 (not RFC-NVS20) in documentation

---

## Recommended Git Tag

```bash
git tag -a v1.0.0 -m "HEXT Standard 1.0 — Initial Public Standard Release"
git push origin v1.0.0
```

Create GitHub Release using [RELEASE-1.0.0.md](RELEASE-1.0.0.md) as release notes.

---

*Migration to HEXT Standard 1.0 · July 7, 2026*