sp-map-build

Rebuilds the schema v5 SQLite project cognition runtime from validated scan evidence.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-map-build-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-map-build
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-map-build
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-map-build-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a project scan produces a value-weighted evidence baseline, teams need a deterministic way to turn that raw evidence into a queryable project cognition database without hand-writing SQL or trusting chat memory. This Skill validates scan packets, compiles them through the project-cognition binary, and publishes a schema v5 SQLite runtime with graph nodes, edges, claims, path indexes, and alias catalogs. ## Core Features & Use Cases - Deterministic graph reconstruction: Runs validate-scan, build-from-scan, and validate-build through the project-cognition CLI so the SQLite runtime is compiled from accepted evidence rather than manual SQL. - Boundary and coverage acceptance: Validates repository-universe.json, scan-targets.json, coverage ledgers, and scan packets, routing back to sp-map-scan with a gap report when evidence is incomplete. - Claim lifecycle and routing substrate: Derives revisioned graph-claim lifecycle states, alias indexes, route packs, and queryable task-oriented bundles for downstream agent workflows. - Use Case: After running sp-map-scan on a brownfield repository, invoke this Skill to publish a query-ready cognition database that later workflows can navigate with compass queries and bounded live verification. ## Quick Start Rebuild the project cognition runtime from the completed scan baseline by invoking /sp-map-build and letting it validate, compile, and publish the schema v5 database.

Frequently Asked Questions about sp-map-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rebuild the project cognition database after a scan?▼

Run sp-map-build after sp-map-scan completes. It validates the scan package, executes project-cognition build-from-scan to compile the schema v5 SQLite database, then runs validate-build and only reports completion when readiness is query_ready.

What inputs does sp-map-build require before building?▼

It requires status.json, the evidence directory, provisional nodes/edges/observations, coverage.json, repository-universe.json, scan-targets.json, coverage-ledger.json, scan-queue.json, handoff-ledger.json, and scan packets under .specify/project-cognition/. Missing artifacts route back to sp-map-scan.

Can I build the cognition database with manual SQL instead?▼

No. Manual SQL, sqlite shell scripting, and hand-picked node subsets are explicitly forbidden as build paths. The project-cognition binary owns DB import, metadata, and status publication through its deterministic proposal compiler.

What happens when build-from-scan returns status blocked?▼

The build stops without creating or publishing a graph store. It reports the compiler errors, identity reconciliation details, rejections, merge records, and recovery action, and treats publication_allowed=false as a hard pre-publication block.

Does sp-map-build support older schema v4 cognition databases?▼

No. Schema v5 is current-only and does not migrate v4 or older databases. You must explicitly remove the incompatible project-cognition.db, then rerun sp-map-scan followed by sp-map-build with the current binary.

Why does the build fail with path index validation errors?▼

Path index rows come only from nodes.json paths, not coverage or repository-universe files. If validate-build reports missing path index rows, repair node paths in the scan package via sp-map-scan rather than inserting rows manually.