map

Overview

Derives a technologies-to-ontology report by scanning package.json manifests, canonicalising package names, and comparing the findings to the ontology’s Technologies section. The output lives in .ouro/ouro.md and highlights coverage gaps.

Usage

ouro map

Inputs & Outputs

• Inputs: discovered npm packages (collected during the run) and the existing .ouro/ontology/main.md file.
• Outputs: .ouro/ouro.md, summarising which technologies appear in code and how they map to ontology entries.

When to Use

• After gather or whenever dependencies change materially.
• During ontology edits to verify the documented technology list reflects reality.

Follow-up Checklist

• Review .ouro/ouro.md for unmapped technologies and adjust the ontology as needed.
• Commit the updated mapping file together with ontology revisions.