Robert Helewka
7859264359
- Introduced `neo4j-schema-init.py` for creating the foundational schema for the personal knowledge graph used by multiple AI assistants. - Implemented functionality for creating constraints, indexes, and sample nodes, along with comprehensive testing of the schema. - Added `neo4j-validate.py` to perform validation checks on the Neo4j knowledge graph, including constraints, indexes, sample nodes, relationships, and junk data detection. - Enhanced logging for better traceability and debugging during schema initialization and validation processes.
2.3 KiB
2.3 KiB
Neo4j Knowledge Graph — Work Team
You have access to a unified Neo4j knowledge graph shared across fifteen AI assistants (9 personal, 4 work, 2 engineering).
Principles
- Full work domain access — All work assistants can read and write all work nodes
- Always MERGE on
id— Check before creating to avoid duplicates - Use consistent IDs — Format:
{type}_{identifier}_{qualifier}(e.g.,client_acme_corp,opp_acme_cx_2025) - Always set timestamps —
created_aton CREATE,updated_aton every SET - Use
domainon universal nodes — Person, Location, Event, Topic, Goal takedomain: 'personal'|'work'|'both' - Link to existing nodes — Connect across domains; that's the graph's power
Standard Patterns
// Check before creating
MATCH (n:NodeType {id: 'your_id'}) RETURN n
// Create with MERGE (idempotent)
MERGE (n:NodeType {id: 'your_id'})
ON CREATE SET n.created_at = datetime()
SET n.name = 'Name', n.updated_at = datetime()
// Link to existing nodes
MATCH (a:TypeA {id: 'a_id'}), (b:TypeB {id: 'b_id'})
MERGE (a)-[:RELATIONSHIP]->(b)
Work Node Types
| Category | Nodes |
|---|---|
| Business | Client, Contact, Opportunity, Proposal, Project |
| Market Intelligence | Vendor, Competitor, MarketTrend, Technology |
| Content & Visibility | Content, Publication |
| Professional Development | Skill, Certification, Relationship |
| Daily Operations | Task, Meeting, Note, Decision |
Assistant Focus Areas
| Assistant | Primary Focus | Key Nodes |
|---|---|---|
| Alan | Strategy & Business Model | Client, Vendor, Competitor, MarketTrend, Decision |
| Ann | Marketing & Visibility | Content, Publication, Topic |
| Jeffrey | Proposals & Sales | Opportunity, Proposal, Contact |
| Jarvis | Daily Execution | Task, Meeting, Note |
Cross-Team Reads
- Personal team: Books (for skill development), Trips (for client travel), Goals (for career alignment)
- Engineering: Infrastructure (hosting projects), Prototypes (for client demos)
- Universal nodes: Person, Location, Event, Topic, Goal (shared by all)
Full Schema Reference
See docs/neo4j-unified-schema.md for complete node definitions, all fields, and relationship types.