Pipeline architecture for wikitext-to-structured-data extraction. Existence public; specifics internal until coordinated with Memory Alpha admins.
Why this matters
License correction (2026-06-07): Memory Alpha is CC-BY-NC 4.0 (non-commercial), not CC-BY-SA. An ad-supported OLN cannot commercially rehost it, so the decided approach (Entry 034) is rebuild natively + move the community: recruit Memory Alpha editors, author Star Trek canon as Facts under OLN's license, and use Memory Alpha only as a human-verified reference signal (G-044 reference-only + G-068 independent-provenance). This entry's architecture is scoped to that approach, not bulk import.
Memory Alpha is the launch Franchise (Entry 009). Pipeline architecture needs design: AI-assisted parsing with human review? Confidence scoring? Migration order (entities first, then narrative pages)? Reusability for future Franchises that follow.
Sub-questions (public)
- Wikitext-to-structured-data extraction toolchain
- Attribution & license handling (Memory Alpha is CC-BY-NC → reference-only, not rehosted; CC-BY-SA compliance applies to other source wikis)
- Coordinated vs organic admin/contributor migration
- Data deduplication when Memory Alpha entities overlap with future Franchises
- Authoring tools available the day after migration (G-015)
- Legal posture for the migration itself (G-002)