Documentation Index
Fetch the complete documentation index at: https://docs.jedify.com/llms.txt
Use this file to discover all available pages before exploring further.
A Contextual Definition explains what a concept means to the business, not just what columns exist. It should enable Jedify to select the right nodes (entities) to answer user questions accurately and consistently.
Include these components:
-
Concept Name & Core Identity
State what the concept is in clear business terms.
Example: “Deal Management represents the end‑to‑end lifecycle of a commercial opportunity from prospecting through closure and revenue recognition.”
-
Business Purpose
Explain why the concept exists and which business problems it solves.
Example: “This concept is the central hub for assessing deal performance, pipeline health, commercial terms, and acquisition efficiency across markets.”
-
Key Business Questions
List the questions this concept helps answer (prioritize the most common/critical ones).
Examples: “How many active deals exist for an account?” “What is the combined deal value?” “What is the current stage and average time to close?”
-
Primary Attributes
Describe the core characteristics the concept tracks - use business language.
Example: “Tracks unique identifiers, names, categorization, commercial terms (valuations, payment structure, contract type), and lifecycle stages (qualification → closed‑won).”
Tip: Add synonyms/aliases to improve recognition (e.g., PL → Playlist, GMV → Gross Merchandise Value). For ambiguous terms (e.g., status, type, tag), include a short clarification or example list.
Consistency Tip: You can draft initial definitions using an LLM (e.g., ChatGPT) by providing examples from existing nodes. Keep tone neutral, concise, and factual.
