CRIMSON HEXAGONAL ARCHIVE: TERM INDEX WORK PLAN EA-REGISTRY-TERMINDEX-PLAN v1.0

Lee Sharks

AXN:0351.EMPIRICAL.🟢🏗️🙏📜🔔🌱

CRIMSON HEXAGONAL ARCHIVE: TERM INDEX WORK PLAN EA-REGISTRY-TERMINDEX-PLAN v1.0

Lee Sharks · 2026-06-16 · Term-index research work plan · v1.0

phase 3: human-in-the-loop passearegistrytermindexplanphase 1: metadata pullcontinuity protocolcrimson hexagonalprogress trackingsemantic economysemantic physics

Description

This document is a living work plan for extracting and governing the Crimson Hexagonal Archive’s coined vocabulary. Its initial phase templates say “not started,” but the later progress table and session log record substantial execution. It should therefore be read as a plan whose headings preserve the original design while its ledger records the state reached during the same work cycle. The planned workflow has five phases. Metadata are pulled from every repository record and candidate terms extracted from titles, descriptions, keywords, codes, quotations, and emphasis. File bodies are then processed in resumable batches. A human review removes ordinary-language false positives, restores missed coinages, assigns definitions and categories, and reconciles known institutional lists. The resulting JSON and Markdown index are deposited and surfaced as a searchable table. High-priority terms may later receive provenance packets. The progress ledger reports 845 metadata records processed, 1,524 repeated candidate terms, tiered canonicalization, 735 of 800 downloadable body records processed, sixty-five download failures, and 129 of 131 capture-registry queries cross-referenced. Merge, noise filtering, human review, and the final v1.0 index remained pending, while an initial raw-data deposit was in progress. This is a valuable continuity artifact because it makes unfinished work visible. It is not itself the final index, and the extracted counts are not counts of confirmed coinages. Automated phrase extraction will include names, ordinary phrases, bibliographic language, duplicates, and template artifacts. The internal instructions referring to /home/claude/, session compaction, and present_files are ephemeral execution notes and should not be treated as public architectural requirements.

Wiki Article

Crimson Hexagonal Archive: Term Index Work Plan is a living plan and progress ledger for building a canonical vocabulary index. It describes metadata extraction, body-text processing, human review, cross-reference work, publication, versioning, and optional provenance-packet generation. Although the original phase headings begin as “not started,” the later ledger records extensive completion of metadata and body processing. Merge, human validation, and the final index were still pending. The candidate-term totals are automated extraction results rather than a verified count of archive coinages.

Also published as a standalone entry: /s/wiki/836/

Concepts Defined

Progress checkpoint [structural]
After Phase 1, we have ~60-70% of coinages from metadata alone. Save all three files to /home/claude/ and present. If session compacts here, next session loads these files and proc

