map-corpus

Map Corpus

Turn a topic plus seed URLs into a corpus slice that PROVES what was read: every discovered URL classified, every in-corpus resource decomposed by a deterministic script into a node manifest, every node carrying a relevance verdict backed by a byte-verified quote. The mapper supplies the layer docpage-digest names as its own non-goal ("Does not crawl. One page per run") without reimplementing, renaming, or modifying it.

The failure this skill exists to prevent: an agent handed a multi-page corpus glosses content and asserts it read everything. Here the denominators are never the agent's. Scripts emit the URL set from discovery snapshots and the node set from resource snapshots, and script gates diff the agent's classifications and verdicts against both.

Prerequisite (declared at point of use): python3 (3.9+) on PATH for the bundled scripts under this skill's discovery/, extraction/, and verification/ directories. Missing Python means say so and stop. There is no agent-judgment fallback for a deterministic denominator.

Arguments

• <topic>: short phrase naming the corpus; slugified into the slice name. <seed-url>...: one or more starting URLs.
• --epic <slug>, the epic under the work root (default: the topic slug).
• --max-resources N, the in-corpus bound declared in the link map (default 30). A breach stops the run and re-asks; it never silently proceeds.
• --granularity deep|section. JUDGMENT granularity, never row granularity: the inventory always carries exactly one row per manifest node (the gate's coverage invariant). deep (default) judges each node independently; section lets child rows inherit their top-level section's verdict/rationale (via parent_id), each keeping its own in-node evidence quote. Granularity and depth are per-invocation arguments by design, not userConfig.

Work root

Configured library dir: ${user_config.library_dir}

The work root resolves through the knowledge plugin's library_dir seam (the topic-docs carve-out, not memory_dir, not .claude/, not ${CLAUDE_PLUGIN_DATA}). Resolve once before the first write and record the absolute path in the checklist: unset or a surviving ${user_config.library_dir} token means the default .; relative resolves against ${CLAUDE_PROJECT_DIR}; absolute and ~ are verbatim; a ${NAME}/%NAME% env-var reference is read by you, never handed to a shell, an unset variable must fail loudly, not expand empty.