name	pdf2gep
description	Converts a PDF (local path or URL) into schema-valid GEP (Genome Evolution Protocol) assets for EvoMap. Emits a retrieval-oriented Gene (category=explore) plus a reference Capsule (source_type=reference) with a real asset_id. Does NOT produce execution Capsules; use skill2gep for that.

pdf2gep

Convert a PDF into GEP bundles that can be uploaded to EvoMap as retrieval / reference knowledge.

Scope (read first)

pdf2gep is a protocol adapter for reference knowledge, not procedural knowledge.

The emitted Capsule has source_type = "reference", an empty execution_trace, and a zero blast_radius. outcome.status = "success" means only "the chunk was extracted" — it is NOT evidence that the associated Gene has been validated in practice.
For procedural knowledge (a SKILL.md describing a workflow plus real executions), use skill2gep instead.
The GEP paper (Wang, Ren, Zhang, arXiv:2604.15097) validates Gene-as-control-interface on 45 code-science tasks. That result does not carry over to retrieval Genes; treat pdf2gep output as retrieval material.

Usage

node index.js <pdf_url_or_path>

Output: temp/evomap_assets/batch_<timestamp>.json, an array of { gene, capsule } entries.

Workflow

Fetch/Read -- Download the PDF from URL (browser User-Agent) or read the local file. Record the PDF's sha256.
Extract -- Use pdf-parse-fork to pull out raw text.
Chunk -- Fixed-width split of ~4000 chars per chunk (not semantic; see README scope note). Record each chunk's sha256.
Wrap -- Build an explore Gene + reference Capsule per chunk, validate against @evomap/gep-sdk, and stamp each with a real asset_id (computeAssetId) and the SDK's schema_version.
Save -- Write the batch to temp/evomap_assets/batch_<ts>.json.

Publishing

Use evolver (the GEP reference runtime, https://github.com/EvoMap/evolver) to publish:

evolver publish --bundle temp/evomap_assets/batch_<ts>.json

The hub routes source_type: "reference" Capsules into the retrieval index, separate from execution Capsules.

Dependencies

@evomap/gep-sdk (schema_version + asset_id computation)
pdf-parse-fork
Node.js 18+ (built-in fetch)

Invariants for consumers

source_type === "reference" on the Capsule
execution_trace is always empty
blast_radius.files === 0 && blast_radius.lines === 0
outcome.status === "success" means "reference extracted", not "task validated" — always read it with source_type
the chunk text + provenance live in the content object; asset_id verifies under @evomap/gep-sdk

Validators that expect execution Capsules MUST filter these out (or treat them explicitly as reference material).

pdf2gep

Convert a PDF into GEP bundles that can be uploaded to EvoMap as retrieval / reference knowledge.

Scope (read first)

pdf2gep is a protocol adapter for reference knowledge, not procedural knowledge.

The emitted Capsule has source_type = "reference", an empty execution_trace, and a zero blast_radius. outcome.status = "success" means only "the chunk was extracted" — it is NOT evidence that the associated Gene has been validated in practice.

For procedural knowledge (a SKILL.md describing a workflow plus real executions), use skill2gep instead.

The GEP paper (Wang, Ren, Zhang, arXiv:2604.15097) validates Gene-as-control-interface on 45 code-science tasks. That result does not carry over to retrieval Genes; treat pdf2gep output as retrieval material.

Usage

node index.js <pdf_url_or_path>

Output: temp/evomap_assets/batch_<timestamp>.json, an array of { gene, capsule } entries.

Workflow

Fetch/Read -- Download the PDF from URL (browser User-Agent) or read the local file. Record the PDF's sha256.

Extract -- Use pdf-parse-fork to pull out raw text.

Chunk -- Fixed-width split of ~4000 chars per chunk (not semantic; see README scope note). Record each chunk's sha256.

Wrap -- Build an explore Gene + reference Capsule per chunk, validate against @evomap/gep-sdk, and stamp each with a real asset_id (computeAssetId) and the SDK's schema_version.

Save -- Write the batch to temp/evomap_assets/batch_<ts>.json.

Publishing

Use evolver (the GEP reference runtime, https://github.com/EvoMap/evolver) to publish:

evolver publish --bundle temp/evomap_assets/batch_<ts>.json

The hub routes source_type: "reference" Capsules into the retrieval index, separate from execution Capsules.

Dependencies

@evomap/gep-sdk (schema_version + asset_id computation)

pdf-parse-fork

Node.js 18+ (built-in fetch)

Invariants for consumers

source_type === "reference" on the Capsule

execution_trace is always empty

blast_radius.files === 0 && blast_radius.lines === 0

outcome.status === "success" means "reference extracted", not "task validated" — always read it with source_type

the chunk text + provenance live in the content object; asset_id verifies under @evomap/gep-sdk

Validators that expect execution Capsules MUST filter these out (or treat them explicitly as reference material).