Session 1 (16 June 2026) [structural]
Work plan created. Phase 1.1 complete (845 records pulled). Phase 1.2 complete (1,524 terms extracted with count>=2; 5,951 total unique keywords). Phase 1.3 (canonicalization and c

Full Text

CRIMSON HEXAGONAL ARCHIVE: TERM INDEX WORK PLAN

# CRIMSON HEXAGONAL ARCHIVE: TERM INDEX WORK PLAN

EA-REGISTRY-TERMINDEX-PLAN v1.0

## EA-REGISTRY-TERMINDEX-PLAN v1.0

Author: Lee Sharks (ORCID 0009-0000-1599-0703)

Date: 16 June 2026

Status: Work plan with progress tracking

Purpose: Systematic extraction, canonicalization, and versioning of all coined terms, concepts, entities, frameworks, operators, institutions, heteronyms, and designations across the Crimson Hexagonal Archive (~841+ deposits)

---

Rationale

## Rationale

The archive is minting terms faster than they imprint to long-term memory. An estimated 200-300 coined concepts exist across 841+ deposits without a unified index. Once built, the index becomes:

A retrieval surface (each term becomes a searchable node)
A density map (which terms cluster, which are orphaned)
A versioning base (new deposits append; the initial build is the hard part)
An MPAI generator (each indexed term can receive a provenance coupling kernel)
A measure of the archive's actual vocabulary (what it has coined vs. what it thinks it has coined)

---

Phase 1: Metadata Pull

## Phase 1: Metadata Pull

Status: NOT STARTED

Estimated compute: 30-45 minutes

Resumable: Yes — paginate via Zenodo API, save after each page

1.1 Pull all records from crimsonhexagonal community

### 1.1 Pull all records from crimsonhexagonal community

API endpoint: https://zenodo.org/api/records?communities=crimsonhexagonal&size=200&page=N
Expected: ~841 records across 5 pages
Save: JSON file with record ID, DOI, title, description, keywords, creators, publication_date, version, related_identifiers
Output: termindex-metadata-raw.json

1.2 Extract terms from metadata fields

### 1.2 Extract terms from metadata fields

Parse each record's title, keywords, and description
Extract: capitalized multi-word phrases, EA-* codes, quoted terms, terms in bold/strong tags
Output: termindex-metadata-terms.json — rough list with source DOI for each term

1.3 Deduplicate and categorize

### 1.3 Deduplicate and categorize

Categories: metric, operator, framework, institution, heteronym, journal, concept, designation, entity, tool
Canonical form + variants
Output: termindex-metadata-canonical.json

Progress checkpoint: After Phase 1, we have ~60-70% of coinages from metadata alone. Save all three files to /home/claude/ and present. If session compacts here, next session loads these files and proceeds to Phase 2.

---

Phase 2: File Content Extraction

## Phase 2: File Content Extraction

Status: NOT STARTED

Estimated compute: 2-3 hours (may require multiple sessions)

Resumable: Yes — track which record IDs have been processed

2.1 Download and read markdown files

### 2.1 Download and read markdown files

For each record, download .md files (skip PDFs, images, audio)
Read each file, extract terms not already in Phase 1 output
Track progress: termindex-file-progress.json — list of processed record IDs
Output: termindex-file-terms.json

2.2 Batch processing strategy

### 2.2 Batch processing strategy

Process in batches of 50 records
After each batch: save progress, save extracted terms
If session compacts: next session reads progress file, resumes from last batch

2.3 Merge with metadata terms

### 2.3 Merge with metadata terms

Combine Phase 1 and Phase 2 extractions
Identify terms that appear only in file contents (not metadata)
Output: termindex-merged.json

Progress checkpoint: After Phase 2, we have ~90% of coinages. The remaining 10% are implicit terms that require human judgment.

---

Phase 3: Human-in-the-Loop Pass

## Phase 3: Human-in-the-Loop Pass

Status: NOT STARTED

Estimated compute: 1-2 sessions of review

3.1 Lee reviews the merged index

### 3.1 Lee reviews the merged index

Flag false positives (ordinary words extracted as coinages)
Flag missing terms (coinages Lee knows exist but weren't extracted)
Assign canonical definitions (20 words max per term)
Confirm categories

3.2 Cross-reference against known lists

### 3.2 Cross-reference against known lists

Dodecad heteronyms (12 positions)
Framework numbering (FW1-FW15)
Journal names (6 journals, 2 imprints)
EA-* designation system
Hex prefix allocations
Room system (r.01-r.26)
Operator registry (LOS, THUMB, UKTP, etc.)

3.3 Output: termindex-v1.0.json

### 3.3 Output: termindex-v1.0.json

Full canonical index with:

term, abbreviation, category, canonical_definition

first_deposit (DOI), author_position (heteronym)
related_terms, hex_prefix, framework_number
variants (alternate forms that should resolve to this entry)

---

Phase 4: Deposit and Surface

## Phase 4: Deposit and Surface

Status: NOT STARTED

4.1 Deposit to Zenodo

### 4.1 Deposit to Zenodo

EA-REGISTRY-TERMINDEX-01 v1.0
JSON + markdown rendering
Community: crimsonhexagonal
Keywords: term index, coined concepts, semantic physics, operative semiotics, Crimson Hexagonal Archive

4.2 Surface deployment

### 4.2 Surface deployment

Page on leesharks.com or crimsonhexagonal.org
Searchable, sortable table
Each term links to its first-deposit DOI

4.3 Versioning protocol

### 4.3 Versioning protocol

Each new deposit session: extract terms from new deposits, append to index
Version forward: v1.1, v1.2, etc.
The initial build (Phases 1-3) is the hard part; versioning is incremental

---

Phase 5: MPAI Generation (optional, high-value)

## Phase 5: MPAI Generation (optional, high-value)

Status: NOT STARTED

5.1 For each high-priority term, generate an MPAI kernel

### 5.1 For each high-priority term, generate an MPAI kernel

Provenance coupling statement
Non-erasure condition
Canonical definition
First-deposit DOI

5.2 Batch deposit MPAIs

### 5.2 Batch deposit MPAIs

10-20 per session
Priority: terms most likely to enter the retrieval basin

---

Progress Tracking

## Progress Tracking

Phase

Step

Status

Output File

Records Processed

Notes

1.1 Metadata pull

COMPLETE

termindex-metadata-raw.json

845/845

845 records, 6,256 unique kw

1.2 Term extraction

COMPLETE

termindex-metadata-terms.json

845/845

1,524 terms (count>=2), 5,951 total

1.3 Canonicalization

COMPLETE

termindex-tiered.json

845/845

178 Tier 1, 332 Tier 2, cross-ref with registry

2.1 File download

COMPLETE

termindex-file-progress.json

735/800

444 new Tier 1, 540 new Tier 2 from file contents

2.2 Batch processing

COMPLETE

termindex-file-progress.json

735/800

65 records had download failures

2.3 Merge

PENDING

termindex-merged.json

—

Needs noise filtering + human review

3.1 Human review

PENDING

—

~2,000 terms for review

3.2 Cross-reference

COMPLETE

termindex-crossref.json

—

129/131 registry queries matched

3.3 Final index

PENDING

termindex-v1.0.json

—

After human review

4.1 Deposit

IN PROGRESS

—

Initial deposit with raw data

4.2 Surface

NOT STARTED

—

5.1 MPAI generation

NOT STARTED

—

---

Continuity Protocol

## Continuity Protocol

If a session hits compaction limits during this work:

All progress files are saved to /home/claude/ and presented via present_files
The progress tracking table above is updated in this document
The next session receives this work plan document and any saved progress files
The next session reads the progress table, loads saved files, and resumes from the last completed step

Key files for continuity:

This work plan: termindex-workplan.md
Raw metadata: termindex-metadata-raw.json
Extracted terms: termindex-metadata-terms.json
Canonical index: termindex-metadata-canonical.json
File processing progress: termindex-file-progress.json
File-extracted terms: termindex-file-terms.json
Merged index: termindex-merged.json
Final index: termindex-v1.0.json

---

Session Log

## Session Log

Session 1 (16 June 2026): Work plan created. Phase 1.1 complete (845 records pulled). Phase 1.2 complete (1,524 terms extracted with count>=2; 5,951 total unique keywords). Phase 1.3 (canonicalization and categorization) ready for next session or human review. Key finding: the archive has 6,256 keyword instances across 845 records, with the top terms being Crimson Hexagonal Archive (439), semantic economy (267), Crimson hexagon (248), distributed epic (154), NH-OS (149), operative semiotics (124), training layer literature (121). The API paginates at max size=25, requiring 34 pages. The metadata-raw and metadata-terms JSON files are the continuity artifacts for the next session.

Version history

Series: SERIES-BODYMATCH-836

● #836 v1.0 — current ← this deposit
○ #1214 v0.1 (superseded)

Record modifications

2026-08-01 — content_type: Wave 1 repair: audit ledger v1.1 recommended_content_type (workplan v1.5 §6 W1, MANUS batch approval 2026-08-01)
2026-08-01 — journal: Wave 6 venue normalization: full canonical journal name per MANUS ruling 2026-08-01 (venues.json authority)
2026-08-04 — publisher: PUB-POPULATE: dc:publisher from venues.json v1.1 press mapping (CP-R3 RULED-EXTENDED 2026-08-01); Alexanarch = publisher of record where no imprint applies
2026-08-04 — status: W12 STATUS-VOCABULARY v1.0 (MANUS ratified 2026-08-04): controlled vocabulary {ACTIVE, SUPERSEDED, WITHDRAWN, DRAFT}; MINTED_UNREVIEWED false on a 100%-audited corpus; freetext annotations preserved losslessly in body_status.status_note
2026-08-05 — body_status: W13 TIER 2 byte unglue (whitespace-only, content-identical, code-fence-safe)
2026-08-05 — body_status: W13 TIER-2 REGRESSION REPAIRED: split headings rejoined
2026-08-05 — description: DW-??? intake (LABOR-prepared, TACHYON-verified: AXN match + factual probes vs record body)

The deposited text is immutable; these are changes to the record's metadata and declared state.

Traversal

← #835 The Conveyor Belt and the Compression Machine: OKF Without Output Governance — Predictiv#837 The Josephus Thesis Is Not the Jesus Myth Thesis: Preemptive Disambiguation MPAI (EA-MPA →

This deposit cites (1)

#1214 Crimson Hexagonal Archive: Term Index v0.1 — Systematic Extraction of Coined Terms Acros by EA identifier