Static reference. Three layers: Schema (structure) → Taxonomy (classification) → Ontology (semantics & relationships).
Node Types
▸ Epics (multi-label: every epic also carries :Epic)
Label
Meaning
Key
RoadmapEpic
Backend product roadmap epic
uid
FERoadmapEpic
Frontend roadmap epic (team=Frontend)
uid
DevEpic
AzDO implementation epic
uid
▸ Planning
Feature
Child of a RoadmapEpic; discrete deliverable
uid
Phase
Delivery phase / milestone
name
Sprint
Sprint or iteration
week
Task
AzDO work item (User Story or Task type)
id
DevBranch
Git feature branch tied to a DevEpic
slug
SpecDir
Spec folder in AleidoTechCore/specs/
slug
▸ Concepts & Terminology
Term
Platform vocabulary term (snake_case lookup_key)
lookup_key
SubConcept
Named sub-concept of a Term; id = “parent::name”
id
Specification
Spec document (folder slug)
slug
UserStory
User story within a Specification
id
AcceptanceCriteria
AC on a UserStory
id
Relationship Types
▸ Delivery structure
CONTAINS
Phase contains Epics or Sprints
HAS_FEATURE
Epic → Feature
HAS_TASK
Epic → AzDO Task (wireframes, FE tasks)
IN_SPRINT
Epic scheduled into a Sprint
PRECEDES
Ordering constraint between Epics/Phases
▸ Development
IMPLEMENTS
DevEpic implements a RoadmapEpic
HAS_DEVELOPMENT_EPIC
RoadmapEpic → its DevEpic
HAS_FRONTEND_COUNTERPART
Backend Epic → FE counterpart
RELATED_TO
AzDO work item link; bidirectional
▸ Specification
SPECIFIED_IN
Epic ← Specification (always backend epic only)
SPECIFIES
Specification → Epic
HAS_USER_STORY
Specification → UserStory
HAS_ACCEPTANCE_CRITERIA
UserStory → AcceptanceCriteria
▸ Terminology (scored)
Rel
Semantic meaning
Score threshold
IMPLEMENTED_BY
Term is a core concept of this Epic
≥ 200
DEPENDS_ON
Term is a prerequisite concept
≥ 100
MENTIONED_IN
Term appears in Epic descriptions
≥ 1
HAS_SUB_CONCEPT
Term → SubConcept (child concept)
—
CONTAINS_TERMINOLOGY
Epic → Term (inverse of MENTIONED_IN)
—
MENTIONED_IN carries score (IDF-weighted) and embed_similarity (0–1). Use the Sim slider to filter by embed_similarity.
FE epic → spec navigation: SPECIFIED_IN always points to the backend epic. To reach a spec from a frontend epic: (fe)←[:HAS_FRONTEND_COUNTERPART]-(be)←[:SPECIFIED_IN]-(spec)
💬Chat
Loading…
Exports visible nodes & edges as JSON for LLM spec refinement.
Node Information
Click a node to see its information
✨AI Summary
Run a query or ask a question to generate an AI summary.
Plain English is converted to Cypher by an LLM, then run directly. Check the generated query before trusting the results.
🧠Reasoning…
Cypher
∿ Sim ≥0.00
Run a query to see the graph
Node Types
Node Details
Hover or click a node
⊕ Expand QueryAdds to or filters the existing graph
Graph
⚙ Graph Admin
Add Skill Type (Neo4j Label)
Add Relationship Type
—[]→
Creates a named placeholder relationship in Neo4j so it appears in the schema.
Wire it to real nodes via Cypher queries afterwards.