Submit a Metadata Packet

1. Deposit your packet first

This site indexes metadata packets — it does not host the source files themselves. Before submitting, your packet must be deposited in a repository that assigns it a persistent identifier: an AXN in Alexanarch, a DOI from a DOI-issuing repository, or another persistent identifier, with a public record page (MPAI Specification v2.0, #1677, §9).

Every packet of the Crimson Hexagonal Archive is deposited in Alexanarch under an AXN, a content-derived identifier carrying the SHA-256 of the canonical bytes, with a date stamp, declared relations, and a record page harvestable through OAI-PMH and ResourceSync. Packets deposited on Zenodo before 2026-06-19 carry DOIs that were severed when the account was terminated that day; their Alexanarch records list each DOI as a former identifier, resolved through /s/doi/{doi}/.

Your packet should follow the MPAI Specification: aphoristic tooth, three confidence levels, disambiguation matrix, inverted fan architecture, citational hierarchy.

2. Submit via GitHub Issue

Once your packet is deposited and you have its identifier, submit it to this catalog by opening a GitHub Issue using the structured submission template:

The template will ask for:

• Title of the packet
• Persistent identifier and record URL (an AXN such as AXN:027D, or a DOI)
• Primary entity (the field-current concept the packet bridges)
• Secondary entity (the proposed extension)
• Aphoristic tooth (the holographic kernel — one or two sentences)
• Category (bridge, disambiguation, retrieval-architecture, forensic, methodology)
• Author(s)
• Date of deposit

You do not need a GitHub account to read these forms, but you do need one (free) to submit.

3. Or: open a Pull Request directly

If you are comfortable with Git, you can open a pull request that adds your packet to public/catalog.json. The schema is simple — see existing entries for examples.

4. Review process

Submissions are reviewed for:

1. Identifier verification: the packet must be deposited and reachable.
2. Specification compliance: the packet should follow the MPAI structure (aphoristic tooth present, confidence levels distinguished, disambiguation matrix present).
3. Categorical fit: the submission's claimed category must match its content.
4. No duplication: the packet must not duplicate an existing catalog entry without offering a meaningful version delta.

Review is light-touch and editorial. The catalog does not gatekeep on disciplinary content; it gatekeeps on structural integrity. A packet may be on any topic so long as it follows the MPAI form.

5. What gets indexed

Accepted packets appear in the public catalog with:

• Title (linked to the deposited record)
• Primary → secondary entity bridge
• Aphoristic tooth as the holographic kernel
• Author(s), date, identifier

The catalog points to the deposited record. It does not republish the full text.

6. Licensing

The catalog itself is open. Submission grants permission to index your packet's metadata (title, identifier, tooth, entity bridge, authors, date) on this site. Your packet's content remains under whatever license you applied at deposit (CC BY 4.0 is standard for the existing catalog).