4 Porting Status
5 Porting Status
The grimoire source corpus has been ported into the public Quarto site and repository.
| Source | Ported form | Status |
|---|---|---|
software_magic_grimoire_v3_public_release.docx |
Main book chapters, public canon, full lexicon data, generated reference pages | Ported; full lexicon structurally authored; semantic review in progress |
pocket_grimoire_software_spellcraft_final.docx |
Pocket field guide, 300-rune pocket canon, quick-reference pages | Ported |
software_spellcraft_addendum_on_stacked_spells.docx |
Stackcraft chapter, stack grammar, six generated stack pages | Ported |
The first public seed was a complete structural port. The reader-linking pass improved the reading layer: guided paths, rune anchors, term index links, spell-to-rune links, stack-to-spell links, and canon maps. The full-canon pass removed explicit stubs. The semantic-canon pass now separates reviewed vocabulary from generated-draft long-tail entries.
5.1 Lexicon Completion
The master lexicon currently has 1645 authored entries and 0 stub entries.
| Status | Count |
|---|---|
| authored | 1645 |
5.2 Semantic Review
Structural completion means the record has required fields. Semantic review means the force, shadow, example, and prompt-use guidance have been reviewed as real operative vocabulary.
| Semantic Status | Count |
|---|---|
| reviewed | 510 |
| generated_draft | 1135 |
5.4 Completion by House
| House | Authored | Generated Draft | Reviewed | Canonical |
|---|---|---|---|---|
| Architecture, Abstraction, and Design | 112 | 0 | 112 | 0 |
| Language, Semantics, and Formal Shape | 137 | 0 | 137 | 0 |
| Data, State, and Representation | 122 | 104 | 18 | 0 |
| Transformation, Algorithms, and Working Verbs | 140 | 120 | 20 | 0 |
| Control Flow, Coordination, and Temporal Logic | 97 | 79 | 18 | 0 |
| Runtime, Memory, and Execution | 76 | 62 | 14 | 0 |
| Systems Programming and Operating-System Words | 86 | 74 | 12 | 0 |
| Networking and Distributed Systems | 116 | 96 | 20 | 0 |
| Databases, Persistence, and Time-Binding Words | 82 | 66 | 16 | 0 |
| Security, Trust, and Warding Words | 95 | 77 | 18 | 0 |
| Build, Tooling, Versioning, and Release | 76 | 60 | 16 | 0 |
| Testing, Verification, and Observability | 71 | 55 | 16 | 0 |
| Hardware, Embedded, and Performance-Near Words | 80 | 66 | 14 | 0 |
| Interface, UX, and Human-Facing Words | 60 | 50 | 10 | 0 |
| Promptcraft, AI-Oriented Engineering, and Spell Structure | 70 | 56 | 14 | 0 |
| Guarantee Words, Quality Attributes, and Behavioral Adjectives | 92 | 73 | 19 | 0 |
| Failure Words, Pathologies, and Counter-Spells | 70 | 50 | 20 | 0 |
| Compound Forms, Prefixes, Suffixes, and Naming Runes | 63 | 47 | 16 | 0 |
5.5 What Counts As Complete
- Source text is preserved.
- Every lexicon entry has a stable sigil, structured data record, generated reference page location, and direct anchor.
- Major and pocket canon entries link into the master house pages.
- Spell templates link to relevant runes and supporting reference pages.
- Stack workflows link to relevant spell templates, runes, and stack grammar.
- Lexicon entries are expected to remain authored: term-specific summary, force, shadow, and sense disambiguation where needed.
- The roadmap distinguishes archival completeness from reader experience completeness.