Knowledge Base editor
The Knowledge Base (KB) is the heart of Lunova. It models your entities (clients, projects, tools, processes, risks, contracts) and their relationships, then serves as context for LLM analyses.
Key concepts
- Entity — a named node with an
entity_type(client,project,contact,tool,process,risk,contract) and astatus(active,inactive,archived,deprecated). - Note — a Markdown file with YAML front-matter. Each note belongs to an entity.
- Dependency —
[[wikilink]]between two notes. Used by the mapping analysis and impact detection. - Tags — arbitrary labels for filtering and segmentation.
Create and link a note
- KB → New note — choose the parent entity.
- Write the body in Markdown.
[[links]]to other notes automatically create a dependency. - Save. The note is validated against the schema (required front-matter:
entity,type,status,name,updated).
Obsidian import
From KB → Import, upload a folder (zip) or connect a synchronised vault. Lunova detects conflicts (duplicates, renames, merges, splits) and offers a Smart Import report that you validate case by case.
Graph visualisation
KB → Graph displays the topology of your dependencies. The colour code
reflects entity_type; edge thickness reflects frequency of appearance in
analysed events.
Consistency checks
- Broken links — note referenced via
[[wikilink]]but non-existent. - Orphan notes — no referring entity.
- Staleness — notes not updated for
KB_STALE_DAYS(90 days by default).
See cli.py check-kb for an automatable report.